Use a single-font-style macro (".B", ".I") for a single argument.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man5/core.5 | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/man5/core.5 b/man5/core.5
index 4b7a7926b..9d200b8b2 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -49,7 +49,7 @@ not produced:
.IP * 3
The process does not have permission to write the core file.
(By default, the core file is called
-.IR core
+.I core
or
.IR core.pid ,
where
@@ -126,7 +126,7 @@ option.
(Since Linux 3.7)
.\" commit 046d662f481830e652ac34cd112249adde16452a
The kernel was configured without the
-.BR CONFIG_COREDUMP
+.B CONFIG_COREDUMP
option.
.PP
In addition,
@@ -327,12 +327,12 @@ via this mechanism.
When collecting core dumps via a pipe to a user-space program,
it can be useful for the collecting program to gather data about
the crashing process from that process's
-.IR /proc/[pid]
+.I /proc/[pid]
directory.
In order to do this safely,
the kernel must wait for the program collecting the core dump to exit,
so as not to remove the crashing process's
-.IR /proc/[pid]
+.I /proc/[pid]
files prematurely.
This in turn creates the
possibility that a misbehaving collecting program can block
@@ -357,7 +357,7 @@ The default value for this file is 0.
.\"
.SS Controlling which mappings are written to the core dump
Since kernel 2.6.23, the Linux-specific
-.IR /proc/[pid]/coredump_filter
+.I /proc/[pid]/coredump_filter
file can be used to control which memory segments are written to the
core dump file in the event that a core dump is performed for the
process with the corresponding process ID.
@@ -500,7 +500,7 @@ allow a specified coredump file to be pulled from the
.BR systemd (1)
location into a specified file.
For example, to extract the core dump for PID 2955 shown above to a file named
-.IR core
+.I core
in the current directory, one could use:
.PP
.in +4n
--
2.20.1
