adding clarifications to release notes

Author: Sam Kleinman

source/release-notes/2.4.txt

@@ -9,8 +9,8 @@ development release series. While 2.3-series releases are currently
 available, these versions of MongoDB are for **testing** *only*, and
 are *not for production use* under any circumstances.
 
-*All* interfaces *and* functionality described in this document are
-subject to change before the 2.4.0 release.
+.. important:: *All* interfaces *and* functionality described in this
+   document are subject to change before the 2.4.0 release.
 
 This document will eventually contain the full release notes for
 MongoDB 2.4; during the development cycle this document will contain
@@ -113,7 +113,8 @@ resemble:
 
 .. code-block:: sh
 
-   env KRB5_KTNAME=/opt/etc/mongodb.keytab /opt/bin/mongod --auth --dbpath /opt/data/db --logpath /opt/log/mongod.log --fork
+   env KRB5_KTNAME=/opt/etc/mongodb.keytab \
+       /opt/bin/mongod --auth --dbpath /opt/data/db --logpath /opt/log/mongod.log --fork
 
 Replace the paths as needed for your test deployment.
 
@@ -124,7 +125,8 @@ associate the current connection with the Kerberos session:
 
 .. code-block:: javascript
 
-   db.getMongo().saslAuthenticate( {mechanism: "GSSAPI", principal: "<username>@<REALM>"} )
+   db.getMongo().saslAuthenticate( { mechanism: "GSSAPI", 
+                                     principal: "<username>@<REALM>" } )
 
 The value of the ``principal`` field *must* be the same principal that
 you initialized with ``kinit``. Continue to gain privileges using the
@@ -133,7 +135,10 @@ following:
 
 .. code-block:: javascript
 
-   db.adminCommand( { acquirePrivilege: 1, resource: <dbname>, principal: <principalName>, actions: [ <actionString> ] } )
+   db.adminCommand( { acquirePrivilege: 1, 
+                      resource: <dbname>, 
+                      principal: <principalName>, 
+                      actions: [ <actionString> ] } )
 
 Replace the ``<dbname>`` with the name of the database you want
 privileges, replace ``<principalName>`` with the Kerberos principal
@@ -193,6 +198,11 @@ and :dbcommand:`eval` is now v8.
 New Geospatial Indexes with GeoJSON and Improved Spherical Geometry
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+.. note:: 
+
+   In 2.3.2, the index type for Spherical Geospatial Indexes will
+   become ``2dsphere``
+
 The 2.3 series adds a new type of geospatial index that supports
 improved spherical queries and GeoJSON. Create the index by specifying
 ``s2d`` as the value of the field in the index specification, as
@@ -233,7 +243,10 @@ the following GeoJSON shapes:
 
    .. code-block:: javascript
 
-      { "type": "Polygon", "coordinates": [ [ 40, 5 ], [ 40, 6 ], [ 41, 6 ], [ 41, 5 ], [ 40, 5 ] ] }
+      {
+        "type": "Polygon", 
+        "coordinates": [ [ 40, 5 ], [ 40, 6 ], [ 41, 6 ], [ 41, 5 ], [ 40, 5 ] ] 
+      }
 
 To query ``s2d`` indexes, all current geospatial :ref:`query operators
 <query-selectors-geospatial>` with an additional
@@ -374,7 +387,9 @@ key. Consider the following properties when using a hashed shard key:
 
   .. code-block:: javascript
 
-     db.adminCommand( { shardCollection: "test.collection", key: { a: "hashed"}, numInitialChunks: 2001 } )
+     db.adminCommand( { shardCollection: "test.collection", 
+                        key: { a: "hashed"}, 
+                        numInitialChunks: 2001 } )
 
   MongoDB will only pre-split chunks in a collection when sharding
   empty collections. MongoDB will not create chunk splits in a