Merge pull request #4740 from EnterpriseDB/docs/edits_to_pgdupgrade_p…

…r4655

copy edits to new upgrade info

product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx

@@ -24,18 +24,18 @@ release, before upgrading to the latest version 5 release. After upgrading to
 
 ## Upgrading from version 3.7 to version 5
 
-At this time, TPA has only enabled upgrades from PGD 3.7 to 4 and PGD 4 to 5.
-Customers moving from 3.7 to 5 and desiring automation would need to use this
-two-step upgrade path and will potentially have their proxy architecture changed
-multiple times from HA Proxy to HARP and finally to PGD Proxy.
+At this time, TPA has enabled upgrades only from PGD 3.7 to 4 and PGD 4 to 5.
+If you're moving from 3.7 to 5 and want automation, you need to use this
+two-step upgrade path. Using this process, it's possible your proxy architecture will change
+multiple times: from HA Proxy to HARP and then to PGD Proxy.
 
-Significant development has been done to make upgrading directly from 3.7 to 5
+Significant development was done to make upgrading directly from 3.7 to 5
 possible and easier. We've expanded the database versions supported with PGD 5
 and enabled the upgradeability of the BDR extension across multiple PGD
-versions. Previously, we only supported upgrades from the previous major
+versions. Previously, we supported upgrades only from the previous major
 version. Often, a database upgrade was also required because only one database
 major version was supported by both PGD versions.  
 
 Development is currently ongoing to provide a direct upgrade path from 3.7 to 5
-using TPA by Q4. In the interim, customers may reach out to EDB Professional
+using TPA by Q4. In the interim, you can reach out to EDB Professional
 Services or Support for assistance and guidance.