Fix docs issues

Author: sam-muncke

examples/ConnectedAccounts.md

@@ -4,15 +4,15 @@ The Connect Accounts feature uses the Auth0 My Account API to allow users to lin
 
 When using Connected Accounts, Auth0 acquires tokens from upstream Identity Providers (like Google) and stores them in a secure [Token Vault](https://auth0.com/docs/secure/tokens/token-vault). These tokens can then be used to access third-party APIs (like Google Calendar) on behalf of the user.
 
-The tokens in the Token Vault are then accessible to [Resource Servers](https://auth0.com/docs/get-started/apis) (APIs) configured in Auth0. The SPA application can then issue requests to the API, which can retrieve the tokens from the Token Vault and use them to access the third-party APIs.
+The tokens in the Token Vault are then accessible to [Resource Servers](https://auth0.com/docs/get-started/apis) (APIs) configured in Auth0. The application can then issue requests to the API, which can retrieve the tokens from the Token Vault and use them to access the third-party APIs.
 
 This is particularly useful for applications that require access to different resources on behalf of a user, like AI Agents.
 
 ## Configure the SDK
 
 The SDK must be configured with an audience (an API Identifier) - this will be the resource server that uses the tokens from the Token Vault.
 
-The Auth0 client Application must be configured to use refresh tokens and MRRT (Multiple Resource Refresh Tokens) since we will use the refresh token grant to get Access Tokens for the My Account API in addition to the API we are calling.
+The Auth0 client Application must be configured to use refresh tokens and [MRRT (Multiple Resource Refresh Tokens)](https://auth0.com/docs/secure/tokens/refresh-tokens/multi-resource-refresh-token) since we will use the refresh token grant to get Access Tokens for the My Account API in addition to the API we are calling.
 
 ```python
 server_client = ServerClient(
@@ -22,6 +22,7 @@ server_client = ServerClient(
     secret="YOUR_SECRET",
     authorization_params={
         "redirect_uri":"YOUR_CALLBACK_URL",
+        "audience": "YOUR_API_IDENTIFIER"
     }
 )
 ```
@@ -37,8 +38,7 @@ authorization_url = await server_client.start_interactive_login(
     {
         "authorization_params": {
             # must include offline_access to obtain a refresh token
-            "scope": "openid profile email offline_access", 
-            "audience": "YOUR_API_IDENTIFIER",
+            "scope": "openid profile email offline_access"
         }
     },
     store_options={"request": request, "response": response}
@@ -53,11 +53,11 @@ result = await server_client.complete_interactive_login(
 )
 ```
 
-## Connect to a third party account
+## Connect to a third-party account
 
-Start the flow using the `start_connect_account` method to redirect the user to the third party Identity Provider to connect their account.
+Start the flow using the `start_connect_account` method to redirect the user to the third-party Identity Provider to connect their account.
 
-The `authorization_params` is used to pass additional parameters required by the third party IdP
+The `authorization_params` is used to pass additional parameters required by the third-party IdP
 The `app_state` parameter allows you to pass custom state (for example, a return URL) that is later available when the connect process completes.
 
 ```python
@@ -79,11 +79,11 @@ connect_url = await self.client.start_connect_account(
 )
 ```
 
-Using the url returned, redirect the user to the third party Identity Provider to complete any required authorization. Once authorized, the user will be redirected back to the provided `redirect_uri` with a `connect_code` and `state` parameter.
+Using the url returned, redirect the user to the third-party Identity Provider to complete any required authorization. Once authorized, the user will be redirected back to the provided `redirect_uri` with a `connect_code` and `state` parameter.
 
 ## Complete the account connection
 
-Call the `complete_connect_account` method using the full callback url returned from the third party IdP to complete the connected account flow. This method extracts the connect_code from the URL, completes the connection, and returns the response data (including any `app_state` you passed originally).
+Call the `complete_connect_account` method using the full callback url returned from the third-party IdP to complete the connected account flow. This method extracts the connect_code from the URL, completes the connection, and returns the response data (including any `app_state` you passed originally).
 
 ```python
 complete_response = await self.client.complete_connect_account(
@@ -95,4 +95,4 @@ complete_response = await self.client.complete_connect_account(
 >[!NOTE]
 >The `callback_url` must include the necessary parameters (`state` and `connect_code`) that Auth0 sends upon successful authentication.
 
-You can now call the API with your access token and the API can use [Access Token Exchange with Token Vault](https://auth0.com/docs/secure/tokens/token-vault/access-token-exchange-with-token-vault) to get tokens from the Token Vault to access third party APIs on behalf of the user.
+You can now call the API with your access token and the API can use [Access Token Exchange with Token Vault](https://auth0.com/docs/secure/tokens/token-vault/access-token-exchange-with-token-vault) to get tokens from the Token Vault to access third-party APIs on behalf of the user.