diff --git a/modules/ossm-federation-create-meshPeer.adoc b/modules/ossm-federation-create-meshPeer.adoc
index a70c3d75d79b..2b33f4a10d6f 100644
--- a/modules/ossm-federation-create-meshPeer.adoc
+++ b/modules/ossm-federation-create-meshPeer.adoc
@@ -12,7 +12,7 @@ This module included in the following assemblies:
 * Two or more {product-title} 4.6 or above clusters.
 * The clusters must already be networked.
 * The load balancers supporting the services associated with the federation gateways must be configured to support raw TLS traffic.
-* Each cluster must have a version 2.1 `ServiceMeshControlPlane` configured to support federation deployed.
+* Each cluster must have a version 2.1 or later `ServiceMeshControlPlane` configured to support federation deployed.
 * An account with the `cluster-admin` role.
 
 ////
diff --git a/modules/ossm-federation-prerequisites.adoc b/modules/ossm-federation-prerequisites.adoc
index 3713f471529d..0bb56d78e93d 100644
--- a/modules/ossm-federation-prerequisites.adoc
+++ b/modules/ossm-federation-prerequisites.adoc
@@ -9,7 +9,7 @@ This module included in the following assemblies:
 The {SMProductName} federated approach to joining meshes has the following prerequisites:
 
 * Two or more {product-title} 4.6 or above clusters.
-* Federation was introduced in {SMProductName} 2.1. You must have the {SMProductName} 2.1 Operator installed on each mesh that you want to federate.
-* You must have a version 2.1 `ServiceMeshControlPlane` deployed on each mesh that you want to federate.
+* Federation was introduced in {SMProductName} 2.1 or later. You must have the {SMProductName} 2.1 or later Operator installed on each mesh that you want to federate.
+* You must have a version 2.1 or later `ServiceMeshControlPlane` deployed on each mesh that you want to federate.
 * You must configure the load balancers supporting the services associated with the federation gateways to support raw TLS traffic. Federation traffic consists of HTTPS for discovery and raw encrypted TCP for service traffic.
 * Services that you want to expose to another mesh should be deployed before you can export and import them. However, this is not a strict requirement. You can specify service names that do not yet exist for export/import. When you deploy the services named in the `ExportedServiceSet` and `ImportedServiceSet` they will be automatically made available for export/import.