From 9a611cdca9ebb8e3068925ad19cd3394701e1f9c Mon Sep 17 00:00:00 2001
From: Kyujin Nam <kyujnam@gmail.com>
Date: Mon, 26 Sep 2022 15:53:42 +0900
Subject: [PATCH] fix: adoc code highlighting syntax (#1817) (#1820)

---
 docs/src/main/asciidoc/getting-started.adoc | 10 +++++-----
 docs/src/main/asciidoc/using.adoc           | 10 +++++-----
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/src/main/asciidoc/getting-started.adoc b/docs/src/main/asciidoc/getting-started.adoc
index f6f76b100d..066f53442b 100644
--- a/docs/src/main/asciidoc/getting-started.adoc
+++ b/docs/src/main/asciidoc/getting-started.adoc
@@ -212,7 +212,7 @@ controller setup or messaging test setup).
 The following example, from `pom.xml`, shows how to specify the base test class:
 
 ====
-[src,xml]
+[source,xml,indent=0]
 ----
 <build>
         <plugins>
@@ -589,7 +589,7 @@ contain all the setup necessary information needed to run them (for example,
 The following example, from `pom.xml`, shows how to specify the base test class:
 
 ====
-[src,xml]
+[source,xml,indent=0]
 ----
 <build>
         <plugins>
@@ -616,7 +616,7 @@ of a `configuration` element within `spring-cloud-contract-maven-plugin`.
 The following example shows a minimal (but functional) base test class:
 
 ====
-[src,Java]
+[source,java, indent=0]
 ----
 package com.example.contractTest;
 
@@ -641,7 +641,7 @@ Now we can move on to the implementation. For that, we first need a data class,
 then use in our controller. The following listing shows the data class:
 
 ====
-[src,Java]
+[source,java, indent=0]
 ----
 package com.example.Test;
 
@@ -680,7 +680,7 @@ client ID in the contract is called `client.id`, we need to use the
 Now we can move along to the controller, which the following listing shows:
 
 ====
-[src,Java]
+[source,java, indent=0]
 ----
 package com.example.docTest;
 
diff --git a/docs/src/main/asciidoc/using.adoc b/docs/src/main/asciidoc/using.adoc
index fbd106ec4f..4e700cf53e 100644
--- a/docs/src/main/asciidoc/using.adoc
+++ b/docs/src/main/asciidoc/using.adoc
@@ -28,7 +28,7 @@ that contains all the stubs for each producer. For an example of such a project,
 As a result of pushing stubs there, the repository has the following structure:
 
 ====
-[src, bash]
+[source,bash,indent=0]
 ----
 $ tree .
 └── META-INF
@@ -239,7 +239,7 @@ For example, for a producer named `producer` and a consumer named `consumer`, th
 . Once the contracts are defined, installs the producer stubs to local storage, as the following example shows:
 +
 ====
-[src,bash]
+[source,bash,indent=0]
 ----
 $ cd src/main/resource/contracts/producer
 $ ./mvnw clean install
@@ -285,7 +285,7 @@ The producer:
 from the command line, as follows
 +
 ====
-[src,bash]
+[source,bash,indent=0]
 ----
 $ git checkout -b the_branch_with_pull_request master
 git pull https://github.com/user_id/project_name.git the_branch_with_pull_request
@@ -294,7 +294,7 @@ git pull https://github.com/user_id/project_name.git the_branch_with_pull_reques
 . Installs the contract definitions, as follows
 +
 ====
-[src,bash]
+[source,bash,indent=0]
 ----
 $ ./mvnw clean install
 ----
@@ -358,7 +358,7 @@ contracts {
 . Merges the pull request to the repository with contract definitions, as follows:
 +
 ====
-[src,bash]
+[source,bash,indent=0]
 ----
 $ git commit -am "Finished the implementation to make the contract tests pass"
 $ git checkout master