summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-06 07:54:58 +0200
committerTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-06 07:54:58 +0200
commitd79e9c071505ef0532021308c96ab0ab144f3786 (patch)
tree3db669b32c3c031b085410ff7aff5552d68a1eea /docs
parenta62ebd5725338d753d49ff1b6b8bf0fe95b19c92 (diff)
downloadpyramid-d79e9c071505ef0532021308c96ab0ab144f3786.tar.gz
pyramid-d79e9c071505ef0532021308c96ab0ab144f3786.tar.bz2
pyramid-d79e9c071505ef0532021308c96ab0ab144f3786.zip
typo
Diffstat (limited to 'docs')
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 7bc37ac06..488da6b19 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -44,7 +44,7 @@ We were becoming hampered by consequences of its early design mistakes.
Zope's lack of documentation was also difficult to work around: it was hard
to hire smart people to work on Zope applications, because there was no
comprehensive documentation set to point them at which explained "it all" in
-one consumble place, and it was too large and self-inconsistent to document
+one consumable place, and it was too large and self-inconsistent to document
properly. Before :mod:`repoze.bfg` went under development, its authors
obviously looked around for other frameworks that fit the bill. But no
non-Zope framework did. So we embarked on building :mod:`repoze.bfg`.