Fix wording in pg_upgrade docs

Author: Daniel Gustafsson

diff --git a/src/bin/pg_upgrade/IMPLEMENTATION b/src/bin/pg_upgrade/IMPLEMENTATION
index 9b5ff7295c109bb6238000ee96c0b0bbc32f5df4..69fcd70a7c526d9f27b43a49f71e9b591a6b889f 100644 (file)
--- a/src/bin/pg_upgrade/IMPLEMENTATION
+++ b/src/bin/pg_upgrade/IMPLEMENTATION
@@ -71,8 +71,8 @@ performs a number of bookkeeping tasks required to 'sync up' the new
 cluster with the existing data.
 
 First, pg_upgrade copies the commit status information and 'next
-transaction ID' from the old cluster to the new cluster. This is the
-steps ensures that the proper tuples are visible from the new cluster.
+transaction ID' from the old cluster to the new cluster. This step
+ensures that the proper tuples are visible from the new cluster.
 Remember, pg_upgrade does not export/import the content of user-defined
 tables so the transaction IDs in the new cluster must match the
 transaction IDs in the old data. pg_upgrade also copies the starting