Formatting fixes

Author: rcastley

content/en/ninja-workshops/10-advanced-otel/8-routing/8-1-routing-test.md

@@ -138,6 +138,4 @@ By inspecting the output files, we confirmed that the OpenTelemetry Collector *c
 
 You can now extend this approach by defining additional routing rules to further categorize spans, metrics, and logs based on different attributes.
 
-If you want to know more about the `routing` connector, you can find it [here](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/routingconnector)
-
-Stop the **Agent**, **Gateway** and the` Quotes generating script` as well using `Ctrl-C`
+Stop the **Agent**, **Gateway** and the **quotes generating script**.

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

@@ -5,7 +5,7 @@ time: 10 minutes
 weight: 8
 ---
 
-The routing connector in OpenTelemetry is a powerful feature that allows you to direct data (`traces`, `metrics`, or `logs`) to different pipelines based on specific criteria. This is especially useful in scenarios where you want to apply different processing or exporting logic to subsets of your telemetry data.
+The [**Routing Connector**](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/routingconnector) in OpenTelemetry is a powerful feature that allows you to direct data (`traces`, `metrics`, or `logs`) to different pipelines based on specific criteria. This is especially useful in scenarios where you want to apply different processing or exporting logic to subsets of your telemetry data.
 
 For example, you might want to send *production* data to one exporter while directing *test* or *development* data to another. Similarly, you could route certain spans based on their attributes, such as service name, environment, or span name, to apply custom processing or storage logic.