From 280c220947b61c9df28e2fcd6d0e1c3d5fb13c3b Mon Sep 17 00:00:00 2001 From: Jeremy Mikola Date: Wed, 29 Oct 2014 11:04:24 -0700 Subject: [PATCH] Replace "nor" with "and" --- .../includes/fact-limitation-one-geo-index-per-collection.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/includes/fact-limitation-one-geo-index-per-collection.rst b/source/includes/fact-limitation-one-geo-index-per-collection.rst index 4ee08998389..fcdf1ac8059 100644 --- a/source/includes/fact-limitation-one-geo-index-per-collection.rst +++ b/source/includes/fact-limitation-one-geo-index-per-collection.rst @@ -6,7 +6,7 @@ stage require that a collection have *at most* only one multiple geospatial indexes. The geospatial index restriction for the :dbcommand:`geoNear` command -nor the :pipeline:`$geoNear` pipeline stage exists because neither the +and the :pipeline:`$geoNear` pipeline stage exists because neither the :dbcommand:`geoNear` command nor the :pipeline:`$geoNear` pipeline stage syntax includes the location field. As such, index selection among multiple ``2d`` indexes or ``2dsphere`` indexes is ambiguous.