diff --git a/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md
index 3bba237ec1a..52882472573 100644
--- a/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md
+++ b/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md
@@ -10,14 +10,15 @@ To upgrade Rancher Server 2.x when a new version is released, create a data cont
 
 ## Before You Start
 
-During upgrade, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (`<EXAMPLE>`). Here's an example of a command with a placeholder:
+During upgrade, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (`<EXAMPLE>`). 
 
+Here's an **example** of a command with a placeholder:
 
 ```
-docker run  --volumes-from rancher-data -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup-<RANCHER_VERSION>-<DATE>.tar.gz /var/lib/rancher
+docker stop <RANCHER_CONTAINER_NAME>
 ```
 
-In this command, `<RANCHER_VERSION>-<DATE>` is the version number and date of creation for a backup of Rancher.
+In this command, `<RANCHER_CONTAINER_NAME>` is the name of your Rancher container.
 
 Cross reference the image and reference table below to learn how to obtain this placeholder data. Write down or copy this information before starting the [procedure below](#completing-the-upgrade).