backport of commit 359409b (#17928)

Co-authored-by: David Yu <dyu@hashicorp.com>

website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx

@@ -89,9 +89,9 @@ metadata:
 spec:
   defaultForFailover: true
   members:                                   
-    partition: partition-1
-    partition: partition-2
-    peer: dc2-partition-1
+    - partition: partition-1
+    - partition: partition-2
+    - peer: dc2-partition-1
 ```
 
 </CodeBlockConfig>
@@ -106,9 +106,9 @@ metadata:
 spec:
   defaultForFailover: true
   members:                                   
-    partition: partition-2
-    partition: partition-1
-    peer: dc2-partition-1  
+    - partition: partition-2
+    - partition: partition-1
+    - peer: dc2-partition-1  
 ```
 
 </CodeBlockConfig>
@@ -123,9 +123,9 @@ metadata:
 spec:
   defaultForFailover: true
   members:                                   
-    partition: partition-1
-    peer: dc1-partition-1
-    peer: dc2-partition-2
+    - partition: partition-1
+    - peer: dc1-partition-1
+    - peer: dc2-partition-2
 ```
 
 </CodeBlockConfig>
@@ -287,4 +287,4 @@ $ kubectl apply --filename api.yaml
 
 It is possible to combine the service intentions configuration entry for creating sameness groups with the entry required to [authorize services for peers](/consul/docs/connect/cluster-peering/usage/establish-cluster-peering#authorize-services-for-peers).
 
-In this workflow, configure the `sources` block with the `samenessGroup` field instead of the `peer` field. You should write the `sameness-group` configuration entry to Consul before referencing it in the `service-intentions` configuration entry.
+In this workflow, configure the `sources` block with the `samenessGroup` field instead of the `peer` field. You should write the `sameness-group` configuration entry to Consul before referencing it in the `service-intentions` configuration entry.