diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx
index 567dda3307..0bae34e173 100644
--- a/website/content/docs/connect/cluster-peering/index.mdx
+++ b/website/content/docs/connect/cluster-peering/index.mdx
@@ -20,7 +20,7 @@ Cluster peering is a process that allows Consul clusters to communicate with eac
 3. Export services between clusters.
 4. Create intentions to authorize services for peers.
 
-For detailed instructions on setting up cluster peering, refer to [Create and Manage Peering Connections](/docs/connect/cluster-peering/create-manage-peering).
+For detailed instructions on establishing cluster peering connections, refer to [Create and Manage Peering Connections](/docs/connect/cluster-peering/create-manage-peering).
 
 ### Differences between WAN federation and cluster peering
 
@@ -39,11 +39,11 @@ Regardless of whether you connect your clusters through WAN federation or cluste
 | Forwards service requests for service discovery    |    ✅     |    ❌     |
 | Shares key/value stores                            |    ✅     |    ❌     |
 
-
 ## Beta release features and constraints
 
-The cluster peering beta includes the following features and functionality:
+The cluster peering beta release includes the following features and functionality:
 
+- **Consul v1.14 beta only**: Dyanmic traffic control with a `ServiceResolver` config entry can target failover and redirects to service instances in a peered cluster.
 - Consul datacenters that are already federated stay federated. You do not need to migrate WAN federated clusters to cluster peering.
 - Mesh gateways for _service to service traffic_ between clusters are available. For more information on configuring mesh gateways across peers, refer to [Service-to-service Traffic Across Peered Clusters](/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers).
 - You can generate peering tokens, establish, list, read, and delete peerings, and manage intentions for peering connections with both the API and the UI.
@@ -54,7 +54,7 @@ Not all features and functionality are available in the beta release. In particu
 
 - Mesh gateways for _server to server traffic_ are not available.
 - Services with node, instance, and check definitions totaling more than 4MB cannot be exported to a peer.
-- Dynamic routing features such as splits, custom routes, and redirects cannot target services in a peered cluster.
+- Some dynamic routing features, such as splits and custom routes, cannot target services in a peered cluster.
 - 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.
 - Because non-Enterprise Consul instances are restricted to the `default` namespace, Consul Enterprise instances cannot export services from outside of the `default` namespace to non-Enterprise peers.