Users are not exclusively male, so fix that implication
in the xfs_quota manpage and the configure.ac comments.
Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx>
---
V2: Fix configure.ac comments too, and fix a missed "him" in the manpage
also "choses" is not a word :)
diff --git a/configure.ac b/configure.ac
index 645e4572..48f3566d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -113,7 +113,7 @@ esac
# Some important tools should be installed into the root partitions.
#
# Check whether exec_prefix=/usr: and install them to /sbin in that
-# case. If the user choses a different prefix assume he just wants
+# case. If the user chooses a different prefix assume they just want
# a local install for testing and not a system install.
#
case $exec_prefix:$prefix in
diff --git a/man/man8/xfs_quota.8 b/man/man8/xfs_quota.8
index 74c24916..cfb87621 100644
--- a/man/man8/xfs_quota.8
+++ b/man/man8/xfs_quota.8
@@ -128,7 +128,7 @@ To most users, disk quotas are either of no concern or a fact of life
that cannot be avoided.
There are two possible quotas that can be imposed \- a limit can be set
on the amount of space a user can occupy, and there may be a limit on
-the number of files (inodes) he can own.
+the number of files (inodes) they can own.
.PP
The
.B quota
@@ -167,10 +167,10 @@ the file, not only are the recent changes lost, but possibly much, or even
all, of the contents that previously existed.
.br
There are several possible safe exits for a user caught in this situation.
-He can use the editor shell escape command to examine his file space
+They can use the editor shell escape command to examine their file space
and remove surplus files. Alternatively, using
.BR sh (1),
-he can suspend
+they can suspend
the editor, remove some files, then resume it.
A third possibility is to write the file to some other filesystem (perhaps
to a file on
