Skip to content

typo run #390

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.

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
Nov 12, 2012
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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/faq/developers.txt
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ storage utilization for these collections:

To optimize storage use, users can specify a value for the ``_id`` field
explicitly when inserting documents into the collection. This
stratgy allows applications to store a value in the ``_id`` field
strategy allows applications to store a value in the ``_id`` field
that would have occupied space in another portion of the document.

You can store any value in the ``_id`` field, but because this value
Expand Down
2 changes: 1 addition & 1 deletion source/reference/command/findAndModify.txt
Original file line number Diff line number Diff line change
Expand Up @@ -158,5 +158,5 @@ findAndModify

This command obtains a write lock on the affected database and
will block other operations until it has completed; however,
typically the write lock is short lived and equivelent to other
typically the write lock is short lived and equivalent to other
similar :method:`update() <db.collection.update()>` operations.
2 changes: 1 addition & 1 deletion source/release-notes/1.8.txt
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ those documents.
Journaling
``````````

Returning to 1.6 after using 1.8 :wiki:`journaliing <Journaling>` works
Returning to 1.6 after using 1.8 :wiki:`journaling <Journaling>` works
fine, as journaling does not change anything about the data file format.
Suppose you are running 1.8.x with journaling enabled and you decide to
switch back to 1.6. There are two scenarios:
Expand Down
4 changes: 2 additions & 2 deletions source/tutorial/aggregation-examples.txt
Original file line number Diff line number Diff line change
Expand Up @@ -539,7 +539,7 @@ Return Total Number of Joins per Month
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The following operation shows how many people joined each month of the
year. You might use this aggregated datause such information for recruiting and marketing
year. You might use this aggregated data for such information for recruiting and marketing
strategies.

.. code-block:: javascript
Expand Down Expand Up @@ -576,7 +576,7 @@ the following operations:
operator increments this field by 1 for every document containing
the given ``month_joined`` value.

- The :agg:pipeline:`$sorte` operator sorts the documents created by
- The :agg:pipeline:`$sort` operator sorts the documents created by
:agg:pipeline:`$group` according to the contents of the
``month_joined`` field.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -328,7 +328,7 @@ Enabling Sharding on the Database Level
```````````````````````````````````````

Issue the :dbcommand:`enableSharding` command. The following example
emables sharding on the "test" database:
enables sharding on the "test" database:

.. code-block:: javascript

Expand Down