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 221d4d74ff9..0ae9fc9ad89 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
@@ -9,26 +9,16 @@ This procedure describes how to use RKE to restore a snapshot of the Rancher Kub
## Restore Outline
-1. [Preparation](#1-preparation)
+
- Install utilities and create new or clean existing nodes to prepare for restore.
-2. [Place Snapshot and PKI Bundle](#2-place-snapshot-and-pki-bundle)
-
- Pick a node and place snapshot `.db` and `pki.bundle.tar.gz` files.
-
-3. [Configure RKE](#3-configure-rke)
-
- Configure RKE `cluster.yml`. Remove `addons:` section and point configuration to the clean nodes.
-
-4. [Restore Database](#4-restore-database)
-
- Run RKE command to restore the `etcd` database to a single node.
-
-5. [Bring Up the Cluster](#5-bring-up-the-cluster)
-
- Run RKE commands to bring up cluster one a single node. Clean up old nodes. Verify and add additional nodes.
+- [1. Preparation](#1-preparation)
+- [2. Place Snapshot and PKI Bundle](#2-place-snapshot-and-pki-bundle)
+- [3. Configure RKE](#3-configure-rke)
+- [4. Restore Database](#4-restore-database)
+- [5. Bring Up the Cluster](#5-bring-up-the-cluster)
+
### 1. Preparation
diff --git a/content/rancher/v2.x/en/installation/server-tags/_index.md b/content/rancher/v2.x/en/installation/server-tags/_index.md
index 2dde9a9e39b..19394fb0593 100644
--- a/content/rancher/v2.x/en/installation/server-tags/_index.md
+++ b/content/rancher/v2.x/en/installation/server-tags/_index.md
@@ -1,13 +1,51 @@
---
-title: Server Tags
+title: Choosing a Version of Rancher
weight: 230
---
-{{< product >}} Server is distributed as a Docker image, which have _tags_ attached to them. Tags are used to identify what version is included in the image. Rancher includes additional tags that point to a specific version. Remember that if you use the additional tags, you must explicitly pull a new version of that image tag. Otherwise it will use the cached image on the host.
+## Single Node Installs
+
+When performing single-node installs, upgrades, or rollbacks, you can use _tags_ to install a specific version of Rancher.
+
+### Server Tags
+
+Rancher Server is distributed as a Docker image, which have tags attached to them. Remember that if you use the additional tags, you must explicitly pull a new version of that image tag. Otherwise it will use the cached image on the host.
You can find Rancher images at [DockerHub](https://hub.docker.com/r/rancher/rancher/tags/).
-- `rancher/rancher:latest`: Our latest development release. These builds are validated through our CI automation framework. These releases are not recommended for production environments.
-- `rancher/rancher:stable`: Our newest stable release. This tag is recommended for production.
+| Tag | Description |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `rancher/rancher:latest` | Our latest development release. These builds are validated through our CI automation framework. These releases are not recommended for production environments. |
+| `rancher/rancher:stable` | Our newest stable release. This tag is recommended for production. |
+| `rancher/rancher:` | You can install specific versions of Rancher by using the tag from a previous release. |
+
The `master` tag or any tag with a `-rc` or another suffix is meant for the {{< product >}} testing team to validate. You should not use these tags, as these builds are not officially supported.
+
+## High Availability Installs
+
+When installing, upgrading, or rolling back Rancher Server in a high availability configuration, you can choose what version of Rancher you want to use.
+
+The images available for installation are controlled by two factors:
+
+- The Rancher Helm repository that you configured (or will configure) during initial installation of Rancher Server.
+- The `rancherImageTag` option, which you can set from the command line.
+
+### Rancher Chart Repositories
+
+In high availability Rancher configurations, Rancher Server is distributed by Helm chart. Therefore, as you prepare to install or upgrade a high availability Rancher configuration, you must configure a chart repository that contains Docker images for Rancher. You can install Rancher from two different repos:
+
+Repository | Repo Configuration Command | Description
+-----------|-----|-------------
+`latest` | `helm repo add rancher-latest https://releases.rancher.com/server-charts/latest` | Adds a repository of Helm charts for the latest versions of Rancher. We recommend using this repo.
+`stable` | `helm repo add rancher-stable https://releases.rancher.com/server-charts/stable` | Adds a repository of Helm charts for older, stable versions of Rancher.
+
+>**Important!**
+>
+>When _upgrading_ or _rolling back_ Rancher in a high availability configuration, you must use the same repository that you used during installation.
+
+### Chart Option: `rancherImageTag`
+
+When installing Rancher in a high availability configuration, the latest version is used by default. However, if you want to install specific version of Rancher, you can set the `rancherImageTag` [option]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/#advanced-options). This option sets the version of Rancher that's deployed when you install by Helm chart.
+
+>**Note:** The versions of Rancher available in [chart repository](#rancher-chart-repositories) are different.
\ No newline at end of file
diff --git a/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm-airgap/_index.md b/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm-airgap/_index.md
index 55021f59cb3..2b5187324ce 100644
--- a/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm-airgap/_index.md
+++ b/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm-airgap/_index.md
@@ -45,14 +45,18 @@ rancher-latest/rancher 2018.10.1 v2.1.0 Install Rancher Serve
helm repo update
```
-1. Fetch the latest `rancher-latest/rancher` chart.
+1. Fetch the latest Rancher Server chart from the helm repository that you used during installation.
This will pull down the chart and save it in the current directory as a `.tgz` file.
+ >**Note:** This command assumes you have the `latest` Rancher helm repo configured. If you initially installed Rancher using the `stable` helm repo, replace `rancher-latest` with `rancher-stable`. For more information, see [Server Tags]({{< baseurl >}}/rancher/v2.x/en/installation/server-tags/).
+
```plain
helm fetch rancher-latest/rancher
```
+
+
1. Render the upgrade template.
Use the same `--set` values you used for the install. Remember to set the `--is-upgrade` flag for `helm`. This will create a `rancher` directory with the Kubernetes manifest files.
diff --git a/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm/_index.md b/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm/_index.md
index 2a091738e35..0f1f3696715 100644
--- a/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm/_index.md
+++ b/content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm/_index.md
@@ -46,6 +46,8 @@ Since there are times where the helm chart will require changes without any chan
Run `helm search rancher` to view which Rancher version will be launched for the specific helm chart version.
+
+
```
NAME CHART VERSION APP VERSION DESCRIPTION
rancher-latest/rancher 2018.10.1 v2.1.0 Install Rancher Server to manage Kubernetes clusters acro...
@@ -78,8 +80,9 @@ rancher-latest/rancher 2018.10.1 v2.1.0 Install Rancher Serve
```
> **Important:**
+ >
>- For any values listed from Step 2, you must use `--set key=value` to apply the same values to the helm chart.
- >- During upgrade, you must use the Rancher chart repository that you used during initial install (the `latest` repository by default). For more information, see [Server Tags]({{< baseurl >}}/rancher/v2.x/en/installation/server-tags/)
+ >- During upgrade, you must use the Rancher chart repository that you used during initial install (the `latest` repository by default). For more information, see [Server Tags]({{< baseurl >}}/rancher/v2.x/en/installation/server-tags/).
## Rolling Back