diff --git a/website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx b/website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx
index d2a590bcff..0b3f1d43c2 100644
--- a/website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx
+++ b/website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx
@@ -146,7 +146,7 @@ The following example demonstrates how to format three different `ExportedServic
 apiVersion: consul.hashicorp.com/v1alpha1
 Kind: ExportedServices
 metadata:
-  name: product-group-export
+  name: partition-1
 spec:
   services:
     - name: api
@@ -163,7 +163,7 @@ spec:
 apiVersion: consul.hashicorp.com/v1alpha1
 Kind: ExportedServices
 metadata:
-  name: product-group-export
+  name: partition-2
 spec:
   services:
     - name: api
@@ -180,7 +180,7 @@ spec:
 apiVersion: consul.hashicorp.com/v1alpha1
 Kind: ExportedServices
 metadata:
-  name: product-group-export
+  name: partition-1
 spec:
   services:
     - name: api
@@ -291,4 +291,4 @@ If your goal for peering clusters is to create a sameness group, you can write a
 
 When `defaultForFailover=true` in a sameness group CRD, additional upstream configuration is not required.
 
-After creating a sameness group, you can also set up failover between services in a sameness group. Refer to [Failover with sameness groups](/consul/docs/connect/manage-traffic/failover/sameness) for more information.
\ No newline at end of file
+After creating a sameness group, you can also set up failover between services in a sameness group. Refer to [Failover with sameness groups](/consul/docs/connect/manage-traffic/failover/sameness) for more information.