Merge pull request #7077 from StefanEnberg/patch-1

Typo fix

docs/concepts/services-networking/dns-pod-service.md

@@ -158,7 +158,7 @@ following pod-specific DNS policies. These policies are specified in the
   for more details.
 - "`ClusterFirst`": Any DNS query that does not match the configured cluster
   domain suffix, such as "`www.kubernetes.io`", is forwarded to the upstream
-  nameserver inherited from the node. Cluster aministrators may have extra
+  nameserver inherited from the node. Cluster administrators may have extra
   stub-domain and upstream DNS servers configured.
   See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#impacts-on-pods)
   for details on how DNS queries are handled in those cases.
@@ -199,7 +199,7 @@ spec:
 ### Pod's DNS Config
 
 Kubernetes v1.9 introduces an Alpha feature that allows users more control on
-the DNS settings for a Pod. To enable this feature, the cluster aministrator
+the DNS settings for a Pod. To enable this feature, the cluster administrator
 needs to enable the `CustomPodDNS` feature gate on the apiserver and the kubelet,
 for example, "`--feature-gates=CustomPodDNS=true,...`".
 When the feature gate is enabled, users can set the `dnsPolicy` field of a Pod