DOCS-120 Copy edits and some markup cleanup

Author: Ed Costello

draft/multi-data-center-awareness.txt

@@ -36,7 +36,7 @@ or a secondary or the *nearest* MongoDB instance in the current topology
 of the network.
 
 Write concerns control how durable the replication of your data is,
-from **fire and forget** to insurance that at least one replica set member
+from insurance that at least one replica set member
 has the data through assurance that a majority or all members of a
 replica set have copies of the data.
 The MongoDB write concern is not comparable to a transaction, it controls

source/applications/replication.txt

@@ -88,10 +88,7 @@ The :data:`~local.system.replset.settings.getLastErrorDefaults` setting affects
    <replica-set-failover>`. Always ensure that your operations have
    specified the required write concern for your application.
 
-.. seealso::
-
-      * :ref:`write-operations-write-concern`
-      * :ref:`connections-write-concern`
+.. seealso:: :ref:`write-operations-write-concern`, :ref:`connections-write-concern`
 
 .. index:: read preference
 .. index:: slaveOk

source/reference/method/sh.addShardTag.txt

@@ -16,37 +16,27 @@ sh.addShardTag()
 
    :method:`sh.addShardTag()` associates a shard with a tag or
    identifier.
-   MongoDB can use these identifiers to direct :term:`chunks <chunk>`
-   which fall within a tagged range to a specific shard.
-   Chunks are associated with a tag range using the 
+   MongoDB uses these identifiers to direct :term:`chunks <chunk>`
+   that fall within a tagged range to specific shards.
+
+   Chunks are associated with a tag range using the
    :method:`sh.addTagRange()` method.
 
    Always issue :method:`sh.addShardTag()` when connected to a
    :program:`mongos` instance.
 
-   .. warning::
-
-      The :program:`mongo` shell does not verify that you are
-      connected to a :program:`mongos` instance.  If you are
-      connected to a :program:`mongod` instance, :method:`sh.addShardTag()`
-      will add the shard tags to a collection in a ``config``
-      database, not to the tags collection on your configuration
-      server.
-
    .. example::
 
-      The following example adds three tags, ``LGA``, ``EWR``, and
-      ``JFK``, to three shards:
+      The following example adds three tags, ``NYC``, ``LAX``, and
+      ``NRT``, to three shards:
 
       .. code-block:: javascript
 
-         sh.addShardTag("shard0000", "LGA")
-         sh.addShardTag("shard0001", "EWR")
-         sh.addShardTag("shard0002", "JFK")
-
-.. seealso::
+         sh.addShardTag("shard0000", "NYC")
+         sh.addShardTag("shard0001", "LAX")
+         sh.addShardTag("shard0002", "NRT")
 
-   * :method:`sh.addTagRange()`
-   * :method:`sh.removeShardTag()`
+   .. seealso::
 
-.. TODO: SERVER-6357 will add dbcommands to replace these methods
+      :method:`sh.addTagRange()`,
+      :method:`sh.removeShardTag()`

source/reference/method/sh.addTagRange.txt

@@ -38,9 +38,7 @@ sh.addTagRange()
    Always issue :method:`sh.addTagRange()` when connected to a
    :program:`mongos` instance.
 
-.. seealso::
+   .. seealso::
 
-   * :method:`sh.addShardTag()`
-   * :method:`sh.removeShardTag()`
-
-.. TODO: SERVER-6357 will add dbcommands to replace these methods
+      :method:`sh.addShardTag()`,
+      :method:`sh.removeShardTag()`

source/reference/method/sh.removeShardTag.txt

@@ -19,9 +19,7 @@ sh.removeShardTag()
    Always issue :method:`sh.removeShardTag()` when connected to a
    :program:`mongos` instance.
 
-.. seealso::
+   .. seealso::
 
-   * :method:`sh.addShardTag()`
-   * :method:`sh.addTagRange()`
-
-.. TODO: SERVER-6357 will add dbcommands to replace these methods
+      :method:`sh.addShardTag()`,
+      :method:`sh.addTagRange()`