7048 Fix spelling mistakes in sections 7D, 7I, 7IPP, and 7P

Reviewed by: Robert Mustacchi <rm@joyent.com>
Approved by: Dan McDonald <danmcd@omniti.com>

15 files changed, 43 insertions, 176 deletions

diff --git a/usr/src/man/man7d/cpuid.7d b/usr/src/man/man7d/cpuid.7d
index 1ede29ccc5..cc522b1969 100644
--- a/usr/src/man/man7d/cpuid.7d
+++ b/usr/src/man/man7d/cpuid.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 CPUID 7D "Sep 16, 2004"
+.TH CPUID 7D "April 9, 2016"
 .SH NAME
 cpuid \- CPU identification driver
 .SH SYNOPSIS
@@ -14,43 +14,36 @@ cpuid \- CPU identification driver
 
 .SH DESCRIPTION
 .SS "SPARC and x86 system"
-.sp
 .LP
 This device provides implementation-private information via ioctls about
 various aspects of the implementation to Solaris libraries and utilities.
 .SS "x86 systems only"
-.sp
 .LP
 This device also provides a file-like view of the namespace and return values
 of the x86 cpuid instruction. The cpuid instruction takes a single 32-bit
 integer function code, and returns four 32-bit integer values corresponding to
 the input value that describe various aspects of the capabilities and
 configuration of the processor.
-.sp
 .LP
 The API for the character device consists of using the seek offset to set the
 function code value, and using a \fBread\fR(2) or \fBpread\fR(2) of 16 bytes to
 fetch the four 32-bit return values of the instruction in the order %\fBeax\fR,
 %\fBebx\fR, %\fBecx\fR and %\fBedx\fR.
-.sp
 .LP
 No data can be written to the device. Like the \fBcpuid\fR instruction, no
 special privileges are required to use the device.
-.sp
 .LP
 The device is useful to enable low-level configuration information to be
 extracted from the CPU without having to write any assembler code to invoke the
 \fBcpuid\fR instruction directly. It also allows the kernel to attempt to
-correct any erroneous data returned by the instruction (prompted by occassional
+correct any erroneous data returned by the instruction (prompted by occasional
 errors in the information exported by various processor implementations over
 the years).
-.sp
 .LP
 See the processor manufacturers documentation for further information about the
 syntax and semantics of the wide variety of information available from this
 instruction.
 .SH EXAMPLE
-.sp
 .LP
 This example allows you to determine if the current x86 processor supports
 "long mode," which is a necessary (but not sufficient) condition for running
@@ -113,7 +106,6 @@ fail:
 .in -2
 
 .SH ERRORS
-.sp
 .ne 2
 .na
 \fBENXIO\fR
@@ -134,7 +126,6 @@ with a size that is not multiple of 16 bytes.
 .RE
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/dev/cpu/self/cpuid\fR\fR
@@ -144,7 +135,6 @@ Provides access to CPU identification data.
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -160,7 +150,6 @@ Interface Stability	Evolving
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBpsrinfo\fR(1M), \fBprtconf\fR(1M), \fBpread\fR(2), \fBread\fR(2),
 \fBattributes\fR(5)
diff --git a/usr/src/man/man7d/ibd.7d b/usr/src/man/man7d/ibd.7d
index 8ba14f7d63..90350ac5c9 100644
--- a/usr/src/man/man7d/ibd.7d
+++ b/usr/src/man/man7d/ibd.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 IBD 7D "Jul 20, 2007"
+.TH IBD 7D "April 9, 2016"
 .SH NAME
 ibd \- Infiniband IPoIB device driver
 .SH SYNOPSIS
@@ -13,7 +13,6 @@ ibd \- Infiniband IPoIB device driver
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBibd\fR driver implements the IETF IP over Infiniband protocol and
 provides IPoIB service for all IBA ports present in the system.
@@ -47,9 +46,8 @@ address 255.255.255.255 (also defined as broadcast-GID in IETF documents) must
 be created prior to initializing the device. IBA properties (including mtu,
 qkey and sl) of this group is used by the driver to create any other IBA
 multicast group as instructed by higher level (IP) software. The driver probes
-for the existance of this broadcast-GID during \fBattach\fR(9E).
+for the existence of this broadcast-GID during \fBattach\fR(9E).
 .SH APPLICATION PROGRAMMING INTERFACE (DLPI)
-.sp
 .LP
 The values returned by the driver in the DL_INFO_ACK primitive in response to
 your DL_INFO_REQ are:
@@ -102,7 +100,6 @@ applications receive the IP/ARP datagram along with the IETF defined 4 byte
 header.
 .RE
 .SH WARNING
-.sp
 .LP
 This section describes warning messages that might be generated by the driver.
 Please note that while the format of these messages may be modified in future
@@ -193,13 +190,11 @@ should be checked that IBA cabling is intact, an SM is running on the fabric,
 and the broadcast-GID with appropriate properties has been created in the IBA
 partition.
 .SH CONFIGURATION
-.sp
 .LP
 The IPoIB service comes preconfigured on all HCA ports in the system. To turn
 the service off, or back on after turning it off, refer to documentation in
 \fBcfgadm_ib(1M)\fR.
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/dev/ibd*\fR\fR
@@ -245,13 +240,11 @@ configuration file to start IPoIB service
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBcfgadm\fR(1M), \fBcfgadm_ib(1M)\fR, \fBifconfig\fR(1M), \fBsyslogd\fR(1M),
 \fBgld\fR(7D), \fBib\fR(7D), \fBkstat\fR(7D), \fBstreamio\fR(7I),
 \fBdlpi\fR(7P), \fBattributes\fR(5), \fBattach\fR(9E)
 .SH NOTES
-.sp
 .LP
 IBD is a GLD-based driver and provides the statistics described by
 \fBgld\fR(7D). Note that valid received packets not accepted by any stream
diff --git a/usr/src/man/man7d/poll.7d b/usr/src/man/man7d/poll.7d
index e3d9e074aa..450da9ec5b 100644
--- a/usr/src/man/man7d/poll.7d
+++ b/usr/src/man/man7d/poll.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 POLL 7D "Sep 10, 2013"
+.TH POLL 7D "April 9, 2016"
 .SH NAME
 poll \- driver for fast poll on many file descriptors
 .SH SYNOPSIS
@@ -109,7 +109,7 @@ successfully or \fB-1\fR when write fails.
 .sp
 .LP
 The \fBDP_POLL\fR ioctl is used to retrieve returned \fBpoll\fR \fBevents\fR
-occured on the  polled file descriptors in the monitored set represented by
+occurred on the  polled file descriptors in the monitored set represented by
 \fIfd\fR. \fIarg\fR \fIis\fR \fIa\fR pointer to the devpoll structures which
 are defined as follows:
 .sp
diff --git a/usr/src/man/man7d/sgen.7d b/usr/src/man/man7d/sgen.7d
index 4578497f6b..dc2c9078f1 100644
--- a/usr/src/man/man7d/sgen.7d
+++ b/usr/src/man/man7d/sgen.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 SGEN 7D "Mar 29, 2008"
+.TH SGEN 7D "April 9, 2016"
 .SH NAME
 sgen \- Generic SCSI device driver
 .SH SYNOPSIS
@@ -18,14 +18,12 @@ sgen \- Generic SCSI device driver
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBsgen\fR driver exports the \fBuscsi\fR(7I) interfaces to user processes.
 The \fBsgen\fR driver can be configured to bind to \fBSCSI\fR devices for which
 no system driver is available. Examples of such devices include \fBSCSI\fR
 scanners and \fBSCSI\fR processor devices.
 .SH SECURITY
-.sp
 .LP
 Typically, drivers which export the \fBuscsi\fR(7I) interface unconditionally
 require that the user present superuser credentials. The \fBsgen\fR driver does
@@ -49,11 +47,10 @@ device may create other   problems. It may be possible for a user to instruct a
 target device to gather data from another target device on the same bus. It may
 also be possible for malicious users to install new firmware onto a device to
 which they are granted access. In environments where security is a concern but
-user access to devices controlled by the \fBsgen\fR driver is nontheless
+user access to devices controlled by the \fBsgen\fR driver is nonetheless
 desired, it is recommended that the devices be separated onto a dedicated
 \fBSCSI\fR bus to mitigate the risk of data corruption and security violations.
 .SH CONFIGURATION
-.sp
 .LP
 The \fBsgen\fR driver is configurable via the \fBsgen.conf\fR file. In addition
 to standard \fBSCSI\fR device configuration directives (see \fBscsi\fR(4)),
@@ -103,7 +100,6 @@ larger systems with many \fBSCSI\fR controllers, carefully edit the
 \fBsgen.conf\fR file so that \fBsgen\fR binds only where needed. Refer to
 \fBdriver.conf\fR(4) for further details.
 .SH PROPERTIES
-.sp
 .ne 2
 .na
 \fB\fBinquiry-config-list\fR\fR
@@ -294,10 +290,9 @@ contents of each CDB passed to the driver.
 .sp
 .LP
 In ascending order, each level includes the diagnostics that the previous level
-reports. See the IOCTLS section for more infomation on the \fBSGEN_IOC_DIAG\fR
+reports. See the IOCTLS section for more information on the \fBSGEN_IOC_DIAG\fR
 ioctl.
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fBsgen.conf\fR\fR
@@ -326,7 +321,6 @@ for naming disks. For example, \fB/dev/dsk/c0t0d0s0\fR and
 .RE
 
 .SH IOCTLS
-.sp
 .LP
 The \fBsgen\fR driver exports the \fBuscsi\fR(7I) interface for each device it
 manages. This allows a user process to talk directly to a \fBSCSI\fR device for
@@ -354,7 +348,6 @@ meaning as in the \fBsgen-diag\fR property discussed in PROPERTIES above.
 .RE
 
 .SH ERRORS
-.sp
 .ne 2
 .na
 \fB\fBEBUSY\fR\fR
@@ -384,7 +377,6 @@ Indicates that the device does  not  support the  requested ioctl function.
 .RE
 
 .SH EXAMPLES
-.sp
 .LP
 Here is an example of how \fBsgen\fR can be configured to bind to scanner
 devices on the system:
@@ -411,7 +403,6 @@ For large systems where boot times are a concern, it is recommended that the
 \fBparent=""\fR property be used to specify which \fBSCSI\fR bus \fBsgen\fR
 should examine.
 .SH SEE ALSO
-.sp
 .LP
 \fBdriver.conf\fR(4), \fBscsi\fR(4), \fBsd\fR(7D), \fBst\fR(7D),
 \fBuscsi\fR(7I)
diff --git a/usr/src/man/man7d/st.7d b/usr/src/man/man7d/st.7d
index e1d5ae3c53..2e1ab1ca38 100644
--- a/usr/src/man/man7d/st.7d
+++ b/usr/src/man/man7d/st.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 ST 7D "Oct 22, 2008"
+.TH ST 7D "April 9, 2016"
 .SH NAME
 st \- driver for SCSI tape devices
 .SH SYNOPSIS
@@ -13,7 +13,6 @@ st \- driver for SCSI tape devices
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBst\fR device driver provides a standard interface to various \fBSCSI\fR
 tape devices. See \fBmtio\fR(7I) for details.
@@ -88,13 +87,11 @@ open, as per the POSIX standard (see \fBstandards\fR(5)). However, if a command
 not found in the above list is used, a  reservation will occur to provide
 reserve/release functionality before the command is issued.
 .SS "Persistent Errors and Asynchronous Tape Operation"
-.sp
 .LP
 The \fBst\fR driver now supports persistent errors (see \fBmtio\fR(7I) and
 asynchronous tape operations (see \fBmtio\fR(7I), \fBaioread\fR(3C), and
 \fBaiowrite\fR(3C)).
 .SS "Read Operation"
-.sp
 .LP
 If the driver is opened for reading in a different format than the tape is
 written in, the driver overrides the user-selected format. For example, if a
@@ -109,12 +106,10 @@ message to inform you of an overridden format selection. Some devices
 automatically perform this function and do not require driver support (1/2"
 reel tape drive, for example).
 .SS "Write Operation"
-.sp
 .LP
 Writing from the beginning of tape is performed in the user-specified format.
 The original tape format is used for appending onto previously written tapes.
 .SS "Tape Configuration"
-.sp
 .LP
 The \fBst\fR driver has a built-in configuration table for most Sun-supported
 tape drives. For those tape drives that are not in the table, the \fBst\fR
@@ -479,7 +474,7 @@ release on close. If an attempt to use a ioctl of \fBMTRESERVE\fR or
 .RS 4n
 The \fBST_READ_IGNORE_ILI\fR flag is applicable only to variable block devices
 which support the SILI bit option. The \fBST_READ_IGNORE_ILI\fR flag indicates
-that SILI (supress incorrect length indicator) bit will be set during reads.
+that SILI (suppress incorrect length indicator) bit will be set during reads.
 When this flag is set, short reads (requested read size is less than the record
 size on the tape) will be successful and the number of bytes transferred will
 be equal to the record size on the tape. The tape will be positioned at the
@@ -626,7 +621,6 @@ before issuing the unload.
 \fB<erase time-out>\fR Time in seconds to preform a full (BOT to EOT) erase of
 longest medium with worst case error recovery.
 .SS "Device Statistics Support"
-.sp
 .LP
 Each device maintains I/O statistics both for the device and for each partition
 allocated on that device. For each device/partition, the driver accumulates
@@ -640,7 +634,6 @@ Each device also has error statistics associated with it. These must include
 counters for hard errors, soft errors and transport errors. Other data may be
 implemented as required.
 .SH IOCTLS
-.sp
 .LP
 The behavior of \fBSCSI\fR tape positioning ioctls is the same across all
 devices which support them. (Refer to \fBmtio\fR(7I).) However, not all devices
@@ -671,7 +664,6 @@ Note that the error status is reset by the \fBMTIOCGET\fR get status ioctl call
 or by the next read, write, or other ioctl operation. If no error has occurred
 (sense key is \fB0\fR), the current file and record position is returned.
 .SH ERRORS
-.sp
 .ne 2
 .na
 \fB\fBEACCES\fR\fR
@@ -805,7 +797,6 @@ name="st" class="scsi"
 .in -2
 
 .SS "Large Record Sizes"
-.sp
 .LP
 To support applications such as seismic programs that require large record
 sizes, the flag \fBST_NO_RECSIZE_LIMIT\fR must be set in drive option in the
@@ -831,7 +822,6 @@ platforms.
 .LP
 (Refer to the \fBWARNINGS\fR section for more information.)
 .SS "EOT Handling"
-.sp
 .LP
 The Emulex drives have only a physical end of tape (PEOT); thus it is not
 possible to write past EOT. All other drives have a logical end of tape
@@ -854,7 +844,6 @@ Reading past \fBEOT\fR is transparent to the user. Reading is stopped only by
 reading EOF's. For 1/2" reel devices, it is possible to read off the end of the
 reel if one reads past the two file marks which mark the end of recorded media.
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/kernel/drv/st.conf\fR\fR
@@ -959,14 +948,12 @@ l l .
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBmt\fR(1), \fBmodload\fR(1M), \fBmodunload\fR(1M), \fBopen\fR(2),
 \fBread\fR(2), \fBwrite\fR(2), \fBaioread\fR(3C), \fBaiowrite\fR(3C),
 \fBkstat\fR(3KSTAT), \fBdriver.conf\fR(4), \fBscsi\fR(4), \fBstandards\fR(5),
 \fBesp\fR(7D), \fBisp\fR(7D), \fBmtio\fR(7I), \fBioctl\fR(9E)
 .SH DIAGNOSTICS
-.sp
 .LP
 The \fBst\fR driver diagnostics may be printed to the console or messages file.
 .sp
@@ -1381,7 +1368,6 @@ These diagnostics are only seen with tape drives with the
 ST_RETRY_ON_RECOVERED_DEFERRED_ERROR bit set. See \fBstdef.h\fR for explanation
 of the specific usage of this setting.
 .SH WARNINGS
-.sp
 .LP
 Effective with Solaris 2.4, the \fBST_NO_RECSIZE_LIMIT\fR flag is set for the
 built-in config entries of the Archive \fBDAT\fR and Exabyte drivers by
@@ -1399,7 +1385,6 @@ reading of tapes written prior to Solaris 2.4 with large block sizes.
 .LP
 (Refer to \fBmtio\fR(7I) for a description of maximum record sizes.)
 .SH BUGS
-.sp
 .LP
 Tape devices that do not return a \fBBUSY\fR status during tape loading prevent
 user commands from being held until the device is ready. The user must delay
diff --git a/usr/src/man/man7d/su.7d b/usr/src/man/man7d/su.7d
index eb04fe961b..8c13961dea 100644
--- a/usr/src/man/man7d/su.7d
+++ b/usr/src/man/man7d/su.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 SU 7D "Jun 18, 2004"
+.TH SU 7D "April 9, 2016"
 .SH NAME
 su \- asynchronous serial port driver
 .SH SYNOPSIS
@@ -22,11 +22,10 @@ open("/dev/cua\fI[a-z]\fR", _\fImode\fR);
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBsu\fR module is a loadable STREAMS driver that provides basic support
 for standard \fBUARTS\fR that use Intel-8250, National
-Semiconductor-16450/16550 hardware and Southbridge 1535D (16550 compatable)
+Semiconductor-16450/16550 hardware and Southbridge 1535D (16550 compatible)
 Super I/O hardware. The module also provides keyboard and mouse I/O support for
 Sun machines using those same Intel, National Semiconductor and Southbridge
 chipsets. The \fBsu\fR driver provides basic asynchronous communication support
@@ -62,7 +61,6 @@ device number. By accessing character-special devices with names of the form
 Detect\fR signal being asserted, either through hardware or an equivalent
 software mechanism. These devices are commonly known as \fI_dial-out_\fR lines.
 .SH APPLICATION PROGRAMMING INTERFACE
-.sp
 .LP
 Once a \fB/dev/cua\fR\fI_n_\fR line is opened, the corresponding tty, or ttyd
 line cannot be opened until the \fB/dev/cua\fR\fI_n_\fR line is closed. A
@@ -77,7 +75,6 @@ renamed from \fB/dev/tty00\fR) and used for dial-in (by enabling the line for
 login in \fB/etc/inittab\fR) or dial-out (by \fBtip\fR(1) or \fBuucp\fR(1C)) as
 \fB/dev/cua0\fR when no one is logged in on the line.
 .SH IOCTLS
-.sp
 .LP
 The standard set of \fBtermio\fR \fBioctl()\fR calls are supported by \fBsu\fR.
 .sp
@@ -122,7 +119,6 @@ carriage return, tilde and control-B (CR ~ CTRL-B), but may be changed by the
 driver. For more information on breaking (entering the debugger or monitor),
 see \fBkbd\fR(1) and \fBkb\fR(7M).
 .SH ERRORS
-.sp
 .LP
 An \fBopen()\fR will fail under the following conditions:
 .sp
@@ -156,7 +152,6 @@ The unit has been marked as exclusive-use by another process with a
 .RE
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/dev/cua/[a-z]\fR\fR
@@ -184,7 +179,6 @@ binary compatibility package device names
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -200,14 +194,12 @@ Architecture	 SPARC
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBstrconf\fR(1), \fBkbd\fR(1), \fBtip\fR(1),\fBuucp\fR(1C),
 \fBautopush\fR(1M), \fBkstat\fR(1M), \fBpppd\fR(1M), \fBioctl\fR(2),
 \fBopen\fR(2), \fBtermios\fR(3C), \fBdacf.conf\fR(4), \fBattributes\fR(5),
 \fBkb\fR(7M), \fBldterm\fR(7M), \fBttcompat\fR(7M), \fBtermio\fR(7I)
 .SH DIAGNOSTICS
-.sp
 .LP
 The \fBsu\fR driver keeps track of various warning and error conditions using
 \fBkstat\fR counters. The output of the \fBkstat su\fR command provides
diff --git a/usr/src/man/man7d/ugen.7d b/usr/src/man/man7d/ugen.7d
index a9a5b11305..d870b946bc 100644
--- a/usr/src/man/man7d/ugen.7d
+++ b/usr/src/man/man7d/ugen.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 UGEN 7D "Sep 10, 2013"
+.TH UGEN 7D "April 9, 2016"
 .SH NAME
 ugen \- USB generic driver
 .SH SYNOPSIS
@@ -18,13 +18,12 @@ ugen \- USB generic driver
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 \fBugen\fR is a generic USBA (Solaris USB Architecture) compliant client
 character driver that presents USB devices to applications through a standard
 \fBopen\fR(2), \fBclose\fR(2), \fBread\fR(2), \fBwrite\fR(2),
 \fBaioread\fR(3C), \fBaiowrite\fR(3C) Unix interface. Uninterpreted raw data
-are transfered to and from the device via file descriptors created for each USB
+are transferred to and from the device via file descriptors created for each USB
 endpoint. Status is obtained by reading file descriptors created for endpoint
 and full device status.
 .sp
@@ -34,7 +33,6 @@ transfers. \fBlibusb\fR(3LIB) uses \fBugen\fR to access devices that do not
 contain drivers (such as digital cameras and PDAs). Refer to
 \fB/usr/sfw/share/doc/libusb/libusb.txt\fR for details.
 .SH BINDING
-.sp
 .LP
 In general, no explicit binding of the \fBugen\fR driver is necessary because
 \fBusb_mid\fR(7D) is the default driver for devices without a class or vendor
@@ -162,7 +160,6 @@ ugen driver device-bindings.
 Any pre-existing ugen driver device-bindings are preserved across operating
 system upgrades.
 .SH LOGICAL DEVICE NAME FORMAT
-.sp
 .LP
 For each device or child device it manages, \fBugen\fR creates one logical
 device name for device-wide status and one logical device name for endpoint 0.
@@ -305,7 +302,6 @@ alternate interface. A configuration change is prohibited when any non-zero
 endpoint device nodes are open. An alternate interface switch is prohibited if
 any endpoint in the same interface is open.
 .SH HOT-PLUGGING
-.sp
 .LP
 A device may be hot-removed at any time. Following hot-removal, the device
 status changes to USB_DEV_STAT_DISCONNECTED, the status of open endpoints
@@ -314,7 +310,6 @@ transfer requests fail. Endpoints are reactivated by first reinserting the
 device and then closing and reopening all endpoints that were open when the
 device was disconnected.
 .SH CPR (CHECKPOINT/RESUME)
-.sp
 .LP
 CPR (Checkpoint/Resume) may be initiated at any time and is treated similarly
 to a hot-removal. Upon successful suspend and resume, all subsequent transfer
@@ -323,19 +318,17 @@ should close and reopen all endpoints to reinstate them. All endpoint and
 device status on Resume (before close and reopen) is USB_LC_STAT_SUSPENDED. A
 system suspend will fail while \fBugen\fR is performing a transfer.
 .SH DEVICE POWER MANAGEMENT
-.sp
 .LP
 Devices which support remote wakeup can be power managed when they have no open
 logical device nodes. When an application opens the first logical device node
 of a device, that application should assume that a reinitialization of device
 state is required.
 .SH DEVICE STATUS MANAGEMENT
-.sp
 .LP
 Applications can monitor device status changes by reading the device status
 from the device status logical name. When opened without O_NONBLOCK and
-O_NDELAY, all reads from that file descriptor (with the exception of the the
-intial read that follows the open) block until a device status change occurs.
+O_NDELAY, all reads from that file descriptor (with the exception of the
+initial read that follows the open) block until a device status change occurs.
 Calls to read will always return immediately if opened with \fBO_NONBLOCK\fR or
 \fBO_NDELAY\fR. Nonblocking calls to read which have no data to return, return
 no error and zero bytes read.
@@ -425,7 +418,6 @@ device status logical names.  Poll indicates when reading a logical name would
 return data. See \fBpoll\fR(2) for details. Calls to read may be done whether
 or not they follow calls to poll.
 .SH ENDPOINT STATUS MANAGEMENT
-.sp
 .LP
 Each data endpoint has a corresponding status logical name. Use the status
 logical name to retrieve the state of the data endpoint, including detail on
@@ -459,7 +451,7 @@ if (ep1_stat_fd < 0) {
 
 data_xfered = write(ep1_data_fd, request, sizeof (request));
 
-/* An error occured during the data transfer. */
+/* An error occurred during the data transfer. */
 if (data_xfered != sizeof (request)) {
 
         /* Read status file descriptor for details on failure. */
@@ -482,7 +474,6 @@ if (data_xfered != sizeof (request)) {
 .in -2
 
 .SH CONTROL TRANSFERS
-.sp
 .LP
 The control endpoint is typically used to set up the device and to query device
 status or configuration.
@@ -760,7 +751,6 @@ configuration.  For sake of brevity, uninteresting parts are omitted.
 .in -2
 
 .SH INTERRUPT-IN TRANSFERS
-.sp
 .LP
 Applications requiring data from an interrupt-IN endpoint should open the
 corresponding logical device name and use \fBread\fR(2), \fBaioread\fR(3C) and
@@ -899,7 +889,6 @@ without O_NONBLOCK  or  O_NDELAY).  Set the new element's event field to POLLIN
 like the other elements. Note that only interrupt-IN endpoints and the device
 status endpoint can be monitored using \fBpoll\fR(2).
 .SH INTERRUPT-OUT TRANSFERS
-.sp
 .LP
 Applications requiring output on an interrupt-OUT endpoint can open the
 corresponding  logical  device name and perform regular UNIX I/O  system calls
@@ -932,7 +921,6 @@ Data can be written to an interrupt-OUT endpoint as follows:
 .in -2
 
 .SH BULK TRANSFERS
-.sp
 .LP
 Applications requiring I/O on a bulk endpoint can open the corresponding
 logical device name and perform regular UNIX I/O system calls. For example:
@@ -977,7 +965,6 @@ Data can be read from a bulk-IN endpoint as follows:
 .in -2
 
 .SH ISOCHRONOUS TRANSFERS
-.sp
 .LP
 Applications requiring I/O on an isochronous endpoint can open the
 corresponding logical device name and perform regular UNIX I/O system calls
@@ -1244,7 +1231,6 @@ endpoint:
 .in -2
 
 .SH ERRORS
-.sp
 .LP
 The following statuses are returned by endpoint status device logical names:
 .sp
@@ -1596,7 +1582,6 @@ No memory for the allocation of internal structures.
 .RE
 
 .SH FILES
-.sp
 .in +2
 .nf
         /kernel/drv/ugen   32 bit ELF kernel module (x86 platform only)
@@ -1638,7 +1623,6 @@ No memory for the allocation of internal structures.
 where \fIN\fR is an integer representing the instance number of this type of
 device. (All logical device names for a single device share the same \fIN\fR.)
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -1654,13 +1638,11 @@ Architecture	PCI-based  SPARC
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBlibusb\fR(3LIB), \fBclose\fR(2), \fBpoll\fR(2), \fBread\fR(2),
 \fBwrite\fR(2), \fBaioread\fR(3C), \fBaiowrite\fR(3C), \fBusba\fR(7D),
 \fBusb_dev_descr\fR(9S).
 .SH DIAGNOSTICS
-.sp
 .LP
 In addition to being logged, the following messages may appear on the system
 console. All messages are formatted in the following manner:
@@ -1717,7 +1699,6 @@ to identify the original device with a name string.
 .RE
 
 .SH NOTES
-.sp
 .LP
 \fBugen\fR returns \fB-1\fR for all commands and sets \fBerrno\fR to
 \fBENODEV\fR when device has been hot-removed or resumed from a suspend. The
diff --git a/usr/src/man/man7d/usba.7d b/usr/src/man/man7d/usba.7d
index dffea6da91..c917bed146 100644
--- a/usr/src/man/man7d/usba.7d
+++ b/usr/src/man/man7d/usba.7d
@@ -3,11 +3,10 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
 .\"  See the License for the specific language governing permissions and limitations under the License. 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 USBA 7D "Apr 22, 2009"
+.TH USBA 7D "April 9, 2016"
 .SH NAME
 usba, usb \- Solaris USB Architecture (USBA)
 .SH DESCRIPTION
-.sp
 .LP
 USB provides a low-cost means for attaching peripheral devices, including
 mass-storage devices, keyboards, mice, and printers, to a system. For complete
@@ -33,7 +32,6 @@ a complete list of USBA interfaces, see \fBIntro\fR(9F) and \fBIntro\fR(9S).
 Devices without a driver may have a  \fBlibusb\fR(3LIB) application. For more
 information, see \fB/usr/sfw/share/doc/libusb/libusb.txt\fR.
 .SH FILES
-.sp
 .LP
 Listed below are drivers and modules which either utilize or are utilized by
 USBA. Drivers in \fB/kernel/drv\fR are 32 bit drivers (x86 only). Drivers in
@@ -91,7 +89,6 @@ kernel/drv/[sparcv9|amd64/]ehci         enhanced host controller driver
 .sp
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for a description of the following attributes:
 .sp
@@ -107,7 +104,6 @@ Architecture	PCI-based  systems
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBcfgadm_usb\fR(1M), \fBlibusb\fR(3LIB), \fBattributes\fR(5), \fBehci\fR(7D),
 \fBhid\fR(7D), \fBhubd\fR(7D), \fBohci\fR(7D), \fBscsa2usb\fR(7D),
@@ -131,12 +127,10 @@ Architecture	PCI-based  systems
 .LP
 http://www.sun.com
 .SH NOTES
-.sp
 .LP
 Booting from USB mass-storage devices is not supported on SPARC, but is
 supported on X86.
 .SH DIAGNOSTICS
-.sp
 .LP
 The messages described below may appear on the system console as well as being
 logged. All  messages are formatted in the following manner:
@@ -168,7 +162,7 @@ name or the device name.
 .ad
 .sp .6
 .RS 4n
-An internal error occured.  Please reboot your system.  If this problem
+An internal error occurred.  Please reboot your system.  If this problem
 persists, contact your system vendor.
 .RE
 
diff --git a/usr/src/man/man7d/usbprn.7d b/usr/src/man/man7d/usbprn.7d
index 5fe69f2b4f..017e648cd7 100644
--- a/usr/src/man/man7d/usbprn.7d
+++ b/usr/src/man/man7d/usbprn.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 USBPRN 7D "Jun 18, 2005"
+.TH USBPRN 7D "April 9, 2016"
 .SH NAME
 usbprn \- USB printer class driver
 .SH SYNOPSIS
@@ -23,7 +23,6 @@ usbprn@unit-address
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBusbprn\fR driver is a USBA (Solaris USB Architecture) compliant client
 driver that supports the \fIUSB Printer Class 1.0\fR specification. The
@@ -43,11 +42,10 @@ additional format conversion packages available in the Solaris distribution.
 Configuration of these conversion packages under the Solaris printing system
 can be simplified through the use of the \fBprintmgr\fR(1M). This tool allows
 selection of printer manufacturer/model information while creating a print
-queue. For USB connected printers, it attempts to pre-select the the
+queue. For USB connected printers, it attempts to pre-select the
 manufacturer and model information based on the 1284 device id supplied by the
 printer.
 .SS "UGEN (Generic USB)"
-.sp
 .LP
 The \fBusbprn\fR driver also supports a \fBugen\fR(7D) interface allowing raw
 access to the device, for example by \fBlibusb\fR(3LIB) applications, by
@@ -55,7 +53,6 @@ passing the drivers bound to each interface. Because a libusb application might
 change the state of the device, you should not access the device through the
 child interface drivers.
 .SH DEFAULT OPERATION
-.sp
 .LP
 With certain minor exceptions (outlined in the Notes sections below), the
 \fBusbprn\fR driver supports a subset of the \fBecpp\fR(7D) ioctl interfaces:
@@ -78,7 +75,6 @@ to their default values with each \fBattach\fR(9E). (The \fBecpp\fR(7D) driver
 resets configuration variables with each \fBopen\fR(2).)
 .RE
 .SH WRITE OPERATION
-.sp
 .LP
 A \fBwrite\fR(2) operation returns the number of bytes successfully written to
 the device. If a failure occurs while a driver is transferring data to printer,
@@ -87,7 +83,6 @@ be retrieved by the application program using the ECPPIOC_GETERR \fBioctl\fR(2)
 call. The captured status information is overwritten each time an
 ECPPIOC_TESTIO \fBioctl\fR(2) occurs.
 .SH IOCTLS
-.sp
 .LP
 The \fBusbprn\fR driver supports \fBprnio(7I)\fR interfaces. Note that the
 \fBPRNIOC_RESET\fR command has no effect on USB printers.
@@ -250,11 +245,9 @@ Unlike \fBecpp\fR(7D), only the ECPP_CENTRONICS mode is currently supported in
 .RE
 
 .SH READ OPERATION
-.sp
 .LP
  The \fBread\fR operation is not supported and returns \fBEIO\fR.
 .SH ERRORS
-.sp
 .ne 2
 .na
 \fB\fBEBUSY\fR\fR
@@ -318,7 +311,6 @@ other than ECPP_CENTRONICS in the \fBecpp_transfer_parms\fR structure.
 .RE
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/kernel/drv/usbprn\fR\fR
@@ -364,7 +356,6 @@ Character special files
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -380,7 +371,6 @@ Architecture	SPARC, x86, PCI-based systems
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBcfgadm_usb\fR(1M), \fBprintmgr\fR(1M), \fBioctl\fR(2), \fBopen\fR(2),
 \fBread\fR(2), \fBwrite\fR(2), \fBlibusb\fR(3LIB), \fBattributes\fR(5),
@@ -402,7 +392,6 @@ Architecture	SPARC, x86, PCI-based systems
 .LP
 http://\fIwww.sun.com/io\fR
 .SH DIAGNOSTICS
-.sp
 .LP
 In addition to being logged, the following messages may appear on the system
 console. All messages are formatted in the following manner:
@@ -462,7 +451,6 @@ to the hot-removal may be lost.
 .RE
 
 .SH NOTES
-.sp
 .LP
 The USB printer will be power managed if the device is closed.
 .sp
diff --git a/usr/src/man/man7d/zs.7d b/usr/src/man/man7d/zs.7d
index 34c7e95f4f..690935cca8 100644
--- a/usr/src/man/man7d/zs.7d
+++ b/usr/src/man/man7d/zs.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
 .\"  See the License for the specific language governing permissions and limitations under the License. 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 ZS 7D "Jul 16, 2009"
+.TH ZS 7D "April 9, 2016"
 .SH NAME
 zs \- Zilog 8530 SCC serial communications driver
 .SH SYNOPSIS
@@ -33,7 +33,6 @@ open("/dev/cua/\fIn\fR", \fImode\fR);
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The Zilog 8530 provides two serial input/output channels capable of supporting
 a variety of communication protocols.  A typical system uses two or more of
@@ -92,7 +91,6 @@ information on parameters that are persistent across reboots, see the
 \fBeeprom\fR(1M) man page.
 .RE
 .SH IOCTLS
-.sp
 .LP
 The \fBzs\fR module supports the standard set of \fBtermio ioctl\fR(\|) calls.
 .sp
@@ -127,7 +125,7 @@ command, respectively.  Due to hardware limitations, only the \fBRTS\fR and
 .LP
 The input and output line speeds may be set to any of the speeds supported by
 \fBtermio\fR. The input and output line speeds cannot be set independently; for
-example, when you set the the output speed, the input speed is automatically
+example, when you set the output speed, the input speed is automatically
 set to the same speed.
 .sp
 .LP
@@ -160,7 +158,6 @@ tilde and control-B (CR ~ CTRL-B), but may be changed by the driver. For more
 information on breaking (entering the debugger or monitor), see \fBkbd\fR(1)
 and \fBkb\fR(7M).
 .SH ERRORS
-.sp
 .LP
 An \fBopen\fR will fail under the following conditions:
 .sp
@@ -212,7 +209,6 @@ The open was interrupted by the delivery of a signal.
 .RE
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/dev/cua/\fR[\fIa-z\fR]\fR
@@ -240,7 +236,6 @@ binary compatibility package device names
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -256,14 +251,12 @@ Architecture	SPARC
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBeeprom\fR(1M), \fBkadb\fR(1M), \fBtip\fR(1), \fBcu\fR(1C), \fBuucp\fR(1C),
 \fBports\fR(1M), \fBpppd\fR(1M), \fBioctl\fR(2), \fBopen\fR(2),
 \fBattributes\fR(5), \fBzsh\fR(7D), \fBtermio\fR(7I), \fBkb\fR(7M),
 \fBldterm\fR(7M), \fBttcompat\fR(7M)
 .SH DIAGNOSTICS
-.sp
 .ne 2
 .na
 \fB\fBzs\fR\fIn\fR\fB\|: silo overflow.\fR\fR
diff --git a/usr/src/man/man7i/mtio.7i b/usr/src/man/man7i/mtio.7i
index 7b3d9eee8a..570cc9d174 100644
--- a/usr/src/man/man7i/mtio.7i
+++ b/usr/src/man/man7i/mtio.7i
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 MTIO 7I "Sep 15, 2007"
+.TH MTIO 7I "April 9, 2016"
 .SH NAME
 mtio \- general magnetic tape interface
 .SH SYNOPSIS
@@ -15,7 +15,6 @@ mtio \- general magnetic tape interface
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 1/2", 1/4", 4mm, and 8mm magnetic tape drives all share the same general
 character device interface.
@@ -29,7 +28,6 @@ record is separated by interrecord (or tape) gaps on a tape.
 End-of-recorded-media (EOM) is indicated by two \fBEOF\fR marks on 1/2" tape;
 by one \fBEOF\fR mark on 1/4", 4mm, and 8mm cartridge tapes.
 .SS "1/2" Reel Tape"
-.sp
 .LP
 Data bytes are recorded in parallel onto the 9-track tape. Since it is a
 variable-length tape device, the number of bytes in a  physical record may
@@ -43,7 +41,6 @@ example, using a 2400 foot tape, 20 Mbyte can be stored using 800 \fBBPI,\fR 40
 Mbyte using 1600 \fBBPI,\fR 140 Mbyte using 6250 \fBBPI,\fR or up to 700 Mbyte
 using data compression.
 .SS "1/4" Cartridge Tape"
-.sp
 .LP
 Data is recorded serially onto 1/4" cartridge tape. The number of bytes per
 record is determined by the physical record size of the device. The I/O request
@@ -73,14 +70,12 @@ The \fBQIC-150\fR tape drives require \fBDC-6150\fR (or equivalent) tape
 cartridges for writing. However, they can read other tape cartridges in
 \fBQIC-11,\fR \fBQIC-24,\fR or \fBQIC-120\fR tape formats.
 .SS "8mm Cartridge Tape"
-.sp
 .LP
 Data is recorded serially onto 8mm helical scan cartridge tape. Since it is a
 variable-length tape device, the number of bytes in a  physical record may
 vary. The recording formats available (check specific tape drive) are standard
 2Gbyte, 5Gbyte, and compressed format.
 .SS "4mm DAT Tape"
-.sp
 .LP
 Data is recorded either in Digital Data Storage (DDS) tape format or in Digital
 Data Storage, Data Compressed (DDS-DC) tape format. Since it is a
@@ -88,7 +83,6 @@ variable-length tape device, the number of bytes in a  physical record may
 vary. The recording formats available are standard 2Gbyte and compressed
 format.
 .SS "Persistent Error Handling"
-.sp
 .LP
 Persistent error handling is a modification of the current error handling
 behaviors, BSD and SVR4. With persistent error handling enabled, all tape
@@ -122,7 +116,6 @@ disable persistent error handling and clear any errors or exceptions.
 The \fBRead Operation\fR and \fBWrite Operation\fR subsections contain more
 pertinent information reguarding persistent error handling.
 .SS "Read Operation"
-.sp
 .LP
 The \fBread\fR(2) function reads the next record on the tape. The record size
 is passed back as the number of bytes read, provided it is not greater than the
@@ -165,7 +158,6 @@ should never hit physical EOT.
 Read requests that are lesser than a physical tape record are not allowed.
 Appropriate error is returned.
 .SS "Write Operation"
-.sp
 .LP
 The \fBwrite\fR(2) function writes the next record on the tape. The record has
 the same length as the given buffer.
@@ -235,7 +227,6 @@ the file as soon as possible.
 .LP
 Seeks are ignored in tape I/O.
 .SS "Close Operation"
-.sp
 .LP
 Magnetic tapes are rewound when closed, except when the "no-rewind" devices
 have been specified. The names of no-rewind device files use the letter \fBn\fR
@@ -284,7 +275,6 @@ one or two file marks are written, thus creating a null file.
 After closing the device, persistent error handling will be disabled and any
 error or exception will be cleared.
 .SH IOCTLS
-.sp
 .LP
 Not all devices support all \fBioctls\fR. The driver returns an \fBENOTTY\fR
 error on unsupported ioctls.
@@ -701,7 +691,7 @@ extensive start-stop operations or long-term storage.
 .LP
 \fBMTERASE\fR rewinds the tape, erases it completely, and returns to the
 beginning of tape. Erasing may take a long time depending on the device and/or
-tapes.  For time details, refer to the the drive specific manual.
+tapes. For time details, refer to the drive specific manual.
 .sp
 .LP
 \fBMTEOM\fR positions the tape at a location just after the last file written
@@ -786,7 +776,6 @@ returned in struct tapepos as defined in
 .LP
 The  MTIOCRESTPOS ioctl restores a saved position from the MTIOCGETPOS.
 .SS "Persistent Error Handling IOCTLs and Asynchronous Tape Operations"
-.sp
 .ne 2
 .na
 \fBMTIOCPERSISTENT\fR
@@ -879,7 +868,6 @@ ioctl(fd, MTIOCGUARANTEEDORDER)
 See the \fBPersistent Error Handling\fR subsection above for more information
 on persistent error handling.
 .SS "Asynchronous and State Change IOCTLS"
-.sp
 .ne 2
 .na
 \fB\fBMTIOCSTATE\fR\fR
@@ -909,7 +897,6 @@ MTIO_INSERTED  /* Tape state is "inserted" */
 When using asynchronous operations, most ioctls will wait for all outstanding
 commands to complete before they are executed.
 .SS "IOCTLS for Multi-initiator Configurations"
-.sp
 .ne 2
 .na
 \fBMTIOCRESERVE\fR
@@ -970,13 +957,12 @@ ioctl(fd, MTIOCFORCERESERVE);
 .in -2
 
 .SS "IOCTLS for Handling Tape Configuration Options"
-.sp
 .ne 2
 .na
 \fBMTIOCSHORTFMK\fR
 .ad
 .RS 23n
-enables/disable support for writing short filemarks. This is specific to
+enables/disables support for writing short filemarks. This is specific to
 Exabyte drives.
 .RE
 
@@ -986,7 +972,7 @@ Exabyte drives.
 \fBMTIOCREADIGNOREILI\fR
 .ad
 .RS 23n
-enables/disable supress incorrect length indicator support during reads
+enables/disables suppress incorrect length indicator (SILI) support during reads
 .RE
 
 .sp
@@ -995,7 +981,7 @@ enables/disable supress incorrect length indicator support during reads
 \fBMTIOCREADIGNOREEOFS\fR
 .ad
 .RS 23n
-enables/disable support for reading past two EOF marks which otherwise indicate
+enables/disables support for reading past two EOF marks which otherwise indicate
 End-Of-recording-Media (EOM) in the case of 1/2" reel tape drives
 .RE
 
@@ -1005,7 +991,7 @@ The \fBMTIOCSHORTFMK\fR ioctl enables or disables support for short filemarks.
 This ioctl is only applicable to Exabyte drives which support short filemarks.
 As an argument, it takes a pointer to an integer.  If 0 (zero) is the
 specified integer, then long filemarks will be written. If 1 is the  specified
-integer, then short filemarks will be written. The specified tape bahavior will
+integer, then short filemarks will be written. The specified tape behavior will
 be in effect until the device is closed.
 .sp
 .LP
@@ -1031,9 +1017,9 @@ Tape drives which do not support short filemarks will return an \fBerrno\fR of
 The \fBMTIOCREADIGNOREILI\fR ioctl enables or disables the suppress incorrect
 length indicator (SILI) support during reads.  As an argument, it takes a
 pointer to an integer.   If 0 (zero) is the specified integer, SILI will not be
-used during reads and incorrect length indicator will not be supressed.  If 1
+used during reads and incorrect length indicator will not be suppressed.  If 1
 is  the specified integer, SILI will be used during reads and incorrect length
-indicator will be supressed.  The specified  tape bahavior will be in effect
+indicator will be suppressed.  The specified  tape behavior will be in effect
 until the device is closed.
 .sp
 .LP
@@ -1057,7 +1043,7 @@ integer.   If 0 (zero) is the specified integer, then double EOF marks indicate
 End-Of-recodred-media (EOD). If 1 is the specified integer, the double EOF
 marks no longer indicate EOM, thus allowing applications to read past two EOF
 marks.  In this case it is the responsibility of the application to detect
-end-of-recorded-media (EOM).  The specified  tape bahavior will be in effect
+end-of-recorded-media (EOM).  The specified  tape behavior will be in effect
 until the device is closed.
 .sp
 .LP
@@ -1144,7 +1130,6 @@ ioctl(fd, MTIOCGETDRIVETYPE, &mtreq);
 .in -2
 
 .SH FILES
-.sp
 .LP
 \fB/dev/rmt/\fR\fI<unit number><density>\fR[\fI<BSD behavior>\fR][\fI<no
 rewind>\fR]
@@ -1158,7 +1143,6 @@ high, ultra/compressed, respectively), the \fIBSD behavior \fR option is
 For example, \fB/dev/rmt/0hbn\fR specifies unit 0, high density, \fBBSD\fR
 behavior and no rewind.
 .SH SEE ALSO
-.sp
 .LP
 \fBmt\fR(1), \fBtar\fR(1), \fBdd\fR(1M), \fBopen\fR(2), \fBread\fR(2),
 \fBwrite\fR(2), \fBaioread\fR(3C), \fBaiowrite\fR(3C), \fBar.h\fR(3HEAD),
diff --git a/usr/src/man/man7i/termiox.7i b/usr/src/man/man7i/termiox.7i
index 1b22b6f20d..67daa26abc 100644
--- a/usr/src/man/man7i/termiox.7i
+++ b/usr/src/man/man7i/termiox.7i
@@ -4,11 +4,10 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 TERMIOX 7I "Jul 3, 1990"
+.TH TERMIOX 7I "April 9, 2016"
 .SH NAME
 termiox \- extended general terminal interface
 .SH DESCRIPTION
-.sp
 .LP
 The extended general terminal interface supplements the \fBtermio\fR(7I)
 general terminal interface by adding support for asynchronous hardware flow
@@ -19,7 +18,6 @@ may not permit certain functions to be disabled.  In these cases the
 appropriate bits will be ignored.  See <\fBsys/termiox.h\fR> for your system to
 find out which capabilities are supported.
 .SS "Hardware Flow Control Modes"
-.sp
 .LP
 Hardware flow control supplements the \fBtermio\fR(7I) \fBIXON\fR, \fBIXOFF\fR,
 and \fBIXANY\fR character flow control. Character flow control occurs when one
@@ -51,7 +49,6 @@ connected device is also a DTE and not a DCE, then DTE to DTE (for example,
 terminal or printer connected to computer) hardware flow control is possible by
 using a null modem to interconnect the appropriate data and control circuits.
 .SS "Clock Modes"
-.sp
 .LP
 Isochronous communication is a variation of asynchronous communication whereby
 two communicating devices may provide transmit and/or receive clock signals to
@@ -69,7 +66,6 @@ In terms of clock modes, traditional asynchronous communication is implemented
 simply by using the local baud rate generator as the incoming transmit and
 receive clock source and not outputting any clock signals.
 .SS "Terminal Parameters"
-.sp
 .LP
 The parameters that control the behavior of devices providing the \fBtermiox\fR
 interface are specified by the \fBtermiox\fR structure defined in the
@@ -129,7 +125,7 @@ functions.
 .sp
 .LP
 Variations of different hardware flow control methods may be selected by
-setting the the appropriate bits. For example, bidirectional RTS/CTS flow
+setting the appropriate bits. For example, bidirectional RTS/CTS flow
 control is selected by setting both the \fBRTSXOFF\fR and \fBCTSXON\fR bits and
 bidirectional DTR/CTS flow control is selected by setting both the
 \fBDTRXOFF\fR and \fBCTSXON\fR. Modem control or unidirectional CTS hardware
@@ -288,7 +284,6 @@ be used by any implementations. The \fBx_sflag\fR may be used by local
 implementations wishing to customize their terminal interface using the
 \fBtermiox\fR ioctl system calls.
 .SH IOCTLS
-.sp
 .LP
 The  \fBioctl\fR(2) system calls have the form:
 .sp
@@ -347,15 +342,12 @@ queued for input are discarded and then the change occurs.
 .RE
 
 .SH FILES
-.sp
 .LP
 \fB/dev/*\fR
 .SH SEE ALSO
-.sp
 .LP
 \fBstty\fR(1), \fBioctl\fR(2), \fBtermio\fR(7I)
 .SH NOTES
-.sp
 .LP
 The  termiox(7I) system call is provided for compatibility with previous
 releases and  its use is discouraged.  Instead, the  \fBtermio\fR(7I) system
diff --git a/usr/src/man/man7ipp/tokenmt.7ipp b/usr/src/man/man7ipp/tokenmt.7ipp
index 8e7ebb2490..8b2f3e22bc 100644
--- a/usr/src/man/man7ipp/tokenmt.7ipp
+++ b/usr/src/man/man7ipp/tokenmt.7ipp
@@ -3,11 +3,10 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" 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 TOKENMT 7IPP "Sep 29, 2004"
+.TH TOKENMT 7IPP "April 9, 2016"
 .SH NAME
 tokenmt \- Single and Two Rate Three Conformance Level Meter
 .SH DESCRIPTION
-.sp
 .LP
 The \fBtokenmt\fR module can be configured as a Single or a Two Rate meter.
 Packets are deemed to belong to one of the three levels - Red, Yellow or Green
@@ -72,7 +71,7 @@ is decided as follows:
                 T(t) = committed rate * (t - t')
                 (where t' is the time the last packet was seen)
               o Add T tokens to C up to a maximum of committed burst
-                size. Add remaining tokens ((C+T) - Commited Burst),
+                size. Add remaining tokens ((C+T) - Committed Burst),
                 if any, to P, to a maximum of peak burst size.
         - Decide outcome
               o If not color aware
@@ -123,7 +122,6 @@ When operating as a Two Rate meter, the outcome (level) is decided as follows:
 .in -2
 
 .SH STATISTICS
-.sp
 .LP
 The \fBtokenmt\fR module exports the following statistics through \fBkstat\fR:
 .sp
@@ -145,7 +143,6 @@ module: tokenmt                          instance: <action id>
 .in -2
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/kernel/ipp/sparcv9/tokenmt\fR\fR
@@ -156,7 +153,6 @@ module: tokenmt                          instance: <action id>
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBipqosconf\fR(1M), \fBdlcosmk\fR(7ipp), \fBdscpmk\fR(7ipp),
 \fBflowacct\fR(7ipp), \fBipqos\fR(7ipp), \fBipgpc\fR(7ipp),
diff --git a/usr/src/man/man7p/dlpi.7p b/usr/src/man/man7p/dlpi.7p
index 6852799626..c2ffdc6889 100644
--- a/usr/src/man/man7p/dlpi.7p
+++ b/usr/src/man/man7p/dlpi.7p
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
 .\"  See the License for the specific language governing permissions and limitations under the License. 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 DLPI 7P "Sep 7, 2009"
+.TH DLPI 7P "April 9, 2016"
 .SH NAME
 dlpi \- Data Link Provider Interface
 .SH SYNOPSIS
@@ -13,7 +13,6 @@ dlpi \- Data Link Provider Interface
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 SunOS STREAMS-based device drivers wishing to support the STREAMS \fB TCP/IP\fR
 and other STREAMS-based networking protocol suite implementations support
@@ -43,7 +42,6 @@ Solaris conforms to The Open Group Technical Standard for \fIDLPI, Version
 \fIwww.opengroup.org/pubs/catalog/c811.htm\fR. Solaris also provides extensions
 to the DLPI standard, as detailed in this man page.
 .SH SOLARIS-SPECIFIC DLPI EXTENSIONS
-.sp
 .ne 2
 .na
 \fBNotification Support\fR
@@ -155,7 +153,7 @@ set to zero by DLPI providers and ignored by DLPI consumers.
 .sp
 In addition to generating DL_NOTIFY_IND messages when a requested event has
 occurred, the \fBDLPI\fR provider must initially generate one or more
-DL_NOTIFY_IND messages to notify the \fBDLPI\fR consumer of the the current
+DL_NOTIFY_IND messages to notify the \fBDLPI\fR consumer of the current
 state of the interface. For instance, if the consumer has requested
 DL_NOTE_LINK_UP | DL_NOTE_LINK_DOWN, the provider must send a DL_NOTIFY_IND
 containing the current state of the link (either DL_NOTE_LINK_UP or
@@ -166,7 +164,7 @@ recommended against sending DL_NOTE_LINK_DOWN, even if the interface is still
 initializing and is not yet ready to send or receive packets. Instead, either
 delaying the DL_NOTIFY_IND message until the interface is ready or
 optimistically reporting DL_NOTIFY_LINK_UP and subsequently   reporting
-DL_NOTE_LINK_DOWN if the negotation fails is strongly   preferred. This
+DL_NOTE_LINK_DOWN if the negotiation fails is strongly   preferred. This
 prevents DL_NOTIFY_IND consumers from needlessly triggering network failover
 operations and logging error messages during network interface initialization.
 .sp
@@ -241,7 +239,7 @@ the links do not have any DLPI consumers or only \fBpassive\fR consumers.
 .RS 4n
 The \fBDLIOCRAW\fR ioctl function is used by some DLPI applications, most
 notably the \fBsnoop\fR(1M) command. The \fBDLIOCRAW\fR command puts the stream
-into a raw mode, which, upon receive, causes the the full MAC-level packet to
+into a raw mode, which, upon receive, causes the full MAC-level packet to
 be sent upstream in an \fBM_DATA\fR message instead of it being transformed
 into the \fBDL_UNITDATA_IND\fR form normally used for reporting incoming
 packets. Packet \fBSAP\fR filtering is still performed on streams that are in
@@ -297,7 +295,6 @@ size.
 .SH DL_ETHER-SPECIFIC DLPI SEMANTICS
 .SS "VLAN Support"
 .SS "Traditional VLAN Access"
-.sp
 .LP
 Some \fBDL_ETHER DLPI\fR providers support \fIIEEE 802.1Q\fR Virtual LANs
 (VLAN). For these providers, traffic for a particular VLAN can be accessed by
@@ -311,7 +308,6 @@ are added by the provider) and received data is passed to interested DLPI
 consumers without link-layer headers.  As a result,  DLPI consumers not require
 special-case logic to implement VLAN access.
 .SS "SAP-Based VLAN Access"
-.sp
 .LP
 As per \fIIEEE 802.1Q\fR, all VLAN traffic is sent using Ether- Type  0x8100,
 meaning  that in addition to directly opening a VLAN data-link, all VLAN
@@ -333,7 +329,6 @@ enables promiscuous mode of a stream at the \fBDL_PROMISC_SAP\fR level. As
 mentioned earlier, these packets are received starting with their VLAN headers
 if raw mode is not enabled.
 .SS "QoS Support"
-.sp
 .LP
 The \fIIEEE 802.1Q\fR standard defines eight classes of priority values used by
 QoS traffic control of Ethernet packets. Although the priority values are
@@ -349,7 +344,6 @@ also specify the per-packet priority value using the b_band field of a M_DATA
 message or the \fBdl_priority\fR field of a \fBDL_UNITDATA_REQ\fR.
 .SS "Raw Mode"
 .SS "SAP-Based VLAN Access"
-.sp
 .LP
 When raw mode is enabled, the complete, unmodified MAC- level packet (including
 Ethernet  and  VLAN headers) is passed to interested DLPI consumers. Similarly,
@@ -358,7 +352,6 @@ to the DLPI provider for transmission.  Note that the priority value specified
 in the b_band field can be overridden by encoding the priority value (if any)
 into the VLAN header.
 .SS "Traditional VLAN Access"
-.sp
 .LP
 When raw mode is enabled, only packets with the correct VLAN ID are passed up
 to interested DLPI consumers. With the exception of priority-tagged packets,
@@ -375,11 +368,9 @@ the VLAN header to  indicate the priority value, however its VLAN ID must be
 zero. The DLPI providers then insert the VLAN tags or encode the VLAN tags
 using the priority value specified in the VLAN headers and send the packets.
 .SH FILES
-.sp
 .LP
 Files in or under \fB/dev\fR.
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -397,12 +388,10 @@ T}	Committed
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBdladm\fR(1M), \fBsnoop\fR(1M), \fBlibdlpi\fR(3LIB), \fBgld\fR(7D),
 \fBip\fR(7P)
 .SH NOTES
-.sp
 .LP
 A Solaris DLPI link name consists of a \fBDLPI provider name\fR followed by a
 numeric \fBPPA\fR (physical point of attachment).
diff --git a/usr/src/man/man7p/route.7p b/usr/src/man/man7p/route.7p
index bbd74fd740..22d4f4c735 100644
--- a/usr/src/man/man7p/route.7p
+++ b/usr/src/man/man7p/route.7p
@@ -7,7 +7,7 @@
 .\" OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
 .\" IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\" Portions Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
-.TH ROUTE 7P "Sep 02, 2015"
+.TH ROUTE 7P "April 9, 2016"
 .SH NAME
 route \- kernel packet forwarding database
 .SH SYNOPSIS
@@ -91,7 +91,7 @@ are exhausted.
 .sp
 .LP
 The \fIprotocol\fR parameter specifies which messages an application listening
-on the routing socket is interested in seeing, based on the the address family
+on the routing socket is interested in seeing, based on the address family
 of the \fBsockaddrs\fR present. Currently, you can specify \fBAF_INET\fR and
 \fBAF_INET6\fR to filter the messages seen by the listener, or alternatively,
 you can specify \fBAF_UNSPEC\fR to indicate that the listener is interested in