--- libev/ev.3	2012/05/06 19:51:52	1.94
+++ libev/ev.3	2012/05/26 08:52:09	1.95
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14)
+.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -124,7 +124,7 @@
 .\" ========================================================================
 .\"
 .IX Title "LIBEV 3"
-.TH LIBEV 3 "2012-05-06" "libev-4.11" "libev - high performance full featured event loop"
+.TH LIBEV 3 "2012-05-26" "libev-4.11" "libev - high performance full featured event loop"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -4090,7 +4090,7 @@
 .PP
 Proper exception specifications might have to be added to callbacks passed
 to libev: exceptions may be thrown only from watcher callbacks, all
-other callbacks (allocator, syserr, loop acquire/release and periodioc
+other callbacks (allocator, syserr, loop acquire/release and periodic
 reschedule callbacks) must not throw exceptions, and might need a \f(CW\*(C`throw
 ()\*(C'\fR specification. If you have code that needs to be compiled as both C
 and \*(C+ you can use the \f(CW\*(C`EV_THROW\*(C'\fR macro for this:
@@ -4681,7 +4681,7 @@
 If defined to be \f(CW1\fR, libev will use \f(CW\*(C`WSASocket\*(C'\fR to create its internal
 communication socket, which works better in some environments. Otherwise,
 the normal \f(CW\*(C`socket\*(C'\fR function will be used, which works better in other
-enviornments.
+environments.
 .IP "\s-1EV_USE_POLL\s0" 4
 .IX Item "EV_USE_POLL"
 If defined to be \f(CW1\fR, libev will compile in support for the \f(CW\*(C`poll\*(C'\fR(2)