Added the word 'below' to refer to the Updating section and removed a few extra white...

diff --git a/update_releases/current/20161027updaterelease.md b/update_releases/current/20161027updaterelease.md
index 0d94fb3f80eab4a9f44d52ccc8992edf1b81ba29..2a4d3c483078b412516b11f0c96311338f78ac34 100644 (file)
--- a/update_releases/current/20161027updaterelease.md
+++ b/update_releases/current/20161027updaterelease.md
@@ -19,7 +19,7 @@ pg_upgrade issues on big-endian machines
 
 On big-endian machines (e.g. many non-Intel CPU architectures), pg_upgrade would incorrectly write the bytes of the visibility map leading to pg_upgrade failing to complete.
 
-If you are using a big-endian machine (many non-Intel architectures are big-endian) and have used pg_upgrade to upgrade from a pre-9.6 release, you should assume that all visibility maps are incorrect and need to be regenerated. It is sufficient to truncate each relation's visibility map with contrib/pg_visibility's pg_truncate_visibility_map() function.  Please read the "Updating" section for post-installation instructions on how to resolve this issue on your PostgreSQL instances.
+If you are using a big-endian machine (many non-Intel architectures are big-endian) and have used pg_upgrade to upgrade from a pre-9.6 release, you should assume that all visibility maps are incorrect and need to be regenerated. It is sufficient to truncate each relation's visibility map with contrib/pg_visibility's pg_truncate_visibility_map() function.  Please read the "Updating" section below for post-installation instructions on how to resolve this issue on your PostgreSQL instances.
 
 This issue is present only in the PostgreSQL 9.6.0 release.
 
@@ -61,7 +61,7 @@ In this update, AMT is no longer shown as being in use to mean Armenia Time. The
 EOL Notice for Version 9.1
 --------------------------
 
-PostgreSQL version 9.1 is now End-of-Life (EOL).  No additional updates or security patches will be released by the community for this version.  Users still on 9.1 are urged to upgrade as soon as possible.  See our [Versioning Policy](https://www.postgresql.org/support/versioning/) for more information.
+PostgreSQL version 9.1 is now End-of-Life (EOL). No additional updates or security patches will be released by the community for this version. Users still on 9.1 are urged to upgrade as soon as possible. See our [Versioning Policy](https://www.postgresql.org/support/versioning/) for more information.
 
 Updating
 --------

diff --git a/update_releases/current/20161027updaterelease.txt b/update_releases/current/20161027updaterelease.txt
index 1c35893607300e29ef74b823ae8dd3f747005f66..a0836c6058f1706b6d318ccfa75cc477b5a577f2 100644 (file)
--- a/update_releases/current/20161027updaterelease.txt
+++ b/update_releases/current/20161027updaterelease.txt
@@ -19,7 +19,7 @@ pg_upgrade issues on big-endian machines
 
 On big-endian machines (e.g. many non-Intel CPU architectures), pg_upgrade would incorrectly write the bytes of the visibility map leading to pg_upgrade failing to complete.
 
-If you are using a big-endian machine (many non-Intel architectures are big-endian) and have used pg_upgrade to upgrade from a pre-9.6 release, you should assume that all visibility maps are incorrect and need to be regenerated. It is sufficient to truncate each relation's visibility map with contrib/pg_visibility's pg_truncate_visibility_map() function.  Please read the "Updating" section for post-installation instructions on how to resolve this issue on your PostgreSQL instances.
+If you are using a big-endian machine (many non-Intel architectures are big-endian) and have used pg_upgrade to upgrade from a pre-9.6 release, you should assume that all visibility maps are incorrect and need to be regenerated. It is sufficient to truncate each relation's visibility map with contrib/pg_visibility's pg_truncate_visibility_map() function. Please read the "Updating" section below for post-installation instructions on how to resolve this issue on your PostgreSQL instances.
 
 This issue is present only in the PostgreSQL 9.6.0 release.
 
@@ -61,7 +61,7 @@ In this update, AMT is no longer shown as being in use to mean Armenia Time. The
 EOL Notice for Version 9.1
 --------------------------
 
-PostgreSQL version 9.1 is now End-of-Life (EOL).  No additional updates or security patches will be released by the community for this version.  Users still on 9.1 are urged to upgrade as soon as possible.  See our Versioning Policy (https://www.postgresql.org/support/versioning/) for more information.
+PostgreSQL version 9.1 is now End-of-Life (EOL). No additional updates or security patches will be released by the community for this version. Users still on 9.1 are urged to upgrade as soon as possible. See our Versioning Policy (https://www.postgresql.org/support/versioning/) for more information.
 
 Updating
 --------