DOCSP-20124 updates for update (#163) (#185)

Author: Dave

source/tutorial/manage-sharded-cluster-balancer.txt

@@ -105,7 +105,7 @@ the ``activeWindow``, as in the following:
 .. code-block:: javascript
 
    use config
-   db.settings.update({ _id : "balancer" }, { $unset : { activeWindow : true } })
+   db.settings.updateOne( { _id : "balancer" }, { $unset : { activeWindow : true } } )
 
 .. _sharding-balancing-disable-temporally:
 .. _sharding-balancing-disable-temporarily:
@@ -344,7 +344,7 @@ the following command:
 .. code-block:: javascript
 
    use config
-   db.settings.update(
+   db.settings.updateOne(
       { "_id" : "balancer" },
       { $set : { "_secondaryThrottle" : { "w": "majority" }  } },
       { upsert : true }
@@ -391,7 +391,7 @@ change the balancer's ``_waitForDelete`` value:
    .. code-block:: javascript
 
       use config
-      db.settings.update(
+      db.settings.updateOne(
          { "_id" : "balancer" },
          { $set : { "_waitForDelete" : true } },
          { upsert : true }
@@ -408,7 +408,7 @@ Once set to ``true``, to revert to the default behavior:
    .. code-block:: javascript
 
       use config
-      db.settings.update(
+      db.settings.updateOne(
          { "_id" : "balancer", "_waitForDelete": true },
          { $unset : { "_waitForDelete" : "" } }
       )

source/tutorial/model-monetary-data.txt

@@ -183,16 +183,15 @@ The results of the aggregation pipeline can be verified using the
 
 If you do not want to add a new field with the ``decimal`` value, the
 original field can be overwritten. The following
-:method:`~db.collection.update()` method first checks that ``price``
+:method:`~db.collection.updateMany()` method first checks that ``price``
 exists and that it is a ``long``, then transforms the ``long`` value to
 ``decimal`` and stores it in the ``price`` field:
 
 .. code-block:: javascript
 
-   db.clothes.update( 
+   db.clothes.updateMany( 
      { price: { $type: "long" } },
-     { $mul: { price: NumberDecimal( "0.01" ) } },
-     { multi: 1 }
+     { $mul: { price: NumberDecimal( "0.01" ) } }
    )
 
 The results can be verified using the ``db.clothes.find()`` query:

source/tutorial/schedule-backup-window-for-sharded-clusters.txt

@@ -25,8 +25,8 @@ chunk migrations affect the content of the backup captured by the
 backup procedure. Using the procedure outlined in the section
 :ref:`sharding-balancing-disable-temporarily` you can manually stop the
 balancer process temporarily. As an alternative, you can
-use the following procedure to define a balancing window so that the balancer
-is always disabled during your automated backup operation.
+use the following procedure to define a balancing window so that the
+balancer is always disabled during your automated backup operation.
 
 .. tip::
 
@@ -42,11 +42,16 @@ following command:
 .. code-block:: javascript
 
    use config
-   db.settings.update( { _id : "balancer" }, { $set : { activeWindow : { start : "06:00", stop : "23:00" } } }, true )
+   db.settings.updateOne(
+      { _id : "balancer" }, 
+      { $set : { activeWindow : { start : "06:00", stop : "23:00" } } }, 
+      true
+   )
 
 This operation configures the balancer to run between 6:00am and
 11:00pm, server time. Schedule your backup operation to run *and
 complete* outside of this time. Ensure that the backup can complete
 outside the window when the balancer is running *and* that the
 balancer can effectively balance the collection among the shards
 in the window allotted to each.
+