From 5a795d406f50c62726f1b08f19b1bf29636563ae Mon Sep 17 00:00:00 2001
From: antonio <45235678+tonypowa@users.noreply.github.com>
Date: Fri, 21 Jun 2024 09:36:11 +0200
Subject: [PATCH] Update
 docs/sources/tutorials/alerting-get-started-pt2/index.md

Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com>
---
 docs/sources/tutorials/alerting-get-started-pt2/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/tutorials/alerting-get-started-pt2/index.md b/docs/sources/tutorials/alerting-get-started-pt2/index.md
index c7dbeeb8907..891238a8e25 100644
--- a/docs/sources/tutorials/alerting-get-started-pt2/index.md
+++ b/docs/sources/tutorials/alerting-get-started-pt2/index.md
@@ -41,7 +41,7 @@ If the query returns more than one time-series, each time-series represents a di
 
 {{< figure src="/media/docs/alerting/get-started-digram-instance-grey.png" max-width="1200px" caption="Alert Instances in the Context of an Alert Rule" >}}
 
-In this scenario, each time-series is evaluated independently against the alert rule. It results in the creation of an alert instance for each time-series. The time-series corresponding to the desktop page views meets the threshold and, therefore, results in an alert instance in **Firing** state for which an alert notification will be sent. The mobile alert instance state remains **Normal**.
+In this scenario, each time-series is evaluated independently against the alert rule. It results in the creation of an alert instance for each time-series. The time-series corresponding to the desktop page views meets the threshold and, therefore, results in an alert instance in **Firing** state for which an alert notification is sent. The mobile alert instance state remains **Normal**.
 
 ## Notification policies