From ca226243a53f10e20c0281d8b12d69922ec91029 Mon Sep 17 00:00:00 2001
From: Glusk <8526099+Glusk@users.noreply.github.com>
Date: Sat, 22 Oct 2022 18:03:41 +0200
Subject: [PATCH] typo fix

---
 .../docs/concepts/services-networking/service-traffic-policy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/services-networking/service-traffic-policy.md b/content/en/docs/concepts/services-networking/service-traffic-policy.md
index a7f5d1c2384..ccf003b5386 100644
--- a/content/en/docs/concepts/services-networking/service-traffic-policy.md
+++ b/content/en/docs/concepts/services-networking/service-traffic-policy.md
@@ -6,7 +6,7 @@ content_type: concept
 weight: 75
 description: >-
   If two Pods in your cluster want to communicate, and both Pods are actually running on
-  the same node, _Service Internal Traffic Policy_ to keep network traffic within that node.
+  the same node, use _Service Internal Traffic Policy_ to keep network traffic within that node.
   Avoiding a round trip via the cluster network can help with reliability, performance
   (network latency and throughput), or cost.
 ---