From ccbe00e469650597adf25206b5de01acf3134474 Mon Sep 17 00:00:00 2001
From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
Date: Fri, 17 Jun 2022 12:35:35 -0500
Subject: [PATCH] Update
 website/content/docs/connect/cluster-peering/create-manage-peering.mdx

---
 .../docs/connect/cluster-peering/create-manage-peering.mdx      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 f0849cd60c..07dd3cf675 100644
--- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
+++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
@@ -24,7 +24,7 @@ You can generate peering tokens and initiate connections using the Consul API on
 
 To begin the cluster peering process, generate a peering token in one of your clusters. The other cluster uses this token to establish the peering connection.
 
-In “cluster-01,” issue a request for a peering token using the HTTP API.
+In `cluster-01`, issue a request for a peering token using the [HTTP API](/api-docs/peering).
 
 ```shell-session
 $ curl --request POST --data '{"PeerName":"cluster-02"}' --url http://localhost:8500/v1/peering/token