DOCSP-26193 replaces 2d and 2dsphere index doc admonitions (#2082)

* DOCSP-26193 replaces 2d and 2dsphere index doc admonitions

* internal review feedback

Author: jmd-mongo

source/core/2d.txt

@@ -36,7 +36,7 @@ Considerations
 Do not use a ``2d`` index if your location data includes GeoJSON
 objects. To index on both :ref:`legacy coordinate pairs
 <geospatial-legacy>` *and* :ref:`GeoJSON objects <geospatial-geojson>`,
-use a :doc:`2dsphere </core/2dsphere>` index.
+use a :ref:`2dsphere <2dsphere-index>` index.
 
 .. include:: /includes/extracts/geospatial-index-shard-key-restriction-2d.rst
 

source/core/2dsphere.txt

@@ -88,7 +88,7 @@ Considerations
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. |first-geo-index| replace:: ``2dsphere`` index
-.. |second-geo-index| replace:: :doc:`2d </core/2d>` index
+.. |second-geo-index| replace:: :ref:`2d <2d-index>` index
 .. include:: /includes/fact-limitation-one-geo-index-per-collection.rst
 
 Shard Key Restrictions
@@ -113,7 +113,7 @@ Create a ``2dsphere`` Index
 
 .. include:: /includes/create-2dsphere-index.rst
 
-Unlike a compound :doc:`2d </core/2d>` index which can reference one
+Unlike a compound :ref:`2d <2d-index>` index which can reference one
 location field and one other field, a :ref:`compound
 <index-type-compound>` ``2dsphere`` index can reference multiple
 location and non-location fields.
@@ -140,8 +140,8 @@ documents that store location data as :ref:`GeoJSON Point
 Create a ``2dsphere`` Index
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The following operation creates a :doc:`2dsphere </core/2dsphere>`
-index on the location field ``loc``:
+The following operation creates a ``2dsphere`` index on the location 
+field ``loc``:
 
 .. code-block:: javascript
 
@@ -162,7 +162,7 @@ respectively.
 
    db.places.createIndex( { loc : "2dsphere" , category : -1, name: 1 } )
 
-Unlike the :doc:`2d </core/2d>` index, a compound ``2dsphere`` index
+Unlike the ``2d`` index, a compound ``2dsphere`` index
 does not require the location field to be the first field indexed. For
 example:
 

source/core/geospatial-indexes.txt

@@ -64,7 +64,7 @@ Multi-location Documents for ``2d`` Indexes
 -------------------------------------------
 
 .. note::
-   :doc:`2dsphere </core/2dsphere>` indexes can cover multiple geospatial fields
+   :ref:`2dsphere <2dsphere-index>` indexes can cover multiple geospatial fields
    in a document, and can express lists of points using
    :ref:`geojson-multipoint` embedded documents.
 

source/core/index-sparse.txt

@@ -77,9 +77,9 @@ behavior.
 Indexes that are ``sparse`` by Default
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-:ref:`2dsphere (version 2) <2dsphere-v2>`, :doc:`2d </core/2d>`,
-:doc:`geoHaystack </core/geohaystack>`, and :doc:`text
-</core/index-text>` indexes are always ``sparse``.
+:ref:`2dsphere (version 2) <2dsphere-v2>`, :ref:`2d <2d-index>`,
+:ref:`geoHaystack <index-geohaystack-index>`, and :ref:`text
+<index-feature-text>` indexes are always ``sparse``.
 
 ``sparse`` Compound Indexes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -89,16 +89,15 @@ ascending/descending index keys will index a document as long as the
 document contains at least one of the keys.
 
 For sparse compound indexes that contain a geospatial key (i.e.
-:doc:`2dsphere </core/2dsphere>`, :doc:`2d </core/2d>`, or
-:doc:`geoHaystack </core/geohaystack>` index keys) along with
-ascending/descending index key(s), only the existence of the geospatial
-field(s) in a document determine whether the index references the
-document.
-
-For sparse compound indexes that contain :ref:`text <index-feature-text>`
-index keys along with ascending/descending index keys, only the
-existence of the ``text`` index field(s) determine whether the index
-references a document.
+``2dsphere``, ``2d``, or ``geoHaystack`` index keys) along 
+with ascending/descending index key(s), only the existence of the 
+geospatial field(s) in a document determine whether the index 
+references the document.
+
+For sparse compound indexes that contain :ref:`text 
+<index-feature-text>` index keys along with ascending/descending index 
+keys, only the existence of the ``text`` index field(s) determine 
+whether the index references a document.
 
 .. _sparse-unique-index:
 

source/core/timeseries/timeseries-limitations.txt

@@ -87,7 +87,7 @@ Time Series Secondary Indexes with MongoDB 6.0 and Later
 Starting in MongoDB 6.0, you can add a :term:`secondary index <secondary
 index>` to any field.
 
-These index types are not supported:
+These index types aren't supported:
 
 - :ref:`Text indexes <index-feature-text>`
 - :ref:`2d indexes <2d-index>`

source/core/timeseries/timeseries-secondary-index.txt

@@ -293,7 +293,7 @@ Starting in MongoDB 6.0, you can:
 - Add a :term:`secondary index <secondary index>` to any field or
   subfield.
 
-- Use the ``metaField`` with :doc:`2dsphere </core/2dsphere>` indexes.
+- Use the ``metaField`` with :ref:`2dsphere <2dsphere-index>` indexes.
 
 .. note::
 

source/geospatial-queries.txt

@@ -28,7 +28,7 @@ GeoJSON Objects
 ~~~~~~~~~~~~~~~
 
 To calculate geometry over an Earth-like sphere, store your location
-data as :doc:`GeoJSON objects </reference/geojson>`.
+data as :ref:`GeoJSON objects <geospatial-indexes-store-geojson>`.
 
 .. include:: /includes/extracts/geojson-specification-geospatial.rst
 
@@ -58,20 +58,20 @@ geospatial queries.
 ``2dsphere``
 ~~~~~~~~~~~~
 
-:doc:`2dsphere </core/2dsphere>` indexes support queries that calculate
+:ref:`2dsphere <2dsphere-index>` indexes support queries that calculate
 :ref:`geometries on an earth-like sphere <geospatial-geometry>`.
 
 .. include:: /includes/create-2dsphere-index.rst
 
 For more information on the ``2dsphere`` index, see
-:doc:`/core/2dsphere`.
+:ref:`<2dsphere-index>`.
 
 .. _geo-2d:
 
 ``2d``
 ~~~~~~
 
-:doc:`2d </core/2d>` indexes support queries that calculate
+:ref:`2d <2d-index>` indexes support queries that calculate
 :ref:`geometries on a two-dimensional plane <geospatial-geometry>`.
 Although the index can support :query:`$nearSphere` queries that
 calculate on a sphere, if possible, use the :ref:`geo-2dsphere` index
@@ -128,32 +128,28 @@ MongoDB provides the following geospatial query operators:
    * - :query:`$geoIntersects`
 
      - Selects geometries that intersect with a :term:`GeoJSON` geometry.
-       The :doc:`2dsphere </core/2dsphere>` index supports
-       :query:`$geoIntersects`.
+       The ``2dsphere`` index supports :query:`$geoIntersects`.
 
 
    * - :query:`$geoWithin`
 
      - Selects geometries within a bounding :ref:`GeoJSON geometry
-       <geospatial-indexes-store-geojson>`. The :doc:`2dsphere
-       </core/2dsphere>` and :doc:`2d </core/2d>` indexes support
-       :query:`$geoWithin`.
+       <geospatial-indexes-store-geojson>`. The ``2dsphere`` and 
+       ``2d`` indexes support :query:`$geoWithin`.
 
 
    * - :query:`$near`
 
      - Returns geospatial objects in proximity to a point.
-       Requires a geospatial index.  The :doc:`2dsphere
-       </core/2dsphere>` and :doc:`2d </core/2d>` 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 :doc:`2d </core/2d>` indexes support
-       :query:`$nearSphere`.
+       Requires a geospatial index.  The ``2dsphere`` and ``2d`` indexes 
+       support :query:`$nearSphere`.
 
 
 
@@ -162,8 +158,8 @@ For more details, including examples, see the individual reference page.
 Geospatial Aggregation Stage
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-MongoDB provides the following geospatial :doc:`aggregation pipeline
-stage </core/aggregation-pipeline>`:
+MongoDB provides the following geospatial :ref:`aggregation pipeline
+stage <aggregation-pipeline>`:
 
 .. list-table::
    :header-rows: 1

source/includes/example-nearSphere-minDistance.rst

@@ -1,5 +1,5 @@
 Consider a collection ``places`` that contains documents with a
-``location`` field and has a :doc:`2dsphere </core/2dsphere>` index.
+``location`` field and has a :ref:`2dsphere <2dsphere-index>` index.
 
 Then, the following example returns whose ``location`` is at least
 ``1000`` meters from and at most ``5000`` meters from the specified

source/includes/extracts-collation.yaml

@@ -183,7 +183,7 @@ content: |
 
    - :ref:`text <index-feature-text>` indexes, 
 
-   - :doc:`2d </core/2d>` indexes, and 
+   - :ref:`2d <2d-index>` indexes, and 
 
    - :doc:`geoHaystack </core/geohaystack>` indexes.
 

source/includes/geo-data-limit-for-2dsphere.rst

@@ -1,4 +1,4 @@
-Fields with :doc:`2dsphere </core/2dsphere>` indexes must hold geometry
+Fields with :ref:`2dsphere <2dsphere-index>` indexes must hold geometry
 data in the form of :term:`coordinate pairs <legacy coordinate pairs>`
 or :term:`GeoJSON` data. If you attempt to insert a document with
 non-geometry data in a ``2dsphere`` indexed field, or build a