diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md
index 3f590016c0a..1900e7e1a4a 100644
--- a/docs/admin/multiple-zones.md
+++ b/docs/admin/multiple-zones.md
@@ -43,7 +43,7 @@ placement, and so if the zones in your cluster are heterogeneous
 (e.g. different numbers of nodes, different types of nodes, or
 different pod resource requirements), this might prevent perfectly
 even spreading of your pods across zones. If desired, you can use
-homogenous zones (same number and types of nodes) to reduce the
+homogeneous zones (same number and types of nodes) to reduce the
 probability of unequal spreading.
 
 When persistent volumes are created, the `PersistentVolumeLabel`
diff --git a/docs/concepts/architecture/cloud-controller.md b/docs/concepts/architecture/cloud-controller.md
index 12d5e13c534..7d482e9d208 100644
--- a/docs/concepts/architecture/cloud-controller.md
+++ b/docs/concepts/architecture/cloud-controller.md
@@ -97,7 +97,7 @@ The Node controller contains the cloud-dependent functionality of the kubelet. P
 
 In this new model, the kubelet initializes a node without cloud-specific information. However, it adds a taint to the newly created node that makes the node unschedulable until the CCM initializes the node with cloud-specific information, and then removes this taint. 
 
-### 3. Kubernets API server
+### 3. Kubernetes API server
 
 The PersistentVolumeLabels controller moves the cloud-dependent functionality of the Kubernetes API server to the CCM as described in the preceding sections.
 
diff --git a/docs/concepts/cluster-administration/controller-metrics.md b/docs/concepts/cluster-administration/controller-metrics.md
index ceca94f7de2..2f1c71e34a0 100644
--- a/docs/concepts/cluster-administration/controller-metrics.md
+++ b/docs/concepts/cluster-administration/controller-metrics.md
@@ -13,10 +13,10 @@ the controller manager.
 
 Controller manager metrics provide important insight into the performance and health of the controller manager.
 These metrics include common Go language runtime metrics such as go_routine count and controller specific metrics such as
-etcd request latencies or Cloudprovider (AWS, GCE, Openstack) API latencies that can be used
+etcd request latencies or Cloudprovider (AWS, GCE, OpenStack) API latencies that can be used
 to gauge the health of a cluster.
 
-Starting from Kubernetes 1.7, detailed Cloudprovider metrics are available for storage operations for GCE, AWS, Vsphere and Openstack.
+Starting from Kubernetes 1.7, detailed Cloudprovider metrics are available for storage operations for GCE, AWS, Vsphere and OpenStack.
 These metrics can be used to monitor health of persistent volume operations.
 
 For example, for GCE these metrics are called:
diff --git a/docs/concepts/cluster-administration/device-plugins.md b/docs/concepts/cluster-administration/device-plugins.md
index 635c8232b29..2078adcf0fe 100644
--- a/docs/concepts/cluster-administration/device-plugins.md
+++ b/docs/concepts/cluster-administration/device-plugins.md
@@ -65,7 +65,7 @@ The general workflow of a device plugin includes the following steps:
   ```gRPC
   service DevicePlugin {
         // ListAndWatch returns a stream of List of Devices
-        // Whenever a Device state change or a Device disapears, ListAndWatch
+        // Whenever a Device state change or a Device disappears, ListAndWatch
         // returns the new list
         rpc ListAndWatch(Empty) returns (stream ListAndWatchResponse) {}
 
diff --git a/docs/concepts/configuration/manage-compute-resources-container.md b/docs/concepts/configuration/manage-compute-resources-container.md
index 8508f6642aa..ee49bdf94c1 100644
--- a/docs/concepts/configuration/manage-compute-resources-container.md
+++ b/docs/concepts/configuration/manage-compute-resources-container.md
@@ -312,7 +312,7 @@ Kubernetes version 1.8 introduces a new resource, _ephemeral-storage_ for managi
 
 This partition is “ephemeral” and applications cannot expect any performance SLAs (Disk IOPS for example) from this partition. Local ephemeral storage management only applies for the root partition; the optional partition for image layer and writable layer is out of scope.
 
-**Note:** If an optional runntime partition is used, root partition will not hold any image layer or writable layers.
+**Note:** If an optional runtime partition is used, root partition will not hold any image layer or writable layers.
 {: .note}
 
 ### Requests and limits setting for local ephemeral storage