docs(pricing-may-2026): polish pass on umbrella PR #119

src/content/docs/agent-platform/cloud-agents/overview.mdx

@@ -128,7 +128,7 @@ Integrations require you to be part of a [Warp team](/knowledge-and-collaboratio
 * **Plan requirements**
   * **Supported plans**: Build, Max, Business
   * Not supported: Pro, Turbo, Lightspeed, legacy Business
-  * Your plan must support Add-on Credits.
+  * Your plan must support add-on credits.
 * **Credit requirements**
   * Your team must have at least 20 credits available to run cloud agents and integrations.
 

src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx

@@ -76,7 +76,7 @@ Integrations and [cloud agents](/agent-platform/cloud-agents/overview/) run insi
 
 Your team must meet the following requirements to run integrations:
 
-* You must be on a **Build, Max, or Business** plan with [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) enabled, or on an **Enterprise** plan with a team credit pool per your contract.
+* You must be on a **Build, Max, or Business** plan with [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) enabled, or on an **Enterprise** plan with a team credit pool per your contract.
 * Your team needs at least **20 credits** available to run cloud agents and integrations
 
 When a user triggers an agent through an integration (like Slack or Linear), the run draws from credits based on who the run is billed to:
@@ -85,7 +85,7 @@ When a user triggers an agent through an integration (like Slack or Linear), the
 * **Team API key or scheduled cloud agent runs on Build, Max, or Business** - Warp bills the team owner. The waterfall is: the owner's plan-included credits, then the owner's Add-on credits. With auto-reload off, the request is blocked when both pools are depleted. With auto-reload on, usage can trigger a reload on the owner's pool subject to the team-wide monthly spend cap.
 * **Enterprise plans** - Runs draw from the team-scoped credit pool, per your Enterprise contract terms.
 
-If all applicable credit sources are exhausted and no auto-reload is configured, integrations and cloud agents will not run until credits are added. See [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve waterfall and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the third bucket that applies to every cloud agent run.
+If all applicable credit sources are exhausted and no auto-reload is configured, integrations and cloud agents will not run until credits are added. See [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve waterfall and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the third bucket that applies to every cloud agent run.
 
 :::note
 If you're on an Enterprise plan, please reach out to [warp.dev/contact-sales](https://www.warp.dev/contact-sales) with any billing questions related to integrations.
@@ -253,6 +253,6 @@ It's the team's responsibility to manage triggers, confirm they behave as intend
 
 ## Related resources
 
-* [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) - How user-scoped Add-on credits, auto-reload, and the team-wide spend cap work on self-serve plans.
+* [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) - How user-scoped add-on credits, auto-reload, and the team-wide spend cap work on self-serve plans.
 * [Platform credits](/support-and-community/plans-and-billing/platform-credits/) - The third credit bucket that applies to every cloud agent run, alongside AI credits and compute credits.
 * [Credits overview](/support-and-community/plans-and-billing/credits/) - The full credit model across plans.

src/content/docs/agent-platform/getting-started/faqs.mdx

@@ -52,7 +52,7 @@ To fix this, try:
 
 #### "Monthly request limit exceeded" or "Monthly credit limit exceeded" errors
 
-Once you exceed your monthly credit limit (see [pricing](https://www.warp.dev/pricing) for current limits), premium models will be disabled until your quota resets at the start of your next billing cycle. On paid plans with Add-on Credits, you can continue using AI with usage-based billing.
+Once you exceed your monthly credit limit (see [pricing](https://www.warp.dev/pricing) for current limits), premium models will be disabled until your quota resets at the start of your next billing cycle. On paid plans with add-on credits, you can continue using AI with usage-based billing.
 
 **Request failed with error: QuotaLimit**
 

src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx

@@ -15,7 +15,7 @@ BYOK provides greater flexibility in model access and ensures Warp **never consu
 BYOK is available on Free and all eligible paid plans for individual users and organizations with 10 or fewer employees, subject to Warp's [Terms of Service](https://www.warp.dev/terms-of-service). Larger organizations need a Business or Enterprise plan. See [warp.dev/pricing](https://www.warp.dev/pricing) for current availability.
 :::
 
-## How BYOK differs from Custom inference endpoint and BYOLLM
+## How BYOK differs from custom inference endpoints and BYOLLM
 
 Warp offers three ways to bring your own AI infrastructure. Use this table to pick the right one, and follow the links for full details.
 
@@ -102,7 +102,8 @@ If your key:
 
 * Is invalid: Warp notifies you and halts the request.
 * Hits usage or rate limits: Warp will not retry using credits.
-* You can update or replace your keys anytime by opening **Settings** and searching for `API keys`.
+
+You can update or replace your keys anytime by opening **Settings** and searching for `API keys`.
 
 **Failover and fallback:**
 

src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx

@@ -32,7 +32,7 @@ A custom inference endpoint expects your endpoint to implement the **OpenAI Chat
 When you configure a custom inference endpoint, Warp stores the endpoint URL, model identifiers, and credentials **locally on your device**. They are never synced to Warp's servers.
 
 :::caution
-Custom inference endpoints don't apply to [Oz Cloud Agents](/agent-platform/cloud-agents/overview/). Because the configuration is stored locally, it isn't available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/).
+Custom inference endpoints don't apply to [Cloud Agents](/agent-platform/cloud-agents/overview/). Because the configuration is stored locally, it isn't available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/).
 :::
 
 When a model routed through your endpoint is selected:
@@ -72,7 +72,7 @@ To use your endpoint, select the specific endpoint-routed model from the model p
 
 ### Other AI features in Warp
 
-Some AI-powered features rely on Warp's infrastructure and are unaffected by a custom inference endpoint. These continue to consume credits according to your plan; see [Credits](/support-and-community/plans-and-billing/credits/) for details.
+Some AI-powered features (Codebase Context, Active AI recommendations, cloud agent runs) rely on Warp's infrastructure and are unaffected by a custom inference endpoint. See the [feature breakdown on the BYOK page](/agent-platform/inference/bring-your-own-api-key/#byok-usage-and-billing-behavior) for which features still consume Warp credits.
 
 ## Zero Data Retention (ZDR)
 

src/content/docs/enterprise/support-and-resources/billing.mdx

@@ -70,7 +70,7 @@ Enterprise administrators can set monthly spending limits across the following f
 * **Total spending limit** - Cap combined monthly spend across both cloud and local agents.
 * **Per-user spending limit** - Cap monthly spend for any individual user. Set a default that applies to all users, or configure limits on a per-user basis for predictable individual spend.
 
-Spending is tracked across all payment types (Add-on Credits, pay-as-you-go usage) so limits apply consistently regardless of how usage is funded.
+Spending is tracked across all payment types (add-on credits, pay-as-you-go usage) so limits apply consistently regardless of how usage is funded.
 
 :::note
 Team-wide spending limits (cloud, local, and total) are also available on Warp's self-serve paid plans through admin-managed Add-on credit settings. **Per-user spending limits are Enterprise-only.** For deeper visibility into how individual users consume credits, see the [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/).
@@ -87,7 +87,7 @@ For enterprises with credit pools, administrators receive alerts as the team cre
 ## Related resources
 
 * [Credits](/support-and-community/plans-and-billing/credits/) - How credits are calculated and consumed
-* [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits and configure auto-reload
+* [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits and configure auto-reload
 * [platform credits](/support-and-community/plans-and-billing/platform-credits/) - The third credit bucket alongside AI credits and compute credits, covering Warp's platform infrastructure
 * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) - Common billing questions
 * [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) - BYOLLM billing and configuration

src/content/docs/enterprise/team-management/teams.mdx

@@ -21,7 +21,6 @@ Each Warp user can be an admin or member of one team at a time.
 
 You can create a new team in two ways:
 
-{/* TODO: Add screenshots for both team creation entry points */}
 * From the **Warp Drive** side panel, click **+ Create a team**.
 * In Warp, navigate to **Settings** > **Teams** and follow the prompts.
 
@@ -64,15 +63,15 @@ If you've received an invite link, use it to sign up or log in and join the team
 If you're a Team Owner and choose to [delete your Warp account](/support-and-community/privacy-and-security/privacy/#delete-your-account-and-data), you'll need to assign a team member as the new owner before your account can be deleted.
 :::
 
-### Reload credit consequences when leaving or removing members
+### Add-on credit consequences when leaving or removing members
 
-On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access:
+On Build, Max, and Business plans, [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access:
 
-* **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin.
-* **A user leaves a team** - They lose access to any Reload credits tied to that team. If they rejoin the same team later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins.
-* **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable.
+* **A user leaves a team** - You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin.
+* **An admin removes a member** - That member loses access to any add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins.
+* **An admin deletes the team** - Any remaining add-on credits tied to the team are no longer usable.
 
-Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team.
+Add-on credits require an active subscription. Downgrading to the Free plan forfeits access to add-on credits tied to your team.
 
 ## Team discoverability
 
@@ -88,7 +87,6 @@ While discoverability is enabled, any new user who joins the team will add a pro
 
 Team Owners can transfer ownership to another team member:
 
-{/* TODO: Add screenshot of transfer ownership flow */}
 1. Navigate to **Settings** > **Teams** > **Team Members**.
 2. Click the three-dot menu icon next to the member you want to transfer ownership to.
 3. Click **Transfer ownership**.
@@ -113,13 +111,13 @@ We recommend having at least one Team Admin in addition to the Team Owner to pre
 
 ### Permissions overview
 
-|  | Owner | Admin | Member |
+| Action | Owner | Admin | Member |
 | --- | --- | --- | --- |
-|| Create a team | ✓ | ✓ | ✓ |
+| Create a team | ✓ | ✓ | ✓ |
 | Restrict invites by domain | ✓ | ✓ | |
 | Invite members | ✓ | ✓ | ✓ |
 | Remove team members | ✓ | ✓ | |
-|| Leave a team | | ✓ | ✓ |
+| Leave a team | | ✓ | ✓ |
 | Delete a team | ✓ | | |
 | Transfer ownership | ✓ | | |
 | Promote/demote admins | ✓ | ✓ | |
@@ -132,7 +130,6 @@ Teams on the **Enterprise** plan can have multiple admins, enabling distributed
 
 To promote or demote a team admin:
 
-{/* TODO: Add screenshot of promote/demote admin flow */}
 1. Navigate to **Settings** > **Teams** > **Team Members**.
 2. Find the user you want to modify and click the three-dot menu icon next to their name.
 3. Click **Promote to Admin** or **Demote from Admin**.

src/content/docs/knowledge-and-collaboration/teams.mdx

@@ -24,10 +24,10 @@ You can create a new team in the following ways:
 * Warp Drive, + Create a team
 * **Settings** > **Teams**
 
-Before you can invite team members, you will need to give your team a meaningful name. We suggest using a name to represent your organization, company, or project. 
+Before you can invite team members, you will need to give your team a meaningful name. We suggest using a name to represent your organization, company, or project.
 
 :::note
-You can rename the team by going to **Settings** > **Teams** and clicking on the team name, entering the new name, and pressing `ENTER` to accept.
+You can rename the team by going to **Settings** > **Teams** and clicking on the team name, entering the new name, and pressing `Enter` to accept.
 :::
 
 ![Teams settings panel with a team name input field and Create button](../../../assets/terminal/team-creation-settings.png)
@@ -67,13 +67,13 @@ If you have received an invite link, you can use that link to sign up or log in
 
 If you’re a member of a team, you can visit **Settings** > **Teams** to leave a team at any time. Team admins (who created teams) may delete a team only after removing all team members.
 
-On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access:
+On Build, Max, and Business plans, [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access:
 
-* **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin.
-* **A user leaves a team** - They lose access to any Reload credits tied to that team. If they rejoin the same team later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins.
-* **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable.
+* **A user leaves a team** - You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin.
+* **An admin removes a member** - That member loses access to any add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins.
+* **An admin deletes the team** - Any remaining add-on credits tied to the team are no longer usable.
 
-Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team.
+Add-on credits require an active subscription. Downgrading to the Free plan forfeits access to add-on credits tied to your team.
 
 ## Team discoverability
 
@@ -93,14 +93,14 @@ Team admins can transfer their role to another team member by going to **Setting
 If you're a Team admin, and you choose to [delete your Warp](/support-and-community/privacy-and-security/privacy/#manage-your-data) account, the deletion flow will require that you assign a team member as the new admin.
 :::
 
-|                                                               | Admin                                                            | Member                                 |
-| ------------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------- |
-|                                                               | This is the Warp user who created a team. There can only be one. | All team members who belong to a team. |
-| Create a team                                                 | ✓                                                                |                                        |
-| Restrict by domain                                            | ✓                                                                |                                        |
-| Invite members                                                | ✓                                                                | ✓                                      |
-| Remove team members                                           | ✓                                                                |                                        |
-| Leave a team                                                  |                                                                  | ✓                                      |
-| Delete a team                                                 | ✓                                                                |                                        |
-| Transfer admin                                                | ✓                                                                |                                        |
-| [Manage billing](/support-and-community/plans-and-billing/plans-pricing-refunds/) | ✓                                                                |                                        |
+| Action | Admin | Member |
+| --- | --- | --- |
+| Description | The Warp user who created the team. There can only be one. | Team members who belong to the team. |
+| Create a team | ✓ | |
+| Restrict by domain | ✓ | |
+| Invite members | ✓ | ✓ |
+| Remove team members | ✓ | |
+| Leave a team | | ✓ |
+| Delete a team | ✓ | |
+| Transfer admin | ✓ | |
+| [Manage billing](/support-and-community/plans-and-billing/plans-pricing-refunds/) | ✓ | |

src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx

@@ -52,7 +52,7 @@ Errors are split into two categories based on what caused the failure:
 
 These indicate something the caller needs to fix. When a cloud agent task encounters a user error, the task transitions to the **FAILED** state.
 
-* [`insufficient_credits`](/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/) — Team has no remaining Add-on Credits
+* [`insufficient_credits`](/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/) — Team has no remaining add-on credits
 * [`feature_not_available`](/reference/api-and-sdk/troubleshooting/errors/feature-not-available/) — Feature not included in your current plan
 * [`external_authentication_required`](/reference/api-and-sdk/troubleshooting/errors/external-authentication-required/) — External service authorization needed
 * [`not_authorized`](/reference/api-and-sdk/troubleshooting/errors/not-authorized/) — Insufficient permissions for the operation