Update monitoring docs

content/rancher/v2.5/en/monitoring-alerting/guides/_index.md

@@ -1,4 +1,15 @@
 ---
-title: Guides
+title: Monitoring Guides
+shortTitle: Guides
 weight: 4
----
+---
+
+- [Enable monitoring](./enable-monitoring)
+- [Uninstall monitoring](./uninstall)
+- [Monitoring Rancher apps](./monitoring-rancher-apps)
+- [Monitoring workloads](./monitoring-workloads)
+- [Customizing Grafana dashboards](./customize-grafana)
+- [Persistent Grafana dashboards](./persist-grafana)
+- [Setting up metrics for horizontal pod autoscaling](./hpa)
+- [Debugging high memory usage](./memory-usage)
+- [Migrating from Monitoring V1 to V2](./migrating)

content/rancher/v2.5/en/monitoring-alerting/guides/enable-monitoring/_index.md

@@ -9,7 +9,7 @@ This page describes how to enable monitoring and alerting within a cluster using
 
 You can enable monitoring with or without SSL.
 
-### Requirements
+# Requirements
 
 - Make sure that you are allowing traffic on port 9796 for each of your nodes because Prometheus will scrape metrics from here.
 - Make sure your cluster fulfills the resource requirements. The cluster should have at least 1950Mi memory available, 2700m CPU, and 50Gi storage. A breakdown of the resource limits and requests is [here.](./configuration/helm-chart-options/#setting-resource-limits-and-requests)
@@ -23,6 +23,8 @@ The resource requests and limits can be configured when installing `rancher-moni
 
 For more information about the default limits, see [this page.](./configuration/helm-chart-options/#setting-resource-limits-and-requests)
 
+# Install the Monitoring Application
+
 {{% tabs %}}
 {{% tab "Rancher v2.5.8" %}}