diff --git a/source/includes/warning-repair.rst b/source/includes/warning-repair.rst
index e84478f4ef6..0156d4f4e6b 100644
--- a/source/includes/warning-repair.rst
+++ b/source/includes/warning-repair.rst
@@ -3,13 +3,15 @@
    - Before using :dbcommand:`repairDatabase`, make a backup copy of
      the dbpath directory.
 
-   - Avoid running :dbcommand:`repairDatabase` against a replica set.
-     If you are trying to repair a :term:`replica set` member, and you
-     have access to an intact copy of your data (e.g. a recent backup
-     or an intact member of the :term:`replica set`), you should
-     restore from that intact copy (see
-     :doc:`/tutorial/resync-replica-set-member`), and **not** use
-     :dbcommand:`repairDatabase`.
+   - Avoid running :dbcommand:`repairDatabase` and its wrappers against
+     a replica set. To repair a replica set member when you have access
+     to an intact copy of your data (e.g. a recent backup or an intact
+     member of the :term:`replica set`), restore from that intact copy
+     (see :doc:`/tutorial/resync-replica-set-member`). Specific to
+     :option:`mongod --repair` and replica set members, if you run
+     :option:`mongod --repair` against a replica set member and the
+     operation modifies the data or the metadata, you must also perform
+     a full resync of the member to rejoin the replica set.
 
    - Only use the :dbcommand:`repairDatabase` command and associated
      wrappers, including :method:`db.repairDatabase()` and
@@ -17,3 +19,6 @@
      operations remove and do not save any corrupt data during the
      repair process.
 
+   - If repair fails to complete for any reason, you must restart the
+     instance using the :option:`--repair <mongod --repair>` option.
+
diff --git a/source/tutorial/resync-replica-set-member.txt b/source/tutorial/resync-replica-set-member.txt
index 46e6fa7f574..12f1017325f 100644
--- a/source/tutorial/resync-replica-set-member.txt
+++ b/source/tutorial/resync-replica-set-member.txt
@@ -18,10 +18,11 @@ resynchronize the member by removing its data and performing an
 :ref:`initial sync <replica-set-initial-sync>`.
 
 This tutorial addresses both resyncing a stale member and creating a
-new member using seed data from another member. When syncing a member,
-choose a time when the system has the bandwidth to move a large amount
-of data. Schedule the synchronization during a time of low usage or
-during a maintenance window.
+new member using seed data from another member, both of which can be
+used to restore a replica set member. When syncing a member, choose a
+time when the system has the bandwidth to move a large amount of data.
+Schedule the synchronization during a time of low usage or during a
+maintenance window.
 
 MongoDB provides two options for performing an initial sync: