diff --git a/source/core/sharded-cluster-internals.txt b/source/core/sharded-cluster-internals.txt
index 91f00bffebd..6de8bed9294 100644
--- a/source/core/sharded-cluster-internals.txt
+++ b/source/core/sharded-cluster-internals.txt
@@ -49,7 +49,7 @@ stores address records:
   number of fixed chunks. This may have a number of effects:
 
   - If MongoDB cannot split a chunk because all of its documents
-    have the same shard key, migrations involving these un-splitable
+    have the same shard key, migrations involving these un-splittable
     chunks will take longer than other migrations, and it will be more
     difficult for your data to stay balanced.
 
@@ -61,7 +61,7 @@ stores address records:
   While this field has a large number of possible values, and thus has
   potentially higher cardinality, it's possible that a large number of users
   could have the same value for the shard key, which would make this
-  chunk of users un-splitable.
+  chunk of users un-splittable.
 
   In these cases, cardinality depends on the data. If your address book
   stores records for a geographically distributed contact list
@@ -168,7 +168,7 @@ To select a shard key for a collection:
 
 If this field has low cardinality (i.e not sufficiently
 selective) you should add a second field to the shard key making a
-compound shard key. The data may become more splitable with a
+compound shard key. The data may become more splittable with a
 compound shard key.
 
 .. see:: :ref:`sharding-mongos` for more information on query
diff --git a/source/tutorial/deploy-shard-cluster.txt b/source/tutorial/deploy-shard-cluster.txt
index 03bc0513909..c4dcba69cd7 100644
--- a/source/tutorial/deploy-shard-cluster.txt
+++ b/source/tutorial/deploy-shard-cluster.txt
@@ -262,7 +262,7 @@ You enable sharding on a per-collection basis.
 
       This shard key distributes documents by the value of the
       ``zipcode`` field. If a number of documents have the same value
-      for this field, then that :term:`chunk` will be :ref:`splitable
+      for this field, then that :term:`chunk` will be :ref:`splittable
       <sharding-shard-key-cardinality>` by the values of the ``name``
       field.
 
@@ -271,7 +271,7 @@ You enable sharding on a per-collection basis.
 
       This shard key distributes documents by the value of the ``state``
       field. If a number of documents have the same value for this
-      field, then that :term:`chunk` will be :ref:`splitable
+      field, then that :term:`chunk` will be :ref:`splittable
       <sharding-shard-key-cardinality>` by the values of the ``_id``
       field.
 
@@ -280,7 +280,7 @@ You enable sharding on a per-collection basis.
 
       This shard key distributes documents by the value of the ``type``
       field. If a number of documents have the same value for this
-      field, then that :term:`chunk` will be :ref:`splitable
+      field, then that :term:`chunk` will be :ref:`splittable
       <sharding-shard-key-cardinality>` by the values of the ``_id``
       field.
 
diff --git a/source/tutorial/select-shard-key.txt b/source/tutorial/select-shard-key.txt
index a904ba5d3b1..febfd207caf 100644
--- a/source/tutorial/select-shard-key.txt
+++ b/source/tutorial/select-shard-key.txt
@@ -21,7 +21,7 @@ Create a Shard Key that is Easily Divisible
 
 An easily divisible shard key makes it easy for MongoDB to distribute
 content among the shards. Shard keys that have a limited number of
-possible values can result in chunks that are "unsplitable." See the
+possible values can result in chunks that are "unsplittable." See the
 :ref:`sharding-shard-key-cardinality` section for more information.
 
 Create a Shard Key that has High Randomness