docs: Fix mangled admonition block in alerting/recording rule docs (#…

…12733)

(cherry picked from commit c825dba)

docs/sources/alert/_index.md

@@ -203,8 +203,8 @@ Another great use case is alerting on high cardinality sources. These are things
 Creating these alerts in LogQL is attractive because these metrics can be extracted at _query time_, meaning we don't suffer the cardinality explosion in our metrics store.
 
 {{% admonition type="note" %}}
-As an example, we can use LogQL v2 to help Loki to monitor _itself_, alerting us when specific tenants have queries that take longer than 10s to complete! To do so, we'd use the following query: `sum by (org_id) (rate({job="loki-prod/query-frontend"} |= "metrics.go" | logfmt | duration > 10s [1m])
-{{% /admonition %}}`.
+As an example, we can use LogQL v2 to help Loki to monitor _itself_, alerting us when specific tenants have queries that take longer than 10s to complete! To do so, we'd use the following query: `sum by (org_id) (rate({job="loki-prod/query-frontend"} |= "metrics.go" | logfmt | duration > 10s [1m])`.
+{{% /admonition %}}
 
 ## Interacting with the Ruler