From 68f9371fa64fd4badf13a40f8a167e06a27c72ca Mon Sep 17 00:00:00 2001 From: Madhura Bhave Date: Fri, 9 Jun 2023 11:34:39 -0700 Subject: [PATCH] Fix minor typo in docs --- .../ROOT/pages/servlet/authentication/session-management.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/servlet/authentication/session-management.adoc b/docs/modules/ROOT/pages/servlet/authentication/session-management.adoc index d46b9ffeb9..f9434d3826 100644 --- a/docs/modules/ROOT/pages/servlet/authentication/session-management.adoc +++ b/docs/modules/ROOT/pages/servlet/authentication/session-management.adoc @@ -80,7 +80,7 @@ If you try to use any of these methods, an exception will be thrown. By default, Spring Security stores the security context for you in the HTTP session. However, here are several reasons you may want to customize that: -* You may want call individual setters on the `HttpSessionSecurityContextRepository` instance +* You may want to call individual setters on the `HttpSessionSecurityContextRepository` instance * You may want to store the security context in a cache or database to enable horizontal scaling First, you need to create an implementation of `SecurityContextRepository` or use an existing implementation like `HttpSessionSecurityContextRepository`, then you can set it in `HttpSecurity`.