diff --git a/content/rancher/v2.x/en/concepts/global-configuration/cli-configuration/_index.md b/content/rancher/v2.x/en/concepts/global-configuration/cli-configuration/_index.md
index c60f737ebc7..4c0646034e7 100644
--- a/content/rancher/v2.x/en/concepts/global-configuration/cli-configuration/_index.md
+++ b/content/rancher/v2.x/en/concepts/global-configuration/cli-configuration/_index.md
@@ -56,7 +56,7 @@ The following commands are available for use in Rancher CLI.
 
 - `apps, [app]`
               
-    Performs operations on catalog applications (i.e. individual [Helm charts](https://docs.helm.sh/developing_charts/) or [Rancher charts]({{< baseurl >}}/rancher/v2.x/en/concepts/catalogs/#rancher-chart-structure).
+    Performs operations on catalog applications (i.e. individual [Helm charts](https://docs.helm.sh/developing_charts/) or [Rancher charts]({{< baseurl >}}/rancher/v2.x/en/concepts/catalogs/#rancher-chart-structure)).
   
 - `catalog`
 
@@ -68,7 +68,7 @@ The following commands are available for use in Rancher CLI.
 
 - `context`
 
-    Switches between Rancher [projects]({{< baseurl >}}/rancher/v2.x/en/concepts/projects).
+    Switches between Rancher [projects]({{< baseurl >}}/rancher/v2.x/en/concepts/projects). For an example, see [Project Selection](#project-selection).
 
 - `inspect [OPTIONS] [RESOURCEID RESOURCENAME]`
 
diff --git a/content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md b/content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md
index b141d888c94..cb9930f726e 100644
--- a/content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md
+++ b/content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md
@@ -2,7 +2,7 @@
 title: Using kubectl to Access a Cluster
 weight: 3450
 ---
-You can access and manage your Kubernetes clusters using the kubectl two ways:
+You can access and manage your Kubernetes clusters using kubectl in two ways:
 
 - [Accessing Clusters with kubectl Shell](#accessing-clusters-with-kubectl-shell)
 - [Accessing Clusters with kubectl CLI and a kubeconfig File](#accessing-clusters-with-kubectl-cli-and-a-kubeconfig-file)
@@ -18,11 +18,11 @@ You can access and manage your clusters by logging into Rancher and opening the
     For more information on using kubectl, see [Kubernetes Documentation: Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/overview/).
 
 
-## Accessing Clusters with kubectl CLI and a kubeconfig File
+## Accessing Clusters with kubectl and a kubeconfig File
 
-Alternatively, you can access your clusters by installing a kubectl on your workstation, and then directing it toward a kubeconfig file automatically generated by Rancher. After install and configuration, you can access your clusters without logging into Rancher.
+Alternatively, you can access your clusters by installing kubectl on your workstation, and then directing it toward a kubeconfig file automatically generated by Rancher. After install and configuration, you can access your clusters without logging into Rancher.
 
-1. Install kubectl on your workstation. For more information, see [Kubernetes Documentation: Install and Set Up kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+1. Install kubectl on your workstation. For more information, see [Kubernetes Documentation: Install and Set Up kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/).
 
 2. Log into Rancher. From the **Global** view, open the cluster that you want to access with kubectl.
 
@@ -32,7 +32,7 @@ Alternatively, you can access your clusters by installing a kubectl on your work
 
     2. Copy the contents displayed to your clipboard.
 
-    3. Paste the contents into a new file on your local computer. Move the file to ``/.kube/config`.
+    3. Paste the contents into a new file on your local computer. Move the file to `~/.kube/config`.
 
         >**Note:** The default location that kubectl uses for the kubeconfig file is `~/.kube/config`, but you can use any directory and specify it using the `--kubeconfig` flag, as in the sample that follows:
         >