fix whitespace

content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/2-alerting.md

@@ -19,7 +19,7 @@ Let's call the detector `Latency by Credit Score Category`.  Set the environment
 
 ![Create New Detector](../../images/create_new_detector.png)
 
-As an alert condition instead of "**Static threshold**" we want to select "**Sudden Change**" to make the example more vivid. 
+As an alert condition instead of "**Static threshold**" we want to select "**Sudden Change**" to make the example more vivid.
 
 ![Alert Condition: Sudden Change](../../images/alert_condition_suddenchange.png)
 

content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/3-slos.md

@@ -5,7 +5,7 @@ weight: 3
 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: 
+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
 
@@ -21,34 +21,34 @@ We can now use the created Monitoring MetricSet together with Service Level Obje
 
 ## Creating a new Service Level Objective
 
-There is an easy to follow wizard to create a new Service Level Objective (SLO). In the left navigation just follow the link "**Detectors & SLOs**". From there select the third tab "**SLOs**" and click the blue button to the right that says "**Create SLO**". 
+There is an easy to follow wizard to create a new Service Level Objective (SLO). In the left navigation just follow the link "**Detectors & SLOs**". From there select the third tab "**SLOs**" and click the blue button to the right that says "**Create SLO**".
 
 ![Create new SLO](../../images/slo_0_create.png)
 
 The wizard guides you through some easy steps. And if everything during the previous steps worked out, you will have no problems here. ;)
 
-In our case we want to use `Service & endpoint` as our **Metric type** instead of `Custom metric`. We filter the **Environment** down to the environment that we are using during this workshop (i.e. `tagging-workshop-yourname`) and select the `creditcheckservice` from the **Service and endpoint** list. Our **Indicator type** for this workshop will be `Request latency` and not `Request success`. 
+In our case we want to use `Service & endpoint` as our **Metric type** instead of `Custom metric`. We filter the **Environment** down to the environment that we are using during this workshop (i.e. `tagging-workshop-yourname`) and select the `creditcheckservice` from the **Service and endpoint** list. Our **Indicator type** for this workshop will be `Request latency` and not `Request success`.
 
 Now we can select our **Filters**. Since we are using the `Request latency` as the **Indicator type** and that is a metric of the APM Service, we can filter on `credit.score.category`. Feel free to try out what happens, when you set the **Indicator type** to `Request success`.
 
 Today we are only interested in our `exceptional` credit scores. So please select that as the filter.
 
 ![Choose Service or Metric for SLO](../../images/slo_1_choose.png)
 
-In the next step we define the objective we want to reach. For the `Request latency` type, we define the **Target (%)**, the **Latency (ms)** and the **Compliance Window**. Please set these to `99`, `100` and `Last 7 days`. This will give us a good idea what we are achieving already. 
+In the next step we define the objective we want to reach. For the `Request latency` type, we define the **Target (%)**, the **Latency (ms)** and the **Compliance Window**. Please set these to `99`, `100` and `Last 7 days`. This will give us a good idea what we are achieving already.
 
 Here we will already be in shock or play around with the numbers to make it not so scary. Feel free to play around with the numbers to see how well we achieve the objective and how much we have left to burn.
 
 ![Define Objective for SLO](../../images/slo_2_define_objective.png)
 
-The third step gives us the chance to alert (aka annoy) people who should be aware about these SLOs to initiate countermeasures. These "people" can also be mechanism like ITSM systems or webhooks to initiate automatic remediation steps. 
+The third step gives us the chance to alert (aka annoy) people who should be aware about these SLOs to initiate countermeasures. These "people" can also be mechanism like ITSM systems or webhooks to initiate automatic remediation steps.
 
 Activate all categories you want to alert on and add recipients to the different alerts.
 
 ![Define Alerting for SLO](../../images/slo_3_define_alerting.png)
 
-The next step is only the naming for this SLO. Have your own naming convention ready for this. In our case we would just name it `creditchceckservice:score:exceptional:YOURNAME` and click the **Create**-button **BUT** you can also **just cancel the wizard** by clicking anything in the left navigation and confirming to **Discard changes**. 
+The next step is only the naming for this SLO. Have your own naming convention ready for this. In our case we would just name it `creditchceckservice:score:exceptional:YOURNAME` and click the **Create**-button **BUT** you can also **just cancel the wizard** by clicking anything in the left navigation and confirming to **Discard changes**.
 
 ![Name and Save the SLO](../../images/slo_4_name_and_save.png)
 
-And with that we have (*nearly*) successfully created an SLO including the alerting in case we might miss or goals. 
+And with that we have (*nearly*) successfully created an SLO including the alerting in case we might miss or goals.

content/en/scenarios/understand_impact_of_changes/7-alerting-dashboards-slos/_index.md

@@ -22,7 +22,7 @@ Let's navigate to **Settings** -> **APM MetricSets**, and click the edit button
 
 ![edit APM MetricSet](../images/edit_apm_metricset.png)
 
-Check the box beside **Also create Monitoring MetricSet** then click **Start Analysis** 
+Check the box beside **Also create Monitoring MetricSet** then click **Start Analysis**
 
 ![Monitoring MetricSet](../images/monitoring_metricset.png)
 
@@ -34,4 +34,4 @@ The `credit.score.category` tag appears again as a **Pending MetricSet**. After
 
 This mechanism creates a new dimension from the tag on a bunch of metrics that can be used to filter these metrics based on the values of that new dimension. **Important**: To differentiate between the original and the copy, the dots in the tag name are replaced by underscores for the new dimension. With that the metrics become a dimension named `credit_score_category` and not `credit.score.category`.
 
-Next, let's explore how we can use this **Monitoring MetricSet**.
+Next, let's explore how we can use this **Monitoring MetricSet**.