spelling error

Signed-off-by: yanan Lee <energylyn@zju.edu.cn>

Incorrect spelling

Signed-off-by: yanan Lee <energylyn@zju.edu.cn>

spelling error

Signed-off-by: yanan Lee <energylyn@zju.edu.cn>

Incorrect spelling

Signed-off-by: yanan Lee <energylyn@zju.edu.cn>

Revert "Incorrect spelling"

fix some typos

Signed-off-by: Jie Luo <luo612@zju.edu.cn>

fix a typo

Signed-off-by: Jie Luo <luo612@zju.edu.cn>

fix a typo

Signed-off-by: Jie Luo <luo612@zju.edu.cn>
This commit is contained in:
yanan Lee
2016-12-22 17:14:39 +08:00
committed by Jie Luo
parent 9440814e65
commit fbf57b224f
22 changed files with 25 additions and 25 deletions
+1 -1
View File
@@ -24,7 +24,7 @@ following diagram:
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
often self-signed, so `$USER/.kube/config` on the user's machine typically
contains the root certficate for the API server's certificate, which when specified
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
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