DOCSP-15834 remove methods not available in mongosh

Author: mungitoperrito

config/redirects

@@ -1522,7 +1522,7 @@ raw: /master/release-notes/3.0-general-improvements -> ${base}/release-notes/3.0
 [*-v3.4]: /${version}/reference/operator/aggregation/currentOp -> ${base}/${version}/reference/command/currentOp/
 
 # 2.8 compatibility
-# 
+
 # [*]: /${version}/release-notes/2.8-downgrade -> ${base}/${version}/release-notes/
 # [*]: /${version}/release-notes/2.8-compatibility -> ${base}/${version}/release-notes/
 # [*]: /${version}/release-notes/2.8-changes -> ${base}/${version}/release-notes/
@@ -1799,9 +1799,14 @@ raw: /manual/core/wildcard -> ${base}/manual/core/index-wildcard/
 
 [v5.0-*]: /${version}/reference/command/isMaster -> ${base}/${version}/reference/command/hello/
 [v5.0-*]: /${version}/reference/method/db.isMaster -> ${base}/${version}/reference/method/db.hello/
+[v5.0-*]: /${version}/reference/method/db.collection.copyTo.txt -> ${base}/${version}/reference/operator/aggregation/out/
+[v5.0-*]: /${version}/reference/method/db.collection.save.txt -> ${base}/${version}/reference/method/db.collection.insertOne/
 [v5.0-*]: /${version}/reference/method/db.eval -> ${base}/${version}/reference/method/js-database/
 [v5.0-*]: /${version}/reference/method/db.getProfilingLevel -> ${base}/${version}/reference/method/db.getProfilingStatus/
-[v5.0-*]: /${version}/reference/method/Mongo.isCausalConsistency -> ${base}/${version}/core/crud/
+[v5.0-*]: /${version}/reference/method/Mongo.getSecondaryOk -> ${base}/${version}/reference/method/Mongo.getReadPrefMode/
+[v5.0-*]: /${version}/reference/method/Mongo.isCausalConsistency -> ${base}/${version}/core/causal-consistency-read-write-concerns/
+[v5.0-*]: /${version}/reference/method/Mongo.setSecondaryOk -> ${base}/${version}/reference/method/Mongo.setReadPref/
+[v5.0-*]: /${version}/reference/method/rs.secondaryOk.txt -> ${base}/${version}/reference/replica-configuration/
 [v5.0-*]: /${version}/mongo -> ${base}/${version}/reference/mongo/
 
 #

source/core/retryable-writes.txt

@@ -93,7 +93,7 @@ cannot be :writeconcern:`{w: 0} <\<number\>>`.
 .. note::
 
    The write operations inside the :doc:`transactions
-   </core/transactions>` are not individually retryable. 
+   </core/transactions>` are not individually retryable.
 
 .. list-table::
    :header-rows: 1
@@ -109,7 +109,6 @@ cannot be :writeconcern:`{w: 0} <\<number\>>`.
 
    * - | :method:`db.collection.updateOne()`
        | :method:`db.collection.replaceOne()`
-       | :method:`db.collection.save()`
        | :method:`db.collection.update()` where ``multi`` is ``false``
 
      - Single-document update operations. [#duplicate-key-update]_
@@ -165,10 +164,10 @@ cannot be :writeconcern:`{w: 0} <\<number\>>`.
    details, see :ref:`update-shard-key`.
 
 .. [#duplicate-key-update]
-   
+
    MongoDB 4.2 will retry certain single-document upserts
-   (update with ``upsert: true`` and ``multi: false``) that encounter a 
-   duplicate key exception. See :ref:`retryable-update-upsert` for 
+   (update with ``upsert: true`` and ``multi: false``) that encounter a
+   duplicate key exception. See :ref:`retryable-update-upsert` for
    conditions.
 
    Prior to MongoDB 4.2, MongoDB would not retry upsert operations
@@ -207,7 +206,7 @@ the failover period exceeds :urioption:`serverSelectionTimeoutMS`.
 Duplicate Key Errors on Upsert
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-MongoDB 4.2 will retry single-document upsert operations 
+MongoDB 4.2 will retry single-document upsert operations
 (i.e ``upsert : true`` and ``multi : false``) that
 fail due to a duplicate key error *only if* the operation meets
 *all* of the following conditions:

source/core/transactions-operations.txt

@@ -134,9 +134,6 @@ operations against a :red:`non-existing` collection:
 
      - :dbcommand:`insert`
 
-   * - :method:`db.collection.save()` results in an insert
-     - 
-
    * - | :method:`db.collection.updateOne()` with ``upsert: true``
        | :method:`db.collection.updateMany()` with ``upsert: true``
        | :method:`db.collection.replaceOne()` with ``upsert: true``

source/includes/extracts-4.2-changes.yaml

@@ -814,10 +814,10 @@ content: |
      document. In earlier versions, these operations only attempt to
      target using the replacement document.
 
-   - The :method:`~db.collection.save()` method is deprecated: use the
+   - The ``save()`` method is deprecated: use the
      :method:`~db.collection.insertOne()` or
      :method:`~db.collection.replaceOne()` method instead. The
-     :method:`~db.collection.save()` method cannot be used with
+     ``save()`` method cannot be used with
      sharded collections that are *not* sharded by ``_id``, and
      attempting to do so will result in an error. 
 

source/includes/fact-getSecondaryOk.rst

@@ -4,8 +4,8 @@
    included in the
    `MongoDB Server Download
    <https://www.mongodb.com/try/download/community?tck=docs_server>`__.
-   For information on the new MongoDB Shell, ``mongosh``, refer to the
-   :mongosh:`mongosh Documentation </>`.
+   For information on the new MongoDB Shell (``mongosh``) refer to the
+   :mongosh:`mongosh documentation </>`.
 
    To understand the differences between the two shells, see
    :ref:`compare-mongosh-mongo`.

source/includes/fact-mongosh-callout.rst

@@ -84,18 +84,6 @@
 
           :ref:`transactions-operations-ddl`
 
-   * - :method:`db.collection.save()`
-     - 
-     - Starting in MongoDB 4.4, if run on a non-existing
-       collection, the collection is implicitly created.
-       
-       In MongoDB 4.2 and earlier, the operation must be run on an
-       existing collection.
-
-       .. seealso::
-
-          :ref:`transactions-operations-ddl`
-
    * - | :method:`db.collection.updateOne()`
        | :method:`db.collection.updateMany()`
        | :method:`db.collection.replaceOne()`

source/includes/fact-secondaryOk.rst

@@ -99,13 +99,13 @@ Example
 Convert a Collection
 ~~~~~~~~~~~~~~~~~~~~
 
-The following example uses a :method:`db.collection.save()` operation to create
+The following example uses :method:`db.collection.insertOne()` to create
 an ``events`` collection, and :method:`db.collection.stats()` to obtain
 information about the collection:
 
 .. code-block:: javascript
 
-   db.events.save( { click: 'button-1', time: new Date() } )
+   db.events.insertOne( { click: 'button-1', time: new Date() } )
    db.events.stats()
 
 MongoDB will return the following: