Updating notes

docs/en/monitoring-alerting/configuration/advanced/alertmanager/alertmanager.md

@@ -7,7 +7,11 @@ It is usually not necessary to directly edit the Alertmanager custom resource. F
 
 When Receivers and Routes are updated, the monitoring application will automatically update the Alertmanager custom resource to be consistent with those changes.
 
-> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../../how-monitoring-works/#3-how-alertmanager-works)
+:::note
+
+This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../../how-monitoring-works/#3-how-alertmanager-works)
+
+:::
 
 # About the Alertmanager Custom Resource
 

docs/en/monitoring-alerting/configuration/advanced/prometheus/prometheus.md

@@ -5,7 +5,11 @@ weight: 1
 
 It is usually not necessary to directly edit the Prometheus custom resource because the monitoring application automatically updates it based on changes to ServiceMonitors and PodMonitors.
 
-> This section assumes familiarity with how monitoring components work together. For more information, see [this section.](../../../how-monitoring-works/)
+:::note
+
+This section assumes familiarity with how monitoring components work together. For more information, see [this section.](../../../how-monitoring-works/)
+
+:::
 
 # About the Prometheus Custom Resource
 

docs/en/monitoring-alerting/configuration/advanced/prometheusrules/prometheusrules.md

@@ -5,12 +5,19 @@ weight: 3
 
 A PrometheusRule defines a group of Prometheus alerting and/or recording rules.
 
-> This section assumes familiarity with how monitoring components work together. For more information, see [this section.]({{<baseurl>}}/rancher/v2.6/en/monitoring-alerting/how-monitoring-works)
+:::note
 
+This section assumes familiarity with how monitoring components work together. For more information, see [this section.]({{<baseurl>}}/rancher/v2.6/en/monitoring-alerting/how-monitoring-works)
+
+:::
 
 ### Creating PrometheusRules in the Rancher UI
 
-> **Prerequisite:** The monitoring application needs to be installed.
+:::note Prerequisite:
+
+The monitoring application needs to be installed.
+
+:::
 
 To create rule groups in the Rancher UI,
 

docs/en/monitoring-alerting/configuration/configuration.md

@@ -11,7 +11,11 @@ For information on configuring custom scrape targets and rules for Prometheus, p
 
 The resource requests and limits for the monitoring application can be configured when installing `rancher-monitoring`. For more information about the default limits, see [this page.](./helm-chart-options/#configuring-resource-limits-and-requests)
 
->**Note:** On an idle cluster, Monitoring V2 has significantly higher CPU usage (up to 70%) as compared to Monitoring V1. To improve performance and achieve similar results as in Monitoring V1, turn off the Prometheus adapter. 
+:::note
+
+On an idle cluster, Monitoring V2 has significantly higher CPU usage (up to 70%) as compared to Monitoring V1. To improve performance and achieve similar results as in Monitoring V1, turn off the Prometheus adapter. 
+
+:::
 
 # Prometheus Configuration
 

docs/en/monitoring-alerting/configuration/receiver/receiver.md

@@ -6,7 +6,11 @@ weight: 1
 
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.
 
-> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../how-monitoring-works/#3-how-alertmanager-works)
+:::note
+
+This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../how-monitoring-works/#3-how-alertmanager-works)
+
+:::
 
 - [Creating Receivers in the Rancher UI](#creating-receivers-in-the-rancher-ui)
 - [Receiver Configuration](#receiver-configuration)
@@ -25,10 +29,12 @@ The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configurati
 
 # Creating Receivers in the Rancher UI
 
-> **Prerequisites:**
->
->- The monitoring application needs to be installed.
->- If you configured monitoring with an existing Alertmanager Secret, it must have a format that is supported by Rancher's UI. Otherwise you will only be able to make changes based on modifying the Alertmanager Secret directly. Note: We are continuing to make enhancements to what kinds of Alertmanager Configurations we can support using the Routes and Receivers UI, so please [file an issue](https://github.com/rancher/rancher/issues/new) if you have a request for a feature enhancement.
+:::note Prerequisites:
+
+- The monitoring application needs to be installed.
+- If you configured monitoring with an existing Alertmanager Secret, it must have a format that is supported by Rancher's UI. Otherwise you will only be able to make changes based on modifying the Alertmanager Secret directly. Note: We are continuing to make enhancements to what kinds of Alertmanager Configurations we can support using the Routes and Receivers UI, so please [file an issue](https://github.com/rancher/rancher/issues/new) if you have a request for a feature enhancement.
+
+:::
 
 To create notification receivers in the Rancher UI,
 

docs/en/monitoring-alerting/configuration/route/route.md

@@ -10,7 +10,11 @@ When a Route is changed, the Prometheus Operator regenerates the Alertmanager cu
 
 For more information about configuring routes, refer to the [official Alertmanager documentation.](https://www.prometheus.io/docs/alerting/latest/configuration/#route)
 
-> This section assumes familiarity with how monitoring components work together. For more information, see [this section.]({{<baseurl>}}/rancher/v2.6/en/monitoring-alerting/how-monitoring-works)
+:::note
+
+This section assumes familiarity with how monitoring components work together. For more information, see [this section.]({{<baseurl>}}/rancher/v2.6/en/monitoring-alerting/how-monitoring-works)
+
+:::
 
 - [Route Restrictions](#route-restrictions)
 - [Route Configuration](#route-configuration)
@@ -45,7 +49,11 @@ The route needs to refer to a [receiver](#receiver-configuration) that has alrea
 {{% tabs %}}
 {{% tab "Rancher v2.6.5+" %}}
 
-> **Note** As of Rancher v2.6.5 `Group By` now accepts a list of strings instead of key-value pairs. See the [upstream documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#route) for details.
+:::note
+
+As of Rancher v2.6.5, `Group By` now accepts a list of strings instead of key-value pairs. See the [upstream documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#route) for details.
+
+:::
 
 | Field |    Default | Description |
 |-------|--------------|---------|

docs/en/monitoring-alerting/configuration/servicemonitor-podmonitor/servicemonitor-podmonitor.md

@@ -10,7 +10,11 @@ These configuration objects declaratively specify the endpoints that Prometheus
 
 ServiceMonitors are more commonly used than PodMonitors, and we recommend them for most use cases.
 
-> This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../how-monitoring-works/)
+:::note
+
+This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../how-monitoring-works/)
+
+:::
 
 ### ServiceMonitors