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.5/reference-guides/cli-with-rancher/rancher-cli.md

@@ -9,18 +9,18 @@ description: Interact with Rancher using command line interface (CLI) tools from
 
 The Rancher CLI (Command Line Interface) is a unified tool that you can use to interact with Rancher. With this tool, you can operate Rancher using a command line rather than the GUI.
 
-### Download Rancher CLI
+## Download Rancher CLI
 
 The binary can be downloaded directly from the UI. The link can be found in the right hand side of the footer in the UI. We have binaries for Windows, Mac, and Linux. You can also check the [releases page for our CLI](https://github.com/rancher/cli/releases) for direct downloads of the binary.
 
-### Requirements
+## Requirements
 
 After you download the Rancher CLI, you need to make a few configurations. Rancher CLI requires:
 
 - Your Rancher Server URL, which is used to connect to Rancher Server.
 - An API Bearer Token, which is used to authenticate with Rancher. For more information about obtaining a Bearer Token, see [Creating an API Key](../../reference-guides/user-settings/api-keys.md).
 
-### CLI Authentication
+## CLI Authentication
 
 Before you can use Rancher CLI to control your Rancher Server, you must authenticate using an API Bearer Token. Log in using the following command (replace `<BEARER_TOKEN>` and `<SERVER_URL>` with your information):
 
@@ -30,7 +30,7 @@ $ ./rancher login https://<SERVER_URL> --token <BEARER_TOKEN>
 
 If Rancher Server uses a self-signed certificate, Rancher CLI prompts you to continue with the connection.
 
-### Project Selection
+## Project Selection
 
 Before you can perform any commands, you must select a Rancher project to perform those commands against. To select a [project](../../how-to-guides/advanced-user-guides/manage-clusters/projects-and-namespaces.md) to work on, use the command `./rancher context switch`. When you enter this command, a list of available projects displays. Enter a number to choose your project.
 
@@ -54,7 +54,7 @@ INFO[0005] Saving config to /Users/markbishop/.ranchcli2.json
 
 Ensure you can run `rancher kubectl get pods` successfully.
 
-### Commands
+## Commands
 
 The following commands are available for use in Rancher CLI.
 
@@ -76,12 +76,12 @@ The following commands are available for use in Rancher CLI.
 | `help, [h]`  | Shows a list of commands or help for one command.  |
 
 
-### Rancher CLI Help
+## Rancher CLI Help
 
 Once logged into Rancher Server using the CLI, enter `./rancher --help` for a list of commands.
 
 All commands accept the `--help` flag, which documents each command's usage.
 
-### Limitations
+## Limitations
 
 The Rancher CLI **cannot** be used to install [dashboard apps or Rancher feature charts](../../how-to-guides/new-user-guides/helm-charts-in-rancher.md).

versioned_docs/version-2.5/reference-guides/cluster-configuration/cluster-configuration.md

@@ -10,7 +10,7 @@ After you provision a Kubernetes cluster using Rancher, you can still edit optio
 
 For information on editing cluster membership, go to [this page.](../../how-to-guides/advanced-user-guides/manage-clusters/access-clusters/add-users-to-clusters.md)
 
-### Cluster Configuration References
+## Cluster Configuration References
 
 The cluster configuration options depend on the type of Kubernetes cluster:
 
@@ -18,7 +18,7 @@ The cluster configuration options depend on the type of Kubernetes cluster:
 - [EKS Cluster Configuration](rancher-server-configuration/eks-cluster-configuration.md)
 - [GKE Cluster Configuration](rancher-server-configuration/gke-cluster-configuration/gke-cluster-configuration.md)
 
-### Cluster Management Capabilities by Cluster Type
+## Cluster Management Capabilities by Cluster Type
 
 The options and settings available for an existing cluster change based on the method that you used to provision it.
 

versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/examples.md

@@ -6,15 +6,15 @@ title: Monitoring V2 Configuration Examples
   <link rel="canonical" href="https://ranchermanager.docs.rancher.com/reference-guides/monitoring-v2-configuration/examples"/>
 </head>
 
-### ServiceMonitor
+## ServiceMonitor
 
 See the official prometheus-operator GitHub repo for an example [ServiceMonitor](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml) YAML.
 
-### PodMonitor
+## PodMonitor
 
 See the [Prometheus Operator documentation](https://prometheus-operator.dev/docs/user-guides/getting-started/#using-podmonitors) for an example PodMonitor and an example Prometheus resource that refers to a PodMonitor.
 
-### PrometheusRule
+## PrometheusRule
 
 A PrometheusRule contains the alerting and recording rules that you would usually place in a [Prometheus rule file](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/).
 
@@ -22,6 +22,6 @@ For a more fine-grained approach, the `ruleSelector` field on a Prometheus resou
 
 See the [Prometheus Operator documentation](https://prometheus-operator.dev/docs/user-guides/alerting/) for an example PrometheusRule.
 
-### Alertmanager Config
+## Alertmanager Config
 
 See the Rancher docs page on Receivers for an example [Alertmanager config](./receivers.md#example-alertmanager-configs).

versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/servicemonitors-and-podmonitors.md

@@ -14,7 +14,7 @@ ServiceMonitors are more commonly used than PodMonitors, and we recommend them f
 
 > This section assumes familiarity with how monitoring components work together. For more information, see [this section.](../../explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md)
 
-### ServiceMonitors
+## ServiceMonitors
 
 This pseudo-CRD maps to a section of the Prometheus custom resource configuration. It declaratively specifies how groups of Kubernetes services should be monitored.
 
@@ -24,7 +24,7 @@ Any Services in your cluster that match the labels located within the ServiceMon
 
 For more information about how ServiceMonitors work, refer to the [Prometheus Operator documentation.](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/running-exporters.md)
 
-### PodMonitors
+## PodMonitors
 
 This pseudo-CRD maps to a section of the Prometheus custom resource configuration. It declaratively specifies how group of pods should be monitored.