Skip to content

Commit 8e6dc6a

Browse files
Correct supersedes instead supercedes
1 parent a3ac85d commit 8e6dc6a

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/modules/ROOT/pages/servlet/appendix/namespace/method-security.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -287,7 +287,7 @@ Use AuthorizationManager API instead of AccessDecisionManager (defaults to true)
287287

288288
[[nsa-intercept-methods-authorization-manager-ref]]
289289
* **authorization-manager-ref**
290-
Optional AuthorizationManager bean ID to be used instead of the default (supercedes use-authorization-manager)
290+
Optional AuthorizationManager bean ID to be used instead of the default (supersedes use-authorization-manager)
291291

292292
[[nsa-intercept-methods-access-decision-manager-ref]]
293293
* **access-decision-manager-ref**

docs/modules/ROOT/pages/servlet/authorization/method-security.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -796,7 +796,7 @@ In-memory filtering can obviously be expensive, and so be considerate of whether
796796
=== Authorizing Method Invocation with `@Secured`
797797

798798
javadoc:org.springframework.security.access.annotation.Secured[format=annotation] is a legacy option for authorizing invocations.
799-
<<use-preauthorize,`@PreAuthorize`>> supercedes it and is recommended instead.
799+
<<use-preauthorize,`@PreAuthorize`>> supersedes it and is recommended instead.
800800

801801
To use the `@Secured` annotation, you should first change your Method Security declaration to enable it like so:
802802

0 commit comments

Comments
 (0)