*** empty log message ***

10 years ago · 8171ab506d
parent 900d99df83
commit 8171ab506d
1 changed files with 1 additions and 1 deletions
--- a/ev.pod
+++ b/ev.pod
@ -688,7 +688,7 @@ name, you can call it anytime, but it makes most sense after forking, in
 the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
 child before resuming or calling C<ev_run>.

-Again, you I<have> to call it on I<any> loop that you want to re-use after 
+Again, you I<have> to call it on I<any> loop that you want to re-use after
 a fork, I<even if you do not plan to use the loop in the parent>. This is
 because some kernel interfaces *cough* I<kqueue> *cough* do funny things
 during fork.