Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: Typos in the code and README
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <f6c71f45-8473-482c-a6f7-ed8f0641e11c@iki.fi>
Date: Fri, 12 Apr 2024 23:17:11 +0200
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E020742-206E-4052-83AF-8721190A10E0@yesql.se>
References: <3F577953-A29E-4722-98AD-2DA9EFF2CBB8@yesql.se>
 <f6c71f45-8473-482c-a6f7-ed8f0641e11c@iki.fi>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Archived-At: <https://www.postgresql.org/message-id/3E020742-206E-4052-83AF-8721190A10E0%40yesql.se>
Precedence: bulk

> On 12 Apr 2024, at 23:15, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>=20
> On 11/04/2024 16:05, Daniel Gustafsson wrote:
>> Now that the tree has settled down a bit post-freeze I ran some =
tooling to
>> check spelling.  I was primarily interested in docs and README* which =
were
>> mostly free from simply typos, while the code had some in various =
comments and
>> one in code.  The attached fixes all that I came across (not =
cross-referenced
>> against ongoing reverts or any other fixup threads but will be before =
pushing
>> of course).
>=20
> Here's a few more. I've accumulate these over the past couple of =
months, keeping them stashed in a branch, adding to it whenever I've =
spotted a minor typo while reading the code.

Nice, let's lot all these together.

--
Daniel Gustafsson