teh teh typo run

source/administration/production-notes.txt

@@ -202,7 +202,7 @@ To fully disable NUMA, you must perform both operations. For more
 information, see the `Documentation for /proc/sys/vm/*
 <http://www.kernel.org/doc/Documentation/sysctl/vm.txt>`_.
 
-See the `The MySQL "swap insanity" problem and the effects of NUMA
+See `The MySQL "swap insanity" problem and the effects of NUMA
 <http://jcole.us/blog/archives/2010/09/28/mysql-swap-insanity-and-the
 -nu ma-architecture/>`_ post, which describes the effects of NUMA on
 databases. This blog post addresses the impact of NUMA for MySQL,

source/core/authentication.txt

@@ -227,7 +227,7 @@ Authentication on Sharded Clusters
 
 In sharded clusters, applications authenticate to directly to
 :program:`mongos` instances, using credentials stored in the ``admin``
-database of the the
+database of the
 :term:`config servers <config server>`. The shards in the sharded
 cluster also have credentials, and clients can authenticate directly
 to the shards to perform maintenance directly on the shards. In

source/core/replica-set-architectures.txt

@@ -162,7 +162,7 @@ Deployment Patterns
 -------------------
 
 The following documents describe common replica set deployment
-patterns. Other patterns are possible and effective depending on the
+patterns. Other patterns are possible and effective depending on
 the application's requirements. If needed, combine features of each
 architecture in your own deployment:
 

source/core/sharding-balancing.txt

@@ -10,7 +10,7 @@ Sharded Collection Balancing
 Balancing is the process MongoDB uses to distribute data of a sharded
 collection evenly across a :term:`sharded cluster`. When a
 :term:`shard` has too many of a sharded collection's :term:`chunks
-<chunk>` compared to other shards, MongoDB automatically balances the
+<chunk>` compared to other shards, MongoDB automatically balances
 the chunks across the shards. The balancing procedure for
 :term:`sharded clusters <sharded cluster>` is entirely transparent to
 the user and application layer.

source/reference/operator/aggregation/let.txt

@@ -78,7 +78,7 @@ A ``sales`` collection has the following documents:
    { _id: 1, price: 10, tax: 0.50, applyDiscount: true }
    { _id: 2, price: 10, tax: 0.25, applyDiscount: false }
 
-The following aggregation uses :expression:`$let` in the the
+The following aggregation uses :expression:`$let` in the
 :pipeline:`$project` pipeline stage to calculate and return the
 ``finalTotal`` for each document:
 

source/tutorial/build-a-2dsphere-index.txt

@@ -65,7 +65,7 @@ Create a Compound Index with ``2dsphere`` Index Key
 
 A :ref:`compound index <index-type-compound>` can include a
 ``2dsphere`` index key in combination with non-geospatial index keys.
-For example, the following operation creates a compound index where the
+For example, the following operation creates a compound index where
 the first key ``loc`` is a ``2dsphere`` index key, and the remaining
 keys ``category`` and ``names`` are non-geospatial index keys,
 specifically descending (``-1``) and ascending (``1``) keys