diff options
author | Karl Berry <karl@freefriends.org> | 2022-01-23 14:27:11 -0800 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2022-01-23 14:27:11 -0800 |
commit | b64df48bd97ea9ed3674ad63751e6dccfd458d87 (patch) | |
tree | d7ec825148d1e4798067e044c2c4dadcbae1a714 | |
parent | a4e22a7bf67fbd0b08781e7f23ba6a7cc2c0a173 (diff) | |
download | automake-b64df48bd97ea9ed3674ad63751e6dccfd458d87.tar.gz |
doc: singular/plural agreement, since it's easy.
* HACKING: singular/plural agreement.
* t/README: likewise.
-rw-r--r-- | HACKING | 5 | ||||
-rw-r--r-- | t/README | 2 |
2 files changed, 4 insertions, 3 deletions
@@ -24,8 +24,9 @@ the short url form, like https://bugs.gnu.org/1234. See section below about commit messages. -* If somebody reports a new bug, mention their name in the commit message - that fixes or exposes the bug, and add a line for them in THANKS. +* If a person or people report a new bug, mention their name(s) in the + commit message that fixes or exposes the bug, and add a line for them + in THANKS. * When documenting a non-trivial idiom or example in the manual, be sure to add a test case for it, and to reference such test case from @@ -222,7 +222,7 @@ Writing test cases than another. * Use cat or grep or similar commands to display (part of) files that - may be interesting for debugging, so that when a user send a verbose + may be interesting for debugging, so that when users send verbose output we don't have to ask them for more details. Display stderr output on the stderr file descriptor. If some redirected command is likely to fail, display its output even in the failure case, before |