DOCSP-26473 docs replacements (mongodb#2378)

Author: lindseymoore

source/core/replica-set-write-concern.txt

@@ -135,7 +135,7 @@ operation uses its own write concern instead of the default.
 Custom Write Concerns
 ---------------------
 
-You can :doc:`tag </tutorial/configure-replica-set-tag-sets>` the
+You can :ref:`tag <replica-set-configuration-tag-sets>` the
 members of replica sets and use the resulting tag sets to create custom write
-concerns. See :doc:`/tutorial/configure-replica-set-tag-sets` for
+concerns. See :ref:`replica-set-configuration-tag-sets` for
 information on configuring custom write concerns using tag sets.

source/core/security-users.txt

@@ -71,7 +71,7 @@ A user's name and authentication database serve as a unique identifier
 for that user. MongoDB associates a user with a unique ``userId`` upon
 creation in MongoDB. However, :ref:`LDAP managed users <security-ldap>`
 created on an LDAP server do not have an associated document in the
-:doc:`system.users </reference/system-users-collection>` collection, and
+:ref:`system.users <system-users>` collection, and
 therefore don't have a :data:`~admin.system.users.userId` field
 associated with them.
 

source/faq/diagnostics.txt

@@ -179,7 +179,7 @@ As a related problem, the system will split chunks only on
 inserts or updates, which means that if you configure sharding and do not
 continue to issue insert and update operations, the database will not
 create any chunks. You can either wait until your application inserts
-data *or* :doc:`split chunks manually </tutorial/split-chunks-in-sharded-cluster>`.
+data *or* :ref:`split chunks manually <split-chunks-sharded-cluster>`.
 
 Finally, if your shard key has a low :ref:`cardinality
 <sharding-shard-key-cardinality>`, MongoDB may not be able to create

source/reference/built-in-roles.txt

@@ -24,7 +24,7 @@ down to a collection level of granularity.
 
 Each of MongoDB's built-in roles defines access at the database level for all
 *non*-system collections in the role's database and at the collection level
-for all :doc:`system collections </reference/system-collections>`.
+for all :ref:`system collections <metadata-system-collections>`.
 
 MongoDB provides the built-in :ref:`database user <database-user-roles>` and
 :ref:`database administration <database-administration-roles>` roles on

source/reference/command/buildInfo.txt

@@ -98,7 +98,7 @@ These fields are stable and should provide consistent behavior.
 
 .. data:: buildInfo.storageEngines
 
-   A list of :doc:`storage engines </faq/storage>` available to the
+   A list of :ref:`storage engines <faq-storage>` available to the
    :binary:`~bin.mongod` server.
 
 .. data:: buildInfo.javascriptEngine

source/reference/command/serverStatus.txt

@@ -2086,7 +2086,7 @@ metrics
 .. serverstatus:: metrics.queryExecutor.collectionScans.nonTailable
 
    The number of queries that performed a collection scan that did not
-   use a :doc:`tailable cursor </core/tailable-cursors>`.
+   use a :ref:`tailable cursor <tailable-cursors-landing-page>`.
 
    .. versionadded:: 4.4
 
@@ -2354,7 +2354,7 @@ metrics
 .. serverstatus:: metrics.repl.syncSource
 
    Information on a replica set node's
-   :doc:`sync source selection </core/replica-set-sync/>` process.
+   :ref:`sync source selection <replica-set-sync>` process.
 
    .. versionadded:: 4.4
 

source/reference/operator/query/text.txt

@@ -20,7 +20,7 @@ Definition
 .. query:: $text
 
    :query:`$text` performs a text search on the content of the fields
-   indexed with a :doc:`text index </core/index-text>`. A
+   indexed with a :ref:`text index <index-feature-text>`. A
    :query:`$text` expression has the following syntax:
 
    .. code-block:: javascript

source/reference/system-collections.txt

@@ -1,7 +1,3 @@
-
-
-
-
 .. _metadata-system-collections:
 
 ==================

source/reference/system-users-collection.txt

@@ -1,3 +1,5 @@
+.. _system-users:
+
 ===========================
 ``system.users`` Collection
 ===========================

source/release-notes/4.4.txt

@@ -1336,7 +1336,7 @@ When creating a collection inside a transaction:
 
 - The :method:`db.createCollection()` method fails if 
   executed against a 
-  :doc:`system collection </reference/system-collections>`.
+  :ref:`system collection <metadata-system-collections>`.
 
 When :ref:`creating an index <transactions-operations-ddl-explicit>`
 inside a transaction:
@@ -1349,7 +1349,7 @@ inside a transaction:
 
 - The :method:`db.collection.createIndex()` method
   fails if executed against a 
-  :doc:`system collection </reference/system-collections>`.
+  :ref:`system collection <metadata-system-collections>`.
 
 For more details, see :ref:`transactions-create-collections-indexes`.
 

source/storage.txt

@@ -10,7 +10,7 @@ Storage
    :depth: 1
    :class: singlecol
 
-The :doc:`storage engine </core/storage-engines>` is the primary
+The :ref:`storage engine <storage-engines>` is the primary
 component of MongoDB responsible for managing data. MongoDB provides a
 variety of storage engines, allowing you to choose one most suited to
 your application.

source/tutorial/configure-replica-set-tag-sets.txt

@@ -1,6 +1,3 @@
-
-
-
 .. _replica-set-configuration-tag-sets:
 
 ==============================

source/tutorial/list-users.txt

@@ -13,7 +13,7 @@ List Users
    :class: singlecol
 
 To list all users, use :binary:`~bin.mongosh` to query the
-:doc:`system.users </reference/system-users-collection>` collection:
+:ref:`system.users <system-users>` collection:
 
 .. code-block:: sh