Typos

Author: rcastley

content/en/s4r/3-quick-tour/6-infrastructure-home/2-infrastructure-home.md

@@ -24,7 +24,7 @@ Using the Infrastructure pane, we can select the infrastructure/technology we ar
 * You will see one or more representations of a Kubernetes Cluster.
 * Even if there is only one visible, still filter & select the Workshop Cluster, by clicking on the {{% button style="gray" %}}Add filters{{% /button %}} button. Type `k8s.cluster.name` and search for the workshop name. This time the naming convention is **[NAME OF WORKSHOP]-k3s-cluster**. Click on {{% button style="blue" %}}Apply Filters{{% /button %}} when selected.
 
-![cluster](../images/k8s-cluster.png)
+  ![cluster](../images/k8s-cluster.png)
 
 * The Kubernetes Navigator uses color to indicate health. As you can see there two pods or services that are unhealthy and in a Failed state (**1**). The rest are healthy and running. This is not uncommon in shared Kubernetes environments, so we replicated that for the workshop.
 * Note the tiles to the side, under **Nodes dependencies** (**2**), specifically the MySQL and Redis tiles. These are the two databases used by our e-commerce application.
@@ -41,7 +41,7 @@ A good example of this is the Kubernetes Navigator showing you **Related Content
 
 * Find and click on the **Redis** tile. This will take you to the list of the *Redis* Datastore services. Select the one running on your cluster, the naming convention is **redis-[NAME OF WORKSHOP]**.
 
- ![redis](../images/redis-2.png)
+  ![redis](../images/redis-2.png)
 
 * This will bring you to the Redis Datastore Navigator. This navigator will show charts with metric data from the active *Redis* cluster from our e-commerce site.
 {{< tabs >}}

content/en/s4r/8-synthetics/1-synthetics-dashboard.md

@@ -12,7 +12,7 @@ During our investigation in the RUM section, we found there was an issue with th
 * In the **Search** box enter **Workshop Browser Test** and select the test for your workshop (your instructor will advise as to which one to select).
 * Under **Performance KPIs** set the Time Picker to **-30m** and hit enter.
 * Click on **Location** and from the drop-down and select **Page**. The next filter will be populated with the pages that are part of the test.
-* Click on **Duration** and deselect **Duration** and then select **First byte time**.
+* Click on **Run Duration** and deselect **Run Duration** and then select **First byte time**.
   ![Transaction Filter](../images/synthetics-transaction-filter.png)
 * Look at the legend and note the color of **First byte time - Page 4**.
 * Select the highest data point for **First byte time - Page 4**.

content/en/s4r/8-synthetics/3-synthetics-to-apm.md

@@ -10,7 +10,7 @@ We now should have a view similar to the one below.
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * In the waterfall find an entry that starts with **POST checkout**.
-* Click on the **>** button in front of it to drop open the metadata section. Observe the metadata that is collected, and note the **Server-Timing**** header. This header is what allows us to correlate the test run to a back-end trace.
+* Click on the **>** button in front of it to drop open the metadata section. Observe the metadata that is collected, and note the **Server-Timing** header. This header is what allows us to correlate the test run to a back-end trace.
 * Click on the blue {{% icon icon="link" %}} **APM** link on the **POST checkout** line in the waterfall.
 {{% /notice %}}