diff --git a/content/en/docs/reference/command-line-tools-reference/kubelet.md b/content/en/docs/reference/command-line-tools-reference/kubelet.md
index 6a5c6a4a02..1026c4fc48 100644
--- a/content/en/docs/reference/command-line-tools-reference/kubelet.md
+++ b/content/en/docs/reference/command-line-tools-reference/kubelet.md
@@ -274,7 +274,7 @@ kubelet
       <td colspan="2">--enforce-node-allocatable stringSlice&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: [pods]</td>
     </tr>
     <tr>
-      <td></td><td style="line-height: 130%">A comma separated list of levels of node allocatable enforcement to be enforced by kubelet. Acceptible options are 'pods', 'system-reserved' & 'kube-reserved'. If the latter two options are specified, '--system-reserved-cgroup' & '--kube-reserved-cgroup' must also be set respectively. See https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ for more details.</td>
+      <td></td><td style="line-height: 130%">A comma separated list of levels of node allocatable enforcement to be enforced by kubelet. Acceptable options are 'pods', 'system-reserved' & 'kube-reserved'. If the latter two options are specified, '--system-reserved-cgroup' & '--kube-reserved-cgroup' must also be set respectively. See https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ for more details.</td>
     </tr>
     <tr>
       <td colspan="2">--event-burst int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 10</td>
@@ -352,7 +352,7 @@ kubelet
       <td colspan="2">--experimental-check-node-capabilities-before-mount</td>
     </tr>
     <tr>
-      <td></td><td style="line-height: 130%">[Experimental] if set true, the kubelet will check the underlying node for required componenets (binaries, etc.) before performing the mount</td>
+      <td></td><td style="line-height: 130%">[Experimental] if set true, the kubelet will check the underlying node for required components (binaries, etc.) before performing the mount</td>
     </tr>
     <tr>
       <td colspan="2">--experimental-kernel-memcg-notification</td>
diff --git a/content/en/docs/tasks/administer-cluster/setup-ha-etcd-with-kubeadm.md b/content/en/docs/tasks/administer-cluster/setup-ha-etcd-with-kubeadm.md
index 9bc4d95059..3bee8f2932 100644
--- a/content/en/docs/tasks/administer-cluster/setup-ha-etcd-with-kubeadm.md
+++ b/content/en/docs/tasks/administer-cluster/setup-ha-etcd-with-kubeadm.md
@@ -1,7 +1,7 @@
 ---
 reviewers:
 - chuckha
-title: Set up a High-Availablity Etcd Cluster With Kubeadm
+title: Set up a High-Availability Etcd Cluster With Kubeadm
 content_template: templates/task
 ---
 
diff --git a/content/en/docs/tasks/federation/set-up-cluster-federation-kubefed.md b/content/en/docs/tasks/federation/set-up-cluster-federation-kubefed.md
index a9f7553b30..14584b7ef8 100644
--- a/content/en/docs/tasks/federation/set-up-cluster-federation-kubefed.md
+++ b/content/en/docs/tasks/federation/set-up-cluster-federation-kubefed.md
@@ -379,7 +379,7 @@ For more information see
 
 It is possible to utilize AWS Route53 as a cloud DNS provider when the
 federation controller-manager is run on-premise. The controller-manager
-Deployment must be configured with AWS credentials since it cannot implicity
+Deployment must be configured with AWS credentials since it cannot implicitly
 gather them from a VM running on AWS.
 
 Currently, `kubefed init` does not read AWS Route53 credentials from the