summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorCarlos de la Guardia <cguardia@yahoo.com>2013-09-15 00:07:01 -0500
committerCarlos de la Guardia <cguardia@yahoo.com>2013-09-15 00:07:01 -0500
commit2d2b438f2d3c44dc5a7c49a64d71e8653c0eac60 (patch)
tree0148ce3cbfa87b8a0f8e76bf69f8f344e3001cf3 /docs/designdefense.rst
parent4fa49f72be3b61182c76eca353e6f37fdb625227 (diff)
downloadpyramid-2d2b438f2d3c44dc5a7c49a64d71e8653c0eac60.tar.gz
pyramid-2d2b438f2d3c44dc5a7c49a64d71e8653c0eac60.tar.bz2
pyramid-2d2b438f2d3c44dc5a7c49a64d71e8653c0eac60.zip
typo
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 02f868e5d..a8f1c409a 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -822,7 +822,7 @@ dismiss this feature in favor of branching and merging because applications
written in their framework of choice aren't extensible out of the box in a
comparably fundamental way.
-While :app:`Pyramid` application are fundamentally extensible even if you
+While :app:`Pyramid` applications are fundamentally extensible even if you
don't write them with specific extensibility in mind, if you're moderately
adventurous, you can also take it a step further. If you learn more about
the :term:`Zope Component Architecture`, you can optionally use it to expose