Skip to content

Replace "nor" with "and" #2056

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

Replace "nor" with "and" #2056

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/includes/fact-limitation-one-geo-index-per-collection.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Member Author

@jmikola jmikola Oct 29, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is correct, as the neither/nor agreement appears later in the sentence -- not in this clause.

: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.
Expand Down