From 28d225e2311858903565e8f3563d8e614b317ada Mon Sep 17 00:00:00 2001 From: Austin Date: Wed, 5 Jun 2019 19:50:11 -0500 Subject: [PATCH] Fix a small typo (#14743) --- content/en/docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 5dac96ec48..dcc3e9b992 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -410,7 +410,7 @@ create a DNS record for `"my-service.my-ns"`. Pods in the `"my-ns"` Namespace should be able to find it by simply doing a name lookup for `my-service` (`"my-service.my-ns"` would also work). -Pods n other Namespaces must qualify the name as `my-service.my-ns`. These names +Pods in other Namespaces must qualify the name as `my-service.my-ns`. These names will resolve to the cluster IP assigned for the Service. Kubernetes also supports DNS SRV (service) records for named ports. If the