From f389cce861a858ca984ba95cc18a87e7ffe00ffe Mon Sep 17 00:00:00 2001
From: Mark Bishop <mark@rancher.com>
Date: Thu, 23 Aug 2018 13:05:11 -0700
Subject: [PATCH] Revert "clarifying what data container to use for rollbacks"

This reverts commit 7fbe122647963a369f2246401f34b4806956444e.
---
 .../en/upgrades/rollbacks/single-node-rollbacks/_index.md     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md b/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md
index 5e9e13a6bb1..08bac2e9107 100644
--- a/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md
+++ b/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md
@@ -31,9 +31,9 @@ docker run  --volumes-from rancher-data \
    && tar zxvf /backup/<BACKUP_FILENAME>.tar.gz"
      ```
 
-4. Start a new Rancher Server container that uses the `<RANCHER_VERSION>` data container that you created in [Step 3]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/#backup) of [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade).
+4. Start a new Rancher Server container with the `<PRIOR_VERSION>` tag pointing to the data container.
     ```
 docker run -d --volumes-from rancher-data \
-  --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:<RANCHER_VERSION>
+  --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:<PRIOR_VERSION>
     ```
     >**Note:** _Do not_ stop the rollback after initiating it, even if the rollback process seems longer than expected. Stopping the rollback may result in database issues during future upgrades.