From 12daf9e069b66aef5715a14641fc269367c091dd Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sat, 19 Dec 2009 19:04:29 +0000 Subject: Wording. --- docs/designdefense.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/designdefense.rst b/docs/designdefense.rst index 0d964f17f..e98dfb00d 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -363,7 +363,7 @@ In this `TOPP Engineering blog entry Ian Bicking asserts that the way :mod:`repoze.bfg` uses a Zope interface to represent an HTTP request method adds too much indirection for not enough gain. We agreed in general, and for this -reason, :mod:`repoze.bfg` version 1.1 adds :term:`view predicate` and +reason, :mod:`repoze.bfg` version 1.1 added :term:`view predicate` and :term:`route predicate` modifiers to view configuration. Predicates are request-specific (or :term:`context` -specific) matching narrowers which don't use interfaces. Instead, each predicate uses a @@ -407,8 +407,8 @@ For more information about predicates, see Many "prebaked" predicates exist. However, use of only "prebaked" predicates, however, doesn't entirely meet Ian's criterion. He would like to be able to match a request using a lambda or another function -which interrogates the request imperatively. In 1.2, we acommodate -this by allowing people to define "custom" view predicates: +which interrogates the request imperatively. In version 1.2, we +acommodate this by allowing people to define "custom" view predicates: .. code-block:: python :linenos: -- cgit v1.2.3