diff options
| author | Kalle Alm <kalle.alm@gmail.com> | 2017-04-14 22:49:34 +0900 |
|---|---|---|
| committer | Kalle Alm <kalle.alm@gmail.com> | 2017-04-14 22:52:11 +0900 |
| commit | 846dc179bcf7296ab9b5f2a56e778e7e96f8123f (patch) | |
| tree | b284dfdbea4484ec593b7efe88d795cfbadda97e /CONTRIBUTING.md | |
| parent | b7365f0545b1a6862e3277b2b2139ee0d5aee1cf (diff) | |
[doc] Wording fixes in CONTRIBUTING.md.
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0766d89f55..b2cf1f810d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,8 +37,8 @@ fixes or code moves with actual code changes. Commit messages should be verbose by default consisting of a short subject line (50 chars max), a blank line and detailed explanatory text as separate -paragraph(s); unless the title alone is self-explanatory (like "Corrected typo -in init.cpp") then a single title line is sufficient. Commit messages should be +paragraph(s), unless the title alone is self-explanatory (like "Corrected typo +in init.cpp") in which case a single title line is sufficient. Commit messages should be helpful to people reading your code in the future, so explain the reasoning for your decisions. Further explanation [here](http://chris.beams.io/posts/git-commit/). |