3 files changed, 5 insertions, 5 deletions
diff --git a/man5/core.5 b/man5/core.5
index 99f325c3f3..a4da8139c0 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -30,7 +30,7 @@ A list of the signals which cause a process to dump core can be found in
 .BR signal (7).
 
 A process can set its soft
-.BR RLIMIT_CORE
+.B RLIMIT_CORE
 resource limit to place an upper limit on the size of the core dump file
 that will be produced if it receives a "core dump" signal; see
 .BR getrlimit (2)
diff --git a/man5/dir_colors.5 b/man5/dir_colors.5
index bc52812919..740dc272e7 100644
--- a/man5/dir_colors.5
+++ b/man5/dir_colors.5
@@ -256,7 +256,7 @@ To do so, you will have to use the
 .BR LEFTCODE ,
 .BR RIGHTCODE ,
 and
-.BR ENDCODE
+.B ENDCODE
 definitions.
 .PP
 When writing out a filename,
diff --git a/man5/proc.5 b/man5/proc.5
index 86e4f9d423..b90f9142e2 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -1381,7 +1381,7 @@ valid for 30 seconds.
 .TP
 .I /proc/sys/kernel/cap-bound
 This file holds the value of the kernel
-.IR "capability bounding set"
+.I "capability bounding set"
 (expressed as a signed decimal number).
 This set is ANDed against the capabilities permitted to a process
 during
@@ -1729,7 +1729,7 @@ Values are:
 In mode 0, calls of
 .BR mmap (2)
 with
-.BR MAP_NORESERVE
+.B MAP_NORESERVE
 set are not checked, and the default check is very weak,
 leading to the risk of getting a process "OOM-killed".
 Under Linux 2.4 any non-zero value implies mode 1.
@@ -1768,7 +1768,7 @@ and the amount of time spent in idle process (seconds).
 This string identifies the kernel version that is currently running.
 It includes the contents of
 .IR /proc/sys/kernel/ostype ,
-.IR /proc/sys/kernel/osrelease
+.I /proc/sys/kernel/osrelease
 and
 .IR /proc/sys/kernel/version .
 For example: