X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/ea42db4da534aff7a623b651d9287644837b32e2..d9672b1486ca958bdd2c51b6c30dfe94e534ce73:/ev.pod?ds=inline

diff --git a/ev.pod b/ev.pod
index 96a6272..be0128a 100644
--- a/ev.pod
+++ b/ev.pod
@@ -10,7 +10,7 @@ libev - a high performance full-featured event loop written in C
 
 Libev is an event loop: you register interest in certain events (such as a
 file descriptor being readable or a timeout occuring), and it will manage
-these event sources and provide your program events.
+these event sources and provide your program with events.
 
 To do this, it must take more or less complete control over your process
 (or thread) by executing the I<event loop> handler, and will then
@@ -27,7 +27,9 @@ Libev supports select, poll, the linux-specific epoll and the bsd-specific
 kqueue mechanisms for file descriptor events, relative timers, absolute
 timers with customised rescheduling, signal events, process status change
 events (related to SIGCHLD), and event watchers dealing with the event
-loop mechanism itself (idle, prepare and check watchers).
+loop mechanism itself (idle, prepare and check watchers). It also is quite
+fast (see a L<http://libev.schmorp.de/bench.html|benchmark> comparing it
+to libevent).
 
 =head1 CONVENTIONS
 
@@ -295,8 +297,8 @@ As long as your watcher is active (has been started but not stopped) you
 must not touch the values stored in it. Most specifically you must never
 reinitialise it or call its set method.
 
-You cna check wether an event is active by calling the C<ev_is_active
-(watcher *)> macro. To see wether an event is outstanding (but the
+You cna check whether an event is active by calling the C<ev_is_active
+(watcher *)> macro. To see whether an event is outstanding (but the
 callback for it has not been called yet) you cna use the C<ev_is_pending
 (watcher *)> macro.
 
@@ -402,7 +404,7 @@ information given in the last section.
 
 =head2 struct ev_io - is my file descriptor readable or writable
 
-I/O watchers check wether a file descriptor is readable or writable
+I/O watchers check whether a file descriptor is readable or writable
 in each iteration of the event loop (This behaviour is called
 level-triggering because you keep receiving events as long as the
 condition persists. Remember you cna stop the watcher if you don't want to
@@ -469,7 +471,7 @@ the timer, and again will automatically restart it if need be.
 
 =back
 
-=head2 ev_periodic
+=head2 ev_periodic - to cron or not to cron it
 
 Periodic watchers are also timers of a kind, but they are very versatile
 (and unfortunately a bit complex).