diff --git a/modules/ossm-federation-config-smcp.adoc b/modules/ossm-federation-config-smcp.adoc
index 915c61fa348f..7bc3a6541f89 100644
--- a/modules/ossm-federation-config-smcp.adoc
+++ b/modules/ossm-federation-config-smcp.adoc
@@ -31,7 +31,6 @@ spec:
         enabled: true
         requestedNetworkView:
         - green-network
-        routerMode: sni-dnat
         service:
           metadata:
             labels:
@@ -45,7 +44,6 @@ spec:
         enabled: true
         requestedNetworkView:
         - blue-network
-        routerMode: sni-dnat
         service:
           metadata:
             labels:
@@ -58,7 +56,6 @@ spec:
     additionalIngress:
       ingress-green-mesh:
         enabled: true
-        routerMode: sni-dnat
         service:
           type: LoadBalancer
           metadata:
@@ -71,7 +68,6 @@ spec:
             name: https-discovery  #note HTTPS here
       ingress-blue-mesh:
         enabled: true
-        routerMode: sni-dnat
         service:
           type: LoadBalancer
           metadata:
@@ -146,14 +142,6 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |Networks associated with exported services.
 |Set to the value of `spec.cluster.network` in the SMCP for the mesh, otherwise use <ServiceMeshPeer-name>-network. For example, if the `ServiceMeshPeer` resource for that mesh is named `west`, then the network would be named `west-network`.
 |
-
-|spec:
-  gateways:
-    additionalEgress:
-      <egressName>:
-        routerMode:
-|The router mode to be used by the gateway.
-|`sni-dnat`
 |
 
 |spec:
@@ -194,14 +182,6 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |`true`/`false`
 |`true`
 
-|spec:
-  gateways:
-    additionalIngress:
-      <ingressName>:
-        routerMode:
-|The router mode to be used by the gateway.
-|`sni-dnat`
-|
 
 |spec:
   gateways:
@@ -266,7 +246,6 @@ In the following example, the administrator is configuring the SMCP for federati
      additionalIngress:
       ingress-green-mesh:
         enabled: true
-        routerMode: sni-dnat
         service:
           type: NodePort
           metadata: