You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unify terminology in create/text.mdx so the page uses "heading" consistently for Markdown headings, matching the page's own frontmatter description and the existing "Custom heading IDs" section.
Replaced "header"/"headers" with "heading"/"headings" throughout prose, tips, code-block titles, and best-practices bullets where referring to Markdown headings.
Updated the keywords frontmatter entry from headers to headings to match.
Context
The page mixed "header" and "heading" interchangeably (11 uses of "header" vs. 6 of "heading") while the page description and the {#custom-id} section already standardized on "heading". No other style deviations (voice, sentence length, heading case) were found in the file in scope.
Note
Low Risk
Documentation-only wording changes in a single MDX page; no runtime, API, or build behavior.
Overview
Standardizes Markdown terminology in create/text.mdx by replacing header with heading everywhere the doc talks about # section titles.
Section titles change from Headers / Create headers to Headings / Create headings, and matching wording updates run through tips, examples, noAnchor notes, horizontal-rule guidance, and best-practices bullets. Frontmatter keywords now lists headings instead of headers, aligned with the page description and Custom heading IDs.
Reviewed by Cursor Bugbot for commit dba8c8a. Bugbot is set up for automated code reviews on this repo. Configure here.
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
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
Unify terminology in
create/text.mdxso the page uses "heading" consistently for Markdown headings, matching the page's own frontmatter description and the existing "Custom heading IDs" section.Changes
## Headers→## Headingsand### Create headers→### Create headings.keywordsfrontmatter entry fromheaderstoheadingsto match.Context
The page mixed "header" and "heading" interchangeably (11 uses of "header" vs. 6 of "heading") while the page description and the
{#custom-id}section already standardized on "heading". No other style deviations (voice, sentence length, heading case) were found in the file in scope.Note
Low Risk
Documentation-only wording changes in a single MDX page; no runtime, API, or build behavior.
Overview
Standardizes Markdown terminology in
create/text.mdxby replacing header with heading everywhere the doc talks about#section titles.Section titles change from Headers / Create headers to Headings / Create headings, and matching wording updates run through tips, examples,
noAnchornotes, horizontal-rule guidance, and best-practices bullets. Frontmatter keywords now listsheadingsinstead ofheaders, aligned with the page description and Custom heading IDs.Reviewed by Cursor Bugbot for commit dba8c8a. Bugbot is set up for automated code reviews on this repo. Configure here.