DOCSP-26454 :doc:s command line - document validation (#7089)

Author: jmd-mongo

source/administration/configuration.txt

@@ -12,8 +12,8 @@ Run-time Database Configuration
    :depth: 1
    :class: singlecol
 
-The :doc:`command line </reference/program/mongod>` and :doc:`configuration
-file </reference/configuration-options>` interfaces provide MongoDB
+The :ref:`command line <mongod>` and :ref:`configuration file 
+<configuration-file>` interfaces provide MongoDB
 administrators with a large number of options and settings for
 controlling the operation of the database system. This document
 provides an overview of common configurations and examples of
@@ -310,8 +310,8 @@ If running as a replica set, :method:`initiate <rs.initiate()>` the
 shard replica set and add members.
 
 For the router (i.e. :binary:`~bin.mongos`), configure at least one
-:binary:`~bin.mongos` process with the following :doc:`setting
-</reference/configuration-options>`:
+:binary:`~bin.mongos` process with the following :ref:`setting
+<configuration-options>`:
 
 .. code-block:: yaml
 

source/administration/production-notes.txt

@@ -681,7 +681,7 @@ WiredTiger uses :term:`prefix compression` on all indexes by default.
 Clock Synchronization
 ---------------------
 
-MongoDB :doc:`components </reference/program>` keep logical clocks for
+MongoDB :ref:`components <mongodb-package-components>` keep logical clocks for
 supporting time-dependent operations. Using `NTP <http://www.ntp.org/>`_
 to synchronize host machine clocks mitigates the risk of clock drift
 between components. Clock drift between components increases the

source/core/data-model-operations.txt

@@ -102,7 +102,7 @@ As you create indexes, consider the following behaviors of indexes:
 
 See :doc:`/applications/indexes` for more information on indexes as
 well as :doc:`/tutorial/analyze-query-plan/`. Additionally, the MongoDB
-:doc:`database profiler </tutorial/manage-the-database-profiler>` may
+:ref:`database profiler <database-profiler>` may
 help identify inefficient queries.
 
 .. _data-model-large-number-of-collections:

source/crud.txt

@@ -52,7 +52,7 @@ collection:
 In MongoDB, insert operations target a single :term:`collection`. All
 write operations in MongoDB are :doc:`atomic
 </core/write-operations-atomicity>` on the level of a single
-:doc:`document </core/document>`.
+:ref:`document <bson-document-format>`.
 
 .. include:: /images/crud-annotated-mongodb-insertOne.rst
 

source/faq/diagnostics.txt

@@ -276,7 +276,7 @@ consider the following options, depending on the nature of the impact:
 #. If the balancer is always migrating chunks to the detriment of
    overall cluster performance:
 
-   - You may want to attempt :doc:`decreasing the chunk size </tutorial/modify-chunk-size-in-sharded-cluster>`
+   - You may want to attempt :ref:`decreasing the chunk size <tutorial-modifying-chunk-size>`
      to limit the size of the migration.
 
    - Your cluster may be over capacity, and you may want to attempt to

source/includes/extracts-4.2-changes.yaml

@@ -129,7 +129,7 @@ content: |
 
    Starting in MongoDB 4.2 (and in 4.0.9), for slow operations, the :doc:`profiler
    entries </tutorial/manage-the-database-profiler>` and
-   :doc:`diagnostic log messages </reference/log-messages>` include
+   :ref:`diagnostic log messages <log-messages-ref>` include
    :data:`~system.profile.storage` information.
 ---
 ref: 4.2-changes-log-query-shapes-plan-cache-key
@@ -402,7 +402,7 @@ content: |
    will use FIPS compliant connections to
    :binary:`mongod` / :binary:`mongos` if the
    :binary:`mongod` / :binary:`mongos` instances are
-   :doc:`configured to use FIPS mode </tutorial/configure-fips>`.
+   :ref:`configured to use FIPS mode <configure-mdb-for-fips>`.
 ---
 ref: 4.2-changes-fips-program-mongod
 content: |
@@ -411,7 +411,7 @@ content: |
    will use FIPS compliant connections to the
    :binary:`~bin.mongod` if the
    :binary:`~bin.mongod` instance is
-   :doc:`configured to use FIPS mode </tutorial/configure-fips>`.
+   :ref:`configured to use FIPS mode <configure-mdb-for-fips>`.
 
 ---
 ref: 4.2-changes-fips
@@ -431,7 +431,7 @@ content: |
    The programs will use FIPS compliant connections to
    :binary:`mongod` / :binary:`mongos` if the
    :binary:`mongod` / :binary:`mongos` instances are
-   :doc:`configured to use FIPS mode </tutorial/configure-fips>`.
+   :ref:`configured to use FIPS mode <configure-mdb-for-fips>`.
 ---
 ref: 4.2-changes-count-syntax-validation
 content: |

source/includes/extracts-bypassDocumentValidation-base.yaml

@@ -2,7 +2,7 @@ ref: _bypassDocValidation
 content: |
      The {{role}} {{interface}} adds support for the
      ``bypassDocumentValidation`` option, which lets you bypass
-     :doc:`document validation </core/schema-validation>` when
+     :ref:`document validation <schema-validation-overview>` when
      inserting or updating documents in a collection with validation    
      rules.
 ...

source/includes/extracts-create-cmd.yaml

@@ -41,7 +41,7 @@ content: |
 
   A user with the :authrole:`readWrite` built in role on the database
   has the required privileges to run the listed operations. Either
-  :doc:`create a user </tutorial/create-users>` with the required role
+  :ref:`create a user <create-users>` with the required role
   or :ref:`grant the role to an existing user
   <modify-existing-user-access>`.
 replacement:

source/includes/extracts-views.yaml

@@ -114,7 +114,7 @@ content: |
 
   A user with the :authrole:`readWrite` built in role on the database
   has the required privileges to run the listed operations. Either
-  :doc:`create a user </tutorial/create-users>` with the required role
+  :ref:`create a user <create-users>` with the required role
   or :ref:`grant the role to an existing user
   <modify-existing-user-access>`
 

source/includes/fact-set-global-write-concern-before-reconfig.rst

@@ -1,6 +1,6 @@
 Starting in MongoDB 5.0, you must explicitly set the global default
 :ref:`write concern <write-concern>` before attempting to reconfigure a
 :term:`replica set <replica set>` with a
-:doc:`configuration </reference/replica-configuration>`
+:ref:`configuration <replica-set-configuration-settings>`
 that would change the implicit default write concern. To set the global
 default write concern, use the :dbcommand:`setDefaultRWConcern` command.

source/includes/steps-deploy-replica-set-with-auth.yaml

@@ -62,7 +62,7 @@ action:
       mongod --config <path-to-config-file>
     post: |
       For more information on the configuration file, see
-      :doc:`configuration options </reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
   - heading: Command Line
     pre: |
       If using the command line options, start the :binary:`~bin.mongod` with the following options:

source/includes/steps-enable-authentication-in-replica-set-no-downtime.yaml

@@ -254,7 +254,7 @@ action:
     post: |
     
       For more information on the configuration file, see 
-      :doc:`configuration options</reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
     
 post: |
 
@@ -341,7 +341,7 @@ action:
       mongod --config <path-to-config-file>
     post: |
       For more information on the configuration file, see 
-      :doc:`configuration options</reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
     
 post: |
 
@@ -413,7 +413,7 @@ action:
     post: |
     
       For more information on the configuration file, see 
-      :doc:`configuration options</reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
     
 post: |
   You can also use the equivalent :binary:`~bin.mongod` options when starting your
@@ -499,7 +499,7 @@ action:
       mongod --config <path-to-config-file>
     post: |
       For more information on the configuration file, see 
-      :doc:`configuration options</reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
     
 post: |
   You can also use the equivalent :binary:`~bin.mongod` options when starting your

source/includes/steps-kerberos-auth-activedirectory-authz.yaml

@@ -169,7 +169,7 @@ ref: security-kerberos-activedirectory-authauthz-configfile
 level: 4
 pre: |
 
-  A MongoDB :doc:`configuration file </administration/configuration>` is a
+  A MongoDB :ref:`configuration file <configuration-file>` is a
   plain-text YAML file with the ``.conf`` file extension.
 
   * If you are upgrading an existing MongoDB deployment, copy the

source/includes/steps-start-sharded-cluster.yaml

@@ -86,7 +86,7 @@ action:
       mongos --config <path-to-config>
     post: |
       For more information on the configuration file, see
-      :doc:`configuration options</reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
   - pre: |
       **Command Line**
 

source/reference/command/getAuditConfig.txt

@@ -124,5 +124,5 @@ has a filter which captures the desired operations and the
 .. seealso::
 
    :method:`db.adminCommand`, :dbcommand:`setAuditConfig`,
-   :doc:`configure audit filters</tutorial/configure-audit-filters>`
+   :ref:`configure audit filters <audit-filter>`
 

source/reference/glossary.txt

@@ -661,7 +661,7 @@ Glossary
       :ref:`geospatial-indexes-store-geojson`.
 
    lock
-      MongoDB uses locks to ensure that :doc:`concurrency </faq/concurrency>`
+      MongoDB uses locks to ensure that :ref:`concurrency <faq-concurrency>`
       does not affect correctness. MongoDB uses :term:`read locks
       <read lock>`, :term:`write locks <write lock>` and
       :term:`intent locks <intent lock>`. For more information, see
@@ -1143,7 +1143,7 @@ Glossary
 
    shell helper
       A method in ``mongosh`` that has a concise
-      syntax for a :doc:`database command <command>`. Shell helpers
+      syntax for a :ref:`database command <database-commands>`. Shell helpers
       improve the interactive experience. See
       :doc:`/reference/method`.
 

source/reference/method.txt

@@ -595,7 +595,7 @@ Database
 
    * - :method:`db.runCommand()`
 
-     - Runs a :doc:`database command </reference/command>`.
+     - Runs a :ref:`database command <database-commands>`.
 
    * - :method:`db.serverBuildInfo()`
 

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

@@ -170,7 +170,7 @@ Type Bracketing
 MongoDB treats some data types as equivalent for comparison purposes.
 For instance, numeric types undergo conversion before comparison. For 
 most data types, however,
-:doc:`comparison operators</reference/operator/query-comparison>` only 
+:ref:`comparison operators <query-selectors-comparison>` only 
 perform comparisons on documents where the 
 :ref:`BSON type <bson-types-comparison-order>` of the 
 target field matches the type of the query operand. Consider the 
@@ -1091,4 +1091,4 @@ Learn More
 - :method:`~db.collection.findOne()`
 - :method:`~db.collection.findAndModify()`
 - :method:`~db.collection.findOneAndDelete()`
-- :method:`~db.collection.findOneAndReplace()`
+- :method:`~db.collection.findOneAndReplace()`

source/reference/method/db.currentOp.txt

@@ -133,7 +133,7 @@ are equivalent:
    db.currentOp( { "$all": true } )
 
 :method:`db.currentOp` and the
-:doc:`database profiler</reference/database-profiler>` report the same
+:ref:`database profiler <database-profiler>` report the same
 basic diagnostic information for all CRUD operations, including the
 following:
 

source/reference/method/js-database.txt

@@ -147,7 +147,7 @@ Database Methods
 
    * - :method:`db.runCommand()`
 
-     - Runs a :doc:`database command </reference/command>`.
+     - Runs a :ref:`database command <database-commands>`.
 
    * - :method:`db.serverBuildInfo()`
 

source/reference/method/rs.reconfig.txt

@@ -50,7 +50,7 @@ Definition
 
         - document
 
-        - A :doc:`document </reference/replica-configuration>` that specifies
+        - A :ref:`document <replica-set-configuration-settings>` that specifies
           the configuration of a replica set.
 
       * - .. _rs-reconfig-method-force: 

source/reference/method/rs.reconfigForPSASet.txt

@@ -75,7 +75,7 @@ The :method:`rs.reconfigForPSASet()` method has the following syntax:
 
      - document
 
-     - A :doc:`document </reference/replica-configuration>` that
+     - A :ref:`document <replica-set-configuration-settings>` that
        specifies the new configuration of a replica set.
 
    * - ``force``

source/release-notes/3.4.txt

@@ -1184,7 +1184,7 @@ MongoDB 3.4 includes the following enhancements:
   megabytes per batch <cursor-batches>`.
 
 :method:`db.currentOp` and the
-:doc:`database profiler</reference/database-profiler>` report the same
+:ref:`database profiler <database-profiler>` report the same
 basic diagnostic information for all CRUD operations, including the
 following:
 

source/release-notes/3.6.txt

@@ -927,7 +927,7 @@ JSON Schema
 -----------
 
 MongoDB 3.6 adds the :query:`$jsonSchema` operator to support
-:doc:`document validation </core/schema-validation>` using JSON
+:ref:`document validation <schema-validation-overview>` using JSON
 Schema. For details, see :query:`$jsonSchema`.
 
 To use :query:`$jsonSchema`, ``featureCompatibilityVersion`` must be

source/release-notes/4.2.txt

@@ -1660,7 +1660,7 @@ Logging
 
 - MongoDB 4.2 adds a ``usedDisk`` indicator to the :doc:`profiler log
   messages </tutorial/manage-the-database-profiler>` and
-  :doc:`diagnostic log messages </reference/log-messages>` for the
+  :ref:`diagnostic log messages <log-messages-ref>` for the
   :dbcommand:`aggregate` operation. The ``usedDisk`` indicates whether
   any stages of an :dbcommand:`aggregate` operation wrote data to
   temporary files due to memory restrictions. For more information on

source/release-notes/4.4.txt

@@ -2454,7 +2454,7 @@ New ``replanReason`` Database Profiler Output Field
 MongoDB 4.4 adds the :data:`replanReason<system.profile.replanReason>`
 field to
 :doc:`database profiler output </tutorial/manage-the-database-profiler>`
-and :doc:`diagnostic log messages </reference/log-messages>`. The
+and :ref:`diagnostic log messages <log-messages-ref>`. The
 ``replanReason`` field contains the reason the query system evicted a
 :ref:`cached plan <query-plans-query-optimization>`.
 

source/tutorial/configure-linux-iptables-firewall.txt

@@ -37,7 +37,7 @@ following two chains:
 ``OUTPUT``
    Controls all outgoing traffic.
 
-Given the :doc:`default ports </reference/default-mongodb-port>` of all
+Given the :ref:`default ports <default-mongodb-port>` of all
 MongoDB processes, you must configure networking rules that permit *only*
 required communication between your application and the appropriate
 :binary:`~bin.mongod` and :binary:`~bin.mongos` instances.

source/tutorial/configure-windows-netsh-firewall.txt

@@ -48,7 +48,7 @@ by rule type, and parsed in the following order:
 By default, the policy in :guilabel:`Windows Firewall` allows all outbound connections
 and blocks all incoming connections.
 
-Given the :doc:`default ports </reference/default-mongodb-port>` of all
+Given the :ref:`default ports <default-mongodb-port>` of all
 MongoDB processes, you must configure networking rules that permit *only*
 required communication between your application and the appropriate
 :binary:`mongod.exe` and :binary:`mongos.exe` instances.

source/tutorial/deploy-shard-cluster.txt

@@ -155,7 +155,7 @@ command line parameter to specify the config servers.
          mongos --config <path-to-config>
 
       For more information on the configuration file, see 
-      :doc:`configuration options</reference/configuration-options>`.
+      :ref:`configuration options <configuration-options>`.
 
    .. tab:: Command Line
       :tabid: command-line

source/tutorial/evaluate-operation-performance.txt

@@ -16,7 +16,7 @@ performance.
 Use the Database Profiler to Evaluate Operations Against the Database
 ---------------------------------------------------------------------
 
-MongoDB provides a :doc:`database profiler </tutorial/manage-the-database-profiler>` that shows performance
+MongoDB provides a :ref:`database profiler <database-profiler>` that shows performance
 characteristics of each operation against the database. Use the profiler
 to locate any queries or write operations that are running slow. You can
 use this information, for example, to determine what indexes to create.