docs: normalize heading capitalization to title case#482
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Fix four headings that deviated from the docs' predominant Title Case heading style.
Changes
configuration/source-db/sql-server-additional-configuration.mdx— "using" → "Using"integrations/flutterflow/legacy-guide.mdx— "all" → "All"resources/hipaa.mdx— "can" → "Can", "available?" → "Available?"Context
Scan of all 216 MDX files found that ~96% of headings use Title Case (264 vs 10 H2s; 326 vs 21 H3s). Most apparent sentence-case headings are intentional (error code labels like
PSYNC_S1xxx: Replication issues, numbered steps, code-prefixed names). Only these four headings were unambiguous deviations within otherwise consistent files (e.g.,hipaa.mdxalready had "What Is the Difference..." and "How Often Is PowerSync Audited?" in title case alongside the two fixed here).No changes made to voice (second-person usage was consistent, with "the user"/"users" appropriately referring to end-users of the reader's app), terminology (click/select used consistently), or sentence structure — those checks surfaced no clear deviations worth correcting without risking changed meaning.