--- AnyEvent/README	2007/03/07 17:37:24	1.9
+++ AnyEvent/README	2007/11/06 16:42:05	1.11
@@ -162,8 +162,10 @@
 
   CHILD PROCESS WATCHERS
     You can also listen for the status of a child process specified by the
-    "pid" argument. The watcher will only trigger once. This works by
-    installing a signal handler for "SIGCHLD".
+    "pid" argument (or any child if the pid argument is 0). The watcher will
+    trigger as often as status change for the child are received. This works
+    by installing a signal handler for "SIGCHLD". The callback will be
+    called with the pid and exit status (as returned by waitpid).
 
     Example: wait for pid 1333
 
@@ -179,8 +181,9 @@
 
         The known classes so far are:
 
-           AnyEvent::Impl::Coro      based on Coro::Event, best choise.
-           AnyEvent::Impl::Event     based on Event, also best choice :)
+           EV::AnyEvent              based on EV (an interface to libev, best choice)
+           AnyEvent::Impl::Coro      based on Coro::Event, second best choice.
+           AnyEvent::Impl::Event     based on Event, also second best choice :)
            AnyEvent::Impl::Glib      based on Glib, second-best choice.
            AnyEvent::Impl::Tk        based on Tk, very bad choice.
            AnyEvent::Impl::Perl      pure-perl implementation, inefficient.
@@ -251,7 +254,7 @@
     *rxvt-unicode* also cheats a bit by not providing blocking access to
     condition variables: code blocking while waiting for a condition will
     "die". This still works with most modules/usages, and blocking calls
-    must not be in an interactive appliation, so it makes sense.
+    must not be in an interactive application, so it makes sense.
 
 ENVIRONMENT VARIABLES
     The following environment variables are used by this module: