Skip to content

fixed syntax in a link #689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

fixed syntax in a link #689

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/administration/indexes.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
6 changes: 3 additions & 3 deletions source/core/geospatial-indexes.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<geospatial-indexes-spherical>` only recognize ``[ longitude, latitude
]`` ordering.
<geospatial-indexes-spherical>` only recognize ``[ longitude, latitude]``
ordering.

.. _geospatial-indexes_create:
.. _geospatial-indexes-create:

Create a Geospatial Index
-------------------------
Expand Down