From 648096888e4f61fa82dbe6aba63f9ac40590631a Mon Sep 17 00:00:00 2001 From: Nick Geoghegan Date: Fri, 19 Apr 2013 14:27:49 +0200 Subject: [PATCH] Missing full stop and "to" --- source/tutorial/shard-gridfs-data.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/tutorial/shard-gridfs-data.txt b/source/tutorial/shard-gridfs-data.txt index 70b7a30a62f..a396b1d0dec 100644 --- a/source/tutorial/shard-gridfs-data.txt +++ b/source/tutorial/shard-gridfs-data.txt @@ -14,7 +14,7 @@ collection. The ``files`` collection is typically small, and only contains metadata. None of the required keys for GridFS lend themselves to an even distribution in a sharded situation. If you *must* shard the ``files`` collection, use the ``_id`` field -possibly in combination with an application field +possibly in combination with an application field. Leaving ``files`` unsharded means that all the file metadata documents live on one shard. For production GridFS stores you *must* @@ -32,8 +32,8 @@ issue commands similar to the following: db.runCommand( { shardCollection : "test.fs.chunks" , key : { files_id : 1 , n : 1 } } ) -You may also want shard using just the ``file_id`` field, as in the -following operation: +You may also want to shard using just the ``file_id`` field, as in +the following operation: .. code-block:: javascript