Skip to content

Fix misspellings of "pipeline" on "Aggregation Framework" page #167

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

Merged
merged 1 commit into from
Aug 31, 2012
Merged

Fix misspellings of "pipeline" on "Aggregation Framework" page #167

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
4 changes: 2 additions & 2 deletions source/applications/aggregation.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ documents.
All pipeline operators process a stream of documents and the
pipeline behaves as if the operation scans a :term:`collection` and
passes all matching documents into the "top" of the pipeline.
Each operator in the pipleine transforms each document as it passes
Each operator in the pipeline transforms each document as it passes
through the pipeline.

.. note::
Expand Down Expand Up @@ -201,7 +201,7 @@ to scan only the matching documents in a collection.
.. operator in front of the :agg:pipeline:`$project`.

In future versions there may be an optimization phase in the
pipleine that reorders the operations to increase performance without
pipeline that reorders the operations to increase performance without
affecting the result. However, at this time place
:agg:pipeline:`$match` operators at the beginning of the pipeline when
possible.
Expand Down