Polish gh-13575

spring-projects · Sep 7, 2023 · 9de717a · 9de717a
1 parent 3a50c92
commit 9de717a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/modules/ROOT/pages/servlet/test/mockmvc/result-handlers.adoc b/docs/modules/ROOT/pages/servlet/test/mockmvc/result-handlers.adoc
@@ -8,7 +8,7 @@ In order to use Spring Security's ``ResultHandler``s implementations ensure the
 import static org.springframework.security.test.web.servlet.response.SecurityMockMvcResultHandlers.*;
 ----
 
-==== Exporting the SecurityContext
+== Exporting the SecurityContext
 
 Often times we want to query a repository to see if some `MockMvc` request actually persisted in the database.
 In some cases our repository query uses the xref:features/integrations/data.adoc[Spring Data Integration] to filter the results based on current user's username or any other property.

diff --git a/docs/modules/ROOT/pages/servlet/test/mockmvc/result-matchers.adoc b/docs/modules/ROOT/pages/servlet/test/mockmvc/result-matchers.adoc
@@ -22,7 +22,7 @@ import org.springframework.security.test.web.servlet.response.SecurityMockMvcRes
 ----
 ======
 
-=== Unauthenticated Assertion
+== Unauthenticated Assertion
 
 At times it may be valuable to assert that there is no authenticated user associated with the result of a `MockMvc` invocation.
 For example, you might want to test submitting an invalid username and password and verify that no user is authenticated.
@@ -49,7 +49,7 @@ mvc
 ----
 ======
 
-=== Authenticated Assertion
+== Authenticated Assertion
 
 It is often times that we must assert that an authenticated user exists.
 For example, we may want to verify that we authenticated successfully.