fix(beta): reset callout headings to H2s #941
Merged
Conversation
This file contains 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
kellyjosephprice
approved these changes
Jul 16, 2024
rafegoldberg
pushed a commit
that referenced
this pull request
Jul 30, 2024
## Version 6.75.0-beta.79 ### 🛠 Fixes & Updates * **beta:** reset callout headings to H2s ([#941](#941)) ([08220ba](08220ba)), closes [/github.com/readmeio/markdown/blob/ad07529eef2513e83072dc31f0469a5f36603957/components/Callout/index.jsx#L11](https://github.com/readmeio//github.com/readmeio/markdown/blob/ad07529eef2513e83072dc31f0469a5f36603957/components/Callout/index.jsx/issues/L11) <!--SKIP CI-->
|
This PR was released!🚀 Changes included in v6.75.0-beta.79 |
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.
🧰 Changes
RMDX wraps callout headings in
<h3>tags, but historically, RDMD has marked these up as<h2>s. (Not sure if there was a reason for this change, but it's making it hard to tell which docs will actually be impacted by the migration!)<h2>