Some more docs updates

Author: dannyroosevelt

docs-v2/pages/connect/api.mdx

@@ -104,7 +104,7 @@ export default function Home() {
 
 ## External users
 
-When you use the Connect API, you'll pass an `external_id` parameter when initiating account connections and retrieving credentials. This is your user's ID, in your system — whatever you use to uniquely identify them. 
+When you use the Connect API, you'll pass an `external_user_id` parameter when initiating account connections and retrieving credentials. This is your user's ID, in your system — whatever you use to uniquely identify them. 
 
 Pipedream associates this ID with user accounts, so you can retrieve credentials for a specific user, and invoke workflows on their behalf.
 
@@ -114,7 +114,7 @@ External IDs are limited to 250 characters.
 
 | API Endpoint               | Rate Limit                                           |
 |----------------------------|------------------------------------------------------|
-| `POST /tokens`   | 100 requests per minute per `external_id`            |
+| `POST /tokens`   | 100 requests per minute per `external_user_id`            |
 | `GET */accounts/*`| The sum of requests across all `*/accounts/*` endpoints must not exceed 100 requests per minute. This includes requests to `/accounts`, `/apps/:app_id/accounts`, `/accounts/:account_id`, and more — any request for account metadata and credentials is counted towards this total. |
 
 If you need higher rate limits, please [reach out](https://pipedream.com/support).
@@ -722,7 +722,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{project_id}/accounts/{account
 Retrieve the account details for a specific account based on the external user ID
 
 ```
-GET /{project_id}/users/{external_id}/accounts
+GET /{project_id}/users/{external_user_id}/accounts
 ```
 
 ##### Path parameters
@@ -733,7 +733,7 @@ GET /{project_id}/users/{external_id}/accounts
 
 ---
 
-`external_id` **string**
+`external_user_id` **string**
 
 [The external user ID](#external-users) in your system that you want to retrieve accounts for.
 
@@ -1095,7 +1095,7 @@ Pipedream returns a `204 No Content` response on successful account deletion
 Delete an end user and all their connected accounts
 
 ```
-DELETE /{project_id}/users/{external_id}
+DELETE /{project_id}/users/{external_user_id}
 ```
 
 ##### Path parameters
@@ -1106,7 +1106,7 @@ DELETE /{project_id}/users/{external_id}
 
 ---
 
-`external_id` **string**
+`external_user_id` **string**
 
 [The external user ID](#external-users) in your system
 
@@ -1162,7 +1162,7 @@ curl -X POST https://api.pipedream.com/v1/oauth/token \
 
 # The response will include an access_token. Use it in the Authorization header below.
 
-curl -X DELETE "https://api.pipedream.com/v1/connect/{project_id}/users/{external_id}" \
+curl -X DELETE "https://api.pipedream.com/v1/connect/{project_id}/users/{external_user_id}" \
   -H "Authorization: Bearer {access_token}"
 ```
 </Tabs.Tab>

docs-v2/pages/connect/environments.mdx

@@ -2,7 +2,7 @@
 
 Pipedream Connect projects support two environments: `development` and `production`.
 
-1. Credentials stored in `development` remain separate from `production`.
+1. Connected accounts and credentials stored in `development` remain separate from `production`.
 2. In `development`, you can use the official Pipedream OAuth apps, so you can test integrations without creating your own OAuth client.
 
 ## How to specify environment

docs-v2/pages/connect/quickstart.mdx

@@ -103,6 +103,10 @@ If you're using a different server / API framework, you'll need to make secure c
 
 Once you have a token, return it to your frontend to start the account connection flow for the user, or redirect them to a Pipedream-hosted URL with [Connect Link](#use-connect-link).
 
+<Callout type="info">
+Refer to the API docs for [all the parameters you can pass](/connect/api#create-a-new-token) in the `ConnectTokenCreate` call.
+</Callout>
+
 ### Connect a user's account
 
 To connect a third-party account for a user, you have two options:

docs-v2/pages/workflows/triggers.mdx

@@ -115,6 +115,8 @@ To configure a static, custom token for HTTP auth:
 2. Select **Custom token**.
 3. Enter whatever secret you'd like and click **Save and Continue**.
 
+![Custom token auth](https://res.cloudinary.com/pipedreamin/image/upload/v1729791152/Google_Chrome_-_Untitled_Workflow_-_10-24-2024_10-30_AM_-_Build_-_Pipedream_2024-10-24_at_10.31.01_AM_pkh8dk.png)
+
 When making HTTP requests, pass the custom token as a `Bearer` token in the `Authorization` header:
 
 ```bash
@@ -129,6 +131,8 @@ You can also authorize requests using [Pipedream OAuth clients](/rest-api/auth#o
 2. Select **OAuth**.
 3. If you don't have an existing OAuth client, [create one in your workspace's API settings](/rest-api/auth#creating-an-oauth-application).
 
+![OAuth authorization](https://res.cloudinary.com/pipedreamin/image/upload/v1729791415/Google_Chrome_-_Untitled_Workflow_-_10-24-2024_10-30_AM_-_Build_-_Pipedream_2024-10-24_at_10.36.04_AM_ujx34e.png)
+
 Next, you'll need to [generate an OAuth access token](/rest-api/auth#how-to-get-an-access-token).
 
 When making HTTP requests, pass the OAuth access token as a `Bearer` token in the `Authorization` header: