DOCSP-28228 unnested important admonitions in geoInterect, geometry, and near (#2747)

jocelyn-mendez1 · web-flow · commit 9a59b1d63bea · 2023-03-22T13:49:10.000-04:00
diff --git a/source/reference/operator/query/geoIntersects.txt b/source/reference/operator/query/geoIntersects.txt
@@ -72,9 +72,8 @@ Definition
    :query:`$geoIntersects` with the MongoDB CRS is the same as with the
    default CRS. See also :ref:`geointersects-big-poly`.
 
-   .. important::
 
-      .. include::  /includes/extracts/geospatial-long-lat-values.rst
+   .. include::  /includes/extracts/geospatial-long-lat-values.rst
 
 Behavior
 --------
diff --git a/source/reference/operator/query/geometry.txt b/source/reference/operator/query/geometry.txt
@@ -47,6 +47,4 @@ $geometry
    The custom MongoDB coordinate reference system has a strict
    counter-clockwise winding order.
 
-   .. important::
-
-      .. include::  /includes/extracts/geospatial-long-lat-values.rst
+   .. include::  /includes/extracts/geospatial-long-lat-values.rst
diff --git a/source/reference/operator/query/near.txt b/source/reference/operator/query/near.txt
@@ -109,9 +109,7 @@ Query on GeoJSON Data
 Query on Legacy Coordinates
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. important::
-
-   .. include::  /includes/extracts/geospatial-long-lat-values.rst
+.. include::  /includes/extracts/geospatial-long-lat-values.rst
 
 Consider a collection ``legacy2d`` that has a ``2d`` index.
 
