From efa44a5c63dd2d769e36a88b6de0b5feafba10dc Mon Sep 17 00:00:00 2001 From: Achim Staebler Date: Thu, 18 Jul 2024 09:53:48 +0200 Subject: [PATCH] fix typo --- .../7-alerting-dashboards-slos/3-slos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/3-slos.md b/content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/3-slos.md index a5cb01e3dc..ef62f78bbf 100644 --- a/content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/3-slos.md +++ b/content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/3-slos.md @@ -7,7 +7,7 @@ time: 10 minutes We can now use the created Monitoring MetricSet together with Service Level Objectives a similar way we used them with dashboards and detectors/alerts before. For that we want to be clear about some key concepts: -## Key Conzepts of Service Level Monitoring +## Key Concepts of Service Level Monitoring ([skip](#creating-a-new-service-level-objective) if you know this)