--- AnyEvent/README	2009/08/21 11:59:24	1.53
+++ AnyEvent/README	2009/09/01 18:27:46	1.54
@@ -1230,16 +1230,9 @@
           },
        );
 
-       my $time_watcher; # can only be used once
-
-       sub new_timer {
-          $timer = AnyEvent->timer (after => 1, cb => sub {
-             warn "timeout\n"; # print 'timeout' about every second
-             &new_timer; # and restart the time
-          });
-       }
-
-       new_timer; # create first timer
+       my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
+          warn "timeout\n"; # print 'timeout' at most every second
+       });
 
        $cv->recv; # wait until user enters /^q/i
 
@@ -1667,13 +1660,13 @@
     backend easily beats IO::Lambda and POE.
 
     And even the 100% non-blocking version written using the high-level (and
-    slow :) AnyEvent::Handle abstraction beats both POE and IO::Lambda by a
-    large margin, even though it does all of DNS, tcp-connect and socket I/O
-    in a non-blocking way.
+    slow :) AnyEvent::Handle abstraction beats both POE and IO::Lambda
+    higher level ("unoptimised") abstractions by a large margin, even though
+    it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
 
     The two AnyEvent benchmarks programs can be found as eg/ae0.pl and
     eg/ae2.pl in the AnyEvent distribution, the remaining benchmarks are
-    part of the IO::lambda distribution and were used without any changes.
+    part of the IO::Lambda distribution and were used without any changes.
 
 SIGNALS
     AnyEvent currently installs handlers for these signals: