diff --git a/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md b/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md
index d015b8b5b03..e7d4186006b 100644
--- a/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md
+++ b/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md
@@ -50,8 +50,7 @@ When upgrading the Kubernetes version of a cluster, we recommend that you:
 
 1. Take a snapshot.
 1. Initiate a Kubernetes upgrade.
-1. If the upgrade fails, revert the cluster to the pre-upgrade Kubernetes version. Before restoring the cluster from the snapshot in the etcd datastore, the cluster should be running the pre-upgrade Kubernetes version.
-1. Restore the cluster from the etcd snapshot.
+1. If the upgrade fails, revert the cluster to the pre-upgrade Kubernetes version. This is achieved by selecting the *Restore etcd and Kubernetes version* option. This will return your cluster to the pre-upgrade kubernetes version before restoring the etcd snapshot.
 
 The restore operation will work on a cluster that is not in a healthy or active state.
 {{% /tab %}}
@@ -158,4 +157,4 @@ A failed node could be in many different states:
 - User drains a node while upgrade is in process, so there are no kubelets on the node
 - The upgrade itself failed
 
-If the max unavailable number of nodes is reached during an upgrade, Rancher user clusters will be stuck in updating state and not move forward with upgrading any other control plane nodes. It will continue to evaluate the set of unavailable nodes in case one of the nodes becomes available. If the node cannot be fixed, you must remove the node in order to continue the upgrade.
\ No newline at end of file
+If the max unavailable number of nodes is reached during an upgrade, Rancher user clusters will be stuck in updating state and not move forward with upgrading any other control plane nodes. It will continue to evaluate the set of unavailable nodes in case one of the nodes becomes available. If the node cannot be fixed, you must remove the node in order to continue the upgrade.