Fixed a few typos in the docs

Author: jonashaag

docs/source/topics/gridfs.rst

@@ -38,21 +38,25 @@ Use :class:`~django_mongodb_engine.fields.GridFSField` to store "nameless" blobs
 besides documents that would normally go into the document itself.
 
 All that's kept in the document is a reference (an ObjectId) to the GridFS blobs
-which is retrieved on demand.
+which are retrieved on demand.
 
 Assuming you want to store a 10MiB blob "in" each document, this is what you
 *shouldn't* do::
 
+   # DON'T DO THIS
    class Bad(models.Model):
-      # DON'T DO THIS
+      blob = models.TextField()
+
+   # NEITHER THIS
+   class EventWorse(models.Model):
        blob = models.CharField(max_length=10*1024*1024)
 
 Instead, use :class:`~django_mongodb_engine.fields.GridFSField`::
 
    class Better(models.Model):
        blob = GridFSField()
 
-A GridFSField may be feeded with anything that PyMongo can handle, that is,
+A GridFSField may be fed with anything that PyMongo can handle, that is,
 (preferably) file-like objects and strings.
 
 You'll always get a :class:`~gridfs.grid_file.GridOut` for documents from the

docs/source/tutorial.rst

@@ -26,9 +26,9 @@ and excluding data.
 Perhaps a good way to get used to non-relational style data modeling is to ask
 yourself "What would I never do in SQL".
 
-Because most relational databases lack proper list data structures you
-may typically model the Posts ⇔ Tags ⇔ Comments relationship using three
-models/tables, one table one table per entity type.
+Because most relational databases lack proper list data structures you may
+typically model the Posts ⇔ Tags ⇔ Comments relationship using three
+models/tables, one table per entity type.
 
 Organizing your data using multiple relationships is the exact opposite of what
 we will do for our non-relational data model: Have one single collection (table)