more minor manual mending

ntfsprogs/mkntfs.8.in

@@ -8,7 +8,7 @@ mkntfs \- create an NTFS 1.2 (Windows NT/2000/XP) file system
 .SH SYNOPSIS
 .B mkntfs
 [\fIoptions\fR] \fIdevice \fR[\fInumber\-of\-sectors\fR]
-.P
+.PP
 .B mkntfs
 [
 .B \-C

ntfsprogs/ntfsclone.8.in

@@ -65,9 +65,9 @@ However none of the common utilities supports it.
 This means when you tar, cp, gzip, bzip2, etc a large sparse file
 they will always read the entire file, even if you use the "sparse support"
 options.
-.BR bzip2 
+.B bzip2
 compresses large sparse files much better than
-.BR gzip 
+.B gzip
 but it does so
 also much slower. Moreover neither of them handles large sparse
 files efficiently during uncompression from disk space usage point
@@ -75,7 +75,7 @@ of view.
 At present the most efficient way, both speed and space\-wise, to
 compress and uncompress large sparse files by common tools
 is using
-.BR tar 
+.B tar
 with the options
 .B \-S
 (handle sparse files "efficiently") and
@@ -182,7 +182,7 @@ at the lowest, sector level in this mode too thus more data can be rescued.
 The contents of the unreadable sectors are filled by character '?' and the
 beginning of such sectors are marked by "BadSectoR\\0".
 .TP
-.B \-m, \-\-metadata
+\fB\-m\fR, \fB\-\-metadata\fR
 Clone
 .B ONLY METADATA
 (for NTFS experts). Moreover only cloning to a file is allowed.
@@ -191,7 +191,7 @@ You can't metadata\-only clone to a device, image or standard output.
 \fB\-\-ignore\-fs\-check\fR
 Ignore the result of the filesystem consistency check. This option is allowed
 to be used only with the
-\fB\-m\fR, \fB\-\-metadata\fR
+.B \-\-metadata
 option, for the safety of user's data. The clusters which cause the
 inconsistency are saved too.
 .TP

ntfsprogs/ntfsls.8.in

@@ -133,7 +133,6 @@ Show the contents of all directories beneath the specified directory.
 Unless this options is specified, all files beginning with a dollar sign
 character will not be listed as these files are usually system files.
 .TP
-.B \-v, \-\-verbose
 \fB\-v\fR, \fB\-\-verbose\fR
 Display more debug/warning/error messages.
 .TP

ntfsprogs/ntfsmount.8.in

@@ -6,7 +6,11 @@
 .SH NAME
 ntfsmount \- NTFS module for FUSE.
 .SH SYNOPSIS
-.BI "ntfsmount " device " " mount_point " [\-o " options "]"
+.B ntfsmount
+.I device mount_point
+[
+.B \-o options
+]
 .SH DESCRIPTION
 .B ntfsmount
 is a
@@ -134,14 +138,17 @@ are not set before partitions from /etc/fstab had been mounted.
 .B streams_interface=
 This option controls how the user can access named data streams.  It can be set
 to, one of
-.BR none ", " windows " or " xattr .
+.BR none ,
+.B windows
+or
+.BR xattr .
 If the option is set to
-.BR "none" ,
+.BR none ,
 the user will have no access to the named data streams.  If it's set to
-.BR "windows" ,
+.BR windows ,
 then the user can access them just like in Windows (eg. cat file:stream).
 If it's set to
-.BR "xattr" ,
+.BR xattr ,
 then the named data streams are mapped to xattrs and user can manipulate them
 using
 .B {get,set}fattr

ntfsprogs/ntfsresize.8.in

@@ -122,6 +122,7 @@ smaller size than what you got by this option and depending on several
 factors it might be unable to shrink very close to this theoretical
 size. Although the integrity of your data should be never in risk,
 it's still strongly recommended to make a test run by using the
+.TP
 \fB\-n\fR, \fB\-\-no\-action\fR
 option before real resizing.
 Practically the smallest shrunken size generally is

ntfsprogs/ntfsundelete.8.in

@@ -240,7 +240,7 @@ and
 .BR \-\-byte .
 .sp
 When the file is recovered it will be given its original name, unless the
-.B "\-\-output"
+.B \-\-output
 option is used.
 .TP
 \fB\-v\fR, \fB\-\-verbose\fR