diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
new file mode 100644
index bf58a0a..18e6af3
*** a/doc/src/sgml/ref/pgupgrade.sgml
--- b/doc/src/sgml/ref/pgupgrade.sgml
*************** NET STOP postgresql-9.0
*** 317,331 ****
! Verify standby servers
! If you are upgrading Streaming Replication and Log-Shipping standby
! servers, verify that the old standby servers are caught up by running
! pg_controldata> against the old primary and standby
! clusters. Verify that the Latest checkpoint location>
! values match in all clusters. (There will be a mismatch if old
! standby servers were shut down before the old primary.)
--- 317,338 ----
! Prepare for standby server upgrades
! If you are upgrading standby servers (as outlined in section ), verify that the old standby
! servers are caught up by running pg_controldata>
! against the old primary and standby clusters. Verify that the
! Latest checkpoint location> values match in all clusters.
! (There will be a mismatch if old standby servers were shut down
! before the old primary.)
!
!
!
! Also, if upgrading standby servers, change wal_level>
! to replica> in the postgresql.conf> file on
! the new cluster.
*************** pg_upgrade.exe
*** 410,416 ****
!
Upgrade Streaming Replication and Log-Shipping standby servers
--- 417,423 ----
!
Upgrade Streaming Replication and Log-Shipping standby servers
*************** pg_upgrade.exe
*** 471,486 ****
-
- Start and stop the new master cluster
-
-
- In the new master cluster, change wal_level> to
- replica> in the postgresql.conf> file
- and then start and stop the cluster.
-
-
-
Run rsync>
--- 478,483 ----