From d55906f8dd4ded0b26aaa1c7f90b836e6eed53d0 Mon Sep 17 00:00:00 2001 From: lemon-tree Date: Tue, 15 Aug 2017 12:21:45 +0800 Subject: [PATCH] Update accessing-the-api.md Modified the "root certificates" to "root certificate". --- docs/admin/accessing-the-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/accessing-the-api.md b/docs/admin/accessing-the-api.md index d181fe8b43..03447f2488 100644 --- a/docs/admin/accessing-the-api.md +++ b/docs/admin/accessing-the-api.md @@ -21,7 +21,7 @@ In a typical Kubernetes cluster, the API serves on port 443. The API server presents a certificate. This certificate is often self-signed, so `$USER/.kube/config` on the user's machine typically contains the root certificate for the API server's certificate, which when specified -is used in place of the system default root certificates. This certificate is typically +is used in place of the system default root certificate. This certificate is typically automatically written into your `$USER/.kube/config` when you create a cluster yourself using `kube-up.sh`. If the cluster has multiple users, then the creator needs to share the certificate with other users.