minor: typo & link repair run

source/core/update.txt

@@ -359,7 +359,7 @@ and a ``<query>`` argument with an ``_id`` field.
 
 .. example::
 
-   Consider the following psudocode explanation of
+   Consider the following pseudocode explanation of
    :method:`~db.collection.save()` as an illustration of its
    behavior:
 

source/data-modeling.txt

@@ -8,7 +8,7 @@ may be able to use different structures for a single data set in
 MongoDB, different data models may have significant impacts on MongoDB
 and applications performance. Consider :doc:`/core/data-modeling` for
 a conceptual overview of data modeling problems in MongoDB, and the
-:ref:`data-modeling-patterns` documents for exaples of different
+:ref:`data-modeling-patterns` documents for examples of different
 approaches to data models.
 
 .. seealso:: :doc:`/use-cases` for overviews of application design,

source/reference/aggregation/concat.txt

@@ -37,7 +37,7 @@ $concat (aggregation)
          { _id: 4, item: { sec: "main", category: "pie", type: "chicken pot" } }
 
       The following operation uses :expression:`$concat` to concatenate
-      the ``type`` field from the sub-document ``item``, a space `` ``,
+      the ``type`` field from the sub-document ``item``, a space,
       and the ``category`` field from the sub-document ``item`` to
       project a new ``food`` field:
 

source/reference/method/cd.txt

@@ -12,5 +12,3 @@ cd()
 
    This function returns with output relative to the current shell
    session, and does not impact the server.
-
-   .. note:: This feature is not yet implemented.

source/reference/mongoimport.txt

@@ -163,7 +163,7 @@ Options
 .. option:: --fieldFile <filename>
 
    As an alternative to :option:`--fields` the :option:`--fieldFile`
-   option allows you to specify a file (e.g. ``<file>```) to that
+   option allows you to specify a file (e.g. ``<file>``) to that
    holds a list of field names if your :term:`csv` or :term:`tsv`
    file does not include field names in the first (i.e. header) line
    of the file. Place one field per line.

source/reference/server-status.txt

@@ -1278,7 +1278,7 @@ metrics
    members of a replica set to acknowledge the write operation
    (i.e. greater than ``1``.)
 
-.. data:: serverStatus.metrics.getLastError.wtime.totalMillis`
+.. data:: serverStatus.metrics.getLastError.wtime.totalMillis
 
    :data:`~serverStatus.metrics.getLastError.wtime.totalMillis` reports
    the total amount of time in milliseconds that the :program:`mongod`

source/reference/ulimit.txt

@@ -65,11 +65,7 @@ For :program:`mongos`, consider the following behaviors:
   fulfill requests without needing to create new connections.
 
 - You can limit the number of incoming connections using
-  the :setting:`maxConns` run-time option:
-
-  .. code-block:: javascript
-
-     :option:`--maxConns <mongos --maxConns>`
+  the :option:`maxConns <mongos --maxConns>` run-time option.
 
   By restricting the number of incoming connections you can prevent a
   cascade effect where the :program:`mongos` creates too many

source/tutorial/isolate-sequence-of-operations.txt

@@ -112,7 +112,7 @@ as:
    reasons: First, in sharded environments, distributed locks could be
    expensive and slow. MongoDB's goal is to be lightweight and fast. We
    dislike the concept of deadlocks. We want the system to be simple and
-   predictable without these sort of surprises. We want Mongo DB to work
+   predictable without these sort of surprises. We want MongoDB to work
    well for realtime problems. If an operation may execute which locks
    large amounts of data, it might stop some small light queries for an
    extended period of time."