DOCSP-26460 replaces hide - oplog :doc:s (#7109)

Author: jmd-mongo

source/administration/monitoring.txt

@@ -35,8 +35,8 @@ a running MongoDB instance:
 - MongoDB distributes a set of utilities that provides real-time
   reporting of database activities.
 
-- MongoDB provides various :doc:`database commands
-  </reference/command>` that return statistics regarding the current
+- MongoDB provides various :ref:`database commands
+  <database-commands>` that return statistics regarding the current
   database state with greater fidelity.
 
 - `MongoDB Atlas <https://www.mongodb.com/atlas/database?tck=docs_server>`_
@@ -156,9 +156,9 @@ by the collection, and information about its indexes.
 ````````````````````
 
 The :dbcommand:`replSetGetStatus` command (:method:`rs.status()` from
-the shell) returns an overview of your replica set's status. The :doc:`replSetGetStatus
-</reference/command/replSetGetStatus>` document details the
-state and configuration of the replica set and statistics about its members.
+the shell) returns an overview of your replica set's status. The 
+``replSetGetStatus`` document details the state and configuration of the 
+replica set and statistics about its members.
 
 Use this data to ensure that replication is properly configured,
 and to check the connections between the current host and the other members
@@ -269,8 +269,7 @@ control these options.
 .. note::
 
    You can specify these configuration operations as the command line
-   arguments to :doc:`mongod </reference/program/mongod>` or :doc:`mongos
-   </reference/program/mongos>`
+   arguments to :binary:`mongod` or :binary:`mongos`.
 
    For example:
 

source/administration/production-checklist-development.txt

@@ -75,7 +75,7 @@ Replication
     .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
 
 - Ensure that your secondaries remain up-to-date by using
-  :doc:`monitoring tools </administration/monitoring>` and by
+  :ref:`monitoring tools <monitoring-for-mdb>` and by
   specifying appropriate :doc:`write concern
   </reference/write-concern>`.
 

source/core/backups.txt

@@ -167,7 +167,7 @@ systems.
 :binary:`~bin.mongodump` and :binary:`~bin.mongorestore` operate against a
 running :binary:`~bin.mongod` process, and can manipulate the underlying
 data files directly. By default, :binary:`~bin.mongodump` does not
-capture the contents of the :doc:`local database </reference/local-database>`.
+capture the contents of the :ref:`local database <replica-set-local-database>`.
 
 :binary:`~bin.mongodump` only captures the documents in the database. The
 resulting backup is space efficient, but :binary:`~bin.mongorestore` or

source/core/replica-set-oplog.txt

@@ -245,7 +245,7 @@ the ``local.oplog.rs`` collection from a standalone MongoDB instance.
 both :ref:`replication` and recovery of a node if the node goes down.
 
 Starting in MongoDB 5.0, it is no longer possible to perform manual
-write operations to the :doc:`oplog </core/replica-set-oplog>` on a
+write operations to the :ref:`oplog <replica-set-oplog>` on a
 cluster running as a :ref:`replica set <replication>`. Performing write
 operations to the oplog when running as a
 :term:`standalone instance <standalone>` should only be done with

source/core/replica-set-secondary.txt

@@ -16,7 +16,7 @@ Replica Set Secondary Members
 
 A secondary maintains a copy of the :term:`primary's <primary>` data
 set. To replicate data, a secondary applies operations from the
-primary's :doc:`oplog </core/replica-set-oplog>` to its own data set
+primary's :ref:`oplog <replica-set-oplog>` to its own data set
 in an asynchronous process. [#slow-oplogs]_ A replica set can have one or more
 secondaries.
 

source/core/replica-set-sync.txt

@@ -268,7 +268,7 @@ Replication
 -----------
 
 Secondary members replicate data continuously after the initial sync.
-Secondary members copy the :doc:`oplog </core/replica-set-oplog>` from
+Secondary members copy the :ref:`oplog <replica-set-oplog>` from
 their *sync from* source and apply these operations in an asynchronous
 process. [#slow-oplogs]_ 
 
@@ -287,7 +287,7 @@ Streaming Replication
 ~~~~~~~~~~~~~~~~~~~~~
 
 *Sync from* sources send a continuous stream 
-of :doc:`oplog </core/replica-set-oplog>` entries to their syncing 
+of :ref:`oplog <replica-set-oplog>` entries to their syncing 
 secondaries. Streaming replication mitigates replication lag in 
 high-load and high-latency networks. It also: 
 

source/core/retryable-writes.txt

@@ -30,7 +30,7 @@ Supported Deployment Topologies
 Supported Storage Engine
   Retryable writes require a storage engine supporting document-level
   locking, such as the :ref:`WiredTiger <storage-wiredtiger>` or
-  :doc:`in-memory </core/inmemory>` storage engines.
+  :ref:`in-memory <storage-inmemory>` storage engines.
 
 3.6+ MongoDB Drivers
   Clients require MongoDB drivers updated for MongoDB 3.6 or greater:

source/includes/steps-change-replica-set-wiredtiger.yaml

@@ -65,7 +65,7 @@ content: |
 
 post: |
   Since no data exists in the ``--dbpath``, the ``mongod`` will perform an
-  :doc:`initial sync </tutorial/resync-replica-set-member>`. The length of the
+  :ref:`initial sync <resync-replica-member>`. The length of the
   initial sync process depends on the size of the database and network
   connection between members of the replica set.
 

source/reference/command/serverStatus.txt

@@ -3775,7 +3775,7 @@ oplogTruncation
 
 .. serverstatus:: oplogTruncation
 
-   A document that reports on :doc:`oplog </core/replica-set-oplog>`
+   A document that reports on :ref:`oplog <replica-set-oplog>`
    truncations.
 
    The field only appears when the current instance is a member of a

source/reference/configuration-options.txt

@@ -199,7 +199,7 @@ Core Options
 
    *Default*: 0
 
-   The default :doc:`log message </reference/log-messages>`
+   The default :ref:`log message <log-messages-ref>`
    verbosity level for :ref:`components <log-message-components>`. The
    verbosity level determines the amount of :ref:`Informational and
    Debug <log-severity-levels>` messages MongoDB outputs. [#log-message]_

source/reference/limits.txt

@@ -679,7 +679,7 @@ Indexes
 
 .. limit:: Hidden Indexes
 
-   - You cannot :doc:`hide </core/index-hidden>` the ``_id`` index.
+   - You cannot :ref:`hide <index-type-hidden>` the ``_id`` index.
 
    - You cannot use :method:`~cursor.hint()` on a :doc:`hidden index
      </core/index-hidden>`.

source/reference/local-database.txt

@@ -126,7 +126,7 @@ Collections on Replica Set Members
    .. include:: /includes/fact-oplog-size.rst
 
    Starting in MongoDB 5.0, it is no longer possible to perform manual
-   write operations to the :doc:`oplog </core/replica-set-oplog>` on a
+   write operations to the :ref:`oplog <replica-set-oplog>` on a
    cluster running as a :ref:`replica set <replication>`. Performing
    write operations to the oplog when running as a
    :term:`standalone instance <standalone>` should only be done with

source/reference/method/cursor.comment.txt

@@ -57,7 +57,7 @@ find operation. This can make it easier to track a particular query in the
 following diagnostic outputs:
 
 - The :data:`system.profile <<database>.system.profile>`
-- The :data:`QUERY` :doc:`log </reference/log-messages>` component
+- The :data:`QUERY` :ref:`log <log-messages-ref>` component
 - :method:`db.currentOp()`
 
 See :ref:`configure log verbosity <log-messages-configure-verbosity>` for the
@@ -103,7 +103,7 @@ The following is an excerpt from the
    }
 
 
-:binary:`~bin.mongod` :doc:`log </reference/log-messages>`
+:binary:`~bin.mongod` :ref:`log <log-messages-ref>`
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The following is an excerpt from the :binary:`~bin.mongod` log. It has been

source/reference/parameters.txt

@@ -1829,7 +1829,7 @@ Logging Parameters
    |both|
 
    Specify an integer between ``0`` and ``5`` signifying the verbosity
-   of the :doc:`logging </reference/log-messages>`, where ``5`` is the
+   of the :ref:`logging <log-messages-ref>`, where ``5`` is the
    most verbose. [#log-message]_
 
    The default :parameter:`logLevel` is ``0`` (Informational).
@@ -2857,7 +2857,7 @@ If you attempt to update ``disableSplitHorizonIPCheck`` at run time,
    streaming replication.
 
    Set the value to ``false`` to disable streaming replication. If
-   disabled, secondaries fetch batches of :doc:`oplog </core/replica-set-oplog>`
+   disabled, secondaries fetch batches of :ref:`oplog <replica-set-oplog>`
    entries by issuing a request to their *sync from* source and waiting for a
    response. This requires a network roundtrip for each batch of :doc:`oplog
    </core/replica-set-oplog>` entries.

source/reference/system-collections.txt

@@ -20,7 +20,7 @@ MongoDB stores system information in collections that use the
 internal use. Do not create collections that begin with ``system``.
 
 MongoDB also stores some additional instance-local metadata in the
-:doc:`local database </reference/local-database>`, specifically for
+:ref:`local database <replica-set-local-database>`, specifically for
 replication purposes and in the :doc:`config database
 </reference/config-database>` for :ref:`sessions information
 <sessions>`.

source/release-notes/3.2.txt

@@ -1276,7 +1276,7 @@ Write Concern
 - For replica sets using :rsconf:`protocolVersion: 1
   <protocolVersion>`, secondaries acknowledge write operations after the
   secondary members have written to their respective on-disk
-  :doc:`journals </core/journaling>`, regardless of the :ref:`j <wc-j>`
+  :ref:`journals <journaling-internals>`, regardless of the :ref:`j <wc-j>`
   option.
 
 - For replica sets using :rsconf:`protocolVersion: 1

source/release-notes/4.4.txt

@@ -888,13 +888,13 @@ Streaming Replication
 ~~~~~~~~~~~~~~~~~~~~~
 
 Starting in MongoDB 4.4, *sync from* sources send a continuous 
-stream of :doc:`oplog </core/replica-set-oplog>` entries to their 
+stream of :ref:`oplog <replica-set-oplog>` entries to their 
 syncing secondaries. 
 
 Prior to MongoDB 4.4, secondaries fetched batches of :doc:`oplog 
 </core/replica-set-oplog>` entries by issuing a request to their *sync 
 from* source and waiting for a response. This required a network roundtrip 
-for each batch of :doc:`oplog </core/replica-set-oplog>` entries. MongoDB 
+for each batch of :ref:`oplog <replica-set-oplog>` entries. MongoDB 
 4.4 adds the :parameter:`oplogFetcherUsesExhaust` startup parameter for 
 disabling streaming replication and using the older replication behavior.
 

source/release-notes/5.0-compatibility.txt

@@ -202,7 +202,7 @@ Manual Oplog Writes
 ~~~~~~~~~~~~~~~~~~~
 
 Starting in MongoDB 5.0, it is no longer possible to perform manual
-write operations to the :doc:`oplog </core/replica-set-oplog>` on a
+write operations to the :ref:`oplog <replica-set-oplog>` on a
 cluster running as a :ref:`replica set <replication>`. Performing write
 operations to the oplog when running as a
 :term:`standalone instance <standalone>` should only be done with
@@ -368,7 +368,7 @@ Map-Reduce
 ----------
 
 Starting in version 5.0, MongoDB deprecates the
-:doc:`map-reduce</core/map-reduce>` operation.
+:ref:`map-reduce <map-reduce>` operation.
 
 For examples of aggregation pipeline alternatives to map-reduce
 operations, see :doc:`/reference/map-reduce-to-aggregation-pipeline` and

source/tutorial/change-replica-set-wiredtiger.txt

@@ -79,7 +79,7 @@ down the :term:`primary`, and updates the stepped-down member.
 
 To update a member to WiredTiger, the procedure removes a member's
 data, starts :binary:`~bin.mongod` with WiredTiger, and performs an
-:doc:`initial sync </tutorial/resync-replica-set-member>`.
+:ref:`initial sync <resync-replica-member>`.
 
 
 A. Update the secondary members to WiredTiger.