diff --git a/.gitignore b/.gitignore index af475ba4653..cb869053011 100644 --- a/.gitignore +++ b/.gitignore @@ -4,3 +4,4 @@ build/* \#*# *__pycache__* *.pyc +*.bak diff --git a/source/about.txt b/source/about.txt index da10f1f478a..2037713adfd 100644 --- a/source/about.txt +++ b/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 `_. If you have any questions, please feel free to open a :issue:`Jira Case `. diff --git a/source/administration/backups.txt b/source/administration/backups.txt index f073a40ac29..7fc06e9650a 100644 --- a/source/administration/backups.txt +++ b/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. diff --git a/source/administration/configuration.txt b/source/administration/configuration.txt index 124ed1a371e..3d3ba79f9fd 100644 --- a/source/administration/configuration.txt +++ b/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 ` start the :program:`mongod` with the appropriate configuration file (see below.) diff --git a/source/administration/monitoring.txt b/source/administration/monitoring.txt index 7ed3eb2c3c0..4a79c06a238 100644 --- a/source/administration/monitoring.txt +++ b/source/administration/monitoring.txt @@ -428,7 +428,7 @@ Balancing and Chunk Distribution ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The most effective :term:`shard clusters ` require that -:term:`chunks ` are evenly balanaced between the shards. MongoDB +:term:`chunks ` 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 `. Issue the :func:`db.printShardingStatus()` or :func:`sh.status()` diff --git a/source/administration/replica-sets.txt b/source/administration/replica-sets.txt index f4b7423606a..dd87af3358e 100644 --- a/source/administration/replica-sets.txt +++ b/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 ` 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 ` for primary. .. seealso:: ":data:`members[n].priority`" and ":ref:`Replica Set diff --git a/source/administration/sharding.txt b/source/administration/sharding.txt index 2909cf5b164..2a940f627d1 100644 --- a/source/administration/sharding.txt +++ b/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 ` 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() ` operation to modify the balancer's window: diff --git a/source/core/replication.txt b/source/core/replication.txt index 9c372403ced..9b7f27f8b10 100644 --- a/source/core/replication.txt +++ b/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 diff --git a/source/core/sharding-internals.txt b/source/core/sharding-internals.txt index 994a2da36e2..d923dc85bed 100644 --- a/source/core/sharding-internals.txt +++ b/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() ` 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 diff --git a/source/faq/developers.txt b/source/faq/developers.txt index 7e716fe9ada..1da813b98c3 100644 --- a/source/faq/developers.txt +++ b/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 `. diff --git a/source/faq/fundamentals.txt b/source/faq/fundamentals.txt index 1e1d6c7ee00..be0c0145caf 100644 --- a/source/faq/fundamentals.txt +++ b/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 `_ diff --git a/source/faq/replica-sets.txt b/source/faq/replica-sets.txt index c4c7efcbaa2..bd064843476 100644 --- a/source/faq/replica-sets.txt +++ b/source/faq/replica-sets.txt @@ -159,7 +159,7 @@ for :term:`primary` but do not replicate the data like :term:`Replica sets ` 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 diff --git a/source/faq/sharding.txt b/source/faq/sharding.txt index 4856ead52e0..4e0afd3d207 100644 --- a/source/faq/sharding.txt +++ b/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``? ------------------------------------------------------------ diff --git a/source/reference/aggregation.txt b/source/reference/aggregation.txt index 9ccfc6c6a7a..44471d339cc 100644 --- a/source/reference/aggregation.txt +++ b/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: diff --git a/source/reference/collection-statistics.txt b/source/reference/collection-statistics.txt index 2f795cf9490..3fa9a8fb773 100644 --- a/source/reference/collection-statistics.txt +++ b/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 diff --git a/source/reference/commands.txt b/source/reference/commands.txt index d42d402b976..92109a844af 100644 --- a/source/reference/commands.txt +++ b/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 diff --git a/source/reference/configuration-options.txt b/source/reference/configuration-options.txt index 648519b3133..a49156e9dbf 100644 --- a/source/reference/configuration-options.txt +++ b/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 diff --git a/source/reference/glossary.txt b/source/reference/glossary.txt index fc0849e8d31..02c2894b841 100644 --- a/source/reference/glossary.txt +++ b/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 `" wiki page for diff --git a/source/reference/javascript.txt b/source/reference/javascript.txt index 10c8d389842..1c416176593 100644 --- a/source/reference/javascript.txt +++ b/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 ` with the set name, followed by at least one existing member of the set as a seed in a diff --git a/source/reference/mongod.exe.txt b/source/reference/mongod.exe.txt index 0b41e35aa22..034227b1f15 100644 --- a/source/reference/mongod.exe.txt +++ b/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 diff --git a/source/reference/mongod.txt b/source/reference/mongod.txt index f36232ecfc2..804d3935f92 100644 --- a/source/reference/mongod.txt +++ b/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 , -f +.. option:: --config , -f 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 @@ -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 - 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 diff --git a/source/reference/mongodump.txt b/source/reference/mongodump.txt index 1615d7fbd3b..1bc19b1d355 100644 --- a/source/reference/mongodump.txt +++ b/source/reference/mongodump.txt @@ -45,7 +45,7 @@ Options attempt to connect to a MongoDB process ruining on the localhost port number ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than ``27017``. To connect to a replica set, use the :option:`--host ` @@ -225,11 +225,11 @@ using the ``/srv/mongodb`` directory. mongodump --dbpath /srv/mongodb In the final example, :program:`mongodump` creates a database dump -located at ``/opt/backup/mongodumpm-2011-10-24``, from a database +located at ``/opt/backup/mongodump-2011-10-24``, from a database running on port ``37017`` on the host ``mongodb1.example.net`` and authenticating using the username ``user`` and the password ``pass``, as follows: .. code-block:: sh - mongodump --host mongodb1.example.net --port 37017 --username user --password pass /opt/backup/mongodumpm-2011-10-24 + mongodump --host mongodb1.example.net --port 37017 --username user --password pass /opt/backup/mongodump-2011-10-24 diff --git a/source/reference/mongoexport.txt b/source/reference/mongoexport.txt index 1bf0ed7abe8..a3303031ff1 100644 --- a/source/reference/mongoexport.txt +++ b/source/reference/mongoexport.txt @@ -52,7 +52,7 @@ Options connect to a MongoDB process ruining on the localhost port number ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than ``27017``. .. option:: --port diff --git a/source/reference/mongofiles.txt b/source/reference/mongofiles.txt index 8c1060877b1..7dddbed4f11 100644 --- a/source/reference/mongofiles.txt +++ b/source/reference/mongofiles.txt @@ -107,7 +107,7 @@ Options to connect to a MongoDB process ruining on the localhost port number ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than 27017. .. option:: --port diff --git a/source/reference/mongoimport.txt b/source/reference/mongoimport.txt index f7b9d06c1cb..dcd9afd3119 100644 --- a/source/reference/mongoimport.txt +++ b/source/reference/mongoimport.txt @@ -53,7 +53,7 @@ Options will attempt to connect to a MongoDB process ruining on the localhost port numbered ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than ``27017``. To connect to a replica set, use the :option:`--host` argument with a diff --git a/source/reference/mongorestore.txt b/source/reference/mongorestore.txt index db512fe0b7c..507c77fd98d 100644 --- a/source/reference/mongorestore.txt +++ b/source/reference/mongorestore.txt @@ -41,7 +41,7 @@ Options :program:`mongorestore` will attempt to connect to a MongoDB process running on the localhost port number ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than ``27017``. .. option:: --port @@ -146,7 +146,7 @@ Options .. option:: --keepIndexVersion Prevents :program:`mongorestore` from upgrading the index to the latest - version durring the restoration process. + version during the restoration process. .. option:: @@ -186,7 +186,7 @@ data directory. mongorestore --dbpath /srv/mongodb In the final example, :program:`mongorestore` restores a database -dump located at ``/opt/backup/mongodumpm-2011-10-24``, from a database +dump located at ``/opt/backup/mongodump-2011-10-24``, from a database running on port ``37017`` on the host ``mongodb1.example.net``. :program:`mongorestore`` authenticates to the this MongoDB instance using the username ``user`` and the @@ -194,4 +194,4 @@ password ``pass``, as follows: .. code-block:: sh - mongorestore --host mongodb1.example.net --port 37017 --username user --password pass /opt/backup/mongodumpm-2011-10-24 + mongorestore --host mongodb1.example.net --port 37017 --username user --password pass /opt/backup/mongodump-2011-10-24 diff --git a/source/reference/mongos.exe.txt b/source/reference/mongos.exe.txt index fd5972acace..6d13b1a7a67 100644 --- a/source/reference/mongos.exe.txt +++ b/source/reference/mongos.exe.txt @@ -6,7 +6,7 @@ :program:`mongos.exe` Manual ============================ -Sypnosis +Synopsis -------- :program:`mongos.exe` is the build of the MongoDB Shard diff --git a/source/reference/mongos.txt b/source/reference/mongos.txt index 14447dfaa11..9b82f480b4e 100644 --- a/source/reference/mongos.txt +++ b/source/reference/mongos.txt @@ -12,8 +12,8 @@ Synopsis :program:`mongos` for "MongoDB Shard," is a routing service for MongoDB shard configurations that processes queries from the application layer, and determines the location of this data in the -:term:`shard cluster`, in order to complete these operations these -operations. From the perspective of the application, a +:term:`shard cluster`, in order to complete these operations. +From the perspective of the application, a :program:`mongos` instance behaves identically to any other MongoDB instance. @@ -49,7 +49,7 @@ Options Returns the version of the :program:`mongod` daemon. -.. option:: --config , -f +.. option:: --config , -f Specifies a configuration file, that you can use to specify runtime-configurations. While the options are equivalent and @@ -197,7 +197,7 @@ Options the ideal size for chunks in most deployments: larger chunk size can lead to uneven data distribution, smaller chunk size often leads to inefficient movement of chunks between nodes. However, in - some circumstances it may be neccessary to set a different chunk + some circumstances it may be necessary to set a different chunk size. This option *only* sets the chunk size when initializing the @@ -212,7 +212,7 @@ Options using IPv6 networks. MongoDB 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 diff --git a/source/reference/mongostat.txt b/source/reference/mongostat.txt index ea2b70776e9..a3752ea5553 100644 --- a/source/reference/mongostat.txt +++ b/source/reference/mongostat.txt @@ -62,7 +62,7 @@ Options want to export data. By default :program:`mongostat` attempts to connect to a MongoDB process running on the localhost port number ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than ``27017``. .. option:: --port diff --git a/source/reference/mongotop.txt b/source/reference/mongotop.txt index 2d3651837f2..67318132ea1 100644 --- a/source/reference/mongotop.txt +++ b/source/reference/mongotop.txt @@ -60,7 +60,7 @@ Options connect to a MongoDB process running on the localhost port number ``27017``. - Optionally, specify a port number to connect a MongboDB instance + Optionally, specify a port number to connect a MongoDB instance running on a port other than ``27017``. .. option:: --port diff --git a/source/reference/operators.txt b/source/reference/operators.txt index bd29e5a6ea3..dff1dc8f3d7 100644 --- a/source/reference/operators.txt +++ b/source/reference/operators.txt @@ -44,7 +44,7 @@ Comparison of ``field`` is greater than the specified ``value``. If ``field`` holds an array, only one value in the array needs to - be greater than the specified ``value`` to produce a succesful + be greater than the specified ``value`` to produce a successful match. .. operator:: $lte @@ -84,7 +84,7 @@ This statement returns all documents with ``field`` between .. note:: - Fields containg arrays match conditional operators, if only one + Fields containing arrays match conditional operators, if only one item matches. Therefore, the following query: .. code-block:: javascript @@ -667,7 +667,7 @@ Array .. operator:: $size The :operator:`$size` operator matches any array with the number of - elements specified by the arguement. For example: + elements specified by the argument. For example: .. code-block:: javascript @@ -846,7 +846,7 @@ Array - The operation will fail if the field specified in the :operator:`$push` statement is *not* an array. :operator:`$push` - does not fail when pushing a value to a non-existant field. + does not fail when pushing a value to a non-existent field. - If ``value1`` is an array itself, :operator:`$push` appends the whole array as an element in the identified array. To add multiple items to an @@ -935,7 +935,7 @@ Array db.collection.update( { field: value }, { $pull: { field: value1 } } ); :operator:`$pull` removes the value ``value1`` from the array in ``field``, - in the document that matches the query statement ``{ field: valppppue + in the document that matches the query statement ``{ field: value }`` in ``collection``. If ``value1`` existed multiple times in the ``field`` array, :operator:`pull` would remove all instances of ``value1`` in this array. @@ -996,7 +996,7 @@ Isolation other operations to interleave with this updates. If these interleaved operations contain writes, the update operation may produce unexpected results. By specifying :operator:`$atomic` you - can garuentee isolation for the entire multi-update. + can guarantee isolation for the entire multi-update. .. seealso:: See :func:`db.collection.update()` for more information about the :func:`db.collection.update()` method. diff --git a/source/reference/replica-configuration.txt b/source/reference/replica-configuration.txt index 7f0758f9b9a..a0c7f94ead6 100644 --- a/source/reference/replica-configuration.txt +++ b/source/reference/replica-configuration.txt @@ -32,7 +32,7 @@ Configuration Variables **Type**: array - Contains an array holding an embeded :term:`document` for each + Contains an array holding an embedded :term:`document` for each member of the replica set. The ``members`` document contains a number of fields that describe the configuration of each member of the replica set. diff --git a/source/reference/replica-status.txt b/source/reference/replica-status.txt index 98fd84e5e4b..d2daf0600f0 100644 --- a/source/reference/replica-status.txt +++ b/source/reference/replica-status.txt @@ -106,7 +106,7 @@ Member Statuses .. include:: /includes/replica-states.rst -.. status:: members.sateStr +.. status:: members.stateStr A string that describes :status:`members.state`. diff --git a/source/reference/replication-info.txt b/source/reference/replication-info.txt index fe6c8f4b946..de75e7f1fb6 100644 --- a/source/reference/replication-info.txt +++ b/source/reference/replication-info.txt @@ -80,4 +80,4 @@ The following fields appear in the output of Returns a time stamp reflecting the current time. The shell process generates this value, and the datum may differ slightly from the server time if you're connecting from a remote host as a - reult. Equivalent to :func:`Date()`. + result. Equivalent to :func:`Date()`. diff --git a/source/reference/server-status.txt b/source/reference/server-status.txt index 6ac90663d54..13a5b0288ae 100644 --- a/source/reference/server-status.txt +++ b/source/reference/server-status.txt @@ -281,7 +281,7 @@ globalLock The value of :status:`globalLock.totalTime` represents the time, in microseconds, since the database last started and creation of the - :status:`globalLock`. This is roughly equivelent to total server + :status:`globalLock`. This is roughly equivalent to total server uptime. .. status:: globalLock.lockTime @@ -307,7 +307,7 @@ globalLock .. versionchanged:: 2.2 :status:`globalLock.ratio` was removed. See :status:`locks`. - The value of :status:`gobalLock.ratio` displays the relationship between + The value of :status:`globalLock.ratio` displays the relationship between :status:`globalLock.lockTime` and :status:`globalLock.totalTime`. Low values indicate that operations have held the :status:`globalLock` @@ -601,7 +601,7 @@ backgroundFlushing The :status:`backgroundFlushing.total_ms` value provides the total number of milliseconds (ms) that the :program:`mongod` processes have spent writing (i.e. flushing) data to disk. Because this is an absolute - value, consider the value of :status:`backgroundFlishing.flushes` + value, consider the value of :status:`backgroundFlushing.flushes` and :status:`backgroundFlushing.average_ms` to provide better context for this datum. diff --git a/source/tutorial/convert-replica-set-to-replicated-shard-cluster.txt b/source/tutorial/convert-replica-set-to-replicated-shard-cluster.txt index 7111269f18a..9307be0669e 100644 --- a/source/tutorial/convert-replica-set-to-replicated-shard-cluster.txt +++ b/source/tutorial/convert-replica-set-to-replicated-shard-cluster.txt @@ -118,7 +118,7 @@ set and then insert test data. "ok" : 1 } -5. Create and populate a new collection. The following JavScript +5. Create and populate a new collection. The following JavaScript function writes one million documents to the collection ``test_collection`` in the following form: @@ -229,7 +229,7 @@ store the cluster's metadata. .. code-block:: javascript - db.runCommand( { addshard : "firstset/localhost:10001,localhost:10002,localhost:10003" } ) + db.runCommand( { addShard : "firstset/localhost:10001,localhost:10002,localhost:10003" } ) 3. Observe the following message, which denotes success: @@ -299,7 +299,7 @@ above, omitting the test data. .. code-block:: javascript use admin - db.runCommand( { addshard : "secondset/localhost:10004,localhost:10005,localhost:10006" } ) + db.runCommand( { addShard : "secondset/localhost:10004,localhost:10005,localhost:10006" } ) This command will return the following success message: diff --git a/source/tutorial/deploy-geographically-distributed-replica-set.txt b/source/tutorial/deploy-geographically-distributed-replica-set.txt index ca2699f50ce..2d9e49ac46a 100644 --- a/source/tutorial/deploy-geographically-distributed-replica-set.txt +++ b/source/tutorial/deploy-geographically-distributed-replica-set.txt @@ -175,7 +175,7 @@ configuration `: rs.config() Now, issue the following sequence of commands to add the remaining -members to the replica set. The following examrsple assumes that the +members to the replica set. The following example assumes that the current primary is ``mongodb0.example.net``. .. code-block:: javascript @@ -418,7 +418,7 @@ the following: the members by deploying the :term:`arbiter` within Site A. For six member sets, deploy at least three voting members in - addition to the arbiter in Site A, the remaining rembmers in + addition to the arbiter in Site A, the remaining members in alternate sites. - Use the procedure for a three member replica set if you have an odd diff --git a/source/tutorial/deploy-replica-set.txt b/source/tutorial/deploy-replica-set.txt index ffff988f40d..851004d5e5d 100644 --- a/source/tutorial/deploy-replica-set.txt +++ b/source/tutorial/deploy-replica-set.txt @@ -119,7 +119,7 @@ information: :func:`rs.initiate()`, :func:`rs.conf()`, :func:`rs.reconfig()` and :func:`rs.add()`. .. [#screen] `GNU Screen `_ is packaged as - ``screen`` on Debian-based, Fedira/Red Hat-based, and Arch Linux. + ``screen`` on Debian-based, Fedora/Red Hat-based, and Arch Linux. .. seealso:: You may also consider the "`simple setup script `_" diff --git a/source/tutorial/install-mongodb-on-debian-or-ubuntu-linux.txt b/source/tutorial/install-mongodb-on-debian-or-ubuntu-linux.txt index cdd2c722ec6..3adb0f48dbe 100644 --- a/source/tutorial/install-mongodb-on-debian-or-ubuntu-linux.txt +++ b/source/tutorial/install-mongodb-on-debian-or-ubuntu-linux.txt @@ -61,7 +61,7 @@ Configure Package Management System (APT) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Debian/Ubuntu package management tool (i.e. ``dpkg`` and ``apt``) -ensure package consistency and authenticity by requring that +ensure package consistency and authenticity by requiring that distributors sign packages with GPG keys. Issue the following command to import the `10gen public GPG Key `_: diff --git a/source/tutorial/install-mongodb-on-windows.txt b/source/tutorial/install-mongodb-on-windows.txt index 67f41f0356b..d43aac1ef1e 100644 --- a/source/tutorial/install-mongodb-on-windows.txt +++ b/source/tutorial/install-mongodb-on-windows.txt @@ -232,7 +232,7 @@ Run all of the following commands in :guilabel:`Command Shell` with C:\mongodb\bin\mongod.exe --config C:\mongodb\mongod.cfg --install - Modify the path to the ``monogd.cfg`` file as needed. For the + Modify the path to the ``mongod.cfg`` file as needed. For the ``--install`` option to succeed, you *must* specify a :setting:`logpath` setting or the :option:`--logpath ` run-time option. diff --git a/source/tutorial/remove-shards-from-cluster.txt b/source/tutorial/remove-shards-from-cluster.txt index e7f408fd71a..91d9cb2a46d 100644 --- a/source/tutorial/remove-shards-from-cluster.txt +++ b/source/tutorial/remove-shards-from-cluster.txt @@ -146,7 +146,7 @@ When successful, the response will be the following: .. 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 } When the value of "state" is "completed", you may safely stop the ``mongodb0`` shard. diff --git a/source/use-cases/inventory-management.txt b/source/use-cases/inventory-management.txt index f49f3f48071..2badcb35333 100644 --- a/source/use-cases/inventory-management.txt +++ b/source/use-cases/inventory-management.txt @@ -70,7 +70,7 @@ The SKU above has 16 items in stock, 1 item a cart, and 2 items in a second cart. This leaves a total of 19 unsold items of merchandise. To model the shopping cart objects, you need to maintain ``sku``, -``quantity``, fields embeded in a shopping cart :term:`document`: +``quantity``, fields embedded in a shopping cart :term:`document`: .. code-block:: javascript diff --git a/source/use-cases/metadata-and-asset-management.txt b/source/use-cases/metadata-and-asset-management.txt index fe886c3c7a0..9c7599c9057 100644 --- a/source/use-cases/metadata-and-asset-management.txt +++ b/source/use-cases/metadata-and-asset-management.txt @@ -130,7 +130,7 @@ document from the ``cms.assets.files`` collection: .. note:: - This document embends the basic node document fields, which allows + This document embeds the basic node document fields, which allows you to use the same code to manipulate nodes, regardless of type. Operations diff --git a/source/use-cases/pre-aggregated-reports.txt b/source/use-cases/pre-aggregated-reports.txt index 298a96e6350..305f226850b 100644 --- a/source/use-cases/pre-aggregated-reports.txt +++ b/source/use-cases/pre-aggregated-reports.txt @@ -295,7 +295,7 @@ Operations ---------- This section outlines a number of common operations for building and -interacting with real-time-analyitics reporting system. The major +interacting with real-time-analytics reporting system. The major challenge is in balancing performance and write (i.e. :term:`upsert`) performance. All examples in this document use the Python programming language and the :api:`PyMongo ` :term:`driver` for @@ -488,7 +488,7 @@ Indexing ```````` To support these query operation, create a compound index on the -following daily statistics fields: ``metadate.site``, +following daily statistics fields: ``metadata.site``, ``metadata.page``, and ``metadata.date`` (in that order.) Use the following operation at the Python/PyMongo console. diff --git a/source/use-cases/product-catalog.txt b/source/use-cases/product-catalog.txt index d23ac8d5a46..7fc1ef9af1a 100644 --- a/source/use-cases/product-catalog.txt +++ b/source/use-cases/product-catalog.txt @@ -285,7 +285,7 @@ Operations ---------- For most deployments the primary use of the product catalog is to -perform search operations. This section provides an overivew of +perform search operations. This section provides an overview of various types of queries that may be useful for supporting an e-commerce site. All examples in this document use the Python programming language and the :api:`PyMongo ` :term:`driver` for @@ -425,7 +425,7 @@ can use the ":py:mod:`python:re`" module to construct the query: MongoDB provides a special syntax for regular expression queries without the need for the :py:mod:`re` module. Consider the following -alternative which is equivelent to the above example: +alternative which is equivalent to the above example: .. code-block:: python diff --git a/source/use-cases/storing-comments.txt b/source/use-cases/storing-comments.txt index c70757f8195..cdd74dbc158 100644 --- a/source/use-cases/storing-comments.txt +++ b/source/use-cases/storing-comments.txt @@ -658,7 +658,7 @@ Retrieve a Comment via Direct Links Query ^^^^^ -To retrieve a comment directly without paging through all preceeding +To retrieve a comment directly without paging through all preceding pages of commentary, use the slug to find the correct page, and then use application logic to find the correct comment: