docs: Fix Cal.com brand casing inconsistencies (#26887)

* Update docs/api-reference/v2/oauth.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/api-reference/v2/oauth.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/api-reference/v2/oauth.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> * Update docs/self-hosting/deployments/gcp.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
2026-01-15 15:27:20 +00:00
1 parent 3feae24b20
commit a2c769251a
@@ -1,9 +1,9 @@
 ---
 title: "OAuth"
-description: "Authorize apps with cal.com accounts using OAuth"
+description: "Authorize apps with Cal.com accounts using OAuth"
 ---

-As an example, you can view our OAuth flow in action on Zapier. Try to connect your cal.com account [here](https://zapier.com/apps/calcom/integrations). To enable OAuth in one of your apps, you will need a Client ID, Client Secret, Authorization URL, Access Token Request URL, and Refresh Token Request URL.
+As an example, you can view our OAuth flow in action on Zapier. Try to connect your Cal.com account [here](https://zapier.com/apps/calcom/integrations). To enable OAuth in one of your apps, you will need a Client ID, Client Secret, Authorization URL, Access Token Request URL, and Refresh Token Request URL.

 <Frame>
  ![](/images/oauth-zapier.png)
@@ -22,7 +22,7 @@ As an example, you can view our OAuth flow in action on Zapier. Try to connect y

 ### OAuth Client Credentials

-Only the cal.com team can create new OAuth clients. Please fill out [this form](https://i.cal.com/forms/4052adda-bc79-4a8d-9f63-5bc3bead4cd3) and book us to get started.
+Only the Cal.com team can create new OAuth clients. Please fill out [this form](https://i.cal.com/forms/4052adda-bc79-4a8d-9f63-5bc3bead4cd3) and book us to get started.

 The Cal.com team will register the app and provide you with the Client ID and Client Secret. Keep these credentials confidential and secure.