summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2014-01-28 21:16:51 -0500
committerChris McDonough <chrism@plope.com>2014-01-28 21:16:51 -0500
commitb93e7e19c97954ec0013df98e0360371f9434643 (patch)
treeb2f718077e2b371547ce4a24a444d6d14ac1af51 /docs
parentea8961e64a7ae2c384883fe4ae4812edf290afc2 (diff)
parent99757cca5328f16a71d7548499b5397051e18863 (diff)
downloadpyramid-b93e7e19c97954ec0013df98e0360371f9434643.tar.gz
pyramid-b93e7e19c97954ec0013df98e0360371f9434643.tar.bz2
pyramid-b93e7e19c97954ec0013df98e0360371f9434643.zip
Merge branch 'master' of github.com:Pylons/pyramid
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 2f3c14881..418ceb08f 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -419,7 +419,7 @@ hierarchical: sections within sections within sections, ad infinitum. If you
want your URLs to indicate this structure, and the structure is indefinite
(the number of nested sections can be "N" instead of some fixed number), a
resource tree is an excellent way to model this, even if the backend is a
-relational database. In this situation, the resource tree a just a site
+relational database. In this situation, the resource tree is just a site
structure.
Traversal also offers better composability of applications than URL dispatch,