diff --git a/docs/concepts/overview/working-with-objects/namespaces.md b/docs/concepts/overview/working-with-objects/namespaces.md
index 0f66878964..aa06eff515 100644
--- a/docs/concepts/overview/working-with-objects/namespaces.md
+++ b/docs/concepts/overview/working-with-objects/namespaces.md
@@ -30,7 +30,7 @@ resources within the same namespace.
 ## Working with Namespaces
 
 Creation and deletion of namespaces is described in the [Admin Guide documentation
-for namespaces](/docs/admin/namespaces)
+for namespaces](/docs/admin/namespaces).
 
 ### Viewing namespaces
 
@@ -74,7 +74,7 @@ $ kubectl config view | grep namespace:
 
 When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns).
 This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
-that if a container just uses `<service-name>` it will resolve to the service which
+that if a container just uses `<service-name>`, it will resolve to the service which
 is local to a namespace.  This is useful for using the same configuration across
 multiple namespaces such as Development, Staging and Production.  If you want to reach
 across namespaces, you need to use the fully qualified domain name (FQDN).