DOCS-449 review edits

Author: Bob Grabar

source/administration/replica-sets.txt

@@ -574,7 +574,7 @@ data.
 
 To do so, use one of the following approaches:
 
-- Restart the machine with an empty data directory and let MongoDB's
+- Restart the :program:`mongod` with an empty data directory and let MongoDB's
   automatic syncing feature restore the data. This approach requires
   fewer steps but can take longer to replace the data.
 
@@ -594,7 +594,7 @@ Automatically Resync a Stale Member
 
 This procedure relies on MongoDB's automatic syncing feature to restore
 the data on the stale member. For an overview of how MongoDB syncs
-replica sets, see :ref:`replica-set-syncing`.
+:term:`replica sets <replica set>`, see :ref:`replica-set-syncing`.
 
 To resync the stale member:
 
@@ -617,7 +617,9 @@ To resync the stale member:
       mongod --dbpath /data/db/ --replSet rsProduction
 
    MongoDB resyncs the member. Resyncing may take a long time, depending on
-   the size of the database and speed of the network.
+   the size of the database and speed of the network. Also,
+   this puts a load on the member being synced from. That
+   member might not be able to keep a working set in memory.
 
 .. index:: replica set; resync
 .. _replica-set-resync-by-copying:
@@ -627,7 +629,7 @@ Resync by Copying Data from Another Member
 
 This approach uses the data directory of an existing member to "seed"
 the stale member. The data must be recent enough to allow the new member
-to catch up with the :term:`primary` member's :term:`oplog`.
+to catch up with the :term:`oplog`.
 
 To resync by copying data from another member, use one of the following
 approaches:
@@ -636,14 +638,11 @@ approaches:
   snapshot to the stale member. Use the snapshot procedures in
   :doc:`/administration/backups`.
 
-- Lock another member's database with the :method:`db.fsyncLock()`
-  command, copy that data, and then restore the data to the stale
+- Lock another member's data with the :method:`db.fsyncLock()`
+  command, copy all of the data in the data directory, and then restore the data to the stale
   member. Use the procedures for backup storage in
   :doc:`/administration/backups`.
 
-- Use the :dbcommand:`copydb` and :dbcommand:`clone` commands, as
-  described in :doc:`/tutorial/copy-databases-between-instances`.
-
 .. _replica-set-security:
 
 Replica Set Security