diff --git a/docker/spring-cloud-contract-docker/Dockerfile b/docker/spring-cloud-contract-docker/Dockerfile
index e14551dc5e..d0b5aa5d31 100644
--- a/docker/spring-cloud-contract-docker/Dockerfile
+++ b/docker/spring-cloud-contract-docker/Dockerfile
@@ -1,6 +1,6 @@
 FROM ubuntu:19.10
 
-ARG SDKMAN_JAVA_INSTALLATION=8.0.242.hs-adpt
+ARG SDKMAN_JAVA_INSTALLATION=8.0.252.hs-adpt
 
 MAINTAINER Marcin Grzejszczak <mgrzejszczak@pivotal.io>
 
diff --git a/docker/spring-cloud-contract-stub-runner-docker/Dockerfile b/docker/spring-cloud-contract-stub-runner-docker/Dockerfile
index e33e16c400..b982a01a38 100644
--- a/docker/spring-cloud-contract-stub-runner-docker/Dockerfile
+++ b/docker/spring-cloud-contract-stub-runner-docker/Dockerfile
@@ -1,6 +1,6 @@
 FROM ubuntu:19.10
 
-ARG SDKMAN_JAVA_INSTALLATION=8.0.242.hs-adpt
+ARG SDKMAN_JAVA_INSTALLATION=8.0.252.hs-adpt
 
 MAINTAINER Marcin Grzejszczak <mgrzejszczak@pivotal.io>
 
diff --git a/docs/src/main/asciidoc/sagan-boot.adoc b/docs/src/main/asciidoc/sagan-boot.adoc
index 6ffcd20542..0e9027b10f 100644
--- a/docs/src/main/asciidoc/sagan-boot.adoc
+++ b/docs/src/main/asciidoc/sagan-boot.adoc
@@ -54,7 +54,8 @@ The following example, from pom.xml, shows how to specify the base test class:
 INFO: The baseClassForTests element lets you specify your base test class. It must be a child of a configuration element within spring-cloud-contract-maven-plugin.
 
 Once the implementation and the test base class are in place, the tests pass, and both the application and the stub artifacts are built and installed in the local Maven repository. You can now merge the changes, and you can publish both the application and the stub artifacts in an online repository.
-2.2. On the Consumer Side
+
+== On the Consumer Side
 
 You can use Spring Cloud Contract Stub Runner in the integration tests to get a running WireMock instance or messaging route that simulates the actual service.