diff options
| author | Daijiro Wachi <daijiro.wachi@gmail.com> | 2017-05-28 22:20:21 +0200 |
|---|---|---|
| committer | Daijiro Wachi <daijiro.wachi@gmail.com> | 2017-05-30 19:18:48 +0200 |
| commit | 1d60fc3aa5b7a6032665595c29bdb382bd526e43 (patch) | |
| tree | 43434f364f452b40ee37e071f47c73a00f52affc /doc/releases.md | |
| parent | a85b48cbd37e4c0b1cf2f99f2e9f7d30d7fa34cf (diff) | |
| download | android-node-v8-1d60fc3aa5b7a6032665595c29bdb382bd526e43.tar.gz android-node-v8-1d60fc3aa5b7a6032665595c29bdb382bd526e43.tar.bz2 android-node-v8-1d60fc3aa5b7a6032665595c29bdb382bd526e43.zip | |
doc: fix doc styles
BUILDING.md
+ L122: Missing code-language flag
+ L170: Strong should use `*` as a marker
doc/changelogs/CHANGELOG_V6.md
+ L1494: Don't pad `emphasis` with inner spaces
doc/guides/maintaining-V8.md
+ L3: Don't use multiple top level headings
+ L16: Don't use multiple top level headings
+ L40: Don't use multiple top level headings
+ L124: Don't use multiple top level headings
+ L182: Missing code-language flag
+ L223: Don't use multiple top level headings
+ L288: Don't use multiple top level headings
+ L307: Don't use multiple top level headings
doc/guides/writing-tests.md
+ L322: Missing code-language flag
+ L329: Missing code-language flag
doc/releases.md
+ L299: Missing code-language flag
PR-URL: https://github.com/nodejs/node/pull/13270
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Alexey Orlenko <eaglexrlnk@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Diffstat (limited to 'doc/releases.md')
| -rw-r--r-- | doc/releases.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/releases.md b/doc/releases.md index eafc906026..f1f82fdb98 100644 --- a/doc/releases.md +++ b/doc/releases.md @@ -296,7 +296,7 @@ Create a new blog post by running the [nodejs.org release-post.js script](https: * The links to the download files won't be complete unless you waited for the ARMv6 builds. Any downloads that are missing will have `*Coming soon*` next to them. It's your responsibility to manually update these later when you have the outstanding builds. * The SHASUMS256.txt.asc content is at the bottom of the post. When you update the list of tarballs you'll need to copy/paste the new contents of this file to reflect those changes. * Always use pull-requests on the nodejs.org repo. Be respectful of that working group, but you shouldn't have to wait for PR sign-off. Opening a PR and merging it immediately _should_ be fine. However, please follow the following commit message format: -``` +```console Blog: vX.Y.Z release post Refs: <full URL to your release proposal PR> |