diff --git a/content/rancher/v2.x/en/installation/k8s-install/create-nodes-lb/nlb/_index.md b/content/rancher/v2.x/en/installation/k8s-install/create-nodes-lb/nlb/_index.md
index 911ff36b62f..29aca8a2e39 100644
--- a/content/rancher/v2.x/en/installation/k8s-install/create-nodes-lb/nlb/_index.md
+++ b/content/rancher/v2.x/en/installation/k8s-install/create-nodes-lb/nlb/_index.md
@@ -5,35 +5,28 @@ aliases:
- /rancher/v2.x/en/installation/ha/create-nodes-lb/nlb
---
-## Objectives
-
-Configuring an Amazon NLB is a multistage process. We've broken it down into multiple tasks so that it's easy to follow.
-
-1. [Create Target Groups](#create-target-groups)
-
- Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.
-
-2. [Register Targets](#register-targets)
-
- Add your Linux nodes to the target groups.
-
-3. [Create Your NLB](#create-your-nlb)
-
- Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
+This how-to guide describes how to set up a load balancer in Amazon's EC2 service that will direct traffic to multiple instances on EC2.
> **Note:** Rancher only supports using the Amazon NLB when terminating traffic in `tcp` mode for port 443 rather than `tls` mode. This is due to the fact that the NLB does not inject the correct headers into requests when terminated at the NLB. This means that if you want to use certificates managed by the Amazon Certificate Manager (ACM), you should use an ELB or ALB.
-## Create Target Groups
+Configuring an Amazon NLB is a multistage process:
+
+1. [Create Target Groups](#1-create-target-groups)
+2. [Register Targets](#2-register-targets)
+3. [Create Your NLB](#3-create-your-nlb)
+4. [Add listener to NLB for TCP port 80](#4-add-listener-to-nlb-for-tcp-port-80)
+
+> **Prerequisite:** These instructions assume you have already created Linux instances in EC2. The load balancer will direct traffic to these two nodes.
+
+# 1. Create Target Groups
+
+Begin by creating two target groups for the **TCP** protocol, one with TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.
Your first NLB configuration step is to create two target groups. Technically, only port 443 is needed to access Rancher, but its convenient to add a listener for port 80 which will be redirected to port 443 automatically. The NGINX ingress controller on the nodes will make sure that port 80 gets redirected to port 443.
-Log into the [Amazon AWS Console](https://console.aws.amazon.com/ec2/) to get started, make sure to select the **Region** where your EC2 instances (Linux nodes) are created.
-
-The Target Groups configuration resides in the **Load Balancing** section of the **EC2** service. Select **Services** and choose **EC2**, find the section **Load Balancing** and open **Target Groups**.
-
-{{< img "/img/rancher/ha/nlb/ec2-loadbalancing.png" "EC2 Load Balancing section">}}
-
-Click **Create target group** to create the first target group, regarding TCP port 443.
+1. Log into the [Amazon AWS Console](https://console.aws.amazon.com/ec2/) to get started. Make sure to select the **Region** where your EC2 instances (Linux nodes) are created.
+1. Select **Services** and choose **EC2**, find the section **Load Balancing** and open **Target Groups**.
+1. Click **Create target group** to create the first target group, regarding TCP port 443.
### Target Group (TCP port 443)
@@ -55,15 +48,6 @@ Configure the first target group according to the table below. Screenshots of th
| Interval (Advanced) | `10 second` |
| Success codes | `200-399` |
-
-**Screenshot Target group TCP port 443 settings**
-{{< img "/img/rancher/ha/nlb/create-targetgroup-443.png" "Target group 443">}}
-
-
-**Screenshot Target group TCP port 443 Advanced settings**
-{{< img "/img/rancher/ha/nlb/create-targetgroup-443-advanced.png" "Target group 443 Advanced">}}
-
-
Click **Create target group** to create the second target group, regarding TCP port 80.
@@ -87,17 +71,7 @@ Configure the second target group according to the table below. Screenshots of t
| Interval (Advanced) | `10 second` |
| Success codes | `200-399` |
-
-**Screenshot Target group TCP port 80 settings**
-{{< img "/img/rancher/ha/nlb/create-targetgroup-80.png" "Target group 80">}}
-
-
-**Screenshot Target group TCP port 80 Advanced settings**
-{{< img "/img/rancher/ha/nlb/create-targetgroup-80-advanced.png" "Target group 80 Advanced">}}
-
-
-
-## Register Targets
+# 2. Register Targets
Next, add your Linux nodes to both target groups.
@@ -121,7 +95,9 @@ When the instances are added, click **Save** on the bottom right of the screen.
Repeat those steps, replacing **rancher-tcp-443** with **rancher-tcp-80**. The same instances need to be added as targets to this target group.
-## Create Your NLB
+# 3. Create Your NLB
+
+Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in [Create Target Groups](#create-target-groups).
@@ -131,41 +107,39 @@ Use Amazon's Wizard to create an Network Load Balancer. As part of this process,
3. Click **Create Load Balancer**.
-4. Choose **Network Load Balancer** and click **Create**.
+4. Choose **Network Load Balancer** and click **Create**. Then complete each form.
-5. Complete the **Step 1: Configure Load Balancer** form.
+- [Step 1: Configure Load Balancer](#step-1-configure-load-balancer)
+- [Step 2: Configure Routing](#step-2-configure-routing)
+- [Step 3: Register Targets](#step-3-register-targets)
+- [Step 4: Review](#step-4-review)
- - **Basic Configuration**
+### Step 1: Configure Load Balancer
- - Name: `rancher`
- - Scheme: `internal` or `internet-facing`
+Set the following fields in the form:
- The Scheme that you choose for your NLB is dependent on the configuration of your instances/VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`.
+- **Name:** `rancher`
+- **Scheme:** `internal` or `internet-facing`. The scheme that you choose for your NLB is dependent on the configuration of your instances and VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`.
+- **Listeners:** The Load Balancer Protocol should be `TCP` and the corresponding Load Balancer Port should be set to `443`.
+- **Availability Zones:** Select Your **VPC** and **Availability Zones**.
- - **Listeners**
+### Step 2: Configure Routing
- Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
- - `TCP`: `443`
+1. From the **Target Group** drop-down, choose **Existing target group**.
+1. From the **Name** drop-down, choose `rancher-tcp-443`.
+1. Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.
- - **Availability Zones**
+### Step 3: Register Targets
- - Select Your **VPC** and **Availability Zones**.
+Since you registered your targets earlier, all you have to do is click **Next: Review**.
-6. Complete the **Step 2: Configure Routing** form.
+### Step 4: Review
- - From the **Target Group** drop-down, choose **Existing target group**.
+Look over the load balancer details and click **Create** when you're satisfied.
- - From the **Name** drop-down, choose `rancher-tcp-443`.
+After AWS creates the NLB, click **Close**.
- - Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.
-
-7. Complete **Step 3: Register Targets**. Since you registered your targets earlier, all you have to do is click **Next: Review**.
-
-8. Complete **Step 4: Review**. Look over the load balancer details and click **Create** when you're satisfied.
-
-9. After AWS creates the NLB, click **Close**.
-
-## Add listener to NLB for TCP port 80
+# 4. Add listener to NLB for TCP port 80
1. Select your newly created NLB and select the **Listeners** tab.
diff --git a/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md b/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md
index a30d1bd9a26..ea0fcda275f 100644
--- a/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md
+++ b/content/rancher/v2.x/en/installation/k8s-install/helm-rancher/_index.md
@@ -1,5 +1,5 @@
---
-title: 3. Installing Rancher Using the Helm Kubernetes Package Manager
+title: 3. Install Rancher on the Kubernetes Cluster
description: Rancher installation is managed using the Helm Kubernetes package manager. Use Helm to install the prerequisites and charts to install Rancher
weight: 200
aliases:
diff --git a/content/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/_index.md b/content/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/_index.md
index 361ebf300c9..a8ef27e1f24 100644
--- a/content/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/_index.md
+++ b/content/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/_index.md
@@ -1,5 +1,5 @@
---
-title: 2. Install Kubernetes with RKE
+title: 2. Set up a Kubernetes Cluster
description: Learn how to use Rancher Kubernetes Engine (RKE) to install Kubernetes with a high availability etcd configuration.
weight: 190
aliases: