[Doc] Document Grafana 12.4 changes

documentation/docs/alert/alert_rules.md

@@ -5,15 +5,16 @@ Alert rules describe the circumstances under which you want to be alerted. The e
 
 An alert rule consists of one or more queries and expressions, a condition, the frequency of evaluation, and the duration over which the condition is met. For example, you might configure an alert to fire and trigger a notification when MongoDB is down.
 
-An alert rule can be in three possible states:
+During evaluation, an alert rule moves through the following states:
 
-- Normal: Everything is working correctly and the conditions specified in the rule has not been met. This is the default state for newly created rules.
-- Pending: The conditions specified in the alert rule has been met, but for a time that is less than the configured duration.
-- Firing: Both the conditions and the duration specified in the alert rule have both been met.
+- **Normal**: Everything is working correctly, and the conditions specified in the rule have not been met. This is the default state for newly created rules.
+- **Pending**: The conditions specified in the alert rule have been met, but for less time than the configured duration.
+- **Firing**: Both the alert condition and the configured duration have been met.
+- **Recovering**: The alert conditions are no longer met, but the alert remains active until the metric is stable below the threshold. This prevents alerts from repeatedly flipping between **Firing** and **Normal** when metrics briefly cross a threshold.
 
 It takes at least one evaluation cycle for an alert rule to transition from one state to another (e.g., from `Normal` to `Pending`).
 
-## Alert rules templates
+## Alert rule templates
 
 PMM provides a set of Alert Rule templates with common events and expressions for alerting. These templates can be used as a basis for creating Alert Rules. You can also create your own templates if you need custom expressions.
 
@@ -109,7 +110,7 @@ If you want to create custom templates, you can test the MetricsQL expressions f
 To test expressions for custom templates:
 {.power-number}
 
-1. On the main menu in PMM, choose **Explore > Metrics**.
+1. On the main menu in PMM, choose **Explore > PromQL builder**.
 2. Enter your expression in the **Metrics** field and click **Run query**.
 
 For example, to check the CPU usage, Go to **Explore > PromQL builder** and run the query expression below:

documentation/docs/alert/silence_alerts.md

@@ -22,7 +22,7 @@ To create a new silence:
 4. Enter one or more matching labels by filling out the **Name** and **Value** fields. Matchers determine which rules the silence will apply to. Note that all labels specified here must be matched by an alert for it to be silenced.
 5. Enter any additional comments you would like about this silence - by default, the date the silence was created is placed here.
 6. Review the affected alert instances that will be silenced.
-7. Click **Save silece**.
+7. Click **Save silence**.
 
 For more information on working with silences, see [About alerting silences](https://grafana.com/docs/grafana/latest/alerting/manage-notifications/create-silence/) in the Grafana documentation.
 
@@ -32,7 +32,7 @@ For more information on working with silences, see [About alerting silences](htt
 
 After upgrading from the latest PMM 2 version to PMM 3, you will find all your alert templates under **Alerting > Alert rule templates**.
 
-If you have any templates available in the  `/srv/ia/templates` folder, make sure to transfer them to `/srv/alerting/templates` as PMM 3 will look for custom templates in this location.
+If you have any templates available in the `/srv/ia/templates` folder, make sure to transfer them to `/srv/alerting/templates` as PMM 3 will look for custom templates in this location.
 
 ### Template compatibility with other alerting tools
 

documentation/docs/release-notes/3.8.0.md

@@ -15,11 +15,19 @@ TODO
 
 ## ✨ Release highlights
 
-TODO
+### Grafana 12.4 upgrade
+
+PMM 3.8.0 ships with [Grafana 12.4](https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v12-0/), so you will notice several day-to-day monitoring improvements right away:
+
+**Faster monitoring dashboards**: Tables in PMM dashboards load, sort, and filter significantly faster. This affects dashboards across PMM including **Nodes Overview**, **MySQL User Details**, **PostgreSQL Instances Overview**, MongoDB, and HA/PXC **Cluster Summary**.
+
+**Less alert noise**: Alert rules now support a [**Recovering** state](https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v12-0/#recovering-state-for-alert-rules). This helps avoid repeated fire/resolved notifications when a metric keeps moving above and below an alert threshold, so you get fewer noisy alerts for spiky metrics like replication lag, query response time, and connection counts.
+
+**Custom dashboard compatibility**: All PMM-provided dashboards are unaffected by Grafana 12's Angular removal. If you have custom dashboards using legacy **Graph (old)** or **Table (old)** panels, Grafana will auto-migrate them on first load.
 
 ## 📦 Components upgrade
 
-TODO
+- **Grafana**: Upgraded to 12.4.
 
 ## 🔒 Security updates