DOCSP-26448 Replace Text Indexes-YAML Docs (#2292)

lindseymoore · web-flow · commit 080523a4ebda · 2022-12-20T16:21:47.000-05:00
* DOCSP-26448 replace docs * fix broken ref * fix another broken ref * removed extra link
diff --git a/source/core/data-model-operations.txt b/source/core/data-model-operations.txt
@@ -245,7 +245,7 @@ Data Lifecycle Management
 Data modeling decisions should take data lifecycle management into
 consideration.
 
-The :doc:`Time to Live or TTL feature </tutorial/expire-data>` of
+The :ref:`Time to Live or TTL feature <ttl-collections>` of
 collections expires documents after a period of time. Consider using
 the TTL feature if your application requires some data to persist in
 the database for a limited period of time.
diff --git a/source/core/index-creation.txt b/source/core/index-creation.txt
@@ -72,7 +72,7 @@ Constraint Violations During Index Build
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 For indexes that enforce constraints on the collection, such as
-:doc:`unique </core/index-unique>` indexes, the :binary:`~bin.mongod`
+:ref:`unique <index-type-unique>` indexes, the :binary:`~bin.mongod`
 checks all pre-existing and concurrently-written documents for
 violations of those constraints *after* the index build completes.
 Documents that violate the index constraints can exist during the index
diff --git a/source/core/index-multikey.txt b/source/core/index-multikey.txt
@@ -57,7 +57,7 @@ special rules. For details on multikey index bounds, see
 Unique Multikey Index
 ---------------------
 
-For :doc:`unique </core/index-unique>` indexes, the unique constraint
+For :ref:`unique <index-type-unique>` indexes, the unique constraint
 applies across separate documents in the collection rather than within
 a single document.
 
diff --git a/source/core/index-unique.txt b/source/core/index-unique.txt
@@ -248,7 +248,7 @@ You cannot specify a unique constraint on a :ref:`hashed index
 <index-type-hashed>`.
 
 For a ranged sharded collection, only the following indexes can be
-:doc:`unique </core/index-unique>`:
+:ref:`unique <index-type-unique>`:
 
 - the index on the shard key
 
diff --git a/source/core/inmemory.txt b/source/core/inmemory.txt
@@ -81,7 +81,7 @@ In-memory storage engine requires that all its data (including indexes,
 oplog if :binary:`~bin.mongod` instance is part of a replica set, etc.) must
 fit into the specified :option:`--inMemorySizeGB <mongod --inMemorySizeGB>` command-line option
 or :setting:`storage.inMemory.engineConfig.inMemorySizeGB` setting in
-the :doc:`YAML configuration file </reference/configuration-options>`.
+the :ref:`YAML configuration file <configuration-options>`.
 
 .. include:: /includes/fact-inmemory-storage-engine-default-ram.rst
 
diff --git a/source/core/journaling.txt b/source/core/journaling.txt
@@ -25,7 +25,7 @@ Journaling and the WiredTiger Storage Engine
    The *log* mentioned in this section refers to the WiredTiger
    write-ahead log (i.e. the journal) and not the MongoDB log file.
 
-:doc:`WiredTiger </core/wiredtiger>` uses :ref:`checkpoints
+:ref:`WiredTiger <storage-wiredtiger>` uses :ref:`checkpoints
 <storage-wiredtiger-checkpoints>` to provide a consistent view of data
 on disk and allow MongoDB to recover from the last checkpoint. However,
 if MongoDB exits unexpectedly in between checkpoints, journaling is
diff --git a/source/core/retryable-writes.txt b/source/core/retryable-writes.txt
@@ -30,7 +30,7 @@ Supported Deployment Topologies
 
 Supported Storage Engine
   Retryable writes require a storage engine supporting document-level
-  locking, such as the :doc:`WiredTiger </core/wiredtiger>` or
+  locking, such as the :ref:`WiredTiger <storage-wiredtiger>` or
   :doc:`in-memory </core/inmemory>` storage engines.
 
 3.6+ MongoDB Drivers
diff --git a/source/core/security-ldap.txt b/source/core/security-ldap.txt
@@ -350,7 +350,7 @@ file settings:
 
       Include any other configuration file settings required for your
       deployment. For complete documentation on configuration files, see
-      :doc:`YAML configuration file </reference/configuration-options>`.
+      :ref:`YAML configuration file <configuration-options>`.
 
 You need to create or update the ``saslauthd.conf`` file with the parameters
 appropriate for your LDAP server. Documenting ``saslauthd.conf`` is out
diff --git a/source/core/sharding-shard-key.txt b/source/core/sharding-shard-key.txt
@@ -61,7 +61,7 @@ uniqueness on the entire key combination and not individual components
 of the shard key.
 
 For a ranged sharded collection, only the following indexes can be
-:doc:`unique </core/index-unique>`:
+:ref:`unique <index-type-unique>`:
 
 - the index on the shard key
 
diff --git a/source/core/storage-engines.txt b/source/core/storage-engines.txt
@@ -24,7 +24,7 @@ applications.
    .. include:: /includes/fact-4.2-mmapv1-removed.rst
 
 |arrow| WiredTiger Storage Engine (*Default*)
-   :doc:`WiredTiger </core/wiredtiger>` is the default storage engine
+   :ref:`WiredTiger <storage-wiredtiger>` is the default storage engine
    starting in MongoDB 3.2. It is well-suited for most workloads and is
    recommended for new deployments. WiredTiger provides a
    document-level concurrency model, checkpointing, and compression,
diff --git a/source/core/transactions.txt b/source/core/transactions.txt
@@ -388,7 +388,7 @@ For a list of operations not supported in transactions, see
 
 .. seealso::
 
-   :doc:`Transactions and Operations Reference </core/transactions-operations>`
+   :ref:`Transactions and Operations Reference <transactions-operations-ref>`
 
 .. _transactions-create-collections-indexes:
 
@@ -499,7 +499,7 @@ Restricted Operations
 
    - :ref:`txn-prod-considerations-ddl`
 
-   - :doc:`Transactions and Operations Reference </core/transactions-operations>`
+   - :ref:`Transactions and Operations Reference <transactions-operations-ref>`
 
 Transactions and Sessions
 -------------------------
diff --git a/source/core/workload-isolation.txt b/source/core/workload-isolation.txt
@@ -53,7 +53,7 @@ documentation in the MongoDB Manual:
 - :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
+- :ref:`Write Concerns <write-concern>`, which controls
   how MongoDB ensures that write operations propagate to members of a
   replica set.
 
diff --git a/source/core/write-performance.txt b/source/core/write-performance.txt
@@ -80,7 +80,7 @@ performance:
   number of available I/O resources. Moving the journal to a
   separate device may increase the capacity for write operations.
 
-- If applications specify :doc:`write concerns </reference/write-concern>`
+- If applications specify :ref:`write concerns <write-concern>`
   that include the :writeconcern:`j option <j>`,
   :binary:`~bin.mongod` will decrease the duration between journal
   writes, which can increase the overall write load.
diff --git a/source/faq/concurrency.txt b/source/faq/concurrency.txt
@@ -115,7 +115,7 @@ also yield locks between individual document modifications in write
 operations that affect multiple documents.
 
 For storage engines supporting document level :term:`concurrency
-control`, such as :doc:`WiredTiger </core/wiredtiger>`, yielding is not
+control`, such as :ref:`WiredTiger <storage-wiredtiger>`, yielding is not
 necessary when accessing storage as the :term:`intent locks <intent
 lock>`, held at the global, database and collection level, do not block
 other readers and writers. However, operations will periodically yield,
diff --git a/source/includes/steps-3.2-downgrade-sharded-cluster-sccc.yaml b/source/includes/steps-3.2-downgrade-sharded-cluster-sccc.yaml
@@ -38,7 +38,7 @@ content: |
 
     Downgrade first ``confserver3``, then ``confserver2``, and lastly,
     ``confserver1``. If your :binary:`~bin.mongod` instance is using the
-    :doc:`WiredTiger </core/wiredtiger>` storage engine, you must
+    :ref:`WiredTiger <storage-wiredtiger>` storage engine, you must
     include the :option:`--storageEngine <mongod --storageEngine>` option (or
     :setting:`storage.engine` if using the configuration file) with the
     3.0 binary.
diff --git a/source/includes/steps-3.2-downgrade-sharded-cluster.yaml b/source/includes/steps-3.2-downgrade-sharded-cluster.yaml
@@ -239,7 +239,7 @@ content: |
 
   For each replica set shard, downgrade the :binary:`~bin.mongod` binaries
   and restart. If your :binary:`~bin.mongod` instance is using the
-  :doc:`WiredTiger </core/wiredtiger>` storage engine, you must include
+  :ref:`WiredTiger <storage-wiredtiger>` storage engine, you must include
   the :option:`--storageEngine <mongod --storageEngine>` option (or :setting:`storage.engine` if
   using the configuration file) with the 3.0 binary.
 
diff --git a/source/introduction.txt b/source/introduction.txt
@@ -67,7 +67,7 @@ operations (CRUD) <crud>` as well as:
 
 - :ref:`Data Aggregation <aggregation-pipeline>`
 
-- :doc:`Text Search </text-search>` and :doc:`Geospatial Queries
+- :ref:`Text Search <text-search>` and :doc:`Geospatial Queries
   </tutorial/geospatial-tutorial>`.
 
 .. seealso::
diff --git a/source/reference/method/db.collection.stats.txt b/source/reference/method/db.collection.stats.txt
@@ -175,7 +175,7 @@ index types.
 Unexpected Shutdown and Count
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-For MongoDB instances using the :doc:`WiredTiger </core/wiredtiger>`
+For MongoDB instances using the :ref:`WiredTiger <storage-wiredtiger>`
 storage engine, after an unclean shutdown, statistics on size and count
 may off by up to 1000 documents as reported by :dbcommand:`collStats`,
 :dbcommand:`dbStats`, :dbcommand:`count`. To restore the correct
diff --git a/source/reference/operator/aggregation/merge.txt b/source/reference/operator/aggregation/merge.txt
@@ -751,7 +751,7 @@ Restrictions
      - An aggregation pipeline cannot use :pipeline:`$merge` inside a
        :ref:`transaction <transactions-operations-crud>`.
 
-   * - :doc:`Time Series Collections </core/timeseries-collections>`
+   * - :ref:`Time Series Collections <manual-timeseries-landing>`
 
      - An aggregation pipeline cannot use :pipeline:`$merge` to output to
        a time series collection.
diff --git a/source/reference/operator/aggregation/out.txt b/source/reference/operator/aggregation/out.txt
@@ -238,7 +238,7 @@ Restrictions
      - An aggregation pipeline cannot use :pipeline:`$out` inside
        :ref:`transactions <transactions>`.
 
-   * - :doc:`Time Series Collections </core/timeseries-collections>`
+   * - :ref:`Time Series Collections <manual-timeseries-landing>`
 
      - An aggregation pipeline cannot use :pipeline:`$out` to output to
        a time series collection.
diff --git a/source/release-notes/3.0-upgrade.txt b/source/release-notes/3.0-upgrade.txt
@@ -44,7 +44,7 @@ authentication and authorization, your user data model ``authSchema``
 must be at least version 3. To verify the version of your existing
 ``authSchema``, see :ref:`legacy-auth-model-removed`. To upgrade your
 ``authSchema`` version, see
-:doc:`Upgrade Authorization Data </release-notes/2.6-upgrade-authorization>` for details.
+:ref:`Upgrade Authorization Data <2.6-upgrade-authorization-model>` for details.
 
 Preparedness
 ~~~~~~~~~~~~
diff --git a/source/text-search.txt b/source/text-search.txt
@@ -1,3 +1,5 @@
+.. _text-search:
+
 ===========
 Text Search
 ===========
@@ -43,8 +45,8 @@ string content. To perform text search, MongoDB uses a :ref:`text index
 
 To learn more about text search for on-premises deployments, see: 
       
-- :doc:`Text Indexes </core/link-text-indexes/>` 
-- :doc:`Text Search Operators </core/text-search-operators/>`
+- :ref:`Text Indexes <text-search-on-premises>` 
+- :ref:`Text Search Operators <text-search-operators-on-premises>`
 
 MongoDB also supports text search for various languages. See
 :doc:`/reference/text-search-languages` for a list of supported
diff --git a/source/tutorial/backup-with-filesystem-snapshots.txt b/source/tutorial/backup-with-filesystem-snapshots.txt
@@ -51,7 +51,7 @@ WiredTiger Storage Engine
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 MongoDB 3.2 added support for volume-level back up of MongoDB instances
-using the :doc:`WiredTiger </core/wiredtiger>` storage engine when
+using the :ref:`WiredTiger <storage-wiredtiger>` storage engine when
 the MongoDB instance's data files and journal files reside on separate
 volumes. However, to create a coherent backup, the database must be locked
 and all writes to the database must be suspended during the backup process.
@@ -75,7 +75,7 @@ disk: either to the :term:`journal` or to data files.
 If there are writes that are not on disk when the backup occurs, the backup
 will not reflect these changes. 
 
-For the :doc:`WiredTiger storage engine </core/wiredtiger>`, the data
+For the WiredTiger storage engine, the data
 files reflect a consistent state as of the last :ref:`checkpoint
 <storage-wiredtiger-checkpoints>`. Checkpoints occur with every 2 GB of
 data or every minute.
diff --git a/source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt b/source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt
@@ -19,7 +19,7 @@ Enforcing access control on a :term:`sharded cluster` requires configuring:
   :ref:`Internal Authentication<replica-set-security>`.
 
 - Security between connecting clients and the cluster using
-  :doc:`User Access Controls</core/authorization>`.
+  :ref:`User Access Controls<authorization>`.
 
 For this tutorial, each member of the sharded cluster *must* use the same
 internal authentication mechanism and settings. This means enforcing internal
diff --git a/source/tutorial/enforce-keyfile-access-control-in-existing-replica-set.txt b/source/tutorial/enforce-keyfile-access-control-in-existing-replica-set.txt
@@ -20,7 +20,7 @@ configuring:
   :ref:`Internal Authentication<replica-set-security>`, and
 
 - Security between connecting clients and the replica set using
-  :doc:`User Access Controls</core/authorization>`.
+  :ref:`User Access Controls<authorization>`.
 
 For this tutorial, each member of the replica set uses the same internal
 authentication mechanism and settings.
