From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: jon77h@gmail.com
Subject: i.e. and e.g. used with incorrect meaning
Date: Thu, 14 Jan 2021 13:15:41 +0000
Message-ID: <161063014110.12228.7559626703707296001@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/ssh-tunnels.html
Description:
You're gonna hate this -- a grammar nit pick.
But for the few of us who know what e.g. and i.e. mean, the wrong one is
confusing.
e.g. = exempli gratia = for example.
i.e. = id est = that is.
"that is" implies that there's no other option.
"for example" implies that there are other options.
So in the following text, they seem to be the wrong way round:
"The name or IP address after this is the remote bind address you are
connecting to, i.e., localhost, which is the default. The second number,
5432, is the remote end of the tunnel, e.g., the port number your database
server is using."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, jon77h@gmail.com
Subject: Re: i.e. and e.g. used with incorrect meaning
In-Reply-To: <161063014110.12228.7559626703707296001@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox