docs: fix typos, IDs are UUIDs, /acl/token endpoints manage ACL tokens (#5736)

website/source/api/acl/policies.html.md

@@ -3,7 +3,7 @@ layout: api
 page_title: ACL Policies - HTTP API
 sidebar_current: api-acl-policies
 description: |-
-  The /acl/policy endpoints manage Consul's ACL Policies.
+  The /acl/policy endpoints manage Consul's ACL policies.
 ---
 
 -> **1.4.0+:**  The APIs are available in Consul versions 1.4.0 and later. The documentation for the legacy ACL API is [here](/api/acl/legacy.html)
@@ -12,7 +12,7 @@ description: |-
 
 The `/acl/policy` endpoints [create](#create-a-policy), [read](#read-a-policy),
 [update](#update-a-policy), [list](#list-policies) and
-[delete](#delete-a-policy)  ACL policies in Consul.  
+[delete](#delete-a-policy) ACL policies in Consul.
 
 For more information on how to setup ACLs, please see
 the [ACL Guide](https://learn.hashicorp.com/consul/advanced/day-1-operations/production-acls).
@@ -165,7 +165,7 @@ The table below shows this endpoint's support for
 
 ### Parameters
 
-- `ID` `(string: <required>)` - Specifies the ID of the policy to update. This is
+- `ID` `(string: <required>)` - Specifies the UUID of the policy to update. This is
    required in the URL path but may also be specified in the JSON body. If specified
    in both places then they must match exactly.
 

website/source/api/acl/tokens.html.md

@@ -11,7 +11,7 @@ description: |-
 # ACL Token HTTP API
 
 The `/acl/token` endpoints [create](#create-a-token), [read](#read-a-token),
-[update](#update-a-token), [list](#list-tokens), [clone](#clone-a-token) and [delete](#delete-a-token)  ACL policies in Consul.
+[update](#update-a-token), [list](#list-tokens), [clone](#clone-a-token) and [delete](#delete-a-token) ACL tokens in Consul.
 
 For more information on how to setup ACLs, please see
 the [ACL Guide](https://learn.hashicorp.com/consul/advanced/day-1-operations/production-acls).
@@ -503,7 +503,7 @@ The table below shows this endpoint's support for
 
 ### Parameters
 
-- `AccessorID` `(string: <required>)` - Specifies the accessor ID of the ACL policy to
+- `AccessorID` `(string: <required>)` - Specifies the accessor ID of the ACL token to
   delete. This is required and is specified as part of the URL path.
 
 - `ns` `(string: "")` - **(Enterprise Only)** Specifies the namespace of the

website/source/docs/guides/agent-encryption.html.md

@@ -14,7 +14,7 @@ To complete the RPC encryption section, you must have [configured agent certific
 
 ## Gossip Encryption
 
-To enable gossip encryption, you need to use an encryption key when starting the Consul agent. The key can be simple set with the `encrypt` parameter in the agent configuration file. Alternatively, the encryption key can be placed in a seperate configuration file with only the `encrypt` field, since the agent can merge multiple configuration files. The key must be 32-bytes, Base64 encoded. 
+To enable gossip encryption, you need to use an encryption key when starting the Consul agent. The key can be simple set with the `encrypt` parameter in the agent configuration file. Alternatively, the encryption key can be placed in a separate configuration file with only the `encrypt` field, since the agent can merge multiple configuration files. The key must be 32-bytes, Base64 encoded.
 
 You can use the Consul CLI command, [`consul keygen`](/docs/commands/keygen.html), to generate a cryptographically suitable key.
 

website/source/docs/guides/autopilot.html.md

@@ -52,7 +52,7 @@ following are the defaults.
 ```
 
 All Consul servers should have Autopilot and its features either enabled
-or disabled to ensure consistency accross servers in case of a failure. Additionally,
+or disabled to ensure consistency across servers in case of a failure. Additionally,
 Autopilot must be enabled to use any of the features, but the features themselves
 can be configured independently. Meaning you can enable or disable any of the features
 separately, at any time.