fix several misspelling (#10126)

content/en/docs/contribute/style/write-new-topic.md

@@ -79,7 +79,7 @@ subdirectory.
 
 ## Placing your topic in the table of contents
 
-The table of contents is built dynamicaly using the directory structure of the
+The table of contents is built dynamically using the directory structure of the
 documentation source. The top-level directories under `/content/en/docs/` create
 top-level navigation, and subdirectories each have entries in the table of
 contents.

content/en/docs/setup/certificates.md

@@ -45,7 +45,7 @@ If you don't want kubeadm to generate the required certificates, you can create
 
 ### Single root CA
 
-You can create a single root CA, controlled by an adminstrator. This root CA can then create multiple intermediate CAs, and delegate all further creation to Kubernetes itself. 
+You can create a single root CA, controlled by an administrator. This root CA can then create multiple intermediate CAs, and delegate all further creation to Kubernetes itself. 
 
 Required CAs:
 
@@ -136,4 +136,4 @@ These files are used as follows:
 [kubeadm]: /docs/reference/setup-tools/kubeadm/kubeadm/
 [proxy]: /docs/tasks/access-kubernetes-api/configure-aggregation-layer/
 
-{{% /capture %}}
+{{% /capture %}}

content/en/docs/setup/independent/kubelet-integration.md

@@ -110,7 +110,7 @@ initializing. A kubelet configuration file is also written to `/etc/kubernetes/k
 baseline cluster-wide configuration for all kubelets in the cluster. This configuration file
 points to the client certificates that allow the kubelet to communicate with the API server. This
 addresses the need to
-[propogate cluster-level configuration to each kubelet](#propagating-cluster-level-configuration-to-each-kubelet).
+[propagate cluster-level configuration to each kubelet](#propagating-cluster-level-configuration-to-each-kubelet).
 
 To address the second pattern of
 [providing instance-specific configuration details](#providing-instance-specific-configuration-details),