DOCS-536 moved arbiter procedure to procedures section

Author: Bob Grabar

source/administration/replica-sets.txt

@@ -274,52 +274,7 @@ arbiters and the other members of the replica set are secure. See the
 documentation for :doc:`/administration/ssl` for more information.
 As with all MongoDB components, run arbiters on secure networks.
 
-Because arbiters do not hold a copy of the data, they have minimal
-resource requirements and do not require dedicated hardware.
-
-To prevent tied :term:`elections <election>`, do not add an arbiter to a
-set if the set already has an odd number of voting members.
-
-Add an Arbiter
-``````````````
-
-1. Create a data directory for the arbiter. The directory is used for
-   configuration information. It *will not* hold database collection data.
-   The following example creates the ``/data/arb`` data directory:
-
-   .. code-block:: sh
-
-      mkdir /data/arb
-
-#. Start the arbiter, making sure to specify the replica set and the
-   data directory. Consider the following example:
-
-   .. code-block:: sh
-
-      mongod --port 30000 --dbpath /data/arb --replSet rs
-
-#. In a :program:`mongo` shell connected to the :term:`primary`, add the
-   arbiter to the replica set by issuing a command that uses the
-   following syntax:
-
-   .. code-block:: javascript
-
-      rs.addArb("<hostname>:<port>")
-
-   For example, if the arbiter runs on example.net:30000, you would
-   issue this command:
-
-   .. code-block:: javascript
-
-      rs.addArb("example.net:30000")
-
-.. seealso::
-
-   - :setting:`replSet`
-
-   - :option:`--replSet <mongod --replSet>`
-
-   - :method:`rs.addArb()`
+To add an arbiter, see :ref:`replica-set-procedure-add-arbiter`.
 
 .. index:: replica set members; non-voting
 .. _replica-set-non-voting-members:
@@ -472,7 +427,7 @@ number. :method:`rs.reconfig()` will not change the value of
 .. _replica-set-member-priority-configuration:
 
 Adjusting Priority
-~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~
 
 To change the value of the :data:`members[n].priority` value in the
 replica set configuration, use the following sequence of commands in
@@ -527,6 +482,50 @@ of the member with the highest :data:`members[n].priority` setting.
    <replica-set-reconfiguration-usage>` example revolves around
    changing the priorities of the :data:`members` of a replica set.
 
+.. _replica-set-procedure-add-arbiter:
+
+Adding an Arbiter
+~~~~~~~~~~~~~~~~~
+
+For a description of :term:`arbiters <arbiter>` and their purpose in
+:term:`replica sets <replica set>`, see :ref:`replica-set-arbiters`.
+
+To prevent tied :term:`elections <election>`, do not add an arbiter to a
+set if the set already has an odd number of voting members.
+
+Because arbiters do not hold a copies of collection data, they have minimal
+resource requirements and do not require dedicated hardware.
+
+1. Create a data directory for the arbiter. The directory is used for
+   configuration information. It *will not* hold database collection data.
+   The following example creates the ``/data/arb`` data directory:
+
+   .. code-block:: sh
+
+      mkdir /data/arb
+
+#. Start the arbiter, making sure to specify the replica set and the
+   data directory. Consider the following example:
+
+   .. code-block:: sh
+
+      mongod --port 30000 --dbpath /data/arb --replSet rs
+
+#. In a :program:`mongo` shell connected to the :term:`primary`, add the
+ß   arbiter to the replica set by issuing the :method:`rs.addArb()`
+   method, which uses the following syntax:
+
+   .. code-block:: javascript
+
+      rs.addArb("<hostname>:<port>")
+
+   For example, if the arbiter runs on example.net:30000, you would
+   issue this command:
+
+   .. code-block:: javascript
+
+      rs.addArb("example.net:30000")
+
 .. _replica-set-procedure-change-oplog-size:
 
 Changing Oplog Size