diff --git a/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md b/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
index d576493dd30ad..73cecd999b5a6 100644
--- a/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
+++ b/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
@@ -215,8 +215,8 @@ etcd2 and etcd3 is as follows:
                       message `etcd2 is no longer a supported storage backend`
 
 Before upgrading a v1.12.x kube-apiserver using `--storage-backend=etcd2` to
-v1.13.x, etcd v2 data MUST by migrated to the v3 storage backend, and
-kube-apiserver invocations changed to use `--storage-backend=etcd3`.
+v1.13.x, etcd v2 data must be migrated to the v3 storage backend and
+kube-apiserver invocations must be changed to use `--storage-backend=etcd3`.
 
 The process for migrating from etcd2 to etcd3 is highly dependent on how the
 etcd cluster was deployed and configured, as well as how the Kubernetes
diff --git a/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md b/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
index 9c81f3b488d7d..e8ab24a52f38b 100644
--- a/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
+++ b/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
@@ -163,7 +163,7 @@ data:
 ```
 
 The ConfigMap is created in the `kube-system` namespace because this
-ConfigMap configures a Kubelet, which is Kubernetes system component.
+ConfigMap configures a Kubelet, which is a Kubernetes system component.
 
 The `--append-hash` option appends a short checksum of the ConfigMap contents
 to the name. This is convenient for an edit-then-push workflow, because it