DOCS-502 edits per review comments redux

Author: Bob Grabar

source/core/replication-internals.txt

@@ -31,14 +31,14 @@ In replication, the ``local`` database is used to store internal replication
 data for each member of a :term:`replica set`. The ``local`` database contains the
 following collections used for replication:
 
-.. data:: system.replset
+.. data:: local.system.replset
 
    This stores the replica set's configuration object. To view the
    object's configuration information, issue :method:`rs.conf()` from
    the :program:`mongo` shell. You can also query this collection
    directly.
 
-.. data:: oplog.rs
+.. data:: local.oplog.rs
 
    This is the capped collection that is the :term:`oplog`. You set its
    size at creation using the :setting:`oplogSize` setting. To change
@@ -48,7 +48,7 @@ following collections used for replication:
    :ref:`replica-set-oplog-sizing` topic in the :doc:`/core/replication`
    document.
 
-.. data:: replset.minvalid
+.. data:: local.replset.minvalid
 
    This contains an object used internally by replica sets to track sync
    status.
@@ -58,31 +58,20 @@ the following collections:
 
 - On the master:
 
-  .. data:: oplog.$main
+  .. data:: local.oplog.$main
 
      This is the oplog for the master-slave configuration.
 
-  .. data:: slaves
+  .. data:: local.slaves
 
      This contains information about each slave.
 
 - On each slave:
 
-  .. data:: sources
+  .. data:: local.sources
 
      This contains information about the slave's master server.
 
-.. note:: In MongoDB versions 1.6 and higher, use replica sets instead
-   of the master-slave configuration. 
-
-.. note::
-
-   The local database also can include these collections:
-
-   - me
-
-   - pair.*. This is for replica pairs, which are deprecated.
-
 .. index:: replica set; oplog
 .. _replica-set-internals-oplog: