docs: adds links and other helpful tips

Author: iOvergaard

16/umbraco-cms/customizing/foundation/fetching-data/README.md

@@ -25,7 +25,7 @@ Here is a quick overview of the two options for you to compare:
 | Error Handling         | Manual                       | Built-in                    |
 | Type Safety            | No                           | Yes                         |
 | Request Cancellation   | Yes (via AbortController)    | Yes (via AbortController)   |
-| Recommended Use Case   | Standard requests              | Complex or frequent requests|
+| Recommended Use Case   | Common requests | Complex or frequent requests |
 
 Once you have decided which option to use, you can read more about how to use it below. After that, you can read about how to work with the data you receive from the server.
 
@@ -39,6 +39,8 @@ The Umbraco HTTP Client is a wrapper around the Fetch API that provides a more c
 
 ## Handle Requests
 
+Once you have chosen a method to fetch data, the next step is to handle the execution of requests. This includes managing errors, refreshing tokens, and ensuring proper authentication.
+
 ## [Executing Requests](try-execute.md)
 
 Executing the request is the next step after fetching data. You can use the `tryExecute` function to handle errors and refresh the token if it is expired.
@@ -47,7 +49,7 @@ Executing the request is the next step after fetching data. You can use the `try
 
 ### [Custom Generated Client](custom-generated-client.md)
 
-It can be useful to generate a custom client for your API. This can save you a lot of time and effort when working with custom API controllers.
+For advanced scenarios, you can generate a custom client for your API using tools like **@hey-api/openapi-ts**. This approach is ideal when working with custom API controllers or when you need type-safe, reusable client code.
 
 ## Further Reading
 

16/umbraco-cms/customizing/foundation/fetching-data/custom-generated-client.md

@@ -30,6 +30,8 @@ npx openapi-ts generate --url https://example.com/openapi.json --output ./my-cli
 
 This will generate a TypeScript client in the `./my-client` folder. You can then import the client into your project and use it to make requests to the Management API.
 
+To learn more about OpenAPI and how to define your API specification, visit the [OpenAPI Documentation](https://swagger.io/specification/).
+
 ## Connecting to the Management API
 
 You will need to set up a few configuration options in order to connect to the Management API. The following options are required:

16/umbraco-cms/customizing/foundation/fetching-data/fetch-api.md

@@ -80,14 +80,18 @@ console.log(data);
 The example assumes that you have a valid authentication token. You can replace this with your own token as needed. Read more about authentication in the [Security](../../../implementation/security.md) article.
 {% endhint %}
 
+{% hint style="warning" %}
+When using the Fetch API with `UMB_AUTH_CONTEXT`, you need to handle token expiration errors manually. If the token is expired, the request will return a 401 error. You will need to refresh the token or prompt the user to log in again.
+{% endhint %}
+
 Why Use **UMB_AUTH_CONTEXT**?
 
 - Simplifies Token Management: Automatically retrieves and refreshes tokens when needed.
 - Aligns with Best Practices: Ensures your requests are authenticated in a way that integrates seamlessly with the Backoffice.
 - Reduces Errors: Avoids common pitfalls like expired tokens or incorrect headers.
 
 {% hint style="info" %}
-The **UMB_AUTH_CONTEXT** is only available in the Backoffice. For external applications, you will need to manage tokens manually or use an API user. Read more about API users in the [API Users article](../../../fundamentals/data/users/api-users.md).
+The **UMB_AUTH_CONTEXT** is only available in the Backoffice. For external applications, you will need to manage tokens manually or use an API user. Read more about API users in the [API Users](../../../fundamentals/data/users/api-users.md) article.
 {% endhint %}
 
 ## Management API Controllers

16/umbraco-cms/customizing/foundation/fetching-data/try-execute.md

@@ -35,7 +35,7 @@ The `tryExecute` function takes the context of the current class or element as t
 The above example requires a host element illustrated by the use of `this`. This is typically a custom element that extends the `UmbLitElement` class.
 {% endhint %}
 
-It is recommended to always use the `tryExecute` function to wrap HTTP requests.
+It is recommended to always use the `tryExecute` function to wrap HTTP requests. It simplifies error handling, manages token expiration, and ensures a consistent user experience in the Backoffice.
 
 ### Disable Notifications
 
@@ -47,9 +47,9 @@ tryExecute(this, request, {
 });
 ```
 
-### Cancelling requests
+### Cancelling Requests
 
-The `tryExecute` function also supports cancelling requests. This is useful if you want to cancel a request that is taking too long or if the user navigates away from the page. You can cancel a request by using the [AbortController API](https://developer.mozilla.org/en-US/docs/Web/API/AbortController). The `AbortController` API is a built-in API in modern browsers that allows you to cancel requests. You can use it directly with tryExecute:
+The `tryExecute` function also supports cancelling requests. This is useful in scenarios where a request is taking too long, or the user navigates away from the page before the request completes. You can cancel a request by using the [AbortController API](https://developer.mozilla.org/en-US/docs/Web/API/AbortController). The `AbortController` API is a built-in API in modern browsers that allows you to cancel requests. You can use it directly with tryExecute:
 
 ```javascript
 const abortController = new AbortController();