Improve docs

Author: martinml

EXAMPLES.md

@@ -384,10 +384,10 @@ After enabling DPoP, **every new session using a supported OAuth 2.0 flow in Aut
 >
 > You decide how to handle this transition. For example, you might require users to log in again the next time they use your application.
 
-> [!IMPORTANT]
+> [!NOTE]
 > Using DPoP requires storing some temporary data in the user's browser. When you log the user out with `logout()`, this data is deleted.
 
-> [!IMPORTANT]
+> [!TIP]
 > If all your clients are already using DPoP, you may want to increase security by making Auth0 reject any non-DPoP interactions. See [the docs on Sender Constraining](https://auth0.com/docs/secure/sender-constraining/configure-sender-constraining) for details.
 
 ### Using DPoP in your own requests

src/auth0-context.tsx

@@ -158,7 +158,7 @@ export interface Auth0ContextInterface<TUser extends User = User>
   getDpopNonce: Auth0Client['getDpopNonce'];
 
   /**
-   * Gets the current DPoP nonce used for making requests to Auth0.
+   * Sets the current DPoP nonce used for making requests to Auth0.
    *
    * It requires enabling the {@link Auth0ClientOptions.useDpop} option.
    *
@@ -177,6 +177,14 @@ export interface Auth0ContextInterface<TUser extends User = User>
    */
   generateDpopProof: Auth0Client['generateDpopProof'];
 
+  /**
+   * Returns a new `Fetcher` class that will contain a `fetchWithAuth()` method.
+   * This is a drop-in replacement for the Fetch API's `fetch()` method, but will
+   * handle certain authentication logic for you, like building the proper auth
+   * headers or managing DPoP nonces and retries automatically.
+   * 
+   * Check the `EXAMPLES.md` file for a deeper look into this method.
+   */
   createFetcher: Auth0Client['createFetcher'];
 }