From fbaf7d8f8150b94d9b6b3a4940ce8bffde371d29 Mon Sep 17 00:00:00 2001
From: qiaolei <qiaolei2@huawei.com>
Date: Wed, 16 Sep 2015 20:53:05 +0800
Subject: [PATCH] Fixed some typos in sharing-clusters.md

Fixes are:

1. `.kubeconfig` -> `kubeconfig`
2. `.kubectl` -> `kubectl`
3. `.kubeconfig` -> `.kube/config`
4. `path/to/.kube/config` -> `/path/to/.kube/config`
5. `commandline` -> `command line`
---
 docs/user-guide/sharing-clusters.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/user-guide/sharing-clusters.md b/docs/user-guide/sharing-clusters.md
index 5835e80978e..4bb86803fe2 100644
--- a/docs/user-guide/sharing-clusters.md
+++ b/docs/user-guide/sharing-clusters.md
@@ -34,7 +34,7 @@ Documentation for other releases can be found at
 # Sharing Cluster Access
 
 Client access to a running Kubernetes cluster can be shared by copying
-the `kubectl` client config bundle ([.kubeconfig](kubeconfig-file.md)).
+the `kubectl` client config bundle ([kubeconfig](kubeconfig-file.md)).
 This config bundle lives in `$HOME/.kube/config`, and is generated
 by `cluster/kube-up.sh`. Sample steps for sharing `kubeconfig` below.
 
@@ -64,7 +64,7 @@ $ mv /path/to/.kube/config $HOME/.kube/config
 $ mv /path/to/.kube/config $PWD
 ```
 
-* Option C: manually pass `kubeconfig` location to `.kubectl`
+* Option C: manually pass `kubeconfig` location to `kubectl`
 
 ```console
 # via environment variable
@@ -99,7 +99,7 @@ $ kubectl config set-credentials $USER_NICK \
     --client-certificate=/path/to/crt_file \
     --client-key=/path/to/key_file \
     --embed-certs=true \
-    --kubeconfig=/path/to/standalone/.kubeconfig
+    --kubeconfig=/path/to/standalone/.kube/config
 
 # create context entry
 $ kubectl config set-context $CONTEXT_NAME --cluster=$CLUSTER_NICKNAME --user=$USER_NICK
@@ -127,9 +127,9 @@ and/or run `kubectl config -h`.
 
 `kubectl` loads and merges config from the following locations (in order)
 
-1. `--kubeconfig=path/to/.kube/config` commandline flag
-2. `KUBECONFIG=path/to/.kube/config` env variable
-3. `$PWD/.kubeconfig`
+1. `--kubeconfig=/path/to/.kube/config` command line flag
+2. `KUBECONFIG=/path/to/.kube/config` env variable
+3. `$PWD/.kube/config`
 4. `$HOME/.kube/config`
 
 If you create clusters A, B on host1, and clusters C, D on host2, you can
@@ -137,14 +137,14 @@ make all four clusters available on both hosts by running
 
 ```console
 # on host2, copy host1's default kubeconfig, and merge it from env
-$ scp host1:/path/to/home1/.kube/config path/to/other/.kube/config
+$ scp host1:/path/to/home1/.kube/config /path/to/other/.kube/config
 
-$ export $KUBECONFIG=path/to/other/.kube/config
+$ export $KUBECONFIG=/path/to/other/.kube/config
 
 # on host1, copy host2's default kubeconfig and merge it from env
-$ scp host2:/path/to/home2/.kube/config path/to/other/.kube/config
+$ scp host2:/path/to/home2/.kube/config /path/to/other/.kube/config
 
-$ export $KUBECONFIG=path/to/other/.kube/config
+$ export $KUBECONFIG=/path/to/other/.kube/config
 ```
 
 Detailed examples and explanation of `kubeconfig` loading/merging rules can be found in [kubeconfig-file.md](kubeconfig-file.md).