--- EV/README	2009/12/31 06:59:47	1.35
+++ EV/README	2010/10/21 02:46:59	1.36
@@ -52,6 +52,15 @@
        EV::loop EV::LOOP_ONESHOT;  # block until at least one event could be handled
        EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block
 
+BEFORE YOU START USING THIS MODULE
+    If you only need timer, I/O, signal, child and idle watchers and not the
+    advanced functionality of this module, consider using AnyEvent instead,
+    specifically the simplified API described in AE.
+
+    When used with EV as backend, the AE API is as fast as the native EV
+    API, but your programs/modules will still run with many other event
+    loops.
+
 DESCRIPTION
     This module provides an interface to libev
     (<http://software.schmorp.de/pkg/libev.html>). While the documentation
@@ -237,7 +246,7 @@
         When an error occurs or either the timeout or I/O watcher triggers,
         then the callback will be called with the received event set (in
         general you can expect it to be a combination of "EV::ERROR",
-        "EV::READ", "EV::WRITE" and "EV::TIMEOUT").
+        "EV::READ", "EV::WRITE" and "EV::TIMER").
 
         EV::once doesn't return anything: the watchers stay active till
         either of them triggers, then they will be stopped and freed, and
@@ -292,8 +301,7 @@
     same callback for multiple watchers. The event mask is named after the
     type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
     EV::periodic sets EV::PERIODIC and so on, with the exception of I/O
-    events (which can set both EV::READ and EV::WRITE bits), and EV::timer
-    (which uses EV::TIMEOUT).
+    events (which can set both EV::READ and EV::WRITE bits).
 
     In the rare case where one wants to create a watcher but not start it at
     the same time, each constructor has a variant with a trailing "_ns" in