From: Alex Chan Date: Sun, 5 Apr 2015 21:42:34 +0000 (+0100) Subject: Fix a few small typos in the docs X-Git-Tag: 2.8~19^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F437%2Fhead;p=thirdparty%2Fjinja.git Fix a few small typos in the docs --- diff --git a/docs/api.rst b/docs/api.rst index 02a8138c..d143ebc5 100644 --- a/docs/api.rst +++ b/docs/api.rst @@ -167,7 +167,7 @@ useful if you want to dig deeper into Jinja2 or :ref:`develop extensions provided as `exc` is raised if something with the generated undefined object is done that the undefined object does not allow. The default exception is :exc:`UndefinedError`. If a `hint` is provided the - `name` may be ommited. + `name` may be omitted. The most common way to create an undefined object is by providing a name only:: @@ -187,7 +187,7 @@ useful if you want to dig deeper into Jinja2 or :ref:`develop extensions return environment.undefined('no first item, sequence was empty') If it the `name` or `obj` is known (for example because an attribute - was accessed) it shold be passed to the undefined object, even if + was accessed) it should be passed to the undefined object, even if a custom `hint` is provided. This gives undefined objects the possibility to enhance the error message. diff --git a/docs/faq.rst b/docs/faq.rst index 00a4d0d7..3869684b 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -135,7 +135,7 @@ the traceback may be incomplete. There is currently no good workaround for Jython or the AppEngine as ctypes is unavailable there and it's not possible to use the debugsupport extension. -If you are working in the Google Appengine development server you can +If you are working in the Google AppEngine development server you can whitelist the ctypes module to restore the tracebacks. This however won't work in production environments:: diff --git a/docs/switching.rst b/docs/switching.rst index 32f04fdd..ab941245 100644 --- a/docs/switching.rst +++ b/docs/switching.rst @@ -4,7 +4,7 @@ Switching from other Template Engines .. highlight:: html+jinja If you have used a different template engine in the past and want to switch -to Jinja2 here is a small guide that shows the basic syntatic and semantic +to Jinja2 here is a small guide that shows the basic syntactic and semantic changes between some common, similar text template engines for Python. Jinja1