MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 02 Sep 2019 18:05:00 +0200
From: Erik Rijkers <er@xs4all.nl>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, PostgreSQL Advocacy
 <pgsql-advocacy@lists.postgresql.org>
Subject: Re: PostgreSQL 12 Press Release - First Draft
In-Reply-To: <aec12df5-688f-620c-8563-c0d824d063f5@postgresql.org>
References: <c56eeb88-4a8c-2c6c-b5f1-9d46872c247c@postgresql.org>
 <0736c146-d9a1-b5e3-4290-866dee8ed2d5@2ndquadrant.com>
 <ea44c9b9-325c-e43a-7dc8-17a89c01a92a@postgresql.org>
 <aec12df5-688f-620c-8563-c0d824d063f5@postgresql.org>
Message-ID: <e74588824f07e55102482d63b1c47739@xs4all.nl>
User-Agent: XS4ALL Webmail
Precedence: bulk

On 2019-09-02 17:36, Jonathan S. Katz wrote:
> On 9/2/19 11:19 AM, Jonathan S. Katz wrote:
>> Please see attached for the latest draft. I tried to move this closer 
>> to


'common-table expression'  should be
'common table expression'
If you really do prefer the hyphen there then it should also be in the 
other usage of 'Common table expressions' in this text, I think.


'most-common value'  should be
'most common value'


'that build on the implementation of the SQL standard' Perhaps better:
'that build on the SQL standard'


'JSON path expressions'  Perhaps better:
'JSON path expressions'


And perhaps 'aka' should be fully written out 'also known as'.  For us 
non-native speakers it takes a while before all these abbreviations 
become clear. I know it's taken me a few years before I decoded it :)


thanks,


Erik Rijkers