Merge pull request #92754 from JoeAldinger/OCPBUGS-55471

OCPBUGS-55471:fixes OVN-K external IP docs

Author: JoeAldinger

modules/nw-networkpolicy-optimize-ovn.adoc

@@ -104,11 +104,11 @@ spec:
 You can apply this optimization when only multiple selectors are expressed as one. In cases where selectors are based on different labels, it may not be possible to apply this optimization. In those cases, consider applying some new labels for network policy optimization specifically.
 
 [id="nw-networkpolicy-external-ip-ovn_{context}"]
-== NetworkPolicies and external IPs in OVN-Kubernetes
+== NetworkPolicy CR and external IPs in OVN-Kubernetes
 
-In OVN-Kubernetes, `NetworkPolicies` enforce strict isolation rules. If a service is exposed using an external IP, `NetworkPolicies` can block access from other namespaces unless explicitly configured.
+In OVN-Kubernetes, the `NetworkPolicy` custom resource (CR) enforces strict isolation rules. If a service is exposed using an external IP, a network policy can block access from other namespaces unless explicitly configured to allow traffic.
 
-To allow access to external IPs across namespaces, create a `NetworkPolicy` that explicitly permits ingress from the required namespaces and ensures traffic is allowed to the designated service ports. Without allowing traffic to the required ports, access might still be restricted.
+To allow access to external IPs across namespaces, create a `NetworkPolicy` CR that explicitly permits ingress from the required namespaces and ensures traffic is allowed to the designated service ports. Without allowing traffic to the required ports, access might still be restricted.
 
 .Example output
 [source,yaml]
@@ -117,7 +117,7 @@ To allow access to external IPs across namespaces, create a `NetworkPolicy` that
   kind: NetworkPolicy
   metadata:
     annotations:
-    name: <policy_name> <1>
+    name: <policy_name>
     namespace: openshift-ingress
   spec:
     ingress:
@@ -130,12 +130,14 @@ To allow access to external IPs across namespaces, create a `NetworkPolicy` that
     - from:
       - namespaceSelector:
           matchLabels:
-          kubernetes.io/metadata.name: <namespace_name> <2>
+          kubernetes.io/metadata.name: <my_namespace>
     podSelector: {}
     policyTypes:
     - Ingress
 ----
-<1> Specify the policy name. 
-<2> Specify the namespace name. 
++
+Where::
+`<policy_name>`: Specifies your name for the policy.
+`<my_namespace>`: Specifies the name of the namespace where the policy is deployed.
 
 For more details, see "About network policy".

networking/understanding-networking.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Understanding the fundamentals of networking in {product-title} ensures efficient and secure communication within your clusters and is essential for effective network administration. Key elements of networking in your environment include understanding how pods and services communicate, the role of IP addresses, and the use of DNS for service discovery. 
+Understanding the fundamentals of networking in {product-title} ensures efficient and secure communication within your clusters and is essential for effective network administration. Key elements of networking in your environment include understanding how pods and services communicate, the role of IP addresses, and the use of DNS for service discovery.
 
 // Introduction
 include::modules/nw-understanding-networking-networking-in-OpenShift.adoc[leveloffset=+1]
@@ -27,8 +27,6 @@ include::modules/nw-understanding-networking-what-is-a-client.adoc[leveloffset=+
 // Concepts and components
 include::modules/nw-understanding-networking-concepts-components.adoc[leveloffset=+1]
 
-include::modules/nw-ne-changes-externalip-ovn.adoc[leveloffset=+1]
-
 [role="_additional-resources"]
 .Additional resources