DOCS-941 review edits II

Author: Bob Grabar

source/administration/replica-sets.txt

@@ -344,6 +344,8 @@ the event of a network partition.
 Chained Replication
 ~~~~~~~~~~~~~~~~~~~
 
+.. versionadded:: 2.0
+
 Chained replication occurs when a :term:`secondary` member replicates
 from another secondary member instead of from the :term:`primary`. This
 might be the case, for example, if a secondary selects its replication
@@ -352,9 +354,7 @@ target based on ping time and if the closest member is another secondary.
 Chained replication can reduce load on the primary. But depending on the network
 topology, chained replication can also result in increased replication lag.
 
-.. versionadded:: 2.2.2
-
-You can use the
+Beginning with version 2.2.2, you can use the
 :data:`chainingAllowed <local.system.replset.settings.chainingAllowed>`
 setting in
 :doc:`/reference/replica-configuration` to disable chained replication
@@ -664,7 +664,7 @@ You can use the following sequence of commands:
 
 .. note:: If chained replication is disabled, you still can use
    :dbcommand:`replSetSyncFrom` to specify that a secondary replicates
-   from the primary. But that configuration will last only until the
+   from another secondary. But that configuration will last only until the
    secondary recalculates which member to sync from.
 
 .. _replica-set-procedure-change-oplog-size:

source/reference/replica-configuration.txt

@@ -228,6 +228,8 @@ Configuration Variables
 
    **Default**: true
 
+   .. versionadded:: 2.2.2
+
    When this value is ``true``, the replica set allows :term:`secondary`
    members to replicate from other secondary members. When this value is
    ``false``, secondaries can replicate only from the :term:`primary`.