Minor edits

Author: rcastley

content/en/conf/1-advanced-collector/3-dropping-spans/3-2-test-filter.md

@@ -20,7 +20,7 @@ To test your configuration, you'll need to generate some trace data that include
 ../otelcol --config ./agent.yaml
 ```
 
-**Start the Loadgen**: In the **Loadgen terminal** window run the `loadgen` with the flag to also send `healthz` spans along with base spans:
+**Start the Loadgen**: In the **Loadgen terminal** window, execute the following command to start the load generator with health check spans enabled:
 
 ```bash
 ../loadgen -health -count 5
@@ -77,7 +77,7 @@ jq -c '.resourceSpans[].scopeSpans[].spans[] | "Span \(input_line_number) found
 {{% tabs %}}
 {{% tab title="Check spans in gateway-traces.out" %}}
 
-```bash { title="Check spans in gateway-traces.out" }
+```bash
 jq -c '.resourceSpans[].scopeSpans[].spans[] | "Span \(input_line_number) found with name \(.name)"' ./gateway-traces.out
 ```
 

content/en/conf/1-advanced-collector/5-transform-data/5-1-configuration.md

@@ -5,7 +5,7 @@ weight: 1
 ---
 
 {{% notice title="Exercise" style="green" icon="running" %}}
-**Add a `transform` processor**: Switch to your **Agent terminal** window and edit the `agent.yaml` and add the following `transform` processor:
+**Add a `transform` processor**: Switch to your **Gateway terminal** window and edit the `gateway.yaml` and add the following `transform` processor:
 
 ```yaml
   transform/logs:                      # Processor Type/Name
@@ -53,34 +53,34 @@ This step is crucial because it ensures that all relevant fields from the log bo
 - **Map Severity Text**: Assigns severity_text from the log’s level attribute.
 - **Assign Severity Numbers**: Converts severity levels into standardized numerical values.
 
-You should have a **single** `transform` processor containing two context blocks: one whose context is for `resource` and one whose context is for `log`.
+> [!IMPORTANT]
+> You should have a **single** `transform` processor containing two context blocks: one whose context is for `resource` and one whose context is for `log`.
 
 This configuration ensures that log severity is correctly extracted, standardized, and structured for efficient processing.
 
 {{% notice title="Tip" style="primary" icon="lightbulb" %}}
 This method of mapping all JSON fields to top-level attributes should only be used for **testing and debugging OTTL**. It will result in high cardinality in a production scenario.
 {{% /notice %}}
 
-**Update the `logs` pipeline**: Add the `transform/logs:` processor into the `logs:` pipeline:
+**Update the `logs` pipeline**: Add the `transform/logs:` processor into the `logs:` pipeline so your configuration looks like this:
 
 ```yaml
-    logs:
+    logs:                         # Logs pipeline
       receivers:
-      - otlp
-      - filelog/quotes
-      processors:
+      - otlp                      # OTLP receiver
+      processors:                 # Processors for logs
       - memory_limiter
-      - resourcedetection
       - resource/add_mode
-      - transform/logs                 # Transform logs processor
+      - transform/logs
       - batch
       exporters:
-      - debug
-      - otlphttp
+      - debug                     # Debug exporter
+      - file/logs
 ```
 
 {{% /notice %}}
 
+<!--
 Validate the agent configuration using [**https://otelbin.io**](https://otelbin.io/). For reference, the `logs:` section of your pipelines will look similar to this:
 
 ```mermaid
@@ -101,18 +101,19 @@ graph LR
     subgraph " "
       subgraph subID1[**Logs**]
       direction LR
-      REC1 --> PRO1
-      REC2 --> PRO1
-      PRO1 --> PRO2
-      PRO2 --> PRO3
-      PRO3 --> PRO4
-      PRO4 --> PRO5
-      PRO5 --> EXP2
-      PRO5 --> EXP1
+      REC1 -- > PRO1
+      REC2 -- > PRO1
+      PRO1 -- > PRO2
+      PRO2 -- > PRO3
+      PRO3 -- > PRO4
+      PRO4 -- > PRO5
+      PRO5 -- > EXP2
+      PRO5 -- > EXP1
       end
     end
 classDef receiver,exporter fill:#8b5cf6,stroke:#333,stroke-width:1px,color:#fff;
 classDef processor fill:#6366f1,stroke:#333,stroke-width:1px,color:#fff;
 classDef con-receive,con-export fill:#45c175,stroke:#333,stroke-width:1px,color:#fff;
 classDef sub-logs stroke:#34d399,stroke-width:1px, color:#34d399,stroke-dasharray: 3 3;
 ```
+-->

content/en/conf/1-advanced-collector/5-transform-data/5-2-setup.md

@@ -18,10 +18,7 @@ weight: 2
 ../otelcol --config=agent.yaml
 ```
 
-**Start the Load Generator**: Open the **Loadgen terminal** window and run the `loadgen`.
-
-> [!IMPORTANT]
-> To ensure the logs are structured in JSON format, include the `-json` flag when starting the script.
+**Start the Load Generator**: In the **Loadgen terminal** window, execute the following command to start the load generator with **JSON enabled**:
 
 ```bash { title="Log Generator" }
 ../loadgen -logs -json -count 5

content/en/conf/1-advanced-collector/5-transform-data/5-3-test-transform.md

@@ -10,14 +10,14 @@ This test verifies that the `com.splunk/source` and `os.type` metadata have been
    - `SeverityText` and `SeverityNumber` are set on the `LogRecord`.  
 2. JSON fields from the log body are promoted to log `attributes`.  
 
-This ensures proper metadata filtering, severity mapping, and structured log enrichment before export.
+This ensures proper metadata filtering, severity mapping, and structured log enrichment before exporting.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 **Check the debug output**: For both the **Agent** and **Gateway** confirm that `com.splunk/source` and `os.type` have been removed:
 
 {{% tabs %}}
-{{% tab title="New Debug Output" %}}
+{{% tab title="Gateway Debug Output" %}}
 
   ```text
 Resource attributes:
@@ -27,7 +27,7 @@ Resource attributes:
   ```
 
 {{% /tab %}}
-{{% tab title="Original Debug Output" %}}
+{{% tab title="Agent Debug Output" %}}
 
   ```text
 Resource attributes:
@@ -44,7 +44,7 @@ Resource attributes:
 For both the **Agent** and **Gateway** confirm that `SeverityText` and `SeverityNumber` in the `LogRecord` is now defined with the severity `level` from the log body. Confirm that the JSON fields from the body can be accessed as top-level log `Attributes`:
 
 {{% tabs %}}
-{{% tab title="New Debug Output" %}}
+{{% tab title="Gateway Debug Output" %}}
 
 ```text
 <snip>
@@ -61,7 +61,7 @@ Attributes:
 ```
 
 {{% /tab %}}
-{{% tab title="Original Debug Output" %}}
+{{% tab title="Agemt Debug Output" %}}
 
 ```text
 <snip>

content/en/conf/1-advanced-collector/5-transform-data/_index.md

@@ -13,22 +13,20 @@ In this exercise we’ll update `agent.yaml` to include a **Transform Processor*
 - **Parse** JSON structured log data into attributes.
 - **Set** log severity levels based on the log message body.
 
-You may have noticed that in previous logs, fields like `SeverityText` and `SeverityNumber` were undefined. This is typical of the `filelog` receiver. However, the severity is embedded within the log body:
+You may have noticed that in previous logs, fields like `SeverityText` and `SeverityNumber` were undefined. This is typical of the `filelog` receiver. However, the severity is embedded within the log body e.g.:
 
 ```text
-<snip>
 SeverityText: 
 SeverityNumber: Unspecified(0)
 Body: Str(2025-01-31 15:49:29 [WARN] - Do or do not, there is no try.)
-</snip>
 ```
 
 Logs often contain structured data encoded as JSON within the log body. Extracting these fields into attributes allows for better indexing, filtering, and querying. Instead of manually parsing JSON in downstream systems, OTTL enables automatic transformation at the telemetry pipeline level.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 > [!IMPORTANT]
-> **Change _ALL_ terminal windows to the `[WORKSHOP]/5-transform-data` directory and run the `clear` command.**
+> **Change _ALL_ terminal windows to the `5-transform-data` directory and run the `clear` command.**
 
 Copy `*.yaml` from the `4-sensitve-data` directory into `5-transform-data`. Your updated directory structure will now look like this: