Skip to content

Commit

Permalink
doc: normalize Markdown code block info strings
Browse files Browse the repository at this point in the history
Prior to this commit, Markdown fenced code blocks in Markdown
files had inconsistent info strings. This has been corrected to
standardize on the one shown in the CommonMark spec.

Refs: https://github.com/commonmark/commonmark-spec/blob/1103710025f340702edcb070be41f9982b6544d5/spec.txt#L131

PR-URL: #33542
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
  • Loading branch information
Derek Lewis authored and codebytere committed Jul 8, 2020
1 parent a5ce90c commit a3b6095
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion doc/guides/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -283,7 +283,7 @@ in the release branch (e.g. a release for Node.js v4 would be added to the

The new entry should take the following form:

```md
```markdown
<a id="x.y.x"></a>
## YYYY-MM-DD, Version x.y.z (Release Type), @releaser

Expand Down
2 changes: 1 addition & 1 deletion tools/doc/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Here's how the node docs work.

Each type of heading has a description block.

```md
```markdown
# module

<!--introduced_in=v0.10.0-->
Expand Down

0 comments on commit a3b6095

Please sign in to comment.