Typo epc 0730

.gitignore

@@ -4,3 +4,4 @@ build/*
 \#*#
 *__pycache__*
 *.pyc
+*.bak

source/about.txt

@@ -11,7 +11,7 @@ About MongoDB
 
 MongoDB is a :term:`document`-oriented database management system
 designed for performance, horizontal scalability, high
-availability, and advanced queryabiliy. See the following :wiki:`wiki
+availability, and advanced queryability. See the following :wiki:`wiki
 pages <>` for more information about MongoDB:
 
 - :wiki:`Introduction`
@@ -65,7 +65,7 @@ via "|hardlink|" and you can always reference the commit of the
 current manual in the :hardlink:`release.txt` file.
 
 The most up-to-date, current, and stable version of the manual is
-always avalible at "http://docs.mongodb.org/manual/."
+always available at "http://docs.mongodb.org/manual/."
 
 Contributing to the Documentation
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -100,6 +100,6 @@ necessary Sphinx extensions and build tools, are available in the same
 repository as the documentation.
 
 You can view the documentation style guide and the build instructions
-in reSturctured Text files in the top-level of the `documentation
+in reStructured Text files in the top-level of the `documentation
 repository <https://github.com/mongodb/docs>`_. If you have any
 questions, please feel free to open a :issue:`Jira Case <DOCS>`.

source/administration/backups.txt

@@ -108,7 +108,7 @@ reliably, and typically provide the easiest backup systems method to
 implement.
 
 Snapshots work by creating pointers between the live data and a
-special snapshot volume: these pointers are theoretically equivelent
+special snapshot volume: these pointers are theoretically equivalent
 to "hard links." Then, as the working data diverges from the snapshot,
 the snapshot process uses a copy-on-write strategy. As a result the snapshot
 only stores modified data.
@@ -469,7 +469,7 @@ example:
 
 .. code-block:: sh
 
-   mongodump --host mongodb1.example.net --port 3017 --username user --password pass /opt/backup/mongodumpm-2011-10-24
+   mongodump --host mongodb1.example.net --port 3017 --username user --password pass /opt/backup/mongodump-2011-10-24
 
 On any :program:`mongodump` command you may, as above specify username
 and password credentials to specify database authentication.
@@ -495,7 +495,7 @@ the dump. Consider the following example:
 
 .. code-block:: sh
 
-   mongorestore --host mongodb1.example.net --port 3017 --username user --password pass /opt/backup/mongodumpm-2011-10-24
+   mongorestore --host mongodb1.example.net --port 3017 --username user --password pass /opt/backup/mongodump-2011-10-24
 
 On any :program:`mongorestore` command you may, as above specify
 username and password credentials as above.

source/administration/configuration.txt

@@ -15,7 +15,7 @@ While both interfaces provide access the same collection of options
 and settings, this document primarily uses the configuration file
 interface. If you run MongoDB using a control script or packaged for
 your operating system, you likely already have a configuration file
-located at ``/etc/mogondb.conf``. Confirm this by checking the content
+located at ``/etc/mongodb.conf``. Confirm this by checking the content
 of the ``/etc/init.d/mongod`` or ``/etc/rc.d/mongod`` script to
 insure that the :term:`control scripts <control script>` start the
 :program:`mongod` with the appropriate configuration file (see below.)

source/administration/monitoring.txt

@@ -428,7 +428,7 @@ Balancing and Chunk Distribution
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The most effective :term:`shard clusters <shard cluster>` require that
-:term:`chunks <chunk>` are evenly balanaced between the shards. MongoDB
+:term:`chunks <chunk>` are evenly balanced between the shards. MongoDB
 has a background :term:`balancer` process that distributes data such that
 chunks are always optimally distributed among the :term:`shards <shard>`.
 Issue the :func:`db.printShardingStatus()` or :func:`sh.status()`

source/administration/replica-sets.txt

@@ -321,7 +321,7 @@ This operation sets the following:
 
    If your replica set has an even number members, add an
    :ref:`arbiter <replica-set-arbiters>` to ensure that
-   nodes wil be able to quickly obtain a majority of votes in an
+   nodes will be able to quickly obtain a majority of votes in an
    :ref:`election <replica-set-elections>` for primary.
 
 .. seealso:: ":data:`members[n].priority`" and ":ref:`Replica Set

source/administration/sharding.txt

@@ -396,7 +396,7 @@ The procedure to remove a shard is as follows:
 
    .. code-block:: javascript
 
-      { msg: "remove shard completed succesfully" , stage: "completed", host: "mongodb0", ok : 1 }
+      { msg: "remove shard completed successfully" , stage: "completed", host: "mongodb0", ok : 1 }
 
 Once the value of the ``stage`` field is "completed," you may safely
 stop the processes comprising the ``mongodb0`` shard.
@@ -516,7 +516,7 @@ To modify the chunk size, use the following procedure:
    To eliminate confusion you should *always* set chunk size using the
    above procedure and never use the runtime options.
 
-Modifying the chunk size has serveral limitations:
+Modifying the chunk size has several limitations:
 
 - Automatic splitting only occurs when inserting :term:`documents
   <document>` or updating existing documents.
@@ -668,7 +668,7 @@ be able to migrate chunks:
 
       use config
 
-#. Use an operation modeled on the folloiwng example :func:`update()
+#. Use an operation modeled on the following example :func:`update()
    <db.collection.update()>` operation to modify the balancer's
    window:
 

source/core/replication.txt

@@ -49,7 +49,7 @@ Member Configurations
 
 All replica sets at most use a single :term:`primary` member and one or
 more :term:`secondary` members. Replica sets allow you to configure
-secondary members in a variey of ways. This section describes uses and
+secondary members in a variety of ways. This section describes uses and
 functions of all the replica set member configurations.
 
 .. seealso:: ":ref:`Replica Set Node Configurations

source/core/sharding-internals.txt

@@ -102,7 +102,7 @@ key, all insert operations will be storing data into a single chunk, and
 therefore, a single shard. As a result, the write capacity of this shard
 will define the effective write capacity of the cluster.
 
-A shard key that increases monotonically will not hinder perforamnce
+A shard key that increases monotonically will not hinder performance
 if you have a very low insert rate, or if most of your write
 operations are :func:`update() <db.collection.update()>` operations
 distributed through your entire data set. Generally, choose shard keys
@@ -202,7 +202,7 @@ are:
 - to ensure that :program:`mongos` can isolate most queries to a specific
   :program:`mongod`.
 
-Furethermore:
+Furthermore:
 
 - Each shard should be a :term:`replica set`, if a specific
   :program:`mongod` instance fails, the replica set members will elect

source/faq/developers.txt

@@ -79,7 +79,7 @@ disk more frequently, so that the above values resents a theoretical
 maximum.
 
 However, by default, MongoDB uses a "lazy" strategy to write to
-disk. This is advantegous in situations where the database receives a
+disk. This is advantageous in situations where the database receives a
 thousand increments to an object within one second, MongoDB only needs
 to flush this data to disk once. In addition to the aforementioned
 configuration options, you can also use :dbcommand:`fsync` and
@@ -147,7 +147,7 @@ Why are MongoDB's data files so large?
 
 MongoDB aggressively preallocates data files to reserve space and
 avoid file system fragmentation. You can use the :setting:`smallfiles`
-flag to modify the file prealocation strategy.
+flag to modify the file preallocation strategy.
 
 .. seealso:: This wiki page that address :wiki:`MongoDB disk use <Excessive+Disk+Space>`.
 

source/faq/fundamentals.txt

@@ -151,7 +151,7 @@ indexes, is 2 gigabytes. For this reason, do not deploy MongoDB to
 production on 32-bit machines.
 
 If you're running a 64-bit build of MongoDB, there's virtually no
-limit to storage size. For production deployments, 64-bit builts and
+limit to storage size. For production deployments, 64-bit builds and
 operating systems are strongly recommended.
 
 .. seealso:: "`Blog Post: 32-bit Limitations <http://blog.mongodb.org/post/137788967/32-bit-limitations>`_

source/faq/replica-sets.txt

@@ -159,7 +159,7 @@ for :term:`primary` but do not replicate the data like
 
 :term:`Replica sets <replica set>` require a majority of the
 original nodes present to elect a primary. Arbiters allow you
-to construct this majorty without the overhead of adding replicating
+to construct this majority without the overhead of adding replicating
 nodes to the system.
 
 There are many possible replica set :doc:`architectures

source/faq/sharding.txt

@@ -173,7 +173,7 @@ clients decreases.
 
 This can lead to an unused :program:`mongos` with a large number open
 of connections. If the :program:`mongos` is no longer in use, you're
-safe restaring the process to close existing connections.
+safe restarting the process to close existing connections.
 
 Where does MongoDB report on connections used by ``mongos``?
 ------------------------------------------------------------

source/reference/aggregation.txt

@@ -15,7 +15,7 @@ These aggregation operations are all accessible by way of the
 :mongodb:func:`aggregate()`. While all examples in this document use this
 function, :mongodb:func:`aggregate()` is merely a wrapper around the
 :term:`database command` :mongodb:dbcommand:`aggregate`. Therefore the
-following prototype aggregate are equivelent:
+following prototype aggregate are equivalent:
 
 .. code-block:: javascript
 
@@ -583,7 +583,7 @@ The current pipeline operators are:
 ..    This command reads all documents in the ``users`` collection and
 ..    writes them to the ``users2`` collection. The documents are then
 ..    returned by the aggregation framework in an array, which is the
-..    default beh avior.
+..    default behavior.
 
 .. _aggregation-expression-operators:
 

source/reference/collection-statistics.txt

@@ -50,7 +50,7 @@ Fields
 
 .. stats:: ns
 
-   The namepsace of the current collection, which follows the format
+   The namespace of the current collection, which follows the format
    ``[database].[collection]``.
 
 .. stats:: count

source/reference/commands.txt

@@ -1654,7 +1654,7 @@ Administration
 
        kill -SIGUSR1 2200
 
-   The rotated files will have a timestamp appended to the filneame.
+   The rotated files will have a timestamp appended to the filename.
 
    .. note::
 
@@ -2350,9 +2350,9 @@ Other Commands
 Internal Use
 ------------
 
-.. dbcommand:: avalibleQueryOptions
+.. dbcommand:: availableQueryOptions
 
-   :dbcommand:`avalibleQueryOptions` is an internal command that is only
+   :dbcommand:`availableQueryOptions` is an internal command that is only
    available on :program:`mongos` instances.
 
 .. dbcommand:: closeAllDatabases

source/reference/configuration-options.txt

@@ -279,7 +279,7 @@ Settings
    =========  ===================================
 
    You can use the :program:`mongosniff` tool to replay this output
-   for investigation. Given a typical daiglog file, located at
+   for investigation. Given a typical diaglog file, located at
    ``/data/db/diaglog.4f76a58c``, you might use a command in the
    following form to read these files:
 
@@ -337,7 +337,7 @@ Settings
    :program:`mongod` using IPv6 networks. :program:`mongod` disables
    IPv6 support by default in :program:`mongod` and all utilities.
 
-.. setting:: jsonnp
+.. setting:: jsonp
 
    *Default:* false
 
@@ -716,7 +716,7 @@ Sharding Cluster Options
    value is 64 megabytes. Larger chunks may lead to an uneven
    distribution of data, while smaller chunks may lead to frequent and
    unnecessary migrations. However, in some circumstances it may be
-   neccessary to set a different chunk size.
+   necessary to set a different chunk size.
 
    This setting only affects :program:`mongos` processes. Furthermore,
    :setting:`chunkSize` *only* sets the chunk size when initializing

source/reference/glossary.txt

@@ -697,7 +697,7 @@ Glossary
    map-reduce
       A data and processing and aggregation paradigm consisting of a
       "map" phase that selects data, and a "reduce" phase that
-      transforms the data. In MongoDB, you can run abitrary aggregations
+      transforms the data. In MongoDB, you can run arbitrary aggregations
       over data using map-reduce.
 
       .. seealso:: The ":wiki:`Map Reduce <MapReduce>`" wiki page for

source/reference/javascript.txt

@@ -446,7 +446,7 @@ Data Aggregation
                   the current document and an aggregation counter
                   object.
 
-   :field inital: The starting value of the aggregation counter
+   :field initial: The starting value of the aggregation counter
                   object.
 
    :field keyf: Optional. An optional function that returns a "key
@@ -851,7 +851,7 @@ Database
                      function.
 
    Provides the ability to run JavaScript code using the JavaScript
-   engine embeded in the MongoDB instance. In this environment the
+   engine embedded in the MongoDB instance. In this environment the
    value of the ``db`` variable on the server is the name of the
    current database.
 
@@ -957,10 +957,10 @@ Database
 
 .. function:: db.killOP(opid)
 
-   :param oppid: Specify an operation ID.
+   :param opid: Specify an operation ID.
 
    Terminates the specified operation. Use :func:`db.currentOp()`
-   to find operations and their correspoinding ids.
+   to find operations and their corresponding ids.
 
 .. function:: db.listCommands()
 
@@ -1534,11 +1534,11 @@ Sharding
 
         [hostname]
         [hostname]:[port]
-        [set]/[hosname]
-        [set]/[hosname],[hostname]:port
+        [set]/[hostname]
+        [set]/[hostname],[hostname]:port
 
    You can specify shards using the hostname, or a hostname and port
-   combination if the shard is ruining on a non-standard port. A
+   combination if the shard is running on a non-standard port. A
    :term:`replica set` can also function as a shard member. In these
    cases supply :func:`addShard <sh.addShard()>` with the set name,
    followed by at least one existing member of the set as a seed in a

source/reference/mongod.exe.txt

@@ -6,7 +6,7 @@
 :program:`mongod.exe` Manual
 ============================
 
-Sypnosis
+Synopsis
 --------
 
 :program:`mongod.exe` is the build of the MongoDB daemon

source/reference/mongod.txt

@@ -10,7 +10,7 @@ Synopsis
 --------
 
 :program:`mongod` is the primary daemon process for the MongoDB
-system. It handles data requests, manages data format, and preforms
+system. It handles data requests, manages data format, and performs
 background management operations.
 
 This document provides a complete overview of all command line options
@@ -35,7 +35,7 @@ Options
 
    Returns the version of the :program:`mongod` daemon.
 
-.. option:: --config <filname>, -f <filename>
+.. option:: --config <filename>, -f <filename>
 
    Specifies a configuration file, that you can use to specify
    runtime-configurations. While the options are equivalent and
@@ -208,7 +208,7 @@ Options
    =========  ===================================
 
    You can use the :program:`mongosniff` tool to replay this output
-   for investigation. Given a typical daiglog file, located at
+   for investigation. Given a typical diaglog file, located at
    ``/data/db/diaglog.4f76a58c``, you might use a command in the
    following form to read these files:
 
@@ -256,7 +256,7 @@ Options
    networks. :program:`mongod` disables IPv6 support by default in
    :program:`mongod` and all utilities.
 
-.. option:: --jsonnp
+.. option:: --jsonp
 
    Permits :term:`JSONP` access via an HTTP interface. Consider the
    security implications of allowing this activity before enabling
@@ -296,7 +296,7 @@ Options
    option has no impact on the size of existing namespace files.
 
    The default value is 16 megabytes, this provides for effectively
-   12,000 possible namespace. The maximum size is 2 gigabytes.
+   12,000 possible namespaces. The maximum size is 2 gigabytes.
 
 .. option:: --profile <level>
 
@@ -351,7 +351,7 @@ Options
    complete more quickly and will result in a more consistent and
    complete data set.
 
-   To continue the repair operation despite the journal files, shut
+   To continue the repair operation despite the journal files, shut down
    :program:`mongod` cleanly and restart with the :option:`--repair`
    option.
 
@@ -393,7 +393,7 @@ Options
 
 .. option:: --syncdelay <value>
 
-   This setting contrils the maximum number of seconds between disk
+   This setting controls the maximum number of seconds between disk
    syncs. While :program:`mongod` is always writing data to disk, this
    setting controls the maximum guaranteed interval between a
    successful write operation and the next time the database flushes
@@ -468,7 +468,7 @@ Master/Slave Replication
 
 These options provide access to conventional master-slave database
 replication. While this functionality remains accessible in MongoDB,
-replica sets are the prefered configuration for database replication.
+replica sets are the preferred configuration for database replication.
 
 .. option:: --master