blog: fix heading levels in Electron 40 and 41 release blogs#1111
Merged
Conversation
Following the same standardization as #952, promote nested "Breaking Changes"/"New Features and Improvements" sections to top-level h2s and their children to h3s.
Deploying electron-website with
|
| Latest commit: |
8aeb51f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a176de76.electron-website.pages.dev |
| Branch Preview URL: | https://claude-audit-blog-headings-j.electron-website.pages.dev |
VerteDinde
approved these changes
May 7, 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
4 participants
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
Continues the cleanup started in #952, which standardized heading levels in release blog posts but only covered posts up through Electron 39. The Electron 40 and 41 posts have the same heading-level inconsistencies that #952 set out to fix.
blog/electron-40-0.md"New Features and Improvements" and "Breaking Changes" were nested under "Stack Changes" as
###instead of being top-level peers. Promoted them to##and bumped their children from####to###.blog/electron-41-0.md"Breaking Changes" was at
###instead of##, with its children one level too deep at####. Promoted accordingly.After this PR, the heading hierarchy in both posts matches the standard from #952:
The Electron 42 post already follows this structure, so no changes were needed there.
Test plan
https://claude.ai/code/session_014rV49r1Rmk6mej76CWCK8e
Generated by Claude Code