Message-ID: <f2fcd2a8f75bde26ae20cf5777e716f3fc3b8046.camel@cybertec.at>
Subject: Re: Typo
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Michael Paquier <michael@paquier.xyz>, pspung@northcarolina.edu,
	pgsql-docs@lists.postgresql.org
Date: Wed, 24 May 2023 06:02:27 +0200
In-Reply-To: <ZG0+9kCWYg9tzL6m@paquier.xyz>
References: <168487514505.719.16546639844327379750@wrigleys.postgresql.org>
	 <ZG0+9kCWYg9tzL6m@paquier.xyz>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/f2fcd2a8f75bde26ae20cf5777e716f3fc3b8046.camel%40cybertec.at>
Precedence: bulk

On Wed, 2023-05-24 at 07:32 +0900, Michael Paquier wrote:
> On Tue, May 23, 2023 at 08:52:25PM +0000, PG Doc comments form wrote:
> > There appears to be a typo, here:
> > https://www.postgresql.org/docs/current/history.html#:~:text=3DPostgres=
95%20code%20was%20completely%20ANSI%20C.
> > A word or two should be added between 'completely' and 'ANSI C', such a=
s
> > 're-written in', or 're-coded using', or some such.
>=20
> This is the current sentence, and it sounds kind of OK to me, FWIW:
> "Postgres95 code was completely ANSI C and trimmed in size by 25%.

That uses "ANSI C" as an adjective, which I think is sloppy wording
(even though English is somewhat relaxed about the distinction between
classes of words).

How about: "... was written completely in ANSI C ..."

Yours,
Laurenz Albe