Docsp 19918 update db.collection.update pt1 v5.1 (#85)

* DOCSP-19918 fix update examples pt1

* More pages

* Add slice page

* Review feedback

Author: Dave

source/core/document.txt

@@ -330,7 +330,7 @@ Update Specification Documents
 
 Update specification documents use :ref:`update operators
 <update-operators>` to specify the data modifications to perform on
-specific fields during an :method:`db.collection.update()` operation.
+specific fields during an update operation.
 
 .. code-block:: javascript
 

source/core/retryable-writes.txt

@@ -107,7 +107,6 @@ cannot be :writeconcern:`{w: 0} <\<number\>>`.
 
    * - | :method:`db.collection.updateOne()`
        | :method:`db.collection.replaceOne()`
-       | :method:`db.collection.update()` where ``multi`` is ``false``
      - Single-document update operations. [#duplicate-key-update]_
 
    * - | :method:`db.collection.deleteOne()`

source/core/write-operations-atomicity.txt

@@ -38,8 +38,7 @@ One approach is to create a :ref:`unique index <index-type-unique>` on a
 field that can only have unique values. This prevents insertions or
 updates from creating duplicate data. Create a unique index on multiple
 fields to force uniqueness on that combination of field values. For
-examples of use cases, see :ref:`update() and Unique Index
-<update-with-unique-indexes>` and :ref:`findAndModify() and Unique Index
+examples of use cases, see :ref:`findAndModify() and Unique Index
 <upsert-and-unique-index>`.
 
 Another approach is to specify the expected current value of a field in

source/faq/concurrency.txt

@@ -110,8 +110,7 @@ In some situations, read and write operations can yield their locks.
 Long running read and write operations, such as queries, updates,
 and deletes, yield locks under many conditions. MongoDB operations can
 also yield locks between individual document modifications in write
-operations that affect multiple documents like
-:method:`~db.collection.update()` with the ``multi`` parameter.
+operations that affect multiple documents.
 
 For storage engines supporting document level :term:`concurrency
 control`, such as :doc:`WiredTiger </core/wiredtiger>`, yielding is not

source/includes/example-addToSet-each.rst

@@ -10,7 +10,7 @@ with the :update:`$each` modifier to add multiple elements to the
 
 .. code-block:: javascript
 
-   db.inventory.update(
+   db.inventory.updateOne(
       { _id: 2 },
       { $addToSet: { tags: { $each: [ "camera", "electronics", "accessories" ] } } }
     )
@@ -25,3 +25,4 @@ The operation adds only ``"camera"`` and ``"accessories"`` to the
      item: "cable",
      tags: [ "electronics", "supplies", "camera", "accessories" ]
    }
+

source/includes/example-push-each.rst

@@ -4,7 +4,8 @@ equals ``joe``:
 
 .. code-block:: javascript
 
-   db.students.update(
+   db.students.updateOne(
       { name: "joe" },
       { $push: { scores: { $each: [ 90, 92, 85 ] } } }
    )
+

source/includes/example-push-with-multiple-modifiers.rst

@@ -26,7 +26,7 @@ The following :update:`$push` operation uses:
 
 .. code-block:: javascript
 
-   db.students.update(
+   db.students.updateOne(
       { _id: 5 },
       {
         $push: { 

source/includes/extracts-collation.yaml

@@ -262,8 +262,7 @@ content: |-
 
       * - :dbcommand:`update`
 
-        - | :method:`db.collection.update()`
-          | :method:`db.collection.updateOne()`,
+        - | :method:`db.collection.updateOne()`,
           | :method:`db.collection.updateMany()`,
           | :method:`db.collection.replaceOne()`
 

source/includes/fact-findAndModify-update-comparison.rst

@@ -1,30 +1,26 @@
 When updating a document, |operation| and the
-:method:`~db.collection.update()` method operate differently:
-
-- By default, both operations modify a single document. However, the
-  :method:`~db.collection.update()` method with its ``multi`` option
-  can modify more than one document.
+:method:`~db.collection.updateOne()` method operate differently:
 
 - If multiple documents match the update criteria, for
   |operation|, you can specify a ``sort`` to provide some
   measure of control on which document to update.
 
-  With the default behavior of the :method:`~db.collection.update()`
-  method, you cannot specify which single document to update when
-  multiple documents match.
+  :method:`~db.collection.updateOne()` updates the first document that
+  matches.
 
 - By default, |operation| returns |return-object|. To
   obtain the updated document, use the ``new`` option.
 
-  The :method:`~db.collection.update()` method returns a
+  The :method:`~db.collection.updateOne()` method returns a
   :method:`WriteResult` object that contains the status of the operation.
+  
   To return the updated document, use the :method:`~db.collection.find()`
   method. However, other updates may have modified the document between
   your update and the document retrieval. Also, if the update modified
   only a single document but multiple documents matched, you will need to
   use additional logic to identify the updated document.
 
 When modifying a *single* document, both |operation| and the
-:method:`~db.collection.update()` method *atomically* update the
+:method:`~db.collection.updateOne()` method *atomically* update the
 document. See :doc:`/core/write-operations-atomicity` for more
 details about interactions and order of operations of these methods.

source/reference/operator/update/slice.txt

@@ -86,7 +86,7 @@ last five elements:
 
 .. code-block:: javascript
 
-   db.students.update(
+   db.students.updateOne(
       { _id: 1 },
       {
         $push: {
@@ -120,7 +120,7 @@ first three elements.
 
 .. code-block:: javascript
 
-   db.students.update(
+   db.students.updateOne(
       { _id: 2 },
       {
         $push: {
@@ -155,7 +155,7 @@ array ``[]`` for the :update:`$each` modifier, as in the following:
 
 .. code-block:: javascript
 
-   db.students.update(
+   db.students.updateOne(
      { _id: 3 },
      {
        $push: {