diff --git a/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/add-axon-firestarter.adoc b/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/add-axon-firestarter.adoc
index 8800f07..bd86da6 100644
--- a/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/add-axon-firestarter.adoc
+++ b/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/add-axon-firestarter.adoc
@@ -17,7 +17,7 @@ NOTE: If you are using the Docker-based bike-rental demo that comes with AxonIQ
 The first thing we need to do is to declare the dependency management in the `pom.xml` of the root project:
 
 ./pom.xml
-[sources,xml]
+[source,xml]
 ----
 include::example$root/pom.xml[tags=dependencyManagement;deps-axon-firestarter;!*]
 ----
@@ -25,13 +25,13 @@ include::example$root/pom.xml[tags=dependencyManagement;deps-axon-firestarter;!*
 With this configuration, we can now add the dependency to any module in our project without specifying the version while keeping the versions in sync. So all you need to do is declare the dependency in your `payment' and `rental' modules:
 
 ./payment/pom.xml
-[sources,xml]
+[source,xml]
 ----
 include::example$payment/pom.xml[tags=dependencies;deps-axon-firestarter;!*]
 ----
 
 ./rental/pom.xml
-[sources,xml]
+[source,xml]
 ----
 include::example$rental/pom.xml[tags=dependencies;deps-axon-firestarter;!*]
 ----
diff --git a/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/your-app-in-axoniq-console.adoc b/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/your-app-in-axoniq-console.adoc
index ec7d918..fcac293 100644
--- a/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/your-app-in-axoniq-console.adoc
+++ b/docs/axoniq-console-guide/modules/ROOT/pages/monitoring/your-app-in-axoniq-console.adoc
@@ -133,7 +133,7 @@ The Processors tab collects information about the event processors defined in yo
 ====
 Event Processors are the components in an Axon Framework application that perform the tasks necessary to handle an event (for example, launching a transaction if required) and call the event handler that defines the business logic associated with receiving the event.
 
-You can learn more about xref:axon-framework-reference:events:event-processors/README.adoc[Event Processors in Axon Framework Applications] in the dedicated section of the Axon Framework Reference Guide.
+You can learn more about xref:axon-framework-reference:events:event-processors/index.adoc[Event Processors in Axon Framework Applications] in the dedicated section of the Axon Framework Reference Guide.
 ====
 
 In the case of our application, we can see the three event processors that we have defined in our bike-rental application:
diff --git a/docs/tutorial/modules/ROOT/pages/run-app-with-docker-compose.adoc b/docs/tutorial/modules/ROOT/pages/run-app-with-docker-compose.adoc
index 3bfc045..34fbe8e 100644
--- a/docs/tutorial/modules/ROOT/pages/run-app-with-docker-compose.adoc
+++ b/docs/tutorial/modules/ROOT/pages/run-app-with-docker-compose.adoc
@@ -24,7 +24,7 @@ Even if we are going to run only one docker image (Axon Server), Docker Compose
 
 We will start by creating the Docker Compose configuration file. Create a `compose.yaml` file in the `root` project with the following contents:
 
-[sources,yaml]
+[source,yaml]
 .compose.yaml
 ----
 include::example$root/compose.yaml[]