Polish

initializr-docs/src/main/asciidoc/configuration-format.adoc

@@ -101,15 +101,16 @@ list of the available configuration options.
 
 Here is the most basic dependency entry you could have
 
-```yml
-initializr:
+[source,yaml,indent=0]
+----
+	initializr:
 	  dependencies:
 	    - name: Core
 	      content:
 	        - id: security
 	          name: Security
 	          description: Secure your application via spring-security
-```
+----
 
 TIP: The `security` dependency is held within a group called "Core".
 
@@ -122,8 +123,9 @@ Let's now add a custom dependency that is not managed by Spring Boot and that on
 work from Spring Boot `1.2.0.RELEASE` and onwards but should not be used in the 1.3
 lines and further for some reason.
 
-```yml
-initializr:
+[source,yaml,indent=0]
+----
+	initializr:
 	  dependencies:
 	    - name: Core
 	      content:
@@ -135,7 +137,7 @@ initializr:
 	          bom: foo-bom
 	          repository: foo-repo
 	          versionRange: "[1.2.0.RELEASE,1.3.0.M1)"
-```
+----
 
 If one selects this entry, the `com.example.foo:foo-core}` dependency will be added
 and the Bill of Materials and repository for `foo` will be added automatically to
@@ -166,8 +168,9 @@ support is meant to react to that.
 For instance, if you want your groupId to default to `org.acme` and the
 `javaVersions` to only be `1.8` and `11` you would write the following config:
 
-```yml
-initializr:
+[source,yaml,indent=0]
+----
+	initializr:
 	  groupId:
 	    value: org.acme
 	  javaVersions:
@@ -175,4 +178,4 @@ initializr:
 	      default: false
 	    - id: 1.8
 	      default: true
-```
+----

initializr-docs/src/main/asciidoc/configuration-guide.adoc

@@ -347,7 +347,7 @@ declared at the top level (under `env`) and given an id via the key in the confi
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  env:
 		repositories:
 		  my-api-repo-1:
@@ -359,7 +359,7 @@ Once defined, the repository can then be referred back to in a dependency
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Other
 		  content:
@@ -394,7 +394,7 @@ configuration key. Example:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  env:
 		boms:
 		  my-api-bom:
@@ -411,7 +411,7 @@ BOMs by referring to the id:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Other
 		  content:
@@ -437,7 +437,7 @@ Here's an example of a BOM with mappings:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  env:
 		boms:
 		  cloud-bom:
@@ -481,7 +481,7 @@ an alias can be defined for ths dependency;
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Other
 		  content:
@@ -626,7 +626,7 @@ versions of Spring Boot, not of your dependency. For example:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Stuff
 		  content:
@@ -650,7 +650,7 @@ the values defined at the top level. For example:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Stuff
 		  content:
@@ -674,7 +674,7 @@ A mapping can also be applied to a BOM declaration. For example:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  env:
 		boms:
 		  my-api-bom:
@@ -713,7 +713,7 @@ existing Spring Boot starter) you can flag it as a "non starter":
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Stuff
 		  content:
@@ -738,13 +738,13 @@ common settings in a group are the `groupId`, `versionRange` and `bom`:
 
 [source,yaml,indent=0]
 ----
-initializr:
+	initializr:
 	  dependencies:
 		- name: Stuff
 		  bom: stuff-bom
 		  versionRange: "[1.3.0.RELEASE,2.0.0.M1)"
 		  content:
-...
+	...
 ----
 
 These dependencies, by default, will be available only for Spring Boot versions 1.3 up to