From fa1dec9ec10e4aca0b1bb69c544e6dc64e297fdf Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Sun, 2 Jan 2011 20:15:38 -0700 Subject: add word chapters --- docs/narr/views.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/narr/views.rst') diff --git a/docs/narr/views.rst b/docs/narr/views.rst index 81f3e644f..e1a7c4679 100644 --- a/docs/narr/views.rst +++ b/docs/narr/views.rst @@ -17,11 +17,12 @@ request made to your application. that implements a view *callable*, and the process of view *lookup*. -The :ref:`urldispatch_chapter`, and :ref:`traversal_chapter` describes how, -using information from the :term:`request`, a :term:`context` resource is -computed. But the context resource itself isn't very useful without an -associated :term:`view callable`. A view callable returns a response to a -user, often using the context resource to do so. +The :ref:`urldispatch_chapter`, and :ref:`traversal_chapter` chapters +describes how, using information from the :term:`request`, a +:term:`context` resource is computed. But the context resource itself +isn't very useful without an associated :term:`view callable`. A view +callable returns a response to a user, often using the context resource +to do so. The job of actually locating and invoking the "best" :term:`view callable` is the job of the :term:`view lookup` subsystem. The view lookup subsystem -- cgit v1.2.3