From e119b41336a1d039b7a8654cea85058510f83134 Mon Sep 17 00:00:00 2001 From: yanghaichao12 Date: Mon, 8 Apr 2019 21:30:26 +0800 Subject: [PATCH] Fix typos (#13376) --- content/en/docs/setup/independent/troubleshooting-kubeadm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/setup/independent/troubleshooting-kubeadm.md b/content/en/docs/setup/independent/troubleshooting-kubeadm.md index 87ca0a3cb5..9bc6211b00 100644 --- a/content/en/docs/setup/independent/troubleshooting-kubeadm.md +++ b/content/en/docs/setup/independent/troubleshooting-kubeadm.md @@ -113,7 +113,7 @@ Right after `kubeadm init` there should not be any pods in these states. This is **expected** and part of the design. kubeadm is network provider-agnostic, so the admin should [install the pod network solution](/docs/concepts/cluster-administration/addons/) of choice. You have to install a Pod Network -before CoreDNS may deployed fully. Hence the `Pending` state before the network is set up. +before CoreDNS may be deployed fully. Hence the `Pending` state before the network is set up. ## `HostPort` services do not work