--- AnyEvent/lib/AnyEvent.pm	2008/04/25 14:07:53	1.88
+++ AnyEvent/lib/AnyEvent.pm	2008/04/25 14:24:29	1.90
@@ -972,10 +972,10 @@
 performance becomes really bad with lots of file descriptors (and few of
 them active), of course, but this was not subject of this benchmark.
 
-The C<Event> module has a relatively high setup and callback invocation cost,
-but overall scores on the third place.
+The C<Event> module has a relatively high setup and callback invocation
+cost, but overall scores in on the third place.
 
-C<Glib>'s memory usage is quite a bit bit higher, but it features a
+C<Glib>'s memory usage is quite a bit higher, but it features a
 faster callback invocation and overall ends up in the same class as
 C<Event>. However, Glib scales extremely badly, doubling the number of
 watchers increases the processing time by more than a factor of four,
@@ -1007,14 +1007,15 @@
 
 =over 4
 
-=item * Using EV through AnyEvent is faster than any other event loop, but most
-event loops have acceptable performance with or without AnyEvent.
+=item * Using EV through AnyEvent is faster than any other event loop
+(even when used without AnyEvent), but most event loops have acceptable
+performance with or without AnyEvent.
 
 =item * The overhead AnyEvent adds is usually much smaller than the overhead of
-the actual event loop, only with extremely fast event loops such as the EV
+the actual event loop, only with extremely fast event loops such as EV
 adds AnyEvent significant overhead.
 
-=item * You should simply avoid POE like the plague if you want performance or
+=item * You should avoid POE like the plague if you want performance or
 reasonable memory usage.
 
 =back