diff --git a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
index fc0f946a4f..5662868834 100644
--- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
+++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
@@ -35,7 +35,7 @@ Every time you generate a peering token, a single-use establishment secret is em
 <Tabs>
 <Tab heading="Consul API">
 
-In `cluster-01`, issue a request for a peering token.
+In `cluster-01`, use the [`/peering/token` endpoint](/api-docs/peering#generate-a-peering-token) to issue a request for a peering token.
 
 ```shell-session
 $ curl --request POST --data '{"PeerName":"cluster-02"}' --url http://localhost:8500/v1/peering/token
@@ -75,13 +75,17 @@ Next, use the peering token to establish a secure connection between the cluster
 <Tabs>
 <Tab heading="Consul API">
 
-In one of the client agents in "cluster-02," use `peering_token.json` to establish the peering connection. This endpoint does not generate an output unless there is an error.
+In one of the client agents in "cluster-02," use `peering_token.json` and the [`/peering/establish` endpoint](/api-docs/peering#establish-a-peering-connection) to establish the peering connection. This endpoint does not generate an output unless there is an error.
 
 ```shell-session
 $ curl --request POST --data @peering_token.json http://127.0.0.1:8500/v1/peering/establish
 ```
 
 When you connect server agents through cluster peering, they peer their default partitions. To establish peering connections for other partitions through server agents, you must add the `Partition` field to `peering_token.json` and specify the partitions you want to peer. For additional configuration information, refer to [Cluster Peering - HTTP API](/api-docs/peering).
+
+
+You can dial the `peering/establish` endpoint once per peering token. Peering tokens cannot be reused after being used to establish a connection. If you need to re-establish a connection, you must generate a new peering token.
+
 </Tab>
 
 <Tab heading="Consul UI">
@@ -118,6 +122,7 @@ Services = [
         ## during the peering process.
         Peer = "cluster-02"
       }
+  }
     ]
 ```
 
@@ -173,7 +178,7 @@ You can list all active peering connections in a cluster.
 <Tabs>
 <Tab heading="Consul API">
 
-After you establish a peering connection, [query the `/peering/` endpoint](/api-docs/peering#list-all-peerings) to get a list of all peering connections. For example, the following command requests a list of all peering connections on `localhost` and returns the information as a series of JSON objects:
+After you establish a peering connection, [query the `/peerings/` endpoint](/api-docs/peering#list-all-peerings) to get a list of all peering connections. For example, the following command requests a list of all peering connections on `localhost` and returns the information as a series of JSON objects:
 
 ```shell-session
 $  curl http://127.0.0.1:8500/v1/peerings
@@ -222,7 +227,7 @@ You can get information about individual peering connections between clusters.
 <Tabs>
 <Tab heading="Consul API">
 
-After you establish a peering connection, [query the `/peering/:name` endpoint](/api-docs/peering#read-a-peering-connection) to get peering information about for a specific cluster. For example, the following command requests peering connection information for "cluster-02" and returns the info as a JSON object:
+After you establish a peering connection, [query the `/peering/` endpoint](/api-docs/peering#read-a-peering-connection) to get peering information about for a specific cluster. For example, the following command requests peering connection information for "cluster-02" and returns the info as a JSON object:
 
 ```shell-session
 $  curl http://127.0.0.1:8500/v1/peering/cluster-02