Markdown Linting

Author: rcastley

content/en/s4r/03-apm.md

@@ -82,4 +82,4 @@ Now I’m starting to get a good picture of what’s going on. This checkout pro
 
 I’d like to look at the logs to see precisely what the error is.
 
-{{% /notice %}}
+{{% /notice %}}

content/en/s4r/15-logs-link.md

@@ -12,4 +12,4 @@ weight: 30
 We are federating logs across multiple Splunk instances and indexes, which can be extremely useful when I have logs in multiple places – on-prem or in the cloud.
 
 Let’s navigate to the linked logs.
-{{% /notice %}}
+{{% /notice %}}

content/en/s4r/16-logs.md

@@ -11,4 +11,4 @@ weight: 31
 {{% notice style="blue" title="Say" icon="user" %}}
 I can now see the log entries coming from this specific trace.
 
-{{% /notice %}}
+{{% /notice %}}

content/en/s4r/17-filter-logs.md

@@ -11,4 +11,4 @@ weight: 32
 {{% notice style="blue" title="Say" icon="user" %}}
 Log Observer gives me an easy way to aggregate and filter on the logs I need to. Here we are just filtering on the log entries that are errors.
 
-{{% /notice %}}
+{{% /notice %}}

content/en/s4r/19-synthetics.md

@@ -3,12 +3,12 @@ title: 19. Synthetics
 weight: 40
 ---
 
-## Use the Splunk Observability Suite to check the perfomance of your Website/API Endpoint 
-So far we have have tested the perfomance of our Website by visting and running manual testscenario's to see how our web site perfomed. 
+## Use the Splunk Observability Suite to check the perfomance of your Website/API Endpoint
 
-But what if we didn't have to wait for that, and could instead test the frontend whenever we want, in both production and pre-production? This is where Synthetics comes in. 
+So far we have have tested the perfomance of our Website by visting and running manual testscenario's to see how our web site perfomed.
+
+But what if we didn't have to wait for that, and could instead test the frontend whenever we want, in both production and pre-production? This is where Synthetics comes in.
 
 ![Synthetics overview](../images/SyntheticTests.png?width=50vw)
-<br>
 
 As part of this excersise we will clone an exsting Synthetic Test and  configure it to test against your website, and have it run automaticly. as part of this excercise we will also set up a detector that will will allow you to be automaticly informed/alerted if the perfomance of your webite is suboptimal.

content/en/s4r/20-browser-test.md

@@ -12,4 +12,4 @@ weight: 41
 Synthetics can test uptime and APIs, but in this example let's look at a browser test, where we are emulating real user behavior of shopping and checking out on the desktop site for my retail application.
 
 We see the details of this test run, what the front end looks like visually, as well as a waterfall of all requests broken down by URL. Because this is a Synthetic test, we can define the test frequency, device type, and locations, as well as the critical user transactions that we want to track.
-{{% /notice %}}
+{{% /notice %}}

content/en/s4r/21-test-failure.md

@@ -10,4 +10,4 @@ weight: 42
 
 {{% notice style="blue" title="Say" icon="user" %}}
 We see that this test run failed because it never got to confirm the Order ID. Looking at the requests in the checkout, we see a long POST request to checkout with an APM link. Familiar, right?
-{{% /notice %}}
+{{% /notice %}}

content/en/s4r/23-wrapup.md

@@ -14,11 +14,11 @@ This wraps up the Splunk for Rookies Workshop of the Splunk Observability Cloud.
 Today we didn’t even talk about the power of the rest of Splunk Observability Cloud, such as:
 
 * Infrastructure monitoring, which shows how our infrastructure is behaving -- hosts, kubernetes, and applications via Dashboards, Navigators and Detectors
-* More about Synthetics, which can simulate web and mobile traffic and report on application behavior and potential areas for improvement 
+* More about Synthetics, which can simulate web and mobile traffic and report on application behavior and potential areas for improvement.
 
 <!-- More information  can be found here:
 
 [API Test](https://docs.splunk.com/Observability/synthetics/api-test/api-test.html) and 
 [Uptime Test](https://docs.splunk.com/Observability/synthetics/uptime-test/uptime-test.html). -->
 
-{{% /notice %}}
+{{% /notice %}}