Apply brand tone and writing style fixes

automations/manage.mdx

@@ -31,7 +31,7 @@ Each automation's configure page groups settings into **Trigger**, **Scope**, an
 Each automation has a default trigger that controls when it runs. To change the trigger, select a different trigger type on the automation's configure page.
 
 - **Content update**: Runs whenever you push content to your project repository, including pull request merges and direct pushes.
-- **Code change**: Runs when a pull request merges in a connected source code repository. You must specify at least one source repository. Click **Add repo** to trigger on pull requests from more than one repository. For each repository, you can optionally set **Exclude author** to ignore pull requests from a specific author, and **Listening to changes in** to only trigger on pull requests with changes under a specific path.
+- **Code change**: Runs when a pull request merges in a connected source code repository. You must specify at least one source repository. Click **Add repo** to trigger on pull requests from more than one repository. For each repository, you can optionally set **Exclude author** to ignore pull requests from a specific author. You can also set **Listening to changes in** to only trigger on pull requests with changes under a specific path.
 - **Custom schedule**: Runs on a recurring schedule you define. Pick a preset (Daily, Every Monday, Every Friday, or Twice weekly) and a start hour, or select **Custom cron** and enter a standard 5-field cron expression (`minute hour day month weekday`). Automations queue within 10 minutes of the scheduled time.
 - **Integration**: Runs when a selected event occurs in a connected shared integration or when a new message posts to a selected Slack channel. Available for custom automations. Select the integration and event, then complete any additional event fields that appear. For Slack triggers, pick one or more channels that you have added the [Mintlify Slack app](/agent/slack) to.
 - **Webhook**: Runs when an authenticated `POST` request hits the automation's webhook endpoint. Available for custom automations only. Save the automation first. The trigger card then shows the webhook URL and a **Copy auth header** action for the `Authorization: Bearer <api-key>` header. Supply an unexpired organization API key with write access from the [API keys](https://app.mintlify.com/settings/organization/api-keys) page. Use this to trigger a run from a CI/CD pipeline, release script, or internal tool. See [Trigger automation webhook](/api/automations/webhook) for the endpoint and rate limits.

dashboard/sso.mdx

@@ -212,7 +212,7 @@ For providers other than Microsoft Entra or Okta SAML, [contact us](mailto:suppo
     1. In Google Workspace, navigate to **Web and mobile apps**.
     2. Click **Add custom SAML app** in the **Add app** dropdown.
   </Step>
-  <Step title="Send us your IdP information">
+  <Step title="Send your IdP information to Mintlify">
     Copy the provided SSO URL, Entity ID, and x509 certificate and send it to the Mintlify team.
   </Step>
   <Step title="Configure integration">
@@ -230,7 +230,7 @@ For providers other than Microsoft Entra or Okta SAML, [contact us](mailto:suppo
     | `First name` | `firstName` |
     | `Last name` | `lastName` |
 
-    After you complete this step and assign users to the application, tell our team. We'll enable SSO for your account.
+    After you complete this step and assign users to the application, tell the Mintlify team. The Mintlify team then enables SSO for your account.
   </Step>
 </Steps>
 
@@ -243,7 +243,7 @@ For providers other than Microsoft Entra or Okta SAML, [contact us](mailto:suppo
   <Step title="Configure integration">
     Select the authorization code grant type and enter the Redirect URI provided by Mintlify.
   </Step>
-  <Step title="Send us your IdP information">
-    Navigate to the **General** tab and locate the client ID and client secret. Securely provide these to us along with your Okta instance URL (for example, `<your-tenant-name>.okta.com`). You can send these details via a service like 1Password or SendSafely.
+  <Step title="Send your IdP information to Mintlify">
+    Navigate to the **General** tab and locate the client ID and client secret. Securely send these to the Mintlify team along with your Okta instance URL (for example, `<your-tenant-name>.okta.com`). You can send these details via a service like 1Password or SendSafely.
   </Step>
 </Steps>

deploy/gitlab.mdx

@@ -23,7 +23,7 @@
       If you already have a GitLab repository with your documentation, you can skip the download and click **Continue setup** directly.
     </Tip>
 
-    If your documentation is hosted by Mintlify, download it as a zip file.
+    If Mintlify hosts your documentation, download it as a zip file.
     * Create a new repository in GitLab.
     * Extract the zip contents.
     * Push the contents to your repository.
@@ -67,7 +67,7 @@
 
 To modify your GitLab connection settings after the initial setup, go to [Git Settings](https://app.mintlify.com/settings/project/git-settings) and update your project ID, access token, branch, or instance URL directly.
 
 ## Revalidate Git settings
 
 If your deployment shows unexpected behavior, such as missing branch options or stale configuration, you can force Mintlify to refresh your Git source.