diff --git a/content/rancher/v2.x/en/installation/options/nlb/_index.md b/content/rancher/v2.x/en/installation/options/nlb/_index.md
index 333e4a03a56..431b354b915 100644
--- a/content/rancher/v2.x/en/installation/options/nlb/_index.md
+++ b/content/rancher/v2.x/en/installation/options/nlb/_index.md
@@ -45,12 +45,12 @@ Regardless of whether an NGINX Ingress or Traefik Ingress controller is used, th
 
 Configure the first target group according to the table below. Screenshots of the configuration are shown just below the table.
 
-| Option      | Setting           | 
-| --------- | ----------------- | 
-| Target Group Name       | `rancher-tcp-443` |
+| Option                              | Setting           | 
+|-------------------------------------|-------------------| 
+| Target Group Name                   | `rancher-tcp-443` |
 | Target type                         | `instance`        |
-| Protocol                            | `TCP`             | 
-| Port                                | `443`                   | 
+| Protocol                            | `TCP`             |
+| Port                                | `443`             |
 | VPC                                 | Choose your VPC   |
 
 Health check settings:
@@ -178,4 +178,4 @@ For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s K
 - **Traefik:** The health check path is `/ping`. By default `/ping` is always matched (regardless of Host), and a response from [Traefik itself](https://docs.traefik.io/operations/ping/) is always served.
 - **NGINX Ingress:** The default backend of the NGINX Ingress controller has a `/healthz` endpoint. By default `/healthz` is always matched (regardless of Host), and a response from [`ingress-nginx` itself](https://github.com/kubernetes/ingress-nginx/blob/0cbe783f43a9313c9c26136e888324b1ee91a72f/charts/ingress-nginx/values.yaml#L212) is always served.
 
-To simulate an accurate health check, it is a best practice to use the Host header (Rancher hostname) combined with `/ping` or `/healthz` (for K3s or for RKE clusters, respectively) wherever possible, to get a response from the Rancher Pods, not the Ingress.
\ No newline at end of file
+To simulate an accurate health check, it is a best practice to use the Host header (Rancher hostname) combined with `/ping` or `/healthz` (for K3s or for RKE clusters, respectively) wherever possible, to get a response from the Rancher Pods, not the Ingress.