From 3fc0045a29cbb056e1dee6e47fe175363e23fbc7 Mon Sep 17 00:00:00 2001 From: Tran Ngoc Nhan Date: Sat, 9 Nov 2024 23:28:30 +0700 Subject: [PATCH] Fix Documentation Typos --- docs/modules/ROOT/pages/features/integrations/localization.adoc | 2 +- docs/modules/ROOT/pages/reactive/getting-started.adoc | 2 +- .../pages/reactive/oauth2/resource-server/bearer-tokens.adoc | 2 +- .../ROOT/pages/servlet/appendix/namespace/method-security.adoc | 2 +- docs/modules/ROOT/pages/servlet/authentication/rememberme.adoc | 2 +- docs/modules/ROOT/pages/servlet/authentication/runas.adoc | 2 +- .../ROOT/pages/servlet/authorization/method-security.adoc | 2 +- docs/modules/ROOT/pages/servlet/saml2/metadata.adoc | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/modules/ROOT/pages/features/integrations/localization.adoc b/docs/modules/ROOT/pages/features/integrations/localization.adoc index e1fc22b9a25..0236b31696a 100644 --- a/docs/modules/ROOT/pages/features/integrations/localization.adoc +++ b/docs/modules/ROOT/pages/features/integrations/localization.adoc @@ -5,7 +5,7 @@ If your application is designed for English-speaking users, you don't need to do If you need to support other locales, everything you need to know is contained in this section. All exception messages can be localized, including messages related to authentication failures and access being denied (authorization failures). -Exceptions and logging messages that are focused on developers or system deplopers (including incorrect attributes, interface contract violations, using incorrect constructors, startup time validation, debug-level logging) are not localized and instead are hard-coded in English within Spring Security's code. +Exceptions and logging messages that are focused on developers or system deployers (including incorrect attributes, interface contract violations, using incorrect constructors, startup time validation, debug-level logging) are not localized and instead are hard-coded in English within Spring Security's code. Shipping in the `spring-security-core-xx.jar` you will find an `org.springframework.security` package that in turn contains a `messages.properties` file, as well as localized versions for some common languages. This should be referred to by your `ApplicationContext`, as Spring Security classes implement Spring's `MessageSourceAware` interface and expect the message resolver to be dependency injected at application context startup time. diff --git a/docs/modules/ROOT/pages/reactive/getting-started.adoc b/docs/modules/ROOT/pages/reactive/getting-started.adoc index d12c64cf985..be6a4c3d3ce 100644 --- a/docs/modules/ROOT/pages/reactive/getting-started.adoc +++ b/docs/modules/ROOT/pages/reactive/getting-started.adoc @@ -75,7 +75,7 @@ Using generated security password: 8e557245-73e2-4286-969a-ff57fe326336 [[authenticating]] == Authenticating -You can access the application at http://localhost:8080/ which will redirect the browser to the default log in page. You can provide the default username of `user` with the randomly generated password that is logged to the console. The browser is then taken to the orginally requested page. +You can access the application at http://localhost:8080/ which will redirect the browser to the default log in page. You can provide the default username of `user` with the randomly generated password that is logged to the console. The browser is then taken to the originally requested page. To log out you can visit http://localhost:8080/logout and then confirming you wish to log out. diff --git a/docs/modules/ROOT/pages/reactive/oauth2/resource-server/bearer-tokens.adoc b/docs/modules/ROOT/pages/reactive/oauth2/resource-server/bearer-tokens.adoc index 47905d6eb03..04913860933 100644 --- a/docs/modules/ROOT/pages/reactive/oauth2/resource-server/bearer-tokens.adoc +++ b/docs/modules/ROOT/pages/reactive/oauth2/resource-server/bearer-tokens.adoc @@ -96,7 +96,7 @@ this.rest.get() ---- ====== -The prececing example invokes the `https://other-service.example.com/endpoint`, adding the bearer token `Authorization` header for you. +The preceding example invokes the `https://other-service.example.com/endpoint`, adding the bearer token `Authorization` header for you. In places where you need to override this behavior, you can supply the header yourself: diff --git a/docs/modules/ROOT/pages/servlet/appendix/namespace/method-security.adoc b/docs/modules/ROOT/pages/servlet/appendix/namespace/method-security.adoc index 71b8d771504..420a34c8280 100644 --- a/docs/modules/ROOT/pages/servlet/appendix/namespace/method-security.adoc +++ b/docs/modules/ROOT/pages/servlet/appendix/namespace/method-security.adoc @@ -287,7 +287,7 @@ Use AuthorizationManager API instead of AccessDecisionManager (defaults to true) [[nsa-intercept-methods-authorization-manager-ref]] * **authorization-manager-ref** -Optional AuthorizationManager bean ID to be used instead of the default (supercedes use-authorization-manager) +Optional AuthorizationManager bean ID to be used instead of the default (supersedes use-authorization-manager) [[nsa-intercept-methods-access-decision-manager-ref]] * **access-decision-manager-ref** diff --git a/docs/modules/ROOT/pages/servlet/authentication/rememberme.adoc b/docs/modules/ROOT/pages/servlet/authentication/rememberme.adoc index 3e8e24199f7..c0c5143f02a 100644 --- a/docs/modules/ROOT/pages/servlet/authentication/rememberme.adoc +++ b/docs/modules/ROOT/pages/servlet/authentication/rememberme.adoc @@ -50,7 +50,7 @@ If you have more than one in your application context, you need to specify which [[remember-me-persistent-token]] == Persistent Token Approach -This approach is based on the article https://web.archive.org/web/20180819014446/http://jaspan.com/improved_persistent_login_cookie_best_practice[Improved Persistent Login Cookie Best Practice] with some minor modifications footnote:[Essentially, the username is not included in the cookie, to prevent exposing a valid login name unecessarily. +This approach is based on the article https://web.archive.org/web/20180819014446/http://jaspan.com/improved_persistent_login_cookie_best_practice[Improved Persistent Login Cookie Best Practice] with some minor modifications footnote:[Essentially, the username is not included in the cookie, to prevent exposing a valid login name unnecessarily. There is a discussion on this in the comments section of this article.]. To use this approach with namespace configuration, you would supply a datasource reference: diff --git a/docs/modules/ROOT/pages/servlet/authentication/runas.adoc b/docs/modules/ROOT/pages/servlet/authentication/runas.adoc index ff8ec87555c..d9c192cb2da 100644 --- a/docs/modules/ROOT/pages/servlet/authentication/runas.adoc +++ b/docs/modules/ROOT/pages/servlet/authentication/runas.adoc @@ -12,7 +12,7 @@ Because Spring Security provides a number of helper classes that automatically c [[runas-config]] == Configuration -Spring Security provices a `RunAsManager` interface: +Spring Security provides a `RunAsManager` interface: [source,java] ---- diff --git a/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc b/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc index 7d827291a19..f3b9d832d40 100644 --- a/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc +++ b/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc @@ -796,7 +796,7 @@ In-memory filtering can obviously be expensive, and so be considerate of whether === Authorizing Method Invocation with `@Secured` javadoc:org.springframework.security.access.annotation.Secured[format=annotation] is a legacy option for authorizing invocations. -<> supercedes it and is recommended instead. +<> supersedes it and is recommended instead. To use the `@Secured` annotation, you should first change your Method Security declaration to enable it like so: diff --git a/docs/modules/ROOT/pages/servlet/saml2/metadata.adoc b/docs/modules/ROOT/pages/servlet/saml2/metadata.adoc index 9a0c557a8ad..af01ba65a34 100644 --- a/docs/modules/ROOT/pages/servlet/saml2/metadata.adoc +++ b/docs/modules/ROOT/pages/servlet/saml2/metadata.adoc @@ -120,7 +120,7 @@ class RefreshableRelyingPartyRegistrationRepository : IterableRelyingPartyRegist ====== [TIP] -`OpenSaml4AssertingPartyMetadataRepository` also ships with a constructor so you can provide a custom `MetadataResolver`. Since the underlying `MetadataResolver` is doing the expirying and refreshing, if you use the constructor directly, you will only get these features by providing an implementation that does so. +`OpenSaml4AssertingPartyMetadataRepository` also ships with a constructor so you can provide a custom `MetadataResolver`. Since the underlying `MetadataResolver` is doing the expiring and refreshing, if you use the constructor directly, you will only get these features by providing an implementation that does so. === Verifying Metadata Signatures