squash. code review

Author: korydraughn

docs/getting_started/upgrading.md

@@ -6,11 +6,11 @@ All servers in a Zone must be running the same version of iRODS.  Using inconsis
 
 It is best practice to stop an iRODS server before upgrading as it will allow the graceful completion of any ongoing transfers or requests.
 
-Upgrades coming from the APT and YUM repositories will cause the server to shut down. This is intentional as the administrator is required to apply catalog schema updates before restarting the server. A catalog schema update could be a relatively heavy operation and will require an amount of time on large installations (hundreds of millions of records) that should be handled within a declared maintenance window.
+Upgrades of packages from APT and YUM repositories will stop the server as part of the package upgrade process. This is intentional as the administrator is required to apply any catalog schema updates before restarting the server. A catalog schema update could be a relatively heavy operation and will require an amount of time on large installations (hundreds of millions of records) that should be handled within a declared maintenance window.
 
 ## Upgrading to iRODS 5 and later
 
-iRODS 5 does not upgrade the catalog or `server_config.json` on server startup. This functionality was deliberately separated to make the upgrade process more deterministic and manageable.
+iRODS 5 does not upgrade the catalog or `server_config.json` on server startup. This functionality has been kept separate deliberately to make the upgrade process more deterministic and manageable.
 
 Upgrading only requires two steps:
 
@@ -20,7 +20,7 @@ Upgrading only requires two steps:
 The `upgrade_irods.py` script is idempotent.
 
 !!! Warning
-    The iRODS server will not start if it detects a difference in the catalog schema version.
+    The iRODS server will not start if it detects an unexpected catalog schema version.
 
 ## Migrating from Static PEPs to Dynamic PEPs