From f5947051d8f9decbe32b25fac1a1280d708a28eb Mon Sep 17 00:00:00 2001 From: Dan Stough Date: Mon, 14 Nov 2022 11:25:09 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> --- .../docs/connect/cluster-peering/create-manage-peering.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 0d1795d6dddf..651826c04d2d 100644 --- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx +++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx @@ -12,9 +12,9 @@ A peering token enables cluster peering between different datacenters. Once you ## Create a peering connection -Cluster peering is enabled by default on Consul servers as of 1.14. For additional information, like disabling peering, refer to [Configuration Files](/docs/agent/config/config-files). +Cluster peering is enabled by default on Consul servers as of v1.14. For additional information, including options to disable cluster peering, refer to [Configuration Files](/docs/agent/config/config-files). -Use the following steps to create a peering connection: +The process to create a peering connection is a sequence with multiple steps: 1. Create a peering token 1. Establish a connection between clusters