DOCS-11987 repaired node can't rejoin replica set

Author: Isabella Siu

source/includes/warning-repair.rst

@@ -6,14 +6,20 @@
    - 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
+     or an intact member of the :term:`replica set`), you must restore
+     from that intact copy (see
      :doc:`/tutorial/resync-replica-set-member`), and **not** use
-     :dbcommand:`repairDatabase`.
+     :dbcommand:`repairDatabase`. A mongod started with the
+     :dbcommand:`repairDatabase` command or associated wrappers and
+     modified by the operation cannot rejoin its original replica set
+     without a full resync.
 
    - Only use the :dbcommand:`repairDatabase` command and associated
      wrappers, including :method:`db.repairDatabase()` and
      :option:`mongod --repair`, if you have no other options. These
      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.
+

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: