fix indents

source/reference/command/geoNear.txt

@@ -29,20 +29,20 @@ Definition
 Command Format
 --------------
 
-   To query a :doc:`2dsphere </core/2dsphere>` index, use the
-   following syntax:
+To query a :doc:`2dsphere </core/2dsphere>` index, use the
+following syntax:
 
-   .. code-block:: javascript
+.. code-block:: javascript
 
-      db.runCommand( { geoNear : <collection> ,
-                       near : { type : "Point" ,
-                                coordinates: [ <coordinates> ] } ,
-                       spherical : true } )
+   db.runCommand( { geoNear : <collection> ,
+                    near : { type : "Point" ,
+                             coordinates: [ <coordinates> ] } ,
+                    spherical : true } )
 
-   To query a :doc:`2d </core/2d>` index, use:
+To query a :doc:`2d </core/2d>` index, use:
 
-   .. code-block:: javascript
+.. code-block:: javascript
 
-      { geoNear : <collection> , near : [ <coordinates> ] }
+   { geoNear : <collection> , near : [ <coordinates> ] }
 
-   .. read-lock, slave-ok
+.. read-lock, slave-ok

source/reference/operator/aggregation/geoNear.txt

@@ -4,6 +4,9 @@ $geoNear (aggregation)
 
 .. default-domain:: mongodb
 
+Definition
+----------
+
 .. pipeline:: $geoNear
 
    .. versionadded:: 2.4
@@ -30,19 +33,18 @@ $geoNear (aggregation)
 
    .. include:: /reference/operator/aggregation/geoNear-field.rst
 
- .. note::
+   .. note::
 
-    The options for :pipeline:`$geoNear` are similar to the
-    :dbcommand:`geoNear` command with the following
-    exceptions:
+      The options for :pipeline:`$geoNear` are similar to the
+      :dbcommand:`geoNear` command with the following exceptions:
 
-    - ``distanceField`` is a mandatory field for the
-      :pipeline:`$geoNear` pipeline operator; the option does not
-      exist in the :dbcommand:`geoNear` command.
+      - ``distanceField`` is a mandatory field for the
+        :pipeline:`$geoNear` pipeline operator; the option does not exist
+        in the :dbcommand:`geoNear` command.
 
-    - ``includeLocs`` accepts a ``string`` in the
-      :pipeline:`$geoNear` pipeline operator and a ``boolean`` in the
-      :dbcommand:`geoNear` command.
+      - ``includeLocs`` accepts a ``string`` in the :pipeline:`$geoNear`
+        pipeline operator and a ``boolean`` in the :dbcommand:`geoNear`
+        command.
 
 Example
 -------

source/reference/operator/aggregation/group.txt

@@ -25,9 +25,9 @@ $group (aggregation)
    The following example of an ``_id`` field specifies a document that
    consists of multiple fields:
 
-     .. code-block:: javascript
+   .. code-block:: javascript
 
-        { _id : { author: '$author', pageViews: '$pageViews', posted: '$posted' } }
+      { _id : { author: '$author', pageViews: '$pageViews', posted: '$posted' } }
 
    Every :pipeline:`$group` expression **must** specify an ``_id``
    field. In addition to the ``_id`` field, :pipeline:`$group`