standardize casing of shardCollection

Author: Ed Costello

source/reference/command/shardCollection.txt

@@ -13,7 +13,7 @@ shardCollection
 
    .. code-block:: javascript
 
-      { shardcollection: "<db>.<collection>", key: { "<shardkey>": 1 } }
+      { shardCollection: "<db>.<collection>", key: { "<shardkey>": 1 } }
 
    This enables sharding for the collection specified by
    ``<collection>`` in the database named ``<db>``, using the key
@@ -28,7 +28,7 @@ shardCollection
 
    .. warning::
 
-      There's no easy way to disable sharding after running :dbcommand:`shardcollection`. In addition,
+      There's no easy way to disable sharding after running :dbcommand:`shardCollection`. In addition,
       you cannot change shard keys once set. If you must convert a sharded cluster to a :term:`standalone`
       node or :term:`replica set`, you must make a single backup of the entire cluster
       and then restore the backup to the standalone :program:`mongod`

source/tutorial/convert-replica-set-to-replicated-shard-cluster.txt

@@ -376,7 +376,7 @@ Issue the following command:
 .. code-block:: javascript
 
    use admin
-   db.runCommand( { shardcollection : "test.test_collection", key : {"number":1} })
+   db.runCommand( { shardCollection : "test.test_collection", key : {"number":1} })
    { "collectionsharded" : "test.test_collection", "ok" : 1 }
 
 The collection ``test_collection`` is now sharded!

source/tutorial/enforce-unique-keys-for-sharded-collections.txt

@@ -62,7 +62,7 @@ using the ``unique`` constraint, specify the :dbcommand:`shardCollection` comman
 
 .. code-block:: javascript
 
-   db.runCommand( { shardcollection : "test.users" , key : { email : 1 } , unique : true } );
+   db.runCommand( { shardCollection : "test.users" , key : { email : 1 } , unique : true } );
 
 Remember that the ``_id`` field index is always unique. By default, MongoDB
 inserts an ``ObjectId`` into the ``_id`` field. However,

source/use-cases/category-hierarchy.txt

@@ -262,7 +262,7 @@ following operation in the Python/PyMongo console.
 
 .. code-block:: python
 
-    >>> db.command('shardcollection', 'categories', {
+    >>> db.command('shardCollection', 'categories', {
     ...     'key': {'_id': 1} })
     { "collectionsharded" : "categories", "ok" : 1 }
 

source/use-cases/hierarchical-aggregation.txt

@@ -468,7 +468,7 @@ timestamp) on the events collection. Consider the following:
 
 .. code-block:: pycon
 
-   >>> db.command('shardcollection','events', {
+   >>> db.command('shardCollection','events', {
    ... 'key' : { 'userid': 1, 'ts' : 1} } )
    { "collectionsharded": "events", "ok" : 1 }
 
@@ -477,13 +477,13 @@ issue the following group of shard operations in the Python/PyMongo shell:
 
 .. code-block:: python
 
-   db.command('shardcollection', 'stats.daily', {
+   db.command('shardCollection', 'stats.daily', {
         'key': { '_id': 1 } })
-   db.command('shardcollection', 'stats.weekly', {
+   db.command('shardCollection', 'stats.weekly', {
         'key': { '_id': 1 } })
-   db.command('shardcollection', 'stats.monthly', {
+   db.command('shardCollection', 'stats.monthly', {
         'key': { '_id': 1 } })
-   db.command('shardcollection', 'stats.yearly', {
+   db.command('shardCollection', 'stats.yearly', {
         'key': { '_id': 1 } })
 
 You should also update the ``h_aggregate``  map-reduce wrapper to

source/use-cases/inventory-management.txt

@@ -454,9 +454,9 @@ cart and inventory collections:
 
 .. code-block:: pycon
 
-   >>> db.command('shardcollection', 'inventory'
+   >>> db.command('shardCollection', 'inventory'
    ...            'key': { '_id': 1 } )
    { "collectionsharded" : "inventory", "ok" : 1 }
-   >>> db.command('shardcollection', 'cart')
+   >>> db.command('shardCollection', 'cart')
    ...            'key': { '_id': 1 } )
    { "collectionsharded" : "cart", "ok" : 1 }

source/use-cases/metadata-and-asset-management.txt

@@ -471,10 +471,10 @@ Use the following operation at the Python/PyMongo shell:
 
 .. code-block:: pycon
 
-   >>> db.command('shardcollection', 'cms.nodes', {
+   >>> db.command('shardCollection', 'cms.nodes', {
    ...     key : { 'metadata.section': 1, 'metadata.slug' : 1 } })
    { "collectionsharded": "cms.nodes", "ok": 1}
-   >>> db.command('shardcollection', 'cms.assets.files', {
+   >>> db.command('shardCollection', 'cms.assets.files', {
    ...     key : { 'metadata.section': 1, 'metadata.slug' : 1 } })
    { "collectionsharded": "cms.assets.files", "ok": 1}
 
@@ -484,7 +484,7 @@ shard the collection
 
 .. code-block:: pycon
 
-   >>> db.command('shardcollection', 'cms.assets.chunks', {
+   >>> db.command('shardCollection', 'cms.assets.chunks', {
    ...     key : { 'files_id': 1 } })
    { "collectionsharded": "cms.assets.chunks", "ok": 1}
 

source/use-cases/storing-comments.txt

@@ -700,7 +700,7 @@ at the Python/PyMongo console:
 
 .. code-block:: pycon
 
-   >>> db.command('shardcollection', 'comments', {
+   >>> db.command('shardCollection', 'comments', {
    ...     'key' : { 'discussion_id' : 1, 'full_slug': 1 } })
 
 This will return the following response:
@@ -721,7 +721,7 @@ at the Python/PyMongo console:
 
 .. code-block:: python
 
-   >>> db.command('shardcollection', 'comment_pages', {
+   >>> db.command('shardCollection', 'comment_pages', {
    ...     key : { 'discussion_id' : 1, 'page': 1 } })
    { "collectionsharded" : "comment_pages", "ok" : 1 }