[PATCH] Use gender-neutral pronouns in HACKING and t/README

[Matthew Leeds]

---
 HACKING  | 4 ++--
 t/README | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/HACKING b/HACKING
index 059ef5ab2..c832a5f5d 100644
--- a/HACKING
+++ b/HACKING
@@ -13,22 +13,22 @@

 * If you incorporate a change from somebody on the net:
   - First, if it is a large change, you must make sure they have
     signed the appropriate paperwork.
   - Second, be sure to add their name and email address to THANKS.

 * If a change fixes a test, mention the test in the commit message.
   If a change fixes a bug registered in the Automake debbugs tracker,
   mention the bug number in the commit message.

-* If somebody reports a new bug, mention his name in the commit message
-  that fixes or exposes the bug, and put him into THANKS.
+* If somebody reports a new bug, mention their name in the commit
+  message that fixes or exposes the bug, and put them into 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
   a proper Texinfo comment.

 * Some files in the automake package are not owned by automake; these
   files are listed in the $(FETCHFILES) variable in Makefile.am.  They
   should never be edited here.  Almost all of them can be updated from
   respective upstreams with "make fetch" (this should be done especially
   before releases).  The only exception is the 'lib/COPYING' (from FSF),
diff --git a/t/README b/t/README
index 23dd943f5..4178a096f 100644
--- a/t/README
+++ b/t/README
@@ -216,21 +216,21 @@ Writing test cases
   the AM_MAKEFLAGS to propagate the variable definitions along to
   sub-make:

     run_make prefix=/opt install        # GOOD

 * Use '$sleep' when you have to make sure that some file is newer
   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
-  output we don't have to ask him for more details.  Display stderr
+  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
   exiting.

 * Use '$PATH_SEPARATOR', not hard-coded ':', as the separator of
   PATH's entries.

 * It's more important to make sure that a feature works, than make
   sure that Automake's output looks correct.  It might look correct
   and still fail to work.  In other words, prefer running 'make' over
-- 
2.14.3