diff --git a/content/en/ninja-workshops/10-advanced-otel/80-routing/8-1-routing-test.md b/content/en/ninja-workshops/10-advanced-otel/80-routing/8-1-routing-test.md
index c600dfcae9..ba1aaf6e2c 100644
--- a/content/en/ninja-workshops/10-advanced-otel/80-routing/8-1-routing-test.md
+++ b/content/en/ninja-workshops/10-advanced-otel/80-routing/8-1-routing-test.md
@@ -106,10 +106,10 @@ Before proceeding, ensure that there are no `*.out` files in the `[WORKSHOP]/8-r
   1. Open your test terminal and navigate to the `[WORKSHOP]/8-routing` directory.
   2. Send a regular span using the `trace.json` file to confirm proper communication.
 
-  Both the `agent` and `gateway` should display debug information, including the span you just sent. The gateway will also generate a new `gateway-traces-default.out` file, as this is now the designated destination for regular spans.
+  Both the `agent` and `gateway` should display debug information, including the span you just sent. The gateway will also generate a new `gateway-traces-standard.out` file, as this is now the designated destination for regular spans.
 
 {{% notice title="Tip" style="primary" icon="lightbulb" %}}
-If you check `gateway-traces-default.out`, it should contain the `span` sent using the `cURL` command. You will also see an empty `gateway-traces-security.out` file, as the routing configuration creates output files immediately, even if no matching spans have been processed yet.
+If you check `gateway-traces-standard.out`, it should contain the `span` sent using the `cURL` command. You will also see an empty `gateway-traces-security.out` file, as the routing configuration creates output files immediately, even if no matching spans have been processed yet.
 {{% /notice %}}
 
 - **Send a Security Span**:  
@@ -117,6 +117,7 @@ If you check `gateway-traces-default.out`, it should contain the `span` sent usi
   2. Send a security span using the `security.json` file to test the gateway’s routing rule.
 
 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-security.out` file, which is designated for spans where the `deployment.environment` resource attribute matches `"security_applications"`.
+The `gateway-traces-standard.out` should be unchanged.
 
 {{% notice title="Tip" style="primary" icon="lightbulb" %}}
 If you verify the `./gateway-traces-security.out` it should only contain the spans from the `"security_applications"` deployment.environment.