Alerting docs: vale fixes (#86972)

* Alerting docs: vale fixes

* ran prettier

docs/sources/alerting/fundamentals/_index.md

@@ -35,23 +35,23 @@ The following concepts are key to your understanding of how Grafana Alerting wor
 
 ### Alert rules
 
-An [alert rule][alert-rules] consists of one or more queries and expressions that select the data you want to measure. It also contains a condition, which is the threshold that an alert rule must meet or exceed in order to fire.
+An [alert rule][alert-rules] consists of one or more queries and expressions that select the data you want to measure. It also contains a condition, which is the threshold that an alert rule must meet or exceed to fire.
 
 Add labels to uniquely identify your alert rule and configure alert routing. Labels link alert rules to notification policies, so you can easily manage which policy should handle which alerts and who gets notified.
 
-Once alert rules are created, they go through various states and transitions.
+After alert rules are created, they go through various states and transitions.
 
 ### Alert instances
 
-Each alert rule can produce multiple alert instances (also known as alerts) - one alert instance for each time series. This is exceptionally powerful as it allows us to observe multiple series in a single expression.
+Each alert rule can produce multiple alert instances (also known as alerts) - one alert instance for each time series. This is exceptionally powerful as it allows you to observe multiple series in a single expression.
 
 ```promql
 sum by(cpu) (
   rate(node_cpu_seconds_total{mode!="idle"}[1m])
 )
 ```
 
-A rule using the PromQL expression above creates as many alert instances as the amount of CPUs we are observing after the first evaluation, enabling a single rule to report the status of each CPU.
+A rule using the PromQL expression above creates as many alert instances as the amount of CPUs after the first evaluation, enabling a single rule to report the status of each CPU.
 
 {{< figure src="/static/img/docs/alerting/unified/multi-dimensional-alert.png" caption="Multiple alert instances from a single alert rule" >}}
 

docs/sources/alerting/fundamentals/alert-rules/organising-alerts.md

@@ -29,7 +29,7 @@ A namespace contains one or more groups. The rules within a group are run sequen
 
 ### Groups
 
-The rules within a group are run sequentially at a regular interval, meaning no rules will be evaluated at the same time and in order of appearance. The default interval is one (1) minute. You can rename Grafana Mimir or Loki rule namespaces and groups, and edit group evaluation intervals.
+The rules within a group are run sequentially at a regular interval, meaning no rules are evaluated at the same time and in order of appearance. The default interval is one (1) minute. You can rename Grafana Mimir or Loki rule namespaces and groups, and edit group evaluation intervals.
 
 > **Note** If you want rules to be evaluated concurrently and with different intervals, consider storing them in different groups.
 

docs/sources/alerting/fundamentals/alert-rules/rule-evaluation.md

@@ -42,7 +42,7 @@ In the pending period, you select the period in which an alert rule can be in br
 
 Imagine you have an alert rule evaluation interval set at every 30 seconds and the pending period to 90 seconds.
 
-Evaluation will occur as follows:
+Evaluation occurs as follows:
 
 [00:30] First evaluation - condition not met.
 
@@ -61,12 +61,12 @@ If the alert rule has a condition that needs to be in breach for a certain amoun
 
 - The rule stays in the "pending" state until the condition has been broken for the required amount of time - pending period.
 
-- Once the required time has passed, the rule goes into a "firing" state.
+- After the required time has passed, the rule goes into a "firing" state.
 
 - If the condition is no longer broken during the pending period, the rule goes back to its normal state.
 
 **Note:**
 
-If you want to skip the pending state, you can simply set the pending period to 0. This effectively skips the pending period and your alert rule will start firing as soon as the condition is breached.
+If you want to skip the pending state, you can simply set the pending period to 0. This effectively skips the pending period and your alert rule starts firing as soon as the condition is breached.
 
 When an alert rule fires, alert instances are produced, which are then sent to the Alertmanager.

docs/sources/alerting/fundamentals/alert-rules/state-and-health.md

@@ -35,10 +35,10 @@ An alert rule can be in either of the following states:
 | **Pending** | At least one alert instances returned by the evaluation engine is `Pending`.                       |
 | **Firing**  | At least one alert instances returned by the evaluation engine is `Firing`.                        |
 
-The alert rule state is determined by the “worst case” state of the alert instances produced. For example, if one alert instance is firing, the alert rule state will also be firing.
+The alert rule state is determined by the “worst case” state of the alert instances produced. For example, if one alert instance is firing, the alert rule state is also firing.
 
 {{% admonition type="note" %}}
-Alerts will transition first to `pending` and then `firing`, thus it will take at least two evaluation cycles before an alert is fired.
+Alerts transition first to `pending` and then `firing`, thus it takes at least two evaluation cycles before an alert is fired.
 {{% /admonition %}}
 
 ## Alert instance state
@@ -55,11 +55,11 @@ An alert instance can be in either of the following states:
 
 ## Keep last state
 
-An alert rule can be configured to keep the last state when a `NoData` and/or `Error` state is encountered. This will both prevent alerts from firing, and from resolving and re-firing. Just like normal evaluation, the alert rule will transition from `Pending` to `Firing` after the pending period has elapsed.
+An alert rule can be configured to keep the last state when a `NoData` and/or `Error` state is encountered. This both prevents alerts from firing, and from resolving and re-firing. Just like normal evaluation, the alert rule transitions from `Pending` to `Firing` after the pending period has elapsed.
 
 ## Alert rule health
 
-An alert rule can have one the following health statuses:
+An alert rule can have one of the following health statuses:
 
 | State                  | Description                                                                                              |
 | ---------------------- | -------------------------------------------------------------------------------------------------------- |
@@ -70,7 +70,7 @@ An alert rule can have one the following health statuses:
 
 ## Special alerts for `NoData` and `Error`
 
-When evaluation of an alert rule produces state `NoData` or `Error`, Grafana Alerting will generate alert instances that have the following additional labels:
+When evaluation of an alert rule produces state `NoData` or `Error`, Grafana Alerting generates alert instances that have the following additional labels:
 
 | Label              | Description                                                            |
 | ------------------ | ---------------------------------------------------------------------- |

docs/sources/alerting/fundamentals/notifications/_index.md

@@ -18,7 +18,7 @@ weight: 110
 
 # Notifications
 
-Choosing how, when, and where to send your alert notifications is an important part of setting up your alerting system. These decisions will have a direct impact on your ability to resolve issues quickly and not miss anything important.
+Choosing how, when, and where to send your alert notifications is an important part of setting up your alerting system. These decisions have a direct impact on your ability to resolve issues quickly and not miss anything important.
 
 As a first step, define your contact points; where to send your alert notifications to. A contact point is a set of one or more integrations that are used to deliver notifications. Add notification templates to contact points for reuse and consistent messaging in your notifications.
 
@@ -58,4 +58,4 @@ All notifications templates are written in [Go's templating language](https://pk
 
 ## Silences
 
-You can use silences to mute notifications from one or more firing rules. Silences do not stop alerts from firing or being resolved, or hide firing alerts in the user interface. A silence lasts as long as its duration which can be configured in minutes, hours, days, months or years.
+You can use silences to mute notifications from one or more firing rules. Silences do not stop alerts from firing or being resolved, or hide firing alerts in the user interface. A silence lasts as long as its duration, which can be configured in minutes, hours, days, months, or years.

docs/sources/alerting/fundamentals/notifications/alertmanager.md

@@ -26,15 +26,15 @@ Alertmanagers are visible from the drop-down menu on the Alerting Contact Points
 
 In Grafana, you can use the Cloud Alertmanager, Grafana Alertmanager, or an external Alertmanager. You can also run multiple Alertmanagers; your decision depends on your set up and where your alerts are being generated.
 
-- **Grafana Alertmanager** is an internal Alertmanager that is pre-configured and available for selection by default if you run Grafana on-premises or open-source.
+- **Grafana Alertmanager** is an internal Alertmanager that is pre-configured and available for selection by default if you run Grafana on-premises or open source.
 
   The Grafana Alertmanager can receive alerts from Grafana, but it cannot receive alerts from outside Grafana, for example, from Mimir or Loki. Note that inhibition rules are not supported.
 
 - **Cloud Alertmanager** runs in Grafana Cloud and it can receive alerts from Grafana, Mimir, and Loki.
 
 - **External Alertmanager** can receive all your Grafana, Loki, Mimir, and Prometheus alerts. External Alertmanagers can be configured and administered from within Grafana itself.
 
-Here are two examples of when you may want to [add your own external alertmanager][configure-alertmanager] and send your alerts there instead of the Grafana Alertmanager:
+Here are two examples of when you may want to [add your own external Alertmanager][configure-alertmanager] and send your alerts there instead of the Grafana Alertmanager:
 
 1. You may already have Alertmanagers on-premises in your own Cloud infrastructure that you have set up and still want to use, because you have other alert generators, such as Prometheus.
 

docs/sources/alerting/fundamentals/notifications/contact-points.md

@@ -24,7 +24,7 @@ weight: 112
 
 # Contact points
 
-Contact points contain the configuration for sending notifications. A contact point is a list of integrations, each of which sends a notification to a particular email address, service or URL. Contact points can have multiple integrations of the same kind, or a combination of integrations of different kinds. For example, a contact point could contain a Pagerduty integration; an email and Slack integration; or a Pagerduty integration, a Slack integration, and two email integrations. You can also configure a contact point with no integrations; in which case no notifications are sent.
+Contact points contain the configuration for sending notifications. A contact point is a list of integrations, each of which sends a notification to a particular email address, service, or URL. Contact points can have multiple integrations of the same kind, or a combination of integrations of different kinds. For example, a contact point could contain a Pagerduty integration; an email and Slack integration; or a Pagerduty integration, a Slack integration, and two email integrations. You can also configure a contact point with no integrations; in which case no notifications are sent.
 
 A contact point cannot send notifications until it has been added to a notification policy. A notification policy can only send alerts to one contact point, but a contact point can be added to a number of notification policies at the same time. When an alert matches a notification policy, the alert is sent to the contact point in that notification policy, which then sends a notification to each integration in its configuration.