minor: fixing rst error

Author: Sam Kleinman

source/release-notes/2.4.txt

@@ -72,7 +72,7 @@ system are available for use in MongoDB:
    instances and :term:`replica sets <replica set>`.
 
 Initial SASL/Kerberos  Support
-`````````````````````````````
+``````````````````````````````
 
 Development work on this functionality is ongoing, and additional
 related functionality is forthcoming. To use Kerberos with MongoDB as
@@ -125,7 +125,7 @@ associate the current connection with the Kerberos session:
 
 .. code-block:: javascript
 
-   db.getMongo().saslAuthenticate( { mechanism: "GSSAPI", 
+   db.getMongo().saslAuthenticate( { mechanism: "GSSAPI",
                                      principal: "<username>@<REALM>" } )
 
 The value of the ``principal`` field *must* be the same principal that
@@ -135,9 +135,9 @@ following:
 
 .. code-block:: javascript
 
-   db.adminCommand( { acquirePrivilege: 1, 
-                      resource: <dbname>, 
-                      principal: <principalName>, 
+   db.adminCommand( { acquirePrivilege: 1,
+                      resource: <dbname>,
+                      principal: <principalName>,
                       actions: [ <actionString> ] } )
 
 Replace the ``<dbname>`` with the name of the database you want
@@ -198,7 +198,7 @@ and :dbcommand:`eval` is now v8.
 New Geospatial Indexes with GeoJSON and Improved Spherical Geometry
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. note:: 
+.. note::
 
    In 2.3.2, the index type for Spherical Geospatial Indexes will
    become ``2dsphere``
@@ -244,8 +244,8 @@ 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
@@ -375,7 +375,7 @@ key. Consider the following properties when using a hashed shard key:
   the appropriate index.
 
 - The :program:`mongos` will route all equality queries to a specific
-  shard or set of shards; however, the :program:`mongos` must route 
+  shard or set of shards; however, the :program:`mongos` must route
   range queries to all shards.
 
 - When using a hashed shard key on a new collection, MongoDB
@@ -387,10 +387,10 @@ key. Consider the following properties when using a hashed shard key:
 
   .. code-block:: javascript
 
-     db.adminCommand( { shardCollection: "test.collection", 
-                        key: { a: "hashed"}, 
+     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
   collection sharding collections that have data.