From c836c716fe0a076ab2272843c09fd80a5ae4c235 Mon Sep 17 00:00:00 2001
From: Eleftheria Stein <eleftheria.kousathana@gmail.com>
Date: Mon, 8 Feb 2021 15:02:16 +0100
Subject: [PATCH] Fix typo in reactive CSRF docs

---
 .../src/docs/asciidoc/_includes/reactive/exploits/csrf.adoc     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/manual/src/docs/asciidoc/_includes/reactive/exploits/csrf.adoc b/docs/manual/src/docs/asciidoc/_includes/reactive/exploits/csrf.adoc
index b5f5652b51..c3a92fea4f 100644
--- a/docs/manual/src/docs/asciidoc/_includes/reactive/exploits/csrf.adoc
+++ b/docs/manual/src/docs/asciidoc/_includes/reactive/exploits/csrf.adoc
@@ -32,7 +32,7 @@ For example, it might be desirable to persist the `CsrfToken` in a cookie to <<w
 By default the `CookieServerCsrfTokenRepository` will write to a cookie named `XSRF-TOKEN` and read it from a header named `X-XSRF-TOKEN` or the HTTP parameter `_csrf`.
 These defaults come from https://docs.angularjs.org/api/ng/service/$http#cross-site-request-forgery-xsrf-protection[AngularJS]
 
-You can configure `CookieCsrfTokenRepository` in Java Configuration using:
+You can configure `CookieServerCsrfTokenRepository` in Java Configuration using:
 
 .Store CSRF Token in a Cookie
 ====