DOCS-270 migrate design concepts

source/administration/replica-sets.txt

@@ -46,11 +46,16 @@ configurations.
 .. warning::
 
    The :method:`rs.reconfig()` shell command can force the current
-   primary to step down, which causes an election. When the primary
+   primary to step down, which causes an :ref:`election <replica-set-elections>`. When the primary
    steps down, the :program:`mongod` closes all client
    connections. While, this typically takes 10-20 seconds, attempt to
    make these changes during scheduled maintenance periods.
 
+.. seealso::
+
+   - The :ref:`replica-set-elections` topic in the :doc:`/core/replication` document
+   - The :ref:`replica-set-election-internals` topic in the :doc:`/core/replication-internals` document
+
 .. index:: replica set members; secondary only
 .. _replica-set-secondary-only-members:
 .. _replica-set-secondary-only-configuration:
@@ -69,9 +74,10 @@ these members from ever becoming primary.
 
 To configure a member as secondary-only, set its
 :data:`members[n].priority` value to ``0``. Any member with a
-:data:`members[n].priority` equal to ``0`` will never seek election and
-cannot become primary in any situation. For more information on priority
-levels, see :ref:`replica-set-node-priority`.
+:data:`members[n].priority` equal to ``0`` will never seek
+:ref:`election <replica-set-elections>` and cannot become primary in any
+situation. For more information on priority levels, see
+:ref:`replica-set-node-priority`.
 
 As an example of modifying member priorities, assume a four-member
 replica set with member ``_id`` values of: ``0``, ``1``, ``2``, and
@@ -107,10 +113,10 @@ This sets the following:
    If your replica set has an even number of members, add an
    :ref:`arbiter <replica-set-arbiters>` to ensure that
    members can quickly obtain a majority of votes in an
-   :ref:`election <replica-set-elections>` for primary.
+   election for primary.
 
 .. seealso:: :data:`members[n].priority` and :ref:`Replica Set
-   Reconfiguration <replica-set-reconfiguration-usage>`.
+   Reconfiguration <replica-set-reconfiguration-usage>`
 
 .. index:: replica set members; hidden
 .. _replica-set-hidden-members:
@@ -183,8 +189,8 @@ the amount of slave delay to apply:
 
 - The size of the oplog is sufficient to capture *more than* the
   number of operations that typically occur in that period of
-  time. See the section on :ref:`oplog sizing
-  <replica-set-oplog-sizing>` for more information.
+  time. For more information on oplog size, see the
+  :ref:`replica-set-oplog-sizing` topic in the :doc:`/core/replication` document.
 
 Delayed members must have a :term:`priority` set to ``0`` to prevent
 them from becoming primary in their replica sets. Also these members
@@ -233,7 +239,7 @@ Arbiters
 
 Arbiters are special :program:`mongod` instances that do not hold a
 copy of the data and thus cannot become primary. Arbiters exist solely
-participate in :term:`elections <election>`.
+participate in :ref:`elections <replica-set-elections>`.
 
 .. note::
 
@@ -290,15 +296,14 @@ Non-Voting
 ~~~~~~~~~~
 
 You may choose to change the number of votes that each member has in
-:term:`elections <election>` for :term:`primary`. In general, all
+:ref:`elections <replica-set-elections>` for :term:`primary`. In general, all
 members should have only 1 vote to prevent intermittent ties, deadlock,
 or the wrong members from becoming :term:`primary`. Use :ref:`replica
 set priorities <replica-set-node-priority>` to control which members
 are more likely to become primary.
 
-To disable a member's ability to vote in :ref:`elections
-<replica-set-elections>` use the following command sequence in the
-:program:`mongo` shell.
+To disable a member's ability to vote in elections, use the following
+command sequence in the :program:`mongo` shell.
 
 .. code-block:: javascript
 
@@ -454,7 +459,7 @@ number. :method:`rs.reconfig()` will not change the value of
 .. warning::
 
    Any replica set configuration change can trigger the current
-   :term:`primary` to step down, which forces an :term:`election`. This
+   :term:`primary` to step down, which forces an :ref:`election <replica-set-elections>`. This
    causes the current shell session, and clients connected to this replica set,
    to produce an error even when the operation succeeds.
 
@@ -486,7 +491,7 @@ the new configuration.
 
 If a member has :data:`members[n].priority` set to ``0``, it is
 ineligible to become :term:`primary` and will not seek
-elections. :ref:`Hidden members <replica-set-hidden-members>`,
+election. :ref:`Hidden members <replica-set-hidden-members>`,
 :ref:`delayed members <replica-set-delayed-members>`, and
 :ref:`arbiters <replica-set-arbiters>` all have :data:`members[n].priority`
 set to ``0``.
@@ -741,4 +746,7 @@ data to a :term:`BSON` file that you can view using
 You can prevent rollbacks by ensuring safe writes by using
 the appropriate :term:`write concern`.
 
-.. seealso:: :ref:`Replica Set Elections <replica-set-elections>`
+.. seealso::
+
+   - The :ref:`replica-set-elections` topic in the :doc:`/core/replication` document
+   - The :ref:`replica-set-election-internals` topic in the :doc:`/core/replication-internals` document