diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md
index 69a1f1ccab..8f4a3db26c 100644
--- a/docs/getting-started-guides/kubeadm.md
+++ b/docs/getting-started-guides/kubeadm.md
@@ -101,7 +101,7 @@ Note: `setenforce 0` will no longer be necessary on CentOS once [#33555](https:/
 The master is the machine where the "control plane" components run, including `etcd` (the cluster database) and the API server (which the `kubectl` CLI communicates with).
 All of these components run in pods started by `kubelet`.
 
-Right now you can't run `kubeadm init` twice without turning down the cluster in between, see [Turndown](#turndown).
+Right now you can't run `kubeadm init` twice without tearing down the cluster in between, see [Tear down](#tear-down).
 
 To initialize the master, pick one of the machines you previously installed `kubelet` and `kubeadm` on, and run: