diff --git a/source/tutorial/recover-data-following-unexpected-shutdown.txt b/source/tutorial/recover-data-following-unexpected-shutdown.txt
index dd678ca335f..18c2c286d7e 100644
--- a/source/tutorial/recover-data-following-unexpected-shutdown.txt
+++ b/source/tutorial/recover-data-following-unexpected-shutdown.txt
@@ -12,7 +12,7 @@ To prevent data inconsistency and corruption, always shut down the
 database cleanly, and use the :ref:`durability journaling
 <setting-journal>`. The journal writes data to disk every 100
 milliseconds by default, and ensures that MongoDB will be able to
-recover a constant state even in the case of an unclean shutdown due to
+recover to a consistent state even in the case of an unclean shutdown due to
 power loss or other system failure.
 
 If you do not have journaling enabled, use the following procedure to
@@ -27,6 +27,13 @@ recover data that may be in an inconsistent state.
    "Control-C" (when running :program:`mongod` in interactive mode,)
    or ``kill $(pidof mongod)`` or ``kill -2 $(pidof mongod)``.
 
+.. warning:: Recovering a member of a replica set
+
+   Do not use this procedure to recover a member of a :term:`replica set`.
+   Instead you should either restore from a :doc:`backup </administration/backups>` 
+   or re-sync from an intact member of the set.
+
+
 Process
 -------