minor hostname clarification

Author: Sam Kleinman

source/tutorial/reconfigure-replica-set-with-unavailable-members.txt

@@ -143,7 +143,7 @@ Reconfigure by "Breaking the Mirror"
 
 This option selects a surviving :term:`replica set` member to be the
 new :term:`primary` and to "seed" a new replica set. In the following
-procedure, the new primary is ``A``. All other members will resync
+procedure, the new primary is ``db0.example.net``. All other members will resync
 from this member.
 
 1. Stop the surviving :program:`mongod` instances. To ensure a clean shutdown, use
@@ -158,15 +158,15 @@ from this member.
    :program:`mongod` instance.
 
 #. Move the data directories (i.e. :setting:`dbpath <mongod --dbpath>`)
-   for all the members except ``A``, so that all the members except ``A``
+   for all the members except ``db0.example.net``, so that all the members except ``db0.example.net``
    have empty data directories. For example:
 
    .. code-block:: sh
 
       mv /data/db /data/db-old
 
 #. Move the data files for ``local`` database (i.e. ``local.*``) so
-   that ``A`` has no local database. For example
+   that ``db0.example.net`` has no local database. For example
 
    .. code-block:: sh
 
@@ -175,15 +175,15 @@ from this member.
 
 #. Start each member of the replica set normally.
 
-#. Connect to ``A`` in a :program:`mongo` shell and run :method:`rs.initiate()`
+#. Connect to ``db0.example.net`` in a :program:`mongo` shell and run :method:`rs.initiate()`
    to initiate the replica set.
 
 #. Add the other set members using :method:`rs.add()`. For example, to
-   add a member running on ``example.net`` at port ``27017``, issue
+   add a member running on ``db1.example.net`` at port ``27017``, issue
    the following command:
 
    .. code-block:: javascript
 
-      rs.add("example.net:27017")
+      rs.add("db1.example.net:27017")
 
-   These members will resync and copy all data from ``A``.
+   These members will resync and copy all data from ``db0.example.net``.