summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChristoph Zwerschke <cito@online.de>2011-10-23 18:23:58 +0200
committerRon DuPlain <ron.duplain@gmail.com>2012-03-13 16:57:39 -0700
commita21f2edfc9536c918bae0ef654f9f3ffb1c2b508 (patch)
tree68c1b24bae8eb18d710070a335d643155ec0d384 /docs
parent796ee3ffac160b5747a010344765914a0dfba98a (diff)
downloadjinja2-a21f2edfc9536c918bae0ef654f9f3ffb1c2b508.tar.gz
Fix typos.
Diffstat (limited to 'docs')
-rw-r--r--docs/templates.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/templates.rst b/docs/templates.rst
index 3032e3a..a21e331 100644
--- a/docs/templates.rst
+++ b/docs/templates.rst
@@ -332,7 +332,7 @@ advantage of it, see :ref:`null-master-fallback`.
The filename of the template depends on the template loader. For example the
:class:`FileSystemLoader` allows you to access other templates by giving the
-filename. You can access templates in subdirectories with an slash::
+filename. You can access templates in subdirectories with a slash::
{% extends "layout/default.html" %}
@@ -819,7 +819,7 @@ Jinja2 supports putting often used code into macros. These macros can go into
different templates and get imported from there. This works similar to the
import statements in Python. It's important to know that imports are cached
and imported templates don't have access to the current template variables,
-just the globals by defualt. For more details about context behavior of
+just the globals by default. For more details about context behavior of
imports and includes see :ref:`import-visibility`.
There are two ways to import templates. You can import the complete template