diff --git a/README.md b/README.md
index dfccae69af8b6f9a45d0db4b256585f1838e9d91..8b30f367a4c66b31ddb684348386c161e36175c0 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,7 @@ Note: When Ansible is already installed via system packages on the control node,
 Python packages installed via `sudo pip install -r requirements.txt` will go to
 a different directory tree (e.g. `/usr/local/lib/python2.7/dist-packages` on
 Ubuntu) from Ansible's (e.g. `/usr/lib/python2.7/dist-packages/ansible` still on
-buntu). As a consequence, the `ansible-playbook` command will fail with:
+Ubuntu). As a consequence, the `ansible-playbook` command will fail with:
 
 ```raw
 ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
diff --git a/docs/upgrades/migrate_docker2containerd.md b/docs/upgrades/migrate_docker2containerd.md
index df2e06c8a8e1ba4c14d85b530b129e7abb5c557b..b444db0a7f930e4c4bb539ced3e337a7e14f35ce 100644
--- a/docs/upgrades/migrate_docker2containerd.md
+++ b/docs/upgrades/migrate_docker2containerd.md
@@ -66,7 +66,7 @@ apt-get install pigz
 ### 5) Run `cluster.yml` playbook with `--limit`
 
 ```commandline
-ansible-playbook cluster.yml -i inventory/sample/hosts.ini cluster.yml --limit=NODENAME
+ansible-playbook -i inventory/sample/hosts.ini cluster.yml --limit=NODENAME
 ```
 
 This effectively reinstalls containerd and seems to place all config files in the right place. When this completes, kubelet will immediately pick up the new container engine and start spinning up DaemonSets and kube-system Pods.