Replace 'functionality' with preferred terms per Vale style guide

components/color.mdx

@@ -1,10 +1,10 @@
 ---
 title: "Color"
-description: "Display color palettes with click-to-copy functionality."
+description: "Display color palettes with click-to-copy."
 keywords: ["color", "palette", "colors", "design system", "hex", "rgb", "rgba", "hsl", "oklch"]
 ---
 
 Use the Color component to showcase color palettes in your documentation. Colors can be displayed in a compact grid or organized in a table with labeled rows.
 
 ## Compact variant
 
@@ -22,7 +22,7 @@
   <Color.Item name="blue-500" value="#3B82F6" />
   <Color.Item name="blue-600" value="#2563EB" />
   <Color.Item name="blue-700" value="#1D4ED8" />
   <Color.Item name="blue-800" value="#1E40AF" />
 </Color>
 ```
 
@@ -44,7 +44,7 @@
 
 ```mdx Table example
 <Color variant="table">
   <Color.Row title="Primary">
     <Color.Item name="primary-500" value="#3B82F6" />
     <Color.Item name="primary-600" value="#2563EB" />
     <Color.Item name="primary-700" value="#1D4ED8" />
@@ -58,7 +58,7 @@
 
 ## Color formats
 
 The component supports all CSS color formats including hex, rgb, rgba, hsl, and oklch.
 
 <Color variant="compact">
   <Color.Item name="hex" value="#FF5733" />

deploy/ghes.mdx

@@ -4,7 +4,7 @@
 keywords: ["GitHub Enterprise Server", "GHES", "GitHub Enterprise"]
 ---
 
 This guide walks you through setting up the Mintlify GitHub App on your GitHub Enterprise Server (GHES) installation. To connect a GHES instance to Mintlify, you must create a local version of our app within your self-hosted environment that communicates with our remote server.
 
 If you use a cloud-hosted GitHub instance, see the [GitHub](/deploy/github) page for setup instructions.
 
@@ -12,21 +12,21 @@
 
 - Admin privileges on your GitHub Enterprise Server organization where you want to install the app
 - Access to your organization's repositories where you want to install the app
 - Network connectivity to communicate with our external services (see [Network requirements](#network-requirements) section below)
 
 ### Network requirements
 
 #### Outbound connectivity
 
 Your GitHub Enterprise Server must be able to reach:
 - Mintlify's API endpoints (https://leaves.mintlify.com)
 - Webhook receivers (port 443)
 
 #### Firewall configuration
 
 The following outbound connections must be allowed:
 - Connections from Mintlify's static IP: `54.242.90.151`
 - HTTPS (port 443) to Mintlify's service domains
 - DNS resolution for Mintlify's service domains
 
 ## Step 1: Register the GitHub App
@@ -52,7 +52,7 @@
 - **GitHub App name:** `Mintlify`
 - **Description:** `Integration with Mintlify services`
 - **Homepage URL:** `https://mintlify.com`
 - **User authorization callback URL:** `https://your-github-server.com/` (replace with your actual GHES domain)
 
 </Step>
 </Steps>
@@ -61,7 +61,7 @@
 
 <Steps>
 <Step title="Set repository permissions">
 Set the following permissions for the app. No Organization, Account, or Enterprise permissions are required:
 
 - **Checks:** Read and write
 - **Contents:** Read and write
@@ -90,7 +90,7 @@
 <Step title="Create the app">
 Click **Create GitHub App**.
 
 You'll be redirected to the app's settings page.
 </Step>
 
 <Step title="Generate private key">
@@ -102,9 +102,9 @@
 <Step title="Note app credentials">
 Record the following:
 
 - **App ID** (visible at the top of the settings page)
 - **Client ID** (in the "About" section)
 - **Client Secret** (generate and record it securely)
 </Step>
 </Steps>
 
@@ -119,11 +119,11 @@
 <Step title="Choose installation scope">
 Select either:
 
 - **All repositories** (for organization-wide access)
 - **Only select repositories** (choose specific repositories)
 
 <Tip>
 We recommend selecting "Only select repositories" and limiting the app to only the repositories where your documentation is located.
 </Tip>
 </Step>
 
@@ -144,8 +144,8 @@
 <Step title="Set webhook URL">
 Configure the following:
 
 - **Webhook URL:** `https://leaves.mintlify.com/github-enterprise/:subdomain` (replace `:subdomain` with the URL that we provide you with)
 - **Webhook secret:** Generate a random string (32+ characters) and record it securely. Mintlify can also generate this and provide it to you.
 </Step>
 </Steps>
 
@@ -154,16 +154,16 @@
 
 ### Required credentials
 - GitHub Enterprise Server base URL: https://your-github-server.com
 - App ID: (from step 3)
 - App client ID: (from step 3)
 - App client secret: (from step 3)
 - Installation ID: (from step 4)
 - Private key: The entire contents of the `.pem` file (should be shared via secure file transfer)
 - Webhook secret: (from step 5)
 
 ### Optional credentials for troubleshooting
 - Organization name: Your GitHub organization name
 - Repository names: Specific repositories where the app is installed
 - GitHub Enterprise Server version: Found in your site admin dashboard
 
 ## Mintlify connection
@@ -172,7 +172,7 @@
 - Integrate your GHES environment with an existing Mintlify deployment.
 - Integrate your GHES environment with a new Mintlify deployment that we provision for you.
 
 After your GHES environment is integrated with a Mintlify deployment, you are ready to enable webhooks for your GitHub App.
 
 <Note>
 The webhook URL may change based on our configuration. We test the integration and provide you with the new URL.
@@ -194,7 +194,7 @@
 </Step>
 </Steps>
 
 ## FAQ and Troubleshooting
 
 <AccordionGroup>
 <Accordion title="The app installation is failing with permission errors.">
@@ -208,7 +208,7 @@
 <Accordion title="Webhooks aren't being delivered">
 - Verify the webhook URL is correct and accessible.
 - Ensure your firewall allows outbound HTTPS connections.
 - Check the webhook secret matches what was configured.
 - Review webhook delivery logs in the "Advanced" tab of your GitHub App settings.
 </Accordion>
 
@@ -219,8 +219,8 @@
 </Accordion>
 
 <Accordion title="The app installs, but doesn't respond to events.">
 - Ensure webhooks are being delivered and acknowledged by our server with response code 200.
 - Required permissions were granted during installation.
 </Accordion>
 
 <Accordion title="Can I limit which repositories the app accesses?">
@@ -230,15 +230,15 @@
 <Accordion title="How do I update app permissions later?">
 - Go to the app settings as a site admin.
 - Modify permissions as needed.
 - The app will need to be re-approved by organization owners.
-- Notify us of any permission changes as they may affect functionality.
+- Notify us of any permission changes as they may affect features.
 </Accordion>
 
 <Accordion title="Our GHES is behind a corporate firewall, nginx proxy, or similar setup.">
 You must:
 
 - Whitelist our service domains in your firewall.
 - Ensure outbound HTTPS (port 443) connectivity.
 - If direct internet access is not allowed, set up a proxy.
 </Accordion>
 
@@ -252,7 +252,7 @@
 - Your GitHub Enterprise Server version.
 - Specific error messages.
 - Screenshots of any issues.
 - Network/firewall configuration details (if relevant).
 </Accordion>
 </AccordionGroup>
 

deploy/route53-cloudfront.mdx

@@ -39,13 +39,13 @@
 3. For the Origin domain, input `[SUBDOMAIN].mintlify.dev` where `[SUBDOMAIN]` is your project's unique subdomain.
 
   <Frame>
     ![CloudFront "Create distribution" page showing "acme.mintlify.dev" as the origin domain.](/images/cloudfront/origin-name.png)
   </Frame>
 
 4. For "Web Application Firewall (WAF)," enable security protections.
 
   <Frame>
     ![Web Application Firewall (WAF) options with "Enable security protections" selected.](/images/cloudfront/enable-security-protections.png)
   </Frame>
 
 5. The remaining settings should be default.
@@ -59,10 +59,10 @@
     ![A CloudFront distribution with the "Origins" tab highlighted.](/images/cloudfront/origins.png)
   </Frame>
 
 2. Find your staging URL that mirrors the main domain. This is highly variant depending on how your landing page is hosted. For example, the Mintlify staging URL is [mintlify-landing-page.vercel.app](https://mintlify-landing-page.vercel.app).
 
 <Info>
   If your landing page is hosted on Webflow, use Webflow's staging URL. It would look like `.webflow.io`.
 
   If you use Vercel, use the `.vercel.app` domain available for every project.
 </Info>
@@ -105,21 +105,21 @@
 </Frame>
 
 <Info>
 If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a minimum for Vercel:
   - `/.well-known/vercel/*` - Required for Vercel domain verification
   - `/.well-known/acme-challenge/*` - Required for Let's Encrypt certificate verification
 </Info>
 
 ### Your subpath
 
 Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.dev` URL (in our case `acme.mintlify.dev`).
 
 - Set "Cache policy" to **CachingOptimized**.
 - Set "Origin request policy" to **AllViewerExceptHostHeader**.
 - Set Viewer Protocol Policy to **Redirect HTTP to HTTPS**
 
 <Frame>
   ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.dev` URL.](/images/cloudfront/behavior-1.png)
 </Frame>
 
 ### Your subpath with wildcard
@@ -143,10 +143,10 @@
 Lastly, we're going to edit the `Default (*)` behavior.
 
 <Frame>
   ![A CloudFront distribution with the "Default (*)" behavior selected and the Edit button emphasized.](/images/cloudfront/default-behavior-1.png)
 </Frame>
 
 1. Change the default behavior's **Origin and origin groups** to the staging URL (in our case `mintlify-landing-page.vercel.app`).
 
 <Frame>
   ![CloudFront "Edit behavior" page with the "Origin and origin groups" input field highlighted.](/images/cloudfront/default-behavior-2.png)
@@ -154,9 +154,9 @@
 
 2. Select **Save changes**.
 
 ### Check behaviors are set up correctly
 
 If you follow the above steps, your behaviors should look like this:
 
 <Frame>
   ![CloudFront "Behaviors" page with 4 behaviors: `/docs/*`, `/docs`, `Default`, and `/.well-known/*`.](/images/cloudfront/all-behaviors.png)
@@ -164,7 +164,7 @@
 
 ## Preview distribution
 
 You can now test if your distribution is set up properly by going to the "General" tab and visiting the **Distribution domain name** URL.
 
 <Frame>
   ![CloudFront "General" tab with the "Distribution domain name" URL highlighted.](/images/cloudfront/preview-distribution.png)
@@ -172,9 +172,9 @@
 
 All pages should be directing to your main landing page, but if you append your chosen subpath, for example `/docs`, to the URL, you should see it going to your Mintlify documentation instance.
 
 ## Connect with Route53
 
-Now, we're going to bring the functionality of the CloudFront distribution into your primary domain.
+Now, we're going to bring the CloudFront distribution into your primary domain.
 
 <Note>
   For this section, you can also refer to AWS's official guide on [Configuring

guides/content-templates.mdx

@@ -52,11 +52,11 @@
   Include practical tips that help users avoid common mistakes or work more efficiently.
 </Tip>
 
 ## Verify the result (optional)
 
 If success is ambiguous, explain how users can confirm they completed the task successfully.
 
 ## Troubleshooting (optional)
 
 Address common issues users might encounter:
 
@@ -176,7 +176,7 @@
 
 ## Reference template
 
-Use reference documentation when users need to look up specific details about your product's functionality. Reference docs prioritize accuracy, consistency, and scannability.
+Use reference documentation when users need to look up specific details about your product's features. Reference docs prioritize accuracy, consistency, and scannability.
 
 ````mdx Reference template
 ---

guides/content-types.mdx

@@ -8,11 +8,11 @@
   This page explains different content types, when to use each one, and how to approach writing for each type.
 </Tip>
 
 Documentation should be organized around the specific goal you're trying to help people achieve. 
 
 ## Categorize using the Diátaxis framework
 
 The [Diátaxis framework](https://diataxis.fr) is a helpful guide for categorizing content based on your audience's needs. Documentation can generally be mapped into one of these types:
 
 1. Tutorials: Learning-oriented content for new users
 2. How-to guides: Task-oriented guidance for specific problems
@@ -38,17 +38,17 @@
 
 ## Writing for each type
 
 ### Tutorials (Learning-oriented)
 
 - **Audience goal**: Learn something new through step-by-step instructions.
 - **Characteristics**: Sequential and assumes no prior knowledge.
 - **Writing approach**:
   - Set expectations of what the user will achieve after reading.
   - Use clear, incremental steps. Minimize choices that need to be made by the user.
   - Point out milestones along the way.
   - Minimize theory and focus on concrete actions.
 
 ### How-To Guides (Problem-oriented)
 
 - **Audience goal**: Perform a specific task correctly.
 - **Characteristics**: Goal-driven and assumes some prior knowledge.
@@ -57,16 +57,16 @@
   - Describe a logical sequence and omit unnecessary details.
   - Minimize context beyond what is necessary.
 
 ### Reference (Information-oriented)
 
-- **Audience goal**: Find details about a product's functionality.
+- **Audience goal**: Find details about a product's features.
 - **Characteristics**: Unambiguous, product-focused, scannable.
 - **Writing approach**:
   - Be scannable and concise.
   - Prioritize consistency.
   - Avoid explanatory content. Focus on examples that are easy to copy and modify.
 
 ### Explanation (Understanding-oriented)
 
 - **Audience goal**: Expand general understanding of a concept or highly complex feature.
 - **Characteristics**: Theoretical, potentially opinionated, broad in scope.

guides/cursor.mdx

@@ -6,11 +6,11 @@
 
 Transform Cursor into a documentation expert that knows your components, style guide, and best practices.
 
 ## Use Cursor with Mintlify
 
 Cursor rules provide persistent context about your documentation, ensuring more consistent suggestions that fit your standards and style.
 
 * **Project rules** are stored in your documentation repository and shared with your team.
 * **User rules** apply to your personal Cursor environment.
 
 We recommend creating project rules for your docs so that all contributors have access to the same rules.
@@ -371,7 +371,7 @@
 
 <Update label="Version 2.1.0" description="Released March 15, 2024">
 ## New features
-- Added bulk user import functionality
+- Added bulk user import
 - Improved error messages with actionable suggestions
 
 ## Bug fixes

guides/linking.mdx

@@ -8,7 +8,7 @@
 
 ## Internal links
 
 Link to other pages in your documentation using root-relative paths. Root-relative paths start from the root of your documentation directory and work consistently regardless of where the linking page is located.
 
 ```mdx
 * [Quickstart guide](/quickstart)
@@ -46,7 +46,7 @@
 * [Customize your playground](/api-playground/overview#customize-your-playground)
 * [Cards properties](/components/cards#properties)
 
 ### How anchor links are generated
 
 Anchor links are automatically created from header text.
 
@@ -62,7 +62,7 @@
 | `#### Step 1: Install` | `#step-1-install` |
 
 <Note>
   Headers with the `noAnchor` prop will not generate anchor links. See [Format text](/create/text#disabling-anchor-links) for details.
 </Note>
 
 ## Link to API endpoints
@@ -86,7 +86,7 @@
 
 ### Write descriptive link text
 
 Use clear, descriptive text that indicates what users will find when they click.
 
 <CodeGroup>
 
@@ -122,7 +122,7 @@
 ```mdx
 To customize your documentation appearance, configure [themes](/customize/themes) 
 and [fonts](/customize/fonts) in your settings. You can also add 
-[custom scripts](/customize/custom-scripts) for advanced functionality.
+[custom scripts](/customize/custom-scripts) for advanced features.
 ```
 
 ### Link to prerequisites

installation.mdx

@@ -15,13 +15,13 @@
   alt="Decorative graphic representing the CLI."
 />
 
-Use the [CLI](https://www.npmjs.com/package/mint) to preview your documentation locally as you write and edit. View changes in real-time before deploying, test your documentation site's appearance and functionality, and catch issues like broken links or accessibility problems.
+Use the [CLI](https://www.npmjs.com/package/mint) to preview your documentation locally as you write and edit. View changes in real-time before deploying, test your documentation site's appearance and features, and catch issues like broken links or accessibility problems.
 
 The CLI also has utilities for maintaining your documentation, including commands to rename files, validate OpenAPI specifications, and migrate content between formats.
 
 ## Prerequisites
 
 - [Node.js](https://nodejs.org/en) v20.17.0+ (LTS versions recommended) installed
 - [Git](https://git-scm.com/downloads) installed
 - Your documentation repository cloned locally
 
@@ -181,7 +181,7 @@
 mint broken-links
 ```
 
 The command ignores files matching [.mintignore](/organize/mintignore) patterns. Links that point to ignored files are reported as broken.
 
 To also check anchor links like `/path/to/page#anchor`, use the `--check-anchors` flag:
 
@@ -217,7 +217,7 @@
 
 Use flags to configure the validation command.
 
 - `--groups [groupname]`: Mock user groups for validation (useful when testing group-based access control)
 - `--disable-openapi`: Disable OpenAPI file generation during validation
 
 ### Check OpenAPI spec
@@ -228,7 +228,7 @@
 mint openapi-check <OpenAPI filename or URL>
 ```
 
 Pass a filename (for example, `./openapi.yaml`) or a URL (for example, `https://petstore3.swagger.io/api/v3/openapi.json`).
 
 ### Rename files
 
@@ -300,7 +300,7 @@
     ```
   </Accordion>
   <Accordion title="Client version shows 'none' after installation">
     If you run `mint version` and the client version displays as `none`, the CLI may be unable to download the client application due to a corporate firewall or VPN blocking the download.
 
     **Solution:** Ask your IT administrator to whitelist `releases.mintlify.com` to enable local development with the CLI.
   </Accordion>

migration-services/enterprise.mdx

@@ -7,7 +7,7 @@
 
 ## What to expect for your migration
 
 A migration is a point-in-time transfer of your documentation that requires a code freeze. We migrate your documentation, API reference pages, branding (logos, colors, and fonts), and navigation structure. Migration services also include design or information architecture consultation and custom component development such as landing pages or custom integrations.
 
 Your migration includes a staging link to review progress and a 7-day feedback window after delivery to address any issues with content, assets, or branding.
 
@@ -39,7 +39,7 @@
 </Step>
 
 <Step title="Feedback window (seven business days)">
 Submit any feedback on content, assets, or branding. We address all in-scope issues within the same timeframe.
 </Step>
 
 <Step title="Go-live support">
@@ -52,20 +52,20 @@
 We work with vetted third-party vendors and conduct an internal quality audit before delivery. Here's what we check for:
 
 <Card title="Content completeness" icon="file-check">
 - All documentation from your source has been migrated.
 - Content is properly formatted with Mintlify components.
 - Navigation structure matches your specifications.
 </Card>
 
 <Card title="Visual elements" icon="palette">
 - Images and videos display correctly.
 - Custom fonts are applied throughout.
 - Light and dark mode logos are used appropriately.
 - Color schemes meet contrast requirements in both modes.
 </Card>
 
 <Card title="Functionality" icon="rocket">
 - All links work correctly (no broken links).
 - Table of contents renders properly.
 - React components function as expected.
 - No performance issues.
@@ -80,7 +80,7 @@
 3. [Configure your custom domain](/customize/custom-domain).
 4. **Test before going live** - Before switching over from your old documentation:
    - Review all pages on your staging link.
-   - Test navigation and search functionality.
+   - Test navigation and search.
    - Verify all images and videos load correctly.
    - Check that code blocks render properly.
    - Test on mobile and desktop.
@@ -98,7 +98,7 @@
 </Accordion>
 
 <Accordion title="Can I request changes after delivery?">
 Yes. You have a 7-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe and work with you right until you are ready to go live.
 </Accordion>
 
 <Accordion title="What do I need to do after the migration is complete?">
@@ -111,12 +111,12 @@
 </Accordion>
 
 <Accordion title="Can I customize the navigation structure?">
 Yes. You can provide a custom information architecture and we will implement it. We also work with you on custom component development if that is needed and supported by the platform.
 </Accordion>
 
 <Accordion title="What happens if my documentation changes during the migration?">
 Since migrations require a code freeze, any changes made to your source documentation after submission won't be included. We recommend completing all updates before starting the migration.
 
 If this is not possible, our team will work with you to set short sprints to migrate certain sections or reserve dedicated time post the first sprint to migrate the delta changes made during the migration.
 </Accordion>
 </AccordionGroup>

migration-services/pro.mdx

@@ -7,7 +7,7 @@
 
 ## What to expect for your migration
 
 A migration is a point-in-time transfer of your documentation that requires a code freeze. We migrate your documentation, branding (logos, colors, and fonts), API reference pages, and navigation structure.
 
 Your migration includes a staging link to review progress and a 3-day feedback window after delivery to address any issues with content, assets, or branding.
 
@@ -15,7 +15,7 @@
 Migration services **do not** include:
 - Dynamic syncing of your documentation
 - Design or information architecture consultation
 - Custom component development (landing pages, custom integrations, etc.)
 - Redirects setup
 - Analytics setup
 </Info>
@@ -42,7 +42,7 @@
   </Step>
 
   <Step title="Feedback window (three business days)">
     Submit any feedback on content, assets, or branding. We address all in-scope issues within the same timeframe.
   </Step>
 
   <Step title="Go-live support">
@@ -55,20 +55,20 @@
 We work with vetted third-party vendors and conduct an internal quality audit before delivery. Here's what we check for:
 
 <Card title="Content completeness" icon="file-check">
   - All documentation from your source has been migrated.
   - Content is properly formatted with Mintlify components.
   - Navigation structure matches your specifications.
 </Card>
 
 <Card title="Visual elements" icon="palette">
   - Images and videos display correctly.
   - Custom fonts are applied throughout.
   - Light and dark mode logos are used appropriately.
   - Color schemes meet contrast requirements in both modes.
 </Card>
 
 <Card title="Functionality" icon="rocket">
   - All links work correctly (no broken links).
   - Table of contents renders properly.
   - React components function as expected.
   - No performance issues.
@@ -83,7 +83,7 @@
 3. [Configure your custom domain](https://www.mintlify.com/docs/customize/custom-domain).
 4. **Test before going live** - Before switching over from your old documentation:
    - Review all pages on your staging link.
-   - Test navigation and search functionality.
+   - Test navigation and search.
    - Verify all images and videos load correctly.
    - Check that code blocks render properly.
    - Test on mobile and desktop.
@@ -101,7 +101,7 @@
   </Accordion>
 
   <Accordion title="Can I request changes after delivery?">
     Yes. You have a 3-day feedback window after delivery to request changes to content, assets, or branding. We address all in-scope feedback within the same timeframe.
   </Accordion>
 
   <Accordion title="What do I need to do after the migration is complete?">
@@ -114,10 +114,10 @@
   </Accordion>
 
   <Accordion title="Can I customize the navigation structure?">
     Yes. You can provide a custom information architecture in the migration form, and we'll implement it. However, custom component development (like custom landing pages) is not included in the migration service.
   </Accordion>
 
   <Accordion title="What happens if my documentation changes during the migration?">
     Since migrations require a code freeze, any changes made to your source documentation after submission won't be included. We recommend completing all updates before starting the migration.
   </Accordion>
 </AccordionGroup>

migration.mdx

@@ -102,7 +102,7 @@
 </svg>} horizontal />
 </Columns>
 
 If your documentation is hosted on another platform, see the manual migration steps.
 
 ### Installing the scraper
 
@@ -114,7 +114,7 @@
 
 ### Scraping pages and sections
 
 The migration tool automatically detects your documentation platform and converts your content. Prepared files are stored locally in `./docs` by default.
 
 For large documentation sites, migrate smaller sections one at a time rather than the entire site at once.
 
@@ -152,7 +152,7 @@
 
 After scraping your existing documentation platform, you are ready to build your docs on Mintlify.
 
 Confirm that all of your pages have been migrated then add these files to the documentation repository that you created during the onboarding process. This is usually a GitHub repository.
 </Tab>
 <Tab title="Manual migration">
 
@@ -160,11 +160,11 @@
 
 ### Content migration
 
 To migrate your content to Mintlify, you will need:
 
 - A valid `docs.json` for your site settings and navigation. See [Global settings](/organize/settings) and [Navigation](/organize/navigation) for more information.
 - A Markdown file (`.md` or `.mdx`) for each page of your documentation. MDX is the recommended format. See [Pages](/organize/pages) for more information.
 - (Optional) An OpenAPI specification for your API endpoint pages. See [OpenAPI setup](/api-playground/openapi-setup) for more information.
 
 1. If your content is already in Markdown format, copy the content to your Mintlify project. Otherwise, convert your content to MDX format.
 2. Create your `docs.json` referencing the paths to your Markdown pages.
@@ -187,13 +187,13 @@
 
 ## Post-migration checklist
 
 After completing your migration (automated or manual), we recommend checking:
 
 - All pages render
 - Navigation works as intended
 - Internal links resolve properly
 - Images and assets load correctly
 - Code blocks display with proper syntax highlighting
-- Search functionality works
+- Search works
 - Deployment is configured
 - Custom domain is set up