diff --git a/content/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/_index.md b/content/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/_index.md
index d20733e6422..e0ca4e8d802 100644
--- a/content/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/_index.md
+++ b/content/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/_index.md
@@ -26,19 +26,18 @@ After you download the tools, complete the following actions:
     ```
     chmod +x system-tools
     ```
-1. Download the Kubeconfig File for your Rancher installation cluster and place it in the `/.kube/config` on your workstation. System-tools uses this file to access your installation cluster.
+1. Find the kubeconfig file that was generated during your Rancher installation, `kube_config_rancher-cluster.yml`. Move it to the `/.kube` on your workstation, if it isn't already there. Create this directory if it doesn't exist. 
+
+    System-tools uses this file to access your installation cluster.
 
-    For instructions on how to download the Kubeconfig file, see [Accessing Clusters with kubectl and a kubeconfig File]({{< baseurl >}}rancher/v2.x/en/k8s-in-rancher/kubectl/#accessing-clusters-with-kubectl-and-a-kubeconfig-file).
 
-1. Move `system-tools` to the same directory as the kubeconfig file: `~/.kube/config`.
- 
 ### Using the System-Tool
 
 System-tools is a utility for running operational tasks on Rancher clusters. In this use case, it will help you remove the Rancher from your installation nodes.
 
 #### Usage
 
-After you move the `system-tools` and kubeconfig file to your workstation's `~/.kube/config` directory, you can run system-tools by changing to the `~/.kube/config`  directory and entering the following command.
+After you move the `system-tools` and kubeconfig file to your workstation's `~/.kube` directory, you can run system-tools by changing to the `~/.kube`  directory and entering the following command.
 
 >**Warning:** This command will remove data from your etcd nodes. Make sure you have created a [backup of etcd]({{< baseurl >}}/rancher/v2.x/en/backups/backups) before executing the command.
 
@@ -54,10 +53,14 @@ When you run this command, the components listed in [What Gets Removed?](#what-g
 
 | Option                                         | Description                                                                                                            |
 | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `--kubeconfig <$KUBECONFIG>, -c <$KUBECONFIG>` | The cluster's kubeconfig file absolute path (`<$KUBECONFIG>`).                                                         |
+| `--kubeconfig <KUBECONFIG_PATH>, -c <KUBECONFIG_PATH>` | The cluster's kubeconfig file absolute path, usually `~/.kube/kube_config_rancher-cluster.yml`.<sup>1</sup>    |
 | `--namespace <NAMESPACE>, -n cattle-system`    | Rancher 2.x deployment namespace (`<NAMESPACE>`). If no namespace is defined, the options defaults to `cattle-system`. |
 | `--force`                                      | Skips the the interactive removal confirmation and removes the Rancher deployment without prompt.                      |
 
+> <sup>1</sup> If you are working with multiple Kubernetes clusters, you can place  `kube_config_rancher-cluster.yml` in another directory path and then set the `KUBECONFIG` environment variable to its path.
+>``` 
+export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
+```
 
 ## What Gets Removed?
 
@@ -65,7 +68,7 @@ When removing Rancher from server nodes provisioned using RKE, the following com
 
 
 - The Rancher deployment namespace (`cattle-system` by default).
-- `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` labeled by Rancher.  
+- Any `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` that Rancher applied the `cattle.io/creator:norman` label to. Rancher applies this label to any resource that it creates as of v2.1.0.  
 - Labels, Annotations, and Finalizers.
 - Rancher Deployment.
 - Machines, clusters, projects, and user custom resource deployments (CRDs).