edits for style, remove references to shell command.

Author: Ed Costello

source/administration/replica-sets.txt

@@ -54,7 +54,7 @@ configurations.
 
 .. warning::
 
-   The :method:`rs.reconfig()` shell command can force the current
+   The :method:`rs.reconfig()` shell method can force the current
    primary to step down, which causes an :ref:`election <replica-set-elections>`. When the primary
    steps down, the :program:`mongod` closes all client
    connections. While, this typically takes 10-20 seconds, attempt to
@@ -102,7 +102,7 @@ replica set. Use the following sequence of operations in the
    cfg.members[3].priority = 2
    rs.reconfig(cfg)
 
-This configures the set, with the following priority settings: 
+This configures the set, with the following priority settings:
 
 - The first (i.e. )Member ``0`` to a priority of ``0`` so that it can never become :term:`primary`.
 
@@ -169,7 +169,7 @@ not advertise the hidden member in the :dbcommand:`isMaster` or
    that *can* become :term:`primary`. In the above example, if you
    issue the :method:`rs.reconfig()` operation to a member with a
    :data:`priority <members.[n].priority>` of ``0`` the operation will
-   fail. 
+   fail.
 
 .. note::
 
@@ -722,7 +722,7 @@ shell connected to the replica set's :term:`primary`. For descriptions
 of the information displayed by :method:`rs.status()`, see
 :doc:`/reference/replica-status`.
 
-.. note:: 
+.. note::
 
    The :method:`rs.status()` method is a wrapper that runs the
    :dbcommand:`replSetGetStatus` database command.
@@ -758,7 +758,7 @@ To check the current length of replication lag:
          syncedTo: Tue Oct 02 2012 11:33:40 GMT-0400 (EDT)
              = 7475 secs ago (2.08hrs)
 
-  .. note:: 
+  .. note::
 
      The :method:`rs.status()` method is a wrapper around the
      :dbcommand:`replSetGetStatus` database command.
@@ -962,7 +962,7 @@ operational errors:
 In many senses, :ref:`rollbacks <replica-set-rollbacks>` represent a
 graceful recovery from an impossible failover and recovery situation.
 
-Rollbacks occur when 
+Rollbacks occur when
 a primary accepts writes that other members of
 the set do not successfully replicate before the primary steps
 down. When the former primary begins replicating again it performs a

source/reference/replica-configuration.txt

@@ -383,7 +383,7 @@ use the following form:
 
 .. note::
 
-   The :method:`rs.reconfig()` shell command can force the current
+   The :method:`rs.reconfig()` shell method can force the current
    primary to step down and causes an election in some
    situations. When the primary steps down, all clients will
    disconnect. This is by design. While this typically takes 10-20

source/tutorial/deploy-geographically-distributed-replica-set.txt

@@ -215,7 +215,7 @@ To deploy a geographically distributed three-member set:
 
       .. note::
 
-         In some situations, the :method:`rs.reconfig()` shell command
+         In some situations, the :method:`rs.reconfig()` shell method
          can force the current primary to step down and causes an
          election. When the primary steps down, all clients will
          disconnect. This is the intended behavior. While, this
@@ -417,7 +417,7 @@ To deploy a geographically distributed four-member set:
 
       .. note::
 
-         In some situations, the :method:`rs.reconfig()` shell command
+         In some situations, the :method:`rs.reconfig()` shell method
          can force the current primary to step down and causes an
          election. When the primary steps down, all clients will
          disconnect. This is the intended behavior. While, this