Simple documentation corrections, mostly typos.

docs/foreword.rst

@@ -44,7 +44,7 @@ object relational mappers, form validation, upload handling, various open
 authentication technologies and more.
 
 Since Flask is based on a very solid foundation there is not a lot of code
-in Flask itself.  As such it's easy to adapt even for lage applications
+in Flask itself.  As such it's easy to adapt even for large applications
 and we are making sure that you can either configure it as much as
 possible by subclassing things or by forking the entire codebase.  If you
 are interested in that, check out the :ref:`becomingbig` chapter.

docs/quickstart.rst

@@ -616,7 +616,7 @@ Storing cookies::
         resp.set_cookie('username', 'the username')
         return resp
 
-Note that cookies are set on response objects.  Since you normally you
+Note that cookies are set on response objects.  Since you normally
 just return strings from the view functions Flask will convert them into
 response objects for you.  If you explicitly want to do that you can use
 the :meth:`~flask.make_response` function and then modify it.

docs/signals.rst

@@ -83,7 +83,7 @@ context are appended to it.
 
 Additionally there is a convenient helper method
 (:meth:`~blinker.base.Signal.connected_to`).  that allows you to
-temporarily subscribe a function to a signal with is a context manager on
+temporarily subscribe a function to a signal with a context manager on
 its own.  Because the return value of the context manager cannot be
 specified that way one has to pass the list in as argument::