diff --git a/content/rancher/v2.x/en/cluster-provisioning/imported-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/imported-clusters/_index.md
index ee0e464256d..3659965b958 100644
--- a/content/rancher/v2.x/en/cluster-provisioning/imported-clusters/_index.md
+++ b/content/rancher/v2.x/en/cluster-provisioning/imported-clusters/_index.md
@@ -5,7 +5,7 @@ aliases:
   - /rancher/v2.x/en/tasks/clusters/import-cluster/
 ---
 
-You can import an existing Kubernetes cluster and then manage it using Rancher.
+You can import an existing Kubernetes cluster and then manage it using Rancher. Keep in mind that editing your Kubernetes cluster (for example: adding/removing nodes, upgrading Kubernetes cluster version and changing Kubernetes component parameters) still has to be done outside of Rancher.
 
 >**Prerequisites:**
 >
@@ -20,17 +20,17 @@ You can import an existing Kubernetes cluster and then manage it using Rancher.
 
 4. {{< step_create-cluster_member-roles >}}
 
-5.	Click **Create**.
+5. Click **Create**.
 
-6.	Copy the first command displayed to your clipboard.
+6. The prerequisite for `cluster-admin` privileges is shown (see **Prerequisites** above), including an example command to fulfil the prerequisite.
 
-7. Log into one of your cluster nodes using your preferred shell, such as PuTTy or a remote Terminal connection. Run the command copied to your clipboard.
+7. Copy the `kubectl` command to your clipboard and run it on a node where kubeconfig is configured to point to the cluster you want to import. If you are unsure it is configured correctly, run `kubectl get nodes` to verify before running the command shown in {{< product >}}.
 
-8.	If you receive a message of `certificate signed by unknown authority`, copy the second command displayed in {{< product >}} to your clipboard. Then run the command on your cluster node.
+8. If you are using self signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in {{< product >}} to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
 
-9. When you finish running the command(s) on your Linux host(s), click **Done**.
+9. When you finish running the command(s) on your node, click **Done**.
 
-{{< result_create-cluster >}}
+{{< result_import-cluster >}}
 
 > **Note:**
 > You can not re-import a cluster that is currently active in a Rancher setup.
diff --git a/layouts/shortcodes/result_create-cluster.html b/layouts/shortcodes/result_create-cluster.html
index 8aaada7a97c..d49bc3d334a 100644
--- a/layouts/shortcodes/result_create-cluster.html
+++ b/layouts/shortcodes/result_create-cluster.html
@@ -3,6 +3,6 @@
 	<ul>
 		<li>Your cluster is created and assigned a state of <strong>Provisioning</strong>. Rancher is standing up your cluster.</li>
 		<li>You can access your cluster after its state is updated to <strong>Active</strong>.</li>
-		<li><strong>Active</strong> clusters are assigned a Project and Namespace, both of which are named <code>Default</code>.</li>
+		<li><strong>Active</strong> clusters are assigned two Projects, <code>Default</code> (containing the namespace <code>default</code>) and <code>System</code> (containing the namespaces <code>cattle-system</code>,<code>ingress-nginx</code>,<code>kube-public</code> and <code>kube-system</code>, if present).
 	</ul>
 </div>
diff --git a/layouts/shortcodes/result_import-cluster.html b/layouts/shortcodes/result_import-cluster.html
new file mode 100644
index 00000000000..482b450bfb8
--- /dev/null
+++ b/layouts/shortcodes/result_import-cluster.html
@@ -0,0 +1,8 @@
+<div>
+	<p><strong>Result:</strong></p>
+	<ul>
+		<li>Your cluster is created and assigned a state of <strong>Pending</strong>. Rancher is deploying resources to manage your cluster.</li>
+		<li>You can access your cluster after its state is updated to <strong>Active</strong>.</li>
+		<li><strong>Active</strong> clusters are assigned two Projects <code>Default</code> (containing the namespace <code>default</code>) and <code>System</code> (containing the namespaces <code>cattle-system</code>,<code>ingress-nginx</code>,<code>kube-public</code> and <code>kube-system</code>, if present).
+	</ul>
+</div>