Skip to content

Copy edits for typos #2273

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

Closed
wants to merge 1 commit into from
Closed
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
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ description: |2
``noPadding`` flag disables the :ref:`power of 2 sizes allocation
<power-of-2-allocation>` for the collection. With ``noPadding``
flag set to true, the allocation strategy does not include
additional space to accomodate document growth, as such, document
additional space to accommodate document growth, as such, document
growth will result in new allocation. Use for collections with
workloads that are insert-only or in-place updates (such as
incrementing counters).
Expand Down
2 changes: 1 addition & 1 deletion source/includes/fact-wiredtiger-cachesizegb.rst
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
The default :setting:`storage.wiredTiger.engineConfig.cacheSizeGB` setting
assumes that there is a single :program:`mongod` instance per node. If a single
node contains multiple instances, then you should adjust the
:setting:`storage.wiredTiger.engineConfig.cacheSizeGB` setting to accomodate the
:setting:`storage.wiredTiger.engineConfig.cacheSizeGB` setting to accommodate the
working set as well as the other :program:`mongod` instances.

If you run :program:`mongod` in a container (e.g. ``lxc``, ``cgroups``,
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ content: |
If your :program:`mongod` has journaling enabled and your journal
and data files are on the same volume, you may skip this step.

If you need to lock the :program:`monogd`, attempt to lock one
If you need to lock the :program:`mongod`, attempt to lock one
secondary member of each replica set in each shard so that your
backups reflect the state of your database at the nearest possible
approximation of a single moment in time.
Expand Down
2 changes: 1 addition & 1 deletion source/includes/steps-backup-sharded-clusters-dumps.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ stepnum: 5
ref: restart-replica-set-members
pre: |
Use :method:`db.fsyncUnlock()` to unlock the locked replica set
members of each shard. Allow these mebers to catch up with the state
members of each shard. Allow these members to catch up with the state
of the primary.
---
title: Re-enable the balancer process.
Expand Down
2 changes: 1 addition & 1 deletion source/reference/command/serverStatus.txt
Original file line number Diff line number Diff line change
Expand Up @@ -1609,7 +1609,7 @@ section <server-status-example-wiredTiger>` of the
.. versionadded:: 3.0.0

:data:`serverStatus.wiredTiger.async` returns statistics related to
the ascynchronous operations API. This is unused by MongoDB.
the asynchronous operations API. This is unused by MongoDB.

.. data:: serverStatus.wiredTiger.block-manager

Expand Down