Term consistency 1 (#445)

* Replace 'integration' with 'toolkit' terminology across documentation

- Update references from 'integration' to 'toolkit' in meta files and components
- Standardize terminology to use 'toolkit' consistently throughout the docs

* Auth Integration -> Auth Provider

* Update terminology: change 'the hosted Arcade Engine' to 'the Arcade Cloud Platform'

* Update 'Arcade Cloud' to 'Arcade Cloud Platform'

* Authentication Provider -> Auth Provider

---------

Co-authored-by: Evan Tahler <[email protected]>

Author: jakubvul

pages/home/_meta.tsx

@@ -19,7 +19,7 @@ export default {
     title: (
       <span className="flex items-center gap-2 font-medium">
         <Plug className="size-4" />
-        Integrations
+        Toolkits
       </span>
     ),
     href: "/toolkits",

pages/home/auth-providers/asana.mdx

@@ -22,7 +22,7 @@ This auth provider is used by:
 
 ## Use Arcade's Default Asana Auth Provider
 
-Arcade offers a default Asana auth provider that you can use in the Arcade Cloud. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
+Arcade offers a default Asana auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
 
 If you choose to use Arcade's Asana auth, you don't need to configure anything. Follow the [Asana toolkit examples](/toolkits/productivity/asana) to get started calling Asana tools.
 
@@ -34,7 +34,7 @@ If you choose to use Arcade's Asana auth, you don't need to configure anything.
 
 In a production environment, you will most likely want to use your own Asana app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Asana credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Asana credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Asana app credentials, let's go through the steps to create an Asana app.
 

pages/home/auth-providers/atlassian.mdx

@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Atlassian app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Atlassian credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Atlassian credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Atlassian app credentials, let's go through the steps to create an Atlassian app.
 

pages/home/auth-providers/clickup.mdx

@@ -19,7 +19,7 @@ This auth provider is used by:
 </Note>
 In a production environment, you will most likely want to use your own ClickUp app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own ClickUp credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own ClickUp credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your ClickUp app credentials, let's go through the steps to create a ClickUp app.
 

pages/home/auth-providers/discord.mdx

@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Discord app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Discord credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Discord credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Discord app credentials, let's go through the steps to create a Discord app.
 

pages/home/auth-providers/dropbox.mdx

@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Dropbox app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Dropbox credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Dropbox credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Dropbox app credentials, let's go through the steps to create a Dropbox app.
 

pages/home/auth-providers/github.mdx

@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own GitHub app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own GitHub credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own GitHub credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your GitHub app credentials, let's go through the steps to create a GitHub app.
 

pages/home/auth-providers/google.mdx

@@ -28,7 +28,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Google app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Google credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Google credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Google app credentials, let's go through the steps to create a Google app.
 

pages/home/auth-providers/hubspot.mdx

@@ -21,7 +21,7 @@ This auth provider is used by:
 
 ## Use Arcade's Default Hubspot Auth Provider
 
-Arcade offers a default Hubspot auth provider that you can use in the Arcade Cloud. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
+Arcade offers a default Hubspot auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
 
 If you choose to use Arcade's Hubspot auth, you don't need to configure anything. Follow the [Hubspot toolkit examples](/toolkits/sales/hubspot) to get started calling Hubspot tools.
 
@@ -33,7 +33,7 @@ If you choose to use Arcade's Hubspot auth, you don't need to configure anything
 
 In a production environment, you will most likely want to use your own Hubspot app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Hubspot credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Hubspot credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Hubspot app credentials, let's go through the steps to create a Hubspot app.
 

pages/home/auth-providers/index.mdx

@@ -9,15 +9,15 @@ import { ToolCard } from "@/components/ToolCard";
 
 Auth providers enable users to seamlessly and securely allow Arcade tools to access their data.
 
-Arcade has several auth providers available in the Arcade cloud so you don't have to configure your own. However, using Arcade's auth providers means that your users will see the Arcade brand (name and logo) on the auth screen and your authentications will share any rate limits from those providers with other Arcade customers.
+Arcade has several auth providers available in the Arcade Cloud Platform so you don't have to configure your own. However, using Arcade's auth providers means that your users will see the Arcade brand (name and logo) on the auth screen and your authentications will share any rate limits from those providers with other Arcade customers.
 
 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)
 
-After adding an auth provider used by an Arcade tool, executing the tool will automatically use your auth provider. Even in the Arcade Cloud, your auth provider will take precedence over the arcade-provided auth provider.
+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.
 
 Adding multiple providers of the same type, not including the arcade-provided ones, can cause Arcade's tool authorization to fail, see [Using multiple providers of the same type](#using-multiple-providers-of-the-same-type) for more information.