Merge pull request #48822 from pwright/patch-2

remove confusing sentence about containers in same pod behaving as if…

Author: jab-rh

networking/understanding-networking.adoc

@@ -11,7 +11,7 @@ Cluster Administrators have several options for exposing applications that run i
 
 * API resources, such as `Ingress` and `Route`
 
-By default, Kubernetes allocates each pod an internal IP address for applications running within the pod. Pods and their containers can network, but clients outside the cluster do not have networking access. This ensures all containers within the pod behave as if they were on the same host. When you expose your application to external traffic, giving each pod its own IP address means that pods can be treated like physical hosts or virtual machines in terms of port allocation, networking, naming, service discovery, load balancing, application configuration, and migration.
+By default, Kubernetes allocates each pod an internal IP address for applications running within the pod. Pods and their containers can network, but clients outside the cluster do not have networking access. When you expose your application to external traffic, giving each pod its own IP address means that pods can be treated like physical hosts or virtual machines in terms of port allocation, networking, naming, service discovery, load balancing, application configuration, and migration.
 
 [NOTE]
 ====