From 8570633214e4749972963ef622b4c86fa8b379fc Mon Sep 17 00:00:00 2001 From: Alex Chan Date: Fri, 3 Apr 2015 20:43:40 +0100 Subject: [PATCH] Fix a few spelling mistakes in the docs --- docs/patterns/appdispatch.rst | 2 +- docs/python3.rst | 2 +- docs/server.rst | 2 +- docs/tutorial/templates.rst | 2 +- docs/upgrading.rst | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/patterns/appdispatch.rst b/docs/patterns/appdispatch.rst index 0b2975a4..3ff99e09 100644 --- a/docs/patterns/appdispatch.rst +++ b/docs/patterns/appdispatch.rst @@ -30,7 +30,7 @@ at :func:`werkzeug.serving.run_simple`:: Note that :func:`run_simple ` is not intended for use in production. Use a :ref:`full-blown WSGI server `. -In order to use the interactive debuggger, debugging must be enabled both on +In order to use the interactive debugger, debugging must be enabled both on the application and the simple server, here is the "hello world" example with debugging and :func:`run_simple `:: diff --git a/docs/python3.rst b/docs/python3.rst index 8318b85b..4d488f16 100644 --- a/docs/python3.rst +++ b/docs/python3.rst @@ -27,7 +27,7 @@ that most libraries (including Werkzeug and Flask) might not quite as stable on Python 3 yet. You might therefore sometimes run into bugs that are usually encoding-related. -The majority of the upgrade pain is in the lower-level libararies like +The majority of the upgrade pain is in the lower-level libraries like Flask and Werkzeug and not in the actual high-level application code. For instance all of the Flask examples that are in the Flask repository work out of the box on both 2.x and 3.x and did not require a single line of diff --git a/docs/server.rst b/docs/server.rst index 3614ff80..c7a7e641 100644 --- a/docs/server.rst +++ b/docs/server.rst @@ -12,7 +12,7 @@ but you can also continue using the :meth:`Flask.run` method. Command Line ------------ -The :command:`flask` command line script (:ref:`cli`) is strongly recommende for +The :command:`flask` command line script (:ref:`cli`) is strongly recommended for development because it provides a superior reload experience due to how it loads the application. The basic usage is like this:: diff --git a/docs/tutorial/templates.rst b/docs/tutorial/templates.rst index 3487a9e1..77991893 100644 --- a/docs/tutorial/templates.rst +++ b/docs/tutorial/templates.rst @@ -3,7 +3,7 @@ Step 6: The Templates ===================== -Now we should start working on the templates. If we were torequest the URLs +Now we should start working on the templates. If we were to request the URLs now, we would only get an exception that Flask cannot find the templates. The templates are using `Jinja2`_ syntax and have autoescaping enabled by default. This means that unless you mark a value in the code with diff --git a/docs/upgrading.rst b/docs/upgrading.rst index 1bf896f5..4f00aa5e 100644 --- a/docs/upgrading.rst +++ b/docs/upgrading.rst @@ -258,7 +258,7 @@ applications automatically, but there might be some cases where it fails to upgrade. What changed? - Blueprints need explicit names. Modules had an automatic name - guesssing scheme where the shortname for the module was taken from the + guessing scheme where the shortname for the module was taken from the last part of the import module. The upgrade script tries to guess that name but it might fail as this information could change at runtime. @@ -296,7 +296,7 @@ Flask 0.6 comes with a backwards incompatible change which affects the order of after-request handlers. Previously they were called in the order of the registration, now they are called in reverse order. This change was made so that Flask behaves more like people expected it to work and -how other systems handle request pre- and postprocessing. If you +how other systems handle request pre- and post-processing. If you depend on the order of execution of post-request functions, be sure to change the order.