From 417bdbf6903d440333e6e221740d2a9140569bff Mon Sep 17 00:00:00 2001 From: Daniel Watkins Date: Thu, 14 Apr 2011 22:23:43 +0100 Subject: [PATCH] s/falsy// bzr revid: daniel@daniel-watkins.co.uk-20110414212343-aam4fc6nxgkxmnwz --- doc/source/development.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/development.rst b/doc/source/development.rst index 8e37ed744b1..a103893d86c 100644 --- a/doc/source/development.rst +++ b/doc/source/development.rst @@ -71,7 +71,7 @@ An important concept in the search view is that of input. It is both an informal protocol and an abstract type that can be inherited from. Inputs are widgets which can contain user data (a char widget for -instance, or a selection box). They are able of action and of +instance, or a selection box). They are capable of action and of reaction: .. _views-search-registration: @@ -93,9 +93,9 @@ reaction: * Return a context (an object), this is the "normal" response if the input holds a value. - * Return a falsy value (generally ``null``). This value indicates - the input does not contain any value and will not take part in the - research. + * Return a value that evaluates as false (generally ``null``). This + value indicates the input does not contain any value and will not + take part in the research. * Raise :js:class:`openerp.base.search.Invalid` to indicate that it holds a value but this value can not be used in the search