diff --git a/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md b/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md
index e5877b14a1c..e4906b85a29 100644
--- a/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md
+++ b/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md
@@ -1,10 +1,10 @@
 ---
-title: Restoring Backups—High Availablity Installs
+title: Restoring Backups—High Availability Installs
 weight: 370
 aliases:
   - /rancher/v2.x/en/installation/after-installation/ha-backup-and-restoration/
 ---
-This procedure describes how to restore your a snapshot of  `etcd` if you lose your Rancher data in a disaster scenario.
+This procedure describes how to restore your a snapshot of `etcd` if you lose your Rancher data in a disaster scenario.
 
 ## Restoration Outline
 
@@ -56,9 +56,9 @@ docker ps | grep calico | cut -f 1 -d " " | xargs docker restart
 
 To restore the most recent `etcd` snapshot on your new node, run RKE the command `rke etcd snapshot-restore`. This command reverts to any snapshot stored in `/opt/rke/etcd-snapshots` that you explicitly define. When you run `rke etcd snapshot-restore`, RKE removes the old `etcd` container if it still exists. To restore operations, RKE creates a new `etcd` cluster using the snapshot you choose.
 
->**Important:** When restoring the etcd database, you must restore each `etcd` to the _same_ snapshot, this means the exact same copy, so to restore you have to copy the snapshot from one of the nodes to the others before doing the `etcd snapshot-restore`.
-
 >**Warning:** Restoring an `etcd` snapshot deletes your current `etcd` cluster and replaces it with a new one. Before you run the `rke etcd snapshot-restore` command, backup any important data in your current cluster.
+>
+>**Prerequisites:** {{< requirements_rollback >}}
 
 
 1. From your workstation, open `rancher-cluster.yml` in your favorite text editor.
diff --git a/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md b/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md
index 913a2f12409..bc981c59d08 100644
--- a/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md
+++ b/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md
@@ -11,6 +11,7 @@ If you upgrade Rancher, but the upgrade does not complete successfully, you may
 >**Warning!**
 >
 > Rolling back to a previous version of Rancher destroys any changes made to Rancher following the upgrade. Unrecoverable data loss may occur.
+
 >
 >**Prerequisites:** {{< requirements_rollback >}}
 
diff --git a/layouts/shortcodes/requirements_rollback.html b/layouts/shortcodes/requirements_rollback.html
index d0d9cd6f81c..ccf2c8d316c 100644
--- a/layouts/shortcodes/requirements_rollback.html
+++ b/layouts/shortcodes/requirements_rollback.html
@@ -8,5 +8,8 @@
             <p><code>rancher-cluster.yml</code></p>
             <p>You'll need the RKE config file that you used for Rancher install, <code>rancher-cluster.yml</code>. You created this file during your initial install. Place this file in same directory as the RKE binary.</p>
         </li>
+        <li>
+            You must restore each of your <code>etcd</code> nodes to the <i>same</i> snapshot. Copy the snapshot you're using from one of your nodes to the others before running the <code>etcd snapshot-restore</code> command.
+        </li>
     </ul>
 </div>
\ No newline at end of file