summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-07-05 21:59:29 +0000
committerChris McDonough <chrism@agendaless.com>2009-07-05 21:59:29 +0000
commit9f8e013dd43b975685bed8cc4ceeb3ec2f44bad4 (patch)
tree60644400639f9c39d7654067d5fde7aad5b11442
parent4b23131f4c50e0bc4dd22ce78bd662fbaa1e3c14 (diff)
downloadpyramid-9f8e013dd43b975685bed8cc4ceeb3ec2f44bad4.tar.gz
pyramid-9f8e013dd43b975685bed8cc4ceeb3ec2f44bad4.tar.bz2
pyramid-9f8e013dd43b975685bed8cc4ceeb3ec2f44bad4.zip
Spelling.
-rw-r--r--docs/narr/introduction.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index bc2c2c8a1..b277d8666 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -62,7 +62,7 @@ job of why explaining why they don't use "MVC" acronym:
:mod:`repoze.bfg` uses terminology similar to Django. The skeleton
code generator of :mod:`repoze.bfg` generates a directory layout very
-simliar to the directory layout suggested by the `Django Book
+similar to the directory layout suggested by the `Django Book
<http://www.djangobook.com/>`_ . Additionally, as suggested above,
the concepts of :term:`view`, :term:`model` and :term:`template` are
used by :mod:`repoze.bfg` as they would be by Django.
@@ -112,7 +112,7 @@ it has no reliance on the ZODB package. Likewise, :term:`Django`
tends to make the assumption that you're going to want to store your
application's data in a relational database. :mod:`repoze.bfg` makes
no such assumption; it allows you to use a relational database but
-doesn't enourage or discourage an application developer about such a
+doesn't encourage or discourage an application developer about such a
decision.
Why?