From: Karel Zak <kzak@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 5/5] Manual pages: various: reword "allow(s) to"
Date: Tue, 14 Jul 2020 14:14:20 +0200 [thread overview]
Message-ID: <20200714121420.fvmuuasgkq5hrtcz@ws.net.home> (raw)
In-Reply-To: <20200714095741.45292-5-mtk.manpages@gmail.com>
On Tue, Jul 14, 2020 at 11:57:41AM +0200, Michael Kerrisk (man-pages) wrote:
> The wording "allow(s) to" is not grammatical English. Reword various
> pages to use a more correct form such "can be use to" or "allows
> the [noun] of".
>
> Aklong the way, fix a few nearby wording errors in some pages.
Some of the "allow to" has been already fixed by Bjarni Ingi Gislason
(well, his fix is "allows <verb>ing" -- not sure what is better ;-).
The rest has been merged without change.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2020-07-14 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 9:57 [PATCH 1/5] manual pages: adjtime_config.5: format pathname with .I Michael Kerrisk (man-pages)
2020-07-14 9:57 ` [PATCH 2/5] Manual pages: login.1: SEE ALSO: add utmp(5), lastlog(8) Michael Kerrisk (man-pages)
2020-07-14 9:57 ` [PATCH 3/5] Manual pages: login.1: formatting fixes Michael Kerrisk (man-pages)
2020-07-14 9:57 ` [PATCH 4/5] Manual pages: login.1: various minor wording fixes Michael Kerrisk (man-pages)
2020-07-14 9:57 ` [PATCH 5/5] Manual pages: various: reword "allow(s) to" Michael Kerrisk (man-pages)
2020-07-14 12:13 ` Michael Kerrisk (man-pages)
2020-07-14 12:38 ` Karel Zak
2020-07-14 12:40 ` Michael Kerrisk (man-pages)
2020-07-14 12:14 ` Karel Zak [this message]
2020-07-14 12:33 ` Michael Kerrisk (man-pages)
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=20200714121420.fvmuuasgkq5hrtcz@ws.net.home \
--to=kzak@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).