(DOCSP-26419): Replace Agg-Collation doc directives (#2174)

* replace doc directives

* fix build and a few outliers

* small fix from copy review

Author: davidhou17

source/administration/production-checklist-operations.txt

@@ -107,8 +107,8 @@ Sharding
 
 .. cssclass:: checklist
 
-   - Place your :doc:`config servers
-     </core/sharded-cluster-config-servers>` on dedicated hardware for
+   - Place your :ref:`config servers
+     <sharding-config-server>` on dedicated hardware for
      optimal performance in large clusters. Ensure that the hardware has
      enough RAM to hold the data files entirely in memory and that it
      has dedicated storage.

source/aggregation.txt

@@ -1,3 +1,5 @@
+.. _aggregation:
+
 ======================
 Aggregation Operations
 ======================

source/core/authorization.txt

@@ -26,8 +26,8 @@ authorization using the :option:`--auth <mongod --auth>` or the
 authentication </core/security-internal-authentication>` also enables
 client authorization.
 
-Once access control is enabled, users must :doc:`authenticate
-</core/authentication>` themselves.
+Once access control is enabled, users must :ref:`authenticate
+<authentication>` themselves.
 
 .. _roles:
 

source/core/data-model-operations.txt

@@ -19,7 +19,7 @@ increase the throughput of insert and update operations, or distribute
 activity to a sharded cluster more effectively.
 
 When developing a data model, analyze all of your application's
-:doc:`read and write operations </crud>` in conjunction with the
+:ref:`read and write operations <crud>` in conjunction with the
 following considerations.
 
 .. _data-model-atomicity:

source/core/document.txt

@@ -15,7 +15,7 @@ Documents
 MongoDB stores data records as BSON documents. BSON is a binary
 representation of :term:`JSON` documents, though it contains more data
 types than JSON. For the BSON spec, see `bsonspec.org
-<http://bsonspec.org/>`_. See also :doc:`/reference/bson-types`.
+<http://bsonspec.org/>`_. See also :ref:`bson-types`.
 
 .. include:: /images/crud-annotated-document.rst
 
@@ -37,8 +37,8 @@ following structure:
       fieldN: valueN
    }
 
-The value of a field can be any of the BSON :doc:`data types
-</reference/bson-types>`, including other documents, arrays, and arrays
+The value of a field can be any of the BSON :ref:`data types
+<bson-types>`, including other documents, arrays, and arrays
 of documents. For example, the following document contains values of varying types:
 
 .. code-block:: javascript
@@ -252,8 +252,8 @@ The ``_id`` field has the following behavior and constraints:
 _ If the ``_id`` contains subfields, the subfield names cannot begin
   with a (``$``) symbol.
 
-- The ``_id`` field may contain values of any :doc:`BSON data type
-  </reference/bson-types>`, other than an array, regex, or undefined.
+- The ``_id`` field may contain values of any :ref:`BSON data type
+  <bson-types>`, other than an array, regex, or undefined.
 
   .. warning:: To ensure functioning replication, do not store values
      that are of the BSON regular expression type in the ``_id``

source/core/hashed-sharding.txt

@@ -80,7 +80,7 @@ inserts similar to the following:
 .. include:: /images/sharded-cluster-monotonic-distribution.rst
 
 Since the value of ``X`` is always increasing, the chunk with an upper bound
-of :doc:`maxKey</reference/bson-types>` receives the majority incoming writes. This
+of :bsontype:`MaxKey` receives the majority incoming writes. This
 restricts insert operations to the single shard containing this chunk, which
 reduces or removes the advantage of distributed writes in a sharded cluster.
 
@@ -178,7 +178,7 @@ Sharding Empty Collection on Compound Hashed Shard Key with Hashed Field Prefix
 
     - The sharding operation creates empty chunks to cover the entire
       range of the shard key values and performs an initial chunk
-      distribution. The value of all non-hashed fields is ``MinKey`` at
+      distribution. The value of all non-hashed fields is :bsontype:`MinKey` at
       each split point. By default, the operation creates 2 chunks per
       shard and migrates across the cluster. You can use
       ``numInitialChunks`` option to specify a different number of

source/core/index-creation.txt

@@ -324,8 +324,8 @@ can occur, such as:
   fails to build the index for an associated shard or incorrectly
   builds an index with different specification.
 
-Starting in MongoDB 4.4 (and in MongoDB 4.2.6), the :doc:`config server
-</core/sharded-cluster-config-servers>` primary periodically checks for
+Starting in MongoDB 4.4 (and in MongoDB 4.2.6), the :ref:`config server
+<sharding-config-server>` primary periodically checks for
 index inconsistencies across the shards for sharded collections. To
 configure these periodic checks, see
 :parameter:`enableShardedIndexConsistencyCheck` and

source/core/security-transport-encryption.txt

@@ -253,8 +253,8 @@ Identity Verification
 ---------------------
 
 In addition to encrypting connections, TLS/SSL allows for authentication
-using certificates, both for :doc:`client authentication
-</core/authentication>` and for :doc:`internal authentication
+using certificates, both for :ref:`client authentication
+<authentication>` and for :doc:`internal authentication
 </core/security-internal-authentication>` of members of replica sets and
 sharded clusters.
 

source/core/sharded-cluster-config-servers.txt

@@ -30,7 +30,7 @@ updates the cache when there are metadata changes for the cluster, such
 as :ref:`adding a shard <sharding-procedure-add-shard>`. Shards also read 
 chunk metadata from the config servers.
 
-The config servers also store :doc:`authentication` configuration
+The config servers also store :ref:`authentication` configuration
 information such as :doc:`Role-Based Access
 Control</core/authorization>` or :doc:`internal
 authentication</core/security-internal-authentication>` settings for
@@ -79,8 +79,8 @@ collections <metadata-system-collections>` for internal use.
 The :doc:`config database </reference/config-database>` contains the
 collections that contain the sharded cluster metadata. MongoDB writes
 data to the :doc:`config database </reference/config-database>` when
-the metadata changes, such as after a :doc:`chunk migration
-</core/sharding-balancer-administration>` or a :doc:`chunk split
+the metadata changes, such as after a :ref:`chunk migration
+<sharding-balancing>` or a :doc:`chunk split
 </core/sharding-data-partitioning>`.
 
 Users should avoid writing directly to the config database in the

source/core/sharding-choose-a-shard-key.txt

@@ -124,10 +124,10 @@ A shard key on a value that increases or decreases monotonically is more
 likely to distribute inserts to a single chunk within the cluster.
 
 This occurs because every cluster has a chunk that captures a range with
-an upper bound of :doc:`maxKey</reference/bson-types>`. ``maxKey``
+an upper bound of :bsontype:`MaxKey`. ``maxKey``
 always compares as higher than all other values. Similarly, there is a
 chunk that captures a range with a lower bound of
-:doc:`minKey</reference/bson-types>`. ``minKey`` always compares as
+:bsontype:`MinKey`. ``minKey`` always compares as
 lower than all other values.
 
 If the shard key value is always increasing, all new inserts are routed

source/core/text-search-operators.txt

@@ -46,14 +46,14 @@ operators, including restrictions and behavior, see:
 Aggregation Pipeline
 --------------------
 
-When working with :doc:`/aggregation` pipelines, use
+When working with :ref:`aggregation <aggregation>` pipelines, use
 :pipeline:`$match` with a :query:`$text` expression to execute a text
 search query. To sort the results in order of relevance score, use the
 :expression:`$meta` *aggregation operator* in the :pipeline:`$sort`
 stage [#meta-aggregation]_.
 
 For more information and examples of text search in
-:doc:`/aggregation` pipelines, see
+:ref:`aggregation` pipelines, see
 :doc:`/tutorial/text-search-in-aggregation`.
 
 .. include:: /includes/fact-atlas-search-search-stage.rst

source/core/zone-sharding.txt

@@ -102,8 +102,8 @@ the specified parameter.
 One valid use of zone ranges on a hashed field is to restrict the data
 for a collection to the shard or shards in a single zone. Create a zone
 range that covers the entire range of possible hashed shard key values
-using :doc:`minKey </reference/bson-types>` as the lower bound and
-:doc:`maxkey </reference/bson-types>` as the upper bound.
+using :bsontype:`MinKey` as the lower bound and
+:bsontype:`MaxKey` as the upper bound.
 
 To define ranges, MongoDB provides the :dbcommand:`updateZoneKeyRange`
 command and the associated helper methods

source/faq/fundamentals.txt

@@ -124,9 +124,9 @@ store data for the collections.
 Does MongoDB support SQL?
 -------------------------
 
-Not directly, no. However, MongoDB does support a rich query language of its own. For
-examples on using MongoDB's query language, see
-:doc:`/crud`
+Not directly, no. However, MongoDB does support a rich query language of
+its own. For examples on using MongoDB's query language, see 
+:ref:`crud`.
 
 You can also use the `MongoDB Connector for BI
 <https://www.mongodb.com/products/bi-connector>`_ to query

source/faq/sharding.txt

@@ -24,7 +24,7 @@ the :doc:`/sharding` section in the manual, which provides an
 - :ref:`sharding-availability`
 
 - :doc:`/core/sharding-data-partitioning` and
-  :doc:`Chunk Migration Process </core/sharding-balancer-administration>`
+  :ref:`Chunk Migration Process <sharding-balancing>`
 
 - :doc:`/tutorial/troubleshoot-sharded-clusters`
 

source/includes/extracts-collation.yaml

@@ -5,7 +5,7 @@ content: |
 ---
 ref: collation-description
 content: |
-   :doc:`Collation </reference/collation>` allows users to specify
+   :ref:`Collation <collation>` allows users to specify
    language-specific rules for string comparison, such as rules for
    lettercase and accent marks.
 

source/includes/extracts-fact-query-bitwise.yaml

@@ -4,12 +4,12 @@ content: |
 
      * - ``{ <field>: { {{op}}: <numeric bitmask> } }``
 
-     * - ``{ <field>: { {{op}}: <`` :doc:`BinData </reference/bson-types>` ``bitmask> } }``
+     * - ``{ <field>: { {{op}}: <`` :bsontype:`BinData <Binary>` ``bitmask> } }``
 
      * - ``{ <field>: { {{op}}: [ <position1>, <position2>, ... ] } }``
 
   The ``field`` value must be either numeric or a
-  :doc:`BinData </reference/bson-types>` instance. Otherwise, :query:`{{op}}`
+  :bsontype:`BinData <Binary>` instance. Otherwise, :query:`{{op}}`
   will not match the current document.
 
   Numeric Bitmask
@@ -18,7 +18,7 @@ content: |
     :query:`{{op}}` will return an error.
 
   BinData Bitmask
-    You can also use an arbitrarily large :doc:`BinData </reference/bson-types>`
+    You can also use an arbitrarily large :bsontype:`BinData <Binary>` 
     instance as a bitmask.
 
   Position List
@@ -134,7 +134,7 @@ content: |
   to be set for the negative number ``-5``, but bit position ``200`` to be clear
   for the positive number ``+5``.
 
-  In contrast, :doc:`BinData </reference/bson-types>` instances are zero-extended.
+  In contrast, :bsontype:`BinData <Binary>` instances are zero-extended.
   For example, given the following document:
 
   .. code-block:: javascript

source/includes/extracts-parent-fact-count-on-sharded-clusters.yaml

@@ -2,7 +2,7 @@ ref: _fact-count-sharded-clusters
 content: |
   On a sharded cluster, {{countOp}} can result in an *inaccurate* count if
   :term:`orphaned documents <orphaned document>` exist or if a
-  :doc:`chunk migration </core/sharding-balancer-administration>` is in progress.
+  :ref:`chunk migration <sharding-balancing>` is in progress.
 
   To avoid these situations, on a sharded cluster, use the
   :method:`db.collection.aggregate()` method:

source/includes/fact-auth-restrictions-array-contents.rst

@@ -38,4 +38,4 @@ following fields. The server throws an error if the
    unable to authenticate the user.
 
 For more information on authentication in MongoDB, see
-:doc:`Authentication </core/authentication/>`.
+:ref:`authentication`.

source/includes/fact-index-key-length-operation-behaviors.rst

@@ -57,6 +57,6 @@ corresponding index entry exceeds the |limit|.
 
 .. index-field-limit-chunk-migration
 
-For existing sharded collections, :doc:`chunk migration
-</core/sharding-balancer-administration>` will fail if the chunk has a document
+For existing sharded collections, :ref:`chunk migration
+<sharding-balancing>` will fail if the chunk has a document
 that contains an indexed field whose index entry exceeds the |limit|.

source/includes/fact-type-bracketing.rst

@@ -1,6 +1,6 @@
 For most data types, :doc:`comparison
 operators</reference/operator/query-comparison>` only perform
 comparisons on fields where the
-:doc:`BSON type</reference/bson-types>` matches the
+:ref:`BSON type <bson-types>` matches the
 query value's type. MongoDB supports limited cross-BSON comparison
 through :ref:`type-bracketing`.

source/includes/in-use-encryption/update-a-key.rst

@@ -4,7 +4,7 @@ To add a {+dek-abbr+} to your {+key-vault-long+}, use the ``createKey`` method o
 To delete or update a {+dek-abbr+}, use one of the following mechanisms:
 
 - The ``rewrapManyDataKey`` method
-- Standard :manual:`CRUD </crud>` operations 
+- Standard :ref:`CRUD <crud>` operations 
 
 To learn more about the ``rewrapManyDataKey`` method, see the documentation
 of the method for your client or driver:

source/includes/steps-3.2-downgrade-sharded-cluster.yaml

@@ -11,8 +11,8 @@ title: "Check the ``minOpTimeUpdaters`` value."
 level: 4
 ref: 3.2-downgrade-minoptimerecovery
 content: |
-    If the sharded cluster uses :doc:`CSRS
-    </core/sharded-cluster-config-servers>`, for *each* shard, check
+    If the sharded cluster uses :ref:`CSRS
+    <sharding-config-server>`, for *each* shard, check
     the ``minOpTimeUpdaters`` value to see if it is zero. A
     ``minOpTimeUpdaters`` value of zero indicates that there are no
     migrations in progress. A non-zero value indicates either that a
@@ -44,8 +44,8 @@ title: "Prepare CSRS Config Servers for downgrade."
 level: 4
 ref: 3.2-downgrade-csrs
 content: |
-    If the sharded cluster uses :doc:`CSRS
-    </core/sharded-cluster-config-servers>`:
+    If the sharded cluster uses :ref:`CSRS
+    <sharding-config-server>`:
 
     a. :ref:`Remove secondary members from the replica set
        <remove-member-using-reconfig>` to have only a primary and two
@@ -99,13 +99,12 @@ content: |
 
     #. If you are rolling back to MMAPv1:
 
-       a. Start a :doc:`CSRS </core/sharded-cluster-config-servers>` member as
+       a. Start a :ref:`CSRS <sharding-config-server>` member as
           a standalone; i.e. without the :option:`--replSet <mongod --replSet>`
           or, if using a configuration file, :setting:`replication.replSetName`.
 
        #. Run :binary:`~bin.mongodump` to dump the ``config`` database, then
-          shutdown the :doc:`CSRS </core/sharded-cluster-config-servers>`
-          member.
+          shutdown the CSRS member.
 
           .. code-block:: bash
 

source/includes/steps-convert-replica-set-enable-sharding.yaml

@@ -60,7 +60,7 @@ action:
     code: |
       { "collectionsharded" : "test.test_collection", "ok" : 1 }
 post: |
-   The :doc:`balancer </core/sharding-balancer-administration>` redistributes
+   The :ref:`balancer <sharding-balancing>` redistributes
    chunks of documents when it next runs. As clients insert additional
    documents into this collection, the :binary:`~bin.mongos` routes the
    documents to the appropriate shard.

source/index.txt

@@ -92,7 +92,7 @@ Work with your data in MongoDB
 
             Use aggregation pipelines to process your data in multiple stages and return the computed results.
 
-            :doc:`To learn more, see Aggregation </aggregation>`
+            To learn more, see :ref:`aggregation`.
 
       .. code-block:: javascript
 

source/introduction.txt

@@ -60,8 +60,8 @@ MongoDB provides high performance data persistence. In particular,
 Query API
 ~~~~~~~~~
 
-The MongoDB Query API supports :doc:`read and write
-operations (CRUD) </crud>` as well as:
+The MongoDB Query API supports :ref:`read and write
+operations (CRUD) <crud>` as well as:
 
 - :ref:`Data Aggregation <aggregation-pipeline>`
 

source/query-api.txt

@@ -17,8 +17,8 @@ your data.
 
 The |query-api| comprises two ways to query data in MongoDB:
 
-- :doc:`CRUD Operations </crud>`
-- :doc:`Aggregation pipelines </core/aggregation-pipeline>`
+- :ref:`CRUD Operations <crud>`
+- :ref:`Aggregation pipelines <aggregation-pipeline>`
 
 You can use the |query-api| to perform:
 

source/reference/aggregation-commands-comparison.txt

@@ -136,7 +136,7 @@ MongoDB aggregation commands.
    * - More Information
 
      - 
-       - :doc:`/core/aggregation-pipeline` 
+       - :ref:`aggregation-pipeline` 
        - :method:`db.collection.aggregate()`
        - :dbcommand:`aggregate`
 

source/reference/command/aggregate.txt

@@ -245,7 +245,7 @@ arguments:
 .. include:: /includes/deprecation-aggregate-wo-cursor.rst
 
 For more information about the aggregation pipeline
-:doc:`/core/aggregation-pipeline`, :doc:`/reference/aggregation`, and
+:ref:`aggregation-pipeline`, :doc:`/reference/aggregation`, and
 :doc:`/core/aggregation-pipeline-limits`.
 
 Sessions

source/reference/command/cleanupOrphaned.txt

@@ -23,8 +23,8 @@ Definition
    in the event of a failover. You no longer need to run the
    :dbcommand:`cleanupOrphaned` command to clean up orphaned documents.
    Instead, use this command to wait for orphaned documents in a chunk
-   range from a shard key's :doc:`minKey</reference/bson-types>` to its
-   :doc:`maxKey</reference/bson-types>` for a specified namespace to be
+   range from a shard key's :bsontype:`MinKey` to its
+   :bsontype:`MaxKey` for a specified namespace to be
    cleaned up from a majority of a shard's members.
 
    **For orphaned documents generated before upgrading to MongoDB

source/reference/command/currentOp.txt

@@ -1460,8 +1460,8 @@ Output Fields
 
    The state of the resharding coordinator for the current
    :ref:`resharding operation <sharding-resharding>`. The resharding
-   coordinator is an operation that runs on the :doc:`config server
-   </core/sharded-cluster-config-servers>` primary. The state is set to
+   coordinator is an operation that runs on the :ref:`config server
+   <sharding-config-server>` primary. The state is set to
    ``unused`` when a new resharding operation starts.
 
    Only present on the coordinating config server.