Minor edits to routing data configuration files

Author: rcastley

content/en/conf/1-advanced-collector/6-routing-data/6-1-connector.md

@@ -35,7 +35,6 @@ In the **Gateway terminal** window, edit `gateway.yaml` and  find and uncomment
 
 {{% /notice %}}
 
-The default pipeline in the configuration file  works at a Catch all. It will be the  routing target for any data (spans in our case) that does match a rule in the routing rules table, In this table you find the pipeline that is the target for any span that matches the following rule: "[deployment.environment"] == "security-applications"
-
+The default pipeline in the configuration file  works at a Catch all. It will be the  routing target for any data (spans in our case) that do not match a rule in the routing rules table, In this table you find the pipeline that is the target for any span that matches the following rule: `["deployment.environment"] == "security-applications"`
 
 With the `routing` configuration complete, the next step is to configure the `pipelines` to apply these routing rules.

content/en/conf/1-advanced-collector/6-routing-data/6-2-pipelines.md

@@ -8,7 +8,7 @@ weight: 2
 
 **Update the original `traces` pipeline to use routing**:
 
-1. To enable `routing`, update the original `traces:` pipeline to use `routing` as the only exporter. This ensures all span data is sent through the **Routing Connector** for evaluation and then onwards to connected pipelines. Also, remove **all** processors and replace it with an empty array (`[]`) as this will now behandeld in the `traces/route1-regular` and `traces/route2-security` pipelines, allowing for custom behaviour for each route.  Your `traces:` configuration should look like this:
+1. To enable `routing`, update the original `traces` pipeline to use `routing` as the only exporter. This ensures all span data is sent through the **Routing Connector** for evaluation and then onwards to connected pipelines. Also, remove **all** processors and replace it with an empty array (`[]`) as this will now behandeld in the `traces/route1-regular` and `traces/route2-security` pipelines, allowing for custom behaviour for each route.  Your `traces:` configuration should look like this:
 
     ```yaml
     traces:                       # Traces pipeline
@@ -19,7 +19,7 @@ weight: 2
       - routing
     ```
 
-**Add both the `route1-regular` and `route2-security` traces pipelines** below the existing `traces:` pipeline:
+**Add both the `route1-regular` and `route2-security` traces pipelines** below the existing `traces` pipeline:
 
 1. **Configure Route1-regular pipeline**: This pipeline will handle all spans that have  **no match** in the routing table in the connector.
 Notice this uses `routing` as its only receiver and will recieve data thought its `connection` from the original traces pipeline. 
@@ -37,7 +37,7 @@ Notice this uses `routing` as its only receiver and will recieve data thought it
           - file/traces/route1-regular # File Exporter for unmatched spans 
     ```
 
-2. **Add the route2-security pipeline**: This pipeline processes all spans that do match our rule "[deployment.environment"] == "security-applications" in the  the routing rule. This pipeline is also using `routing` as its receiver. Add this  pipline below the `traces/route1-regular` one.
+2. **Add the route2-security pipeline**: This pipeline processes all spans that do match our rule `"[deployment.environment"] == "security-applications"` in the  the routing rule. This pipeline is also using `routing` as its receiver. Add this pipline below the `traces/route1-regular` one.
 
     ```yaml
         traces/route2-security:         # Default pipeline for unmatched spans

content/en/conf/1-advanced-collector/6-routing-data/6-3-test-routing.md

@@ -6,7 +6,7 @@ weight: 3
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-In this section, we will test the `routing` rule configured for the **Gateway**. The expected result is that a `span` generated by the `loadgen`  that match the “[deployment.environment”] == “security-applications” rule will be sent to the `gateway-traces-route2-security.out` file.
+In this section, we will test the `routing` rule configured for the **Gateway**. The expected result is that a `span` generated by the `loadgen`  that match the `"[deployment.environment"] == "security-applications"` rule will be sent to the `gateway-traces-route2-security.out` file.
 
 **Start the Gateway**: In your **Gateway terminal** window start the **Gateway**.
 
@@ -39,7 +39,6 @@ If you check `gateway-traces-route1-regular.out`, it will contain the `span` sen
 ```
 
 Again, both the **Agent** and **Gateway** should display debug information, including the span you just sent. This time, the **Gateway** will write a line to the `gateway-traces-route2-security.out` file, which is designated for spans where the `deployment.environment` resource attribute matches `"security-applications"`.
-The `gateway-traces-route1-regular.out` should be unchanged.
 
 {{% tabs %}}
 {{% tab title="Validate resource attribute matches" %}}