Apply Vale style fixes: replace 'functionality' with preferred terms

[mintlify]

Summary

• Replaced 11 instances of "functionality" with preferred alternatives per the Mintlify Vale WordList rule
• Used "feature", "capability", or simpler phrasing depending on context

Files changed

File	Change
components/color.mdx	"click-to-copy functionality" → "click-to-copy feature"
deploy/ghes.mdx	"affect functionality" → "affect features"
deploy/route53-cloudfront.mdx	"the functionality of the CloudFront" → "the capabilities of the CloudFront"
guides/content-templates.mdx	"product's functionality" → "product's features"
guides/content-types.mdx	"product's functionality" → "product's features"
guides/cursor.mdx	"bulk user import functionality" → "bulk user import feature"
guides/linking.mdx	"advanced functionality" → "advanced features"
installation.mdx	"appearance and functionality" → "appearance and features"
migration-services/enterprise.mdx	"search functionality" → "search"
migration-services/pro.mdx	"search functionality" → "search"
migration.mdx	"Search functionality works" → "Search works"

Issues requiring human judgment

Will usage (warning) - ~50 instances

Replace "will" with present tense. Examples:

• quickstart.mdx:162: "preview how your pages will look"
• deploy/preview-deployments.mdx:11: "changes to your docs will look before merging"
• optimize/pdf-exports.mdx:31: "you will receive an email"

Exclamation points (error) - ~10 instances

Found in banner examples (intentionally demonstrative):

• components/banner.mdx:14,59,72
• organize/settings.mdx:625
• organize/navigation.mdx:574,587

First person (warning) - ~15 instances

Found in FAQ accordion titles where first person is appropriate:

• migration-services/pro.mdx:103,107,116
• deploy/ghes.mdx:226,230,249

These require editorial review to determine appropriate rewording.

---

Note

Low Risk
Pure copy edits in documentation with no code or behavioral changes; low risk beyond minor wording nuance.

Overview
Updates multiple MDX docs to replace the term “functionality” with preferred wording (primarily “feature(s)” or “capabilities”) to align with the Vale WordList style rule.

Also simplifies a few checklist-style phrases (for example, “search functionality” → “search”), without changing any documented behavior or procedures.

^{Written by Cursor Bugbot for commit 4954eef. This will update automatically on new commits. Configure here.}