[shiro-site] branch master updated: Update authentication.md.vtl

[fp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

fpapon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shiro-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 5318f3c  Update authentication.md.vtl
     new a7513e1  Merge pull request #51 from Mccreew/patch-1
5318f3c is described below

commit 5318f3cc72bbd0485ecb3a0e4630fe12385e11ce
Author: Mccreew <30...@users.noreply.github.com>
AuthorDate: Wed Nov 20 11:08:04 2019 +0800

    Update authentication.md.vtl
    
    unnecessary "an"
---
 authentication.md.vtl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/authentication.md.vtl b/authentication.md.vtl
index 733cbfc..fcf352d 100644
--- a/authentication.md.vtl
+++ b/authentication.md.vtl
@@ -222,7 +222,7 @@ An AuthenticationStrategy is a stateless component that is consulted 4 times dur
 
 1.  before any of the Realms are invoked
 2.  immediately before an individual Realm's `getAuthenticationInfo` method is called
-3.  immediately after an an individual Realm's `getAuthenticationInfo` method is called
+3.  immediately after an individual Realm's `getAuthenticationInfo` method is called
 4.  after all of the Realms have been invoked
 
 Also an `AuthenticationStrategy` is responsible for aggregating the results from each successful Realm and 'bundling' them into a single [`AuthenticationInfo`](static/current/apidocs/org/apache/shiro/authc/AuthenticationInfo.html) representation. This final aggregate `AuthenticationInfo` instance is what is returned by the `Authenticator` instance and is what Shiro uses to represent the `Subject`'s final identity (aka Principals).