diff --git a/source/core/indexes.txt b/source/core/indexes.txt
index 63bca4dc7d4..2843ac95d7c 100644
--- a/source/core/indexes.txt
+++ b/source/core/indexes.txt
@@ -585,7 +585,7 @@ and each key's direction in the index (1 or -1).
 
    The resulting index is named: ``item_1_quantity_-1``.
 
-Optionally. you can specify a name for an index instead of using the
+Optionally, you can specify a name for an index instead of using the
 default name.
 
 .. example:: Issue the following command to create an index on ``item``
diff --git a/source/faq/developers.txt b/source/faq/developers.txt
index e2c51fc3942..9f92d6bede0 100644
--- a/source/faq/developers.txt
+++ b/source/faq/developers.txt
@@ -651,7 +651,7 @@ information on indexes.
 
 .. Commenting out.. If your small documents are approximately the page
    cache unit size, there is no benefit for ram cache efficiency, although
-   embedding will provide some benefit regarding random disk i/o.
+   embedding will provide some benefit regarding random disk I/O.
 
 .. _faq-developers-manual-padding:
 
diff --git a/source/faq/fundamentals.txt b/source/faq/fundamentals.txt
index 9789ef99dc9..0ec9d5e864a 100644
--- a/source/faq/fundamentals.txt
+++ b/source/faq/fundamentals.txt
@@ -31,7 +31,7 @@ partitioning.
 .. note::
 
    MongoDB uses :term:`BSON`, a binary object format similar
-   to, but more expressive than, :term:`JSON`.
+   to, but more expressive than :term:`JSON`.
 
 Do MongoDB databases have tables?
 ---------------------------------
diff --git a/source/reference/glossary.txt b/source/reference/glossary.txt
index 62ad3429f2d..b0ca98ef40e 100644
--- a/source/reference/glossary.txt
+++ b/source/reference/glossary.txt
@@ -271,7 +271,7 @@ Glossary
       for to store indexes. MongoDB uses b-trees for its indexes.
 
    ISODate
-     The international date format used by :program:`mongo`.
+     The international date format used by :program:`mongo`
      to display dates. E.g. ``YYYY-MM-DD HH:MM.SS.milis``.
 
    journal
diff --git a/source/tutorial/manage-chunks-in-sharded-cluster.txt b/source/tutorial/manage-chunks-in-sharded-cluster.txt
index 995145d6735..ea5a8c67ae3 100644
--- a/source/tutorial/manage-chunks-in-sharded-cluster.txt
+++ b/source/tutorial/manage-chunks-in-sharded-cluster.txt
@@ -175,10 +175,10 @@ Modify Chunk Size
 -----------------
 
 When you initialize a sharded cluster, [#mongos-initialization]_ the
-default chunk size is 64 megabytes. this default chunk size works well
-for most deployments. however, if you notice that automatic migrations
-are incurring a level of i/o that your hardware cannot handle, you may
-want to reduce the chunk size. for the automatic splits and
+default chunk size is 64 megabytes. This default chunk size works well
+for most deployments; however, if you notice that automatic migrations
+are incurring a level of I/O that your hardware cannot handle, you may
+want to reduce the chunk size. For the automatic splits and
 migrations, a small chunk size leads to more rapid and frequent
 migrations.
 
diff --git a/source/tutorial/write-scripts-for-the-mongo-shell.txt b/source/tutorial/write-scripts-for-the-mongo-shell.txt
index d9b80adf13d..f1c8f54a439 100644
--- a/source/tutorial/write-scripts-for-the-mongo-shell.txt
+++ b/source/tutorial/write-scripts-for-the-mongo-shell.txt
@@ -91,7 +91,7 @@ evaluate a javascript file
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can specify a ``.js`` file to the :program:`mongo` shell, and
-:program:`mongo` will evaluate the javascript directly. consider the
+:program:`mongo` will evaluate the javascript directly. Consider the
 following example:
 
 .. code-block:: sh