DOCSP-26275 replaces write-related doc directives (#2094)

Author: jmd-mongo

source/administration/production-notes.txt

@@ -208,7 +208,7 @@ Write Concern
 
 .. include:: /includes/introduction-write-concern.rst
 
-See the :doc:`Write Concern </reference/write-concern>` document for more
+See the :ref:`Write Concern <write-concern>` document for more
 information about choosing an appropriate write concern level for your
 deployment.
 

source/core/replica-set-rollbacks.txt

@@ -171,7 +171,7 @@ administrators can decide the next course of action to take.
 Avoid Replica Set Rollbacks
 ---------------------------
 
-For replica sets, the :doc:`write concern </reference/write-concern>`
+For replica sets, the :ref:`write concern <write-concern>`
 :writeconcern:`{ w: 1 } <\<number\>>` only provides acknowledgement of write
 operations on the primary. Data may be rolled back if the primary steps
 down before the write operations have replicated to any of the

source/includes/extracts-mongos-operations.yaml

@@ -9,15 +9,15 @@ ref: mongos-operations-wc-drop
 content: |
 
    When issued on a sharded cluster, :binary:`~bin.mongos` converts the
-   :doc:`write concern </reference/write-concern>` of the
+   :ref:`write concern <write-concern>` of the
    :dbcommand:`drop` command and its helper
    :method:`db.collection.drop()` to :writeconcern:`"majority"`.
 ---
 ref: mongos-operations-wc-rename-collection
 content: |
 
    When issued on a sharded cluster, :binary:`~bin.mongos` converts the
-   :doc:`write concern </reference/write-concern>` of the
+   :ref:`write concern <write-concern>` of the
    :dbcommand:`renameCollection` command and its helper
    :method:`db.collection.renameCollection()` to
    :writeconcern:`"majority"`.
@@ -26,23 +26,23 @@ ref: mongos-operations-wc-create
 content: |
 
    When issued on a sharded cluster, :binary:`~bin.mongos` converts the
-   :doc:`write concern </reference/write-concern>` of the
+   :ref:`write concern <write-concern>` of the
    :dbcommand:`create` command and its helper
    :method:`db.createCollection()` to :writeconcern:`"majority"`.
 ---
 ref: mongos-operations-wc-drop-database
 content: |
 
    When issued on a sharded cluster, MongoDB converts the specified
-   :doc:`write concern </reference/write-concern>` to
+   :ref:`write concern <write-concern>` to
    :writeconcern:`"majority"`.
 
 ---
 ref: mongos-operations-wc-shard-collection
 content: |
 
    :binary:`~bin.mongos` uses :writeconcern:`"majority"` for the
-   :doc:`write concern </reference/write-concern>` of the
+   :ref:`write concern <write-concern>` of the
    :dbcommand:`shardCollection` command and its helper
    :method:`sh.shardCollection()`.
 
@@ -68,14 +68,14 @@ ref: mongos-operations-wc-remove-shard
 content: |
 
    :binary:`~bin.mongos` converts the
-   :doc:`write concern </reference/write-concern>` of the
+   :ref:`write concern <write-concern>` of the
    :dbcommand:`removeShard` command to :writeconcern:`"majority"`.
 
 ---
 ref: mongos-operations-wc-fcv
 content: |
    When issued on a sharded cluster, :binary:`~bin.mongos` converts the
-   :doc:`write concern </reference/write-concern>` of the
+   :ref:`write concern <write-concern>` of the
    :dbcommand:`setFeatureCompatibilityVersion` command to :writeconcern:`"majority"`.
 ---
 ref: mongos-operations-wc

source/includes/introduction-write-concern.rst

@@ -1,4 +1,4 @@
-:doc:`Write concern </reference/write-concern>` describes the level of
+:ref:`Write Concern <write-concern>` describes the level of
 acknowledgement requested from MongoDB for write operations. The level
 of the write concerns affects how quickly the write operation returns.
 When write operations have a *weak* write concern, they return quickly.

source/includes/list-visibility-of-data.rst

@@ -1,4 +1,4 @@
-- Regardless of a write's :doc:`write concern </reference/write-concern>`, other
+- Regardless of a write's :ref:`write concern <write-concern>`, other
   clients using :readconcern:`"local"` or :readconcern:`"available"`
   read concern can see the result of a write operation before the write
   operation is acknowledged to the issuing client.

source/reference/command/aggregate.txt

@@ -223,7 +223,7 @@ arguments:
 
      - document
 
-     - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+     - Optional. A document that expresses the :ref:`write concern <write-concern>`
        to use with the :pipeline:`$out` or :pipeline:`$merge` stage. 
 
        Omit to use the default write concern with the :pipeline:`$out` or

source/reference/command/create.txt

@@ -372,7 +372,7 @@ The :dbcommand:`create` command has the following fields:
 
      - document
 
-     - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+     - Optional. A document that expresses the :ref:`write concern <write-concern>`
        for the operation. Omit to use the default write
        concern.
 

source/reference/command/delete.txt

@@ -116,7 +116,7 @@ The command takes the following fields:
      - document
      - .. _delete-command-wc:
 
-       Optional. A document expressing the :doc:`write concern </reference/write-concern>`
+       Optional. A document expressing the :ref:`write concern <write-concern>`
        of the :dbcommand:`delete` command. Omit to use the default write
        concern.
 

source/reference/command/findAndModify.txt

@@ -155,7 +155,7 @@ The command takes the following fields:
 
    * - ``writeConcern``
      - document
-     - Optional. A document expressing the :doc:`write concern </reference/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

source/reference/command/insert.txt

@@ -76,7 +76,7 @@ The command takes the following fields:
 
    * - ``writeConcern``
      - document
-     - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+     - Optional. A document that expresses the :ref:`write concern <write-concern>`
        of the :dbcommand:`insert` command. Omit to use the default write
        concern.
 

source/reference/command/renameCollection.txt

@@ -72,7 +72,7 @@ The command contains the following fields:
 
    * - ``writeConcern``
      - document
-     - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+     - Optional. A document that expresses the :ref:`write concern <write-concern>`
        for the operation. Omit to use the default write
        concern.
 

source/reference/command/update.txt

@@ -90,7 +90,7 @@ The command takes the following fields:
 
    * - ``writeConcern``
      - document
-     - Optional. A document expressing the :doc:`write concern </reference/write-concern>`
+     - Optional. A document expressing the :ref:`write concern <write-concern>`
        of the :dbcommand:`update` command. Omit to use the default write
        concern.
 

source/reference/method/Bulk.execute.txt

@@ -37,7 +37,7 @@ Description
 
         - document
 
-        - Optional. :doc:`Write concern </reference/write-concern>`
+        - Optional. :ref:`write concern <write-concern>`
           document for the bulk operation as a whole. Omit to use
           default. For a standalone :binary:`~bin.mongod` server, the
           write concern defaults to ``{ w: majority }``. With a replica

source/reference/method/db.aggregate.txt

@@ -163,7 +163,7 @@ Definition
 
           - document
 
-          - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+          - Optional. A document that expresses the :ref:`write concern <write-concern>`
             to use with the :pipeline:`$out` or :pipeline:`$merge` stage. 
 
             Omit to use the default write concern with the :pipeline:`$out` or

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

@@ -195,7 +195,7 @@ Definition
 
         - document
 
-        - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+        - Optional. A document that expresses the :ref:`write concern <write-concern>`
           to use with the :pipeline:`$out` or :pipeline:`$merge` stage. 
 
           Omit to use the default write concern with the :pipeline:`$out` or

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

@@ -180,7 +180,7 @@ Definition
 
         - document
 
-        - Optional. A document expressing the :doc:`write concern </reference/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

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

@@ -65,7 +65,7 @@ Definition
 
       * - ``writeConcern``
         - document
-        - Optional. A document expressing the :doc:`write concern </reference/write-concern>`.
+        - Optional. A document expressing the :ref:`write concern <write-concern>`.
           Omit to use the default write concern.
 
           .. code-block:: javascript

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

@@ -221,7 +221,7 @@ Override Default Write Concern
 
 The following operation to a replica set removes all the documents from
 the collection ``products`` where ``qty`` is greater than ``20`` and
-specifies a :doc:`write concern </reference/write-concern>` of ``w: 2``
+specifies a :ref:`write concern <write-concern>` of ``w: 2``
 with a ``wtimeout`` of 5000 milliseconds. This operation either returns
 after the write propagates to both the primary and one secondary, or
 times out after 5 seconds.

source/reference/method/db.createCollection.txt

@@ -392,7 +392,7 @@ Definition
 
         - document
 
-        - Optional. A document that expresses the :doc:`write concern </reference/write-concern>`
+        - Optional. A document that expresses the :ref:`write concern <write-concern>`
           for the operation. Omit to use the default write
           concern.
 

source/reference/method/db.getCollection.txt

@@ -53,7 +53,7 @@ The :method:`db.getCollection()` object can access any
 
 The collection specified may or may not exist on the server.  If the collection
 does not exist, MongoDB creates it implicitly as part of 
-:doc:`write operations </crud>` like 
+:ref:`write operations <crud>` like 
 :method:`db.collection.insertOne()`.
 
 Example

source/reference/mongodb-defaults.txt

@@ -240,7 +240,7 @@ Specify Write Concern: MongoDB Drivers
          Transactions`` tab.
 
       Using the :driver:`MongoDB drivers </>`, you can override the default 
-      :doc:`write concern </reference/write-concern>` and set write concern for 
+      :ref:`write concern <write-concern>` and set write concern for 
       operations at the following levels:
 
       .. list-table::

source/release-notes/2.6-compatibility.txt

@@ -167,7 +167,7 @@ Description
    The ``mongo`` shell write methods
    :method:`db.collection.insert()`, :method:`db.collection.update()`,
    ``db.collection.save()`` and :method:`db.collection.remove()`
-   now integrate the :doc:`write concern </reference/write-concern>`
+   now integrate the :ref:`write concern <write-concern>`
    directly into the method rather than with a separate ``getLastError``
    command to provide :ref:`acknowledgement of writes <wc-w>` whether
    run interactively in the ``mongo`` shell or

source/release-notes/5.0.txt

@@ -1003,7 +1003,7 @@ Implicit Default Write Concern
 .. include:: /includes/5.0-default-wc.rst
 
 The :writeconcern:`{ w: "majority" } <"majority">` default
-:doc:`write concern </reference/write-concern>` provides a stronger
+:ref:`write concern <write-concern>` provides a stronger
 durability guarantee in the event of an election, or if replica set
 members become unavailable.