DOCSP-26474 Replace ttl index refs (#2346)

* DOCSP-26474 Replace ttl index refs

* add extra ref

* fix update-operator conflict

Author: lindseymoore

source/administration/production-notes.txt

@@ -832,7 +832,7 @@ consider the following recommendations:
   files <dbpath>`.
 
 - Adjust the ``ulimit`` settings for your platform according to the
-  recommendations in the :doc:`ulimit </reference/ulimit>` reference.
+  recommendations in the :ref:`ulimit <ulimit>` reference.
   Low ``ulimit`` values will negatively affect MongoDB when under heavy
   use and can lead to failed connections to MongoDB processes and loss
   of service. 

source/core/index-hidden.txt

@@ -29,7 +29,7 @@ Behavior
 Apart from being hidden from the planner, hidden indexes behave like
 unhidden indexes. For example:
 
-- If a hidden index is a :doc:`unique index </core/index-unique>`, the
+- If a hidden index is a :ref:`unique index <index-type-unique>`, the
   index still applies its unique constraint to the documents.
 
 - If a hidden index is a :ref:`TTL index <index-feature-ttl>`, the index

source/core/sharding-reshard-a-collection.txt

@@ -134,8 +134,8 @@ Limitations
 - Only one collection can be resharded at a time.
 - :rsconf:`writeConcernMajorityJournalDefault` must be ``true``.
 - Resharding a collection that has a
-  :doc:`uniqueness </core/index-unique>` constraint is not supported.
-- The new shard key cannot have a :doc:`uniqueness </core/index-unique>`
+  :ref:`uniqueness <index-type-unique>` constraint is not supported.
+- The new shard key cannot have a :ref:`uniqueness <index-type-unique>`
   constraint.
 - The following commands and corresponding shell methods are not
   supported on the collection that is being resharded while the

source/reference/command/serverStatus.txt

@@ -2406,17 +2406,17 @@ metrics
 .. serverstatus:: metrics.ttl
 
    A document that reports on the operation of the resource use of the
-   :doc:`ttl index </tutorial/expire-data/>` process.
+   :ref:`ttl index <ttl-collections>` process.
 
 .. serverstatus:: metrics.ttl.deletedDocuments
 
    The total number of documents deleted from collections with a
-   :doc:`ttl index </tutorial/expire-data/>`.
+   :ref:`ttl index <ttl-collections>`.
 
 .. serverstatus:: metrics.ttl.passes
 
    The number of times the background process removes documents from
-   collections with a :doc:`ttl index </tutorial/expire-data/>`.
+   collections with a :ref:`ttl index <ttl-collections>`.
 
 .. _server-status-metrics-cursor:
 

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

@@ -217,7 +217,7 @@ otherwise specified:
      - boolean
 
      - Optional. Specifies that each index specified in the ``keyPatterns`` array
-       is a :doc:`unique index </core/index-unique>`. Unique indexes will not
+       is a :ref:`unique index <index-type-unique>`. Unique indexes will not
        accept insertion or update of documents where the index key value matches an
        existing value in the index.
 

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

@@ -72,8 +72,7 @@ Definition
 
         - The replacement document.
 
-          Cannot contain  
-          :doc:`update operators </reference/operator/update>`.
+          Cannot contain :ref:`update operators <update-operators-top-level>`.
 
 
 

source/reference/ulimit.txt

@@ -1,3 +1,5 @@
+.. _ulimit:
+
 =========================
 UNIX ``ulimit`` Settings
 =========================

source/release-notes/3.2.txt

@@ -1126,7 +1126,7 @@ additional CRUD methods that are consistent with the drivers' CRUD API:
 
      - Equivalent to :method:`db.collection.findAndModify()` method
        with ``update`` set to a document that specifies modifications
-       using :doc:`update operators </reference/operator/update>`.
+       using :ref:`update operators <update-operators-top-level>`.
 
    * - :method:`db.collection.insertMany()`
      - Equivalent to :method:`db.collection.insert()` method
@@ -1147,16 +1147,16 @@ additional CRUD methods that are consistent with the drivers' CRUD API:
      - Equivalent to :method:`db.collection.update( \<query\>,
        \<update\>, { multi: true, ... }) <db.collection.update()>`
        method with an ``<update>`` document that specifies
-       modifications using :doc:`update operators
-       </reference/operator/update>` and the ``multi`` option set to
+       modifications using :ref:`update operators
+       <update-operators-top-level>` and the ``multi`` option set to
        true.
 
    * - :method:`db.collection.updateOne()`
 
      - Equivalent to :method:`db.collection.update( \<query\>,
        \<update\> ) <db.collection.update()>` method with an
        ``<update>`` document that specifies modifications using
-       :doc:`update operators </reference/operator/update>`.
+       :ref:`update operators <update-operators-top-level>`.
 
 WiredTiger and ``fsyncLock``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

source/release-notes/4.2-compatibility.txt

@@ -810,7 +810,7 @@ features include:
 - Removal of :limit:`Index Name Length` for MongoDB versions with fCV
   set to 4.2+.
 
-- New internal format for :doc:`unique indexes </core/index-unique>`.
+- New internal format for :ref:`unique indexes <index-type-unique>`.
   The new format applies to both existing unique indexes as well as
   newly created/rebuilt unique indexes.
 

source/tutorial/deploy-replica-set-with-keyfile-access-control.txt

@@ -29,7 +29,7 @@ authentication mechanism and settings.
 
 Enforcing internal authentication also enforces user access control. To
 connect to the replica set, clients like :binary:`~bin.mongosh` need to
-use a :doc:`user account</core/authorization>`. See
+use a :ref:`user account<authorization>`. See
 :ref:`security-repSetDeploy-access-control`.
 
 Cloud Manager and Ops Manager

source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt

@@ -30,7 +30,7 @@ enable internal authentication.
 
 Enforcing internal authentication also enforces user access control. To
 connect to the replica set, clients like :binary:`~bin.mongosh` need to
-use a :doc:`user account</core/authorization>`. See
+use a :ref:`user account<authorization>`. See
 :ref:`security-shardClust-deploy-access-control`.
 
 CloudManager and OpsManager

source/tutorial/enforce-keyfile-access-control-in-existing-replica-set.txt

@@ -27,7 +27,7 @@ authentication mechanism and settings.
 
 Enforcing internal authentication also enforces user access control. To
 connect to the replica set, clients like :binary:`~bin.mongosh` need to
-use a :doc:`user account</core/authorization>`. See
+use a :ref:`user account<authorization>`. See
 :ref:`security-replSet-auth-access-control`.
 
 Cloud Manager and Ops Manager

source/tutorial/enforce-keyfile-access-control-in-existing-sharded-cluster.txt

@@ -30,7 +30,7 @@ enable internal authentication.
 
 Enforcing internal authentication also enforces user access control. To
 connect to the replica set, clients like :binary:`~bin.mongosh` need to
-use a :doc:`user account</core/authorization>`. See
+use a :ref:`user account<authorization>`. See
 :ref:`security-shardClust-enforce-access-control`.
 
 CloudManager and OpsManager