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.0-2.4/how-to-guides/advanced-user-guides/manage-projects/manage-namespaces.md

@@ -26,7 +26,7 @@ To manage permissions in a vanilla Kubernetes cluster, cluster admins configure
 > **Note:** If you create a namespace with `kubectl`, it may be unusable because `kubectl` doesn't require your new namespace to be scoped within a project that you have access to. If your permissions are restricted to the project level, it is better to [create a namespace through Rancher](manage-namespaces.md) to ensure that you will have permission to access the namespace.
 
 
-### Creating Namespaces
+## Creating Namespaces
 
 Create a new namespace to isolate apps and resources in a project.
 
@@ -44,7 +44,7 @@ Create a new namespace to isolate apps and resources in a project.
 
 **Result:** Your namespace is added to the project. You can begin assigning cluster resources to the namespace.
 
-### Moving Namespaces to Another Project
+## Moving Namespaces to Another Project
 
 Cluster admins and members may occasionally need to move a namespace to another project, such as when you want a different team to start using the application.
 
@@ -64,7 +64,7 @@ Cluster admins and members may occasionally need to move a namespace to another
 
 **Result:** Your namespace is moved to a different project (or is unattached from all projects). If any project resources are attached to the namespace, the namespace releases them and then attached resources from the new project.
 
-### Editing Namespace Resource Quotas
+## Editing Namespace Resource Quotas
 
 You can always override the namespace default limit to provide a specific namespace with access to more (or less) project resources.