All of lore.kernel.org
 help / color / mirror / Atom feed
From: J William Piggott <elseifthen@gmx.com>
To: Peter Cordes <peter@cordes.ca>
Cc: Benno Schulenberg <bensberg@justemail.net>, util-linux@vger.kernel.org
Subject: Re: [PATCH 8/8] docs: add the Sort command to the man page of	cfdisk
Date: Sun, 01 Feb 2015 19:21:07 -0500	[thread overview]
Message-ID: <54CEC2F3.7060906@gmx.com> (raw)
In-Reply-To: <20150201212138.GV29504@cordes.ca>



On 02/01/2015 04:21 PM, Peter Cordes wrote:
> On Sun, Feb 01, 2015 at 02:38:10PM -0500, J William Piggott wrote:
>>
>>
>> On 02/01/2015 09:00 AM, Benno Schulenberg wrote:
>>> Also sort T into its proper position, improve the wording of U,
>>> and add the Left and Right arrow keys.
>>>
>>> Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
>>> ---
>>>  disk-utils/cfdisk.8 |   38 +++++++++++++++++++++++---------------
>>>  1 files changed, 23 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/disk-utils/cfdisk.8 b/disk-utils/cfdisk.8
>>> index dc30b70..e4577d5 100644
>>> --- a/disk-utils/cfdisk.8
>>> +++ b/disk-utils/cfdisk.8
> ...
>>>  .PP
>>>  All commands can be entered with either uppercase or lowercase
>>>  letters (except for
>>>  .BR W rite).
>>> -When in a submenu or at a prompt for entering a size, you can hit the
>>> -.I ESC
>>> +When in a submenu or at a prompt, you can hit the
>>> +.I Esc
>>>  key to return to the main menu.
>>
>> s/can hit/may use/
> 
>  I think "can" is better.  "can use", though, rather than "can hit".
> There's a "can be entered" earlier in the paragraph, which I think is
> good usage.
> 
> "may" sounds like either the docs / software is giving you permission
> to use this feature,

Yes, that is exactly why 'may' is better. One 'can' use the <ESC>
anytime, I'm hitting it right now. Can means: it is possible.

What is being said, is in this particular circumstance the program
'allows' you to use that key and something will happen.

Having said that, grammatically either one is considered acceptable.
So 'can vs may' is a subjective call, but 'hit' needs to go IMO.


> or commenting on whether or not you might
> actually use the feature.
> 
> 
>  Docs should get their meaning across with as simple and
> straightforward language as possible, for quick reading and
> understanding by as many people as possible.  And hopefully not
> distract ADHD people like me into thinking about re-wording them while
> I'm in the middle of trying to figure out how to do something else :P.
> 

  reply	other threads:[~2015-02-02  0:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 14:00 [PATCH 1/8] cfdisk: remove the mistaken B from the explanation of size suffixes Benno Schulenberg
2015-02-01 14:00 ` [PATCH 2/8] cfdisk: improve wording and consistency of the size warnings Benno Schulenberg
2015-02-01 14:00 ` [PATCH 3/8] cfdisk: punctuate the bottombar messages consistently Benno Schulenberg
2015-02-01 14:00 ` [PATCH 4/8] cfdisk: make '?' an alias of 'h', to also show the help screen Benno Schulenberg
2015-02-01 14:00 ` [PATCH 5/8] lib/strutils: accept not just 'B' but also lowercase 'b' in a size suffix Benno Schulenberg
2015-02-01 14:00 ` [PATCH 6/8] libfdisk: actually translate the human-readable name of the partition type Benno Schulenberg
2015-02-01 14:00 ` [PATCH 7/8] build-sys: improve wording and punctuation of several messages Benno Schulenberg
2015-02-01 14:00 ` [PATCH 8/8] docs: add the Sort command to the man page of cfdisk Benno Schulenberg
2015-02-01 19:38   ` J William Piggott
2015-02-01 21:21     ` Peter Cordes
2015-02-02  0:21       ` J William Piggott [this message]
2015-02-02  1:12         ` Peter Cordes
2015-02-02 10:03     ` Karel Zak
2015-02-02  9:59 ` [PATCH 1/8] cfdisk: remove the mistaken B from the explanation of size suffixes Karel Zak

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=54CEC2F3.7060906@gmx.com \
    --to=elseifthen@gmx.com \
    --cc=bensberg@justemail.net \
    --cc=peter@cordes.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.