diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc
index e41a3244b1..4bbb58325b 100644
--- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc
+++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc
@@ -619,6 +619,7 @@ make sure to check the
 section.
 
 
+
 [[howto-disable-registration-of-a-servlet-or-filter]]
 ===== Disable Registration of a Servlet or Filter
 As <<howto-add-a-servlet-filter-or-listener-as-spring-bean,described earlier>>, any
diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
index 03d6256293..00173447ef 100644
--- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
+++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
@@ -2756,11 +2756,11 @@ If convention-based mapping is not flexible enough, you can use the
 `ServletListenerRegistrationBean` classes for complete control.
 
 Spring Boot ships with many auto-configurations that can define Servlet filter beans.
-Depending on the outcome of these auto-configuration conditions, Spring Boot
-can configure predefined Servlet filters in in your application.
+Depending on the outcome of these auto-configuration conditions, Spring Boot can configure
+predefined Servlet filters in in your application.
 
-Here are a few examples of Servlet filters and their respective order (lower order
-value means higher precedence):
+Here are a few examples of Servlet filters and their respective order (lower order value
+means higher precedence):
 
 |===
 | Servlet Filter | Order
@@ -2780,12 +2780,12 @@ value means higher precedence):
 
 It is usually safe to leave filter beans unordered.
 
-If a specific order is required, you should avoid
-configuring a Servlet filter that reads the request body at
-`Ordered.HIGHEST_PRECEDENCE`, since it might go against the character encoding
-configuration of your application. Servlet filters should be configured
-at less or equal than `FilterRegistrationBean.REQUEST_WRAPPER_FILTER_MAX_ORDER`
-if they wrap the servlet request.
+If a specific order is required, you should avoid configuring a Servlet filter that reads
+the request body at `Ordered.HIGHEST_PRECEDENCE`, since it might go against the character
+encoding configuration of your application. Servlet filters should be configured at less
+or equal than `FilterRegistrationBean.REQUEST_WRAPPER_FILTER_MAX_ORDER` if they wrap the
+servlet request.
+
 
 
 [[boot-features-embedded-container-context-initializer]]