DOCSP-26426 Replaces Compound-GeoJSON doc directives (#2156)

Author: jmd-mongo

source/administration/production-checklist-operations.txt

@@ -57,7 +57,7 @@ Replication
    - Verify that all non-hidden replica set members are identically
      provisioned in terms of their RAM, CPU, disk, network setup, etc.
 
-   - :doc:`Configure the oplog size </tutorial/change-oplog-size>` to
+   - :ref:`Configure the oplog size <tutorial-change-oplog-size>` to
      suit your use case:
 
      - The replication oplog window should cover normal maintenance and

source/administration/production-notes.txt

@@ -418,7 +418,7 @@ NUMA for use with MongoDB.
 
          You must use ``numactl`` to start each of your
          :binary:`~bin.mongod` instances, including all
-         :doc:`config servers </core/sharded-cluster-config-servers>`,
+         :ref:`config servers <sharding-config-server>`,
          :binary:`~bin.mongos` instances, and clients. Edit the default
          **systemd** service file for each as follows:
 
@@ -472,7 +472,7 @@ NUMA for use with MongoDB.
 
          You must use ``numactl`` to start each of your
          :binary:`~bin.mongod` instances, including all
-         :doc:`config servers </core/sharded-cluster-config-servers>`,
+         :ref:`config servers <sharding-config-server>`,
          :binary:`~bin.mongos` instances, and clients.
 
          #. Install ``numactl`` for your platform if not already

source/core/document.txt

@@ -72,7 +72,7 @@ Field Names
 
 Field names are strings.
 
-:doc:`Documents </core/document>` have the following restrictions on field
+:ref:`Documents <bson-document-format>` have the following restrictions on field
 names:
 
 - .. include:: /includes/fact-id-field-name-rules.rst

source/core/sharded-cluster-components.txt

@@ -28,7 +28,7 @@ A MongoDB :term:`sharded cluster` consists of the following components:
   can support :ref:`hedged reads <mongos-hedged-reads>` to minimize
   latencies.
 
-* :doc:`config servers </core/sharded-cluster-config-servers>`: Config
+* :ref:`config servers <sharding-config-server>`: Config
   servers store metadata and configuration settings for the cluster. As
   of MongoDB 3.4, config servers must be deployed as a replica set (CSRS).
 

source/includes/driver-examples/driver-example-update-52.rst

@@ -104,7 +104,7 @@
 
                Because |compass| does not support
                :update:`$currentDate` or any other
-               :doc:`Field Update Operators </reference/operator/update-field>`,
+               :ref:`Field Update Operators <field-update-operators>`,
                you must manually enter the date value in Compass.
 
      - id: python

source/includes/extracts-geojson-specification.yaml

@@ -43,7 +43,7 @@ content: |
       }
 
    For a list of the GeoJSON objects supported in MongoDB as well as
-   examples, see :doc:`GeoJSON objects </reference/geojson>`.
+   examples, see :ref:`GeoJSON objects <geospatial-indexes-store-geojson>`.
 
    .. include:: /includes/extracts/geojson-specification-query-calculation.rst
 ...

source/includes/fact-sharded-cluster-components.rst

@@ -8,7 +8,7 @@ A MongoDB :term:`sharded cluster` consists of the following components:
   query router, providing an interface between client applications and the
   sharded cluster.
 
-- :doc:`config servers </core/sharded-cluster-config-servers>`: Config
+- :ref:`config servers <sharding-config-server>`: Config
   servers store metadata and configuration settings for the cluster. As
   of MongoDB 3.4, config servers must be deployed as a replica set (CSRS).
 

source/includes/steps-deploy-geographically-distributed-replica-set-5member.yaml

@@ -57,7 +57,7 @@ content: |
    Alternatively, you can also specify the :setting:`replica set name
    <replication.replSetName>` and the :setting:`hostnames/ip
    addresses <net.bindIp>` in a
-   :doc:`configuration file </reference/configuration-options>`:
+   :ref:`configuration file <configuration-options>`:
 
    .. code-block:: yaml
 

source/includes/steps-run-mongodb-on-osx.yaml

@@ -57,7 +57,7 @@ pre: |
   from above, and the ``fork`` parameter to run :binary:`~bin.mongod`
   in the background. Alternatively, you may choose to store the values
   for ``dbpath``, ``logpath``, ``fork``, and many other parameters in a
-  :doc:`configuration file </reference/configuration-options>`.
+  :ref:`configuration file <configuration-options>`.
 action:
   - heading: Run ``mongod`` with command-line parameters
     pre: |
@@ -71,7 +71,7 @@ action:
     pre: |
       Run the :binary:`~bin.mongod` process at the system prompt,
       providing the path to a
-      :doc:`configuration file </reference/configuration-options>`
+      :ref:`configuration file <configuration-options>`
       with the ``config`` parameter:
     language: sh
     code: |

source/includes/steps-stop-sharded-cluster.yaml

@@ -29,7 +29,7 @@ ref: stop-servers
 content: |
 
    Run :method:`db.shutdownServer()` from the ``admin`` database on each
-   of the :doc:`config servers </core/sharded-cluster-config-servers>` to
+   of the :ref:`config servers <sharding-config-server>` to
    shutdown its :binary:`mongod <bin.mongod>` process. Shutdown all
    secondary members before shutting down the primary.
 

source/introduction.txt

@@ -63,7 +63,7 @@ Query API
 The MongoDB Query API supports :doc:`read and write
 operations (CRUD) </crud>` as well as:
 
-- :doc:`Data Aggregation </core/aggregation-pipeline>`
+- :ref:`Data Aggregation <aggregation-pipeline>`
 
 - :doc:`Text Search </text-search>` and :doc:`Geospatial Queries
   </tutorial/geospatial-tutorial>`.

source/reference/bson-types.txt

@@ -36,7 +36,7 @@ following table:
 To determine a field's type, see :ref:`check-types-in-shell`.
 
 If you convert BSON to JSON, see
-the :doc:`Extended JSON </reference/mongodb-extended-json>` reference.
+the :ref:`Extended JSON <mongodb-extended-json-v2>` reference.
 
 The following sections describe special considerations for particular
 BSON types.

source/reference/method/cursor.comment.txt

@@ -62,7 +62,7 @@ following diagnostic outputs:
 
 See :ref:`configure log verbosity <log-messages-configure-verbosity>` for the
 :binary:`~bin.mongod` log, the
-:doc:`Database Profiler tutorial </tutorial/manage-the-database-profiler>`, or
+:ref:`Database Profiler tutorial <database-profiler>`, or
 the :method:`db.currentOp()` command.
 
 Example

source/reference/method/db.getLogComponents.txt

@@ -90,7 +90,7 @@ verbosity settings. For example:
 To modify these settings, you can configure the
 :setting:`systemLog.verbosity` and
 ``systemLog.component.<name>.verbosity`` settings in the
-:doc:`configuration file </reference/configuration-options>` or set the
+:ref:`configuration file <configuration-options>` or set the
 :parameter:`logComponentVerbosity` parameter using the
 :dbcommand:`setParameter` command or use the :method:`db.setLogLevel()`
 method. For examples, see :ref:`log-messages-configure-verbosity`.

source/reference/mongodb-extended-json.txt

@@ -1,3 +1,5 @@
+.. _mongodb-extended-json-v2:
+
 ==========================
 MongoDB Extended JSON (v2)
 ==========================

source/reference/operator/update-field.txt

@@ -1,3 +1,6 @@
+.. _field-update-operators:
+
+
 ======================
 Field Update Operators
 ======================

source/reference/program/mongod.txt

@@ -672,7 +672,7 @@ Core Options
    The :option:`--shutdown` option cleanly and safely terminates the :program:`mongod`
    process. When invoking :program:`mongod` with this option you must set the
    :option:`--dbpath` option either directly or by way of the
-   :doc:`configuration file </reference/configuration-options>` and the
+   :ref:`configuration file <configuration-options>` and the
    :option:`--config` option.
 
    The :option:`--shutdown` option is available only on Linux systems.
@@ -1388,7 +1388,7 @@ Storage Options
    The directory where the :program:`mongod` instance stores its data.
 
    If using the default
-   :doc:`configuration file </reference/configuration-options>`
+   :ref:`Configuration File <configuration-options>`
    included with a package manager installation of MongoDB, the
    corresponding :setting:`storage.dbPath` setting uses a different
    default.

source/release-notes/2.6-compatibility.txt

@@ -933,7 +933,7 @@ outputs. This format follows the template
 ``YYYY-MM-DDTHH:mm:ss.mmm<+/-Offset>``. For example, ``2014-03-04T20:13:38.944-0500``.
 
 This change impacts all clients using
-:doc:`Extended JSON </reference/mongodb-extended-json>` in *Strict mode*, such as
+:ref:`Extended JSON <mongodb-extended-json-v2>` in *Strict mode*, such as
 :binary:`~bin.mongoexport`.
 
 .. _2.6-compatibility-other-resources:

source/release-notes/2.6.txt

@@ -509,7 +509,7 @@ Configuration Options YAML File Format
 
 MongoDB 2.6 supports a YAML-based configuration file format in addition
 to the previous configuration file format. See the documentation of
-the :doc:`Configuration File </reference/configuration-options>` for
+the :ref:`Configuration File <configuration-options>` for
 more information.
 
 Operational Changes

source/release-notes/3.2-compatibility.txt

@@ -38,7 +38,7 @@ storage engine setting either:
 
      mongod --storageEngine mmapv1
 
-- Or in a :doc:`configuration file </reference/configuration-options>`,
+- Or in a :ref:`configuration file <configuration-options>`,
   using the :setting:`storage.engine` setting:
 
   .. code-block:: yaml

source/release-notes/3.2.txt

@@ -464,7 +464,7 @@ engine setting either:
 
      mongod --storageEngine mmapv1
 
-- Or in a :doc:`configuration file </reference/configuration-options>`,
+- Or in a :ref:`Configuration File <configuration-options>`,
   using the :setting:`storage.engine` setting:
 
   .. code-block:: yaml

source/release-notes/4.4.txt

@@ -2449,21 +2449,21 @@ Improvements to ``explain`` Results
 
 Starting in version 4.4:
 
-- :doc:`Explain results </reference/explain-results/>` for commands run
+- :ref:`Explain results <explain-results>` for commands run
   on sharded clusters include a top-level :ref:`serverInfo <serverInfo>`
   object for the :binary:`~bin.mongos` in addition to the ``serverInfo``
   objects returned for each shard. This is also available in versions 
   4.2.2, 4.0.14, and 3.6.16.
 
-- :doc:`Explain results </reference/explain-results/>` include the
+- :ref:`Explain results <explain-results>` include the
   :ref:`serverInfo <serverInfo>` object when
   :data:`~explain.queryPlanner.optimizedPipeline` is ``true``. In
   previous versions of MongoDB, ``explain`` results would occasionally
   not include the ``serverInfo`` object when
   :data:`~explain.queryPlanner.optimizedPipeline` was ``true``. This is 
   also available in versions 4.2.2, 4.0.14, and 3.6.16.
 
-- :doc:`Explain results </reference/explain-results/>` for aggregation include 
+- :ref:`Explain results <explain-results>` for aggregation include 
   the :data:`nReturned <explain.executionStats.nReturned>` and 
   :data:`executionTimeMillisEstimate 
   <explain.executionStats.executionStages.executionTimeMillisEstimate>` fields 
@@ -2473,7 +2473,7 @@ Starting in version 4.4:
 
 .. seealso::
 
-   :doc:`Explain results </reference/explain-results/>`.
+   :ref:`Explain results <explain-results>`.
 
 ``comment`` Option Available to all Database Commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

source/sharding.txt

@@ -80,7 +80,7 @@ A MongoDB :term:`sharded cluster` consists of the following components:
   the sharded cluster. Starting in MongoDB 4.4, ``mongos`` can support
   :ref:`hedged reads <mongos-hedged-reads>` to minimize latencies.
 
-* :doc:`config servers </core/sharded-cluster-config-servers>`: Config
+* :ref:`config servers <sharding-config-server>`: Config
   servers store metadata and configuration settings for the cluster.
 
 The following graphic describes the interaction of components within a

source/tutorial/geospatial-tutorial.txt

@@ -109,7 +109,7 @@ figure:
 .. include:: /images/geospatial-single-point.rst
 
 Because the tutorial uses a ``2dsphere`` index, the geometry data in the
-``location`` field must follow the :doc:`GeoJSON format </reference/geojson>`.
+``location`` field must follow the :ref:`GeoJSON format <geospatial-indexes-store-geojson>`.
 
 Now inspect an entry in the ``neighborhoods`` collection:
 

source/tutorial/getting-started.txt

@@ -79,7 +79,7 @@ examples in the shell above.
 
       The following example uses the
       :method:`db.collection.insertMany()` method to insert new
-      :doc:`documents </core/document>` into the ``movies``
+      :ref:`documents <bson-document-format>` into the ``movies``
       collection. You can copy and paste the example into the
       :ref:`shell <mongo-web-shell>` above.
 

source/tutorial/restart-sharded-cluster.txt

@@ -18,7 +18,7 @@ This procedure demonstrates the shutdown and startup sequence for restarting
 a sharded cluster. Stopping or starting the components of a sharded cluster
 in a different order may cause communication errors between members. For
 example, :doc:`shard </core/sharded-cluster-shards>` servers may appear to hang
-if there are no :doc:`config servers </core/sharded-cluster-config-servers>`
+if there are no :ref:`config servers <sharding-config-server>`
 available.
 
 .. important:: This procedure should only be performed during a planned