[MINOR] fixed internal link and some typos (#528)

* fixed internal link

Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>

* customise -> customize

Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>

* synchronise -> synchronize

Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>

* added abbreviation markdown for JWT

Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>

docs/HowTo/Backup/Backup.md

@@ -24,7 +24,7 @@ to Besu.
 The default data location is the Besu installation directory, or `/opt/besu/database` if using the
 [Besu Docker image](../../HowTo/Get-Started/Run-Docker-Image.md).
 
-Having some data reduces the time to synchronise a new node. You can perform periodic backups of
+Having some data reduces the time to synchronize a new node. You can perform periodic backups of
 the data directory and send the data to your preferred backup mechanism. For example, cron job and
 rsync, archives to the cloud such as s3, or `tar.gz` archives.
 

docs/HowTo/Limit-Access/Local-Permissioning.md

@@ -120,7 +120,7 @@ Transaction validation against the accounts allowlist occurs at the following po
 * Added to a block by a mining node.
 
 After adding transactions to a block, the transactions are not validated against the allowlist
-when received by another node. That is, a node can synchronise and add blocks containing
+when received by another node. That is, a node can synchronize and add blocks containing
 transactions from accounts that are not on the accounts allowlist of that node.
 
 The following diagram illustrates applying local and onchain permissioning rules.

docs/HowTo/Upgrade/Upgrade-Node.md

@@ -13,7 +13,7 @@ We recommend:
 ## Ansible
 
 You can use the [Ansible role on Galaxy](https://galaxy.ansible.com/pegasyseng/hyperledger_besu)
-directly or customise it to suit your needs.
+directly or customize it to suit your needs.
 
 Upgrade the Besu version on nodes by running the play with the new version. For more information,
 see the [Galaxy Readme](https://galaxy.ansible.com/pegasyseng/hyperledger_besu). The play:

docs/Tutorials/Examples/Nat-Manager-Kubernetes.md

@@ -40,7 +40,7 @@ Deploy a `LoadBalancer` service for Besu to recover IP address and ports.
 
 !!!example
 
-    Here is an example that you can customise with your own ports and routing rules.
+    Here is an example that you can customize with your own ports and routing rules.
 
     ```yaml
     ---

docs/Tutorials/Privacy/Configuring-Multi-Tenancy.md

@@ -25,7 +25,7 @@ IBFT-Network/
 
 !!! note
 
-    This tutorial uses [JSON Web Token (JWT) public key authentication] to create the tenant's JWT,
+    This tutorial uses [JWT public key authentication] to create the tenant's JWT,
     but you can also use [username and password authentication].
 
 ## Prerequisites
@@ -128,7 +128,10 @@ token. For example, ensure you enable the `PRIV` and `EEA` APIs for privacy.
 [Use the authentication token to make requests].
 
 <!-- Links -->
-[JSON Web Token (JWT) public key authentication]: ../../HowTo/Interact/APIs/Authentication.md#jwt-public-key-authentication
+[JWT public key authentication]: ../../HowTo/Interact/APIs/Authentication.md#jwt-public-key-authentication
 [username and password authentication]: ../../HowTo/Interact/APIs/Authentication.md#username-and-password-authentication
 [generate the private and public key pair]: ../../HowTo/Interact/APIs/Authentication.md#1-generate-a-private-and-public-key-pair
 [Use the authentication token to make requests]: ../../HowTo/Interact/APIs/Authentication.md#using-an-authentication-token-to-make-requests
+
+<!-- Abbreviations -->
+*[JWT]: JSON Web Token