diff --git a/source/release-notes/2.4-upgrade.txt b/source/release-notes/2.4-upgrade.txt
index 3c38217a236..bdb1b11cd57 100644
--- a/source/release-notes/2.4-upgrade.txt
+++ b/source/release-notes/2.4-upgrade.txt
@@ -61,8 +61,9 @@ metadata in any other way.
    The upgraded config database will require more storage space than
    before, though this storage increase represents a fraction of the
    current config database size. The additional storage requirement
-   will be less for deployments that have run with 2.2 for a
-   non-trivial period of time. See
+   will be much less for deployments that have run with 2.2 for a
+   non-trivial period of time, but, as always, pre-allocation of 
+   data files could be triggered. See
    :ref:`faq-tools-for-measuring-storage-use` for more information.
 
 .. _2.4-upgrade-meta-data:
@@ -93,7 +94,9 @@ procedure.
 #. Start a single 2.4 :program:`mongos` process with
    :setting:`configdb` pointing to the sharded cluster's :ref:`config
    servers <sharding-config-server>` and with the :option:`--upgrade
-   <mongos --upgrade>` option. You can upgrade an existing
+   <mongos --upgrade>` option.  The upgrade process happens pre :option:`--fork`.
+   
+   You can upgrade an existing
    :program:`mongos` instance to 2.4 or you can start a new `mongos`
    instance that can reach all config servers if you need to avoid
    reconfiguring a production :program:`mongos`.
@@ -176,7 +179,7 @@ incompatibilities in future versions of MongoDB.
 
 .. _upgrade-cluster-resync:
 
-Resync after a Network Interruption
+Resync after a Critical Section Interruption
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 During the short critical section of the upgrade that applies changes