public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH 3/3] xfs_quota: make manpage non-male-specific
Date: Thu, 3 Dec 2020 14:01:24 -0600	[thread overview]
Message-ID: <9fde98da-d221-87d0-a401-2c82cf1df35f@redhat.com> (raw)
In-Reply-To: <44dcd8f3-0585-e463-499f-44256d8bad8d@redhat.com>

Users are not exclusively male, so fix that implication.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
 man/man8/xfs_quota.8 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man/man8/xfs_quota.8 b/man/man8/xfs_quota.8
index bfdc2e4f..beb6da13 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 his 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
-- 
2.17.0


  parent reply	other threads:[~2020-12-03 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 19:53 [PATCH 0/3] xfs_quota: man page fixups Eric Sandeen
2020-12-03 20:00 ` [PATCH 1/3] xfs_quota: document how the default quota is stored Eric Sandeen
2020-12-03 20:07   ` Darrick J. Wong
2020-12-03 20:12     ` Eric Sandeen
2020-12-03 20:38       ` Darrick J. Wong
2020-12-03 20:36   ` [PATCH 1/3 V2] " Eric Sandeen
2020-12-03 20:46   ` [PATCH 1/3 V3] " Eric Sandeen
2020-12-03 21:20     ` Darrick J. Wong
2020-12-03 20:00 ` [PATCH 2/3] xfs_quota: Remove delalloc caveat from man page Eric Sandeen
2020-12-03 20:08   ` Darrick J. Wong
2020-12-03 20:01 ` Eric Sandeen [this message]
2020-12-03 20:10   ` [PATCH 3/3] xfs_quota: make manpage non-male-specific Darrick J. Wong
2020-12-03 20:15     ` Eric Sandeen
2020-12-03 20:33   ` [PATCH 3/3 V2] xfsprogs: make things non-gender-specific Eric Sandeen
2020-12-03 20:40     ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9fde98da-d221-87d0-a401-2c82cf1df35f@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox