More typo fixes

docs/becomingbig.rst

@@ -33,7 +33,7 @@ scale applications:
     also requires that the whole application is imported when the system
     initializes or certain URLs will not be available right away.   A
     better solution would be to have one module with all URLs in there and
-    specifing the target functions explictliy or by name and importing
+    specifing the target functions explictly or by name and importing
     them when needed.
 -   switch to explicit request object passing.  This makes it more to type
     (because you now have something to pass around) but it makes it a

docs/patterns.rst

@@ -195,7 +195,7 @@ SQLAlchemy in Flask
 
 Many people prefer `SQLAlchemy`_ for database access.  In this case it's
 encouraged to use a package instead of a module for your flask application
-and drop the modules into a separate module (:ref:`larger-applications`).
+and drop the models into a separate module (:ref:`larger-applications`).
 Although that is not necessary but makes a lot of sense.
 
 There are three very common ways to use SQLAlchemy.  I will outline each
@@ -225,10 +225,11 @@ Here the example `database.py` module for your application::
     def init_db():
         Base.metadata.create_all(bind=engine)
 
-To define your models, subclass the `Base` class the above code generated.
+To define your models, just subclass the `Base` class that was created by
+the code above.
 
 To use SQLAlchemy in a declarative way with your application, you just
-have to put the following code into your application module  Flask will
+have to put the following code into your application module.  Flask will
 automatically remove database sessions at the end of the request for you::
 
     from yourapplication.database import db_session