Added feedback

Reviewed-by: David Rowley <dgrowleyml@gmail.com>
Reviewed-by: Erik Rijkers <er@xs4all.nl>
Reviewed-by: Robert Treat <rob@xzilla.net>
Reviewed-by: Noah Misch <noah@leadboat.com>
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>

diff --git a/update_releases/current/20230810securityrelease.md b/update_releases/current/20230810securityrelease.md
index 64f9df0c80e4e4aed30e3da6de6ce0a3f84de324..d21d7a21b5b28a23411573d23a327276dd105649 100644 (file)
--- a/update_releases/current/20230810securityrelease.md
+++ b/update_releases/current/20230810securityrelease.md
@@ -5,7 +5,7 @@ vulnerabilities and over 40 bugs reported over the last several months.
 
 If you use [BRIN]((https://www.postgresql.org/docs/current/brin-intro.html))
 indexes to  look up `NULL` values, you will need to [reindex](https://www.postgresql.org/docs/current/sql-reindex.html)
-them after upgrading to this release. You us
+them after upgrading to this release. On PostgreSQL 12 and above, you can use
 [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html)
 to avoid blocking writes to the affected index and table, for example:
 
@@ -136,11 +136,6 @@ For the full list of changes available, please review the
 Fixes in PostgreSQL 16 Beta 3
 -----------------------------
 
-The following includes fixes included in PostgreSQL 16 Beta 3:
-
-* Fix a performance regression when running concurrent
-[`COPY`](https://www.postgresql.org/docs/16/sql-copy.html) statements on a
-single table.
 * Add the `\drg` command to `psql` to display information about role grants.
 * Add timeline ID to filenames generated with `pg_waldump --save-fullpage`.
 * Fix crash after a deadlock occurs in a parallel `VACUUM` worker.
@@ -160,7 +155,7 @@ update its binaries.
 
 If you use [BRIN]((https://www.postgresql.org/docs/current/brin-intro.html))
 indexes to  look up `NULL` values, you will need to [reindex](https://www.postgresql.org/docs/current/sql-reindex.html)
-them after upgrading to this release. You us
+them after upgrading to this release. On PostgreSQL 12 and above, you can use
 [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html)
 to avoid blocking writes to the affected index and table, for example:
 
@@ -168,8 +163,8 @@ to avoid blocking writes to the affected index and table, for example:
 REINDEX INDEX CONCURRENTLY your_index_name;
 ```
 
-Users who have skipped one or more update releases may need to run additional,
-post-update steps; please see the release notes for earlier versions for
+Users who have skipped one or more update releases may need to run additional
+post-update steps; please see the release notes from earlier versions for
 details.
 
 For more details, please see the
@@ -179,7 +174,7 @@ Updating to PostgreSQL 16 Beta 3
 --------------------------------
 
 To upgrade to PostgreSQL 16 Beta 3 from a previous PostgreSQL 16 Beta version,
-or an previous major version of PostgreSQL, you will need to use a strategy
+or a previous major version of PostgreSQL, you will need to use a strategy
 similar to upgrading between major versions of PostgreSQL (e.g. `pg_upgrade` or
 `pg_dump` / `pg_restore`). For more information, please visit the documentation
 section on [upgrading](https://www.postgresql.org/docs/16/static/upgrading.html).