Polish

spring-boot-docs/src/main/asciidoc/howto.adoc

@@ -1483,6 +1483,7 @@ repository types (Elasticsearch, Solr). Just change the names of the annotations
 respectively.
 
 
+
 [[howto-use-exposing-spring-data-repositories-rest-endpoint]]
 === Expose Spring Data repositories as REST endpoint
 
@@ -1497,6 +1498,7 @@ extending from `RepositoryRestMvcBootConfiguration` instead as the latter provid
 the handling of `spring.data.rest` properties.
 
 
+
 [[howto-database-initialization]]
 == Database initialization
 An SQL database can be initialized in different ways depending on what your stack is. Or

spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -297,14 +297,13 @@ Maven '`project properties`' via `@..@` placeholders, e.g.
 NOTE: In the above example we used `+project.*+` to set some values to be used as
 fallbacks if the Maven resource filtering has not been switched on for some reason.
 
-TIP: The `spring-boot:run` maven goal adds `src/main/resources` directly to 
-the classpath (for hot reloading purposes). This circumvents the resource 
-filtering and this feature. You can use the `exec:java` goal instead or 
-customize the plugin's configuration, see the 
+TIP: The `spring-boot:run` maven goal adds `src/main/resources` directly to the classpath
+(for hot reloading purposes). This circumvents the resource filtering and this feature.
+You can use the `exec:java` goal instead or customize the plugin's configuration, see the
 {spring-boot-maven-plugin-site}/usage.html[plugin usage page] for more details.
 
-
-NOTE: If you don't use the starter parent, in your `pom.xml` you need (inside the `<build/>` element):
+If you don't use the starter parent, in your `pom.xml` you need (inside the `<build/>`
+element):
 
 [source,xml,indent=0]
 ----
@@ -332,6 +331,8 @@ and (inside `<plugins/>`):
 	</plugin>
 ----
 
+
+
 [[production-ready-application-info-automatic-expansion-gradle]]
 ===== Automatic property expansion using Gradle
 You can automatically expand info properties from the Gradle project by configuring

spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -1271,7 +1271,7 @@ instance. By default the embedded server will listen for HTTP requests on port `
 
 [[boot-features-embedded-container-servlets-and-filters]]
 ==== Servlets and Filters
-When using an embedded servlet container you can register Servlets, Filters and all the 
+When using an embedded servlet container you can register Servlets, Filters and all the
 listeners from the Servlet spec (e.g. `HttpSessionListener`) directly as
 Spring beans. This can be particularly convenient if you want to refer to a value from
 your `application.properties` during configuration.
@@ -1281,10 +1281,9 @@ the case of multiple Servlet beans the bean name will be used as a path prefix.
 will map to `+/*+`.
 
 If convention-based mapping is not flexible enough you can use the
-`ServletRegistrationBean`, `FilterRegistrationBean` and
-`ServletListenerRegistrationBean` classes for complete control. You
-can also register items directly if your bean implements the
-`ServletContextInitializer` interface.
+`ServletRegistrationBean`, `FilterRegistrationBean` and `ServletListenerRegistrationBean`
+classes for complete control. You can also register items directly if your bean implements
+the `ServletContextInitializer` interface.