whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix several misspelling (#10126)

Browse Source
This commit is contained in:
CaoShuFeng
2018-08-30 01:26:33 +08:00
committed by k8s-ci-robot
parent d79087cb91
commit a936d465fb
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/certificates.md
+2 -2
View File
@@ -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
+1 -1
View File
@@ -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),