From cece06e3382e52feb15be47d6edc02a975f96a42 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?M=C3=A1rio=20Pereira?=
 <16617269+mariodmpereira@users.noreply.github.com>
Date: Tue, 23 May 2023 20:12:08 +0100
Subject: [PATCH] Fix typo on method-security.adoc

---
 .../ROOT/pages/servlet/authorization/method-security.adoc       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc b/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc
index 51949ca534..089b14ae2a 100644
--- a/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc
+++ b/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc
@@ -369,7 +369,7 @@ fun readAccountWithWrongRoleThenAccessDenied() {
 `@PreAuthorize` also can be a <<meta-annotations, meta-annotation>>, be defined <<class-or-interface-annotations,at the class or interface level>>, and use <<authorization-expressions, SpEL Authorization Expressions>>.
 
 While `@PreAuthorize` is quite helpful for declaring needed authorities, it can also be used to evaluate more complex <<using_method_parameters,expressions that involve the method parameters>>.
-asdf
+
 The above two snippets are ensuring that the user can only request orders that belong to them by comparing the username parameter to xref:servlet/authentication/architecture.adoc#servlet-authentication-authentication[`Authentication#getName`].
 
 The result is that the above method will only be invoked if the `username` in the request path matches the logged-in user's `name`.