diff --git a/source/administration/indexes.txt b/source/administration/indexes.txt index 0eb95cfcb8f..f46a9718aef 100644 --- a/source/administration/indexes.txt +++ b/source/administration/indexes.txt @@ -101,7 +101,7 @@ Special Creation Options .. note:: - To create geospatial indexes, see :ref:`geospatial-indexes_create`. + To create geospatial indexes, see :ref:`geospatial-indexes-create`. .. index:: index; sparse .. _index-sparse-index: diff --git a/source/core/geospatial-indexes.txt b/source/core/geospatial-indexes.txt index 0d17fadf42e..5fb964fbf78 100644 --- a/source/core/geospatial-indexes.txt +++ b/source/core/geospatial-indexes.txt @@ -45,10 +45,10 @@ document with two fields. Consider the following two examples: All documents must store location data in the same order. If you use latitude and longitude as your coordinate system, always store longitude first. MongoDB's :ref:`2d spherical index operators -` only recognize ``[ longitude, latitude -]`` ordering. +` only recognize ``[ longitude, latitude]`` +ordering. -.. _geospatial-indexes_create: +.. _geospatial-indexes-create: Create a Geospatial Index -------------------------