diff --git a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
index 35ed99bcf82..d3f743042a2 100644
--- a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
+++ b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
@@ -3,9 +3,9 @@ title: Single Node Upgrade
 weight: 1010
 draft: true
 ---
-Upgrading Rancher Server running on a single node requires only a few commands.
+To upgrade Rancher Server 2.x to the latest version, you need to enter only a few commands.
 
-1. Stop your Rancher container. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
+1. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
 
 	```
 docker stop <RANCHER_CONTAINER_ID>
@@ -13,7 +13,7 @@ docker stop <RANCHER_CONTAINER_ID>
 
 	>**Tip:** You can obtain the ID for your Rancher container by entering the following command: `docker container ls`
 
-2. Create a `rancher-data` container. This container backs up the data from your current Rancher install, which you'll restore later.
+2. Create a `rancher-data` container. This container backs up the data from your current Rancher Server, which you'll restore in step 4.
 
 	```
 docker create --volumes-from <RANCHER_CONTAINER_ID> \
@@ -29,15 +29,17 @@ docker pull rancher/rancher:latest
 
 	```
 docker run -d --volumes-from rancher-data --restart=unless-stopped \
--p 8080:8080 rancher/rancher:latest
+-p 80:80 -p 443:443 rancher/rancher:latest
 	```
 	>**Note:** _Do not_ stop the upgrade after initiating it, even if the upgrade process seems longer than expected. Stopping the upgrade may result in database migration errors during future upgrades.
 	><br/>
 	><br/>
-	>**Note:** After standing up your upgraded Rancher Server, data from your upgraded server is also saved to the `rancher-data` container for use in future upgrades.
+	>**Note:** After upgrading Rancher Server, data from your upgraded server is also saved to the `rancher-data` container for use in future upgrades.
 
 5. Remove the previous Rancher Server container.
 
 	If you only stop the previous Rancher Server container (and don't remove it), the container may restart after the next server reboot.
 
+6. Log into Rancher. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window.
+
 **Result:** Rancher server is upgraded to the latest version.