Merge pull request #73013 from rh-tokeefe/OSSM-6086

OSSM-6086: Formatting issue in federation gateway parameters table

Author: skopacz1

modules/ossm-federation-config-smcp.adoc

@@ -200,15 +200,15 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalEgress:
-      <egressName>:
+      <egress_name>:
 |Define an additional egress gateway for _each_ mesh peer in the federation.
 |
 |
 
 |spec:
   gateways:
     additionalEgress:
-      <egressName>:
+      <egress_name>:
         enabled:
 |This parameter enables or disables the federation egress.
 |`true`/`false`
@@ -217,7 +217,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalEgress:
-      <egressName>:
+      <egress_name>:
         requestedNetworkView:
 |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`.
@@ -226,7 +226,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalEgress:
-      <egressName>:
+      <egress_name>:
         service:
           metadata:
             labels:
@@ -238,7 +238,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalEgress:
-      <egressName>:
+      <egress_name>:
         service:
           ports:
 |Used to specify the `port:` and `name:` used for TLS and service discovery. Federation traffic consists of raw encrypted TCP for service traffic.
@@ -255,7 +255,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalIgress:
-      <ingressName>:
+      <ingress_name>:
         enabled:
 |This parameter enables or disables the federation ingress.
 |`true`/`false`
@@ -265,7 +265,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalIngress:
-      <ingressName>:
+      <ingress_name>:
         service:
           type:
 |The ingress gateway service must be exposed through a load balancer that operates at Layer 4 of the OSI model and is publicly available.
@@ -275,7 +275,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalIngress:
-      <ingressName>:
+      <ingress_name>:
         service:
           type:
 |If the cluster does not support `LoadBalancer` services, the ingress gateway service can be exposed through a `NodePort` service.
@@ -285,7 +285,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalIngress:
-      <ingressName>:
+      <ingress_name>:
         service:
           metadata:
             labels:
@@ -297,7 +297,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalIngress:
-      <ingressName>:
+      <ingress_name>:
         service:
           ports:
 |Used to specify the `port:` and `name:` used for TLS and service discovery. Federation traffic consists of raw encrypted TCP for service traffic. Federation traffic consists of HTTPS for discovery.
@@ -307,7 +307,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
 |spec:
   gateways:
     additionalIngress:
-      <ingressName>:
+      <ingress_name>:
         service:
           ports:
             nodePort: