qeoff changes on windows test

Author: hagen-p

content/en/ninja-workshops/10-advanced-otel/10-agent-setup/1-initialtest.md

@@ -14,11 +14,13 @@ To improve organization during the workshop, consider customizing your terminal
 
 Run the following command from the `1-agent` directory (ensure you’re using the correct OpenTelemetry Collector binary you downloaded):
 
-```text
+```sh
 ../otelcol --config=agent.yaml
 ```
 
-If everything is set up correctly, the first and last line of the output should read:
+In this workshop, we use `MacOS/Linux` commands by default. If you’re using Windows, adjust the commands as needed.
+
+If everything is set up correctly, the first and last lines of the output should display:
 
 ```text
 2025/01/13T12:43:51 settings.go:478: Set config to [agent.yaml]

content/en/ninja-workshops/10-advanced-otel/10-agent-setup/3-metadata.md

@@ -5,7 +5,7 @@ weight: 3
 ---
 ### Setup
 
-So far, we’ve essentially exported a direct copy of the trace sent through the OpenTelemetry Collector. Now, let’s enhance the base trace by adding metadata using `processors`. This additional information can be valuable for troubleshooting and for enabling features like Related Content.
+So far, we’ve essentially exported a direct copy of the `span` sent through the OpenTelemetry Collector. Now, let’s enhance the base `span` by adding metadata using `processors`. This additional information can be valuable for troubleshooting and for enabling features like `Related Content`.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 We will enhance the data flowing through our pipelines by making the following changes to the `agent.yaml`:  
@@ -122,6 +122,10 @@ A new `agent.out` file should be created:
 
 {{% /tab %}}
 
+{{% notice title="Tip" style="primary" icon="lightbulb" %}}
+Note: On `Windows`, attempting to read an open file can cause issues. To avoid this, make sure to stop the `agent` or the `gateway` before examining a file when instructed to do so.
+{{% /notice %}}
+
 Check the newly created `agent.out` file. You should see a line written for the trace.
 
 {{% tabs %}}

content/en/ninja-workshops/10-advanced-otel/20-gateway-setup/1-gateway-test.md

@@ -41,11 +41,11 @@ Open the `agent.yaml` we copied earlier in your editor, and configure a `otlphtt
 
 - **Add a batch processor to the agent**: since the agent can send data from different sources, and benefit from retries, adding a Batch processor is useful too:
 
-```yaml
+  ```yaml
     batch:                     # Processor Type
     # Array of metadata keys to batch data by
       metadata_keys: [X-SF-Token] 
-```
+  ```
 
 - **Update Pipelines**: replace the `file:` exporter with the `otlphttp` exporter in the `traces`, `metrics`, and `logs` pipelines.
 

content/en/ninja-workshops/10-advanced-otel/80-routing/_index.md

@@ -29,7 +29,6 @@ WORKSHOP
 │   ├── gateway.yaml
 │   ├── log-gen.sh (or .ps1)
 │   ├── health.json
-│   ├── data.json
 │   └── trace.json
 └── otelcol
 ```
@@ -131,10 +130,9 @@ Keep in mind that any existing processors have been removed from this pipeline.
 {{% /notice %}}
 
 - **Create a trace for different Environments**
+To test your configuration, you’ll need to generate some trace data that includes a span named
 
-Create a copy of your trace.json and name it security.json
-
-open an editor and update the RespourceSpan atttribute deployment.environem4etn and set it to "security_applications". ( You can change the service.name attribute  as well)
+Copy the following JSON and save to a file called security.json in the 8-routing directory:
 
 {{% tabs %}}
 {{% tab title="Compacted JSON" %}}