diff --git a/content/en/ninja-workshops/6-lambda-kinesis/2-auto-instrumentation.md b/content/en/ninja-workshops/6-lambda-kinesis/2-auto-instrumentation.md
index 5de0fd8501..6d5b6d79d1 100644
--- a/content/en/ninja-workshops/6-lambda-kinesis/2-auto-instrumentation.md
+++ b/content/en/ninja-workshops/6-lambda-kinesis/2-auto-instrumentation.md
@@ -99,7 +99,7 @@ Next, let's take a look at the `producer-lambda` function code:
 
 - Run the following command to view the contents of the `producer.mjs` file:
   ```bash
-  cat ~/o11y-lambda-workshop/auto/handler/producer.mjs
+  cat ~/workshop/lambda/auto/handler/producer.mjs
   ```
   - This NodeJS module contains the code for the producer function.
   - Essentially, this function receives a message, and puts that message as a record to the targeted Kinesis Stream
diff --git a/content/en/ninja-workshops/6-lambda-kinesis/5-redeploy-lambdas.md b/content/en/ninja-workshops/6-lambda-kinesis/5-redeploy-lambdas.md
index d236113f9e..5ae95c92a1 100644
--- a/content/en/ninja-workshops/6-lambda-kinesis/5-redeploy-lambdas.md
+++ b/content/en/ninja-workshops/6-lambda-kinesis/5-redeploy-lambdas.md
@@ -125,7 +125,7 @@ Examine the logs carefully.
 
 > Do you notice the difference?
 
-#### Copy the Trace ID from the `consumer-lambda` logs
+#### Copy the Trace ID from the `consumer.logs` file
 
 This time around, we can see that the consumer-lambda log group is logging our message as a `record` together with the `tracecontext` that we propagated.