ArcadeAI · jakubvul · Nov 8, 2025 · Nov 8, 2025 · Nov 8, 2025 · Nov 8, 2025
diff --git a/app/en/home/agentic-development/page.mdx b/app/en/home/agentic-development/page.mdx
@@ -9,7 +9,7 @@ Give your AI IDE access to Arcade.dev's documentation using our [llms.txt](/llms
 
 ## LLMs.txt
 
-LLMs.txt is a file format that allows you to give your AI IDE access to Arcade.dev's documentation in a format that can be easily parsed by the LLM. All you need to do is paste in the conent of the file into your IDE's settings, or reference the docs, e.g. via [Cursor's `@docs` annotation](https://cursor.com/docs/context/symbols#docs).
+LLMs.txt is a file format that allows you to give your AI IDE access to Arcade.dev's documentation in a format that can be easily parsed by the LLM. All you need to do is paste in the content of the file into your IDE's settings, or reference the docs, e.g. via [Cursor's `@docs` annotation](https://cursor.com/docs/context/symbols#docs).
 
 Our LLMs.txt files are available at [`/llms.txt`](/llms.txt).
 

diff --git a/app/en/home/auth-providers/oauth2/page.mdx b/app/en/home/auth-providers/oauth2/page.mdx
@@ -11,8 +11,8 @@ import ToggleContent from "@/app/_components/toggle-content";
 The OAuth 2.0 auth provider enables tools and agents to authorize with any OAuth 2.0-compatible API on behalf of a user.
 
 <Callout>
-  Arcade has [pre-built integrations](/home/auth-providers) with many popular
-  OAuth 2.0 providers. Use this OAuth 2.0 provider to connect to other systems
+  Arcade has [pre-built auth providers](/home/auth-providers) for many popular
+  OAuth 2.0 services. Use this OAuth 2.0 provider to connect to other systems
   that aren't pre-built.
 </Callout>
 

diff --git a/app/en/home/auth-providers/page.mdx b/app/en/home/auth-providers/page.mdx
@@ -15,7 +15,7 @@ It can be useful to configure your own auth provider for the following reasons:
 
 - You want to use your own brand on the auth screen
 - You want to isolate your rate limits from other Arcade customers
-- You want to use a provider that Arcade [does not have a built-in integration for](/home/auth-providers/oauth2)
+- You want to use a service that Arcade [does not have a built-in auth provider for](/home/auth-providers/oauth2)
 
 After adding an auth provider used by an Arcade tool, executing the tool will automatically use your auth provider. Even in the Arcade Cloud Platform, your auth provider will take precedence over the arcade-provided auth provider.
 

diff --git a/app/en/home/auth-providers/zendesk/page.mdx b/app/en/home/auth-providers/zendesk/page.mdx
@@ -42,7 +42,7 @@ The following three guides from Zendesk will be helpful additional information a
 ### Creating a Zendesk app for Arcade
 
 1. Create your Organization in the [Zendesk Marketplace portal](https://apps.zendesk.com/).
-1. Create a Zendesk support account at https://www.zendesk.com/login . If you need a global OAuth client, then the subdomain MUST begin with "d3v-". You will need a global OAuth client if your app will use integrations/tools for multiple customers with their own Zendesk instances (multiple subdomains).
+1. Create a Zendesk support account at https://www.zendesk.com/login . If you need a global OAuth client, then the subdomain MUST begin with "d3v-". You will need a global OAuth client if your app will use tools for multiple customers with their own Zendesk instances (multiple subdomains).
 1. In [the Admin Center](https://support.zendesk.com/hc/en-us/articles/4581766374554#topic_hfg_dyz_1hb), click "Apps and integrations" in the sidebar, then select APIs > OAuth clients > Add OAuth client.
    - Ensure your identifier is prefixed with "zdg-" if you will need a global OAuth client.
    - Select "Public" for "Client kind".

diff --git a/app/en/home/build-tools/create-a-tool-with-auth/page.mdx b/app/en/home/build-tools/create-a-tool-with-auth/page.mdx
@@ -264,7 +264,7 @@ async with httpx.AsyncClient() as client:
 
 ## Key takeaways
 
-- **OAuth Integration:** Arcade handles OAuth flows and token management
+- **OAuth Support:** Arcade handles OAuth flows and token management
 - **Secure Token Injection:** Tokens are injected into context at runtime
 - **Scope Management:** Specify exactly which permissions your tool needs
 - **Provider Support:** Multiple OAuth providers available out of the box

diff --git a/app/en/home/changelog/page.mdx b/app/en/home/changelog/page.mdx
@@ -422,7 +422,7 @@ Self-hosed Arcade developers cannot be grandfathered into the old (insecure) beh
 
 **Platform and Engine**
 
-- `[feature - 🚀]` Concurrent auth requests for the same user and same scopes use the same authentication flow and URLs. This means that your users only have to authenticate once if the agent chooses to use multiple tools at once with teh same scopes.
+- `[feature - 🚀]` Concurrent auth requests for the same user and same scopes use the same authentication flow and URLs. This means that your users only have to authenticate once if the agent chooses to use multiple tools at once with the same scopes.
 - `[bugfix - 🐛]` Fix secret deletion
 
 **Cloud**

diff --git a/app/en/home/glossary/page.mdx b/app/en/home/glossary/page.mdx
@@ -190,7 +190,7 @@ _Learn more about [the Arcade clients](/references)._
 
 ### Arcade Engine
 
-The Arcade Engine is the core of the Arcade platform. It is responsible for routing tool execution requests to the correct worker, managing the lifecycle of tool executions, and for enforcing security and authorization decisions.
+The Arcade Engine is the core of the Arcade platform. It is responsible for routing tool execution requests to the correct MCP server, managing the lifecycle of tool executions, and for enforcing security and authorization decisions.
 
 The Arcade Engine is also responsible for the OAuth flow for your agent's users. This includes granting and elevating permissions and keeping tokens fresh.
 

diff --git a/app/en/home/oai-agents/user-auth-interrupts/page.mdx b/app/en/home/oai-agents/user-auth-interrupts/page.mdx
@@ -423,7 +423,7 @@ This example handles the authentication flow by:
 
 ## Authentication persistence
 
-Once a user authorizes an integration, Arcade will remember the authorization for that specific user_id and MCP Server. You don't need to re-authorize each time you run the agent.
+Once a user authorizes with an auth provider, Arcade will remember the authorization for that specific user_id and MCP Server. You don't need to re-authorize each time you run the agent.
 
 Key points to remember:
 

diff --git a/app/en/home/serve-tools/arcade-deploy/page.mdx b/app/en/home/serve-tools/arcade-deploy/page.mdx
@@ -8,7 +8,7 @@ import { SignupLink } from "@/app/_components/analytics";
 
 # Deploying to the cloud with Arcade Deploy
 
-Running your MCP servers locally is very convenient during development and testing. Once your MCP server is mature, however, you may want to access it from any MCP client, or to facilitate multi-user support. Doing all that from your computer comes with the complexity of running and maintaining a server, handling auth and high availability for all your users and all the integrations you want to support. Arcade Deploy takes care of all that for you. Your MCP server will be registered to Arcade, adding all the tools you created to the larger tool catalog. From there, you can create MCP Gateways to pick and choose which tools you want to use in you MCP clients, which can be from any connected MCP server.
+Running your MCP servers locally is very convenient during development and testing. Once your MCP server is mature, however, you may want to access it from any MCP client, or to facilitate multi-user support. Doing all that from your computer comes with the complexity of running and maintaining a server, handling auth and high availability for all your users and all the integrations you want to support. Arcade Deploy takes care of all that for you. Your MCP server will be registered to Arcade, adding all the tools you created to the larger tool catalog. From there, you can create MCP Gateways to pick and choose which tools you want to use in your MCP clients, which can be from any connected MCP server.
 
 <GuideOverview>
 <GuideOverview.Outcomes>
@@ -28,7 +28,7 @@ This guide shows you how to deploy your MCP Server with Arcade Deploy.
 <GuideOverview.YouWillLearn>
 
 - How to deploy your existing MCP Server to the cloud with the `arcade deploy` CLI command.
-- How to create an MCP Gateway to pick and choose which tools you want to use in you MCP clients.
+- How to create an MCP Gateway to pick and choose which tools you want to use in your MCP clients.
 - How to use Arcade clients to call the tools in your MCP Server.
 
 </GuideOverview.YouWillLearn>
@@ -152,7 +152,7 @@ Navigate to the [Servers](https://api.arcade.dev/dashboard/servers) page in your
 
 ## Create an MCP Gateway to call the tools in your MCP Server
 
-Once the MCP server is deployed to Arcade, all the tools in the server will be available in the [tool catalog](https://api.arcade.dev/dashboard/tools) page in your Arcade dashboard. To call the tools from an MCP client, you first need to [create an MCP Gateway](/home/mcp-gateways) to pick and choose which tools you want to use in you MCP clients.
+Once the MCP server is deployed to Arcade, all the tools in the server will be available in the [tool catalog](https://api.arcade.dev/dashboard/tools) page in your Arcade dashboard. To call the tools from an MCP client, you first need to [create an MCP Gateway](/home/mcp-gateways) to pick and choose which tools you want to use in your MCP clients.
 
 When creating an MCP gateway, you can select the tools you want to include in the Gateway from any MCP Servers available to the project, including the one you just deployed.
 

diff --git a/app/en/home/use-tools/tools-overview/page.mdx b/app/en/home/use-tools/tools-overview/page.mdx
@@ -40,7 +40,7 @@ In the example above, when the user asks: "_help me analyze the 'Project XYZ' Go
 
 One challenge to make all that happen is authorization. How do you give the LLM permission to access someone's Google Docs and Gmail in a secure and convenient way?
 
-Arcade solves this problem by providing a standardized [interface for authorization](/home/auth/how-arcade-helps), as well as pre-built integrations with [popular services](/home/auth-providers) such as Google, Dropbox, GitHub, Notion, and many more.
+Arcade solves this problem by providing a standardized [interface for authorization](/home/auth/how-arcade-helps), as well as pre-built auth providers for [popular services](/home/auth-providers) such as Google, Dropbox, GitHub, Notion, and many more.
 
 Our SDK also [allows you to integrate](/home/auth-providers/oauth2) LLMs with any OAuth 2.0-compliant API.