From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 40011@debbugs.gnu.org, rms@gnu.org
Subject: bug#40011: Remove unnecessary abbreviations from documentation
Date: Mon, 27 Apr 2020 09:41:11 -0700 (PDT) [thread overview]
Message-ID: <920f1068-b0c7-4c40-92fa-4ad219b3dd07@default> (raw)
In-Reply-To: <87lfmg99wq.fsf@stefankangas.se>
> > (minor nit)
> >
> > * "like" -> "such as"
> > * "more clear" -> "clearer"
>
> Thanks. As you might know, English is a
> second language for me so I really
> appreciate this kind of input.
You're welcome. And this is very minor.
Colloquially many (most?) people use "like"
when they really mean "such as".
The difference is that "such as" includes
those explicit examples - it says "these
and others (like them)"; whereas "like"
says "things similar to these things".
"Like" doesn't explicitly include those
things; it says to use them to get an idea
of what kind of things might be included.
1. The award was given to people like
George Washington.
2. The award was given to people such as
George Washington.
#1 says that people with characteristics
like GW got the award. #2 says that GW is
an example of the people who got the award.
In case #2, GW got the award.
---
There's nothing wrong with "more clear".
But "clearer" is usually clearer. ;-)
next prev parent reply other threads:[~2020-04-27 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 13:54 bug#40011: Remove unnecessary abbreviations from documentation Stefan Kangas
2020-03-10 14:49 ` Eli Zaretskii
2020-04-27 6:05 ` Stefan Kangas
2020-04-27 14:39 ` Eli Zaretskii
2020-04-27 17:08 ` Stefan Kangas
2020-04-27 18:30 ` Eli Zaretskii
2020-04-30 16:05 ` Stefan Kangas
2020-04-28 2:46 ` Richard Stallman
2020-04-27 16:08 ` Drew Adams
2020-04-27 16:21 ` Stefan Kangas
2020-04-27 16:41 ` Drew Adams [this message]
2020-04-28 2:49 ` Richard Stallman
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=920f1068-b0c7-4c40-92fa-4ad219b3dd07@default \
--to=drew.adams@oracle.com \
--cc=40011@debbugs.gnu.org \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.