path fixes

JenSeReal · Apr 17, 2024 · da22833 · da22833
1 parent 2f44512
commit da22833
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/tutorial/content/labs/instrumentation/automatic/auto-instrumentation/index.md b/tutorial/content/labs/instrumentation/automatic/auto-instrumentation/index.md
@@ -75,7 +75,7 @@ please switch to this directory and call `docker compose down` to stop it.
 Change to the `labs` directory within your git project root and then into the `auto-instrumentation/initial/todobackend-springboot` path.
 
 ```sh
-cd labs/auto-instrumentation/initial/todobackend-springboot
+cd labs/automatic-instrumentation/auto-instrumentation/initial/todobackend-springboot
 ```
 
 This is the same Java project as used for the backend component in the `OpenTelemetry in Action`chapter.
@@ -288,7 +288,7 @@ Now point your browser to `http://localhost:16686/`.
 If you run your application with a local container daemon, `localhost` in your browser will work. If you are using a cloud-based setup like Codespaces or Gitpod , please see the section "How to use this lab".
 
 Especially the section about ports and hostnames is relevant here.
-[Test](/labs/introduction/#important-differences-between-local-and-remote-way-of-running-the-lab)
+[Link](/labs/introduction/#important-differences-between-local-and-remote-way-of-running-the-lab)
 
 The Jaeger UI will come up. Click the button `Find traces`.
 

diff --git a/tutorial/content/labs/use_case_scenarios/_index.md b/tutorial/content/labs/use_case_scenarios/_index.md
@@ -47,7 +47,7 @@ The entire stack of components is modeled in containers and can be run using a d
 To access the demo environment, switch to the directory for this exercise:
 
 ```sh { title="terminal" }
-cd /workspace/exercise-use-case-scenario
+cd labs/otel-in-action
 ```
 
 Then execute the docker-compose file to build and bring up the containers.