orbit-oss/flask
4
4
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #591 from finbarrocallaghan/master

Browse source 
fixed some typos
This commit is contained in:
Armin Ronacher 2012-10-07 03:54:58 -07:00
commit 39329bfc07
6 changed files with 17 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/appcontext.rst
View file

@ -37,7 +37,7 @@ context local.
Purpose of the Application Context
----------------------------------
The main reason for the application's context existance is that in the
The main reason for the application's context existence is that in the
past a bunch of functionality was attached to the request context in lack
of a better solution. Since one of the pillar's of Flask's design is that
you can have more than one application in the same Python process.
@ -58,7 +58,7 @@ Creating an Application Context
To make an application context there are two ways. The first one is the
implicit one: whenever a request context is pushed, an application context
will be created alongside if this is necessary. As a result of that, you
can ignore the existance of the application context unless you need it.
can ignore the existence of the application context unless you need it.
The second way is the explicit way using the
:meth:`~flask.Flask.app_context` method::

2
docs/upgrading.rst
View file

@ -210,7 +210,7 @@ Manual Error Handler Attaching
While it is still possible to attach error handlers to
:attr:`Flask.error_handlers` it's discouraged to do so and in fact
deprecated. In generaly we no longer recommend custom error handler
deprecated. In general we no longer recommend custom error handler
attaching via assignments to the underlying dictionary due to the more
complex internal handling to support arbitrary exception classes and
blueprints. See :meth:`Flask.errorhandler` for more information.