diff --git a/src/docs/asciidoc/30-testing.adoc b/src/docs/asciidoc/30-testing.adoc
index 9fcb4834..15911173 100644
--- a/src/docs/asciidoc/30-testing.adoc
+++ b/src/docs/asciidoc/30-testing.adoc
@@ -16,7 +16,7 @@ class OrderIntegrationTests {
 }
 ----
 
-This will run you integration test similar to what `@SpringBootTest` would have achieved but with the bootstrap actually limited to the application module the test resides in.
+This will run your integration test similar to what `@SpringBootTest` would have achieved but with the bootstrap actually limited to the application module the test resides in.
 If you configure the log level for `org.springframework.modulith` to `DEBUG`, you will see detailed information about how the test execution customizes the Spring Boot bootstrap:
 
 .The log output of a application module integration test bootstrap
diff --git a/src/docs/asciidoc/70-observability.adoc b/src/docs/asciidoc/70-observability.adoc
index bf469bf6..900e8046 100644
--- a/src/docs/asciidoc/70-observability.adoc
+++ b/src/docs/asciidoc/70-observability.adoc
@@ -9,10 +9,10 @@ To activate the instrumentation add the following runtime dependency to your pro
 ----
 <dependency>
   <groupId>org.springframework.modulith</groupId>
-  <artifactId>spring-modulith</artifactId>
+  <artifactId>spring-modulith-observability</artifactId>
   <version>{projectVersion}</version>
   <scope>runtime</scope
-</dependency
+</dependency>
 ----
 
 This will cause all Spring components that are part of the application module's API being decorated with an aspect that will intercept invocations and create Micrometer spans for them.