From 703336cacd0d0cbf8061d86252b59b2a670e4e2c Mon Sep 17 00:00:00 2001 From: Daniel Bastos Date: Tue, 20 Nov 2018 01:34:24 -0200 Subject: [PATCH] Improve overall sentence clearness and understanding (#11102) --- content/en/docs/concepts/services-networking/service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 7b747a6a79..02aa47ff5d 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -324,8 +324,8 @@ DNS server watches the Kubernetes API for new `Services` and creates a set of DNS records for each. If DNS has been enabled throughout the cluster then all `Pods` should be able to do name resolution of `Services` automatically. -For example, if you have a `Service` called `"my-service"` in Kubernetes -`Namespace` `"my-ns"` a DNS record for `"my-service.my-ns"` is created. `Pods` +For example, if you have a `Service` called `"my-service"` in a Kubernetes +`Namespace` called `"my-ns"`, a DNS record for `"my-service.my-ns"` is created. `Pods` which exist in the `"my-ns"` `Namespace` should be able to find it by simply doing a name lookup for `"my-service"`. `Pods` which exist in other `Namespaces` must qualify the name as `"my-service.my-ns"`. The result of these name lookups is the