From 0845e951e19dc884e67f761d0c225754dd32e0cf Mon Sep 17 00:00:00 2001
From: ClaireM <127452294+clairekinde11@users.noreply.github.com>
Date: Thu, 2 Oct 2025 10:42:11 +1000
Subject: [PATCH] Update refresh-tokens.mdx

---
 src/content/docs/build/tokens/refresh-tokens.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/build/tokens/refresh-tokens.mdx b/src/content/docs/build/tokens/refresh-tokens.mdx
index 662fe7775..4f234755e 100644
--- a/src/content/docs/build/tokens/refresh-tokens.mdx
+++ b/src/content/docs/build/tokens/refresh-tokens.mdx
@@ -85,7 +85,7 @@ Kinde allows a small overlap period when both a previous and new refresh token i
 
 You should store the refresh token you get with your initial `/token` request. Otherwise, your user will need to go through the sign in process again, to get a new access token.
 
-## Refresh tokens when you are using a front-end SDK
+## Use the SDK `getToken` function to silently refresh tokens
 
 If you’re using a front-end SDK like [JavaScript](/developer-tools/sdks/frontend/javascript-sdk/) or [React](/developer-tools/sdks/frontend/react-sdk/), the `getToken` function stores an in-memory cache of the access token, which it returns by default. If the token is about to expire it will use a refresh token to get a new access token from Kinde silently in the background so additional network requests to Kinde are only made when absolutely necessary.