From 05dd1a8b1fbe7e609a095a1984a90fe96ac8b422 Mon Sep 17 00:00:00 2001 From: Tu Nguyen Date: Thu, 17 Aug 2023 12:02:29 -0700 Subject: [PATCH] fix broken link --- website/content/docs/connect/failover/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/failover/index.mdx b/website/content/docs/connect/failover/index.mdx index a4c51b799731..022b6542a971 100644 --- a/website/content/docs/connect/failover/index.mdx +++ b/website/content/docs/connect/failover/index.mdx @@ -44,4 +44,4 @@ In networks with multiple datacenters or partitions that share a peer connection You can configure sameness groups for this type of network. Sameness groups allow you to define a group of admin partitions where identical services are deployed in identical namespaces. After you configure the sameness group, you can reference the `SamenessGroup` parameter in service resolver, exported service, and service intention configuration entries, enabling you to add or remove cluster peers from the group without making changes to every cluster peer every time. -Refer to [Sameness groups usage page](/consul/docs/connect/cluster-peering/usage/sameness-groups) for more information. +Refer to [Sameness groups usage page](/consul/docs/connect/cluster-peering/usage/create-sameness-groups) for more information.