Fix minor typos and misspells detected using misspell (#7313)

docs/admin/admission-controllers.md

@@ -354,7 +354,7 @@ webhooks are called in serial; each one may modify the object if it desires.
 This admission controller (as implied by the name) only runs in the mutating phase.
 
 If a webhook called by this has side effects (for example, decrementing quota) it
-*must* have a reconcilation system, as it is not guaranteed that subsequent
+*must* have a reconciliation system, as it is not guaranteed that subsequent
 webhooks or validating admission controllers will permit the request to finish.
 
 If you disable the MutatingAdmissionWebhook, you must also disable the
@@ -565,7 +565,7 @@ fails. This admission controller only runs in the validation phase; the webhooks
 mutate the object, as opposed to the webhooks called by the `MutatingAdmissionWebhook` admission controller.
 
 If a webhook called by this has side effects (for example, decrementing quota) it
-*must* have a reconcilation system, as it is not guaranteed that subsequent
+*must* have a reconciliation system, as it is not guaranteed that subsequent
 webhooks or other validating admission controllers will permit the request to finish.
 
 If you disable the ValidatingAdmissionWebhook, you must also disable the

docs/concepts/cluster-administration/networking.md

@@ -243,7 +243,7 @@ to run, and in both cases, the network provides one IP address per pod - as is s
 
 ### CNI-Genie from Huawei
 
-[CNI-Genie](https://github.com/Huawei-PaaS/CNI-Genie) is a CNI plugin that enables Kubernetes to [simultanously have access to different implementations](https://github.com/Huawei-PaaS/CNI-Genie/blob/master/docs/multiple-cni-plugins/README.md#what-cni-genie-feature-1-multiple-cni-plugins-enables) of the [Kubernetes network model](https://git.k8s.io/website/docs/concepts/cluster-administration/networking.md#kubernetes-model) in runtime. This includes any implementation that runs as a [CNI plugin](https://github.com/containernetworking/cni#3rd-party-plugins), such as [Flannel](https://github.com/coreos/flannel#flannel), [Calico](http://docs.projectcalico.org/), [Romana](http://romana.io), [Weave-net](https://www.weave.works/products/weave-net/).
+[CNI-Genie](https://github.com/Huawei-PaaS/CNI-Genie) is a CNI plugin that enables Kubernetes to [simultaneously have access to different implementations](https://github.com/Huawei-PaaS/CNI-Genie/blob/master/docs/multiple-cni-plugins/README.md#what-cni-genie-feature-1-multiple-cni-plugins-enables) of the [Kubernetes network model](https://git.k8s.io/website/docs/concepts/cluster-administration/networking.md#kubernetes-model) in runtime. This includes any implementation that runs as a [CNI plugin](https://github.com/containernetworking/cni#3rd-party-plugins), such as [Flannel](https://github.com/coreos/flannel#flannel), [Calico](http://docs.projectcalico.org/), [Romana](http://romana.io), [Weave-net](https://www.weave.works/products/weave-net/).
 
 CNI-Genie also supports [assigning multiple IP addresses to a pod](https://github.com/Huawei-PaaS/CNI-Genie/blob/master/docs/multiple-ips/README.md#feature-2-extension-cni-genie-multiple-ip-addresses-per-pod), each from a different CNI plugin.
 

docs/concepts/storage/persistent-volumes.md

@@ -536,7 +536,7 @@ spec:
 
 ### Binding Block Volumes
 
-If a user requests a raw block volume by indicating this using the `volumeMode` field in the `PersistentVolumeClaim` spec, the binding rules differ slighty from previous releases that didn't consider this mode as part of the spec.
+If a user requests a raw block volume by indicating this using the `volumeMode` field in the `PersistentVolumeClaim` spec, the binding rules differ slightly from previous releases that didn't consider this mode as part of the spec.
 Listed is a table of possible combinations the user and admin might specify for requesting a raw block device. The table indicates if the volume will be bound or not given the combinations:
 Volume binding matrix for statically provisioned volumes:
 

docs/reference/index.md

@@ -21,7 +21,7 @@ To call the Kubernetes API from a programming language, you can use
 client libraries:
 
 - [Kubernetes Go client library](https://github.com/kubernetes/client-go/)
-- [Kubernetes Python client libary](https://github.com/kubernetes-incubator/client-python)
+- [Kubernetes Python client library](https://github.com/kubernetes-incubator/client-python)
 
 ## CLI Reference
 

docs/reference/setup-tools/kubeadm/implementation-details.md

@@ -241,7 +241,7 @@ Other API server flags that are set unconditionally are:
     - [`ServiceAccount`](/docs/admin/admission-controllers/#serviceaccount) to enforce service account automation
     - [`PersistentVolumeLabel`](/docs/admin/admission-controllers/#persistentvolumelabel) attaches region or zone labels to
       PersistentVolumes as defined by the cloud provider (This admission controller is deprecated and will be removed in a future version. 
-      It is not deployed by kubeadm by default with v1.9 onwards when not explicitely opting into using `gce` or `aws` as cloud providers)
+      It is not deployed by kubeadm by default with v1.9 onwards when not explicitly opting into using `gce` or `aws` as cloud providers)
     - [`DefaultStorageClass`](/docs/admin/admission-controllers/#defaultstorageclass) to enforce default storage class on `PersistentVolumeClaim` objects
     - [`DefaultTolerationSeconds`](/docs/admin/admission-controllers/#defaulttolerationseconds) 
     - [`NodeRestriction`](/docs/admin/admission-controllers/#noderestriction) to limit what a kubelet can modify 

docs/tasks/administer-cluster/reconfigure-kubelet.md

@@ -333,7 +333,7 @@ condition's message reverts to either `using current (default)` or
 
 ### Deauthorize your Node fom reading the old ConfigMap
 
-Once you know your Node is using the default configuraiton again, it is a good
+Once you know your Node is using the default configuration again, it is a good
 idea to deauthorize the node from reading the old ConfigMap. Run the following
 commands to remove the RoleBinding and Role:
 

docs/tasks/administer-cluster/running-cloud-controller.md

@@ -25,7 +25,7 @@ Every cloud has their own set of requirements for running their own cloud provid
 
 * cloud authentication/authorization: your cloud may require a token or IAM rules to allow access to their APIs
 * kubernetes authentication/authorization: cloud-controller-manager may need RBAC rules set to speak to the kubernetes apiserver
-* high availabilty: like kube-controller-manager, you may want a high available setup for cloud controller manager using leader election (on by default).
+* high availability: like kube-controller-manager, you may want a high available setup for cloud controller manager using leader election (on by default).
 
 ### Running cloud-controller-manager
 

docs/tutorials/stateful-application/zookeeper.md

@@ -498,11 +498,11 @@ servers' WALs, and all of their snapshots, remain durable.
 ## Ensuring Consistent Configuration
 
 As noted in the [Facilitating Leader Election](#facilitating-leader-election) and
-[Achieving Consensus](#achieving-consensus) sections, the servers in a 
-ZooKeeper ensemble require consistent configuration in order to elect a leader 
+[Achieving Consensus](#achieving-consensus) sections, the servers in a
+ZooKeeper ensemble require consistent configuration in order to elect a leader
 and form a quorum. They also require consistent configuration of the Zab protocol
-in order for the protocol to work correctly over a network. In our example we 
-achive consistent configuration by embedding the configuration directly into 
+in order for the protocol to work correctly over a network. In our example we
+achieve consistent configuration by embedding the configuration directly into
 the manifest.
 
 Get the `zk` StatefulSet.