edits: DOCS-675

Author: Sam Kleinman

source/applications/read.txt

@@ -135,7 +135,7 @@ Consider the following examples that illustrate the use of the
             contribs: 'UNIX'
           }
        )
-       
+
   - The following operation returns all documents in the ``bios``
     collection where ``awards`` array contains a subdocument element
     that contains the ``award`` field equal to ``'Turing Award'`` and the
@@ -374,7 +374,7 @@ variable:
 
   .. code-block:: javascript
 
-     if (myDocument) { 
+     if (myDocument) {
 
          var myName = myDocument.name;
 
@@ -465,28 +465,21 @@ You can chain these cursor methods, as in the following examples [#dbquery-serve
      db.bios.find().sort( { name: 1 } ).limit( 5 )
      db.bios.find().limit( 5 ).sort( { name: 1 } )
 
-See :ref:`JavaScript cursor methods <js-query-cursor-methods>` and your
-:doc:`driver </applications/drivers>` documentation for more
-information on cursor methods. See :ref:`read-operations-cursors` for
+See the :ref:`JavaScript cursor methods <js-query-cursor-methods>`
+reference and your :doc:`driver </applications/drivers>` documentation
+for additional references. See :ref:`read-operations-cursors` for
 more information regarding cursors.
 
-.. [#dbquery-server] Regardless of the order you chain the :method:`limit()
-   <cursor.limit()>` and the :method:`sort() <cursor.sort()>`, the
-   request to the server has the following structure that treats the
-   query and the :method:`sort() <cursor.sort()>` modifier as a single
-   object:
-
-   .. code-block:: javascript
-
-      db.bios.find( { $query: {}, $orderby: { name: 1 } } ).limit( 5 )
-
-   This structure means that the :method:`limit() <cursor.limit()>`
-   method is always applied after the :method:`sort() <cursor.sort()>`
-   regardless of the order in which the client chains the two methods.
-
-   For other cursor modifiers that are sent with the
-   query as a single object to the server, see the :doc:`meta query operators
-   </reference/meta-query-operators>`.
+.. [#dbquery-server] Regardless of the order you chain the
+   :method:`limit() <cursor.limit()>` and the :method:`sort()
+   <cursor.sort()>`, the request to the server has the following
+   structure that treats the query and the :method:`sort()
+   <cursor.sort()>` modifier as a single object. Therefore, the
+   :method:`limit() <cursor.limit()>` operation method is always
+   applied after the :method:`sort() <cursor.sort()>` regardless of
+   the specified order of the operations in the chain. See the
+   :doc:`meta query operators </reference/meta-query-operators>` for
+   more information.
 
 .. _crud-read-findOne:
 .. _crud-read-find-one:

source/core/read-operations.txt

@@ -97,7 +97,6 @@ operators, refer to the :doc:`/applications/read` page of the
    wrapper for the more formal query structure with the
    :operator:`$query` operator.
 
-
 .. _read-operations-query-document:
 .. _read-operations-query-argument:
 
@@ -669,7 +668,7 @@ Cursors
 The :method:`find() <db.collection.find()>` method returns a
 :term:`cursor` to the results; however, in the :program:`mongo` shell,
 if the returned cursor is not assigned to a variable, then the cursor
-is automatically iterated up to 20 times [#setShellBatchSize]_ to print
+is automatically iterated up to 20 times [#set-shell-batch-size]_ to print
 up to the first 20 documents that match the query, as in the following
 example:
 
@@ -680,8 +679,8 @@ example:
 When you assign the :method:`find() <db.collection.find()>` to a
 variable:
 
-- you can type the name of the cursor variable to iterate up to 20
-  times [#setShellBatchSize]_ and print the matching documents, as in
+- you can call the cursor variable in the shell to iterate up to 20
+  times [#set-shell-batch-size]_ and print the matching documents, as in
   the following example:
 
   .. code-block:: javascript
@@ -696,25 +695,20 @@ variable:
   .. code-block:: javascript
 
      var myCursor = db.inventory.find( { type: 'food' } );
-
      var myDocument = myCursor.hasNext() ? myCursor.next() : null;
 
      if (myDocument) {
-
          var myItem = myDocument.item;
-
          print(tojson(myItem));
      }
 
-  To print, you can also use the ``printjson()`` method instead of
-  ``print(tojson())``:
+  As an alternative print operation, cosider the the ``printjson()``
+  helper method to replace ``print(tojson())``:
 
   .. code-block:: javascript
 
-     if (myDocument) { 
-
+     if (myDocument) {
          var myItem = myDocument.item;
-
          printjson(myItem);
      }
 
@@ -732,13 +726,8 @@ See :ref:`JavaScript cursor methods <js-query-cursor-methods>` and your
 :doc:`driver </applications/drivers>` documentation for more
 information on cursor methods.
 
-.. [#setShellBatchSize] You can use the ``DBQuery.shellBatchSize`` to
-   change the number of iteration from the default value ``20``, as in the
-   following example which sets the number to ``10``:
-
-   .. code-block:: javascript
-
-      DBQuery.shellBatchSize = 10
+.. [#set-shell-batch-size] You can use the ``DBQuery.shellBatchSize`` to
+   change the number of iteration from the default value ``20``.
 
 Iterator Index
 ~~~~~~~~~~~~~~
@@ -788,11 +777,11 @@ Consider the following behaviors related to cursors:
   should either close the cursor manually or exhaust the cursor. In the
   :program:`mongo` shell, you can set the ``noTimeout`` flag
   [#queryOptions]_:
-  
-  .. code-block:: javascript 
-  
+
+  .. code-block:: javascript
+
      var myCursor = db.inventory.find().addOption(DBQuery.Option.noTimeout);
-  
+
   See your :doc:`driver </applications/drivers>` documentation for
   information on setting the ``noTimeout`` flag.