Merge pull request #42085 from AlexanderSerbul/patch-1

Update connect-applications-service.md

Author: k8s-ci-robot

content/en/docs/tutorials/services/connect-applications-service.md

@@ -59,7 +59,7 @@ to make queries against both IPs. Note that the containers are *not* using port
 the node, nor are there any special NAT rules to route traffic to the pod. This means
 you can run multiple nginx pods on the same node all using the same `containerPort`,
 and access them from any other pod or node in your cluster using the assigned IP
-address for the Service. If you want to arrange for a specific port on the host
+address for the pod. If you want to arrange for a specific port on the host
 Node to be forwarded to backing Pods, you can - but the networking model should
 mean that you do not need to do so.
 
@@ -189,7 +189,7 @@ Note there's no mention of your Service. This is because you created the replica
 before the Service. Another disadvantage of doing this is that the scheduler might
 put both Pods on the same machine, which will take your entire Service down if
 it dies. We can do this the right way by killing the 2 Pods and waiting for the
-Deployment to recreate them. This time around the Service exists *before* the
+Deployment to recreate them. This time the Service exists *before* the
 replicas. This will give you scheduler-level Service spreading of your Pods
 (provided all your nodes have equal capacity), as well as the right environment
 variables: