From 4f036ad4db0f45f242f563794d68cf43ab7f302d Mon Sep 17 00:00:00 2001 From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com> Date: Mon, 21 Feb 2022 18:48:35 +0100 Subject: [PATCH] Update mute-timings.md (#45679) (#45693) cleaned up feature description (there were some leftovers from when the text was last edited) (cherry picked from commit 34ae28846edd1011b8ebbfaea39cb410561eed9a) Co-authored-by: juschm --- .../alerting/unified-alerting/notifications/mute-timings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/alerting/unified-alerting/notifications/mute-timings.md b/docs/sources/alerting/unified-alerting/notifications/mute-timings.md index a41915e1660..254a9a0d26b 100644 --- a/docs/sources/alerting/unified-alerting/notifications/mute-timings.md +++ b/docs/sources/alerting/unified-alerting/notifications/mute-timings.md @@ -7,7 +7,7 @@ weight = 450 # Mute timings -A mute timing is a recurring interval of time when no new notifications for a policy are generated or sent. are sent for a policy. Use them to prevent alerts from firing a specific and reoccurring period, for example, a regular maintenance period. +A mute timing is a recurring interval of time when no new notifications for a policy are generated or sent. Use them to prevent alerts from firing a specific and reoccurring period, for example, a regular maintenance period. Similar to silences, mute timings do not prevent alert rules from being evaluated, nor do they stop alert instances from being shown in the user interface. They only prevent notifications from being created.