summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2010-10-24 19:44:27 +0000
committerroot <root>2010-10-24 19:44:27 +0000
commit4a5e45f8ba1fac859b445f13d79ce4987bde0c27 (patch)
tree9a44e22d03ca2df31296103b436d66e53d6464f6 /ev.pod
parent1a1e52705cd6c8b3536f6acc70c8627cc0bf314f (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/ev.pod b/ev.pod
index d0c4c51..60707b0 100644
--- a/ev.pod
+++ b/ev.pod
@@ -3111,7 +3111,7 @@ Cleanup watchers are called just before the event loop they are registered
with is being destroyed.
While there is no guarantee that the event loop gets destroyed, cleanup
-watchers provide a convenient method to install cleanup watchers for your
+watchers provide a convenient method to install cleanup hooks for your
program, worker threads and so on - you just to make sure to destroy the
loop when you want them to be invoked.