doc: singular/plural agreement, since it's easy.

* HACKING: singular/plural agreement.
* t/README: likewise.

diff --git a/HACKING b/HACKING
index 2a0894046ac35f5724e17ee30f44c5fbcb3a737c..4ee6ab3cc52908bec725a3d06265e04c484bdb1d 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -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

diff --git a/t/README b/t/README
index 3431487e6acff4252c246b801a920021b64be4f2..16096ca7bda8b7bdbe809bacb5e4c23e8f214298 100644 (file)
--- a/t/README
+++ b/t/README
@@ -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