fix codespell findings

docs/appcontext.rst

@@ -119,7 +119,7 @@ The context will have the same lifetime as an activity, such as a request, CLI
 command, or ``with`` block. Various callbacks and signals registered with the
 app will be run during the context.
 
-When a Flask application handles a request, it pushes a requet context
+When a Flask application handles a request, it pushes a request context
 to set the active application and request data. When it handles a CLI command,
 it pushes an app context to set the active application. When the activity ends,
 it pops that context. Proxy objects like :data:`.request`, :data:`.session`,

docs/quickstart.rst

@@ -462,7 +462,7 @@ broad overview. First it needs to be imported.
 If you have some experience with Python you might be wondering how that object
 can be global when Flask handles multiple requests at a time. The answer is
 that :data:`.request` is actually a proxy, pointing at whatever request is
-currently being handled by a given worker, which is managed interanlly by Flask
+currently being handled by a given worker, which is managed internally by Flask
 and Python. See :doc:`/appcontext` for much more information.
 
 The current request method is available in the :attr:`~.Request.method`

docs/templating.rst

@@ -183,7 +183,7 @@ For template tests, use the :meth:`~.Flask.template_test` decorator or
 method.
 
 The same methods also exist on :class:`.Blueprint`, prefixed with ``app_`` to
-indicate that the registered functions will be avaialble to all templates, not
+indicate that the registered functions will be available to all templates, not
 only when rendering from within the blueprint.
 
 The Jinja environment is also available as :attr:`~.Flask.jinja_env`. It may be