Skip to content

Commit 5445e47

Browse files
committed
docs(alerting): typo
1 parent 1f2b804 commit 5445e47

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/sources/alerting/rules.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ weight = 1
1818
{{< imgbox max-width="40%" img="/img/docs/v4/drag_handles_gif.gif" caption="Alerting overview" >}}
1919

2020
Alerting in Grafana allows you to attach rules to your graph panels. When you save the dashboard
21-
Grafana will extract the alert rules into a seperate alert rule storage and schedule them for evaluation.
21+
Grafana will extract the alert rules into a separate alert rule storage and schedule them for evaluation.
2222

2323
In the alert tab of the graph panel you can configure how often the alert rule should be evaluated
2424
and the conditions that need to be met for the alert to change state and trigger its
@@ -92,7 +92,7 @@ Error or timeout option | Description
9292
Alerting | Set alert rule state to `Alerting`
9393
Keep Last State | Keep the current alert rule state, what ever it is.
9494

95-
If you an unreliable time series store that where queries sometime timesout or fail randomly you can set this option
95+
If you an unreliable time series store that where queries sometime timeout or fail randomly you can set this option
9696
t `Keep Last State` to basically ignore them.
9797

9898
## Troubleshooting
@@ -104,7 +104,7 @@ to the point where you can see the raw data that was returned form your query.
104104

105105
Further troubleshooting can also be done by inspecting the grafana-server log. If it's not an error or for some reason
106106
the log does not say anything you can enable debug logging for some relevant components. This is done
107-
in grafana's ini config file.
107+
in Grafana's ini config file.
108108

109109
Example showing loggers that could be relevant when troubleshooting alerting.
110110

0 commit comments

Comments
 (0)