From 5936a61de4e3c1163de207055adf74c17e3cf30b Mon Sep 17 00:00:00 2001 From: Tu Nguyen Date: Tue, 21 Jun 2022 16:15:34 -0700 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 07dd3cf675..263fe81247 100644 --- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx +++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx @@ -57,7 +57,7 @@ In the peer parameter, specify a name for the first cluster. The `PeeringToken` When you connect server agents through cluster peering, they will peer their default partitions. To establish peering connections for other partitions through server agents, you must specify the partitions you want to peer using the `Partition` field of the request body. -## Connect service endpoints +## Export service endpoints After you establish a connection between the clusters, you need to create a configuration entry that defines the services that are available for other clusters. Consul uses this configuration entry to advertise service information and support service mesh connections across clusters.