Minor edits

Author: rcastley

content/en/conf/1-advanced-collector/3-dropping-spans/3-1-configuration.md

@@ -12,11 +12,11 @@ Switch to your **Gateway terminal** window and open the `gateway.yaml` file. Upd
    Configure the gateway to exclude spans with the name `/_healthz`. The `error_mode: ignore` directive ensures that any errors encountered during filtering are ignored, allowing the pipeline to continue running smoothly. The `traces` section defines the filtering rules, specifically targeting spans named `/_healthz` for exclusion.
 
    ```yaml
-   filter/health:                       # Defines a filter processor
-     error_mode: ignore                 # Ignore errors
-     traces:                            # Filtering rules for traces
-       span:                            # Exclude spans named "/_healthz"
-         - 'name == "/_healthz"'
+     filter/health:                       # Defines a filter processor
+       error_mode: ignore                 # Ignore errors
+       traces:                            # Filtering rules for traces
+         span:                            # Exclude spans named "/_healthz"
+          - 'name == "/_healthz"'
    ```
 
 2. **Add the `filter` processor to the `traces` pipeline**:  
@@ -36,12 +36,13 @@ Switch to your **Gateway terminal** window and open the `gateway.yaml` file. Upd
        - file/traces
    ```
 
-This setup ensures that health check-related spans (`/_healthz`) are filtered out early in the pipeline, reducing unnecessary noise in your telemetry data.
+This setup ensures that health check related spans (`/_healthz`) are filtered out early in the pipeline, reducing unnecessary noise in your telemetry data.
 
 {{% /notice %}}
 
-Validate the agent configuration using **[otelbin.io](https://www.otelbin.io/)**. For reference, the `traces:` section of your pipelines will look similar to this:
+<!--Validate the agent configuration using **[otelbin.io](https://www.otelbin.io/)**. For reference, the `traces:` section of your pipelines will look similar to this:-->
 
+<!--
 ```mermaid
 %%{init:{"fontFamily":"monospace"}}%%
 graph LR
@@ -58,16 +59,17 @@ graph LR
     subgraph " "
       subgraph subID1[**Traces**]
       direction LR
-      REC1 --> PRO1
-      PRO1 --> PRO4
-      PRO4 --> PRO3
-      PRO3 --> PRO5
-      PRO5 --> EXP1
-      PRO5 --> EXP2
+      REC1 -- > PRO1
+      PRO1 -- > PRO4
+      PRO4 -- > PRO3
+      PRO3 -- > PRO5
+      PRO5 -- > EXP1
+      PRO5 -- > EXP2
       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-traces stroke:#fbbf24,stroke-width:1px, color:#fbbf24,stroke-dasharray: 3 3;
 ```
+-->

content/en/conf/1-advanced-collector/3-dropping-spans/_index.md

@@ -7,12 +7,12 @@ weight: 5
 
 In this section, we will explore how to use the [**Filter Processor**](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/filterprocessor/README.md) to selectively drop spans based on certain conditions.
 
-Specifically, we will drop traces based on the span name, which is commonly used to filter out unwanted spans such as health checks or internal communication traces. In this case, we will be filtering out spans whose name is `"/_healthz"`, typically associated with health check requests and usually are quite "**noisy**".
+Specifically, we will drop traces based on the span name, which is commonly used to filter out unwanted spans such as health checks or internal communication traces. In this case, we will be filtering out spans that contain `"/_healthz"`, typically associated with health check requests and usually are quite "**noisy**".
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 > [!IMPORTANT]
-> **Change _ALL_ terminal windows to the `[WORKSHOP]/3-dropping-spans` directory.**
+> **Change _ALL_ terminal windows to the `3-dropping-spans` directory and run the `clear` command.**
 
 Copy `*.yaml` from the `2-building-resilience` directory into `3-dropping-spans`. Your updated directory structure will now look like this: