From 6ec9b2e7c2674d748f2742d6392adf95f2f9e9ba Mon Sep 17 00:00:00 2001 From: Tony Hsu Date: Thu, 15 Oct 2015 18:37:29 +0800 Subject: [PATCH] Fix typo --- docs/user-guide/accessing-the-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/accessing-the-cluster.md b/docs/user-guide/accessing-the-cluster.md index 83709c6bc96..c9a503c0005 100644 --- a/docs/user-guide/accessing-the-cluster.md +++ b/docs/user-guide/accessing-the-cluster.md @@ -135,7 +135,7 @@ The above example uses the `--insecure` flag. This leaves it subject to MITM attacks. When kubectl accesses the cluster it uses a stored root certificate and client certificates to access the server. (These are installed in the `~/.kube` directory). Since cluster certificates are typically self-signed, it -make take special configuration to get your http client to use root +may take special configuration to get your http client to use root certificate. On some clusters, the apiserver does not require authentication; it may serve