diff --git a/docs/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/docs/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 68c7ca9d6dd..25845cdc87d 100644
--- a/docs/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/docs/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod Container Logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+## Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+## Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` Lease in the `kube-system` namespace (in this example, `rancher-dbc7ff869-gvg6k`).
 
@@ -87,7 +87,7 @@ NAME                 HOLDER                    AGE
 cattle-controllers   rancher-dbc7ff869-gvg6k   6h10m
 ```
 
-#### Configuration
+### Configuration
 
 _Available as of Rancher 2.8.3_
 
diff --git a/versioned_docs/version-2.0-2.4/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/versioned_docs/version-2.0-2.4/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 3ce3d3881bc..2e32d94ec22 100644
--- a/versioned_docs/version-2.0-2.4/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/versioned_docs/version-2.0-2.4/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_rancher-cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod Container Logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+### Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+### Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`).
 
diff --git a/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 8917f80da4d..fe044bf9d8c 100644
--- a/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/versioned_docs/version-2.5/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod container logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+## Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+## Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`).
 
diff --git a/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 8917f80da4d..ac27df91156 100644
--- a/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod Container Logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+## Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+## Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`).
 
diff --git a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 8917f80da4d..ac27df91156 100644
--- a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod Container Logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+## Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+## Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`).
 
diff --git a/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 68c7ca9d6dd..25845cdc87d 100644
--- a/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/versioned_docs/version-2.8/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod Container Logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+## Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+## Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` Lease in the `kube-system` namespace (in this example, `rancher-dbc7ff869-gvg6k`).
 
@@ -87,7 +87,7 @@ NAME                 HOLDER                    AGE
 cattle-controllers   rancher-dbc7ff869-gvg6k   6h10m
 ```
 
-#### Configuration
+### Configuration
 
 _Available as of Rancher 2.8.3_
 
diff --git a/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/rancher-ha.md b/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/rancher-ha.md
index 68c7ca9d6dd..25845cdc87d 100644
--- a/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+++ b/versioned_docs/version-2.9/troubleshooting/other-troubleshooting-tips/rancher-ha.md
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
 
 Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
 
-### Check Rancher pods
+## Check Rancher Pods
 
 Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
 
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb   1/1     Running   0          8m    x.x.x.x     x.x.x.
 
 If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
 
-#### Pod details
+### Pod Details
 
 ```
 kubectl -n cattle-system describe pods -l app=rancher
 ```
 
-#### Pod container logs
+### Pod Container Logs
 
 ```
 kubectl -n cattle-system logs -l app=rancher
 ```
 
-#### Namespace events
+### Namespace Events
 
 ```
 kubectl -n cattle-system get events
 ```
 
-### Check ingress
+## Check Ingress
 
 Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
 
@@ -64,7 +64,7 @@ NAME      HOSTS                    ADDRESS                   PORTS     AGE
 rancher   rancher.yourdomain.com   x.x.x.x,x.x.x.x,x.x.x.x   80, 443   2m
 ```
 
-### Check ingress controller logs
+## Check Ingress Controller Logs
 
 When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
 
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
 kubectl -n ingress-nginx logs -l app=ingress-nginx
 ```
 
-### Leader election
+## Leader Election
 
 The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` Lease in the `kube-system` namespace (in this example, `rancher-dbc7ff869-gvg6k`).
 
@@ -87,7 +87,7 @@ NAME                 HOLDER                    AGE
 cattle-controllers   rancher-dbc7ff869-gvg6k   6h10m
 ```
 
-#### Configuration
+### Configuration
 
 _Available as of Rancher 2.8.3_