Update FAQ.md

Co-authored-by: Adam Mcgrath <[email protected]>
auth0 · Sep 15, 2023 · 4031b99 · 4031b99
1 parent c6a8e70
commit 4031b99
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/FAQ.md b/FAQ.md
@@ -107,4 +107,4 @@ Authentication is about who you are (id token), not what you can do (access toke
 So even when the refresh token fails, or `getTokenSilently` returns nothing, that doesn't impact the existence of the id token, and as a consequence of that, the authentication state. So it's expected for isAuthenticated to stay true in that case.
 
 On top of that, the SDK can have multiple access tokens and multiple refresh tokens (e.g. when using multiple audience and scope combinations to call multiple API's), but only one id token.
-If there are multiple access and refresh tokens, and one of the refresh tokens fails, it doesnt mean the other access tokens or refresh tokens are invalid and they might still be perfectly usable.
+If there are multiple access and refresh tokens, and one of the refresh tokens fails, it doesn't mean the other access tokens or refresh tokens are invalid, they might still be perfectly usable.