Re: PostgreSQL 14 press release draft

Some super quick nitpicks; feel free to ignore/apply/laugh off.

...
administrators to deploy their data-backed applications. PostgreSQL
continues to
add innovations on complex data types, including more conveniences for
accessing
JSON and support for noncontiguous ranges of data. This latest release also
adds
to PostgreSQL's trend on improvements for high performance and distributed
data workloads, with advances in support for connection concurrency,
high-write
workloads, query parallelism and logical replication.

>> add innovations on complex data types -> add innovations to? "on" sounds
odd

>> comma after "query parallelism" please

now works. This aligns PostgreSQL with commonly recognized syntax for
retrieving information from JSON data. The subscripting framework added to
PostgreSQL 14 can be generally extended to other nested data structures,
and is
also applied to the `hstore` data type in this release.

>> with commonly recognized syntax -> with the commonly recognized syntax

>> hyperlink hstore?

[Range types](https://www.postgresql.org/docs/14/rangetypes.html), also
first
released in PostgreSQL 9.2, now have support for noncontiguous ranges
through
the introduction of the "[multirange](
https://www.postgresql.org/docs/14/rangetypes.html#RANGETYPES-BUILTIN)".
A multirange is an ordered list of ranges that are nonoverlapping, which
allows
for developers to write simpler queries for dealing with complex sequences
of

>> introduction of the multirange -> introduction of the multirange type

>> which allows for developers to write -> which lets developers write

on the recent improvements to the overall management of B-tree indexes by

>> to the overall management -> to the management

operations. As this is a client-side feature, you can use pipeline mode
with any
modern PostgreSQL database so long as you use the version 14 client.

>> more complicated than "version 14 client", more like - if the
application has explicit
>> support for it and was compiled via libpq against PG 14.
>> Just don't want to overpromise here

[Foreign data wrappers](
https://www.postgresql.org/docs/14/sql-createforeigndatawrapper.html),
which are used for working with federated workloads across PostgreSQL and
other

>> which are used for -> used for

In addition to supporting query parallelism, `postgres_fdw` can now also
bulk
insert data on foreign tables and import table partitions with the
[`IMPORT FOREIGN SCHEMA`](
https://www.postgresql.org/docs/14/sql-importforeignschema.html)
directive.

>> can now also bulk insert -> can now bulk insert

>> on foreign tables and import -> on foreign tables, and can import

PostgreSQL 14 extends its performance gains to the [vacuuming](
https://www.postgresql.org/docs/14/routine-vacuuming.html)
system, including optimizations for reducing overhead from B-Trees.

>> B-Tree or B-tree - pick one (latter used earlier in this doc)

lets you uniquely track a query through several PostgreSQL systems,
including
[`pg_stat_activity`](
https://www.postgresql.org/docs/14/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW
),
[`EXPLAIN VERBOSE`](https://www.postgresql.org/docs/14/sql-explain.html),
and
through several logging functions.

>> "several PostgreSQL systems" sounds weird.

>> "several logging functions" - not sure what this means

parallel queries when using the `RETURN QUERY` directive, and enabling

>> directive -> command

now benefit from incremental sorts, a feature that was introduced in
[PostgreSQL 13](
https://www.postgresql.org/about/news/postgresql-13-released-2077/).

>> that was introduced in -> introduced in

function. This release also adds the SQL conforming
[`SEARCH`](
https://www.postgresql.org/docs/14/queries-with.html#QUERIES-WITH-SEARCH)
and [`CYCLE`](
https://www.postgresql.org/docs/14/queries-with.html#QUERIES-WITH-CYCLE)
directives to help with ordering and cycle detection for recursive
[common table expressions](
https://www.postgresql.org/docs/14/queries-with.html#QUERIES-WITH-RECURSIVE
).

>> directives -> clauses

PostgreSQL 14 makes it convenient to assign read-only and write-only
privileges

>> convenient -> easy

companies and organizations. Built on over 30 years of engineering,
starting at

>> companies -> companies,

>> we claims 25 years at the top, 30 here. That's 5 non-open-source years?
:)