From d78cc2f1fc6fdfe6a6ce875ea66eb36610de2750 Mon Sep 17 00:00:00 2001
From: Josselin Francois Downey <44689065+Jojofoulk@users.noreply.github.com>
Date: Fri, 15 Jan 2021 11:06:12 +1100
Subject: [PATCH] Fixed typo

Line 5: "an refresh token" should be "a refresh token"
---
 docs-src/token-refresh.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs-src/token-refresh.md b/docs-src/token-refresh.md
index 7a4e93dd..d79af269 100644
--- a/docs-src/token-refresh.md
+++ b/docs-src/token-refresh.md
@@ -2,7 +2,7 @@
 
 When using code flow, you can get an ``refresh_token``. While the original standard DOES NOT allow this for SPAs, the mentioned [OAuth 2.0 Security Best Current Practice](https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13) document proposes to ease this limitation. However, it specifies a list of requirements one should take care about before using ``refresh_tokens``. Please make sure you respect those requirements.
 
-Please also note, that you have to request the ``offline_access`` scope to get an refresh token.
+Please also note, that you have to request the ``offline_access`` scope to get a refresh token.
 
 To refresh your token, just call the ``refreshToken`` method: