7 files changed, 7 insertions, 47 deletions

diff --git a/usr/src/man/man5/attributes.5 b/usr/src/man/man5/attributes.5
index fcfe09fd1b..f9c0290fda 100644
--- a/usr/src/man/man5/attributes.5
+++ b/usr/src/man/man5/attributes.5
@@ -8,7 +8,6 @@
 attributes, architecture, availability, CSI, stability, MT-Level, standard \-
 attributes of interfaces
 .SH DESCRIPTION
-.sp
 .LP
 The \fBATTRIBUTES\fR section of a manual page contains a table defining
 attribute types and their corresponding values. The following is an example of
@@ -35,13 +34,11 @@ Standard	See \fBstandards\fR(5).
 .TE
 
 .SS "Architecture"
-.sp
 .LP
 Architecture defines processor or specific hardware. See \fB-p\fR option of
 \fBuname\fR(1). In some cases, it may indicate required adapters or
 peripherals.
 .SS "Code Set Independence (CSI)"
-.sp
 .LP
 \fBOS\fR utilities and libraries free of dependencies on the properties of any
 code sets are said to have Code Set Independence (CSI). They have the attribute
@@ -182,7 +179,6 @@ applied. Statically bound programs will only get support for C and POSIX
 locales.
 .RE
 .SS "Interface Stability"
-.sp
 .LP
 Sun often provides developers with early access to new technologies, which
 allows developers to evaluate with them as soon as possible. Unfortunately, new
@@ -213,7 +209,6 @@ structures and some symbols in system header files) may be implementation
 artifacts. Such internal interfaces are not only subject to incompatible change
 or removal, but we are unlikely to mention such a change in release notes.
 .SS "Release Levels"
-.sp
 .LP
 Products are given release levels, as well as names, to aid compatibility
 discussions. Each release level may also include changes suitable for lower
@@ -244,7 +239,6 @@ T}
 In the context of interface stability, update releases (occasionally referred
 to as patch releases) should be considered equivalent to Micro Releases.
 .SS "Classifications"
-.sp
 .LP
 The following table summarizes how stability level  classifications relate to
 release level. The first column lists the Stability Level. The second column
@@ -327,7 +321,7 @@ general expectation should be that Uncommitted interfaces are not likely to
 change incompatibly and if such changes occur they will be small in impact and
 may often have a mitigation plan.
 .sp
-Uncommitted interfaces generally fall into one of the following subcategorizes:
+Uncommitted interfaces generally fall into one of the following subcategories:
 .RS +4
 .TP
 1.
@@ -450,7 +444,6 @@ support. Use of an Obsolete interface may produce warning messages.
 .RE
 
 .SS "Exceptions"
-.sp
 .LP
 There are rare instances when it is in the best interest of both Sun and the
 customer to break the interface stability commitment. The following list
@@ -493,7 +486,6 @@ major" release vehicle possible.  However, often the consequences of the
 vulnerabilities or contractual branding requirements will force delivery in a
 patch.
 .SS "Compatibility with Earlier Interface Classification Schemes"
-.sp
 .LP
 In releases up to and including Solaris 10, a different interface
 classification scheme was used. The following table summarizes the mapping
@@ -530,7 +522,6 @@ interpretation. As part of the migration to the new classification scheme, many
 formerly Evolving interfaces were upgraded to Committed. However, upon
 encountering the term Evolving, Uncommitted should be inferred.
 .SS "MT-Level"
-.sp
 .LP
 Libraries are classified into categories that define their ability to support
 multiple threads. Manual pages containing functions that are of multiple or
@@ -706,7 +697,6 @@ also, by definition, Deferred-Cancel-Safe.
 .RE
 
 .SS "Standard"
-.sp
 .LP
 Many interfaces are defined and controlled as industry standards. When this is
 the case, the controlling body and/or public, versioned document is noted in
@@ -728,6 +718,5 @@ very formal organization, as in ISO or ANSII, a less formal, but generally
 accepted organization such as IETF, or as informal as the sole contributor in
 the case of FOSS (Free or Open Source Software).
 .SH SEE ALSO
-.sp
 .LP
 \fBuname\fR(1), \fBpkgadd\fR(1M), \fBIntro\fR(3), \fBstandards\fR(5)
diff --git a/usr/src/man/man5/largefile.5 b/usr/src/man/man5/largefile.5
index 3da728fe79..619dac08ec 100644
--- a/usr/src/man/man5/largefile.5
+++ b/usr/src/man/man5/largefile.5
@@ -48,7 +48,7 @@ l l l l l .
 \fBrm\fR	\fBrmdir\fR	\fBrsh\fR	\fBsed\fR	\fBsh\fR
 \fBsort\fR	\fBsplit\fR	\fBsum\fR	\fBtail\fR	\fBtar\fR
 \fBtee\fR	\fBtest\fR	\fBtouch\fR	\fBtr\fR	\fBuncompress\fR
-\fBuudcode\fR	\fBuuencode\fR	\fBvacation\fR	\fBwc\fR	\fBzcat\fR
+\fBuudecode\fR	\fBuuencode\fR	\fBvacation\fR	\fBwc\fR	\fBzcat\fR
 .TE
 
 .LP
diff --git a/usr/src/man/man5/pam_authtok_get.5 b/usr/src/man/man5/pam_authtok_get.5
index 580186b52d..b4e4d650a4 100644
--- a/usr/src/man/man5/pam_authtok_get.5
+++ b/usr/src/man/man5/pam_authtok_get.5
@@ -35,7 +35,7 @@ Due to the nature of the PAM Password Management stack traversal mechanism, the
 .LP
 In the first (\fBPRELIM\fR) invocation, the implementation of
 \fBpam_sm_chauthtok\fR(3PAM) moves the contents of the \fBPAM_AUTHTOK\fR
-(current authentication token) to \fBPAM_OLDAUTHTOK\fR, and subsequentially
+(current authentication token) to \fBPAM_OLDAUTHTOK\fR, and subsequently
 prompts the user for a new password. This new password is stored in
 \fBPAM_AUTHTOK\fR.
 .sp
diff --git a/usr/src/man/man5/pam_ldap.5 b/usr/src/man/man5/pam_ldap.5
index fec71f0322..26d2786af8 100644
--- a/usr/src/man/man5/pam_ldap.5
+++ b/usr/src/man/man5/pam_ldap.5
@@ -13,7 +13,6 @@ pam_ldap \- authentication and account management PAM module for LDAP
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBpam_ldap\fR module implements \fBpam_sm_authenticate\fR(3PAM) and
 \fBpam_sm_acct_mgmt\fR(3PAM), the functions that provide functionality for the
@@ -44,7 +43,6 @@ is, LDAP users. For the stacks to work, \fBpam_unix_auth\fR,
 \fBbinding\fR control flag and the \fBserver_policy\fR option. This
 configuration allows local account override of a network account.
 .SS "LDAP Authentication Module"
-.sp
 .LP
 The LDAP authentication module verifies the identity of a user. The
 \fBpam_sm_authenticate\fR(3PAM) function uses the password entered by the user
@@ -86,7 +84,6 @@ Turn off warning messages.
 .LP
 These options are case sensitive and must be used exactly as presented here.
 .SS "LDAP Account Management Module"
-.sp
 .LP
 The LDAP account management module validates the user's account. The
 \fBpam_sm_acct_mgmt\fR(3PAM) function authenticates to the LDAP server to
@@ -120,14 +117,12 @@ Turn off warning messages.
 These options are case sensitive, and the options must be used exactly as
 presented here.
 .SS "LDAP Password Management Module"
-.sp
 .LP
 LDAP password management is no longer supported by \fBpam_ldap\fR. Use
 \fBpam_authtok_store\fR(5) instead of \fBpam_ldap\fR for password change.
 \fBpam_authtok_store\fR(5) handles both the local and LDAP accounts and updates
 the passwords in all the repositories configured by \fBnsswitch.conf\fR(4).
 .SH ERRORS
-.sp
 .LP
 The authentication service returns the following error codes:
 .sp
@@ -136,7 +131,7 @@ The authentication service returns the following error codes:
 \fB\fBPAM_SUCCESS\fR\fR
 .ad
 .RS 20n
-The uthentication was successful.
+The authentication was successful.
 .RE
 
 .sp
@@ -344,7 +339,6 @@ other password required   pam_authtok_store.so.1 server_policy
 .in -2
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/var/ldap/ldap_client_file\fR\fR
@@ -369,7 +363,6 @@ PAM configuration file.
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -387,7 +380,6 @@ MT-Level	MT-Safe with exceptions
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBldap\fR(1), \fBidsconfig\fR(1M), \fBldap_cachemgr\fR(1M),
 \fBldapclient\fR(1M), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM),
@@ -398,7 +390,6 @@ MT-Level	MT-Safe with exceptions
 \fBpam_authtok_get\fR(5), \fBpam_authtok_store\fR(5), \fBpam_passwd_auth\fR(5),
 \fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5)
 .SH NOTES
-.sp
 .LP
 The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the
 multi-threaded application uses its own \fBPAM\fR handle.
diff --git a/usr/src/man/man5/regex.5 b/usr/src/man/man5/regex.5
index ae69ddd34f..68ae1656a7 100644
--- a/usr/src/man/man5/regex.5
+++ b/usr/src/man/man5/regex.5
@@ -12,7 +12,6 @@
 .SH NAME
 regex \- internationalized basic and extended regular expression matching
 .SH DESCRIPTION
-.sp
 .LP
 Regular Expressions (REs) provide a mechanism to select specific strings from a
 set of character strings. The Internationalized Regular Expressions described
@@ -43,14 +42,12 @@ EREs are supported by the Regular Expression Matching interfaces
 \fBregcomp\fR(3C) and \fBregexec\fR(3C).
 .SH BASIC REGULAR EXPRESSIONS
 .SS "BREs Matching a Single Character"
-.sp
 .LP
 A BRE ordinary character, a special character preceded by a backslash, or a
 period matches a single character. A bracket expression matches a single
 character or a single collating element. See \fBRE Bracket Expression\fR,
 below.
 .SS "BRE Ordinary Characters"
-.sp
 .LP
 An ordinary character is a BRE that matches itself: any character in the
 supported character set, except for the BRE special characters listed in \fBBRE
@@ -76,7 +73,6 @@ below)
 a character inside a bracket expression.
 .RE
 .SS "BRE Special Characters"
-.sp
 .LP
 A BRE \fIspecial\fR \fIcharacter\fR has special properties in certain contexts.
 Outside those contexts, or when preceded by a backslash, such a character will
@@ -154,12 +150,10 @@ The dollar sign is special when used as an anchor.
 .RE
 
 .SS "Periods in BREs"
-.sp
 .LP
 A period (\fB\&.\fR), when used outside a bracket expression, is a BRE that
 matches any character in the supported character set except NUL.
 .SS "RE Bracket Expression"
-.sp
 .LP
 A bracket expression (an expression enclosed in square brackets, [\|]) is an RE
 that matches a single collating element contained in the non-empty set of
@@ -349,7 +343,6 @@ first (after the ^, if any) and the \(mi last within the bracket expression.
 Note: Latin-1 characters such as \(ga or ^ are not printable in some locales,
 for example, the \fBja\fR locale.
 .SS "BREs Matching Multiple Characters"
-.sp
 .LP
 The following rules can be used to construct BREs matching multiple characters
 from BREs matching a single character:
@@ -425,7 +418,6 @@ the BRE c\e{1,3\e}d is matched by characters ten to thirteen.
 The behavior of multiple adjacent duplication symbols \fB(\fR \fB*\fR \fB\fR
 and intervals) produces undefined results.
 .SS "BRE Precedence"
-.sp
 .LP
 The order of precedence is as shown in the following table:
 .sp
@@ -454,7 +446,6 @@ anchoring	^  $
 .TE
 
 .SS "BRE Expression Anchoring"
-.sp
 .LP
 A BRE can be limited to matching strings that begin or end a line; this is
 called \fIanchoring\fR. The circumflex and dollar sign special characters will
@@ -497,9 +488,8 @@ For example, the BRE \fB^abcdef$\fR matches strings consisting only of
 Note: The Solaris implementation does not support anchoring in BRE
 subexpressions.
 .SH EXTENDED REGULAR EXPRESSIONS
-.sp
 .LP
-The rules specififed for BREs apply to Extended Regular Expressions (EREs) with
+The rules specified for BREs apply to Extended Regular Expressions (EREs) with
 the following exceptions:
 .RS +4
 .TP
@@ -529,7 +519,6 @@ The back reference operator is not supported.
 Anchoring (\fB^$\fR) is supported in subexpressions.
 .RE
 .SS "EREs Matching a Single Character"
-.sp
 .LP
 An ERE ordinary character, a special character preceded by a backslash, or a
 period matches a single character. A bracket expression matches a single
@@ -537,7 +526,6 @@ character or a single collating element. An \fIERE\fR \fImatching\fR \fIa\fR
 \fIsingle\fR \fIcharacter\fR enclosed in parentheses matches the same as the
 ERE without parentheses would have matched.
 .SS "ERE Ordinary Characters"
-.sp
 .LP
 An \fIordinary character\fR is an ERE that matches itself. An ordinary
 character is any character in the supported character set, except for the ERE
@@ -545,7 +533,6 @@ special characters listed in \fBERE\fR \fBSpecial\fR \fBCharacters\fR below.
 The interpretation of an ordinary character preceded by a backslash (\fB\e\fR)
 is undefined.
 .SS "ERE Special Characters"
-.sp
 .LP
 An \fIERE\fR \fIspecial\fR \fIcharacter\fR has special properties in certain
 contexts. Outside those contexts, or when preceded by a backslash, such a
@@ -642,17 +629,14 @@ The dollar sign is special when used as an anchor.
 .RE
 
 .SS "Periods in EREs"
-.sp
 .LP
 A period (\fB\&.\fR), when used outside a bracket expression, is an ERE that
 matches any character in the supported character set except NUL.
 .SS "ERE Bracket Expression"
-.sp
 .LP
 The rules for ERE Bracket Expressions are the same as for Basic Regular
 Expressions; see \fBRE Bracket Expression\fR, above).
 .SS "EREs Matching Multiple Characters"
-.sp
 .LP
 The following rules will be used to construct EREs matching multiple characters
 from EREs matching a single character:
@@ -719,7 +703,6 @@ six.
 The behavior of multiple adjacent duplication symbols \fB(\fR+\fB,\fR \fB*\fR,
 \fB?\fR and intervals) produces undefined results.
 .SS "ERE Alternation"
-.sp
 .LP
 Two EREs separated by the special character vertical-line (|) match a string
 that is matched by either. For example, the ERE a((bc)|d) matches the string
@@ -727,7 +710,6 @@ abc and the string ad. Single characters, or expressions matching single
 characters, separated by the vertical bar and enclosed in parentheses, will be
 treated as an ERE matching a single character.
 .SS "ERE Precedence"
-.sp
 .LP
 The order of precedence will be as shown in the following table:
 .sp
@@ -754,7 +736,6 @@ For example, the ERE \fBabba\||\|cde\fR matches either the string \fBabba\fR or
 the string \fBcde\fR (rather than the string \fBabbade\fR or \fBabbcde\fR,
 because concatenation has a higher order of precedence than alternation).
 .SS "ERE Expression Anchoring"
-.sp
 .LP
 An ERE can be limited to matching strings that begin or end a line; this is
 called \fIanchoring\fR. The circumflex and dollar sign special characters are
@@ -783,7 +764,6 @@ valid, but can never match because the \fBf\fR prevents the expression e$ from
 matching ending at the last character.
 .RE
 .SH SEE ALSO
-.sp
 .LP
 \fBlocaledef\fR(1), \fBregcomp\fR(3C), \fBattributes\fR(5), \fBenviron\fR(5),
 \fBlocale\fR(5), \fBregexp\fR(5)
diff --git a/usr/src/man/man5/standards.5 b/usr/src/man/man5/standards.5
index 766890ea52..43e22bb85e 100644
--- a/usr/src/man/man5/standards.5
+++ b/usr/src/man/man5/standards.5
@@ -137,7 +137,7 @@ conflicts with POSIX.2, POSIX.2a, SUS, or SUSv2, a new version that is SUSv3
 standard-conforming has been provided in \fB/usr/xpg6/bin\fR.
 .sp
 .LP
-An application that wants to use standard-conforming utilitues must set the
+An application that wants to use standard-conforming utilities must set the
 \fBPATH\fR (\fBsh\fR(1) or \fBksh\fR(1)) or \fBpath\fR (\fBcsh\fR(1))
 environment variable to specify the directories listed below in the order
 specified to get the appropriate utilities:
diff --git a/usr/src/man/man5/threads.5 b/usr/src/man/man5/threads.5
index 5d882e7d45..02b308de9b 100644
--- a/usr/src/man/man5/threads.5
+++ b/usr/src/man/man5/threads.5
@@ -74,7 +74,7 @@ which may be accessed concurrently from multiple threads of execution. To avoid
 such problems, programs may use atomic operations (see \fBatomic_ops\fR(3C)) and
 locking primitives, such as mutexes, readers/writer locks, condition variables,
 and semaphores. Note, that depending on the hardware platform, memory
-synchronization may be necesary, for more information, see \fBmembar_ops\fR(3C).
+synchronization may be necessary, for more information, see \fBmembar_ops\fR(3C).
 .LP
 POSIX, C11, and illumos threads each have their own implementation within
 \fBlibc\fR(3LIB). All implementations are interoperable, their functionality