From a587b0899cfafb04ea726a6e9316777aa7d0ebda Mon Sep 17 00:00:00 2001
From: root <root>
Date: Fri, 11 Oct 2013 07:50:43 +0000
Subject: *** empty log message ***

---
 ev.pod | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ev.pod b/ev.pod
index 92f0d42..7eb9ea9 100644
--- 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.
-- 
cgit v1.2.3