> The output from "nroff" and "groff" is unchanged, except for the style > of the "()" part of the name of a function. > --- a/man2/write.2 > +++ b/man2/write.2 > @@ -139,7 +139,7 @@ and the write would block. > See > .BR open (2) > for further details on the > -.BR O_NONBLOCK > +.B O_NONBLOCK > flag. > .TP > .BR EAGAIN " or " EWOULDBLOCK > @@ -289,11 +289,11 @@ returning the number of bytes actually transferred. > (This is true on both 32-bit and 64-bit systems.) > .PP > An error return value while performing > -.BR write() > +.BR write () > using direct I/O does not mean the > entire write has failed. Partial data may be written > and the data at the file offset on which the > -.BR write() > +.BR write () > was attempted should be considered inconsistent. > .SH BUGS > According to POSIX.1-2008/SUSv4 Section XSI 2.9.7 I applied this piece manually. Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
