Fixed several duplicate terms

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

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

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)``.

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.
 

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 <replica set>` and
+:setting:`keyFile` with :term:`replica sets <replica set>` and
 :term:`sharded clusters <sharded cluster>`. :setting:`keyFile` implies
 :setting:`auth` and allows members of a MongoDB deployment to
 authenticate internally.

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 <<database>.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
 <<database>.system.profile>` collection, you must:

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::