From bd17a0e81906a37374a3208c5f9bf6656eb040e5 Mon Sep 17 00:00:00 2001 From: TigerXu Date: Fri, 18 Aug 2017 01:09:16 +0800 Subject: [PATCH] update accessing-the-api.md (#4734) --- docs/admin/accessing-the-api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/accessing-the-api.md b/docs/admin/accessing-the-api.md index 08c1eecd06..d181fe8b43 100644 --- a/docs/admin/accessing-the-api.md +++ b/docs/admin/accessing-the-api.md @@ -17,8 +17,8 @@ following diagram: ## Transport Security -In a typical Kubernetes cluster, the API served on port 443. A TLS connection is -established. The API server presents a certificate. This certificate is +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