Merge pull request #44539 from cowgirljessi/BZ2072784_Take2

BZ 2072784 updated text to match graphic

Author: ahardin-rh

modules/nw-ingress-controller-endpoint-publishing-strategies.adoc

@@ -17,7 +17,7 @@ image::202_OpenShift_Ingress_0222_node_port.png[{product-title} Ingress NodePort
 The preceding graphic shows the following concepts pertaining to {product-title} Ingress NodePort endpoint publishing strategy:
 
 * All the available nodes in the cluster have their own, externally accessible IP addresses. The service running in the cluster is bound to the unique NodePort for all the nodes.
-* When the client connects to a node that is down, for example, by way of the `193.10.0.10` IP address in the graphic, the node port directly connects the client to an available node that is running the service. In this scenario, no load balancing is required. As the image shows, `193.10.0.10` is down and another IP address must be used instead.
+* When the client connects to a node that is down, for example, by connecting the `10.0.128.4` IP address in the graphic, the node port directly connects the client to an available node that is running the service. In this scenario, no load balancing is required. As the image shows, the `10.0.128.4` address is down and another IP address must be used instead.
 
 [NOTE]
 ====