doc: fix spelling in release announcement guidance#62663
doc: fix spelling in release announcement guidance#62663Rohan5commit wants to merge 1 commit intonodejs:mainfrom
Conversation
Signed-off-by: Codex <codex@openai.com>
|
Review requested:
|
There was a problem hiding this comment.
Pull request overview
Fixes a typo in the release announcement contributor documentation, improving clarity in the “Announce” section of the release process guidance.
Changes:
- Corrects
offical→officialin release announcement guidance text. - Updates the affected Markdown line (including leading whitespace) in the “Announce” section.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| To announce the build on social media, please ping the @nodejs-social-team | ||
| on offical slack channel. | ||
| on official slack channel. |
There was a problem hiding this comment.
Consider capitalizing “Slack” for consistency with other parts of this document (e.g., later sections refer to “Slack channel”). Also, the sentence reads more naturally as “on the official Slack channel.”
| To announce the build on social media, please ping the @nodejs-social-team | ||
| on offical slack channel. | ||
| on official slack channel. |
There was a problem hiding this comment.
This change also removes leading indentation before the continuation line. In Markdown, indentation can change rendering (e.g., turning text into a code block). If the intent is only a spelling fix, consider either keeping the original indentation or updating the PR description to reflect the formatting change.
aduh95
added
fast-track
|
Fast-track has been requested by @aduh95. Please 👍 to approve. |
Summary
officaltoofficialindoc/contributing/releases.md.Related issue
N/A (trivial docs typo fix)
Guideline alignment
Validation