diff --git a/source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt b/source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt
index 45b02327b78..bdf3d9b1c45 100644
--- a/source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt
+++ b/source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt
@@ -8,7 +8,7 @@ Overview
 --------
 
 This document describes a procedure for taking a backup of all
-components of a sharded cluster. This procedure uses file system
+components in a sharded cluster. This procedure uses file system
 snapshots to capture a copy of the :program:`mongod` instance. An
 alternate procedure that uses :program:`mongodump` to create binary
 database dumps when file-system snapshots are not available. See
@@ -25,11 +25,11 @@ Procedure
 ---------
 
 In this procedure, you will stop the cluster balancer and take a backup
-up of the :term:`config database`, and then take backups of each
+of the :term:`config database`, and then take backups of each
 shard in the cluster using a file-system snapshot tool. If you need an
 exact moment-in-time snapshot of the system, you will need to stop all
 application writes before taking the filesystem snapshots; otherwise
-the snapshot will only approximate a moment of in time.
+the snapshot will only approximate a moment in time.
 
 For approximate point-in-time snapshots, you can improve the quality
 of the backup while minimizing impact on the cluster by taking the
@@ -47,7 +47,7 @@ shard.
       It is essential that you stop the balancer before creating
       backups. If the balancer remains active, your resulting backups
       could have duplicate data or miss some data, as :term:`chunks
-      <chunk>` migrate while recording backups.
+      <chunk>` may migrate while preforming the backup.
 
 #. Lock one member of each replica set in each shard so that your
    backups reflect the state of your database at the nearest possible
@@ -75,7 +75,7 @@ shard.
 
       mongodump --db config
 
-#. Back up the replica set members of the shards that you locked. You
+#. Back up the replica set members of the shards that you have locked. You
    may back up the shards in parallel. For each shard, create a
    snapshot. Use the procedures in
    :doc:`/tutorial/backup-databases-with-filesystem-snapshots`.