diff options
| author | Dan Jacka <danjacka@gmail.com> | 2014-01-29 14:41:01 +1300 |
|---|---|---|
| committer | Dan Jacka <danjacka@gmail.com> | 2014-01-29 14:41:01 +1300 |
| commit | d11d30c43c7178363504997310bc9a2bf9f1a7a9 (patch) | |
| tree | b2f718077e2b371547ce4a24a444d6d14ac1af51 /docs/designdefense.rst | |
| parent | 78d202a1c7537c135de8c377d63317f823fb8e22 (diff) | |
| download | pyramid-d11d30c43c7178363504997310bc9a2bf9f1a7a9.tar.gz pyramid-d11d30c43c7178363504997310bc9a2bf9f1a7a9.tar.bz2 pyramid-d11d30c43c7178363504997310bc9a2bf9f1a7a9.zip | |
Wee typo fix
Diffstat (limited to 'docs/designdefense.rst')
| -rw-r--r-- | docs/designdefense.rst | 2 |
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, |