From 29cfd50406b8d8a0e606eed3c5670d7fb1a1bddf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jorge=20Puente=20Sarr=C3=ADn?= Date: Fri, 10 May 2013 15:25:52 -0500 Subject: [PATCH] Fixed several duplicate terms --- source/faq/diagnostics.txt | 4 ++-- source/includes/ref-toc-command-replication.yaml | 2 +- source/reference/method/sh.status.txt | 4 ++-- source/reference/program/mongoperf.txt | 2 +- source/tutorial/enable-authentication.txt | 2 +- source/tutorial/manage-the-database-profiler.txt | 6 +++--- source/use-cases/storing-comments.txt | 5 ++--- 7 files changed, 12 insertions(+), 13 deletions(-) diff --git a/source/faq/diagnostics.txt b/source/faq/diagnostics.txt index 22e7275b7c3..6dd6a6baced 100644 --- a/source/faq/diagnostics.txt +++ b/source/faq/diagnostics.txt @@ -78,8 +78,8 @@ To set a shorter keep alive period use the following invocation: sysctl -w net.inet.tcp.keepinit=300 If your replica set or sharded cluster experiences keepalive-related -issues, you must must alter the ``tcp_keepalive_time`` value on all -machines hosting MongoDB processes. This includes all machines hosting +issues, you must alter the ``tcp_keepalive_time`` value on all machines +hosting MongoDB processes. This includes all machines hosting :program:`mongos` or :program:`mongod` servers. Windows users should consider the `Windows Server Technet Article on diff --git a/source/includes/ref-toc-command-replication.yaml b/source/includes/ref-toc-command-replication.yaml index 2d385caf716..4c7f7d0a41a 100644 --- a/source/includes/ref-toc-command-replication.yaml +++ b/source/includes/ref-toc-command-replication.yaml @@ -32,7 +32,7 @@ description: "Forces a :program:`mongod` to re-synchronize from the :term:`maste --- name: ":dbcommand:`applyOps`" file: /reference/command/applyOps -description: "Internal command that applies applies :term:`oplog` entries to the current data set." +description: "Internal command that applies :term:`oplog` entries to the current data set." --- name: ":dbcommand:`isMaster`" file: /reference/command/isMaster diff --git a/source/reference/method/sh.status.txt b/source/reference/method/sh.status.txt index f0550491508..42193e3b02d 100644 --- a/source/reference/method/sh.status.txt +++ b/source/reference/method/sh.status.txt @@ -202,5 +202,5 @@ Sharded Collection .. [#chunk-details] The sharded collection section, by default, displays the chunk information if the total number of chunks is less than 20. To display the information when you have 20 or more chunks, - call the the :method:`sh.status()` methods with the ``verbose`` - parameter set to ``true``, i.e. ``sh.status(true)``. + call the :method:`sh.status()` methods with the ``verbose`` parameter + set to ``true``, i.e. ``sh.status(true)``. diff --git a/source/reference/program/mongoperf.txt b/source/reference/program/mongoperf.txt index c3055d8e112..98b1d5db7ab 100644 --- a/source/reference/program/mongoperf.txt +++ b/source/reference/program/mongoperf.txt @@ -172,7 +172,7 @@ Configuration Fields The :setting:`~mongoperf.syncDelay` controls how frequently :program:`mongoperf` performs an asynchronous disk flush the memory mapped file used for testing. By default, :program:`mongod` - performs this operation every every 60 seconds. Use + performs this operation every 60 seconds. Use :setting:`~mongoperf.syncDelay` to test basic system performance of this type of operation. diff --git a/source/tutorial/enable-authentication.txt b/source/tutorial/enable-authentication.txt index b094696b661..c776ba9d148 100644 --- a/source/tutorial/enable-authentication.txt +++ b/source/tutorial/enable-authentication.txt @@ -6,7 +6,7 @@ Enable Authentication Enable authentication using the :setting:`auth` or :setting:`keyFile` settings. Use :setting:`auth` for standalone instances, and -:setting:`keyFile` with with :term:`replica sets ` and +:setting:`keyFile` with :term:`replica sets ` and :term:`sharded clusters `. :setting:`keyFile` implies :setting:`auth` and allows members of a MongoDB deployment to authenticate internally. diff --git a/source/tutorial/manage-the-database-profiler.txt b/source/tutorial/manage-the-database-profiler.txt index 773c11a59c3..52a4df8fa50 100644 --- a/source/tutorial/manage-the-database-profiler.txt +++ b/source/tutorial/manage-the-database-profiler.txt @@ -291,9 +291,9 @@ Profiler Overhead When enabled, profiling has a minor effect on performance. The :data:`system.profile <.system.profile>` collection is a :term:`capped collection` with a default size of 1 megabyte. A -collection of this size can typically store store several thousand -profile documents, but some application may use more or less profiling -data per operation. +collection of this size can typically store several thousand profile +documents, but some application may use more or less profiling data per +operation. To change the size of the :data:`system.profile <.system.profile>` collection, you must: diff --git a/source/use-cases/storing-comments.txt b/source/use-cases/storing-comments.txt index 2af73703953..f9d4a94de0c 100644 --- a/source/use-cases/storing-comments.txt +++ b/source/use-cases/storing-comments.txt @@ -107,9 +107,8 @@ This structure: - modifies the ``slug`` field to hold a path composed of the parent or parent's slug and this comment's unique slug, and -- adds a ``full_slug`` field that that combines the slugs and time - information to make it easier to sort documents in a threaded - discussion by date. +- adds a ``full_slug`` field that combines the slugs and time information + to make it easier to sort documents in a threaded discussion by date. .. warning::