Improve some wording in pg_upgrade/IMPLEMENTATION

Author: Gurjeet Singh
Discussion: https://postgr.es/m/CABwTF4VFKtKrb78fBnMXwHvOu4a+-7y86siBSEety2knti2eGA@mail.gmail.com

diff --git a/src/bin/pg_upgrade/IMPLEMENTATION b/src/bin/pg_upgrade/IMPLEMENTATION
index 229399a45ae0587c345e618dd5e2e9507d20656c..f47deee90c14e9f41f9e97a03a004b25e9abf525 100644 (file)
--- a/src/bin/pg_upgrade/IMPLEMENTATION
+++ b/src/bin/pg_upgrade/IMPLEMENTATION
@@ -48,9 +48,9 @@ HOW IT WORKS
 To use pg_upgrade during an upgrade, start by installing a fresh
 cluster using the newest version in a new directory. When you've
 finished installation, the new cluster will contain the new executables
-and the usual template0, template1, and postgres, but no user-defined
-tables. At this point, you can shut down the old and new postmasters and
-invoke pg_upgrade.
+and the usual template0, template1, and postgres databases, but no
+user-defined tables. At this point, you can shut down the old and new
+postmasters and invoke pg_upgrade.
 
 When pg_upgrade starts, it ensures that all required executables are
 present and contain the expected version numbers. The verification