docs(guides:auth): correct information about oat

insus-tecnologia · May 21, 2021 · 5149182 · 5149182
1 parent ce757b2
commit 5149182
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 3 deletions.
diff --git a/content/guides/auth/api-tokens-guard.md b/content/guides/auth/api-tokens-guard.md
@@ -2,9 +2,13 @@
 summary: Authenticate requests using Opaque access tokens
 ---
 
-The API guard uses the database backend **opaque access token** to authenticate the user requests.
+The API guard uses an **opaque access token** to authenticate the user requests. You may want to use the api guard when **creating an API that should be accessed by third-party client**, or for **any other system that does not support cookies**.
 
-You must use this guard to implement stateless authentication, meaning no state is stored inside cookies or sessions by the AdonisJS application. Also, with stateless authentication, it is the responsibility of the client to keep the tokens secure.
+:::note
+
+It is the responsibility of the client to keep the tokens secure.
+
+:::
 
 ## Tokens storage
 The API tokens guard allows you store tokens either in a SQL database or store them inside Redis. Both the storage options have their own use cases.

diff --git a/content/guides/auth/web-guard.md b/content/guides/auth/web-guard.md
@@ -2,7 +2,7 @@
 summary: Authenticate requests using session and cookies
 ---
 
-The web guard uses sessions/cookies to login a user. You must use the web guard when **creating a server rendered application**, or even for an **SPA running on same domain/sub-domain**.
+The web guard uses sessions/cookies to login a user. You must use the web guard when **creating a server rendered application**, or for **an API having a first-party client running on the same domain/sub-domain**.
 
 :::note