diff --git a/docs/modules/ROOT/pages/_observability.adoc b/docs/modules/ROOT/pages/_observability.adoc
index 01121b26..2b4083fa 100644
--- a/docs/modules/ROOT/pages/_observability.adoc
+++ b/docs/modules/ROOT/pages/_observability.adoc
@@ -1,7 +1,7 @@
 :root-target: ../../../target/
 
 [[observability]]
-== Observability metadata
+= Observability metadata
 
 include::{root-target}_metrics.adoc[]
 
diff --git a/docs/modules/ROOT/pages/appendix-building-the-documentation.adoc b/docs/modules/ROOT/pages/appendix-building-the-documentation.adoc
index 1103edaf..9532545f 100644
--- a/docs/modules/ROOT/pages/appendix-building-the-documentation.adoc
+++ b/docs/modules/ROOT/pages/appendix-building-the-documentation.adoc
@@ -1,6 +1,6 @@
 
 [[appendix-building-the-documentation]]
-== Building This Documentation
+= Building This Documentation
 
 This project uses Maven to generate this documentation. To generate it for yourself,
 run the following command: `$ mvn clean install -DskipTests -P docs`.
diff --git a/docs/modules/ROOT/pages/appendix-task-repository-schema.adoc b/docs/modules/ROOT/pages/appendix-task-repository-schema.adoc
index 6bbc90c0..ffd91a7f 100644
--- a/docs/modules/ROOT/pages/appendix-task-repository-schema.adoc
+++ b/docs/modules/ROOT/pages/appendix-task-repository-schema.adoc
@@ -1,5 +1,5 @@
 [[appendix-task-repository-schema]]
-== Task Repository Schema
+= Task Repository Schema
 
 [[partintro]]
 --
@@ -9,7 +9,7 @@ This appendix provides an ERD for the database schema used in the task repositor
 image::task_schema.png[]
 
 [[table-information]]
-=== Table Information
+== Table Information
 --
 
 .TASK_EXECUTION
@@ -86,7 +86,7 @@ NOTE: The DDL for setting up tables for each database type can be found https://
 --
 
 [[sql-server]]
-=== SQL Server
+== SQL Server
 By default Spring Cloud Task uses a sequence table for determining the `TASK_EXECUTION_ID` for the `TASK_EXECUTION` table.
 However, when launching multiple tasks simultaneously while using SQL Server, this can cause a deadlock to occur on the `TASK_SEQ` table.
 The resolution is to drop the `TASK_EXECUTION_SEQ` table and create a sequence using the same name.   For example: