(DOCSP-26418): Replace remaining 2d inline doc directives (#2213)

* replace doc directives

* fix build errors

* small fixes

* tech review feedback

Author: davidhou17

source/core/geohaystack.txt

@@ -21,8 +21,8 @@ results over small areas. ``geoHaystack`` indexes improve performance
 on queries that use flat geometry.
 
 For queries that use spherical geometry, a **2dsphere index is a better
-option** than a haystack index. :doc:`2dsphere indexes
-</core/2dsphere>` allow field reordering; ``geoHaystack`` indexes
+option** than a haystack index. :ref:`2dsphere indexes
+<2dsphere-index>` allow field reordering; ``geoHaystack`` indexes
 require the first field to be the location field. Also, ``geoHaystack``
 indexes are only usable via commands and so always return all results
 at once.

source/core/index-creation.txt

@@ -413,7 +413,7 @@ process:
         indexed fields. For example, a document with duplicate field
         values when building a :ref:`unique index <index-type-unique>`
         *or* malformed :ref:`GeoJSON objects <geospatial-geojson>` when
-        building a :doc:`2dsphere index </core/2dsphere>`.
+        building a :ref:`2dsphere index <2dsphere-index>`.
 
   * - Lock
 

source/includes/extracts-4.4-changes.yaml

@@ -331,7 +331,7 @@ content: |
 ref: 4.4-changes-geo-deprecation
 content: |
    MongoDB 4.4 deprecates the :doc:`geoHaystack </core/geohaystack>` index and the
-   :dbcommand:`geoSearch` command.  Use a :doc:`2d index </core/2d>`
+   :dbcommand:`geoSearch` command.  Use a :ref:`2d index <2d-index>`
    with :pipeline:`$geoNear` or :query:`$geoWithin` instead.
 ---
 ref: 4.4-changes-index-builds-simultaneous-fcv

source/includes/extracts-geonear-facts.yaml

@@ -21,6 +21,6 @@ content: |
 ---
 ref: geoNear-stage-index-requirement
 content: |
-   :pipeline:`$geoNear` requires a :doc:`geospatial index
-   </core/geospatial-indexes>`.
+   :pipeline:`$geoNear` requires a :ref:`geospatial index
+   <index-feature-geospatial>`.
 ...

source/includes/fact-5.0-geohaystack-removed.rst

@@ -1,6 +1,6 @@
 MongoDB 5.0 removes the deprecated :doc:`geoHaystack
 </core/geohaystack>` index and :dbcommand:`geoSearch` command. Use a
-:doc:`2d index </core/2d>` with :pipeline:`$geoNear` or one of the
+:ref:`2d index <2d-index>` with :pipeline:`$geoNear` or one of the
 supported :ref:`geospatial query operators <geospatial-query-selectors>`
 instead.
 

source/indexes.txt

@@ -169,11 +169,11 @@ Geospatial Index
 ~~~~~~~~~~~~~~~~
 
 To support efficient queries of geospatial coordinate data, MongoDB
-provides two special indexes: :doc:`2d indexes </core/2d>` that uses
-planar geometry when returning results and :doc:`2dsphere indexes
-</core/2dsphere>` that use spherical geometry to return results.
+provides two special indexes: :ref:`2d indexes <2d-index>` that uses
+planar geometry when returning results and :ref:`2dsphere indexes
+<2dsphere-index>` that use spherical geometry to return results.
 
-See :doc:`/core/geospatial-indexes` for a high level introduction to
+See :ref:`index-feature-geospatial` for a high level introduction to
 geospatial indexes.
 
 Text Indexes

source/reference/limits.txt

@@ -422,7 +422,7 @@ Operations
 
       - :query:`$or`
 
-      - :doc:`/core/geospatial-indexes`
+      - :ref:`2d-index-internals`
 
 .. limit:: Geospatial Queries
 

source/reference/operator/aggregation/geoNear.txt

@@ -426,8 +426,8 @@ The aggregation returns a document with:
 Specify Which Geospatial Index to Use
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Consider a ``places`` collection that has a :doc:`2dsphere
-</core/2dsphere>` index on the ``location`` field and a
+Consider a ``places`` collection that has a :ref:`2dsphere
+<2dsphere-index>` index on the ``location`` field and a
 :ref:`2d <2d-index>` index on the ``legacy`` field.
 
 A document in the ``places`` collection resembles the following:

source/reference/operator/query-geospatial.txt

@@ -41,25 +41,23 @@ Query Selectors
    * - :query:`$geoWithin`
 
      - Selects geometries within a bounding :ref:`GeoJSON geometry
-       <geospatial-indexes-store-geojson>`. The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
+       <geospatial-indexes-store-geojson>`. The :ref:`2dsphere
+       <2dsphere-index>` and :ref:`2d <2d-index>` indexes support
        :query:`$geoWithin`.
 
 
    * - :query:`$near`
 
      - Returns geospatial objects in proximity to a point.
-       Requires a geospatial index.  The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
-       :query:`$near`.
+       Requires a geospatial index. The ``2dsphere``
+       and ``2d`` indexes support :query:`$near`.
 
 
    * - :query:`$nearSphere`
 
      - Returns geospatial objects in proximity to a point on a sphere.
-       Requires a geospatial index.  The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
-       :query:`$nearSphere`.
+       Requires a geospatial index. The ``2dsphere``
+       and ``2d`` indexes support :query:`$nearSphere`.
 
 
 
@@ -86,15 +84,15 @@ Geometry Specifiers
    * - :query:`$box`
 
      - Specifies a rectangular box using legacy coordinate pairs for
-       :query:`$geoWithin` queries. The :ref:`2d <2d-index>` index supports
-       :query:`$box`.
+       :query:`$geoWithin` queries. The :ref:`2d <2d-index>` index
+       supports :query:`$box`.
 
 
    * - :query:`$center`
 
      - Specifies a circle using legacy coordinate pairs to
-       :query:`$geoWithin` queries when using planar geometry. The :doc:`2d
-       </core/2d>` index supports :query:`$center`.
+       :query:`$geoWithin` queries when using planar geometry. The
+       ``2d`` index supports :query:`$center`.
 
 
    * - :query:`$centerSphere`
@@ -112,9 +110,8 @@ Geometry Specifiers
    * - :query:`$maxDistance`
 
      - Specifies a maximum distance to limit the results of :query:`$near`
-       and :query:`$nearSphere` queries. The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
-       :query:`$maxDistance`.
+       and :query:`$nearSphere` queries. The ``2dsphere``
+       and ``2d`` indexes support :query:`$maxDistance`.
 
 
    * - :query:`$minDistance`
@@ -127,7 +124,7 @@ Geometry Specifiers
    * - :query:`$polygon`
 
      - Specifies a polygon to using legacy coordinate pairs for
-       :query:`$geoWithin` queries. The :ref:`2d <2d-index>` index supports
+       :query:`$geoWithin` queries. The ``2d`` index supports
        :query:`$center`.
 
 .. toctree::

source/reference/operator/query.txt

@@ -195,24 +195,24 @@ Geospatial
    * - :query:`$geoWithin`
 
      - Selects geometries within a bounding :ref:`GeoJSON geometry
-       <geospatial-indexes-store-geojson>`. The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
+       <geospatial-indexes-store-geojson>`. The :ref:`2dsphere
+       <2dsphere-index>` and :ref:`2d <2d-index>` indexes support
        :query:`$geoWithin`.
 
 
    * - :query:`$near`
 
      - Returns geospatial objects in proximity to a point.
-       Requires a geospatial index.  The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
+       Requires a geospatial index.  The :ref:`2dsphere
+       <2dsphere-index>` and :ref:`2d <2d-index>` indexes support
        :query:`$near`.
 
 
    * - :query:`$nearSphere`
 
      - Returns geospatial objects in proximity to a point on a sphere.
-       Requires a geospatial index.  The :doc:`2dsphere
-       </core/2dsphere>` and :ref:`2d <2d-index>` indexes support
+       Requires a geospatial index.  The :ref:`2dsphere
+       <2dsphere-index>` and :ref:`2d <2d-index>` indexes support
        :query:`$nearSphere`.
 
 

source/reference/operator/query/geoWithin.txt

@@ -104,8 +104,8 @@ Geospatial Indexes
 ~~~~~~~~~~~~~~~~~~
 
 :query:`$geoWithin` does not require a geospatial index. However, a
-geospatial index will improve query performance. Both :doc:`2dsphere
-</core/2dsphere>` and :ref:`2d <2d-index>` geospatial indexes support
+geospatial index will improve query performance. Both :ref:`2dsphere
+<2dsphere-index>` and :ref:`2d <2d-index>` geospatial indexes support
 :query:`$geoWithin`.
 
 Unsorted Results

source/reference/operator/query/near.txt

@@ -22,7 +22,7 @@ Definition
    :query:`$near` requires a geospatial index:
 
    - :ref:`2dsphere <2dsphere-index>` index if specifying a
-     :term:`GeoJSON` point,
+     :term:`GeoJSON` point.
 
    - :ref:`2d <2d-index>` index if specifying a point using legacy
      coordinates.

source/reference/operator/query/nearSphere.txt

@@ -22,10 +22,10 @@ Definition
    :query:`$nearSphere` *requires* a geospatial index:
 
    - :ref:`2dsphere <2dsphere-index>` index for location data defined
-     as GeoJSON points
+     as GeoJSON points.
 
    - :ref:`2d <2d-index>` index for location data defined as legacy
-     coordinate pairs. To use a :ref:`2d <2d-index>` index on
+     coordinate pairs. To use a ``2d`` index on
      :ref:`GeoJSON points <geojson-point>`, create the index on the
      ``coordinates`` field of the GeoJSON object.
 
@@ -114,8 +114,8 @@ Specify Center Point Using Legacy Coordinates
 ````````````
 
 Consider a collection ``legacyPlaces`` that contains documents with
-legacy coordinates pairs in the ``location`` field and has a :doc:`2d
-</core/2d>` index.
+legacy coordinates pairs in the ``location`` field and has a :ref:`2d
+<2d-index>` index.
 
 Then, the following example returns those documents whose ``location``
 is at most ``0.10`` radians from the specified point, ordered from

source/release-notes/1.2.txt

@@ -1,3 +1,5 @@
+.. _release-notes-1.2:
+
 ===============================
 Release Notes for MongoDB 1.2.x
 ===============================

source/release-notes/1.4.txt

@@ -16,7 +16,7 @@ Upgrading
 We're pleased to announce the 1.4 release of MongoDB. 1.4 is a drop-in
 replacement for 1.2. To upgrade you just need to shutdown
 :binary:`~bin.mongod`, then restart with the new binaries. (Users upgrading
-from release 1.0 should review the :doc:`1.2 release notes </release-notes/1.2>`,
+from release 1.0 should review the :ref:`1.2 release notes <release-notes-1.2>`,
 in particular the instructions for upgrading the DB format.)
 
 Release 1.4 includes the following improvements over release 1.2:

source/release-notes/2.4.txt

@@ -229,7 +229,7 @@ Add support for text search of content in MongoDB databases as a
 Geospatial Support Enhancements
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- Add new :doc:`2dsphere index </core/2dsphere>`. The new index
+- Add new :ref:`2dsphere index <2dsphere-index>`. The new index
   supports `GeoJSON <https://tools.ietf.org/html/rfc7946>`_ objects
   ``Point``, ``LineString``, and ``Polygon``. See
   :doc:`/core/2dsphere` and :doc:`/geospatial-queries`.

source/release-notes/2.6-compatibility.txt

@@ -381,8 +381,8 @@ Solution
 ----------------------------
 
 Description
-   MongoDB 2.6 introduces a version 2 of the :doc:`2dsphere index
-   </core/2dsphere>`. If a document lacks a ``2dsphere``
+   MongoDB 2.6 introduces a version 2 of the :ref:`2dsphere index
+   <2dsphere-index>`. If a document lacks a ``2dsphere``
    index field (or the field is ``null`` or an empty array), MongoDB
    does not add an entry for the document to the ``2dsphere`` index.
    For inserts, MongoDB inserts the document but does not add to the

source/release-notes/3.2.txt

@@ -1223,13 +1223,12 @@ The diagnostic logs and the system profiler report on this statistic.
 Geospatial Optimization
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-MongoDB 3.2 introduces version 3 of :doc:`2dsphere
-indexes </core/2dsphere>`, which index :doc:`GeoJSON geometries
-</reference/geojson>` at a finer gradation. The new version improves
-performance of :doc:`2dsphere index </core/2dsphere>` queries over
-smaller regions. In addition, for both :doc:`2d indexes </core/2d>` and
-:doc:`2dsphere indexes </core/2dsphere>`, the performance of
-geoNear queries has been improved for dense datasets.
+MongoDB 3.2 introduces version 3 of :ref:`2dsphere-index`, which index
+:doc:`GeoJSON geometries </reference/geojson>` at a finer gradation. The
+new version improves performance of ``2dsphere`` index queries over
+smaller regions. In addition, for both :ref:`2d-index` and ``2dsphere`` 
+indexes, the performance of geoNear queries has been improved for dense 
+datasets.
 
 .. seealso::
 

source/release-notes/4.0.txt

@@ -1495,8 +1495,8 @@ Geospatial Query Improvements
 - As of MongoDB 4.0, the :pipeline:`$geoNear` aggregation operator and
   ``geoNear`` command support using the ``minDistance`` option
   with :ref:`2d <2d-index>` indexes. Similarly, :query:`$near` and
-  :query:`$nearSphere` support the ``$minDistance`` option for :doc:`2d
-  </core/2d>` indexes. Previously, ``minDistance`` and ``$minDistance``
+  :query:`$nearSphere` support the ``$minDistance`` option for :ref:`2d
+  <2d-index>` indexes. Previously, ``minDistance`` and ``$minDistance``
   were only available for :ref:`2dsphere <2dsphere-index>` indexes.
 
 - MongoDB 4.0 adds a ``key`` option for the :pipeline:`$geoNear`

source/release-notes/5.0-compatibility.txt

@@ -107,7 +107,7 @@ Removed Index Types
 -------------------
 
 MongoDB 5.0 removes the deprecated :doc:`geoHaystack
-</core/geohaystack>` index. Use a :doc:`2d index </core/2d>` instead.
+</core/geohaystack>` index. Use a :ref:`2d index <2d-index>` instead.
 
 Upgrading your MongoDB instance to 5.0 and setting
 :ref:`featureCompatibilityVersion <view-fcv>` to ``5.0`` will delete any

source/release-notes/6.0.txt

@@ -774,7 +774,7 @@ Additional Secondary Index Types
 
 You can add additional :term:`secondary index <secondary index>` types
 to time series collections, including :ref:`2dsphere <2dsphere-index>`
-and :doc:`2d </core/2d>` indexes.
+and :ref:`2d <2d-index>` indexes.
 
 For all additional indexes and other improvements, see
 :ref:`timeseries-add-secondary-index-mongodb-6.0`.