DOCS-11628 Add missing word and clarify phrasing

Author: kallimachos

source/core/gridfs.txt

@@ -74,11 +74,11 @@ can update the metadata field that indicates "latest" status in an
 atomic update after uploading the new version of the file, and later
 remove previous versions if needed.
 
-Furthermore, if your files are all smaller the 16 MB :limit:`BSON
-Document Size` limit, consider storing the file manually within a
-single document instead of using GridFS. You may use the BinData data
-type to store the binary data. See your :doc:`drivers
-</applications/drivers>` documentation for details on using BinData.
+Furthermore, if your files are all smaller than the 16 MB :limit:`BSON
+Document Size` limit, consider storing each file in a single document instead
+of using GridFS. You may use the BinData data type to store the binary data.
+See your :doc:`drivers </applications/drivers>` documentation for details on
+using BinData.
 
 .. index:: GridFS; initialize
 .. _gridfs-use:
@@ -316,12 +316,12 @@ index.
 ``files_id`` is an :term:`objectid` and changes
 :ref:`monotonically<shard-key-monotonic>`.
 
-You cannot use :doc:`/core/hashed-sharding` when sharding the ``chunks`` 
+You cannot use :doc:`/core/hashed-sharding` when sharding the ``chunks``
 collection.
 
 The ``files`` collection is small and only contains metadata. None of the
-required keys for GridFS lend themselves to an even distribution in a 
-sharded environment. If you *must* shard the ``files`` collection, use the 
+required keys for GridFS lend themselves to an even distribution in a
+sharded environment. If you *must* shard the ``files`` collection, use the
 ``_id`` field, possibly in combination with an application field.
 
 Leaving ``files`` unsharded allows all the file metadata documents to live