Remove excess Spaces (#11106)

content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md

@@ -356,7 +356,7 @@ The complete Corefile with the default plugins:
 .:53 {
         errors
         health
-        kubernetes cluster.local  in-addr.arpa ip6.arpa {
+        kubernetes cluster.local in-addr.arpa ip6.arpa {
            upstream  8.8.8.8 8.8.4.4
            pods insecure
            fallthrough in-addr.arpa ip6.arpa

content/en/docs/tasks/administer-cluster/extended-resource-node.md

@@ -112,7 +112,7 @@ number of dongles. See
 ## Discussion
 
 Extended resources are similar to memory and CPU resources. For example,
-just as  a Node has a certain amount of memory and CPU to be shared by all components
+just as a Node has a certain amount of memory and CPU to be shared by all components
 running on the Node, it can have a certain number of dongles to be shared
 by all components running on the Node. And just as application developers
 can create Pods that request a certain amount of memory and CPU, they can

content/en/docs/tasks/administer-cluster/network-policy-provider/romana-network-policy.md

@@ -14,7 +14,7 @@ This page shows how to use Romana for NetworkPolicy.
 
 {{% capture prerequisites %}}
 
-Complete steps 1, 2, and 3 of  the [kubeadm getting started guide](/docs/getting-started-guides/kubeadm/).
+Complete steps 1, 2, and 3 of the [kubeadm getting started guide](/docs/getting-started-guides/kubeadm/).
 
 {{% /capture %}}
 

content/en/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md

@@ -118,7 +118,7 @@ View the files in the `/etc/podinfo` directory:
 In the output, you can see that the `labels` and `annotations` files
 are in a temporary subdirectory: in this example,
 `..2982_06_02_21_47_53.299460680`. In the `/etc/podinfo` directory, `..data` is
-a symbolic link to the temporary subdirectory. Also in  the `/etc/podinfo` directory,
+a symbolic link to the temporary subdirectory. Also in the `/etc/podinfo` directory,
 `labels` and `annotations` are symbolic links.
 
 ```

content/en/docs/tutorials/stateful-application/zookeeper.md

@@ -103,7 +103,7 @@ StatefulSet controller create the StatefulSet's Pods.
 kubectl get pods -w -l app=zk
 ```
 
-Once the `zk-2` Pod is Running and Ready, use `CTRL-C` to  terminate kubectl.
+Once the `zk-2` Pod is Running and Ready, use `CTRL-C` to terminate kubectl.
 
 ```shell
 NAME      READY     STATUS    RESTARTS   AGE

content/en/docs/user-journeys/users/application-developer/intermediate.md

@@ -141,7 +141,7 @@ For the full list of kubectl commands and their options, check out {{< link text
 
 To leverage pre-packaged configurations from the community, you can use **{{< glossary_tooltip text="Helm charts" term_id="helm-chart" >}}**.
 
-Helm charts package up YAML configurations for specific apps like Jenkins and Postgres. You can then  install and run these apps on your cluster with minimal extra configuration. This approach makes the most sense for "off-the-shelf" components which do not require much custom implementation logic.
+Helm charts package up YAML configurations for specific apps like Jenkins and Postgres. You can then install and run these apps on your cluster with minimal extra configuration. This approach makes the most sense for "off-the-shelf" components which do not require much custom implementation logic.
 
 For writing your own Kubernetes app configurations, there is a {{< link text="thriving ecosystem of tools" url="https://docs.google.com/a/heptio.com/spreadsheets/d/1FCgqz1Ci7_VCz_wdh8vBitZ3giBtac_H8SBw4uxnrsE/edit?usp=drive_web" >}} that you may find useful.