Fix some spell checking

Signed-off-by: Ricardo Pchevuzinske Katz <ricardo.katz@gmail.com>

content/en/docs/reference/using-api/api-concepts.md

@@ -514,7 +514,7 @@ The meaning of the get and list semantics are:
 - **Any:** Return data at any resource version. The newest available resource version is preferred,
   but strong consistency is not required; data at any resource version may be served. It is possible
   for the request to return data at a much older resource version that the client has previously
-  observed, particularly in high availabiliy configurations, due to partitions or stale
+  observed, particularly in high availability configurations, due to partitions or stale
   caches. Clients that cannot tolerate this should not use this semantic.
 - **Not older than:** Return data at least as new as the provided resourceVersion. The newest
   available data is preferred, but any data not older than the provided resourceVersion may be

content/en/docs/setup/best-practices/multiple-zones.md

@@ -29,7 +29,7 @@ one zone also impairs services in another zone.
 ## Control plane behavior
 
 All [control plane components](/docs/concepts/overview/components/#control-plane-components)
-support running as a pool of interchangable resources, replicated per
+support running as a pool of interchangeable resources, replicated per
 component.
 
 When you deploy a cluster control plane, place replicas of

content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md

@@ -273,7 +273,7 @@ The behavior of the flags behave differently as described below:
 * MemoryPressure Condition is not implemented
 * There are no OOM eviction actions taken by the kubelet
 * Kubelet running on the windows node does not have memory restrictions. `--kubelet-reserve` and `--system-reserve` do not set limits on kubelet or processes running on the host. This means kubelet or a process on the host could cause memory resource starvation outside the node-allocatable and scheduler
-* An additional flag to set the priority of the kubelet process is availabe on the Windows nodes called `--windows-priorityclass`. This flag allows kubelet process to get more CPU time slices when compared to other processes running on the Windows host. More information on the allowable values and their meaning is available at [Windows Priority Classes](https://docs.microsoft.com/en-us/windows/win32/procthread/scheduling-priorities#priority-class). In order for kubelet to always have enough CPU cycles it is recommended to set this flag to `ABOVE_NORMAL_PRIORITY_CLASS` and above
+* An additional flag to set the priority of the kubelet process is available on the Windows nodes called `--windows-priorityclass`. This flag allows kubelet process to get more CPU time slices when compared to other processes running on the Windows host. More information on the allowable values and their meaning is available at [Windows Priority Classes](https://docs.microsoft.com/en-us/windows/win32/procthread/scheduling-priorities#priority-class). In order for kubelet to always have enough CPU cycles it is recommended to set this flag to `ABOVE_NORMAL_PRIORITY_CLASS` and above
 
 #### Storage
 
@@ -634,7 +634,7 @@ We have a lot of features in our roadmap. An abbreviated high level list is incl
 
 ### Hyper-V isolation
 
-Hyper-V isolation is requried to enable the following use cases for Windows containers in Kubernetes:
+Hyper-V isolation is required to enable the following use cases for Windows containers in Kubernetes:
 
 * Hypervisor-based isolation between pods for additional security
 * Backwards compatibility allowing a node to run a newer Windows Server version without requiring containers to be rebuilt

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

@@ -255,7 +255,7 @@ To migrate from kube-dns to CoreDNS, a detailed
 [blog article](https://coredns.io/2018/05/21/migration-from-kube-dns-to-coredns/)
 is available to help users adapt CoreDNS in place of kube-dns.
 
-You can also migrate using the offical CoreDNS
+You can also migrate using the official CoreDNS
 [deploy script](https://github.com/coredns/deployment/blob/master/kubernetes/deploy.sh).
 
 

content/en/docs/tasks/administer-cluster/topology-manager.md

@@ -24,7 +24,7 @@ _Topology Manager_ is a Kubelet component that aims to co-ordinate the set of co
  
 
 
-## {{% heading "prerequisites" %}}
+## {{% heading "prerequisites" %}}
 
 
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
@@ -192,7 +192,7 @@ spec:
 
 This pod runs in the `Burstable` QoS class because requests are less than limits.
 
-If the selected policy is anything other than `none`, Topology Manager would consider these Pod specifications. The Topology Manager would consult the Hint Providers to get topology hints. In the case of the `static`, the CPU Manager policy would return default topology hint, because these Pods do not have explicity request CPU resources.
+If the selected policy is anything other than `none`, Topology Manager would consider these Pod specifications. The Topology Manager would consult the Hint Providers to get topology hints. In the case of the `static`, the CPU Manager policy would return default topology hint, because these Pods do not have explicitly request CPU resources.
 
 
 ```yaml

content/en/docs/tasks/configure-pod-container/configure-gmsa.md

@@ -254,4 +254,4 @@ If the above command corrects the error, you can automate the step by adding the
 If you add the `lifecycle` section show above to your Pod spec, the Pod will execute the commands listed to restart the `netlogon` service until the `nltest.exe /query` command exits without error.
 
 ## GMSA limitations
-When using the [ContainerD runtime for Windows](/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#cri-containerd) accessing restricted network shares via the GMSA domain identity fails. The container will recieve the identity of and calls from `nltest.exe /query` will work.  It is recommended to use the [Docker EE runtime](/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#docker-ee) if access to network shares is required.  The Windows Server team is working on resolving the issue in the Windows Kernel and will release a patch to resolve this issue in the future. Look for updates on the [Microsoft Windows Containers issue tracker](https://github.com/microsoft/Windows-Containers/issues/44).
+When using the [ContainerD runtime for Windows](/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#cri-containerd) accessing restricted network shares via the GMSA domain identity fails. The container will receive the identity of and calls from `nltest.exe /query` will work.  It is recommended to use the [Docker EE runtime](/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#docker-ee) if access to network shares is required.  The Windows Server team is working on resolving the issue in the Windows Kernel and will release a patch to resolve this issue in the future. Look for updates on the [Microsoft Windows Containers issue tracker](https://github.com/microsoft/Windows-Containers/issues/44).