Various typo fixes and grammar improvements

Author: rcastley

content/en/s4r/6-apm/5-apm-trace-analyzer.md

@@ -14,10 +14,10 @@ In **Trace Analyzer** you can filter traces by any indexed/unindexed span tag. I
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * In the time picker select **Last 1 hour**.
-* Make sure **Sample Ratio** is set to `1:1` and **not** `1:10`.
+* Make sure the **Sample Ratio** is set to `1:1` and **not** `1:10`.
 * Click on **Group traces by** and select `version`.
 * Click on the ellipsis next to `v350.10` and click **Add to filter**.
-* Click **Add filters**, type in **orderId** and select **orderId** from the **Unindexed Tags** list.
+* Click on **Add filters**, type in **orderId** and select **orderId** from the **Unindexed Tags** list.
 * Paste in your **Order Confirmation ID** from when you went shopping earlier in the workshop and hit enter.
 
 ![Traces by Duration](../images/apm-trace-by-duration.png)

content/en/s4r/7-log-observer/1-log-filtering.md

@@ -3,9 +3,9 @@ title: 1. Log Filtering
 weight: 1
 ---
 
-Log Observer, or LO for short, can be used in multiple ways. In the quick tour, you used the LO **no-code interface** to search for specific entries in the logs. This section, however, assumes you have arrived in LO from a trace in APM using the **Related Content** link.
+**Log Observer (LO)**, can be used in multiple ways. In the quick tour, you used the LO **no-code interface** to search for specific entries in the logs. This section, however, assumes you have arrived in LO from a trace in APM using the **Related Content** link.
 
-The advantage of this is, as it was with the link between RUM & APM, that you are looking at your logs within the context of your previous actions.  In this case, the context is the time frame **(1)**,  which matches that of the trace and the filter **(2)** which is set to the **trace_id**.
+The advantage of this is, as it was with the link between RUM & APM, that you are looking at your logs within the context of your previous actions.  In this case, the context is the time frame (**1**),  which matches that of the trace and the filter (**2**) which is set to the **trace_id**.
 
 ![Trace Logs](../images/log-observer-trace-logs.png)
 
@@ -19,12 +19,9 @@ We need to focus on just the Error messages in the logs:
 
 * Click on the **Group By** drop-down box and use the filter to find **Severity**.
 * Once selected click the {{% button style="blue" %}}Apply{{% /button %}} button (notice that the chart legend changes to show debug, error and info).
-
   ![legend](../images/severity-logs.png)
-
 * Selecting just the error logs can be done by either clicking on the word error **(1)** in the legend, followed by selecting **Add to filter** or by adding `severity=error` directly in the filter box.
-* You could also add the service name, `sf_service=paymentservice`, to the filter if there are error lines for multiple services, but in our case, this is not really necessary.
-
+* You could also add the service name, `sf_service=paymentservice`, to the filter if there are error lines for multiple services, but in our case, this is not necessary.
   ![Error Logs](../images/log-observer-errors.png)
 
 {{% /notice %}}

content/en/s4r/7-log-observer/2-log-entry.md

@@ -5,31 +5,9 @@ weight: 2
 
 Before we look at a specific log line, let's quickly recap what we have done so far and why we are here based on the 3 pillars of Observability:
 
-{{< mermaid >}}
-
----
-title: The 3 Pillars of Observability
-
----
-
-%%{
-  init:{
-    "theme": "neutral",
-    "themeVariables": {
-      "lineColor": "#ffffff"
-    }
-  }
-}%%
-
-graph LR;
-    A["`_Metrics_
-    **Do I have a problem?**`"]
-    B["`_Traces_
-    **Where is the problem?**`"]
-    C["`_Logs_
-    **What is the problem?**`"]
-    A --> B --> C
-{{< /mermaid >}}
+| Metrics | Traces | Logs |
+|:-------:|:------:|:----:|
+| _**Do I have a problem?**_ | _**Where is the problem?**_ | _**What is the problem?**_ |
 
 * Using metrics we identified **we have a problem** with our application. This was obvious from the error rate in the Service Dashboards as it was higher than it should be.
 * Using traces and span tags we found **where the problem is**. The **paymentservice** comprises of two versions, `v350.9` and `v350.10`, and the error rate was **100%** for `v350.10`.

content/en/s4r/7-log-observer/3-log-timeline-chart.md

@@ -21,7 +21,7 @@ First, we will reduce the amount of information to just the columns we are inter
 * Click **Save** and select **Save to Dashboard**.
   ![save it](../images/save-query.png)
 * In the chart creation dialog box that appears, enter the **Chart name**, this will be the name of the chart on the dashboard. Use the following format: `Initials - Log Timeline Chart`
-* Ensure **Log Timeline** is selected as the **Chart Type**.
+* Ensure that **Log Timeline** is selected as the **Chart Type**.
   ![log timeline](../images/log-timeline.png?classes=left&width=25vw)
 * Click {{% button style="blue" %}}Select Dashboard{{% /button %}} and then click {{% button style="blue" %}}New Dashboard{{% /button %}} in the Dashboard Selection dialog box.
 * In the **New dashboard** dialog box, enter a name for the new dashboard (no need to enter a description). Use the following format: `Initials - Service Health Dashboard` and click {{% button style="blue" %}}Save{{% /button %}}

content/en/s4r/7-log-observer/_index.md

@@ -7,6 +7,12 @@ archetype: chapter
 
 {{% badge icon="clock" color="#ed0090" %}}20 minutes{{% /badge %}}
 
+{{% notice icon="user" style="orange" title="Persona" %}}
+
+Remaining in your **back-end developer** role, you need to inspect the logs from your application to determine the root cause of the issue.
+
+{{% /notice %}}
+
 Using the content related to the APM trace (logs) we will now use Splunk Log Observer to drill down further to understand exactly what the problem is.
 
 Related Content is a powerful feature that allows you to jump from one component to another and is available for **metrics**, **traces** and **logs**.