Skip to content

Fix simple 'insure' typo #1455

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
2 changes: 1 addition & 1 deletion source/administration/configuration.txt
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ interface. If you run MongoDB using a control script or installed from
a package for your operating system, you likely already have a
configuration file located at ``/etc/mongodb.conf``. Confirm this by
checking the contents of the ``/etc/init.d/mongod`` or
``/etc/rc.d/mongod`` script to insure that the :term:`control scripts
``/etc/rc.d/mongod`` script to ensure that the :term:`control scripts
<control script>` start the :program:`mongod` with the appropriate
configuration file (see below.)

Expand Down
2 changes: 1 addition & 1 deletion source/administration/monitoring.txt
Original file line number Diff line number Diff line change
Expand Up @@ -688,7 +688,7 @@ Stale Locks

In nearly every case, all locks used by the balancer are automatically
released when they become stale. However, because any long lasting
lock can block future balancing, it's important to insure that all
lock can block future balancing, it's important to ensure that all
locks are legitimate. To check the lock status of the database,
connect to a :program:`mongos` instance using the :program:`mongo`
shell. Issue the following command sequence to switch to the
Expand Down