DOCSP-41298-Geospatial-indexes-covering (#8325) (#8480)

* DOCSP-41298-Geospatial-indexes-covering

* Reverting an edit.

* Responding to internal feedback, minor edit.

* Responding to external feedback, removing irrelevant link, small edit.

(cherry picked from commit 1cff141)

# Conflicts:
#	source/core/indexes/index-types/index-geospatial.txt

Author: mmaville-mdb

source/core/query-optimization.txt

@@ -92,10 +92,9 @@ index use <regex-index-use>`.
 Covered Query
 -------------
 
-A covered query is a query that can be satisfied entirely using an index
-and does not have to examine any documents. An index
-:ref:`covers <indexes-covered-queries>` a query when all of the
-following apply:
+A covered query is a query that can be satisfied entirely using an 
+index and does not have to examine any documents. An index covers a 
+query when all of the following apply:
 
 - all the fields in the :ref:`query <read-operations-query-document>`
   are part of an index, **and**
@@ -205,8 +204,6 @@ To determine whether a query is a covered query, use the
 :method:`db.collection.explain()` or the :method:`~cursor.explain()`
 method and review the :ref:`results <explain-output-covered-queries>`.
 
-For more information see :ref:`indexes-measuring-use`.
-
 .. toctree::
    :titlesonly:
    :hidden:

source/reference/explain-results.txt

@@ -915,10 +915,11 @@ For more information on execution statistics of collection scans, see
 Covered Queries
 ---------------
 
-When an index covers a query, MongoDB can both match the query
-conditions **and** return the results using only the index keys; i.e.
-MongoDB does not need to examine documents from the collection to
-return the results.
+When an index :ref:`covers <indexes-covered-queries>` a query, 
+MongoDB can both match the query conditions **and** return the 
+results using only the index keys. MongoDB does not need to 
+examine documents from the collection to to perform any part of the 
+query.
 
 When an index covers a query, the explain result has an ``IXSCAN``
 stage that is **not** a descendant of a ``FETCH`` stage, and in the