From 8face3d0085c8dd9a5eb02c644464d6be9fb3a88 Mon Sep 17 00:00:00 2001
From: Alex Serbul <22218473+AlexanderSerbul@users.noreply.github.com>
Date: Wed, 19 Jul 2023 13:16:49 +0300
Subject: [PATCH] Update connect-applications-service.md

We are talking about pods here, not about services yet.
---
 .../en/docs/tutorials/services/connect-applications-service.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tutorials/services/connect-applications-service.md b/content/en/docs/tutorials/services/connect-applications-service.md
index 7425fa119b..24245584fa 100644
--- a/content/en/docs/tutorials/services/connect-applications-service.md
+++ b/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.