man pages: fix spacing between man page name & section number

Most have standardized correctly, but fix a few latent ones.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>

diff --git a/disk-utils/cfdisk.8 b/disk-utils/cfdisk.8
index ff95aa9dc073c0537754e66b9021ad76913adb3b..68cec94921f82ac2340ffa6412f26710a6392e9d 100644 (file)
--- a/disk-utils/cfdisk.8
+++ b/disk-utils/cfdisk.8
@@ -190,7 +190,7 @@ enables libsmartcols debug output.
 .BR sfdisk (8),
 .BR parted (8),
 .BR partprobe (8),
-.BR partx(8)
+.BR partx (8)
 .SH AUTHOR
 Karel Zak <kzak@redhat.com>
 .PP

diff --git a/disk-utils/sfdisk.8 b/disk-utils/sfdisk.8
index 79424c5260b67b54dd6864ecb5ccc01541775c2d..0c13a48850aa8805657adf496def9d7ae44a0961 100644 (file)
--- a/disk-utils/sfdisk.8
+++ b/disk-utils/sfdisk.8
@@ -441,7 +441,7 @@ The GPT header can later be restored by:
 .RE
 Note that \fBsfdisk\fR since version 2.26 no longer provides the \fB\-I\fR option to
 restore sectors.
-.B dd (1)
+.BR dd (1)
 provides all necessary functionality.
 
 .SH COLORS
@@ -487,7 +487,7 @@ enables libsmartcols debug output.
 .BR cfdisk (8),
 .BR parted (8),
 .BR partprobe (8),
-.BR partx(8)
+.BR partx (8)
 
 .SH AUTHOR
 Karel Zak <kzak@redhat.com>

diff --git a/misc-utils/kill.1 b/misc-utils/kill.1
index 2d8c8837704f41ec5d5f0803ff1b2d70485b83da..d3dc20e0d57284100d788039b7db40655b4748b3 100644 (file)
--- a/misc-utils/kill.1
+++ b/misc-utils/kill.1
@@ -118,7 +118,7 @@ It is not possible to send a signal to an explicitly selected thread in a
 multithreaded process using the
 .BR kill (2)
 syscall.  If
-.BR kill(2)
+.BR kill (2)
 is used to send a signal to a thread group, then the kernel selects an arbitrary
 member of the thread group that has not blocked the signal.  For more details
 see

diff --git a/misc-utils/logger.1 b/misc-utils/logger.1
index 017a66bf0a90dd1ca6373775af520cbdd0a4519a..e30af9897999df6dcf39d81deb968af16ca675fd 100644 (file)
--- a/misc-utils/logger.1
+++ b/misc-utils/logger.1
@@ -75,7 +75,7 @@ command's PID.  The use of \fB\-\-id=$$\fR
 Note that the system logging infrastructure (for example \fBsystemd\fR when
 listening on /dev/log) may follow local socket credentials to overwrite the
 PID specified in the message.
-.BR logger(1)
+.BR logger (1)
 is able to set those socket credentials to the given \fIid\fR, but only if you
 have root permissions and a process with the specified PID exists, otherwise
 the socket credentials are not modified and the problem is silently ignored.

diff --git a/sys-utils/losetup.8 b/sys-utils/losetup.8
index dbc909594b00e1de1e129567eef17c007a735708..b614416df3b3592e2011aa0531e6bdfc241ddf7b 100644 (file)
--- a/sys-utils/losetup.8
+++ b/sys-utils/losetup.8
@@ -151,7 +151,7 @@ Display help text and exit.
 
 .SH ENCRYPTION
 .B Cryptoloop is no longer supported in favor of dm-crypt.
-.B For more details see cryptsetup (8).
+.B For more details see cryptsetup(8).
 
 .SH RETURN VALUE
 .B losetup