aboutsummaryrefslogtreecommitdiffstats
path: root/doc/manual
diff options
context:
space:
mode:
authorHolger Hans Peter Freyther <zecke@selfish.org>2006-05-27 20:30:17 +0000
committerHolger Hans Peter Freyther <zecke@selfish.org>2006-05-27 20:30:17 +0000
commite15fd00b048820e7aa656dfc9a34a0977fe667d3 (patch)
treecd57a9aa7ff76b8e7c2000153cc95d13277be676 /doc/manual
parenta918a86cabea73974144fbf8183f4b4d723d0c0c (diff)
downloadbitbake-e15fd00b048820e7aa656dfc9a34a0977fe667d3.tar.gz
doc/manual/usermanual.xml: Simplify the sentence
Diffstat (limited to 'doc/manual')
-rw-r--r--doc/manual/usermanual.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/usermanual.xml b/doc/manual/usermanual.xml
index e7942e9a3..eb5eedb19 100644
--- a/doc/manual/usermanual.xml
+++ b/doc/manual/usermanual.xml
@@ -195,7 +195,7 @@ addtask printdate before do_build</screen></para>
<section>
<title>Events</title>
<para><emphasis>NOTE:</emphasis> This is only supported in .bb and .bbclass files.</para>
- <para>BitBake also implements a means of registering event handlers. Events are triggered at certain points during operation, such as, the beginning of operation against a given .bb, the start of a given task, task failure, task success, et cetera. The intent was to make it easy to do things like email notifications on build failure.</para>
+ <para>BitBake allows to install event handlers. Events are triggered at certain points during operation, such as, the beginning of operation against a given .bb, the start of a given task, task failure, task success, et cetera. The intent was to make it easy to do things like email notifications on build failure.</para>
<para><screen>addhandler myclass_eventhandler
python myclass_eventhandler() {
from bb.event import NotHandled, getName