From e239c813bd55f2ceea478812208cf4ee629e83a3 Mon Sep 17 00:00:00 2001 From: Derek Lewis Date: Sun, 24 May 2020 00:59:13 -0400 Subject: [PATCH] doc: normalize Markdown code block info strings 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 --- doc/guides/releases.md | 2 +- tools/doc/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/releases.md b/doc/guides/releases.md index 68f4d0b8bacc6f..2e7e3c6eb6f2ea 100644 --- a/doc/guides/releases.md +++ b/doc/guides/releases.md @@ -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 ## YYYY-MM-DD, Version x.y.z (Release Type), @releaser diff --git a/tools/doc/README.md b/tools/doc/README.md index 3679c2c23df6e2..f2f37faa653d4d 100644 --- a/tools/doc/README.md +++ b/tools/doc/README.md @@ -4,7 +4,7 @@ Here's how the node docs work. Each type of heading has a description block. -```md +```markdown # module