Fix tables of contents, headers and formatting

versioned_docs/version-2.5/pages-for-subheaders/fleet-gitops-at-scale.md

@@ -8,20 +8,12 @@ Fleet is GitOps at scale. Fleet is designed to manage up to a million clusters.
 
 Fleet is a separate project from Rancher, and can be installed on any Kubernetes cluster with Helm.
 
-- [Architecture](../explanations/integrations-in-rancher/fleet-gitops-at-scale/architecture.md)
-- [Accessing Fleet in the Rancher UI](#accessing-fleet-in-the-rancher-ui)
-- [Windows Support](../explanations/integrations-in-rancher/fleet-gitops-at-scale/windows-support.md)
-- [GitHub Repository](#github-repository)
-- [Use Fleet Behind a Proxy](../explanations/integrations-in-rancher/fleet-gitops-at-scale/use-fleet-behind-a-proxy.md)
-- [Helm Chart Dependencies](#helm-chart-dependencies)
-- [Troubleshooting](#troubleshooting)
-- [Documentation](#documentation)
 
-# Architecture
+## Architecture
 
 For information about how Fleet works, see [this page](../explanations/integrations-in-rancher/fleet-gitops-at-scale/architecture.md).
 
-# Accessing Fleet in the Rancher UI
+## Accessing Fleet in the Rancher UI
 
 Fleet comes preinstalled in Rancher v2.5. Users can leverage continuous delivery to deploy their applications to the Kubernetes clusters in the git repository without any manual operation by following **gitops** practice. For additional information on Continuous Delivery and other Fleet troubleshooting tips, refer [here](https://fleet.rancher.io/troubleshooting/).
 
@@ -45,29 +37,29 @@ Follow the steps below to access Continuous Delivery in the Rancher UI:
 
 1. Once the gitrepo is deployed, you can monitor the application through the Rancher UI.
 
-# Windows Support
+## Windows Support
 
 _Available as of v2.5.6_
 
 For details on support for clusters with Windows nodes, see [this page](../explanations/integrations-in-rancher/fleet-gitops-at-scale/windows-support.md).
 
-# GitHub Repository
+## GitHub Repository
 
 The Fleet Helm charts are available [here](https://github.com/rancher/fleet/releases/tag/v0.3.10).
 
-# Using Fleet Behind a Proxy
+## Using Fleet Behind a Proxy
 
 _Available as of v2.5.8_
 
 For details on using Fleet behind a proxy, see [this page](../explanations/integrations-in-rancher/fleet-gitops-at-scale/use-fleet-behind-a-proxy.md).
 
-# Helm Chart Dependencies
+## Helm Chart Dependencies
 
 In order for Helm charts with dependencies to deploy successfully, you must run a manual command (as listed below), as it is up to the user to fulfill the dependency list. If you do not do this and proceed to clone your repository and run `helm install`, your installation will fail because the dependencies will be missing.
 
 The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` OR run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters
 
-# Troubleshooting
+## Troubleshooting
 
 - **Known Issue**: Fleet becomes inoperable after a restore using the [backup-restore-operator](../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher#1-install-the-rancher-backup-operator). We will update the community once a permanent solution is in place.
 
@@ -85,7 +77,7 @@ The Helm chart in the git repository must include its dependencies in the charts
 
 - **Temporary Workaround**: By default, user-defined secrets are not backed up in Fleet. It is necessary to recreate secrets if performing a disaster recovery restore or migration of Rancher into a fresh cluster. To modify resourceSet to include extra resources you want to backup, refer to docs [here](https://github.com/rancher/backup-restore-operator#user-flow).
 
-# Documentation
+## Documentation
 
 The Fleet documentation is at https://fleet.rancher.io/.