From 3bf7d6658afa39ed354acda6a1ee752b295aecaf Mon Sep 17 00:00:00 2001 From: Richard Shaw Date: Tue, 14 Mar 2017 16:34:43 +0000 Subject: [PATCH] Update kubeadm.md A couple of minor grammatical errors. --- docs/getting-started-guides/kubeadm.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index b8c72cadee..20f89817b4 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -216,14 +216,14 @@ To help diagnose what happened, you can use the following command to check what kubectl describe -n kube-system po {YOUR_POD_NAME} ``` -Do not using kubectl logs. You will got the following error: +Do not use kubectl logs. You will get the following error: ``` # kubectl logs -n kube-system canal-node-f0lqp Error from server (BadRequest): the server rejected our request for an unknown reason (get pods canal-node-f0lqp) ``` -The ```kubectl describe``` comand gives you more details about the logs +The ```kubectl describe``` command gives you more details about the logs ``` # kubectl describe -n kube-system po kube-dns-2924299975-1l2t7 @@ -236,7 +236,7 @@ Or 6m 1m 191 {kubelet nac} Warning FailedSync Error syncing pod, skipping: failed to "SetupNetwork" for "kube-dns-2924299975-1l2t7_kube-system" with SetupNetworkError: "Failed to setup network for pod \"kube-dns-2924299975-1l2t7_kube-system(dee8ef21-fbcb-11e6-ba19-38d547e0006a)\" using network plugins \"cni\": open /run/flannel/subnet.env: no such file or directory; Skipping pod" ``` -You can then do some Google searches on the error messages, which may help you to find some solutions. +You can then search Google for the error messages, which may help you find a solution. ### (4/4) Joining your nodes