docs: update and move description for Authenticators

Author: kenjis

docs/getting_started/authenticators.md

@@ -5,9 +5,10 @@
 Shield provides the following Authenticators:
 
 - **Session** authenticator provides traditional ID/Password authentication.
-  See [Using Session Authenticator](../quick_start_guide/using_session_auth.md)
-  for usage.
-- **AccessTokens** authenticator provides stateless authentication using Personal Access Tokens.
+  It uses username/email/password to authenticate against and stores the user
+  information in the session. See [Using Session Authenticator](../quick_start_guide/using_session_auth.md) for usage.
+- **AccessTokens** authenticator provides stateless authentication using Personal
+  Access Tokens passed in the HTTP headers.
   See [Protecting an API with Access Tokens](../guides/api_tokens.md) for usage.
 - **HmacSha256** authenticator provides stateless authentication using HMAC Keys.
   See [Protecting an API with HMAC Keys](../guides/api_hmac_keys.md) for usage.

docs/references/authentication.md

@@ -6,9 +6,8 @@ web apps and APIs.
 
 ## Available Authenticators
 
-Shield ships with 2 authenticators that will serve several typical situations within web app development: the
-Session authenticator, which uses username/email/password to authenticate against and stores it in the session,
-and the Access Tokens authenticator which uses private access tokens passed in the headers.
+Shield ships with 4 authenticators that will serve several typical situations within web app development.
+You can see the [Authenticator List](../getting_started/authenticators.md).
 
 The available authenticators are defined in `Config\Auth`:
 
@@ -18,6 +17,7 @@ public $authenticators = [
     'session' => Session::class,
     'tokens'  => AccessTokens::class,
     'hmac'    => HmacSha256::class,
+    // 'jwt'  => JWT::class,
 ];
 ```