Minor fixes to text #357

Author: rcastley

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/2-gateway/2-2-configure-agent.md

@@ -9,7 +9,7 @@ weight: 2
 **Add the `otlphttp` exporter**: The [**OTLP/HTTP Exporter**](https://docs.splunk.com/observability/en/gdi/opentelemetry/components/otlphttp-exporter.html) is used to send data from the agent to the gateway using the **OTLP/HTTP** protocol.
 
 1. Switch to your **Agent terminal** window.
-2. Validate that `gateway-logs.out`, `gateway-metrics.out`, and `gateway-traces.out` files are present in the directory.
+2. Validate that the newly generated `gateway-logs.out`, `gateway-metrics.out`, and `gateway-traces.out` are present in the directory.
 3. Open the `agent.yaml` file in your editor.
 4. Add the `otlphttp` exporter configuration to the `exporters:` section:
 

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/2-gateway/_index.md

@@ -103,6 +103,9 @@ service:                          # Service configuration
       - file/logs
 ```
 
+> [!NOTE]
+> When the `gateway` is started it will generate three files: `gateway-traces.out`, `gateway-metrics.out`, and `gateway-logs.out`. These files will eventually contain the telemetry data received by the gateway.
+
 ```text { title="Updated Directory Structure" }
 .
 ├── agent.yaml

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/8-routing-data/8-2-pipelines.md

@@ -23,36 +23,36 @@ weight: 2
 
 **Add both the `standard` and `security` traces pipelines**:
 
-1. **Add the Standard pipeline**: This pipeline processes all spans that do not match the routing rule.  
-This pipeline is using `routing` as its receiver. Place it below the existing `traces:` pipeline, keeping its configuration unchanged for now:
+1. **Configure the Security pipeline**: This pipeline will handle all spans that match the routing rule for `security`.
+This uses `routing` as its receiver. Place it below the existing `traces:` pipeline:
 
     ```yaml
-        traces/standard:              # Default pipeline for unmatched spans
+        traces/security:              # New Security Traces/Spans Pipeline
           receivers: 
           - routing                   # Receive data from the routing connector
           processors:
           - memory_limiter            # Memory Limiter Processor
           - resource/add_mode         # Adds collector mode metadata
           - batch
           exporters:
-          - debug                     # Debug exporter
-          - file/traces/standard      # File exporter for unmatched spans
+          - debug                     # Debug Exporter 
+          - file/traces/security      # File Exporter for spans matching rule
     ```
 
-2. **Configure the Security pipeline**: This pipeline will handle all spans that match the routing rule.  
-This also uses `routing` as its receiver. Add this below the Standard one:
+2. **Add the Standard pipeline**: This pipeline processes all spans that do not match the routing rule.
+This pipeline is also using `routing` as its receiver. Add this below the `traces/security` one:
 
     ```yaml
-        traces/security:              # New Security Traces/Spans Pipeline
+        traces/standard:              # Default pipeline for unmatched spans
           receivers: 
           - routing                   # Receive data from the routing connector
           processors:
           - memory_limiter            # Memory Limiter Processor
           - resource/add_mode         # Adds collector mode metadata
           - batch
           exporters:
-          - debug                     # Debug Exporter 
-          - file/traces/security      # File Exporter for spans matching rule
+          - debug                     # Debug exporter
+          - file/traces/standard      # File exporter for unmatched spans
     ```
 
 {{% /notice %}}