From c81116eecf7ecc07e25451cbe312c3794c905539 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sat, 16 Jan 2010 09:02:16 +0000 Subject: Meh. --- docs/authorintro.rst | 4 ++-- docs/narr/urlmapping.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/authorintro.rst b/docs/authorintro.rst index 98ec24d92..c811818b8 100644 --- a/docs/authorintro.rst +++ b/docs/authorintro.rst @@ -109,6 +109,6 @@ Simon Oram of Electrosoup, Ian Bicking of the Open Planning Project, Jim Fulton of Zope Corporation, Tom Moroz of the Open Society Institute, and Todd Koym of Environmental Health Sciences. -Special thanks to Guido van Rossum and Tim Peters for Python. +Thanks to Guido van Rossum and Tim Peters for Python. -Special thanks also to Tricia for putting up with me. +Special thanks to Tricia for putting up with me. diff --git a/docs/narr/urlmapping.rst b/docs/narr/urlmapping.rst index da8d6ab9f..7fdfef398 100644 --- a/docs/narr/urlmapping.rst +++ b/docs/narr/urlmapping.rst @@ -42,7 +42,7 @@ application developer, and invokes it. A view callable returns a into a single step. In these systems, a URL can map *directly* to a view callable. This makes them simpler to understand than systems which use distinct subsystems to locate a context and find - a view. However, explicitly using context finding step provides + a view. However, explicitly using a context finding step provides extra flexibility. For example, it makes it possible to protect your application with declarative context-sensitive instance-level :term:`authorization`, which is not well-supported in frameworks -- cgit v1.2.3