Improve quickstart documentation for better translatability (#750)

* Documentation edits made through Mintlify web editor

* 💅

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <[email protected]>

Author: mintlify[bot]

quickstart.mdx

@@ -4,42 +4,42 @@ description: "Deploy your documentation in minutes"
 icon: "rocket"
 ---
 
-This quickstart guide will walk you through the process of setting up and deploying your documentation site in just a few minutes.
+This quickstart guide shows you how to set up and deploy your documentation site in minutes.
 
-By the end of this guide, you'll have a live documentation site that's ready to customize and expand.
+After you complete this guide, you will have a live documentation site ready to customize and expand.
 
 <Info>
 
-**Prerequisites**: Before you begin, make sure to [create an account](https://mintlify.com/start) and complete onboarding.
+**Prerequisites**: Before you begin, [create an account](https://mintlify.com/start) and complete onboarding.
 
 </Info>
 
 ## Getting Started
 
-Once you've completed the onboarding process, your documentation site will be automatically deployed to a unique URL with the following format.
+After you complete the onboarding process, your documentation site will automatically deploy to a unique URL with this format:
 
 ```
 https://<your-project-name>.mintlify.app
 ```
 
-You can find your URL from the Overview page of the dashboard.
+Find your URL on the Overview page of your [dashboard](https://dashboard.mintlify.com/).
 
 <Frame>
   <img src="/images/quickstart/mintlify-domain-light.png" alt="Mintlify Domain" className="block dark:hidden" />
   <img src="/images/quickstart/mintlify-domain-dark.png" alt="Mintlify Domain" className="hidden dark:block" />
 </Frame>
 
-This URL is instantly available and will update whenever you make changes to your documentation. It's perfect for testing and sharing with your team during development.
+This URL becomes available immediately and updates when you make changes to your documentation. Use this URL for testing and sharing with your team during development.
 
 ### Install the GitHub App
 
-Mintlify provides a GitHub App that automates the deployment process when you push changes to your repository.
+Mintlify provides a GitHub App that automates deployment when you push changes to your repository.
 
-You can install the GitHub App by following the instructions from the onboarding checklist or from your dashboard.
+Install the GitHub App by following the instructions from the onboarding checklist or from your dashboard.
 
 1. Navigate to **Settings** in your Mintlify dashboard.
 2. Select **GitHub App** from the sidebar.
-3. Select **Install GitHub App**. This will open a new tab to the GitHub App installation page.
+3. Select **Install GitHub App**. This opens a new tab to the GitHub App installation page.
 4. Select the organization or user account where you want to install the app. Then select the repositories that you want to connect.
 
 <Frame>
@@ -48,38 +48,38 @@ You can install the GitHub App by following the instructions from the onboarding
 </Frame>
 
 <Info>
-  Remember to update the GitHub App permissions if you move the documentation to a different repository.
+  Update the GitHub App permissions if you move your documentation to a different repository.
 </Info>
 
 ### 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 will open a new tab to the GitHub authorization page.
+3. Select **Authorize GitHub account**. This opens a new tab to the GitHub authorization page.
 
 <Info>
-  You may need an admin for your GitHub organization to authorize your account depending on your organization's settings.
+  An admin for your GitHub organization may need to authorize your account depending on your organization settings.
 </Info>
 
 ## Editing Workflows
 
-Mintlify offers two different workflows for creating and maintaining your documentation.
+Mintlify offers two workflows for creating and maintaining your documentation.
 
 <Card title="Code-based workflow" icon="terminal" horizontal href="#code-based-workflow">
-  For developers who prefer working with their existing tools. Click to jump to section.
+  For users who prefer working with existing tools in their local environment. Click to jump to this section.
 </Card>
 
 <Card title="Web editor workflow" icon="mouse-pointer-2" horizontal href="#web-editor-workflow">
-  For those who prefer a visual interface. Click to jump to section.
+  For users who prefer a visual interface in their web browser. Click to jump to this section.
 </Card>
 
 ## Code-Based Workflow
 
-The code-based workflow integrates with your existing development environment and Git repositories, making it ideal for technical teams who want to manage documentation alongside their 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.
 
 ### Install the CLI
 
-To work locally with your documentation, install the Command Line Interface (CLI), called [mint](https://www.npmjs.com/package/mint), by running the following command in your terminal:
+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>
 
@@ -105,9 +105,9 @@ pnpm add -g mint
 
 ### Edit the Documentation
 
-Now that your environment is set up, you can start editing your documentation files. As an example, let's update the title of the introduction page:
+After you set up your environment, you can start editing your documentation files. For example, update the title of the introduction page:
 
-Open your repository created during onboarding, find the `introduction.mdx` file, and find the top of the file, that should look like this:
+Open your repository created during onboarding, find the `introduction.mdx` file, and find the top of the file:
 
 ```jsx introduction.mdx
 ---
@@ -127,7 +127,7 @@ description: "This is the introduction to the documentation"
 
 ### Preview the Changes
 
-To preview the changes locally, run the following command.
+To preview the changes locally, run this command:
 
 ```bash
 mint dev
@@ -142,27 +142,27 @@ Your preview will be available at `localhost:3000`.
 
 ### Push the Changes
 
-When you're ready to publish your changes, simply push the changes to your repository.
+When you are ready to publish your changes, push the changes to your repository.
 
-Mintlify will automatically detect the changes, build your documentation, and deploy the updates to your site. You can monitor the deployment status in your GitHub repository's commit history or the [dashboard](https://dashboard.mintlify.com).
+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).
 
-Once the deployment is complete, your last update will be available at `<your-project-name>.mintlify.app`.
+After the deployment is complete, your latest update will be available at `<your-project-name>.mintlify.app`.
 
 <Card title="Jump to adding a custom domain" icon="arrow-down" href="#adding-a-custom-domain" horizontal>
-  Optionally skip the web editor workflow and jump to 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. It's ideal for people who want to work in their web browser without additional local development tools.
+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
 
 1. Log in to your [Mintlify Dashboard](https://dashboard.mintlify.com).
 2. Select **Editor** on the left sidebar.
 
 <Info>
-  If you haven't installed the GitHub App, you will be prompted to do so upon opening the web editor.
+  If you have not installed the GitHub App, you will be prompted to install the app when you open the web editor.
 </Info>
 
 <Frame>
@@ -172,7 +172,7 @@ The web editor workflow provides a what-you-see-is-what-you-get (WYSIWYG) interf
 
 ### Edit the Documentation
 
-In the web editor, you can navigate your documentation files in the sidebar. Let's update the introduction page.
+In the web editor, you can navigate through your documentation files in the sidebar. Let's update the introduction page:
 
 Find and click on `introduction.mdx` in the file explorer.
 
@@ -184,14 +184,14 @@ Then, in the visual editor, update the title field to "Hello World".
 </Frame>
 
 <Tip>
-  The editor provides a rich set of formatting tools and components. Access them by typing "/" in the editor to open the command menu.
+  The editor provides a rich set of formatting tools and components. Type <kbd>/</kbd> in the editor to open the command menu and access these tools.
 </Tip>
 
 ### Publish Your Changes
 
-When you're satisfied with your edits, click the `Publish` button in the top-right corner.
+When you are satisfied with your edits, click the `Publish` button in the top-right corner.
 
-Your changes will be deployed immediately to your documentation site.
+Your changes are immediately deployed to your documentation site.
 
 For more details about using the web editor, including advanced features like slash commands and image uploads, see our [Web Editor documentation](/editor).
 
@@ -206,7 +206,7 @@ To add a custom domain, go to `Settings` > `Custom Domain` from the dashboard.
   <img src="/images/quickstart/custom-domain-dark.png" alt="Custom Domain" className="hidden dark:block" />
 </Frame>
 
-Enter your domain (e.g., docs.yourcompany.com) and follow the provided instructions to configure DNS settings with your domain provider.
+Enter your domain (for example, `docs.yourcompany.com`) and follow the provided instructions to configure DNS (Domain Name System) settings with your domain provider.
 
 <Table>
 | Record Type | Name | Value | TTL |
@@ -215,12 +215,12 @@ Enter your domain (e.g., docs.yourcompany.com) and follow the provided instructi
 </Table>
 
 <Info>
-  DNS changes can take up to 48 hours to propagate, though they often complete much sooner.
+  DNS changes can take up to 48 hours to propagate, though changes often complete much sooner.
 </Info>
 
 ## Next Steps
 
-Congratulations! You've successfully deployed your documentation site with Mintlify. Here are some suggested next steps to enhance your documentation:
+Congratulations! You have successfully deployed your documentation site with Mintlify. Here are suggested next steps to enhance your documentation:
 
 <Card title="Customize Your Theme" icon="paintbrush" href="themes" horizontal>
   Learn how to customize colors, fonts, and the overall appearance of your documentation site.
@@ -237,11 +237,11 @@ Congratulations! You've successfully deployed your documentation site with Mintl
 
 ## Troubleshooting
 
-If you encounter any issues during the setup process, check our common troubleshooting solutions:
+If you encounter issues during the setup process, check these common troubleshooting solutions:
 
 <AccordionGroup>
   <Accordion title="Local preview not working">
-    Make sure you have Node.js v19+ installed and that you're running the `mint dev` command from the directory containing your `docs.json` file.
+    Make sure you have Node.js v19+ installed and that you run the `mint dev` command from the directory containing your `docs.json` file.
   </Accordion>
   <Accordion title="Changes not reflecting on live site">
     Deployment can take upwards 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.