DOCS-351 adding replica set configuration examples

Author: Sam Kleinman

source/reference/replica-configuration.txt

@@ -221,11 +221,10 @@ Configuration Variables
 Example Document
 ----------------
 
-The following document is a prototypical representation a MongoDB
-replica set configuration document. Square brackets (e.g. ``[`` and
+the following document is a prototypical representation a mongodb
+replica set configuration document. square brackets (e.g. ``[`` and
 ``]``) enclose all optional fields.
 
-
 .. code-block:: javascript
 
    {
@@ -234,53 +233,108 @@ replica set configuration document. Square brackets (e.g. ``[`` and
        {
          _id : <ordinal>,
          host : <hostname[:port]>
-         [, arbiterOnly : true]
-         [, buildIndexes : <bool>]
+         [, arbiteronly : true]
+         [, buildindexes : <bool>]
          [, hidden : true]
          [, priority: <priority>]
-         [, tags: {loc1 : desc1, loc2 : desc2, ..., locN : descN}]
-         [, slaveDelay : <n>]
+         [, tags: {loc1 : desc1, loc2 : desc2, ..., locn : descn}]
+         [, slavedelay : <n>]
          [, votes : <n>]
        }
        , ...
      ],
      [settings: {
-       [getLastErrorDefaults: <lasterrdefaults>]
-       [, getLastErrorModes : <modes>]
+       [getlasterrordefaults: <lasterrdefaults>]
+       [, getlasterrormodes : <modes>]
      }]
    }
 
 .. _replica-set-reconfiguration-usage:
 
-Use
+use
 ---
 
-Most modifications of replica set configuration use the
-:program:`mongo` shell. Consider the following example:
+most modifications of replica set configuration use the
+:program:`mongo` shell. consider the following:
+
+.. example::
+
+   Given the following replica set configuration:
+
+   .. code-block:: javascript
+
+      {
+          "_id" : "rs0",
+          "version" : 1,
+          "members" : [
+                   {
+                           "_id" : 0,
+                           "host" : "mongodb0.example.net:27017",
+                   },
+                   {
+                           "_id" : 1,
+                           "host" : "mongodb1.example.net:27017"
+                   },
+                   {
+                           "_id" : 2,
+                           "host" : "mongodb2.example.net:27017",
+                   }
+           ]
+      }
+
+   And the following reconfiguration operation:
+
+   .. code-block:: javascript
+
+      cfg = rs.conf()
+      cfg.members[0].priority = 0.5
+      cfg.members[1].priority = 2
+      cfg.members[2].priority = 2
+      rs.reconfig(cfg)
+
+   This operation begins by saving the current replica set
+   configuration to the local variable ``cfg`` using the
+   :func:`rs.conf()` method. Then it adds priority values to the
+   :term:`document` where the :data:`members[n]._id` field has a value
+   of ``0``, ``1``, or ``2``. Finally, it calls the
+   :func:`rs.reconfig()` method with the argument of ``cfg`` to
+   initialize this new configuration. The replica set configuration
+   after this operation will resemble the following:
+
+   .. code-block:: javascript
+
+      {
+          "_id" : "rs0",
+          "version" : 1,
+          "members" : [
+                   {
+                           "_id" : 0,
+                           "host" : "mongodb0.example.net:27017",
+                           "priority" : 0.5
+                   },
+                   {
+                           "_id" : 1,
+                           "host" : "mongodb1.example.net:27017"
+                           "priority" : 2
+                   },
+                   {
+                           "_id" : 2,
+                           "host" : "mongodb2.example.net:27017",
+                           "priority" : 1
+                   }
+           ]
+      }
 
-.. code-block:: javascript
 
-   cfg = rs.conf()
-   cfg.members[0].priority = 0.5
-   cfg.members[1].priority = 2
-   cfg.members[2].priority = 2
-   rs.reconfig(cfg)
-
-This operation begins by saving the current replica set configuration
-to the local variable ``cfg`` using the :func:`rs.conf()`
-method. Then it adds priority values to the :term:`document`
-where the :data:`members[n]._id` field has a value of ``0``, ``1``, or
-``2``. Finally, it calls the :func:`rs.reconfig()` method with the
-argument of ``cfg`` to initialize this new configuration.
-
-Using this "dot notation," you can modify any existing setting or
-specify any of optional :ref:`replica set configuration variables
+Using the "dot notation" demonstrated in the above example, you can
+modify any existing setting or specify any of optional :ref:`replica
+set configuration variables
 <replica-set-configuration-variables>`. Until you run
 ``rs.reconfig(cfg)`` at the shell, no changes will take effect. You
 can issue ``cfg = rs.conf()`` at any time before using
-:func:`rs.reconfig()` to undo your changes and start from the
-current configuration. If you issue ``cfg`` as an operation at any
-point, the :program:`mongo` shell at any point will output the complete
+:func:`rs.reconfig()` to undo your changes and start from the current
+configuration. If you issue ``cfg`` as an operation at any point, the
+:program:`mongo` shell at any point will output the complete
 :term:`document` with modifications for your review.
 
 The :func:`rs.reconfig()` operation has a "force" option, to make it