7045 Fix spelling mistakes in section 4

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

12 files changed, 34 insertions, 144 deletions

diff --git a/usr/src/man/man4/NISLDAPmapping.4 b/usr/src/man/man4/NISLDAPmapping.4
index 2c5888e830..4ff72e3826 100644
--- a/usr/src/man/man4/NISLDAPmapping.4
+++ b/usr/src/man/man4/NISLDAPmapping.4
@@ -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 NISLDAPMAPPING 4 "Mar 29, 2006"
+.TH NISLDAPMAPPING 4 "April 9, 2016"
 .SH NAME
 NISLDAPmapping \- mapping file used by the NIS server components
 .SH SYNOPSIS
@@ -13,7 +13,6 @@ NISLDAPmapping \- mapping file used by the NIS server components
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBNISLDAPmapping\fR file specifies the mapping between NIS map entries and
 equivalent Directory Information Tree (DIT) entries. The syntax of this file is
@@ -44,7 +43,7 @@ values) takes precedence.
 .LP
 A continuation is indicated by a '\e' (backslash) in the last position,
 immediately before the newline of a line. Characters are escaped, that is,
-exempted from special interpretation, when preceeded by a backslash character.
+exempted from special interpretation, when preceded by a backslash character.
 .sp
 .LP
 The '#' (hash) character starts a comment. White space is either ASCII space or
@@ -52,7 +51,6 @@ a horizontal tab. In general, lines consist of optional white space, an
 attribute name, at least one white space character, and an attribute value.
 .SH EXTENDED DESCRIPTION
 .SS "File Syntax"
-.sp
 .LP
 Repeated fields, with separator characters, are described by the following
 syntax:
@@ -88,7 +86,6 @@ entry[":"...]
 .RE
 
 .SS "Attributes"
-.sp
 .LP
 Attributes generally apply to one more more NIS maps. Map names can be
 specified either on their own,that is in \fBpasswd.byname\fR, in which case
@@ -479,7 +476,7 @@ fields.
 \fB\fBrf_comment\fR\fR
 .ad
 .RS 18n
-Everything following the first occurance of a symbol. \fBrf_comment\fR is
+Everything following the first occurrence of a symbol. \fBrf_comment\fR is
 defined by \fBnisLDAPcommentChar\fR.
 .RE
 
@@ -745,7 +742,6 @@ field name are ignored when information is mapped into the DIT.
 .RE
 
 .SS "Field and Attribute Conversion Syntax"
-.sp
 .LP
 The general format of a \fBfieldattrspec\fR is:
 .sp
@@ -967,7 +963,7 @@ performed without checking if read and write are enabled for the LDAP container
 or NIS map.
 .sp
 .LP
-The ommision of the \fBnamespec\fR in an \fBrhs\fR is only allowed if the
+The omission of the \fBnamespec\fR in an \fBrhs\fR is only allowed if the
 \fBlhs\fR is one or more attributes. The effect is to delete the specified
 attribute(s). In all other situations, an omitted \fBnamespec\fR means that the
 rule is ignored.
@@ -1015,7 +1011,6 @@ If there is an error when evaluating a certain \fBfieldattrspec\fR, including
 retrieval or assignment of entry or field values, the extent to which the other
 \fBfieldattrspec\fR rules are evaluated is unspecified.
 .SS "Wildcards"
-.sp
 .LP
 Where wildcard support is available, it is of the following limited form:
 .sp
@@ -1050,7 +1045,6 @@ Matches any character in the range x to y, inclusive
 Combinations such as \fB[a-cA-C0123]\fR are also allowed, which would match any
 one of a, b, c, A, B, C, 0, 1, 2, or 3.
 .SS "Substring Extraction"
-.sp
 .in +2
 .nf
 substringextract = "(" namespec "," matchspec ")"
@@ -1109,7 +1103,6 @@ way to specify that special case is:
 .in -2
 
 .SS "Values"
-.sp
 .in +2
 .nf
 lval            = "(" formatspec "," namespec *("," namespec) ")"
@@ -1281,7 +1274,6 @@ Remove value of \fBmyName\fR from value \fBmyAliases\fR
 This results in the field values \fBmyName\fR is set to \fBfoo\fR, and
 \fBmyAliases\fR is set to \fBfoo1 foo2\fR.
 .SS "Assignments"
-.sp
 .LP
 The assignment syntax, also found at Field and Attribute Conversion Syntax, is
 as follows:
@@ -1477,7 +1469,6 @@ instance of \fBmgrprfc822mailmember\fR:
 .in -2
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/var/yp/NISLDAPmapping\fR\fR
@@ -1487,7 +1478,6 @@ Mapping file used by the NIS server components
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -1503,7 +1493,6 @@ Interface Stability 	Obsolete
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBinityp2l\fR(1M), \fBmakedbm\fR(1M), \fBypserv\fR(1M),
 \fBber_printf\fR(3LDAP), \fBsprintf\fR(3C), \fBsscanf\fR(3C),
diff --git a/usr/src/man/man4/fdi.4 b/usr/src/man/man4/fdi.4
index a3f7feabaf..60cc582ebd 100644
--- a/usr/src/man/man4/fdi.4
+++ b/usr/src/man/man4/fdi.4
@@ -4,7 +4,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 FDI 4 "Sep 5, 2006"
+.TH FDI 4 "April 9, 2016"
 .SH NAME
 fdi \- HAL device information file format
 .SH SYNOPSIS
@@ -14,7 +14,6 @@ fdi \- HAL device information file format
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The hardware abstraction layer facility, described in \fBhal\fR(5), uses an
 \fBXML\fR-based file format to merge arbitrary properties onto device objects.
@@ -309,7 +308,7 @@ following syntax:
 
 .sp
 .LP
-Device Information files are stored in the following standard hierachy with the
+Device Information files are stored in the following standard hierarchy with the
 following default top level directories \fBinformation\fR, \fBpolicy\fR and
 \fBpreprobe\fR:
 .sp
@@ -429,7 +428,6 @@ Device information for specific devices.
 .LP
 All device information files are matched for every \fBhal\fR device object.
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -445,7 +443,6 @@ Interface Stability	Volatile
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBhald\fR(1M), \fBattributes\fR(5), \fBhal\fR(5), \fBlocale\fR(5),
 \fBsmf\fR(5)
diff --git a/usr/src/man/man4/hosts_access.4 b/usr/src/man/man4/hosts_access.4
index 9df0d16182..7452c14b07 100644
--- a/usr/src/man/man4/hosts_access.4
+++ b/usr/src/man/man4/hosts_access.4
@@ -3,7 +3,7 @@
 .\" Modified for Solaris to to add the Solaris stability classification,
 .\" and to add a note about source availability.
 .\"
-.TH HOSTS_ACCESS 4 "Sep 15, 2011"
+.TH HOSTS_ACCESS 4 "April 9, 2016"
 .SH NAME
 hosts_access \- format of host access control files
 .SH DESCRIPTION
@@ -17,7 +17,7 @@ An extended version of the access control language is described in the
 \fIhosts_options\fR(4) document. The extensions are turned on at
 program build time by building with -DPROCESS_OPTIONS.
 .PP
-In the following text, \fIdaemon\fR is the the process name of a
+In the following text, \fIdaemon\fR is the process name of a
 network daemon process, and \fIclient\fR is the name and/or address of
 a host requesting service. Network daemon process names are specified
 in the inetd configuration file.
diff --git a/usr/src/man/man4/inetd.conf.4 b/usr/src/man/man4/inetd.conf.4
index 123129afb5..1b272d6b28 100644
--- a/usr/src/man/man4/inetd.conf.4
+++ b/usr/src/man/man4/inetd.conf.4
@@ -1,7 +1,7 @@
 '\" te
 .\"  Copyright 1989 AT&T Copyright (c) 1985 Regents of the University of California. All rights reserved. The Berkeley software License Agreement specifies the terms and conditions for redistribution.
 .\" Copyright (C) 2004, Sun Microsystems, Inc. All Rights Reserved
-.TH INETD.CONF 4 "Dec 17, 2004"
+.TH INETD.CONF 4 "April 9, 2016"
 .SH NAME
 inetd.conf \- Internet servers database
 .SH SYNOPSIS
@@ -16,7 +16,6 @@ inetd.conf \- Internet servers database
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 In the current release of the Solaris operating system, the \fBinetd.conf\fR
 file is no longer directly used to configure \fBinetd\fR. The Solaris services
@@ -161,7 +160,7 @@ the server that is invoked by \fBinetd\fR will take over the listening socket
 associated with the service, and whether once launched, \fBinetd\fR will
 \fBwait\fR for that server to exit, if ever, before it resumes listening for
 new service requests. The \fIwait-status\fR for datagram servers must be set to
-\fBwait\fR, as they are always invoked with the orginal datagram socket that
+\fBwait\fR, as they are always invoked with the original datagram socket that
 will participate in delivering the service bound to the specified service. They
 do not have separate "listening" and "accepting" sockets. Accordingly, do not
 configure \fBUDP\fR services as \fBnowait\fR. This causes a race condition by
@@ -208,7 +207,6 @@ for services whose \fIwait-status\fR value is \fBnowait\fR.
 .RE
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/etc/netconfig\fR\fR
@@ -236,12 +234,10 @@ Internet network services
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBrlogin\fR(1), \fBrsh\fR(1), \fBin.tftpd\fR(1M), \fBinetadm\fR(1M),
 \fBinetconv\fR(1M), \fBinetd\fR(1M), \fBservices\fR(4), \fBsmf\fR(5)
 .SH NOTES
-.sp
 .LP
 \fB/etc/inet/inetd.conf\fR is the official SVR4 name of the \fBinetd.conf\fR
 file. The symbolic link \fB/etc/inetd.conf\fR exists for \fBBSD\fR
diff --git a/usr/src/man/man4/ippool.4 b/usr/src/man/man4/ippool.4
index 419515db8e..d70b5cad9a 100644
--- a/usr/src/man/man4/ippool.4
+++ b/usr/src/man/man4/ippool.4
@@ -4,7 +4,7 @@
 .\" environment has been installed anywhere other than the default, modify the
 .\" given path to access the file at the installed location.
 .\" Portions Copyright (c) 2015, Joyent, Inc.
-.TH IPPOOL 4 "Mar 18, 2015"
+.TH IPPOOL 4 "April 9, 2016"
 .SH NAME
 ippool, ippool.conf \- IP Pool file format
 .SH DESCRIPTION
@@ -100,7 +100,7 @@ configuration entries.
 When a pool is defined in the configruation file, it must have an associated
 role.  At present the only supported role is
 .B ipf.
-Future development will see futher expansion of their use by other sections
+Future development will see further expansion of their use by other sections
 of IPFilter code.
 .SH EXAMPLES
 The following examples show how the pool configuration file is used with
diff --git a/usr/src/man/man4/krb5.conf.4 b/usr/src/man/man4/krb5.conf.4
index 63ead95eb2..6959901737 100644
--- a/usr/src/man/man4/krb5.conf.4
+++ b/usr/src/man/man4/krb5.conf.4
@@ -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 KRB5.CONF 4 "Oct 29, 2015"
+.TH KRB5.CONF 4 "April 9, 2016"
 .SH NAME
 krb5.conf \- Kerberos configuration file
 .SH SYNOPSIS
@@ -13,7 +13,6 @@ krb5.conf \- Kerberos configuration file
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBkrb5.conf\fR file contains Kerberos configuration information, including
 the locations of \fBKDC\fRs and administration daemons for the Kerberos realms
@@ -142,7 +141,6 @@ For a Key Distribution Center (\fBKDC\fR), can contain the location of the
 .RE
 
 .SS "The \fB[libdefaults]\fR Section"
-.sp
 .LP
 The \fB[libdefaults]\fR section can contain any of the following relations:
 .sp
@@ -409,7 +407,6 @@ to make it a network-wide setting for all realms.
 .RE
 
 .SS "The \fB[appdefaults]\fR Section"
-.sp
 .LP
 This section contains subsections for Kerberos V5 applications, where
 \fIrelation-subsection\fR is the name of an application. Each subsection
@@ -592,7 +589,6 @@ In the following example, \fBkinit\fR gets forwardable tickets by default and
 The application defaults specified here are overridden by those specified in
 the \fB[realms]\fR section.
 .SS "The \fB[realms]\fR Section"
-.sp
 .LP
 This section contains subsections for Kerberos realms, where
 \fIrelation-subsection\fR is the name of a realm. Each subsection contains
@@ -873,7 +869,6 @@ parameters. Most often, you need to specify them only when using a
 non-Solaris-based Kerberos server. Otherwise, the change request is sent over
 \fBRPCSEC_GSS\fR to the Solaris Kerberos administration server.
 .SS "The \fB[domain_realm]\fR Section"
-.sp
 .LP
 This section provides a translation from a domain name or hostname to a
 Kerberos realm name. The \fIrelation\fR can be a host name, or a domain name,
@@ -907,7 +902,6 @@ default into the \fBFUBAR.ORG\fR realm. The entries for the hosts \fBmit.edu\fR
 and \fBfubar.org\fR. Without these entries, these hosts would be mapped into
 the Kerberos realms \fBEDU\fR and \fBORG\fR, respectively.
 .SS "The \fB[logging]\fR Section"
-.sp
 .LP
 This section indicates how Kerberos programs are to perform logging. There are
 two types of relations for this section: relations to specify how to log and a
@@ -1117,7 +1111,6 @@ with a specified time interval of a day.
 .sp
 
 .SS "The \fB[capaths]\fR Section"
-.sp
 .LP
 In order to perform direct (non-hierarchical) cross-realm authentication, a
 database is needed to construct the authentication paths between the realms.
@@ -1222,7 +1215,6 @@ In the above examples, the ordering is not important, except when the same
 relation is used more than once. The client uses this to determine the path.
 (It is not important to the server, since the transited field is not sorted.)
 .SS "PKINIT-specific Options"
-.sp
 .LP
 The following are \fBpkinit-specific\fR options. These values can be specified
 in \fB[libdefaults]\fR as global defaults, or within a realm-specific
@@ -1443,7 +1435,7 @@ it has an acceptable EKU. The use of this option is not recommended.
 .ad
 .sp .6
 .RS 4n
-The presense of this option indicates that the client is willing to accept a
+The presence of this option indicates that the client is willing to accept a
 KDC certificate with a \fBdNSName\fR SAN (Subject Alternative Name) rather than
 requiring the \fBid-pkinit-san\fR as defined in RFC4556. This option can be
 specified multiple times. Its value should contain the acceptable hostname for
@@ -1536,7 +1528,6 @@ pkinit_cert_match = <EKU>msScLogin,clientAuth<KU>digitalSignature
 .RE
 
 .SS "PKINIT URI Types"
-.sp
 .ne 2
 .na
 \fB\fBFILE:\fR\fIfile-name[,key-file-name]\fR\fR
@@ -1655,7 +1646,6 @@ been set to \fBFILE:/tmp/my_proxy.pem\fR.
 .RE
 
 .SS "The \fB[dbmodules]\fR Section"
-.sp
 .LP
 This section consists of relations that provide configuration information for
 plug-in modules. In particular, the relations describe the configuration for
@@ -1840,7 +1830,6 @@ a Kerberos configuration file when the KDC is using the LDAP KDB plug-in.
 .sp
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/var/krb5/kdc.log\fR\fR
@@ -1851,7 +1840,6 @@ a Kerberos configuration file when the KDC is using the LDAP KDB plug-in.
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -1871,13 +1859,11 @@ Interface Stability	See below.
 All of the keywords are Committed, except for the \fBPKINIT\fR keywords, which
 are Volatile.
 .SH SEE ALSO
-.sp
 .LP
 \fBkinit\fR(1), \fBrcp\fR(1), \fBrdist\fR(1), \fBrlogin\fR(1), \fBrsh\fR(1),
 \fBtelnet\fR(1), \fBsyslog\fR(3C), \fBattributes\fR(5), \fBkerberos\fR(5),
 \fBregex\fR(5)
 .SH NOTES
-.sp
 .LP
 If the \fBkrb5.conf\fR file is not formatted properly, the \fBtelnet\fR command
 fails. However, the \fBdtlogin\fR and \fBlogin\fR commands still succeed, even
diff --git a/usr/src/man/man4/ncad_addr.4 b/usr/src/man/man4/ncad_addr.4
index 2b8cc73c05..198a6e87ff 100644
--- a/usr/src/man/man4/ncad_addr.4
+++ b/usr/src/man/man4/ncad_addr.4
@@ -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 NCAD_ADDR 4 "Feb 18, 2003"
+.TH NCAD_ADDR 4 "April 9, 2016"
 .SH NAME
 ncad_addr \- name of the Solaris Network Cache and Accelerator (NCA) socket
 utility library
@@ -14,7 +14,6 @@ utility library
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 \fBncad_addr.so\fR is the Solaris Network Cache and Accelerator (\fBNCA\fR)
 socket utility library. Use this library with a web server to avoid support for
@@ -33,7 +32,7 @@ Interpose the \fBncad_addr\fR interfaces before the interfaces in
 .sp
 .LP
 Using Bourne shell syntax as an example, set \fBLD_PRELOAD\fR as shown below to
-interpose the \fBncad_addr\fR socket utility libary:
+interpose the \fBncad_addr\fR socket utility library:
 
 .sp
 .in +2
@@ -43,7 +42,6 @@ LD_PRELOAD=/usr/lib/ncad_addr.so /usr/bin/httpd
 .in -2
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/usr/lib/ncad_addr.so\fR\fR
@@ -53,7 +51,6 @@ LD_PRELOAD=/usr/lib/ncad_addr.so /usr/bin/httpd
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5)  for descriptions of the following attributes:
 .sp
@@ -69,12 +66,10 @@ Interface Stability	Unstable
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBsocket\fR(3SOCKET),
 \fBnca.if\fR(4),  \fBncakmod.conf\fR(4), \fBattributes\fR(5)
 .SH NOTES
-.sp
 .LP
 Only applications that use the \fBNCA\fR feature, for example, web servers,
 should interpose this library.
diff --git a/usr/src/man/man4/printers.conf.4 b/usr/src/man/man4/printers.conf.4
index b83b032fd2..ed91e8ca6f 100644
--- a/usr/src/man/man4/printers.conf.4
+++ b/usr/src/man/man4/printers.conf.4
@@ -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 PRINTERS.CONF 4 "Jun 2, 2006"
+.TH PRINTERS.CONF 4 "April 9, 2016"
 .SH NAME
 printers.conf \- system printing configuration database
 .SH SYNOPSIS
@@ -31,7 +31,6 @@ printers.conf \- system printing configuration database
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBprinters.conf\fR file is the system printing configuration database.
 System administrators use \fBprinters.conf\fR to describe destinations for the
@@ -46,7 +45,6 @@ checks to see if the NIS+ table (\fBprinters.org_dir\fR) exists and if it does
 not it goes ahead and creates it in the correct format. See \fBlpset\fR(1M) for
 more information.
 .SS "Entries"
-.sp
 .LP
 Each entry in \fBprinters.conf\fR describes one destination. Entries are one
 line consisting of any number of fields separated by colons (`\fB:\fR') and
@@ -76,13 +74,11 @@ NEWLINE. Use the \fBlpset\fR command to create or modify \fBprinters.conf\fR.
 See \fBlpset\fR(1M). Do \fBnot\fR make changes in \fBprinters.conf\fR by using
 an editor.
 .SS "Specifying Configuration Options"
-.sp
 .LP
 \fIkey\fR\fB=\fR\fIvalue\fR pairs are configuration options defined by the
 system administrator. \fIkey\fR and \fIvalue\fR can be of arbitrary length.
 Separate \fIkey\fR and \fIvalue\fR by the equal (`\fB='\fR) character.
 .SS "Client/Server Configuration Options"
-.sp
 .LP
 The following client/server configuration options (represented as
 \fIkey\fR\fB=\fR\fIvalue\fR pairs) are supported:
@@ -139,12 +135,12 @@ and format of the endpoint is determined by the remote print service.
 .ad
 .sp .6
 .RS 4n
-This URI form is used for print queues that are remotely accessable by way of
+This URI form is used for print queues that are remotely accessible by way of
 the BSD Print Protocol. Though limited in capability, this protocol is widely
-used between client and server. It provides maximium interoperability with
+used between client and server. It provides maximum interoperability with
 remote print services. When used to communicate with print services on a
 Solaris print server, the optional \fB#Solaris\fR component of the URI
-indicates that Solaris protcol extensions can be used during print job
+indicates that Solaris protocol extensions can be used during print job
 submission.
 .RE
 
@@ -168,7 +164,7 @@ no protocol extensions are generated. \fIserver\fR is the name of the host
 containing the queue for \fIdestination\fR. \fIdestination\fR is the atomic
 name by which the server knows the destination.  If the configuration file
 contents are to be shared with legacy systems (Solaris 2.6 - Solaris 10), this
-key/value pair should be provided for backward compatability.
+key/value pair should be provided for backward compatibility.
 .RE
 
 .sp
@@ -198,7 +194,6 @@ See \fBlpget\fR(1M), \fBlpstat\fR(1), and \fBcancel\fR(1).
 .RE
 
 .SS "LP Server Options"
-.sp
 .LP
 The following \fBLP\fR configuration options (represented as
 \fIkey\fR\fB=\fR\fIvalue\fR pairs) are supported:
@@ -216,12 +211,11 @@ print requests submitted from a different host. \fBuser-equivalence\fR is set
 to \fBfalse\fR by default. \fBfalse\fR means that usernames are not considered
 equivalent, and does not permit users cancel a print request submitted from a
 different host. If \fBuser-equivalence\fR is set to \fBfalse\fR, print requests
-can only be cancelled by the users on the host on whichs the print prequest was
+can only be cancelled by the users on the host on which the print request was
 generated or by the superuser on the print server.
 .RE
 
 .SS "Print Queue Name Resolution"
-.sp
 .LP
 Applications needing to resolve print queue names (destinations) to the
 associated print service and communications endpoint make use of a specific
@@ -230,7 +224,6 @@ unto themselves and require no further resolution.  Names in atomic form are
 resolved based on the \fBprinters\fR database entry in the /etc/nsswitch.conf
 file. See nsswitch.conf(4)
 .SS "Locating the Personal Default Destination"
-.sp
 .LP
 The default destination is located differently depending on the command.
 .sp
@@ -291,7 +284,6 @@ destination in the following order:
 \fB_default\fR destination in \fB/etc/printers.conf\fR.
 .RE
 .SS "Locating the Interest List for lpstat, lpget, and cancel"
-.sp
 .LP
 The \fBlpget\fR, \fBlpstat\fR, and \fBcancel\fR commands locate the interest
 list in the following order:
@@ -325,7 +317,7 @@ and \fBcancel\fR commands to \fBprinter1\fR, \fBprinter2\fR and \fBprinter3\fR:
 \fBExample 2 \fRSetting the Server Name
 .sp
 .LP
-The following entry sets the server name to \fBserver\fR and and printer name
+The following entry sets the server name to \fBserver\fR and printer name
 to \fBps_printer\fR for destinations \fBprinter1\fR and \fBps\fR. It does not
 generate BSD protocol extensions.
 
@@ -400,7 +392,6 @@ The following example uses IPP as the URI:
 .sp
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/etc/printers.conf\fR\fR
@@ -446,7 +437,6 @@ LDAP version of \fB/etc/printers.conf\fR
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -462,7 +452,6 @@ Stability Level	Stable
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBcancel\fR(1), \fBenable\fR(1), \fBenable\fR(1), \fBlp\fR(1), \fBlpq\fR(1B),
 \fBlpr\fR(1B), \fBlprm\fR(1B), \fBlpstat\fR(1), \fBaccept\fR(1M),
diff --git a/usr/src/man/man4/protocols.4 b/usr/src/man/man4/protocols.4
index 967a9b77fd..199da6e0e0 100644
--- a/usr/src/man/man4/protocols.4
+++ b/usr/src/man/man4/protocols.4
@@ -4,7 +4,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 PROTOCOLS 4 "Jun 13, 2002"
+.TH PROTOCOLS 4 "April 9, 2016"
 .SH NAME
 protocols \- protocol name database
 .SH SYNOPSIS
@@ -19,13 +19,12 @@ protocols \- protocol name database
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBprotocols\fR file  is a local source of information regarding the known
 protocols used in the \fBDARPA\fR Internet. The protocols file can be used in
 conjunction with or instead of other protocols sources, including the \fBNIS\fR
-maps ``protcols.byname'' and "protocols.bynumber" and the \fBNIS+\fR table
-``protocols''. Programs use the \fBgetprotobyname\fR(3SOCKET) routine to access
+maps "protocols.byname" and "protocols.bynumber" and the \fBNIS+\fR table
+"protocols". Programs use the \fBgetprotobyname\fR(3SOCKET) routine to access
 this information.
 .sp
 .LP
@@ -83,7 +82,6 @@ ipv6-opts   60  IPv6-Opts   # Destination Options for IPv6
 .sp
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/etc/nsswitch.conf\fR\fR
@@ -93,11 +91,9 @@ configuration file for name-service switch
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBgetprotobyname\fR(3SOCKET), \fBnsswitch.conf\fR(4)
 .SH NOTES
-.sp
 .LP
 \fB/etc/inet/protocols\fR is the official SVR4 name of the \fBprotocols\fR
 file.  The symbolic link \fB/etc/protocols\fR exists for \fBBSD\fR
diff --git a/usr/src/man/man4/terminfo.4 b/usr/src/man/man4/terminfo.4
index d585eed8d6..d1d5577d62 100644
--- a/usr/src/man/man4/terminfo.4
+++ b/usr/src/man/man4/terminfo.4
@@ -4,7 +4,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 TERMINFO 4 "Jul 9, 1996"
+.TH TERMINFO 4 "April 9, 2016"
 .SH NAME
 terminfo \- terminal and printer capability database
 .SH SYNOPSIS
@@ -14,7 +14,6 @@ terminfo \- terminal and printer capability database
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBterminfo\fR database describes the capabilities of devices such as
 terminals and printers. Devices are described in \fBterminfo\fR source files by
@@ -110,7 +109,6 @@ The \fBterminfo\fR reference manual page is organized in two sections:
 \fBPART 2: PRINTER CAPABILITIES\fR
 .RE
 .SS "PART 1: DEVICE CAPABILITIES"
-.sp
 .LP
 Capabilities in \fBterminfo\fR are of three types:  Boolean capabilities (which
 show that a device has or does not have a particular feature), numeric
@@ -141,7 +139,6 @@ exception of those used for input. Input capabilities, listed under the
 \fBkey_\fR. The \fB#i\fR symbol in the description field of the following
 tables refers to the \fIi\fRth parameter.
 .SS "Booleans"
-.sp
 .in +2
 .nf
 ________________________________________________________________
@@ -215,7 +212,6 @@ xon_xoff                  xon    xo       Terminal uses xon/xoff
 .sp
 
 .SS "Numbers"
-.sp
 .in +2
 .nf
 ________________________________________________________________
@@ -280,7 +276,6 @@ width_status_line     wsl     ws       Number of columns in status line
 .sp
 
 .SS "Strings"
-.sp
 .in +2
 .nf
 ________________________________________________________________
@@ -448,7 +443,6 @@ insert_padding             ip     ip       Insert pad after
 .sp
 
 .SS "key_Strings"
-.sp
 .LP
 The ``\fBkey_\fR'' strings are sent by specific keys. The ``\fBkey_\fR''
 descriptions include the macro, defined in \fB<curses.h>\fR, for the code
@@ -627,7 +621,7 @@ key_left                kcub1   kl       KEY_LEFT, sent by
 key_ll                  kll     kH       KEY_LL, sent by home-down key
 key_mark                kmrk    %2       KEY_MARK, sent by
 key_message             kmsg    %3       KEY_MESSAGE, sent by message key
-key_mouse               kmous   Km       0631, Mouse event has occured
+key_mouse               kmous   Km       0631, Mouse event has occurred
 key_move                kmov    %4       KEY_MOVE, sent by move key
 key_next                knxt    %5       KEY_NEXT, sent by next-object
                                          key
@@ -911,7 +905,6 @@ zero_motion             zerom   Zx       No motion for the
 .sp
 
 .SS "Sample Entry"
-.sp
 .LP
 The following entry, which describes the AT&T 610 terminal, is among the more
 complex entries in the \fBterminfo\fR file as of this writing.
@@ -953,7 +946,6 @@ complex entries in the \fBterminfo\fR file as of this writing.
 .in -2
 
 .SS "Types of Capabilities in the Sample Entry"
-.sp
 .LP
 The sample entry shows the formats for the three types of \fBterminfo\fR
 capabilities listed:  Boolean, numeric, and string. All capabilities specified
@@ -1016,7 +1008,6 @@ period before the capability name. For example, see the second \fBind\fR in the
 example above. Note that capabilities are defined in a left-to-right order and,
 therefore, a prior definition will override a later definition.
 .SS "Preparing Descriptions"
-.sp
 .LP
 The most effective way to prepare a device description is by imitating the
 description of a similar device in \fBterminfo\fR and building up a description
@@ -1033,7 +1024,6 @@ from the middle of the screen, and then press the \fBu\fR key several times
 quickly. If the display is corrupted, more padding is usually needed. A similar
 test can be used for insert-character.
 .SS "Section 1-1: Basic Capabilities"
-.sp
 .LP
 The number of columns on each line for the device is given by the \fBcols\fR
 numeric capability. If the device has a screen, then the number of lines on the
@@ -1123,7 +1113,6 @@ adm3 | lsi adm3,
 .sp
 
 .SS "Section 1-2: Parameterized Strings"
-.sp
 .LP
 Cursor addressing and other strings requiring parameters are described by a
 parameterized string capability, with \fBprintf\fR-like escapes
@@ -1359,7 +1348,6 @@ space (32), adds them (pushing the sum on the stack in place of the two
 previous values), and outputs that value as a character. Then the same is done
 for the second parameter. More complex arithmetic is possible using the stack.
 .SS "Section 1-3: Cursor Motions"
-.sp
 .LP
 If the terminal has a fast way to home the cursor (to very upper left corner of
 screen) then this can be given as \fBhome\fR; similarly a fast way of getting
@@ -1394,7 +1382,6 @@ command character to be the one used by \fBterminfo\fR. If the \fBsmcup\fR
 sequence will not restore the screen after an \fBrmcup\fR sequence is output
 (to the state prior to outputting \fBrmcup\fR), specify \fBnrrmc\fR.
 .SS "Section 1-4: Area Clears"
-.sp
 .LP
 If the terminal can clear from the current position to the end of the line,
 leaving the cursor where it is, this should be given as \fBel\fR. If the
@@ -1405,7 +1392,6 @@ then this should be given as \fBed\fR. \fBed\fR is only defined from the first
 column of a line. (Thus, it can be simulated by a request to delete a large
 number of lines, if a true \fBed\fR is not available.)
 .SS "Section 1-5: Insert/Delete Line"
-.sp
 .LP
 If the terminal can open a new blank line before the line where the cursor is,
 this should be given as \fBil1\fR; this is done only from the first position of
@@ -1452,7 +1438,6 @@ be given. These indicate that deleting a line or scrolling a full screen may
 bring non-blank lines up from below or that scrolling back with \fBri\fR may
 bring down non-blank lines.
 .SS "Section 1-6: Insert/Delete Character"
-.sp
 .LP
 There are two basic kinds of intelligent terminals with respect to
 insert/delete character operations which can be described using \fBterminfo.\fR
@@ -1515,7 +1500,6 @@ terminal needs to be placed in for \fBdch1\fR to work).
 A command to erase \fIn\fR characters (equivalent to outputting \fIn\fR blanks
 without moving the cursor) can be given as \fBech\fR with one parameter.
 .SS "Section 1-7: Highlighting, Underlining, and Visible Bells"
-.sp
 .LP
 Your device may have one or more kinds of display attributes that allow you to
 highlight selected characters when they appear on the screen. The following
@@ -1661,7 +1645,6 @@ Putting this all together into the \fBsgr\fR sequence gives:
 .LP
 Remember that \fBsgr\fR and \fBsgr0\fR must always be specified.
 .SS "Section 1-8: Keypad"
-.sp
 .LP
 If the device has a keypad that transmits sequences when the keys are pressed,
 this information can also be specified. Note that it is not possible to handle
@@ -1704,7 +1687,6 @@ and off, give them in \fBsmln\fR and \fBrmln\fR. \fBsmln\fR is normally output
 after one or more \fBpln\fR sequences to make sure that the change becomes
 visible.
 .SS "Section 1-9: Tabs and Initialization"
-.sp
 .LP
 If the device has hardware tabs, the command to advance to the next tab stop
 can be given as \fBht\fR (usually control I). A ``backtab'' command that moves
@@ -1761,7 +1743,6 @@ Any margin can be cleared with \fBmgc\fR. (For instructions on how to specify
 commands to set and clear margins, see "Margins" below under "PRINTER
 CAPABILITIES".)
 .SS "Section 1-10: Delays"
-.sp
 .LP
 Certain capabilities control padding in the \fBtty\fR driver. These are
 primarily needed by hard-copy terminals, and are used by \fBtput\fR \fBinit\fR
@@ -1771,7 +1752,6 @@ appropriate delay bits to be set in the tty driver. If \fBpb\fR (padding baud
 rate) is given, these values can be ignored at baud rates below the value of
 \fBpb\fR.
 .SS "Section 1-11: Status Lines"
-.sp
 .LP
 If the terminal has an extra ``status line'' that is not normally used by
 software, this fact can be indicated. If the status line is viewed as an extra
@@ -1796,7 +1776,6 @@ line is a different width (possibly because the terminal does not allow an
 entire line to be loaded) the width, in columns, can be indicated with the
 numeric parameter \fBwsl\fR.
 .SS "Section 1-12: Line Graphics"
-.sp
 .LP
 If the device has a line drawing alternate character set, the mapping of glyph
 to character would be given in \fBacsc\fR. The definition of this string is
@@ -1868,7 +1847,6 @@ Now write down the characters left to right, as in
 In addition, \fBterminfo\fR allows you to define multiple character sets. See
 Section 2-5 for details.
 .SS "Section 1-13: Color Manipulation"
-.sp
 .LP
 Let us define two methods of color manipulation:  the Tektronix method and the
 HP method. The Tektronix method uses a set of N predefined colors (usually 8)
@@ -1960,7 +1938,6 @@ cannot coexist with colors. For example, if the terminal uses colors to
 simulate reverse video (bit number 2 and decimal value 4) and bold (bit number
 5 and decimal value 32), the resulting value for \fBncv\fR will be 36 (4 + 32).
 .SS "Section 1-14: Miscellaneous"
-.sp
 .LP
 If the terminal requires other than a null (zero) character as a pad, then this
 can be given as \fBpad\fR. Only the first character of the \fBpad\fR string is
@@ -2032,7 +2009,6 @@ screen when the printer is on, specify \fBmc5i\fR (silent printer). All text,
 including \fBmc4\fR, is transparently passed to the printer while an \fBmc5p\fR
 is in effect.
 .SS "Section 1-15: Special Cases"
-.sp
 .LP
 The working model used by \fBterminfo\fR fits most terminals reasonably well.
 However, some terminals do not completely match that model, requiring special
@@ -2068,7 +2044,6 @@ Those Beehive Superbee terminals which do not transmit the escape or
 control\(miC characters, should specify \fBxsb\fR, indicating that the f1 key
 is to be used for escape and the f2 key for control C.
 .SS "Section 1-16: Similar Terminals"
-.sp
 .LP
 If there are two very similar terminals, one can be defined as being just like
 the other with certain exceptions. The string capability \fBuse\fR can be given
@@ -2092,14 +2067,12 @@ defines an AT&T4424 terminal that does not have the \fBrev\fR, \fBsgr\fR, and
 different modes for a terminal, or for different user preferences. More than
 one \fBuse\fR capability may be given.
 .SS "PART 2: PRINTER CAPABILITIES"
-.sp
 .LP
 The \fBterminfo\fR database allows you to define capabilities of printers as
 well as terminals. To find out what capabilities are available for printers as
 well as for terminals, see the two lists under "DEVICE CAPABILITIES" that list
 capabilities by variable and by capability name.
 .SS "Section 2-1: Rounding Values"
-.sp
 .LP
 Because parameterized string capabilities work only with integer values, we
 recommend that \fBterminfo\fR designers create strings that expect numeric
@@ -2107,7 +2080,6 @@ values that have been rounded. Application designers should note this and
 should always round values to the nearest integer before using them with a
 parameterized string capability.
 .SS "Section 2-2: Printer Resolution"
-.sp
 .LP
 A printer's resolution is defined to be the smallest spacing of characters it
 can achieve. In general printers have independent resolution horizontally and
@@ -2150,7 +2122,6 @@ capability would give the width of a page in columns. In ``micro mode,'' many
 printers the micro mode may be concomitant with normal mode, so that all the
 capabilities work at the same time.
 .SS "Section 2-3: Specifying Printer Resolution"
-.sp
 .LP
 The printing resolution of a printer is given in several ways. Each specifies
 the resolution as the number of smallest steps per distance:
@@ -2318,7 +2289,6 @@ $V sub italic cpi$, $V sub italic lpi$, $V sub italic chr$, and $V sub italic
 cvr$ are the arguments used with \fBcpi\fR, \fBlpi\fR, \fBchr\fR, and
 \fBcvr\fR, respectively. The prime marks (\|'\|) indicate the old values.
 .SS "Section 2-4: Capabilities that Cause Movement"
-.sp
 .LP
 In the following descriptions, ``movement'' refers to the motion of the
 ``current position.'' With video terminals this would be the cursor; with some
@@ -2483,7 +2453,6 @@ Miscellaneous Motion Strings
 .sp
 
 .SS "Margins"
-.sp
 .LP
 \fBterminfo\fR provides two strings for setting margins on terminals:  one for
 the left and one for the right margin. Printers, however, have two additional
@@ -2547,7 +2516,6 @@ the bottom line of the page.
 .LP
 All margins can be cleared with \fBmgc\fR.
 .SS "Shadows, Italics, Wide Characters"
-.sp
 .LP
 Five new sets of strings describe the capabilities printers have of enhancing
 printed text.
@@ -2626,7 +2594,6 @@ affecting shadow, italicized, widened, superscript, or subscript printing.
 Conversely, if \fBmsgr\fR is not set, a program should end these modes before
 attempting any motion.
 .SS "Section 2-5: Alternate Character Sets"
-.sp
 .LP
 In addition to allowing you to define line graphics (described in Section
 1-12), \fBterminfo\fR lets you define alternate character sets. The following
@@ -2713,7 +2680,6 @@ are not available, the strings should not be defined. For printers that have
 manually changed print-wheels or font cartridges, the boolean \fBdaisy\fR is
 set.
 .SS "Section 2-6: Dot-Matrix Graphics"
-.sp
 .LP
 Dot-matrix printers typically have the capability of reproducing
 ``raster-graphics'' images. Three new numeric capabilities and three new string
@@ -2803,7 +2769,6 @@ the decimal values are further offset by the value 63. The \fBporder\fR string
 for these printers would be \fB,,6,5,4,3,2,1;63\fR, or alternately
 \fBo,o,6,5,4,3,2,1;63\fR.
 .SS "Section 2-7: Effect of Changing Printing Resolution"
-.sp
 .LP
 If the control sequences to change the character pitch or the line pitch are
 used, the pin or dot spacing may change:
@@ -2864,7 +2829,6 @@ in steps per inch, before using \fBlpi\fR and after using \fBlpi\fR,
 respectively. Thus, the changes in the dots per inch for dot-matrix graphics
 follow the changes in steps per inch for printer resolution.
 .SS "Section 2-8: Print Quality"
-.sp
 .LP
 Many dot-matrix printers can alter the dot spacing of printed text to produce
 near ``letter quality'' printing or ``draft quality'' printing. Usually it is
@@ -2889,7 +2853,6 @@ The capabilities are listed in decreasing levels of quality. If a printer
 doesn't have all three levels, one or two of the strings should be left blank
 as appropriate.
 .SS "Section 2-9: Printing Rate and Buffer Size"
-.sp
 .LP
 Because there is no standard protocol that can be used to keep a program
 synchronized with a printer, and because modern printers can buffer data before
@@ -2945,7 +2908,6 @@ already been printed, it should shrink the estimate. The application will thus
 err in favor of the user, who wants, above all, to see all the output in its
 correct place.
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/usr/share/lib/terminfo/?/*\fR\fR
@@ -2977,13 +2939,11 @@ terminal (escape sequences that set margins and tabs)
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBls\fR(1), \fBpg\fR(1), \fBstty\fR(1), \fBtput\fR(1), \fBtty\fR(1),
 \fBvi\fR(1), \fBinfocmp\fR(1M), \fBtic\fR(1M), \fBprintf\fR(3C),
 \fBcurses\fR(3CURSES), \fBcurses\fR(3XCURSES)
 .SH NOTES
-.sp
 .LP
 The most effective way to prepare a terminal description is by imitating the
 description of a similar terminal in \fBterminfo\fR and to build up a
diff --git a/usr/src/man/man4/utmpx.4 b/usr/src/man/man4/utmpx.4
index f676ed6c3f..7bcd3c6ad9 100644
--- a/usr/src/man/man4/utmpx.4
+++ b/usr/src/man/man4/utmpx.4
@@ -4,7 +4,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 UTMPX 4 "Mar 6, 2008"
+.TH UTMPX 4 "April 9, 2016"
 .SH NAME
 utmpx, wtmpx \- utmpx and wtmpx database entry formats
 .SH SYNOPSIS
@@ -16,7 +16,6 @@ utmpx, wtmpx \- utmpx and wtmpx database entry formats
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fButmpx\fR and \fBwtmpx\fR files are extended database files that have
 superseded the obsolete \fButmp\fR and \fBwtmp\fR database files.
@@ -27,20 +26,18 @@ commands such as \fBwho\fR(1), \fBwrite\fR(1), and \fBlogin\fR(1). The
 \fBwtmpx\fR database contains the history of user access and accounting
 information for the  \fButmpx\fR database.
 .SH USAGE
-.sp
 .LP
 Applications should not access these databases directly, but should use the
 functions described on the \fBgetutxent\fR(3C) manual page to interact with the
 \fButmpx\fR and \fBwtmpx\fR databases to ensure that they are maintained
 consistently.
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/var/adm/utmpx\fR\fR
 .ad
 .RS 18n
-user access and adminstration information
+user access and administration information
 .RE
 
 .sp
@@ -49,10 +46,9 @@ user access and adminstration information
 \fB\fB/var/adm/wtmpx\fR\fR
 .ad
 .RS 18n
-history of user access and adminstrative information
+history of user access and administrative information
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBgetutxent\fR(3C), \fBwait\fR(3C), \fBwait.h\fR(3HEAD)
diff --git a/usr/src/man/man4/volume-request.4 b/usr/src/man/man4/volume-request.4
index 8f7464051e..bb8f53c7f0 100644
--- a/usr/src/man/man4/volume-request.4
+++ b/usr/src/man/man4/volume-request.4
@@ -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 VOLUME-REQUEST 4 "Apr 27, 2005"
+.TH VOLUME-REQUEST 4 "April 9, 2016"
 .SH NAME
 volume-request, volume-defaults \- Solaris Volume Manager configuration
 information for top down volume creation with metassist
@@ -24,7 +24,6 @@ information for top down volume creation with metassist
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 A volume request file, XML-based and compliant with the
 \fBvolume-request.dtd\fR Document Type Definition, describes the
@@ -55,7 +54,6 @@ definition in the volume-request.dtd file, located at
 \fB/usr/share/lib/xml/dtd/volume-request.dtd\fR. You create a volume request
 file, and provide it as input to metassist to create volumes from the top down.
 .SS "Defining Volume Request"
-.sp
 .LP
 The top level element \fB<volume-request>\fR surrounds the volume request data.
 This element has no attributes. A volume request requires at least one
@@ -83,14 +81,12 @@ Optionally, the volume-request can include one or more \fB<concat>\fR,
 \fB<stripe>\fR, \fB<mirror>\fR, \fB<volume>\fR elements to specify volumes to
 create.
 .SS "Defining Disk Set"
-.sp
 .LP
 Within the \fB<volume-request>\fR element, a \fB<diskset>\fR element must
 exist. The \fB<diskset>\fR element, with the name attribute, specifies the name
 of the disk set to be used. If this disk set does not exist, it is created.
 This element and the name attribute are required.
 .SS "Defining Availability"
-.sp
 .LP
 Within the \fB<volume-request>\fR element and within other elements, you can
 specify available or unavailable components (disks, or disks on a specific
@@ -111,7 +107,7 @@ specifying \fBc3t2d\fR0 as available would look like:
 .sp
 .LP
 The \fB<available>\fR element also makes any unnamed components unavailable.
-Specifying all controllers exept \fBc1\fR unavailable would look like:
+Specifying all controllers except \fBc1\fR unavailable would look like:
 .sp
 .in +2
 .nf
@@ -132,7 +128,7 @@ Specifying all disks on controller 2 as unavailable would look like:
 .sp
 .LP
 The \fB<unavailable>\fR element can also be used to further restrict the list
-of available components. For example, specifying all controllers exept \fBc1\fR
+of available components. For example, specifying all controllers except \fBc1\fR
 unavailable, and making all devices associated with c1t2 unavailable as well
 would look like this:
 .sp
@@ -158,7 +154,6 @@ example, an unmounted slice that is reserved for different uses) must be
 explicitly specified as unavailable, or the \fBmetassist\fR command can include
 them in the configuration.
 .SS "Defining Hot Spare Pool"
-.sp
 .LP
 The next element within the <volume-request> element, after the \fB<diskset>\fR
 and, optionally, \fB<available>\fR and \fB<unavailable>\fR elements, is the
@@ -190,7 +185,6 @@ SLICE\fR). Depending on the requirements placed on the hot spare pool by other
 parts of the volume request, additional slices can be added to the hot spare
 pool.
 .SS "Defining Slice"
-.sp
 .LP
 The \fB<slice>\fR element is used to define slices to include or exclude within
 other elements. It requires only a name attribute to specify the ctd name of
@@ -205,7 +199,6 @@ of the element. Sample slice elements might look like:
 .in -2
 
 .SS "Defining Stripe"
-.sp
 .LP
 The \fB<stripe>\fR element defines stripes (interlaced RAID 0 volumes) to be
 used in a volume. It can contain either slice elements (to explicitly determine
@@ -244,14 +237,12 @@ hot spare pool should be associated with this component. This attribute is
 specified as a boolean value, as \fBusehsp="TRUE"\fR. If the component is not a
 submirror, this attribute is ignored.
 .SS "Defining Concat"
-.sp
 .LP
 The \fB<concat>\fR element defines concats (non-interlaced RAID 0 volumes) to
 be used in a configuration. It is specified in the same way as a \fB<stripe>\fR
 element, except that the \fBmincomp\fR, \fBmaxcomp\fR, and interlace attributes
 are not valid.
 .SS "Defining Mirror"
-.sp
 .LP
 The \fB<mirror>\fR element defines mirrors (RAID 1 volumes) to be used in a
 volume configuration. It can contain combinations of \fB<concat>\fR and
@@ -293,7 +284,6 @@ attribute is specified in the configuration of the \fB<stripe>\fR or
 \fB<concat>\fR element used as a submirror, it overrides the value of
 \fBusehsp\fR attributes for the mirror as a whole.
 .SS "Defining Volume by Quality of Service"
-.sp
 .LP
 The \fB<volume>\fR element defines volumes (high-level) by the quality of
 service they should provide. (The \fB<volume>\fR element offers the same
@@ -333,7 +323,6 @@ The \fB<volume>\fR element takes an optional datapaths attribute to determine
 if multiple data paths should be required to access the volume. The datapaths
 attribute should be set to a numeric value.
 .SS "Defining Default Values Globally"
-.sp
 .LP
 Global defaults can be set in \fB/etc/default/metassist.xml\fR. This
 volume-defaults file can contain most of the same elements as a volume-request
@@ -429,7 +418,6 @@ set name, and specifically itemizes characteristics of components to create.
 .in -2
 
 .SH BOUNDARY VALUES
-.sp
 .in +2
 .nf
 Attribute       Minimum         Maximum
@@ -444,7 +432,6 @@ redundancy      0               4
 .sp
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/usr/share/lib/xml/dtd/volume-request.dtd\fR\fR
@@ -475,7 +462,6 @@ redundancy      0               4
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBmetassist\fR(1M), \fBmetaclear\fR(1M), \fBmetadb\fR(1M),
 \fBmetadetach\fR(1M), \fBmetahs\fR(1M), \fBmetainit\fR(1M),