Skip to content
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.

Corrected small typos (fixes #6) #9

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Corrected small typos (fixes #6) #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ chain of `AccessDecisionVoter`, a bit like the `ProviderManager`
delegates to `AuthenticationProviders`.

An `AccessDecisionVoter` considers an `Authentication` (representing a
principal) and a secure `Object` which as been decorated with
principal) and a secure `Object` which has been decorated with
`ConfigAttributes`:

[source, java]
Expand Down Expand Up @@ -293,7 +293,7 @@ request.
image::{images}/security-filters-dispatch.png[Security Filter Dispatch,70%]

A vanilla Spring Boot application with no custom security
configuration has a several (call it n) filter chains, where usually
configuration has several (call it n) filter chains, where usually
n=6. The first (n-1) chains are there just to ignore static resource
patterns, like `/css/{all}` and `/images/{all}`, and the error view
`/error` (the paths can be controlled by the user with
Expand Down Expand Up @@ -510,7 +510,7 @@ the method parameter. The type of the `Principal` in an
`Authentication` is dependent on the `AuthenticationManager` used to
validate the authentication, so this can be a useful little trick to get a type safe reference to your user data.

If Spring Security is in use the `Principal` from the
If Spring Security is in use, the `Principal` from the
`HttpServletRequest` will be of type `Authentication`, so you can also
use that directly:

Expand Down