diff --git a/src/main/asciidoc/jdbc.adoc b/src/main/asciidoc/jdbc.adoc
index f5318752..9051fd49 100644
--- a/src/main/asciidoc/jdbc.adoc
+++ b/src/main/asciidoc/jdbc.adoc
@@ -457,7 +457,7 @@ The execution of CRUD operations and query methods can be delegated to MyBatis.
 This section describes how to configure Spring Data JDBC to integrate with MyBatis and which conventions to follow to hand over the execution of the queries as well as the mapping to the library.
 
 [[jdbc.mybatis.configuration]]
-== Configuration
+=== Configuration
 
 The easiest way to properly plug MyBatis into Spring Data JDBC is by importing `MyBatisJdbcConfiguration` into you application configuration:
 
@@ -478,7 +478,7 @@ class Application {
 As you can see, all you need to declare is a `SqlSessionFactoryBean` as `MyBatisJdbcConfiguration` relies on a `SqlSession` bean to be available in the `ApplicationContext` eventually.
 
 [[jdbc.mybatis.conventions]]
-== Usage conventions
+=== Usage conventions
 
 For each operation in `CrudRepository`, Spring Data JDBC runs multiple statements.
 If there is a https://github.com/mybatis/mybatis-3/blob/master/src/main/java/org/apache/ibatis/session/SqlSessionFactory.java[`SqlSessionFactory`] in the application context, Spring Data checks, for each step, whether the `SessionFactory` offers a statement.