diff options
author | Jeremie Guichard <djebrest@gmail.com> | 2018-04-09 07:59:33 +0200 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2018-04-09 07:48:01 -0700 |
commit | f633cb81ae095ea128a406e69b5eecab23be92a9 (patch) | |
tree | 2a0737a74ff7007b51570488413ce9435f98976f /CONTRIBUTING.md | |
parent | d64c48855df647cc4d80fba6874ae6f89511f7d3 (diff) | |
download | subsurface-f633cb81ae095ea128a406e69b5eecab23be92a9.tar.gz |
Fix minor typos and spelling mistakes in README.md and related
Signed-off-by: Jeremie Guichard <djebrest@gmail.com>
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 a82a797f3..68ea8ca12 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,7 +37,7 @@ Body of commit message is a few lines of text, explaining things in more detail, possibly giving some background about the issue being fixed, etc etc. -The body of the commit message can be several paragrahps, and +The body of the commit message can be several paragraphs, and please do proper word-wrap and keep columns shorter than about 74 characters or so. That way "git log" will show things nicely even when it's indented. @@ -47,7 +47,7 @@ Signed-off-by: Your Name That header line really should be meaningful, and really should be just one line. The header line is what is shown by tools like gitk and shortlog, and should summarize the change in one readable line of text, independently of the longer explanation. -The prefered way to write a commit message is using imperative mood, e.g. "Make foo do xyz" instead of "This patch makes foo do xyz" or "I made foo do xyz", as if you are giving commands or requests to the code base. +The preferred way to write a commit message is using imperative mood, e.g. "Make foo do xyz" instead of "This patch makes foo do xyz" or "I made foo do xyz", as if you are giving commands or requests to the code base. https://en.wikipedia.org/wiki/Imperative_mood ![gitk sample][10] |