diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx
index 9c049456029d..f43a65007c8b 100644
--- a/website/content/docs/connect/cluster-peering/index.mdx
+++ b/website/content/docs/connect/cluster-peering/index.mdx
@@ -46,6 +46,6 @@ Regardless of whether you connect your clusters through WAN federation or cluste
 Consider the following technical constraints:
 
 - Services with node, instance, and check definitions totaling more than 50MB cannot be exported to a peer.
-- Two admin partitions in the same datacenter cannot be peered. Consider using [`exported-services`](/docs/connect/config-entries/exported-services#exporting-services-to-peered-clusters) directly.
+- Two admin partitions in the same datacenter cannot be peered. Use [`exported-services`](/docs/connect/config-entries/exported-services#exporting-services-to-peered-clusters) directly.
 - The `consul intention` CLI command is not supported. To manage intentions that specify services in peered clusters, use [configuration entries](/docs/connect/config-entries/service-intentions).
 - Accessing key/value stores across peers is not supported.