DOCS-15596 Revises Sort for $near and $nearSphere (#2577) (#2590)

* DOCS-15596 Adds section on / in aggregation pipelines

* Adjusts include text

* Adjusts include text

* Fixes build

* Fixe per Maddie Zechar

* Fixes per Maddie

* Fixes per Maddie

* Fixes per Dave

* Fixes per Dave

* Fixes per Dave

* Fixes per Dave

Author: kennethdyer

source/includes/example-near-minDistance.rst

@@ -1,6 +1,4 @@
-.. important::
-
-   .. include::  /includes/extracts/geospatial-long-lat-values.rst
+.. include::  /includes/extracts/geospatial-long-lat-values.rst
 
 Consider a collection ``places`` that has a ``2dsphere`` index.
 

source/includes/fact-geo-near-returns-sorted-results.rst

@@ -1,7 +1,14 @@
-|geo-operation| sorts documents by distance. If you also include a
-:method:`~cursor.sort()` for the query, :method:`~cursor.sort()`
-re-orders the matching documents, effectively overriding the sort
-operation already performed by |geo-operation|. When using
-:method:`~cursor.sort()` with geospatial queries, consider using
-:query:`$geoWithin` operator, which does not sort documents, instead of
-|geo-operation|.
+The |geo-operation| operator sorts documents by distance.
+
+- If you use the :method:`~cursor.sort` method in your query,
+  MongoDB performs a second sort operation, re-ordering the matching
+  documents.  When querying large collections, this can negatively 
+  affect query performance.
+
+- If the order of the documents is not important to you, consider
+  using the :query:`$geoWithin` operator instead, as it returns 
+  unsorted results.
+
+- |geo-operation| is a Match Execution operator and is not
+  permitted in aggregation pipelines.
+

source/reference/operator/query/near.txt

@@ -98,7 +98,6 @@ Sort Operation
 
    :ref:`3.0-geo-near-compatibility`
 
-
 Examples
 --------
 

source/reference/operator/query/nearSphere.txt

@@ -99,6 +99,7 @@ Sort Operation
 
 .. |geo-operation| replace:: :query:`$nearSphere`
 
+
 Examples
 --------