From c075576f3ac77b4a7d5c450904ad53966b458e3c Mon Sep 17 00:00:00 2001
From: Amal <56926487+amalkurup89@users.noreply.github.com>
Date: Wed, 13 May 2020 19:16:27 +0530
Subject: [PATCH] Minor correction in documentation (#24472)

---
 docs/sources/alerting/rules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/alerting/rules.md b/docs/sources/alerting/rules.md
index b7da2f91170..4a07a208f0b 100755
--- a/docs/sources/alerting/rules.md
+++ b/docs/sources/alerting/rules.md
@@ -86,7 +86,7 @@ What Grafana does not do currently is track alert rule state **per series**. Thi
 in the scenario below.
 
 - Alert condition with query that returns 2 series: **server1** and **server2**
-- **server1** series cause the alert rule to fire and switch to state `Alerting`
+- **server1** series causes the alert rule to fire and switch to state `Alerting`
 - Notifications are sent out with message:  _load peaking (server1)_
 - In a subsequence evaluation of the same alert rule the **server2** series also cause the alert rule to fire
 - No new notifications are sent as the alert rule is already in state `Alerting`.