Emphasize Git integration in quickstart

quickstart.mdx

@@ -4,10 +4,10 @@
 keywords: ["quickstart","deploy","get started","first steps"]
 ---
 
 After completing this guide, you will have a live documentation site ready to customize and expand.
 
 <Info>
   **Prerequisites**: Before you begin, [create an account](https://mintlify.com/start) and complete onboarding.
 </Info>
 
 ## Getting started
@@ -36,11 +36,13 @@
 
 Your site's URL is available immediately. Use this URL for testing and sharing with your team while you are setting up your docs site.
 
-### Install the GitHub App
+### Connect your GitHub repository
 
-Mintlify provides a GitHub App that automates deployment when you push changes to your repository.
+Mintlify integrates directly with GitHub to automatically deploy your documentation when you push changes to your repository. This Git-based workflow ensures your documentation stays in sync with your codebase and enables version control, collaboration, and review processes.
 
-Install the GitHub App by following the instructions from the onboarding checklist or your dashboard.
+#### Install the GitHub App
+
+The Mintlify GitHub App monitors your repository for changes and triggers automatic deployments.
 
 1. Navigate to **Settings** in your Mintlify dashboard.
 2. Select **GitHub App** from the sidebar.
@@ -66,14 +68,14 @@
   Update the GitHub App permissions if you move your documentation to a different repository.
 </Info>
 
-### Authorize your GitHub account
+#### Authorize your GitHub account
 
 1. Navigate to **Settings** in your Mintlify dashboard.
 2. Select **My Profile** from the sidebar.
 3. Select **Authorize GitHub account**. This opens a new tab to the GitHub authorization page.
 
 <Info>
   An admin for your GitHub organization may need to authorize your account depending on your organization settings.
 </Info>
 
 ## Editing workflows
@@ -90,15 +92,15 @@
 
 ## Code-based workflow
 
-The code-based workflow integrates with your existing development environment and Git repositories. This workflow is best for technical teams who want to manage documentation alongside code.
+The code-based workflow integrates with your existing development environment and Git repositories. This workflow is best for technical teams who want to manage documentation alongside code using familiar Git-based version control.
 
 ### Install the CLI
 
 <Info>
   **Prerequisite**: The CLI requires [Node.js](https://nodejs.org/en) v20.17.0 or higher through v24. LTS versions are preferred.
 </Info>
 
 To work locally with your documentation, install the Command Line Interface (CLI), called [mint](https://www.npmjs.com/package/mint), by running this command in your terminal:
 
 <CodeGroup>
 
@@ -166,19 +168,29 @@
 
 ### Push the changes
 
-When you are ready to publish your changes, push them to your repository.
+When you are ready to publish your changes, commit and push them to your GitHub repository:
+
+```bash
+git add .
+git commit -m "Update introduction title"
+git push origin main
+```
 
-Mintlify automatically detects the changes, builds your documentation, and deploys the updates to your site. Monitor the deployment status in your GitHub repository commit history or the [dashboard](https://dashboard.mintlify.com).
+Mintlify automatically detects the changes through the GitHub App, builds your documentation, and deploys the updates to your site. Monitor the deployment status in your GitHub repository commit history or the [dashboard](https://dashboard.mintlify.com).
 
 After the deployment completes, your latest update will be available at `<your-project-name>.mintlify.app`.
 
+<Tip>
+  Use Git branches and pull requests to review changes before merging to your main branch. Learn more about [working with branches](/guides/branches).
+</Tip>
+
 <Card title="Jump to adding a custom domain" icon="arrow-down" horizontal href="#adding-a-custom-domain">
   Optionally, skip the web editor workflow and jump to adding a custom domain.
 </Card>
 
 ## Web editor workflow
 
 The web editor workflow provides a what-you-see-is-what-you-get (WYSIWYG) interface for creating and editing documentation. This workflow is best for people who want to work in their web browser without additional local development tools.
 
 ### Access the web editor
 
@@ -186,7 +198,7 @@
 2. Select **Editor** on the left sidebar.
 
 <Info>
   If you have not installed the GitHub App, you will be prompted to install the app when you open the web editor.
 </Info>
 
 <Frame>
@@ -205,11 +217,11 @@
 
 ### Edit the documentation
 
 In the web editor, you can navigate through your documentation files in the sidebar. Let's update the introduction page:
 
 Find and select `index.mdx` in the file explorer.
 
 Then, in the editor, update the title field to "Hello World".
 
 <Frame>
   <img
@@ -233,13 +245,13 @@
 
 ### Publish your changes
 
-When you're satisfied with your edits, select the **Publish** button in the top-right corner. Your changes are immediately deployed to your documentation site.
+When you're satisfied with your edits, select the **Publish** button in the top-right corner. The web editor commits your changes to your GitHub repository and triggers an automatic deployment to your documentation site.
 
 <Tip>
-  Use branches to preview and review changes through pull requests before deploying to your live site.
+  Use Git branches to preview and review changes through pull requests before deploying to your live site. The web editor supports creating and switching between branches.
 </Tip>
 
 For more details about using the web editor, including using branches and pull requests to collaborate and preview changes, see our [web editor documentation](/editor).
 
 ## Adding a custom domain
 
@@ -261,21 +273,21 @@
   />
 </Frame>
 
 Enter your domain (for example, `docs.yourcompany.com`) and follow the provided instructions to configure DNS settings with your domain provider.
 
 <Table>
   | Record Type | Name                | Value                | TTL  |
   | ----------- | ------------------- | -------------------- | ---- |
   | CNAME       | docs (or subdomain) | cname.vercel-dns.com | 3600 |
 </Table>
 
 <Info>
   DNS changes can take up to 48 hours to propagate, though changes often complete much sooner.
 </Info>
 
 ## Next steps
 
 Congratulations! You have successfully deployed your documentation site with Mintlify. Here are suggested next steps to enhance your documentation:
 
 <Card title="Configure your global settings" icon="settings" horizontal href="organize/settings">
   Configure site-wide styling, navigation, integrations, and more with the `docs.json` file.
@@ -309,5 +321,5 @@
     Deployment can take up to a few minutes. Check your GitHub Actions (for code-based workflow) or deployment logs in the Mintlify dashboard to ensure there are no build errors.
   </Accordion>
   <Accordion title="Custom domain not connecting">
     Verify that your DNS records are set up correctly and allow sufficient time for DNS propagation (up to 48 hours). You can use tools like [DNSChecker](https://dnschecker.org) to verify your CNAME record.
   </Accordion>