summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-05-21 16:08:18 +0000
committerChris McDonough <chrism@agendaless.com>2009-05-21 16:08:18 +0000
commitca444e177948a3676aeaa159209e2412a2804eee (patch)
treef438efe92b3e5e2967b254db1f5909561d0dc344 /docs
parent5a11e2ad0828b7c763d0c81211f686a85bc0324c (diff)
downloadpyramid-ca444e177948a3676aeaa159209e2412a2804eee.tar.gz
pyramid-ca444e177948a3676aeaa159209e2412a2804eee.tar.bz2
pyramid-ca444e177948a3676aeaa159209e2412a2804eee.zip
Disambiguate.
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/views.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index 1bc6b4419..6f3be2f63 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -358,8 +358,8 @@ decorator syntactic sugar), if you wish:
Using Model Interfaces
----------------------
-Instead of registering your views ``for`` a Python *class*, you can
-optionally register a view for an :term:`interface`. Since an
+Instead of registering your views ``for`` a Python model *class*, you
+can optionally register a view for an :term:`interface`. Since an
interface can be attached arbitrarily to any instance (as opposed to
its identity being implied by only its class), associating a view with
an interface can provide more flexibility for sharing a single view