From fe4c1da340d04228d38257b46bfa974a014c7918 Mon Sep 17 00:00:00 2001
From: Pepe Cano <825430+ppcano@users.noreply.github.com>
Date: Mon, 31 Mar 2025 11:46:22 +0200
Subject: [PATCH] [release-11.6.1] docs(alerting): stale alert instance minor
 change (#103031)

docs(alerting): stale alert instance minor change (#103030)

docs(alerting): stale alert instance minor text change

(cherry picked from commit 37c6c519c8b7d02b575735c54f5f2e639056fdff)
---
 .../fundamentals/alert-rule-evaluation/state-and-health.md      | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/sources/alerting/fundamentals/alert-rule-evaluation/state-and-health.md b/docs/sources/alerting/fundamentals/alert-rule-evaluation/state-and-health.md
index 70a20c8b6ee..a0785c18553 100644
--- a/docs/sources/alerting/fundamentals/alert-rule-evaluation/state-and-health.md
+++ b/docs/sources/alerting/fundamentals/alert-rule-evaluation/state-and-health.md
@@ -72,6 +72,8 @@ The `No Data` state occurs when the alert rule query runs successfully but retur
 
 An alert instance is considered stale if the query returns data but its dimension or series has disappeared for two evaluation intervals. In this case, the alert instance transitions to the **Normal (MissingSeries)** state as resolved, and is then evicted.
 
+The process for handling stale alert instances is as follows:
+
 1. The alert rule runs and returns data for some label sets.
 
 1. An alert instance that previously existed is now missing.