changing :func: to :method:

Author: Andrew Leung

source/administration/sharding.txt

@@ -125,7 +125,7 @@ more detail or use the following procedure as a quick starting point:
          replicaSetName/<seed1>,<seed2>,<seed3>
 
       For example, if the name of the replica set is "``repl0``", then
-      your :func:`sh.addShard` command would be:
+      your :method:`sh.addShard` command would be:
 
       .. code-block:: javascript
 
@@ -136,7 +136,7 @@ more detail or use the following procedure as a quick starting point:
    MongoDB enables sharding on a per-database basis. This is only a
    meta-data change and will not redistribute your data. To enable
    sharding for a given database, use the :dbcommand:`enableSharding`
-   command or the :func:`sh.enableSharding()` shell function.
+   command or the :method:`sh.enableSharding()` shell function.
 
    .. code-block:: javascript
 
@@ -165,7 +165,7 @@ more detail or use the following procedure as a quick starting point:
    collections must belong to a database for which you have enabled
    sharding. When you shard a collection, you also choose the shard
    key. To shard a collection, run the :dbcommand:`shardCollection`
-   command or the :func:`sh.shardCollection()` shell helper.
+   command or the :method:`sh.shardCollection()` shell helper.
 
    .. code-block:: javascript
 
@@ -223,7 +223,7 @@ procedure:
 
 #. First, you need to tell the cluster where to find the individual
    shards. You can do this using the :dbcommand:`addShard` command or
-   the :func:`sh.addShard()` helper:
+   the :method:`sh.addShard()` helper:
 
    .. code-block:: javascript
 
@@ -266,7 +266,7 @@ procedure:
       following form: the replica set name, followed by a forward
       slash, followed by a comma-separated list of seeds for the
       replica set. For example, if the name of the replica set is
-      "myapp1", then your :func:`sh.addShard` command might resemble:
+      "myapp1", then your :method:`sh.addShard` command might resemble:
 
       .. code-block:: javascript
 
@@ -312,7 +312,7 @@ The procedure to remove a shard is as follows:
    shard name when you first ran the :dbcommand:`addShard` command. If not,
    you can find out the name of the shard by running the
    :dbcommand:`listshards` or :dbcommand:`printShardingStatus`
-   commands or the :func:`sh.status()` shell helper.
+   commands or the :method:`sh.status()` shell helper.
 
    The following examples will remove a shard named ``mongodb0`` from the cluster.
 
@@ -444,11 +444,11 @@ You may want to split chunks manually if:
    keys are between ``250`` and ``500`` are in a single chunk.
 
 To determine the current chunk ranges across the cluster, use
-:func:`sh.status()` or :func:`db.printShardingStatus()`. 
+:method:`sh.status()` or :method:`db.printShardingStatus()`. 
 
 To split chunks manually, use the :dbcommand:`split` command with
 operators: ``middle`` and ``find``. The equivalent shell helpers are
-:func:`sh.splitAt()` or :func:`sh.splitFind()`.
+:method:`sh.splitAt()` or :method:`sh.splitFind()`.
 
 .. example::
 
@@ -459,13 +459,13 @@ operators: ``middle`` and ``find``. The equivalent shell helpers are
 
       sh.splitFind( { "zipcode": 63109 } )
 
-:func:`sh.splitFind()` will split the chunk containing the queried
+:method:`sh.splitFind()` will split the chunk containing the queried
 document into two equal sized chunks, dividing the chunk using the
-balancer algorithm. The :func:`sh.splitFind()` query may not be based
+balancer algorithm. The :method:`sh.splitFind()` query may not be based
 on the shard key, but it makes sense to use the shard key, and
 including the shard key will expedite the operation.
 
-Use :func:`sh.splitAt()` to split a chunk in two using the queried
+Use :method:`sh.splitAt()` to split a chunk in two using the queried
 document as the partition point:
 
 .. code-block:: javascript
@@ -574,7 +574,7 @@ To modify the chunk size, use the following procedure:
 
       use config
 
-#. Issue the following :func:`save() <db.collection.save()>`
+#. Issue the following :method:`save() <db.collection.save()>`
    operation:
 
    .. code-block:: javascript
@@ -718,7 +718,7 @@ Here's what this tells you:
 
   .. note::
 
-     Use the :func:`sh.isBalancerRunning()` helper in the
+     Use the :method:`sh.isBalancerRunning()` helper in the
      :program:`mongo` shell to determine if the balancer is
      running, as follows:
 
@@ -746,7 +746,7 @@ be able to migrate chunks:
 
       use config
 
-#. Use an operation modeled on the following example :func:`update()
+#. Use an operation modeled on the following example :method:`update()
    <db.collection.update()>` operation to modify the balancer's
    window:
 
@@ -800,10 +800,10 @@ all migration, use the following procedure:
 
    If a balancing round is in progress, the system will complete the
    current round before the balancer is officially disabled.  After
-   disabling, you can use the :func:`sh.getBalancerState()` shell
+   disabling, you can use the :method:`sh.getBalancerState()` shell
    function to determine whether the balancer is in fact disabled.
 
-The above process and the :func:`sh.setBalancerState()` helper provide a
+The above process and the :method:`sh.setBalancerState()` helper provide a
 wrapper on the following process, which may be useful if you need to
 run this operation from a driver that does not have helper functions:
 
@@ -1168,6 +1168,6 @@ operation:
   for the duration of the backup procedure.
 
 Confirm that the balancer is not active using the
-:func:`sh.getBalancerState()` method before starting a backup
+:method:`sh.getBalancerState()` method before starting a backup
 operation. When the backup procedure is complete you can reactivate
 the balancer process.