Polish

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

@@ -3379,6 +3379,8 @@ NOTE: `TomcatServletWebServerFactory`, `JettyServletWebServerFactory` and `Under
 are dedicated variants of `ConfigurableServletWebServerFactory` that have additional customization setter methods
 for Tomcat, Jetty and Undertow respectively.
 
+
+
 [[boot-features-customizing-configurableservletwebserverfactory-directly]]
 ===== Customizing ConfigurableServletWebServerFactory Directly
 If the preceding customization techniques are too limited, you can register the
@@ -3403,6 +3405,7 @@ are also provided should you need to do something more exotic. See the
 code documentation] for details.
 
 
+
 [[boot-features-jsp-limitations]]
 ==== JSP Limitations
 When running a Spring Boot application that uses an embedded servlet container (and is
@@ -3422,17 +3425,19 @@ instead.
 There is a {github-code}/spring-boot-samples/spring-boot-sample-web-jsp[JSP sample] so
 that you can see how to set things up.
 
+
+
 [[boot-features-reactive-server]]
 === Embedded Reactive Server Support
-
 Spring Boot includes support for the following embedded reactive web servers:
 Reactor Netty, Tomcat, Jetty, and Undertow. Most developers use the appropriate “Starter”
 to obtain a fully configured instance. By default, the embedded server listens for HTTP
 requests on port 8080.
 
+
+
 [[boot-features-reactive-server-resources]]
 === Reactive Server Resources Configuration
-
 When auto-configuring a Reactor Netty or Jetty server, Spring Boot will create specific
 beans that will provide HTTP resources to the server instance: `ReactorResourceFactory`
 or `JettyResourceFactory`.
@@ -3451,6 +3456,8 @@ both clients and servers.
 You can learn more about the resource configuration on the client side in the
 <<boot-features-webclient-runtime, WebClient Runtime section>>.
 
+
+
 [[boot-features-rsocket]]
 == RSocket
 
@@ -3483,6 +3490,8 @@ The following code shows a typical `@Controller`:
 	}
 ----
 
+
+
 [[boot-features-rsocket-strategies-auto-configuration]]
 === RSocket Strategies Auto-configuration
 Spring Boot auto-configures an `RSocketStrategies` bean that provides all the required
@@ -3499,6 +3508,7 @@ implement the `RSocketStrategiesCustomizer` interface. Note that their `@Order`
 important, as it determines the order of codecs.
 
 
+
 [[boot-features-rsocket-server-auto-configuration]]
 === RSocket server Auto-configuration
 Spring Boot provides auto-configuration for RSocket servers. The required dependencies
@@ -3544,6 +3554,8 @@ about customization possibilities.
 Developers can create `RSocketStrategiesCustomizer` beans to add other strategies,
 assuming there are `Encoder` and `Decoder` implementations available.
 
+
+
 [[boot-features-rsocket-requester]]
 === Calling RSocket Services with `RSocketRequester`
 
@@ -3582,6 +3594,7 @@ The following code shows a typical example:
 ----
 
 
+
 [[boot-features-security]]
 == Security
 If {spring-security}[Spring Security] is on the classpath, then web applications are
@@ -3620,6 +3633,7 @@ the entire application (including actuator endpoints if actuator is on the class
 You can provide a different `AuthenticationEventPublisher` by adding a bean for it.
 
 
+
 [[boot-features-security-mvc]]
 === MVC Security
 The default security configuration is implemented in `SecurityAutoConfiguration` and

spring-boot-project/spring-boot-docs/src/main/java/org/springframework/boot/docs/test/autoconfigure/restdocs/restassured/UserDocumentationTests.java

@@ -29,7 +29,7 @@ import org.springframework.boot.web.server.LocalServerPort;
 import org.springframework.test.context.junit4.SpringRunner;
 
 import static io.restassured.RestAssured.given;
-import static org.hamcrest.CoreMatchers.is;
+import static org.hamcrest.Matchers.is;
 import static org.springframework.restdocs.restassured3.RestAssuredRestDocumentation.document;
 
 @RunWith(SpringRunner.class)