DOCSP-26431 replace docs (#2274)

* DOCSP-26431 replace docs

* found unsaved file

* another unsaved file

Author: lindseymoore

source/core/index-creation.txt

@@ -353,7 +353,7 @@ Observe Stopped and Resumed Index Builds in the Logs
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 While an index is being built, progress is written to the 
-:doc:`MongoDB log</reference/log-messages>`. If an index build is
+:ref:`MongoDB log<log-messages-ref>`. If an index build is
 stopped and resumed there will be log messages with fields like these:
 
 .. code-block:: bash

source/core/read-preference-mechanics.txt

@@ -34,7 +34,7 @@ Read Preference for Replica Sets
 --------------------------------
 
 Server selection occurs once per operation and is governed by the
-:doc:`read preference </core/read-preference>` and ``localThresholdMS``
+:ref:`read preference <read-preference>` and ``localThresholdMS``
 settings to determine member eligibility for reads. The read preference
 is re-evaluated for each operation.
 
@@ -92,7 +92,7 @@ To use hedged reads:
 - the :binary:`~bin.mongos` must have enabled support for hedged reads
   (Default). See the :parameter:`readHedgingMode` parameter.
 
-- Non-``primary`` :doc:`read preferences </core/read-preference>` must
+- Non-``primary`` :ref:`read preferences <read-preference>` must
   enable use of hedged reads.
 
 .. include:: /includes/extracts/server-selection-read-preference-sharded-clusters.rst

source/core/workload-isolation.txt

@@ -50,7 +50,7 @@ Specifically, with MongoDB, you can:
 For full documentation of these features, see the following
 documentation in the MongoDB Manual:
 
-- :doc:`Read Preferences </core/read-preference>`, which controls how drivers
+- :ref:`Read Preferences <read-preference>`, which controls how drivers
   help applications target read operations to members of a replica set.
 
 - :doc:`Write Concerns </reference/write-concern>`, which controls

source/faq/sharding.txt

@@ -19,7 +19,7 @@ the :doc:`/sharding` section in the manual, which provides an
 - :doc:`Shard Keys and Considerations for Shard Key Selection
   </core/sharding-shard-key>`
 
-- :doc:`Query Routing </core/sharded-cluster-query-router/>`
+- :ref:`Query Routing <sharding-read-operations>`
 
 - :ref:`sharding-availability`
 
@@ -60,7 +60,7 @@ sharding a collection and cannot upgrade, the best option is to:
 
 - configure sharding using a more ideal shard key.
 
-- :doc:`pre-split </tutorial/create-chunks-in-sharded-cluster>` the shard
+- :ref:`pre-split <create-chunks-in-a-sharded-cluster>` the shard
   key range to ensure initial even distribution.
 
 - restore the dumped data into MongoDB.

source/includes/limits-sharding-shardkey-immutable.rst

@@ -6,7 +6,7 @@ In MongoDB 4.2 and earlier, to change a shard key:
 
 - Configure sharding using the new shard key.
 
-- :doc:`Pre-split </tutorial/create-chunks-in-sharded-cluster>` the shard
+- :ref:`Pre-split <create-chunks-in-a-sharded-cluster>` the shard
   key range to ensure initial even distribution.
 
 - Restore the dumped data into MongoDB.

source/indexes.txt

@@ -211,7 +211,7 @@ Index Properties
 Unique Indexes
 ~~~~~~~~~~~~~~
 
-The :doc:`unique </core/index-unique>` property for an index causes
+The :ref:`unique <index-type-unique>` property for an index causes
 MongoDB to reject duplicate values for the indexed field. Other than
 the unique constraint, unique indexes are functionally interchangeable
 with other MongoDB indexes.
@@ -221,7 +221,7 @@ with other MongoDB indexes.
 Partial Indexes
 ~~~~~~~~~~~~~~~
 
-:doc:`Partial indexes </core/index-partial>` only index the documents in
+:ref:`Partial indexes <index-type-partial>` only index the documents in
 a collection that meet a specified filter expression. By indexing a
 subset of the documents in a collection, partial indexes have lower
 storage requirements and reduced performance costs for index creation
@@ -233,7 +233,7 @@ and should be preferred over sparse indexes.
 Sparse Indexes
 ~~~~~~~~~~~~~~
 
-The :doc:`sparse </core/index-sparse>` property of an index ensures
+The :ref:`sparse <index-type-sparse>` property of an index ensures
 that the index only contain entries for documents that have the indexed
 field. The index skips documents that *do not* have the indexed field.
 

source/reference/command/profile.txt

@@ -1,3 +1,5 @@
+.. _profile-command:
+
 =======
 profile
 =======

source/reference/configuration-options.txt

@@ -4733,7 +4733,7 @@ LDAP Parameters
    until the :binary:`~bin.mongos` recalculates the average.
 
    See the :ref:`replica-set-read-preference-behavior-member-selection`
-   section of the :doc:`read preference </core/read-preference>`
+   section of the :ref:`read preference <read-preference>`
    documentation for more information.
 
 

source/reference/connection-string.txt

@@ -840,7 +840,7 @@ For more information, see :doc:`/reference/read-concern`.
 Read Preference Options
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-:doc:`Read preferences </core/read-preference>` describe the
+:ref:`Read preferences <read-preference>` describe the
 behavior of read operations with regards to :term:`replica sets
 <replica set>`. These parameters allow you to specify read preferences
 on a per-connection basis in the connection string.
@@ -891,7 +891,7 @@ For details, see :ref:`read-preference-tag-order-matching`.
 
    * - .. urioption:: readPreference
 
-     - Specifies the :doc:`read preferences </core/read-preference>`
+     - Specifies the :ref:`read preferences <read-preference>`
        for this connection. Possible values are:
 
        - :readmode:`primary` (*Default*)
@@ -953,7 +953,7 @@ For details, see :ref:`read-preference-tag-order-matching`.
        :binary:`mongo` shell. See :method:`cursor.readPref()` and
        :method:`Mongo.setReadPref()` instead.
 
-For more information, see :doc:`Read preferences </core/read-preference>`.
+For more information, see :ref:`Read preferences <read-preference>`.
 
 .. _connection-string-auth-options:
 

source/reference/glossary.txt

@@ -907,7 +907,7 @@ Glossary
       sets. By default, MongoDB directs reads to :term:`primaries
       <primary>`. However, you may also direct reads to secondaries for
       :term:`eventually consistent <eventual consistency>` reads. See
-      :doc:`Read Preference </core/read-preference>`.
+      :ref:`Read Preference <read-preference>`.
 
    read lock
       A shared :term:`lock` on a resource such as a collection or