ffix

man7/epoll.7

@@ -226,7 +226,6 @@ with
 
 .SH QUESTIONS AND ANSWERS (from linux-kernel)
 
-.RS
 .TP 
 .B Q1 
 What happens if you add the same fd to an epoll_set twice?
@@ -317,10 +316,8 @@ returns a lower number of bytes, you can be sure to have exhausted the read
 I/O space for such file descriptor. Same is valid when writing using the
 .BR write (2)
 function.
-.RE
 
 .SH POSSIBLE PITFALLS AND WAYS TO AVOID THEM
-.RS
 .TP
 .B o Starvation ( Edge Triggered )
 .PP
@@ -335,8 +332,6 @@ in its associated data structure, thereby allowing the application to
 remember which files need to be processed but still round robin amongst
 all the ready files. This also supports ignoring subsequent events you
 receive for fd's that are already ready.
-.PP
-
 .TP
 .B o If using an event cache...  
 .PP
@@ -351,7 +346,6 @@ If you remove the structure and
 the fd for event #13, then your 
 event cache might still say there are events waiting for that fd causing 
 confusion.
-.PP
 .PP 
 One solution for this is to call, during the processing of event 47,
 .BR epoll_ctl ( EPOLL_CTL_DEL )
@@ -361,9 +355,7 @@ then mark its associated
 data structure as removed and link it to a cleanup list. If you find another
 event for fd 13 in your batch processing, you will discover the fd had been
 previously removed and there will be no confusion.
-.PP
 
-.RE
 .SH CONFORMING TO
 .BR epoll (7)
 is a new API introduced in Linux kernel 2.5.44.