Fix order of headings (#1465)

* Fix 'title out of sequence' errors

fixed Dockershim.md

* fixed deprecated-features.md

* fixed install-and-configure-kubectl.md

* fixed rancher-is-no-longer-needed.md

* fixed security.md

* fixed technical-items.md + spacing, duplicate section, admonitions

* fixed telemetry.md

* fixed upgrades.md

* fixed upgrade-kubernetes-without-upgrading-rancher.md

* fixed air-gapped-upgrades.md

* fixed dockershim.md

* fixed docker-install-commands.md

* fixed install-kubernetes.md

* fixed infrastructure-private-registry.md

* fixed install-rancher-ha

* fixed manage-namespaces and tune-etcd-for-large-installs.md

* fixed cis-scans/configuration-reference.md

* fixed custom-benchmark.md

* fixed supportconfig.md

* fixed harvester/overview.md

* fixed logging-architecture.md

* fixed logging-helm-chart-options.md + rm'd unnecessary annotation title

* fixed taints-and-tolerances.md

* fixed longhorn/overview.md

* fixed neuvector/overview.md

* fixed monitoring-and-alerting

* fixed rancher-cli.md

* fixed cluster-configuration.md

* fixed monitoring-v2-configuration/examples.md

* fixed servicemonitors-and-podmonitors.md

* fixed other-troubleshooting-tips/dns.md

versioned_docs/version-2.8/integrations-in-rancher/logging/logging-architecture.md

@@ -10,7 +10,7 @@ This section summarizes the architecture of the Rancher logging application.
 
 For more details about how the Logging operator works, see the [official documentation.](https://kube-logging.github.io/docs/#architecture)
 
-### How the Logging Operator Works
+## How the Logging Operator Works
 
 The Logging operator automates the deployment and configuration of a Kubernetes logging pipeline. It deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system.
 

versioned_docs/version-2.8/integrations-in-rancher/logging/logging-helm-chart-options.md

@@ -6,7 +6,7 @@ title: rancher-logging Helm Chart Options
   <link rel="canonical" href="https://ranchermanager.docs.rancher.com/integrations-in-rancher/logging/logging-helm-chart-options"/>
 </head>
 
-### Enable/Disable Windows Node Logging
+## Enable/Disable Windows Node Logging
 
 You can enable or disable Windows node logging by setting `global.cattle.windows.enabled` to either `true` or `false` in the `values.yaml`.
 
@@ -21,7 +21,7 @@ Currently an [issue](https://github.com/rancher/rancher/issues/32325) exists whe
 
 :::
 
-### Working with a Custom Docker Root Directory
+## Working with a Custom Docker Root Directory
 
 If using a custom Docker root directory, you can set `global.dockerRootDirectory` in `values.yaml`.
 
@@ -31,11 +31,11 @@ Note that this only affects Linux nodes.
 
 If there are any Windows nodes in the cluster, the change will not be applicable to those nodes.
 
-### Adding NodeSelector Settings and Tolerations for Custom Taints
+## Adding NodeSelector Settings and Tolerations for Custom Taints
 
 You can add your own `nodeSelector` settings and add `tolerations` for additional taints by editing the logging Helm chart values. For details, see [this page.](taints-and-tolerations.md)
 
-### Enabling the Logging Application to Work with SELinux
+## Enabling the Logging Application to Work with SELinux
 
 :::note Requirements:
 
@@ -49,7 +49,7 @@ To use Logging v2 with SELinux, we recommend installing the `rancher-selinux` RP
 
 Then, when installing the logging application, configure the chart to be SELinux aware by changing `global.seLinux.enabled` to `true` in the `values.yaml`.
 
-### Additional Logging Sources
+## Additional Logging Sources
 
 By default, Rancher collects logs for [control plane components](https://kubernetes.io/docs/concepts/overview/components/#control-plane-components) and [node components](https://kubernetes.io/docs/concepts/overview/components/#node-components) for all cluster types.
 
@@ -72,7 +72,7 @@ When enabled, Rancher collects all additional node and control plane logs the pr
 
 If you're already using a cloud provider's own logging solution such as AWS CloudWatch or Google Cloud operations suite (formerly Stackdriver), it is not necessary to enable this option as the native solution will have unrestricted access to all logs.
 
-### Systemd Configuration
+## Systemd Configuration
 
 In Rancher logging, `SystemdLogPath` must be configured for K3s and RKE2 Kubernetes distributions.
 
@@ -87,7 +87,7 @@ K3s and RKE2 Kubernetes distributions log to journald, which is the subsystem of
   * If `/var/log/journal` exists, then use `/var/log/journal`.
   * If `/var/log/journal` does not exist, then use `/run/log/journal`.
 
-:::note Notes:
+:::note
 
 If any value not described above is returned, Rancher Logging will not be able to collect control plane logs. To address this issue, you will need to perform the following actions on every control plane node:
 

versioned_docs/version-2.8/integrations-in-rancher/logging/taints-and-tolerations.md

@@ -20,7 +20,7 @@ Both provide choice for the what node(s) the pod will run on.
 - [Adding NodeSelector Settings and Tolerations for Custom Taints](#adding-nodeselector-settings-and-tolerations-for-custom-taints)
 
 
-### Default Implementation in Rancher's Logging Stack
+## Default Implementation in Rancher's Logging Stack
 
 By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes.
 The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes.
@@ -47,7 +47,7 @@ In the above example, we ensure that our pod only runs on Linux nodes, and we ad
 
 You can do the same with Rancher's existing taints, or with your own custom ones.
 
-### Adding NodeSelector Settings and Tolerations for Custom Taints
+## Adding NodeSelector Settings and Tolerations for Custom Taints
 
 If you would like to add your own `nodeSelector` settings, or if you would like to add `tolerations` for additional taints, you can pass the following to the chart's values.