Fix typos.

Patch by Al Chu11.

README

@@ -9,7 +9,7 @@ ABOUT
                 http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
    Library Documentation: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod
 
-   Libev is modelled (very losely) after libevent and the Event perl
+   Libev is modelled (very loosely) after libevent and the Event perl
    module, but is faster, scales better and is more correct, and also more
    featureful. And also smaller. Yay.
 

ev.3

@@ -4423,7 +4423,7 @@ For \f(CW\*(C`ev::embed\*(C'\fR watchers this method is called \f(CW\*(C`set_emb
 clashing with the \f(CW\*(C`set (loop)\*(C'\fR method.
 .Sp
 For \f(CW\*(C`ev::io\*(C'\fR watchers there is an additional \f(CW\*(C`set\*(C'\fR method that acepts a
-new event mask only, and internally calls \f(CW\*(C`ev_io_modfify\*(C'\fR.
+new event mask only, and internally calls \f(CW\*(C`ev_io_modify\*(C'\fR.
 .IP "w\->start ()" 4
 .IX Item "w->start ()"
 Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the

ev.c

@@ -2398,7 +2398,7 @@ fd_reify (EV_P)
 {
   int i;
 
-  /* most backends do not modify the fdchanges list in backend_modfiy.
+  /* most backends do not modify the fdchanges list in backend_modify.
    * except io_uring, which has fixed-size buffers which might force us
    * to handle events in backend_modify, causing fdchanges to be amended,
    * which could result in an endless loop.
@@ -3510,7 +3510,7 @@ loop_fork (EV_P)
   if (postfork != 2)
     {
       #if EV_USE_SIGNALFD
-        /* surprisingly, nothing needs to be done for signalfd, accoridng to docs, it does the right thing on fork */
+        /* surprisingly, nothing needs to be done for signalfd, according to docs, it does the right thing on fork */
       #endif
       
       #if EV_USE_TIMERFD

ev.pod

@@ -4270,7 +4270,7 @@ For C<ev::embed> watchers this method is called C<set_embed>, to avoid
 clashing with the C<set (loop)> method.
 
 For C<ev::io> watchers there is an additional C<set> method that acepts a
-new event mask only, and internally calls C<ev_io_modfify>.
+new event mask only, and internally calls C<ev_io_modify>.
 
 =item w->start ()
 

ev_iouring.c

@@ -67,7 +67,7 @@
  *    later versions not only bump this to 32k, but also can handle
  *    an unlimited amount of events, so this only affects the batch size.
  * i) unlike linux aio, you *can* register more then the limit
- *    of fd events. while early verisons of io_uring signalled an overflow
+ *    of fd events. while early versions of io_uring signalled an overflow
  *    and you ended up getting wet. 5.5+ does not do this anymore.
  * j) but, oh my! it had exactly the same bugs as the linux aio backend,
  *    where some undocumented poll combinations just fail. fortunately,

ev_linuxaio.c

@@ -93,7 +93,7 @@
 
 #include <sys/syscall.h> /* no glibc wrappers */
 
-/* aio_abi.h is not versioned in any way, so we cannot test for its existance */
+/* aio_abi.h is not versioned in any way, so we cannot test for its existence */
 #define IOCB_CMD_POLL 5
 
 /* taken from linux/fs/aio.c. yup, that's a .c file.

import_libevent

@@ -3,7 +3,7 @@
 LE=../libevent-1.4.3-stable
 
 if ! [ -e evbuffer.c ]; then
-   echo do not run this programm unless you know what you are doing
+   echo do not run this program unless you know what you are doing
    exit 1
 fi