indent

Author: nastasha-solomon

solutions/observability/incident-management/view-alerts.md

@@ -89,9 +89,8 @@ Alert flapping is turned on by default. You can modify the criteria for changing
 
     A flapping alert changes to recovered when the rule's conditions are unmet for a specific number of consecutive runs. This number is determined by the **Alert status change threshold** setting, which you can configure under the **Alert flapping detection** settings.
 
-For instance, if the threshold is set so an alert must change status at least 6 times in the last 10 runs to be considered flapping, then for the flapping alert to recover, the rule's conditions must remain unmet for 6 consecutive runs. If the rule's conditions are met at any point during this recovery period, the count of consecutive unmet runs will reset, requiring the alert to remain unmet for an additional 6 consecutive runs to finally be reported as recovered.
+    For instance, if the threshold is set so an alert must change status at least 6 times in the last 10 runs to be considered flapping, then for the flapping alert to recover, the rule's conditions must remain unmet for 6 consecutive runs. If the rule's conditions are met at any point during this recovery period, the count of consecutive unmet runs will reset, requiring the alert to remain unmet for an additional 6 consecutive runs to finally be reported as recovered.
 
-    
     Once a flapping alert is recovered, it cannot be changed to flapping again. Only new alerts with repeated status changes are candidates for the flapping status. 
 
 `untracked`