Use a single-font-style macro (".B", ".I") for a single argument.
Separate the "()" part from the name of a function.
The output from "nroff" and "groff" is unchanged, except for the style
of the "()" part of the name of a function.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man2/vfork.2 | 2 +-
man2/vm86.2 | 2 +-
man2/write.2 | 6 +++---
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/man2/vfork.2 b/man2/vfork.2
index eddce6a5a..92399a3dc 100644
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -218,7 +218,7 @@ is designed to be implementable on systems that lack an MMU.)
On systems where memory is constrained,
.BR vfork ()
avoids the need to temporarily commit memory (see the description of
-.IR /proc/sys/vm/overcommit_memory
+.I /proc/sys/vm/overcommit_memory
in
.BR proc (5))
in order to execute a new program.
diff --git a/man2/vm86.2 b/man2/vm86.2
index 3317af1b0..53020bd6b 100644
--- a/man2/vm86.2
+++ b/man2/vm86.2
@@ -42,7 +42,7 @@ and a new
.BR vm86 ()
was introduced.
The definition of
-.IR "struct vm86_struct"
+.I "struct vm86_struct"
was changed
in 1.1.8 and 1.1.9.
.PP
diff --git a/man2/write.2 b/man2/write.2
index 5118a1550..b842c2100 100644
--- 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
--
2.20.1
