edits: DOCS-671 minor changes for style of min/max docs

Author: Sam Kleinman

source/faq/indexes.txt

@@ -109,6 +109,15 @@ wait for the index to finish building.
    Kill the current operation (see :method:`db.killOp()`). The partial
    index will be deleted.
 
+.. _faq-index-min-max:
+
+Can I use index keys to constrain query matches?
+------------------------------------------------
+
+You can use the :method:`min() <cursor.min()>` and :method:`max()
+<cursor.max()>` methods to constrain the results of the cursor returned
+from :method:`find() <db.collection.find()>` by using index keys.
+
 Using ``$ne`` and ``$nin`` in a query is slow. Why?
 ---------------------------------------------------
 
@@ -117,11 +126,3 @@ See :ref:`index-selectivity`. If you need to use these,
 it is often best to make sure that an additional, more selective
 criterion is part of the query.
 
-.. _faq-index-min-max:
-
-Can I use index keys to constrain query matches?
-------------------------------------------------
-
-You can use the :method:`min() <cursor.min()>` and the :method:`max()
-<cursor.max()>` methods to constrain the results of the cursor returned
-from :method:`find() <db.collection.find()>` by using the index keys.

source/reference/method/cursor.max.txt

@@ -21,7 +21,7 @@ cursor.max()
 
           .. code-block:: javascript
 
-             { field1: <max value>, field2: <max value2> ... fieldN:<max valueN>} 
+             { field1: <max value>, field2: <max value2> ... fieldN:<max valueN>}
 
           The fields correspond to *all* the keys of a particular index
           *in order*. You can explicitly specify the particular index
@@ -31,9 +31,9 @@ cursor.max()
           fields with different sort orders, the selection of the index
           may be ambiguous.
 
-   Consider the following examples of :method:`max() <cursor.max()>`:
-
-   The examples assume a collection ``products`` with the following documents:
+   Consider the following example of :method:`max() <cursor.max()>`,
+   which assumes a collection named ``products`` that holds the
+   following documents:
 
    .. code-block:: javascript
 
@@ -47,8 +47,8 @@ cursor.max()
       { "_id" : 10, "item" : "orange", "type" : "navel", "price" : 1.39 }
       { "_id" : 9, "item" : "orange", "type" : "satsuma", "price" : 1.99 }
       { "_id" : 8, "item" : "orange", "type" : "valencia", "price" : 0.99 }
-      
-   The collection has the following four indexes:
+
+   The collection has the following indexes:
 
    .. code-block:: javascript
 
@@ -102,14 +102,14 @@ cursor.max()
 
    .. note::
 
-      - Because :method:`max() <cursor.max()>` requires a corresponding
-        index as well as enforces the use of that index, it may be
-        preferable to use the :operator:`$lt` operator in the query if
+      - Because :method:`max() <cursor.max()>` requires an index on a
+        field, and forces the query to use this index, you may prefer
+        the :operator:`$lt` operator for the query if
         possible. Consider the following example:
 
         .. code-block:: javascript
 
-           db.products.find( { _id: 7 } ).max( { price: 1.39 } )   
+           db.products.find( { _id: 7 } ).max( { price: 1.39 } )
 
         The query will use the index on the ``price`` field, even if
         the index on ``_id`` may be better.
@@ -124,4 +124,3 @@ cursor.max()
 
       - :method:`max() <cursor.max()>` is a shell wrapper around the
         special operator :operator:`$max`.
-

source/reference/method/cursor.min.txt

@@ -21,19 +21,19 @@ cursor.min()
 
           .. code-block:: javascript
 
-             { field1: <min value>, field2: <min value2> ... fieldN:<min valueN>} 
+             { field1: <min value>, field2: <min value2> ... fieldN:<min valueN>}
 
           The fields correspond to *all* the keys of a particular index
           *in order*. You can explicitly specify the particular index
           with the :method:`hint() <cursor.hint()>` method. Otherwise,
-          :program:`mongod` selects the index using the fields in the
+          MongoDB selects the index using the fields in the
           ``indexbounds``; however, if multiple indexes exist on same
           fields with different sort orders, the selection of the index
           may be ambiguous.
 
-   Consider the following examples of :method:`min() <cursor.min()>`:
-
-   The examples assume a collection ``products`` with the following documents:
+   Consider the following example of :method:`min() <cursor.min()>`,
+   which assumes a collection named ``products`` that holds the
+   following documents:
 
    .. code-block:: javascript
 
@@ -47,8 +47,8 @@ cursor.min()
       { "_id" : 10, "item" : "orange", "type" : "navel", "price" : 1.39 }
       { "_id" : 9, "item" : "orange", "type" : "satsuma", "price" : 1.99 }
       { "_id" : 8, "item" : "orange", "type" : "valencia", "price" : 0.99 }
-      
-   The collection has the following four indexes:
+
+   The collection has the following indexes:
 
    .. code-block:: javascript
 
@@ -60,13 +60,12 @@ cursor.min()
    - Using the ordering of ``{ item: 1, type: 1 }`` index,
      :method:`min() <cursor.min()>` limits the query to the documents
      that are at or above the index key bound of ``item`` equal to
-     ``apple`` and ``type`` equal to ``jonagold``:
-     
+     ``apple`` and ``type`` equal to ``jonagold``, as in the following:
+
      .. code-block:: javascript
 
         db.products.find().min( { item: 'apple', type: 'jonagold' } ).hint( { item: 1, type: 1 } )
 
-      
      The query returns the following documents:
 
      .. code-block:: javascript
@@ -106,15 +105,15 @@ cursor.min()
 
    .. note::
 
-      - Because :method:`min() <cursor.min()>` requires a corresponding
-        index as well as enforces the use of that index, it may be
-        preferable to use the :operator:`$gte` operator in the query if
+      - Because :method:`min() <cursor.min()>` requires an index on a
+        field, and forces the query to use this index, you may prefer
+        the :operator:`$gte` operator for the query if
         possible. Consider the following example:
-        
+
         .. code-block:: javascript
-        
-           db.products.find( { _id: 7 } ).min( { price: 1.39 } )   
-        
+
+           db.products.find( { _id: 7 } ).min( { price: 1.39 } )
+
         The query will use the index on the ``price`` field, even if
         the index on ``_id`` may be better.