DOCSP-26150 Replace :doc: with :method: / :command: where possible (#2074)

* Date()

* internal review feedback

* internal review feedback

* internal review

Author: jmd-mongo

source/core/replica-set-oplog.txt

@@ -203,9 +203,8 @@ Replication Lag and Flow Control
 Under various exceptional situations, updates to a :term:`secondary's
 <secondary>` oplog might lag behind the desired performance time.  Use
 :method:`db.getReplicationInfo()` from a secondary member and the
-:doc:`replication status </reference/method/db.getReplicationInfo>`
-output to assess the current state of replication and determine if
-there is any unintended replication delay.
+replication status output to assess the current state of replication and 
+determine if there is any unintended replication delay.
 
 .. include:: /includes/extracts/4.2-changes-flow-control-general-desc.rst
 

source/faq/concurrency.txt

@@ -87,9 +87,9 @@ methods:
   MongoDB Enterprise Advanced
   </mongodb-enterprise-advanced?tck=docs_server>`
 
-Specifically, the :serverstatus:`locks` document in the :doc:`output of
-serverStatus </reference/command/serverStatus>`, or the :data:`~currentOp.locks` field
-in the :doc:`current operation reporting </reference/method/db.currentOp>`
+Specifically, the :serverstatus:`locks` document in the :ref:`output of
+serverStatus <server-status-output>`, or the :data:`~currentOp.locks` 
+field in the :method:`current operation reporting <db.currentOp>`
 provides insight into the type of locks and amount of lock
 contention in your :binary:`~bin.mongod` instance.
 

source/includes/fact-bulkwrite-operation-batches.rst

@@ -14,8 +14,7 @@ less than or equal to the value of the limit. For example, with the
 .. note::
 
    The driver only divides the group into smaller groups when using
-   the high-level API. If using
-   :doc:`db.runCommand() </reference/method/db.runCommand/>` directly
+   the high-level API. If using :method:`db.runCommand()` directly
    (for example, when writing a driver), MongoDB throws an error when
    attempting to execute a write batch which exceeds the limit.
 

source/includes/fact-index-build-memory-limit.rst

@@ -1,20 +1,18 @@
-Index builds may be initiated either by a user command
-such as :doc:`Create Index </reference/method/db.collection.createIndex/>`
-or by an administrative process such as an
-:doc:`initial sync </core/replica-set-sync>`.
-Both are subject to the limit set by
-:parameter:`maxIndexBuildMemoryUsageMegabytes`.
+Index builds may be initiated either by a user command such as 
+:dbcommand:`createIndexes` or by an administrative process such as an
+:ref:`initial sync <replica-set-sync>`. Both are subject to the limit 
+set by :parameter:`maxIndexBuildMemoryUsageMegabytes`.
 
-An :doc:`initial sync operation </core/replica-set-sync>` populates
-only one collection at a time and has no risk of exceeding the memory
-limit. However, it is possible for a user to start index
-builds on multiple collections in multiple databases simultaneously
-and potentially consume an amount of memory greater than the limit
-set in :parameter:`maxIndexBuildMemoryUsageMegabytes`.
+An :ref:`initial sync <replica-set-sync>` populates only one collection 
+at a time and has no risk of exceeding the memory limit. However, it is 
+possible for a user to start index builds on multiple collections in 
+multiple databases simultaneously and potentially consume an amount of 
+memory greater than the limit set by
+:parameter:`maxIndexBuildMemoryUsageMegabytes`.
 
 .. tip::
 
    To minimize the impact of building an index on replica sets and
    sharded clusters with replica set shards, use a rolling index build
-   procedure as described on
-   :doc:`/tutorial/build-indexes-on-replica-sets`.
+   procedure as described on :ref:`Rolling Index Builds on Replica Sets 
+   <index-building-replica-sets>`.

source/includes/warning-possible-data-loss-body.rst

@@ -1,16 +1,14 @@
 There is a small chance of data loss when using dollar (``$``) prefixed
 field names or field names that contain periods (``.``) if these
 field names are used in conjunction with unacknowledged writes
-(:doc:`write concern </reference/write-concern>` ``w=0``) on servers
+(:ref:`write concern <write-concern>` ``w=0``) on servers
 that are older than MongoDB 5.0.
 
-When running :doc:`insert </tutorial/insert-documents>`,
-:doc:`update </tutorial/insert-documents>`, and
-:doc:`findAndModify </reference/method/db.collection.findAndModify>`
-commands, drivers that are 5.0 compatible remove restrictions on
-using documents with field names that are dollar (``$``) prefixed or
-that contain periods (``.``). These field names generated a client-side
-error in earlier driver versions.
+When running :dbcommand:`insert`, :dbcommand:`update`, and 
+:dbcommand:`findAndModify` commands, drivers that are 5.0 compatible 
+remove restrictions on using documents with field names that are 
+dollar (``$``) prefixed or that contain periods (``.``). These field 
+names generated a client-side error in earlier driver versions.
 
 The restrictions are removed regardless of the server version the
 driver is connected to. If a 5.0 driver sends a document to an older

source/reference/method/db.collection.bulkWrite.txt

@@ -75,8 +75,8 @@ Definition
 
         - document
 
-        - Optional. A document expressing the :doc:`write concern
-          </reference/write-concern>`. Omit to use the default write concern.
+        - Optional. A document expressing the :ref:`write concern
+          <write-concern>`. Omit to use the default write concern.
 
           .. include:: /includes/extracts/transactions-operations-write-concern.rst
 
@@ -207,7 +207,7 @@ updateOne and updateMany
        - A document that only contains :ref:`update operator
          <update-operators>` expressions.
 
-       - An :doc:`aggregation pipeline </core/aggregation-pipeline>` ``[
+       - An :ref:`aggregation pipeline <aggregation-pipeline>` ``[
          <stage1>, <stage2>, ... ]`` that specifies the modifications to
          perform.
 
@@ -230,7 +230,7 @@ updateOne and updateMany
 
    * - ``hint``
 
-     - Optional. The :doc:`index </indexes>` to use to support the
+     - Optional. The :ref:`index <indexes>` to use to support the
        update ``filter``. If you specify an index that does not exist,
        the operation errors.
 
@@ -278,7 +278,7 @@ matching document only.
    * - ``replacement``
 
      - The replacement document. The document cannot contain
-       :doc:`update operators </reference/operator/update>`.
+       :ref:`update operators <update-operators>`.
 
    * - ``upsert``
 
@@ -292,7 +292,7 @@ matching document only.
 
    * - ``hint``
 
-     - Optional. The :doc:`index </indexes>` to use to support the
+     - Optional. The :ref:`index <indexes>` to use to support the
        update ``filter``. If you specify an index that does not exist,
        the operation errors.
 
@@ -477,7 +477,7 @@ Error Handling
 exception on errors (unless the operation is part of a transaction on
 MongoDB 4.0). See :ref:`bulkwrite-error-handling-txn`.
 
-Excluding :doc:`/reference/write-concern` errors, ordered operations
+Excluding :ref:`write concern <write-concern>` errors, ordered operations
 stop after an error, while unordered operations continue to process any
 remaining write operations in the queue, unless when run inside a
 transaction. See :ref:`bulkwrite-error-handling-txn`.

source/reference/method/db.collection.insertMany.txt

@@ -57,8 +57,8 @@ Definition
 
         - document
 
-        - Optional. A document expressing the :doc:`write concern
-          </reference/write-concern>`. Omit to use the default write concern.
+        - Optional. A document expressing the :ref:`write concern
+          <write-concern>`. Omit to use the default write concern.
 
           .. include:: /includes/extracts/transactions-operations-write-concern.rst
 
@@ -137,9 +137,9 @@ Error Handling
 
 Inserts throw a ``BulkWriteError`` exception.
 
-Excluding :doc:`/reference/write-concern` errors, ordered operations stop
-after an error, while unordered operations continue to process any
-remaining write operations in the queue.
+Excluding :ref:`write concern <write-concern>` errors, ordered 
+operations stop after an error, while unordered operations continue to 
+process any remaining write operations in the queue.
 
 Write concern errors are displayed in the ``writeConcernErrors`` field, while
 all other errors are displayed in the ``writeErrors`` field. If an error is

source/reference/operator/aggregation/dateAdd.txt

@@ -17,7 +17,7 @@ Definition
 
    .. versionadded:: 5.0
 
-   Increments a :doc:`Date </reference/method/Date>` object by a
+   Increments a :method:`Date()` object by a
    specified number of time units.
 
    The :expression:`$dateAdd` expression has the following syntax:
@@ -33,10 +33,10 @@ Definition
          }
       }
 
-   Returns a :doc:`Date </reference/method/Date>`. The ``startDate``  
-   can be any expression that resolves to type Date, Timestamp or
-   ObjectId. No matter which data type is used as input, the value
-   returned will be a :doc:`Date </reference/method/Date>` object.
+   Returns a ``Date()``. The ``startDate`` can be any expression that 
+   resolves to type Date, Timestamp or ObjectId. No matter which data 
+   type is used as input, the value returned will be a 
+   ``Date()`` object.
 
    .. list-table::
       :header-rows: 1

source/reference/operator/aggregation/dateFromString.txt

@@ -41,7 +41,7 @@ Definition
       * - ``dateString``
 
         - The date/time string to convert to a date object. See
-          :doc:`Date </reference/method/Date>` for
+          :method:`Date()` for
           more information on date/time formats.
 
           .. note::

source/reference/operator/aggregation/dateSubtract.txt

@@ -17,7 +17,7 @@ Definition
 
    .. versionadded:: 5.0
 
-   Decrements a :doc:`Date </reference/method/Date>` object by a
+   Decrements a :method:`Date()` object by a
    specified number of time units.
 
    The :expression:`$dateSubtract` expression has the following syntax:
@@ -33,10 +33,10 @@ Definition
          }
       } 
 
-   Returns a :doc:`Date </reference/method/Date>`. The ``startDate`` 
-   can be any expression that resolves to type Date, Timestamp or
-   ObjectId. No matter which data type is used as input, the value
-   returned will be a :doc:`Date </reference/method/Date>` object.
+   Returns a ``Date()``. The ``startDate`` can be any expression that 
+   resolves to type Date, Timestamp or ObjectId. No matter which data 
+   type is used as input, the value returned will be a ``Date()`` 
+   object.
 
    .. list-table::
       :header-rows: 1