summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2011-09-09 03:09:23 -0700
committerSteve Piercy <web@stevepiercy.com>2011-09-09 03:09:23 -0700
commit814455d4475046a24cd11a30805a5db8d4e4ed13 (patch)
tree6b5954a346bb371b582a18da5d8f452e3fdbb2ed /docs
parent82dcba5bf8d6d024f42ded1565d30c314b8e8b4b (diff)
downloadpyramid-814455d4475046a24cd11a30805a5db8d4e4ed13.tar.gz
pyramid-814455d4475046a24cd11a30805a5db8d4e4ed13.tar.bz2
pyramid-814455d4475046a24cd11a30805a5db8d4e4ed13.zip
Insert missing "to".
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/introduction.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index 8694556b2..63f142124 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -618,7 +618,7 @@ A lot is made of the aesthetics of what *kinds* of objects you're allowed to
return from view callables in various frameworks. In a previous section in
this document we showed you that, if you use a :term:`renderer`, you can
usually return a dictionary from a view callable instead of a full-on
-:term:`Response` object. But some frameworks allow you return strings or
+:term:`Response` object. But some frameworks allow you to return strings or
tuples from view callables. When frameworks allow for this, code looks
slightly prettier, because fewer imports need to be done, and there is less
code. For example, compare this: