From 4aa8120aeab54a87568e51feb945b7ae2809f8ae Mon Sep 17 00:00:00 2001 From: Сковорода Никита Андреевич Date: Thu, 14 Jul 2016 12:55:30 +0300 Subject: doc: *.md formatting fixes in the top-level dir MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Continuing what a58b48bc3bcf43f7090d4cc914606af68fe55815 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 https://github.com/nodejs/node/pull/7971 Refs: https://github.com/nodejs/node/pull/7637 PR-URL: https://github.com/nodejs/node/pull/7727 Reviewed-By: Rich Trott Reviewed-By: Michaël Zasso Reviewed-By: James M Snell --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'CONTRIBUTING.md') diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 500e0a79d5..ba8ca3da72 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -100,7 +100,7 @@ changed and why. Follow these guidelines when writing one: A good commit log can look something like this: -``` +```txt subsystem: explaining the commit in one line Body of commit message is a few lines of text, explaining things @@ -122,7 +122,7 @@ what subsystem (or subsystems) your changes touch. If your patch fixes an open issue, you can add a reference to it at the end of the log. Use the `Fixes:` prefix and the full issue URL. For example: -``` +```txt Fixes: https://github.com/nodejs/node/issues/1337 ``` -- cgit v1.2.3