--- libev/ev.3	2007/11/24 16:33:23	1.18
+++ libev/ev.3	2007/11/24 16:57:38	1.19
@@ -1777,20 +1777,20 @@
 \&    SV *self; /* contains this struct */  \e
 \&    SV *cb_sv, *fh /* note no trailing ";" */
 .Ve
-.IP "\s-1EV_CB_DECLARE\s0(type)" 4
-.IX Item "EV_CB_DECLARE(type)"
+.IP "\s-1EV_CB_DECLARE\s0 (type)" 4
+.IX Item "EV_CB_DECLARE (type)"
 .PD 0
-.IP "\s-1EV_CB_INVOKE\s0(watcher,revents)" 4
-.IX Item "EV_CB_INVOKE(watcher,revents)"
-.IP "ev_set_cb(ev,cb)" 4
-.IX Item "ev_set_cb(ev,cb)"
+.IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4
+.IX Item "EV_CB_INVOKE (watcher, revents)"
+.IP "ev_set_cb (ev, cb)" 4
+.IX Item "ev_set_cb (ev, cb)"
 .PD
 Can be used to change the callback member declaration in each watcher,
 and the way callbacks are invoked and set. Must expand to a struct member
 definition and a statement, respectively. See the \fIev.v\fR header file for
 their default definitions. One possible use for overriding these is to
-avoid the ev_loop pointer as first argument in all cases, or to use method
-calls instead of plain function calls in \*(C+.
+avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use
+method calls instead of plain function calls in \*(C+.
 .Sh "\s-1EXAMPLES\s0"
 .IX Subsection "EXAMPLES"
 For a real-world example of a program the includes libev