summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2010-10-12 00:24:47 +0000
committerChris McDonough <chrism@agendaless.com>2010-10-12 00:24:47 +0000
commite3be0426582a9478ac8a4bf1d543e314ea4c2b61 (patch)
treebf45a99764495fa25232633d818e206db364dcf0
parent3e338a3835a1d37d328f19c8add42af0afd9533c (diff)
downloadpyramid-e3be0426582a9478ac8a4bf1d543e314ea4c2b61.tar.gz
pyramid-e3be0426582a9478ac8a4bf1d543e314ea4c2b61.tar.bz2
pyramid-e3be0426582a9478ac8a4bf1d543e314ea4c2b61.zip
double however
-rw-r--r--docs/tutorials/bfgwiki/definingviews.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/tutorials/bfgwiki/definingviews.rst b/docs/tutorials/bfgwiki/definingviews.rst
index ecd0bc8fc..6749606c1 100644
--- a/docs/tutorials/bfgwiki/definingviews.rst
+++ b/docs/tutorials/bfgwiki/definingviews.rst
@@ -16,10 +16,10 @@ assumed to return a :term:`response` object.
applications, such as this tutorial, the context is used frequently
within the body of a view method, so it makes sense to use the
two-argument syntax in this application. However, in :term:`url
- dispatch` based applications, however, the context object is rarely
- used in the view body itself, so within code that uses
- URL-dispatch-only, it's common to define views as callables that
- accept only a request to avoid the visual "noise".
+ dispatch` based applications, the context object is rarely used in
+ the view body itself, so within code that uses URL-dispatch-only,
+ it's common to define views as callables that accept only a request
+ to avoid the visual "noise".
We're going to define several :term:`view callable` functions then
wire them into :mod:`repoze.bfg` using some :term:`view