plhery
diff --git a/‎doc/auth.md‎
Lines changed: 3 additions & 3 deletions b/‎doc/auth.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎doc/examples.md‎
Lines changed: 19 additions & 1 deletion b/‎doc/examples.md‎
Lines changed: 19 additions & 1 deletion
@@ -246,17 +246,17 @@ app.get('/callback', (req, res) => {
 The `.loginWithOAuth2()` method already returns a logged client, but if you want to create an instance by yourself with an access token (for example to use your refresh token), use it as a **Bearer token**.
 
 ```ts
-const client = new TwitterApi('<YOUR_ACCESS_TOKEN>');
+const client = new TwitterApi('<YOUR-ACCESS-TOKEN>');
 ```
 
 ### Optional: refresh the token later
 
 If you choose to include `'offline.access'` as scope, you can store and re-use later `refreshToken` when `expiresIn` time kicks in.
 
 ```ts
-// Obtain the couple {accessToken} + {refreshToken} from your DB/store
-const client = new TwitterApi(accessToken);
+const client = new TwitterApi({ clientId: '<YOUR-CLIENT-ID>', clientSecret: '<YOUR-CLIENT-SECRET>' });
 
+// Obtain the {refreshToken} from your DB/store
 const { client: refreshedClient, accessToken, refreshToken: newRefreshToken } = await client.refreshOAuth2Token(refreshToken);
 
 // Store refreshed {accessToken} and {newRefreshToken} to remplace the old ones
 
@@ -15,11 +15,14 @@ For each implemented endpoint, you have a link to documentation available in JSD
 
 ### With user credentials (act as a logged user)
 
-This kind of auth is needed for endpoint mentionned with `"OAuth 1.0a User context"` in Twitter documentation.
+This kind of auth is needed for endpoint mentionned with `"OAuth 1.0a User context"` or `"OAuth 2.0 Authorization Code with PKCE"` in Twitter documentation.
 Usually, this is used to act on behalf of a user.
 
 Access token and access secret are obtained through [the 3-legged auth flow](./auth.md).
 
+- OAuth 1.0a User context
+
+This authentification method requires to use a couple of 4 keys, 2 are your app keys and 2 are obtained with the 3-legged auth flow.
 ```ts
 const client = new TwitterApi({
   appKey: '<YOUR-TWITTER-APP-TOKEN>',
@@ -30,6 +33,21 @@ const client = new TwitterApi({
 // NOTE: accessToken and accessSecret are not required if you want to generate OAuth login links.
 ```
 
+- OAuth 2.0 Authorization Code with PKCE
+
+This authentification method only requires to use the obtained **access token** with the 3-legged OAuth2 auth flow.
+```ts
+const client = new TwitterApi('<YOUR-ACCESS-TOKEN>');
+```
+
+If your access token is no longer valid, but your have a refresh token (you specified `offline.access` in scope array), you can ask for a new access token with your client keys:
+```ts
+const client = new TwitterApi({ clientId: '<YOUR-CLIENT-ID>', clientSecret: '<YOUR-CLIENT-SECRET>' });
+const { client: refreshedClient, accessToken, refreshToken } = await client.refreshOAuth2Token('<YOUR-REFRESH-TOKEN>');
+
+// Use {refreshedClient}, and save {accessToken} and {refreshToken} in your storage to use them later
+```
+
 ### With app-only credentials
 
 This kind of auth is accepted on Twitter endpoints with `"OAuth 2.0 Bearer token"` (or Application context) mentionned in documentation.