shorter

Author: dwight

source/release-notes/2.2.txt

@@ -98,8 +98,8 @@ Use the following procedure to upgrade a sharded cluster:
 
 - Upgrade all :program:`mongos` instances *first*, in any order.
 
-- Upgrade all of the :program:`mongod` config server instances *one at
-  a time* using the :ref:`stand alone <2.2-upgrade-standalone>` procedure.
+- Upgrade all of the :program:`mongod` config server instances 
+  using the :ref:`stand alone <2.2-upgrade-standalone>` procedure.
   To keep the cluster online, be that at all times at least one config 
   server is up.
 
@@ -225,24 +225,15 @@ MongoDB 2.2 provides more reliable and robust support for
 authentication clients, including drivers and :program:`mongos`
 instances.
 
-If your :program:`mongod` instances or cluster runs with
-authentication:
-
-- In sharded environments, 2.0 version :program:`mongos` instances are
-  **not** compatible with 2.2 shard clusters running with
-  authentication.
-
-  To ensure that your cluster remains available during the upgrade
-  process you **must** use the :ref:`upgrade procedure for shard clusters
-  <2.2-upgrade-shard-cluster>` and upgrade all :program:`mongos`
-  instances *before* upgrading the shard.
+If your cluster runs with authentication:
 
 - For all drivers, use the latest release of your driver and check
   its release notes.
 
-Drivers and :program:`mongos` instances that connect to
-:program:`mongod` instances that do *not* have authentication enabled
-are not affected by this issue.
+- In sharded environments, 
+  to ensure that your cluster remains available during the upgrade
+  process you **must** use the :ref:`upgrade procedure for shard clusters
+  <2.2-upgrade-shard-cluster>`.
 
 .. _2.2-findandmodify-returns-null: