--- libev/ev.pod	2009/08/26 17:15:05	1.266
+++ libev/ev.pod	2009/08/29 08:15:11	1.268
@@ -706,8 +706,8 @@
 =item ev_loop (loop, int flags)
 
 Finally, this is it, the event handler. This function usually is called
-after you initialised all your watchers and you want to start handling
-events.
+after you have initialised all your watchers and you want to start
+handling events.
 
 If the flags argument is specified as C<0>, it will not return until
 either no event watchers are active anymore or C<ev_unloop> was called.
@@ -2132,10 +2132,14 @@
 the signal mask to whatever "default" you expect (all clear is a good
 choice usually).
 
-In current versions of libev, you can ensure that the signal mask is not
-blocking any signals (except temporarily, so thread users watch out) by
-specifying the C<EVFLAG_NOSIGNALFD> when creating the event loop. This is
-not guaranteed for future versions, however.
+The simplest way to ensure that the signal mask is reset in the child is
+to install a fork handler with C<pthread_atfork> that resets it. That will
+catch fork calls done by libraries (such as the libc) as well.
+
+In current versions of libev, you can also ensure that the signal mask is
+not blocking any signals (except temporarily, so thread users watch out)
+by specifying the C<EVFLAG_NOSIGNALFD> when creating the event loop. This
+is not guaranteed for future versions, however.
 
 =head3 Watcher-Specific Functions and Data Members