DOCS-617 removed default write-concern note and added cursor handling

Author: kay-kim

draft/applications/create.txt

@@ -41,7 +41,7 @@ All insert operations in MongoDB exhibit the following properties:
 
 .. note::
 
-   .. include:: /includes/fact-write-concerns.rst
+..   .. include:: /includes/fact-write-concerns.rst
 
 .. _crud-create-insert:
 

draft/applications/delete.txt

@@ -20,7 +20,7 @@ shell provides this operation, as do corresponding methods in the
 
 .. note::
 
-   .. include:: /includes/fact-write-concerns.rst
+..   .. include:: /includes/fact-write-concerns.rst
 
 .. _crud-delete-remove:
 

draft/applications/read.txt

@@ -293,6 +293,46 @@ Consider the following examples that illustrate the use of the
           { _id: 0, 'name.first': 0, birth: 0 } 
       )
 
+  - The following operation finds all documents in the ``bios``
+    collection and returns the the ``last`` field in the ``name``
+    subdocument and the first two elements in the ``contribs`` field:
+
+    .. code-block:: javascript
+
+       db.bios.find( 
+          { },
+          { 
+            _id: 0,
+            'name.last': 1, 
+            contribs: { $slice: 2 }
+          } 
+       )
+
+Cursor
+~~~~~~
+
+:method:`find() <db.collection.find()>` returns a *cursor*; however, in
+the :program:`mongo` shell, the cursor is automatically iterated up to
+20 times to print the documents referenced by the cursor. To access the
+documents, you must explicitly handle the cursor, as in the following
+example:
+
+.. code-block:: javascript
+
+   var myCursor = db.bios.find( { _id: 1 } );
+
+   var myDocument = myCursor.hasNext() ? myCursor.next() : null;
+
+   if (myDocument) {
+      var myName = myDocument.name;
+
+      print (tojson(myName));
+   }
+
+See the :method:`cursor.forEach()`, :method:`cursor.hasNext()`,
+:method:`cursor.next()` documentation for more information on cursor
+handling.
+
 In addition to the ``<query>`` and the ``<projection>`` arguments, the
 :program:`mongo` shell and the :doc:`drivers </applications/drivers>`
 provide several cursor methods that you can call on the *cursor*
@@ -437,4 +477,15 @@ because the :method:`findOne() <db.collection.findOne()>` method
 returns a document rather than a cursor, you cannot apply the cursor
 methods such as :method:`limit() <cursor.limit()>`, :method:`sort()
 <cursor.sort()>`, and :method:`skip() <cursor.skip()>` to the result of
-the :method:`findOne() <db.collection.findOne()>` method.
+the :method:`findOne() <db.collection.findOne()>` method. However, you
+can access the document directly, as in the following example:
+
+.. code-block:: javascript
+
+   var myDocument = db.bios.findOne();
+
+   if (myDocument) {
+      var myName = myDocument.name;
+
+      print (tojson(myName));   
+   }

draft/applications/update.txt

@@ -24,9 +24,9 @@ methods to perform update operations:
 
 .. note::
 
-   - .. include:: /includes/fact-update-field-order.rst
+   .. include:: /includes/fact-update-field-order.rst
 
-   - .. include:: /includes/fact-write-concerns.rst
+..   - .. include:: /includes/fact-write-concerns.rst
 
 .. _crud-update-update:
 
@@ -319,13 +319,11 @@ Consider the following examples of the :method:`save()
 
 - If no ``_id`` field exists or if the ``_id`` field exists but does
   not match any document in the collection, the :method:`save()
-  <db.collection.save()>` method performs an insert. If no ``_id``
-  field exists, the insert will generate a unique :term:`Object` for
-  and create an ``_id`` field for the new document.
+  <db.collection.save()>` method performs an insert. 
 
   The following operation adds the ``_id`` field to the document,
-  assigns to the field a unique ``ObjectId``, and inserts the document
-  into the ``bios`` collection:
+  assigns to the field a unique :term:`ObjectId <object-id>`, and
+  inserts the document into the ``bios`` collection:
 
   .. code-block:: javascript