11622 clean up rarer mandoc lint warnings

@@ -5,11 +5,10 @@
 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
 .TH PCFS 7FS "Nov 6, 2007"
 .SH NAME
 pcfs \- FAT formatted file system
 .SH SYNOPSIS
-.LP
 .nf
 #include <sys/param.h>
 #include <sys/mount.h>
 #include <sys/fs/pc_fs.h>
 

@@ -18,12 +17,10 @@
      \fB"pcfs", NULL, 0,\fR \fBchar *\fR\fIoptptr\fR,
      \fBint\fR \fIoptlen\fR);
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 \fBpcfs\fR is a file system type that enables direct access to files on
 \fBFAT\fR formatted disks from within the SunOS operating system.
 .sp
 .LP
 Once mounted, \fBpcfs\fR provides standard SunOS file operations and semantics.

@@ -74,12 +71,10 @@
 .sp
 .LP
 The FAT filesystem doesn't support multiple links. As a result, the link count
 for all files and directories in \fBpcfs\fR is hard-coded as "1."
 .SS "Mounting File Systems"
-.sp
-.LP
 Use the following command to mount \fBpcfs\fR from diskette:
 .sp
 .in +2
 .nf
 mount \fB-F\fR pcfs \fIdevice-special\fR \fIdirectory-name\fR

@@ -210,12 +205,10 @@
 .fi
 .in -2
 .sp
 
 .SS "Conventions"
-.sp
-.LP
 Files and directories created through \fBpcfs\fR must comply with either the
 \fBFAT\fR short file name convention or the long file name convention
 introduced with Windows 95. The \fBFAT\fR short file name convention is of the
 form \fIfilename\fR[.\fIext\fR], where \fIfilename\fR generally consists of
 from one to eight upper-case characters, while the optional \fIext\fR consists

@@ -258,12 +251,10 @@
 .LP
 To format a diskette or a \fBPCMCIA\fR pseudo-floppy memory card in \fBFAT\fR
 format in the SunOS system, use either the \fBfdformat\fR \fB-d\fR or the
 \fBDOS\fR \fBFORMAT\fR command.
 .SS "Boot Partitions"
-.sp
-.LP
 On x86 systems, hard drives may contain an \fBfdisk\fR partition reserved for
 the Solaris boot utilities. These partitions are special instances of
 \fBpcfs\fR. You can mount an x86 boot partition with the command:
 .sp
 .in +2

@@ -305,11 +296,10 @@
 .sp
 .LP
 All files on a boot partition are owned by super-user. Only the super-user may
 create, delete, or modify files on a boot partition.
 .SH EXAMPLES
-.LP
 \fBExample 1 \fRSample Displays of File Names
 .sp
 .LP
 If you copy a file \fBfinancial.data\fR from a UNIX file system to \fBpcfs\fR,
 it displays as \fBfinancial.data\fR in \fBpcfs\fR, but may show up as

@@ -318,11 +308,10 @@
 .sp
 .LP
 The following are legal long file names. They are also \fBillegal\fR short file
 names:
 
-.br
 .in +2
 \fBtest.sh.orig\fR
 .in -2
 .br
 .in +2

@@ -334,11 +323,10 @@
 .in -2
 .sp
 .LP
 Other systems that do not support long file names may see:
 
-.br
 .in +2
 \fBTESTSH~1.ORI\fR
 .in -2
 .br
 .in +2

@@ -352,11 +340,10 @@
 .LP
 The short file name is generated from the initial characters of the long file
 name, so differentiate names in the first few characters. For example, these
 names:
 
-.br
 .in +2
 \fBWorkReport.January.Data\fR
 .in -2
 .br
 .in +2

@@ -368,11 +355,10 @@
 .in -2
 .sp
 .LP
 result in these short names, which are not distinguishable:
 
-.br
 .in +2
 \fBWORKRE~1.DAT\fR
 .in -2
 .br
 .in +2

@@ -384,11 +370,10 @@
 .in -2
 .sp
 .LP
 These names, however:
 
-.br
 .in +2
 \fBJanuary.WorkReport.Data\fR
 .in -2
 .br
 .in +2

@@ -400,11 +385,10 @@
 .in -2
 .sp
 .LP
 result in the more descriptive short names:
 
-.br
 .in +2
 \fBJANUAR~1.DAT\fR
 .in -2
 .br
 .in +2

@@ -413,11 +397,10 @@
 .br
 .in +2
 \fBMARCHW~1.DAT\fR
 .in -2
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/usr/lib/fs/pcfs/mount\fR\fR
 .ad
 .RS 26n

@@ -432,24 +415,18 @@
 .RS 26n
 32-bit kernel module
 .RE
 
 .SH ENVIRONMENT VARIABLES
-.sp
-.LP
 See \fBenviron\fR(5) for descriptions of the following environment variables
 for the current locale setting: LANG, LC_ALL, LC_CTYPE, and LC_COLLATE.
 .SH SEE ALSO
-.sp
-.LP
 \fBchgrp\fR(1), \fBchown\fR(1), \fBdos2unix\fR(1), \fBeject\fR(1),
 \fBfdformat\fR(1), \fBunix2dos\fR(1), \fBvolcheck\fR(1), \fBmount\fR(1M),
 \fBmount_pcfs\fR(1M), \fBumount\fR(1M), \fBctime\fR(3C), \fBvfstab\fR(4),
 \fBenviron\fR(5), \fBpcmem\fR(7D)
 .SH WARNINGS
-.sp
-.LP
 Do not physically eject a \fBFAT\fR floppy while the device is mounted as
 \fBpcfs\fR. If Volume Management is managing a device, use the \fBeject\fR(1)
 command before physically removing media.
 .sp
 .LP

@@ -460,12 +437,10 @@
 Because \fBpcfs\fR has no provision for handling owner-IDs or group-IDs on
 files, \fBchown\fR(1) or \fBchgrp\fR(1) may generate various errors. This is a
 limitation of \fBpcfs\fR, but it should not cause problems other than error
 messages.
 .SH NOTES
-.sp
-.LP
 Only the following characters are allowed in \fBpcfs\fR short file names and
 extensions:
 .br
 .in +2
 \fB0-9\fR

@@ -506,10 +481,8 @@
 locales. In the same context, when new file names with non-ASCII characters are
 created, \fBpcfs\fR expects that such file names are in UTF-8. This feature
 increases the interoperability of \fBpcfs\fR on Solaris with other operating
 systems.
 .SH BUGS
-.sp
-.LP
 \fBpcfs\fR should handle the disk change condition in the same way that
 \fBDOS\fR does, so you do not need to unmount the file system to change
 floppies.