diff --git a/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md b/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md
index 4c72e4dccbb..1048763f0d8 100644
--- a/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md
+++ b/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md
@@ -29,7 +29,7 @@ RKE, the installer that provisions your air gapped cluster, will configure an In
 Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configuration will vary depending on your environment.
 
 >**Important:**
->Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend 1) dedicating the `local` cluster to Rancher and no other apps and 2) deploying applications only in clusters that you launch using Rancher. 
+>Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
 
 **Load Balancer Configuration Samples:**
 
diff --git a/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md b/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md
index 99edb3c1aa8..a062c9b1108 100644
--- a/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md
+++ b/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md
@@ -20,7 +20,7 @@ RKE will configure an Ingress controller pod, on each of your nodes. The Ingress
 Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configuration will vary depending on your environment. 
 
 >**Important:**
->Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend 1) dedicating the `local` cluster to Rancher and no other apps and 2) deploying applications only in clusters that you launch using Rancher.
+>Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
 
 #### Examples