Polish whitespace

spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/getting-started.adoc

@@ -1,6 +1,5 @@
 [[getting-started]]
 == Getting started
-
 The Spring Boot Plugin has the following goals:
 
 include::goals/overview.adoc[]

spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/integration-tests.adoc

@@ -1,6 +1,5 @@
 [[integration-tests]]
 == Running Integration tests
-
 While you may start your Spring Boot application very easily from your test (or test suite) itself, it may be desirable to handle that in the build itself.
 To make sure that the lifecycle of your Spring Boot application is properly managed around your integration tests, you can use the `start` and `stop` goals, as shown in the following example:
 
@@ -40,6 +39,7 @@ include::goals/start.adoc[leveloffset=+1]
 include::goals/stop.adoc[leveloffset=+1]
 
 
+
 [[integration-tests-example]]
 === Examples
 

spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/packaging-oci-image.adoc

@@ -30,6 +30,8 @@ It is possible to automate the creation of an image whenever the `package` phase
 TIP: While the buildpack runs from an <<repackage,executable archive>>, it is not necessary to execute the `repackage` goal first as the executable archive is created automatically if necessary.
 When the `build-image` repackages the application, it applies the same settings as the `repackage` goal would, i.e. dependencies can be excluded using one of the exclude options, and Devtools is automatically excluded by default (you can control that using the `excludeDevtools` property).
 
+
+
 [[build-image-customization]]
 === Image Customizations
 The plugin invokes a {buildpacks-reference}/concepts/components/builder/[builder] to orchestrate the generation of an image.
@@ -62,7 +64,6 @@ The following table summarizes the available properties and their default values
 | `verboseLogging`
 | Enables verbose logging of builder operations.
 | `false`
-
 |===
 
 For more details, see <<build-image-example-custom-image-builder,custom image builder>> and <<build-image-example-custom-image-name,custom image name>>.
@@ -70,9 +71,12 @@ For more details, see <<build-image-example-custom-image-builder,custom image bu
 include::goals/build-image.adoc[leveloffset=+1]
 
 
+
 [[build-image-examples]]
 === Examples
 
+
+
 [[build-image-example-custom-image-builder]]
 ==== Custom Image Builder
 If you need to customize the builder used to create the image, configure yours as shown in the following example:

spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/packaging.adoc

@@ -73,9 +73,13 @@ The `layout` property defaults to a guess based on the archive type (`jar` or `w
 
 include::goals/repackage.adoc[leveloffset=+1]
 
+
+
 [[repackage-examples]]
 === Examples
 
+
+
 [[repackage-example-custom-classifier]]
 ==== Custom Classifier
 By default, the `repackage` goal replaces the original artifact with the repackaged one.

spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/running.adoc

@@ -80,6 +80,8 @@ Note that this is only applied when you run an application: the `repackage` goal
 
 include::goals/run.adoc[leveloffset=+1]
 
+
+
 [[run-examples]]
 === Examples