Home Original page

doc: use consistent markdown in README by Trott · Pull Request #7971 · nodejs/node

@Trott added the doc

Issues and PRs related to the documentations.

label

Aug 3, 2016

@Trott 

Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

@Trott

@Trott

@Trott

ChALkeR added a commit that referenced this pull request

Aug 4, 2016 
Continuing what a58b48b did for the
doc/ dir, this fixes some formatting issues in the *.md files that
are placed directly in the top-level directory.

README.md changes are excluded as they are covered by
#7971

Refs: #7637

ChALkeR added a commit to ChALkeR/io.js that referenced this pull request

Aug 4, 2016 
Continuing what a58b48b did for the
doc/ dir, this fixes some formatting issues in the *.md files that
are placed directly in the top-level directory.

README.md changes are excluded as they are covered by
nodejs#7971

Refs: nodejs#7637
PR-URL: nodejs#7727
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

jasnell pushed a commit that referenced this pull request

Aug 5, 2016 
Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

PR-URL: #7971
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

cjihrig pushed a commit that referenced this pull request

Aug 10, 2016 
Continuing what a58b48b did for the
doc/ dir, this fixes some formatting issues in the *.md files that
are placed directly in the top-level directory.

README.md changes are excluded as they are covered by
#7971

Refs: #7637
PR-URL: #7727
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

cjihrig pushed a commit that referenced this pull request

Aug 10, 2016 
Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

PR-URL: #7971
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

MylesBorins pushed a commit that referenced this pull request

Sep 9, 2016 
Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

PR-URL: #7971
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

MylesBorins pushed a commit that referenced this pull request

Sep 28, 2016 
Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

PR-URL: #7971
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

rvagg pushed a commit that referenced this pull request

Oct 18, 2016 
Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

PR-URL: #7971
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

MylesBorins pushed a commit that referenced this pull request

Oct 26, 2016 
Improve markdown practices in README:

* consistent header indicators
* consistent emphasis indicators
* wrap bare URLs in `<` and `>`
* wrap at 80 chars
* specifying language in fenced code

PR-URL: #7971
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>