diff --git a/website/content/docs/k8s/connect/cluster-peering/tech-specs.mdx b/website/content/docs/k8s/connect/cluster-peering/tech-specs.mdx
index 2d27a4f369..f6c0ae0316 100644
--- a/website/content/docs/k8s/connect/cluster-peering/tech-specs.mdx
+++ b/website/content/docs/k8s/connect/cluster-peering/tech-specs.mdx
@@ -158,12 +158,4 @@ To learn how to change the mesh gateway mode to `local` on your Kubernetes deplo
 
 The `exported-services` CRD is required in order for services to communicate across partitions with cluster peering connections. Basic guidance on using the `exported-services` configuration entry is included in [Establish cluster peering connections](/consul/docs/k8s/connect/cluster-peering/usage/establish-peering#export-services-between-clusters).
 
-Refer to [`exported-services` configuration entry](/consul/docs/connect/config-entries/exported-services) for more information.
-
-## ACL specifications
-
-If ACLs are enabled, you must add tokens to grant the following permissions:
-
-- Grant `service:write` permissions to services that define mesh gateways in their server definition.
-- Grant `service:read` permissions for all services on the partition.
-- Grant `mesh:write` permissions to the mesh gateways that participate in cluster peering connections. This permission allows a leaf certificate to be issued for mesh gateways to terminate TLS sessions for HTTP requests.
+Refer to [`exported-services` configuration entry](/consul/docs/connect/config-entries/exported-services) for more information.
\ No newline at end of file