summaryrefslogtreecommitdiff
path: root/docs/narr/traversal.rst
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2011-01-01 12:17:07 -0700
committerCasey Duncan <casey.duncan@gmail.com>2011-01-01 12:17:07 -0700
commitf69e1986538ff12fbea36f378b9a2e74cfd11aaf (patch)
tree489915a490d7aa4dbd48c73b57ed38d00a950027 /docs/narr/traversal.rst
parent9423c199cd87f15526b09a49b1c2bd4d029258ea (diff)
downloadpyramid-f69e1986538ff12fbea36f378b9a2e74cfd11aaf.tar.gz
pyramid-f69e1986538ff12fbea36f378b9a2e74cfd11aaf.tar.bz2
pyramid-f69e1986538ff12fbea36f378b9a2e74cfd11aaf.zip
clarify opening paragraph
Diffstat (limited to 'docs/narr/traversal.rst')
-rw-r--r--docs/narr/traversal.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/narr/traversal.rst b/docs/narr/traversal.rst
index fa8d7d7ee..d1d695dce 100644
--- a/docs/narr/traversal.rst
+++ b/docs/narr/traversal.rst
@@ -9,10 +9,11 @@ nested dictionary-like objects. Traversal is done by using each segment
of the path portion of the URL to navigate through the :term:`resource
tree`. You might think of this as looking up files and directories in a
file system. Traversal walks down the path until it finds a published
-"directory" or "file". The resource we find as the result of a
-traversal becomes the :term:`context`. Then, the :term:`view lookup`
+resource, analogous to a file system "directory" or "file". The
+resource found as the result of a traversal becomes the
+:term:`context` of the :term:`request`. Then, the :term:`view lookup`
subsystem is used to find some view code willing "publish" this
-resource.
+resource by generating a :term:`response`.
Using :term:`Traversal` to map a URL to code is optional. It is often
less easy to understand than :term:`URL dispatch`, so if you're a rank