Update CI checks page

- Improve language clarity and conciseness throughout
- Remove unnecessary words and phrases
- Use present tense for more direct communication
- Fix grammar issues and improve flow
- Replace 'in-built' with 'built-in' for standard terminology
- Streamline explanations for better readability

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: ethanpalm

settings/ci.mdx

@@ -8,19 +8,17 @@ icon: "circle-check"
   CI checks are available on [Growth and Enterprise plans](https://mintlify.com/pricing?ref=docs-ci), an add-on for other plans, and for GitHub.
 </Info>
 
-Use CI checks to lint your docs for errors, and give you warnings before you deploy.
+Use CI checks to lint your docs for errors and provide warnings before you deploy.
 
 ## Installation
 
-To begin, you will need to have followed the steps on the [GitHub](/settings/github) page.
+To begin, follow the steps on the [GitHub](/settings/github) page.
 
-For GitHub Apps, you can choose to only give permissions to a single repository.
-We highly recommend you do so as we only need access to the repository where
-your docs are hosted.
+For GitHub Apps, you can choose to give permissions to only a single repository. We highly recommend you do so as we only need access to the repository where your docs are hosted.
 
 ## Configuration
 
-You can configure the CI checks enabled for a deployment on the Mintlify dashboard by navigating to the 'Add-Ons' tab. There you can enable or disable the checks you'd like to run.
+Configure the CI checks enabled for a deployment on the Mintlify dashboard by navigating to the 'Add-Ons' tab. There you can enable or disable the checks you'd like to run.
 
 When enabling checks, you can choose to run them at a `Warning` or `Blocking` level.
 
@@ -41,30 +39,28 @@ CI checks are configured to run on commits to your configured deployment branch,
 
 ### Broken Links
 
-Similarly to how the [CLI link checker](/settings/broken-links#broken-links) works on your local machine, we will automatically check your docs for broken links.
-To see the results of this check, you can visit GitHub's check results page for a specific commit.
+Similar to how the [CLI link checker](/settings/broken-links#broken-links) works on your local machine, we automatically check your docs for broken links. To see the results of this check, visit GitHub's check results page for a specific commit.
 
 ### Vale
 
 [Vale](https://vale.sh/) is an open-source rule-based prose linter which supports a range of document types, including Markdown and MDX.
 
-Mintlify supports automatically running Vale in a CI check, and displaying the results as a check status.
+Mintlify supports automatically running Vale in a CI check and displaying the results as a check status.
 
 #### Configuration
-If you have a `.vale.ini` file in the root the content directory for your deployment, we will automatically use that configuration file.
-We will also automatically use any configuration files in your specified `stylesPath`.
+If you have a `.vale.ini` file in the root content directory for your deployment, we automatically use that configuration file. We also automatically use any configuration files in your specified `stylesPath`.
 
-<Tip>Don't have a Vale config or not sure where to get started? Don't worry, Mintlify has a default configuration that will automatically be used if one is not provided.</Tip>
+<Tip>Don't have a Vale config or not sure where to get started? Don't worry, Mintlify has a default configuration that automatically loads if one is not provided.</Tip>
 
 <Warning>
 Please note that for security reasons, we are unable to support any absolute `stylesPath`, or `stylesPath` which include `..` values. Please use relative paths and include the `stylesPath` in your repository.
 </Warning>
 
 #### Packages
 Vale supports a range of [packages](https://vale.sh/docs/keys/packages), which can be used to check for spelling and style errors.
-Any packages you include in your repository under the correct `stylesPath` will be automatically installed and used in your Vale configuration.
+Any packages you include in your repository under the correct `stylesPath` are automatically installed and used in your Vale configuration.
 
-For packages not included in your repository, you may specify any packages from the [Vale package registry](https://vale.sh/explorer), and they will automatically be downloaded and used in your Vale configuration.
+For packages not included in your repository, you may specify any packages from the [Vale package registry](https://vale.sh/explorer), and they are automatically downloaded and used in your Vale configuration.
 
 <Warning>
 Please note that for security reasons, we are unable to support automatically downloading packages that are not from the [Vale package registry](https://vale.sh/explorer).
@@ -73,7 +69,7 @@ Please note that for security reasons, we are unable to support automatically do
 #### Vale with MDX
 Vale does not natively support MDX, but Vale's author has provided a [custom extension](https://github.com/errata-ai/MDX) to support it.
 
-If you'd prefer not to use this extension, we recommend the following lines in your `.vale.ini` file:
+If you prefer not to use this extension, we recommend the following lines in your `.vale.ini` file:
 ```ini
 [formats]
 mdx = md
@@ -89,9 +85,7 @@ BlockIgnores = (?sm)^(<\w+\n .*\s\/>)$, \
 (?sm)^({.+.*})
 ```
 
-To use Vale's in-document comments, use MDX-style comments `{/* ... */}`.
-If you use the `CommentDelimiters = {/*, */}` [setting](https://vale.sh/docs/keys/commentdelimiters) in your configuration, Vale will automatically interpret these comments while linting.
-This means you can easily use Vale's in-built features, like skipping lines or sections.
+To use Vale's in-document comments, use MDX-style comments `{/* ... */}`. If you use the `CommentDelimiters = {/*, */}` [setting](https://vale.sh/docs/keys/commentdelimiters) in your configuration, Vale automatically interprets these comments while linting. This means you can easily use Vale's built-in features, like skipping lines or sections.
 
 ```mdx
 {/* vale off */}
@@ -102,7 +96,7 @@ This text will be ignored by Vale
 ```
 
 
-If you choose not to use `CommentDelimiters`, but still choose to use Vale's comments, you must wrap any Vale comments in MDX comments `{/* ... */}`. For example:
+If you choose not to use `CommentDelimiters` but still choose to use Vale's comments, you must wrap any Vale comments in MDX comments `{/* ... */}`. For example:
 
 ```mdx
 {/* <!-- vale off --> */}
@@ -111,4 +105,4 @@ This text will be ignored by Vale
 
 {/* <!-- vale on --> */}
 ```
-Please note that these comment tags are not supported within Mintlify components, but can be used anywhere at the base level of a document.
+These comment tags are not supported within Mintlify components but can be used anywhere at the base level of a document.