Fix Vale style violation: file name → filename#3618
Merged
Conversation
Generated-By: mintlify-agent
ethanpalm
approved these changes
Feb 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
editor/publish.mdx:50Issues requiring human judgment
The following Vale warnings were identified but require manual review as they may be intentional:
Will.yml warnings (use of "will")
These are suggestions to avoid future tense. Many are appropriate in context:
quickstart.mdxoptimize/pdf-exports.mdxmigration.mdxintegrations/analytics/google-analytics.mdxcustomize/custom-scripts.mdxcreate/text.mdxcreate/files.mdxcomponents/view.mdxapi-playground/troubleshooting.mdxRecommendation: These are mostly appropriate for describing expected behavior. Consider reviewing on a case-by-case basis if active voice is preferred.
Ellipses (Ellipses.yml warnings)
All ellipses found are in valid contexts:
# ...,/*...*/No action required - these are intentional.
Passive voice (Passive.yml suggestions)
Found ~50+ instances of passive voice. Most are appropriate for technical documentation (e.g., "files are ignored", "data is collected"). Review if a more active voice is desired for specific sections.
Note
Low Risk
Single-word documentation edit with no functional or behavioral impact.
Overview
Fixes a documentation style/wording issue in
editor/publish.mdxby changing “file name” to “filename” in the instructions for undoing changes, aligning with Vale WordList rules.Written by Cursor Bugbot for commit 7e530ff. This will update automatically on new commits. Configure here.