DOCS-249 removed edit to Rep Set Admin doc

Author: Bob Grabar

draft/core/write-operations.txt

@@ -241,7 +241,11 @@ For more information on replica sets and write operations, see
 :ref:`replica-set-write-concern`, :ref:`replica-set-oplog-sizing`,
 :ref:`replica-set-oplog`,
 :ref:`replica-set-procedure-change-oplog-size`, and
-:ref:`replica-set-resync-stale-member`.
+
+.. todo add this :ref:`replica-set-resync-stale-member` WHEN
+   the "Resyncing a Member of a Replica Set" topic is added to
+   source/administration/replica-sets.txt.
+   (See pull request "DOCS-449 resync stale replica set member")
 
 .. _write-operations-sharded-clustsers:
 

source/administration/replica-sets.txt

@@ -558,18 +558,6 @@ the oplog. For a detailed procedure, see
 
 .. include:: /includes/procedure-change-oplog-size.rst
 
-.. _replica-set-resync-stale-member:
-
-Resyncing a Member of a Replica Set
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-When a member's data falls too far behind the :term:`oplog` to catch up,
-the member and it's data are considered "stale". A member's data is too
-far behind when the oplog on the :term:`primary` has overwritten its
-entries before the member has copied them. When that occurs, you must
-resync the member by removing its data and replacing it with up-to-date
-data.
-
 .. _replica-set-security:
 
 Replica Set Security