13890 Some manual pages miss spaces next to formatting

Reviewed by: Andy Fiddaman <andy@omnios.org>
Approved by: Richard Lowe <richlowe@richlowe.net>

14 files changed, 52 insertions, 205 deletions

diff --git a/usr/src/man/man1m/cfgadm_pci.1m b/usr/src/man/man1m/cfgadm_pci.1m
index ebed12b823..f89982cbbb 100644
--- a/usr/src/man/man1m/cfgadm_pci.1m
+++ b/usr/src/man/man1m/cfgadm_pci.1m
@@ -3,12 +3,11 @@
 .\" 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 CFGADM_PCI 1M "April 9, 2016"
+.TH CFGADM_PCI 1M "June 20, 2021"
 .SH NAME
 cfgadm_pci \- PCI, CompactPCI, and PCI Express Hotplug hardware specific
 commands for cfgadm
 .SH SYNOPSIS
-.LP
 .nf
 \fB/usr/sbin/cfgadm\fR [\fB-f\fR] [\fB-y\fR | \fB-n\fR] [\fB-v\fR]
      [\fB-o\fR \fIhardware_options\fR] \fB-c\fR \fIfunction\fR \fIap_id\fR [\fIap_id\fR]
@@ -39,12 +38,11 @@ commands for cfgadm
 .fi
 
 .SH DESCRIPTION
-.LP
 The PCI hardware specific library, \fB/usr/lib/cfgadm/pci.so.1\fR, provides the
 support for hot plugging PCI, CompactPCI, and PCI Express adapter cards into
 the respective hot pluggable slots in a system that is hot plug capable,
 through the \fBcfgadm\fR command (see \fBcfgadm\fR(1M)). Hot plug
-administrative models between PCI, CompactPCI, and  PCI Express remain the same
+administrative models between PCI, CompactPCI, and PCI Express remain the same
 except where noted in this document.
 .sp
 .LP
@@ -75,7 +73,6 @@ Note that the \fBap_type\fR is not the same as the information in the
 .LP
 See the \fI\fR for a detailed description of the hot plug procedure.
 .SS "PCI Express ap_id naming"
-.LP
 For attachment points located in a PCI Express hierarchy (that is, the parent
 or an ancestor is a PCI Express device), including attachment points which are
 not PCI Express devices themselves, the following naming scheme is used:
@@ -114,7 +111,7 @@ is the PCI device number in standard PCI nomenclature.
 .LP
 First, an \fIabsolute-slot-path\fR is constructed that attempts to describe the
 attachment point's topological location in more physically identifiable terms
-for the user . This \fIabsolute-slot-path\fR consists of \fIslot-path\fR
+for the user. This \fIabsolute-slot-path\fR consists of \fIslot-path\fR
 components each separated by a ":" (colon). The leaf or left-most
 \fIslot-path\fR component describes the device of the attachment point itself
 while its right adjacent \fIslot-path\fR component up to the right or top-most
@@ -167,7 +164,7 @@ Each \fIslot-id\fR consists of one of three possible forms:
 .sp
 .LP
 The precedence of which form to select flows from the lowest form number to the
-highest form number, or from top to bottowm as described above. If a form
+highest form number, or from top to bottom as described above. If a form
 cannot be successfully constructed, then the next numerically higher form is
 attempted.
 .sp
@@ -250,7 +247,7 @@ form, "slot-id form (3)", of the last \fIslot_path\fR component is used
 .LP
 Whichever final \fIap_id\fR name is used, the \fIabsolute-slot-path\fR is
 stored in the Information ("info") field which can be displayed using the
-\fB-s\fR or \fB-v\fRoptions. This information can be used to physically locate
+\fB-s\fR or \fB-v\fR options. This information can be used to physically locate
 any \fIap_id\fRs named using "ap_id form (2)" or "ap_id form (3)". The
 \fIabsolute-slot-path\fR is transformed slightly when stored in the information
 field, by the replacement of a colon (":") with forward slashes ("/") to more
@@ -261,7 +258,6 @@ right-most \fIslot-path\fR component up to the onboard host slot.
 .LP
 See the EXAMPLES section for a list of hotpluggable examples.
 .SH OPTIONS
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -410,7 +406,7 @@ attachment point's absolute slot path location, including any hardware or
 platform specific labeling information for each component in the slot path.
 Each component in the slot path will be separated by a "/" (forward slash). See
 the PCI Express ap_id naming section. For PCI Hot Plug attachment points not
-located in a PCI Express hieararchy, the \fBInformation\fR field will be the
+located in a PCI Express hierarchy, the \fBInformation\fR field will be the
 slot's system label, if any. This string will be obtained from the
 \fBslot-name\fR property of the slot's bus node. The information in the Type
 field is printed with or without the \fB-v\fR option. The occupant \fBType\fR
@@ -441,7 +437,7 @@ multi-functional device, \fBMULT\fR will get printed instead.
 .sp
 \fIboard\fR is a string representing the board type of the device. For example,
 hp is the string used for a PCI Hot Plug adapter, hs is used for a Hot Swap
-Board, nhs for a Non\(emHot Swap cPCI Board,  bhs for a Basic Hot Swap cPCI
+Board, nhs for a Non\(emHot Swap cPCI Board, bhs for a Basic Hot Swap cPCI
 Board, and fhs for a Full Hot Swap cPCI Board.
 .sp
 Most PCI cards with more than one device are not multi-function devices, but
@@ -571,7 +567,6 @@ example# \fBcfgadm -x led=active,mode=on pci0:hpc0_slot3\fR
 .RE
 
 .SH EXAMPLES
-.LP
 \fBExample 1 \fRPrinting out the Value of Each Slot
 .sp
 .LP
@@ -716,7 +711,7 @@ iou#0-pci#3:iobBADF.pci2       Location: iou#0-pci#3/iobBADF.pci2
 .LP
 In this example, the "iou#0-pci#[0-3]" represents the top-most hotpluggable
 slots in the system. Since the "iou#<n>-pci#<n>" form does not match any of the
-forms stated in the grammar specification section described earilier, we can
+forms stated in the grammar specification section described earlier, we can
 infer that such a name for the base component in this hotplug topology is
 derived from the platform through the "slot-names" property.
 
@@ -928,7 +923,7 @@ length limit, and the leaf \fIslot-path\fR component is not globally unique,
 The default form or "slot-id form (3)" of the leaf component
 ".../iob.pcie1"represents a PCI Express slot with device number 0, bound to
 driver instance 20 of "px_pci". Likewise, the default form of the leaf
-component ".../iob.pcie2" represents a  PCI Express slot with device number 0,
+component ".../iob.pcie2" represents a PCI Express slot with device number 0,
 bound to driver instance 21 of "px_pci"
 
 .SH FILES
@@ -942,7 +937,6 @@ Hardware specific library for PCI hot plugging.
 .RE
 
 .SH SEE ALSO
-.LP
 \fBcfgadm\fR(1M), \fBconfig_admin\fR(3CFGADM), \fBlibcfgadm\fR(3LIB),
 \fBattributes\fR(5)
 .sp
diff --git a/usr/src/man/man1m/datadm.1m b/usr/src/man/man1m/datadm.1m
index 929714d912..ca16dff943 100644
--- a/usr/src/man/man1m/datadm.1m
+++ b/usr/src/man/man1m/datadm.1m
@@ -3,18 +3,16 @@
 .\" 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 DATADM 1M "May 13, 2017"
+.TH DATADM 1M "June 20, 2021"
 .SH NAME
 datadm \- maintain DAT static registry file
 .SH SYNOPSIS
-.LP
 .nf
 \fB/usr/bin/datadm\fR [\fB-v\fR] [\fB-u\fR] [\fB-a\fR service_provider.conf]
      [\fB-r\fR service_provider.conf]
 .fi
 
 .SH DESCRIPTION
-.LP
 The \fBdatadm\fR utility maintains the DAT static registry file,
 \fBdat.conf\fR(4).
 .sp
@@ -29,7 +27,6 @@ a system after its installation. You can use \fBdatadm\fR to update the
 interface adapters for all the service providers currently installed is
 regenerated.
 .SH OPTIONS
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -73,7 +70,6 @@ Display the DAT static registry file, \fBdat.conf\fR.
 .RE
 
 .SH EXAMPLES
-.LP
 \fBExample 1 \fREnumerating a Device Entry
 .sp
 .LP
@@ -115,8 +111,8 @@ each port, there are two IPoIB device instances, \fBibd0\fR and \fBibd1\fR:
 .sp
 .LP
 Running the command, \fBdatadm -a /usr/share/dat/SUNWudaplt.conf\fR appends two
-new entries (if they do not already exists]) in the
-\fB/etc/dat/dat.conf\fRfile:
+new entries (if they do not already exist) in the
+\fB/etc/dat/dat.conf\fR file:
 
 .sp
 .in +2
@@ -181,7 +177,6 @@ DAT static registry file
 .RE
 
 .SH ATTRIBUTES
-.LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
 
@@ -196,6 +191,5 @@ Interface Stability	Evolving
 .TE
 
 .SH SEE ALSO
-.LP
 \fBlibdat\fR(3LIB), \fBdat.conf\fR(4),
 \fBservice_provider.conf\fR(4), \fBattributes\fR(5)
diff --git a/usr/src/man/man1m/dladm.1m b/usr/src/man/man1m/dladm.1m
index d6050c5114..c242d38ac2 100644
--- a/usr/src/man/man1m/dladm.1m
+++ b/usr/src/man/man1m/dladm.1m
@@ -44,7 +44,7 @@
 .\" Copyright 2016 Joyent, Inc.
 .\" Copyright 2020 RackTop Systems, Inc.
 .\"
-.TH DLADM 1M "May 4, 2020"
+.TH DLADM 1M "June 20, 2021"
 .SH NAME
 dladm \- administer data links
 .SH SYNOPSIS
@@ -900,7 +900,7 @@ Multiple links are included in the aggregation by specifying multiple \fB-l\fR
 options. For backward compatibility with previous versions of Solaris, the
 \fBdladm\fR command also supports the using the \fB-d\fR option (or
 \fB--dev\fR) with a device name to specify links by their underlying device
-name. The other \fB*\fR\fB-aggr\fR subcommands that take \fB-l\fRoptions also
+name. The other \fB*\fR\fB-aggr\fR subcommands that take \fB-l\fR options also
 accept \fB-d\fR.
 .RE
 
diff --git a/usr/src/man/man1m/fstyp.1m b/usr/src/man/man1m/fstyp.1m
index 3b5c623d87..14cd484cfb 100644
--- a/usr/src/man/man1m/fstyp.1m
+++ b/usr/src/man/man1m/fstyp.1m
@@ -4,18 +4,15 @@
 .\" 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 FSTYP 1M "Dec 19, 2007"
+.TH FSTYP 1M "June 20, 2021"
 .SH NAME
 fstyp \- determine file system type
 .SH SYNOPSIS
-.LP
 .nf
 \fBfstyp\fR [\fB-a\fR | \fB-v\fR] \fIspecial\fR [:\fIlogical-drive\fR]
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 \fBfstyp\fR allows the user to determine the file system type of unmounted file
 systems using heuristic programs.
 .sp
@@ -34,7 +31,6 @@ status is \fB2\fR. Other errors are printed in the same format.
 This command is unreliable and its results should not be used to make any
 decisions about subsequent use of a storage device or disk partition.
 .SH OPTIONS
-.sp
 .ne 2
 .na
 \fB\fB-a\fR\fR
@@ -150,20 +146,14 @@ superblock and varies across different \fIFSTypes\fR. See \fBufs\fR(7FS),
 .RE
 
 .SH USAGE
-.sp
-.LP
 See \fBlargefile\fR(5) for the description of the behavior of \fBfstyp\fR when
 encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
 .SH SEE ALSO
-.sp
-.LP
 \fBfsck\fR(1M), \fBmkfs_ufs\fR(1M), \fBtunefs\fR(1M), \fBattributes\fR(5),
 \fBlibfstyp\fR(3LIB), \fBlargefile\fR(5), \fBhsfs\fR(7FS), \fBufs\fR(7FS),
 \fBpcfs\fR(7FS)
 .SH NOTES
-.sp
-.LP
-The use of heuristics implies that the result of\fBfstyp\fR is not guaranteed
+The use of heuristics implies that the result of \fBfstyp\fR is not guaranteed
 to be accurate.
 .sp
 .LP
diff --git a/usr/src/man/man1m/fwflash.1m b/usr/src/man/man1m/fwflash.1m
index d81d7f7dae..eecda587a4 100644
--- a/usr/src/man/man1m/fwflash.1m
+++ b/usr/src/man/man1m/fwflash.1m
@@ -1,10 +1,11 @@
 '\" te
 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
 .\" Copyright 2020 Oxide Computer Company
+.\" Copyright 2021 Peter Tribble
 .\" 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 FWFLASH 1M "June 9, 2020"
+.TH FWFLASH 1M "June 20, 2021"
 .SH NAME
 fwflash \- firmware query and update utility
 .SH SYNOPSIS
@@ -47,7 +48,7 @@ The following options are supported:
 An optional parameter, valid only when used with the \fB-l\fR option. This
 option causes the command to list only devices of a specific class type.
 Currently supported classes are \fBIB\fR, \fBses\fR, \fBsd\fR, \fBufm\fR, or
-\fBALL\fR. If \fB-c\fR is not specified for the \fB-l\fRoption, the class
+\fBALL\fR. If \fB-c\fR is not specified for the \fB-l\fR option, the class
 defaults to \fBALL\fR.
 .RE
 
@@ -58,8 +59,8 @@ defaults to \fBALL\fR.
 .ad
 .sp .6
 .RS 4n
-The \fIdev_path\fR is absolute path name of the device that the user wants to
-modify with the \fB-f\fRor \fB-r\fR operation. If the device cannot be found,
+The \fIdev_path\fR is the absolute path name of the device that the user wants
+to modify with the \fB-f\fR or \fB-r\fR option. If the device cannot be found,
 the command fails. If the \fB-d\fR option is specified, then either \fB-f\fR or
 \fB-r\fR must also be specified.
 .RE
@@ -105,7 +106,7 @@ Display the command line usage message for \fBfwflash\fR.
 List the devices on a system available for firmware upgrade and display
 information specific to each device or device class.
 .sp
-For InfiniBand (IB) devices, the list operation  displays the \fBguid\fRs
+For InfiniBand (IB) devices, the list operation displays the \fBguid\fRs
 (Globally Unique Identifier) currently set for the HCA, as well as the current
 firmware revision installed. There are four separate \fBguid\fRs on the HCA;
 two of them can be set with the same value.
@@ -152,7 +153,7 @@ Display \fBfwflash\fR version information and exit.
 .ad
 .sp .6
 .RS 4n
-Valid only when a flash read (\fB-r\fR) or write (\fB-f\fR) operation is
+Valid only when a flash read (\fB-r\fR) or write (\fB-f\fR) option is
 specified. This option causes \fBfwflash\fR not to prompt for confirmation
 during operation and operate non-interactively. Note that there is no option
 that allows you to forcibly flash an incompatible firmware image onto a device.
@@ -162,8 +163,8 @@ that allows you to forcibly flash an incompatible firmware image onto a device.
 \fBExample 1 \fREntering Command Without Arguments
 .sp
 .LP
-The following command shows \fBfwflash\fR when the command is entered without
-arguments.
+The following command shows \fBfwflash\fR output when the command is entered
+without arguments.
 
 .sp
 .in +2
diff --git a/usr/src/man/man1m/ikecert.1m b/usr/src/man/man1m/ikecert.1m
index 601cb47f68..da2a53cd08 100644
--- a/usr/src/man/man1m/ikecert.1m
+++ b/usr/src/man/man1m/ikecert.1m
@@ -3,12 +3,11 @@
 .\" 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 IKECERT 1M "April 9, 2016"
+.TH IKECERT 1M "June 20, 2021"
 .SH NAME
 ikecert \- manipulates the machine's on-filesystem public-key certificate
 databases
 .SH SYNOPSIS
-.LP
 .nf
 \fBikecert\fR certlocal
      [\fB-a\fR | \fB-e\fR | \fB-h\fR | \fB-k\fR | \fB-l\fR | \fB-r\fR | \fB-U\fR | \fB-C\fR | \fB-L\fR]
@@ -35,7 +34,6 @@ databases
 .fi
 
 .SH DESCRIPTION
-.LP
 The \fBikecert\fR command manipulates the machine's on-filesystem public-key
 certificate databases. See the "Files" section, below.
 .sp
@@ -72,7 +70,6 @@ repository.
 The only supported PKCS#11 library and hardware is the Sun Cryptographic
 Accelerator 4000.
 .SH OPTIONS
-.LP
 Except for \fBtokens\fR, each subcommand requires one option, possibly followed
 by one or more option-specific arguments.
 .sp
@@ -234,7 +231,7 @@ matches in the database is extracted. See \fBNOTES\fR, below, for details on
 When specified with the \fBcertlocal\fR subcommand, this option generates a IKE
 public/private key pair and adds it into the local ID database. It also
 generates a certificate request and sends that to standard output. For details
-on the above options see  for details on the \fIdname\fR argument and see
+on the above options see for details on the \fIdname\fR argument and see
 ALTERNATIVE NAMES for details on the \fIaltname\fR argument(s) to this command.
 .sp
 If \fB-T\fR is specified, the hardware token will generate the pair of keys.
@@ -331,7 +328,7 @@ The list displays the identity string of the certificates, as well as, the
 private key if in the key database. The \fB-v\fR switches the output to a
 verbose mode where the entire certificate is printed.
 .sp
-If the matching ceritifcate is on a hardware token, the token ID is also
+If the matching certificate is on a hardware token, the token ID is also
 listed.
 .RE
 
@@ -346,7 +343,7 @@ When specified with the \fBcertrldb\fR subcommand, this option lists the CRLs
 in the IKE database along with any certificates that reside in the database and
 match the Issuer Name. \fBcertspec\fR can be used to specify to list a specific
 CRL. The \fB-v\fR option switches the output to a verbose mode where the entire
-certificate is printed. See \fBNOTES\fR, below, for details on\fBcertspec\fR
+certificate is printed. See \fBNOTES\fR, below, for details on \fBcertspec\fR
 patterns.
 .RE
 
@@ -541,7 +538,6 @@ token with \fBikeadm\fR(1M) once \fBin.iked\fR(1M) is running.
 .RE
 
 .SH PARAMETERS
-.LP
 The following parameters are supported:
 .sp
 .ne 2
@@ -726,7 +722,6 @@ instance.
 .RE
 
 .SH SECURITY
-.LP
 This command can save private keys of a public-private key pair into a file.
 Any exposure of a private key may lead to compromise if the key is somehow
 obtained by an adversary.
@@ -748,7 +743,6 @@ Refer to the afterword by Matt Blaze in Bruce Schneier's \fIApplied
 Cryptography: Protocols, Algorithms, and Source Code in C\fR for additional
 information.
 .SH EXAMPLES
-.LP
 \fBExample 1 \fRGenerating a Self-Signed Certificate
 .sp
 .LP
@@ -809,7 +803,6 @@ example# \fB# ikecert certlocal -kc -m 1024 -t rsa-md5 -T vca0-keystore \e
 .sp
 
 .SH EXIT STATUS
-.LP
 The following exit values are returned:
 .sp
 .ne 2
@@ -874,7 +867,6 @@ Consulted for the pathname of a PKCS#11 library.
 .RE
 
 .SH ATTRIBUTES
-.LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
 
@@ -889,7 +881,6 @@ Interface Stability	Evolving
 .TE
 
 .SH SEE ALSO
-.LP
 \fBikeadm\fR(1M), \fBin.iked\fR(1M), \fBgetdate\fR(3C), \fBike.config\fR(4),
 \fBattributes\fR(5), \fBpkcs11_softtoken\fR(5)
 .sp
@@ -901,7 +892,6 @@ Code in C\fR. Second Edition. John Wiley & Sons. New York, NY. 1996.
 RSA Labs, PKCS#11 v2.11: \fICryptographic Token Interface Standards\fR,
 November 2001.
 .SH NOTES
-.LP
 The following is the validity date and time syntax when the \fB-F\fR or
 \fB-S\fR flags are used:
 .sp
diff --git a/usr/src/man/man1m/in.rlogind.1m b/usr/src/man/man1m/in.rlogind.1m
index 7a952fa7c5..fdddcee08d 100644
--- a/usr/src/man/man1m/in.rlogind.1m
+++ b/usr/src/man/man1m/in.rlogind.1m
@@ -4,19 +4,16 @@
 .\" 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 IN.RLOGIND 1M "Oct 29, 2015"
+.TH IN.RLOGIND 1M "June 20, 2021"
 .SH NAME
 in.rlogind, rlogind \- remote login server
 .SH SYNOPSIS
-.LP
 .nf
 \fB/usr/sbin/in.rlogind\fR [\fB-k5eExXciPp\fR] [\fB-s\fR \fItos\fR] [\fB-S\fR \fIkeytab\fR]
      [\fB-M\fR \fIrealm\fR]
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 \fBin.rlogind\fR is the server for the \fBrlogin\fR(1) program.  The server
 provides a remote login facility with authentication based on Kerberos V5 or
 privileged port numbers.
@@ -104,8 +101,6 @@ interrupt signals to the remote programs. The login process propagates the
 client terminal's baud rate and terminal type, as found in the environment
 variable, \fBTERM\fR.
 .SH OPTIONS
-.sp
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -212,7 +207,7 @@ Sets the \fBIP\fR \fBTOS\fR option.
 \fB\fB-S\fR \fIkeytab\fR\fR
 .ad
 .RS 13n
-Sets the \fBKRB5\fR keytab file to use. The\fB/etc/krb5/krb5.keytab\fR file is
+Sets the \fBKRB5\fR keytab file to use. The \fB/etc/krb5/krb5.keytab\fR file is
 used by default.
 .RE
 
@@ -235,8 +230,6 @@ Same as \fB-e\fR, for backwards compatibility.
 .RE
 
 .SH USAGE
-.sp
-.LP
 \fBrlogind\fR and \fBin.rlogind\fR are IPv6-enabled. See \fBip6\fR(7P).
 \fBIPv6\fR is not currently supported with Kerberos V5 authentication.
 .sp
@@ -254,8 +247,6 @@ svc:/network/login:eklogin (rlogin with kerberos and encryption)
 .sp
 
 .SH SECURITY
-.sp
-.LP
 \fBin.rlogind\fR uses \fBpam\fR(3PAM) for authentication, account management,
 and session management. The \fBPAM\fR configuration policy, listed through
 \fB/etc/pam.conf\fR, specifies the modules to be used for \fBin.rlogind\fR.
@@ -272,11 +263,11 @@ rlogin	auth sufficient	pam_rhosts_auth.so.1
 rlogin	auth requisite	pam_authtok_get.so.1
 rlogin	auth required	pam_dhkeys.so.1
 rlogin	auth required	pam_unix_auth.so.1
-		
+
 rlogin	account required	pam_unix_roles.so.1
 rlogin	account required	pam_unix_projects.so.1
 rlogin	account required	pam_unix_account.so.1
-		
+
 rlogin	session required	pam_unix_session.so.1
 .TE
 
@@ -304,8 +295,6 @@ type the password. The \fIsufficient\fR flag indicates that authentication
 through the \fBpam_rhosts_auth.so.1\fR module is sufficient to authenticate the
 user. Only if this authentication fails is the next authentication module used.
 .SH SEE ALSO
-.sp
-.LP
 \fBlogin\fR(1), \fBsvcs\fR(1), \fBrlogin\fR(1),
 \fBin.rshd\fR(1M), \fBinetadm\fR(1M), \fBinetd\fR(1M), \fBkadmin\fR(1M),
 \fBsvcadm\fR(1M), \fBpam\fR(3PAM), \fBhosts\fR(4), \fBhosts.equiv\fR(4),
@@ -318,8 +307,6 @@ user. Only if this authentication fails is the next authentication module used.
 .LP
 \fI\fR
 .SH DIAGNOSTICS
-.sp
-.LP
 All diagnostic messages are returned on the connection associated with the
 \fBstderr\fR, after which any network connections are closed. An error is
 indicated by a leading byte with a value of 1.
@@ -354,8 +341,6 @@ The user's login shell could not be started.
 .RE
 
 .SH NOTES
-.sp
-.LP
 The authentication procedure used here assumes the integrity of each client
 machine and the connecting medium.  This is insecure, but it is useful in an
 ``open'' environment.
diff --git a/usr/src/man/man1m/in.rshd.1m b/usr/src/man/man1m/in.rshd.1m
index d1bd3d70cf..50ac4db395 100644
--- a/usr/src/man/man1m/in.rshd.1m
+++ b/usr/src/man/man1m/in.rshd.1m
@@ -4,19 +4,16 @@
 .\" 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 IN.RSHD 1M "Oct 29, 2015"
+.TH IN.RSHD 1M "June 20, 2021"
 .SH NAME
 in.rshd, rshd \- remote shell server
 .SH SYNOPSIS
-.LP
 .nf
 \fBin.rshd\fR [\fB-k5eciU\fR] [\fB-s\fR \fItos\fR] [\fB-S\fR \fIkeytab\fR] [\fB-M\fR \fIrealm\fR]
      [\fB-L\fR \fIenv_var\fR] \fIhost.port\fR
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 \fBin.rshd\fR is the server for the \fBrsh\fR(1) program. The server provides
 remote execution facilities with authentication based on Kerberos V5 or
 privileged port numbers.
@@ -135,8 +132,6 @@ passed to the normal login shell of the user. The \fBPATH\fR variable is set to
 \fBin.rshd\fR.
 .RE
 .SH OPTIONS
-.sp
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -225,7 +220,7 @@ Sets the \fBIP\fR \fBTOS\fR option.
 \fB\fB-S\fR \fIkeytab\fR\fR
 .ad
 .RS 14n
-Sets the \fBKRB5\fR keytab file to use. The\fB/etc/krb5/krb5.keytab\fR file is
+Sets the \fBKRB5\fR keytab file to use. The \fB/etc/krb5/krb5.keytab\fR file is
 used by default.
 .RE
 
@@ -240,8 +235,6 @@ Refuses connections that cannot be mapped to a name through the
 .RE
 
 .SH USAGE
-.sp
-.LP
 \fBrshd\fR and \fBin.rshd\fR are IPv6-enabled. See \fBip6\fR(7P). \fBIPv6\fR is
 not currently supported with Kerberos V5 authentication.
 .sp
@@ -257,8 +250,6 @@ svc:/network/shell:kshell (rshd with kerberos (ipv4 only))
 .sp
 
 .SH SECURITY
-.sp
-.LP
 \fBin.rshd\fR uses \fBpam\fR(3PAM) for authentication, account management, and
 session management. The \fBPAM\fR configuration policy, listed through
 \fB/etc/pam.conf\fR, specifies the modules to be used for \fBin.rshd\fR. Here
@@ -292,8 +283,6 @@ If there are no entries for the \fBrsh\fR service, then the entries for the
 \fBpam\fR(3PAM). For Kerberized \fBrsh\fR service, the appropriate \fBPAM\fR
 service name is \fBkrsh\fR.
 .SH FILES
-.sp
-.LP
 \fB/etc/hosts.equiv\fR
 .sp
 .ne 2
@@ -314,8 +303,6 @@ Kerberos configuration file.
 .RE
 
 .SH SEE ALSO
-.sp
-.LP
 \fBrsh\fR(1), \fBsvcs\fR(1), \fBinetadm\fR(1M),
 \fBinetd\fR(1M), \fBkadmin\fR(1M), \fBsvcadm\fR(1M), \fBpam\fR(3PAM),
 \fBgetnameinfo\fR(3SOCKET), \fBhosts\fR(4), \fBkrb5.conf\fR(4),
@@ -328,8 +315,6 @@ Kerberos configuration file.
 .LP
 \fI\fR
 .SH DIAGNOSTICS
-.sp
-.LP
 The following diagnostic messages are returned on the connection associated
 with \fBstderr\fR, after which any network connections are closed. An error is
 indicated by a leading byte with a value of 1 in step 8 above (\fB0\fR is
@@ -417,8 +402,6 @@ A \fIfork\fR by the server failed.
 .RE
 
 .SH NOTES
-.sp
-.LP
 The authentication procedure used here assumes the integrity of each client
 machine and the connecting medium. This is insecure, but it is useful in an
 "open" environment.
diff --git a/usr/src/man/man1m/in.telnetd.1m b/usr/src/man/man1m/in.telnetd.1m
index ba6d80c2dc..c233dccf49 100644
--- a/usr/src/man/man1m/in.telnetd.1m
+++ b/usr/src/man/man1m/in.telnetd.1m
@@ -4,18 +4,16 @@
 .\" 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 IN.TELNETD 1M "Oct 29, 2015"
+.TH IN.TELNETD 1M "June 20, 2021"
 .SH NAME
 in.telnetd, telnetd \- DARPA TELNET protocol server
 .SH SYNOPSIS
-.LP
 .nf
 \fB/usr/sbin/in.telnetd\fR [\fB-a\fR \fIauthmode\fR] [\fB-EXUh\fR] [\fB-s\fR \fItos\fR]
      [\fB-S\fR \fIkeytab\fR] [\fB-M\fR \fIrealm\fR]
 .fi
 
 .SH DESCRIPTION
-.LP
 \fBin.telnetd\fR is a server that supports the \fBDARPA\fR standard
 \fBTELNET\fR virtual terminal protocol. \fBin.telnetd\fR is normally invoked in
 the internet server (see \fBinetd\fR(1M)), for requests to connect to the
@@ -93,7 +91,6 @@ BANNER=""
 .in -2
 
 .SH OPTIONS
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -192,7 +189,7 @@ Sets the \fBIP\fR \fBTOS\fR option.
 \fB\fB-S\fR \fIkeytab\fR\fR
 .ad
 .RS 15n
-Sets the \fBKRB5\fR keytab file to use. The\fB/etc/krb5/krb5.keytab\fR file is
+Sets the \fBKRB5\fR keytab file to use. The \fB/etc/krb5/krb5.keytab\fR file is
 used by default.
 .RE
 
@@ -216,10 +213,8 @@ Disables Kerberos V5 authentication support negotiation.
 .RE
 
 .SH USAGE
-.LP
 \fBtelnetd\fR and \fBin.telnetd\fR are IPv6-enabled. See \fBip6\fR(7P).
 .SH SECURITY
-.LP
 \fBin.telnetd\fR can authenticate using Kerberos V5 authentication,
 \fBpam\fR(3PAM), or both. By default, the telnet server will accept valid
 Kerberos V5 authentication credentials from a \fBtelnet\fR client that supports
@@ -294,7 +289,6 @@ For a Kerberized telnet service, the correct \fBPAM\fR service name is
 .RE
 
 .SH SEE ALSO
-.LP
 \fBlogin\fR(1), \fBsvcs\fR(1), \fBtelnet\fR(1),
 \fBinetadm\fR(1M), \fBinetd\fR(1M), \fBkadmin\fR(1M), \fBsvcadm\fR(1M),
 \fBpam\fR(3PAM), \fBgetnameinfo\fR(3SOCKET), \fBissue\fR(4),
@@ -355,7 +349,6 @@ Ts'o, T., \fITelnet Data Encryption Option, RFC 2946\fR. September 2000.
 Ts'o, T., \fITelnet Encryption: DES 64 bit Cipher Feedback, RFC 2952\fR.
 September 2000.
 .SH NOTES
-.LP
 Some \fBTELNET\fR commands are only partially implemented.
 .sp
 .LP
diff --git a/usr/src/man/man1m/kdb5_ldap_util.1m b/usr/src/man/man1m/kdb5_ldap_util.1m
index 8beb8c03a0..0e8923241c 100644
--- a/usr/src/man/man1m/kdb5_ldap_util.1m
+++ b/usr/src/man/man1m/kdb5_ldap_util.1m
@@ -4,34 +4,27 @@
 .\" 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 KDB5_LDAP_UTIL 1M "Aug 28, 2007"
+.TH KDB5_LDAP_UTIL 1M "June 20, 2021"
 .SH NAME
 kdb5_ldap_util \- Kerberos configuration utility
 .SH SYNOPSIS
-.LP
 .nf
 \fBkdb5_ldap_util\fR  [\fB-D\fR \fIuser_dn\fR [\fB-w\fR \fIpasswd\fR]] [\fB-H\fR \fIldap_uri\fR] \fIcommand\fR
      [\fIcommand_options\fR]
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 The \fBkdb5_ldap_util\fR utility allows an administrator to manage realms,
 Kerberos services, and ticket policies. The utility offers a set of general
 options, described under OPTIONS, and a set of commands, which, in turn, have
 their own options. Commands and their options are described in their own
 subsections, below.
 .SH OPTIONS
-.sp
-.LP
 \fBkdb5_ldap_util\fR has a small set of general options that apply to the
 \fBkdb5_ldap_util\fR utility itself and a larger number of options that apply
 to specific commands. A number of these command-specific options apply to
 multiple commands and are described in their own section, below.
 .SS "General Options"
-.sp
-.LP
 The following general options are supported:
 .sp
 .ne 2
@@ -65,8 +58,6 @@ Specifies the password of \fIuser_dn\fR. This option is not recommended.
 .RE
 
 .SS "Common Command-specific Options"
-.sp
-.LP
 The following options apply to a number of \fBkdb5_ldap_util\fR commands.
 .sp
 .ne 2
@@ -134,13 +125,9 @@ Specifies the Kerberos realm of the database; by default the realm returned by
 .RE
 
 .SH \fBkdb5_ldap_util\fR COMMANDS
-.sp
-.LP
 The \fBkdb5_ldap_util\fR utility comprises a set of commands, each with its own
 set of options. These commands are described in the following subsections.
 .SS "The \fBcreate\fR Command"
-.sp
-.LP
 The \fBcreate\fR command creates a realm in a directory. The command has the
 following syntax:
 .sp
@@ -292,8 +279,6 @@ these flags.
 .RE
 
 .SS "The \fBmodify\fR Command"
-.sp
-.LP
 The \fBmodify\fR command modifies the attributes of a realm. The command has
 the following syntax:
 .sp
@@ -388,8 +373,6 @@ these flags.
 .RE
 
 .SS "The \fBview\fR Command"
-.sp
-.LP
 The \fBview\fR command displays the attributes of a realm. The command has the
 following syntax:
 .sp
@@ -414,8 +397,6 @@ See "Common Command-specific Options," above.
 .RE
 
 .SS "The \fBdestroy\fR Command"
-.sp
-.LP
 The \fBdestroy\fR command destroys a realm, including the master key stash
 file. The command has the following syntax:
 .sp
@@ -450,8 +431,6 @@ See "Common Command-specific Options," above.
 .RE
 
 .SS "The \fBlist\fR Command"
-.sp
-.LP
 The \fBlist\fR command displays the names of realms. The command has the
 following syntax:
 .sp
@@ -466,8 +445,6 @@ list
 .LP
 The \fBlist\fR command has no options.
 .SS "The \fBstashsrvpw\fR Command"
-.sp
-.LP
 The \fBstashsrvpw\fR command enables you to store the password for service
 object in a  file so that a KDC and Administration server can use it to
 authenticate to the LDAP server. The command has the following syntax:
@@ -512,8 +489,6 @@ to be stored in file.
 .RE
 
 .SS "The \fBcreate_policy\fR Command"
-.sp
-.LP
 The \fBcreate_policy\fR command creates a ticket policy in a directory. The
 command has the following syntax:
 .sp
@@ -586,8 +561,6 @@ Specifies the name of the ticket policy.
 .RE
 
 .SS "The \fBmodify_policy\fR Command"
-.sp
-.LP
 The \fBmodify_policy\fR command modifies the attributes of a ticket policy. The
 command has the following syntax:
 .sp
@@ -608,8 +581,6 @@ modify_policy \e
 The \fBmodify_policy\fR command has the same options and argument as those for
 the \fBcreate_policy\fR command.
 .SS "The \fBview_policy\fR Command"
-.sp
-.LP
 The \fBview_policy\fR command displays the attributes of a ticket policy. The
 command has the following syntax:
 .sp
@@ -644,8 +615,6 @@ Specifies the name of the ticket policy.
 .RE
 
 .SS "The \fBdestroy_policy\fR Command"
-.sp
-.LP
 The \fBdestroy_policy\fR command destroys an existing ticket policy. The
 command has the following syntax:
 .sp
@@ -692,8 +661,6 @@ Specifies the name of the ticket policy.
 .RE
 
 .SS "The \fBlist_policy\fR Command"
-.sp
-.LP
 The \fBlist_policy\fR command lists the ticket policies in the default or a
 specified realm. The command has the following syntax:
 .sp
@@ -718,8 +685,6 @@ See "Common Command-specific Options," above.
 .RE
 
 .SH TICKET FLAGS
-.sp
-.LP
 A number of \fBkdb5_ldap_util\fR commands have \fBticket_flag\fR options. These
 flags are described as follows:
 .sp
@@ -876,7 +841,6 @@ flag.
 .RE
 
 .SH EXAMPLES
-.LP
 \fBExample 1 \fRUsing \fBcreate\fR
 .sp
 .LP
@@ -892,7 +856,7 @@ Initializing database for realm 'ATHENA.MIT.EDU'
 You will be prompted for the database Master Password.
 It is important that you NOT FORGET this password.
 Enter KDC database master key: \fImaster key entered\fR
-Re-enter KDC database master key to verify: \fImaster key re-entered\fRjjjjjj
+Re-enter KDC database master key to verify: \fImaster key re-entered\fR
 .fi
 .in -2
 .sp
@@ -1196,8 +1160,6 @@ cn=service-pwd,o=org
 .sp
 
 .SH ATTRIBUTES
-.sp
-.LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
 
@@ -1212,6 +1174,4 @@ Interface Stability	Volatile
 .TE
 
 .SH SEE ALSO
-.sp
-.LP
 \fBkinit\fR(1), \fBkadmin\fR(1M), \fBkdc.conf\fR(4), \fBattributes\fR(5)
diff --git a/usr/src/man/man1m/logadm.1m b/usr/src/man/man1m/logadm.1m
index a69172a64f..cd9d95933c 100644
--- a/usr/src/man/man1m/logadm.1m
+++ b/usr/src/man/man1m/logadm.1m
@@ -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 LOGADM 1M "May 23, 2007"
+.TH LOGADM 1M "June 20, 2021"
 .SH NAME
 logadm \- manage endlessly growing log files
 .SH SYNOPSIS
-.LP
 .nf
 \fBlogadm\fR
 .fi
@@ -18,8 +17,6 @@ logadm \- manage endlessly growing log files
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 \fBlogadm\fR is a general log rotation tool that is suitable for running from
 \fBcron\fR(1M).
 .sp
@@ -106,16 +103,14 @@ owner, group ID, and permissions match the original file.
 .LP
 Three options control when old log files are expired: \fB-A\fR age \fB-C\fR
 count \fB-S\fR size. These options expire the oldest log files until a
-particular condition or conditions are met. For example, the combination
-\fB\fR\fB-C\fR \fB5\fR and the \fB\fR\fB-S\fR \fB10m\fR options expires old log
-files until there are no more than 5 of the \fBand\fR their combined disk usage
+particular condition or conditions are met. For example, the combination of the
+\fB\fR\fB-C\fR \fB5\fR and \fB\fR\fB-S\fR \fB10m\fR options expires old log
+files until there are no more than 5 of them \fBand\fR their combined disk usage
 is no more than 10 megabytes. If none of these options are specified, the
 default expiration is \fB\fR\fB-C\fR \fB10\fR which keeps ten old log files. If
 no files are to be expired, use \fB\fR\fB-C\fR \fB0\fR to prevent expiration by
 default.
 .SH OPTIONS
-.sp
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -224,7 +219,7 @@ expire it.
 after \fIcmd\fR completes. If the old log file is not removed or renamed by the
 \fIcmd\fR, \fBlogadm\fR considers it for expiration the next time that it runs
 on the specified log file. If present, the keyword \fB$file\fR is expanded in
-the specified \fIcmd\fRto the name of the file being expired.
+the specified \fIcmd\fR to the name of the file being expired.
 .sp
 This option is useful for tasks such as mailing old log files to
 administrators, or copying old log files to long term storage.
@@ -698,8 +693,6 @@ suffix of \fB\&.gz\fR.
 .RE
 
 .SH OPERANDS
-.sp
-.LP
 The following operands are supported:
 .sp
 .ne 2
@@ -714,7 +707,6 @@ is the same as the actual log file name.
 .RE
 
 .SH EXAMPLES
-.LP
 \fBExample 1 \fRRotating a File and Keeping Previous Versions
 .sp
 .LP
@@ -873,7 +865,6 @@ logadm -w apache /var/apache/logs/*_log
 .sp
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/etc/logadm.conf\fR\fR
@@ -884,8 +875,6 @@ configuration file for \fBlogadm\fR command
 .RE
 
 .SH ATTRIBUTES
-.sp
-.LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
 
@@ -900,14 +889,10 @@ Interface Stability	Evolving
 .TE
 
 .SH SEE ALSO
-.sp
-.LP
 \fBchgrp\fR(1), \fBchmod\fR(1), \fBchown\fR(1), \fBcsh\fR(1), \fBgzip\fR(1),
 \fBcron\fR(1M), \fBctime\fR(3C), \fBstrftime\fR(3C), \fBlogadm.conf\fR(4),
 \fBattributes\fR(5)
 .SH NOTES
-.sp
-.LP
 When \fBlogadm\fR applies expire conditions (supplied by the \fB-A\fR,
 \fB-C\fR, and \fB-S\fR options), it deletes files, the oldest first, until the
 conditions are satisfied. If the template used for naming the old logs
diff --git a/usr/src/man/man1m/lpadmin.1m b/usr/src/man/man1m/lpadmin.1m
index c509eafe2e..006d0994cf 100644
--- a/usr/src/man/man1m/lpadmin.1m
+++ b/usr/src/man/man1m/lpadmin.1m
@@ -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 LPADMIN 1M "May 13, 2017"
+.TH LPADMIN 1M "June 20, 2021"
 .SH NAME
 lpadmin \- configure the LP print service
 .SH SYNOPSIS
-.LP
 .nf
 \fBlpadmin\fR \fB-p\fR \fIprinter\fR {\fIoptions\fR}
 .fi
@@ -29,13 +28,11 @@ lpadmin \- configure the LP print service
 .fi
 
 .SH DESCRIPTION
-.LP
 \fBlpadmin\fR configures the LP print service by defining printers and devices.
 It is used to add and change printers, to remove printers from service, to set
 or change the system default destination, to define alerts for printer faults,
 and to mount print wheels.
 .SH OPTIONS
-.LP
 The \fBlpadmin\fR command has options for:
 .RS +4
 .TP
@@ -81,7 +78,6 @@ one,two,three
 .in -2
 
 .SS "Adding or Changing a Printer"
-.LP
 The first form of the \fBlpadmin\fR command (\fBlpadmin\fR \fB-p\fR
 \fIprinter\fR {\fIoptions\fR}) configures a new printer or changes the
 configuration of an existing printer. It also starts the print scheduler.
@@ -687,7 +683,7 @@ are generally of the format:
 
 In either case, \fIserver\fR specifies the hostname or IP address of the remote
 print server, \fIqueue\fR specifies the name of the print queue on the remote
-print server, and the optional \fB#Solaris\fRspecifies that the remote print
+print server, and the optional \fB#Solaris\fR specifies that the remote print
 server is a Solaris server when \fBlpd\fR URI format is being used.
 .sp
 For example:
@@ -714,7 +710,7 @@ In an environment where the nodename is variable, print queues are invalidated
 when the nodename changes. Using \fBlocalhost\fR as the \fIsystem-name\fR
 allows print queues to be maintained across changing nodenames. The
 \fIsystem-name\fR, as used by the print service, is only set to \fBlocalhost\fR
-when explicitely set with this option; by default, \fBlpadmin\fR sets
+when explicitly set with this option; by default, \fBlpadmin\fR sets
 \fIsystem-name\fR to \fInodename\fR. For example, if you want to configure a
 new printer on the local system, and want it called \fIprinter3\fR:
 .sp
@@ -893,7 +889,6 @@ See the \fBsmbspool\fR man page for details.
 .RE
 
 .SS "Removing a Printer Destination"
-.LP
 The \fB-x\fR \fIdest\fR option removes the destination \fIdest\fR (a printer or
 a class), from the \fBLP\fR print service. If \fIdest\fR is a printer and is
 the only member of a class, then the class is deleted, too. If \fIdest\fR is
@@ -903,7 +898,6 @@ local printers and the scheduler is still running, the scheduler is shut down.
 .LP
 No other \fIoptions\fR are allowed with \fB-x\fR.
 .SS "Setting/Changing the System Default Destination"
-.LP
 The \fB-d\fR [\fIdest\fR] option makes \fIdest\fR (an existing printer or
 class) the new system default destination. If \fIdest\fR is not supplied, then
 there is no system default destination. No other \fIoptions\fR are allowed with
@@ -952,7 +946,7 @@ terminals, one is arbitrarily chosen.
 Do not send messages for the current condition. An administrator can use this
 option to temporarily stop receiving further messages about a known problem.
 Once the \fIprint-wheel\fR has been mounted and subsequently unmounted,
-messages are sent againwhen the number of print requests reaches the threshold
+messages are sent again when the number of print requests reaches the threshold
 specified by the \fB-Q\fR option.
 .RE
 
@@ -1029,14 +1023,12 @@ anyone submits a print request for the print wheel when it is not mounted.
 .RE
 
 .SH PREDEFINED OPTIONS USED WITH THE \fB-o\fR OPTION
-.LP
 A number of options, described below, are predefined for use with \fB-o\fR.
 These options are used for adjusting printer capabilities, adjusting printer
 port characteristics, configuring network printers, and controlling the use of
 banner. The \fB-o\fR also supports an arbitrary \fB\fIkeyword\fR=\fIvalue\fR\fR
 format, which is referred to below as an undefined option.
 .SS "Adjusting Printer Capabilities"
-.LP
 The \fBlength\fR, \fBwidth\fR, \fBcpi\fR, and \fBlpi\fR parameters can be used
 in conjunction with the \fB-o\fR option to adjust printer capabilities. The
 format of the parameters and their values is as follows:
@@ -1082,7 +1074,6 @@ lpadmin -p \fIprintername\fR -o lpi=\fR
 .sp
 
 .SS "Adjusting Printer Port Characteristics"
-.LP
 You use the \fBstty\fR keyword in conjunction with the o option to adjust
 printer port characteristics. The general form of the \fBstty\fR portion of the
 command is:
@@ -1126,7 +1117,6 @@ The default can be reset by:
 .sp
 
 .SS "Configuring Network Printers"
-.LP
 The \fBdest\fR, \fBprotocol\fR, \fBbsdctrl\fR, and \fBtimeout\fR parameters are
 used in conjunction with the \fB-o\fR option to configure network printers. The
 format of these keywords and their assigned values is as follows:
@@ -1169,7 +1159,6 @@ lpadmin -p \fIprintername\fR -o timeout=
 .sp
 
 .SS "Controlling the Use of the Banner Page"
-.LP
 Use the following commands to control the use of the banner page:
 .sp
 .in +2
@@ -1200,7 +1189,6 @@ The fourth command (\fB-o\fR \fBbanner=never\fR) causes a banner page never to
 be printed, even if a user specifies \fBlp\fR \fB-o\fR \fBbanner\fR. The root
 user can override this command.
 .SS "Undefined Options"
-.LP
 The \fB-o\fR option supports the use of arbitrary, user-defined options with
 the following format:
 .sp
@@ -1237,7 +1225,6 @@ Sets boolean values \fBfoo=true | foo=false\fR.
 .RE
 
 .SH EXAMPLES
-.LP
 In the following examples, \fIprtr\fR can be any name up to 14 characters and
 can be the same name as the \fBping\fR(1M) name.
 .LP
@@ -1278,7 +1265,6 @@ example# \fBaccept \fIprtr\fR\fR
 .sp
 
 .SH EXIT STATUS
-.LP
 The following exit values are returned:
 .sp
 .ne 2
@@ -1335,7 +1321,6 @@ System printer configuration database
 .RE
 
 .SH ATTRIBUTES
-.LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
 
@@ -1350,7 +1335,6 @@ Interface Stability	Obsolete
 .TE
 
 .SH SEE ALSO
-.LP
 \fBenable\fR(1), \fBlp\fR(1), \fBlpstat\fR(1), \fBmail\fR(1), \fBstty\fR(1),
 \fBaccept\fR(1M), \fBlpforms\fR(1M), \fBlpsched\fR(1M), \fBlpsystem\fR(1M),
 \fBping\fR(1M), \fBdial\fR(3NSL), \fBterminfo\fR(4), \fBattributes\fR(5)
@@ -1358,7 +1342,6 @@ Interface Stability	Obsolete
 .LP
 \fI\fR
 .SH NOTES
-.LP
 When using lpadmin to provide access to a remote printer, remote configuration
 data is stored in \fB/etc/printers.conf\fR. This data includes a \fBbsdaddr\fR
 and a \fBprinter-uri-supported\fR attribute. The data in this file can be
diff --git a/usr/src/man/man1m/smrsh.1m b/usr/src/man/man1m/smrsh.1m
index 40e3b5f8cb..190965a880 100644
--- a/usr/src/man/man1m/smrsh.1m
+++ b/usr/src/man/man1m/smrsh.1m
@@ -23,7 +23,7 @@
 .\" 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 DAMAGES.
 .\" Copyright (c) 2009, Sun Microsystems, Inc.  All Rights Reserved.
-.TH SMRSH 1M "May 23, 2021"
+.TH SMRSH 1M "June 20, 2021"
 .SH NAME
 smrsh \- restricted shell for sendmail
 .SH SYNOPSIS
@@ -51,7 +51,7 @@ acceptable commands. It also rejects any commands with the characters: \fB,\fR,
 Initial pathnames on programs are stripped, so forwarding to
 \fB/usr/ucb/vacation\fR, \fB/usr/bin/vacation\fR,
 \fB/home/server/mydir/bin/vacation\fR, and \fBvacation\fR all actually forward
-to\fB/var/adm/sm.bin/vacation\fR.
+to \fB/var/adm/sm.bin/vacation\fR.
 .sp
 .LP
 System administrators should be conservative about populating
diff --git a/usr/src/man/man1m/syslogd.1m b/usr/src/man/man1m/syslogd.1m
index 9e1c58e64f..42e34de642 100644
--- a/usr/src/man/man1m/syslogd.1m
+++ b/usr/src/man/man1m/syslogd.1m
@@ -4,19 +4,16 @@
 .\" 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 SYSLOGD 1M "Oct 17, 2013"
+.TH SYSLOGD 1M "June 20, 2021"
 .SH NAME
 syslogd \- log system messages
 .SH SYNOPSIS
-.LP
 .nf
 \fB/usr/sbin/syslogd\fR [\fB-d\fR] [\fB-f\fR \fIconfigfile\fR] [\fB-m\fR \fImarkinterval\fR]
      [\fB-p\fR \fIpath\fR] [\fB-t\fR | \fB-T\fR]
 .fi
 
 .SH DESCRIPTION
-.sp
-.LP
 \fBsyslogd\fR reads and forwards system messages to the appropriate log files
 or users, depending upon the priority of a message and the system facility from
 which it originates. The configuration file \fB/etc/syslog.conf\fR (see
@@ -99,8 +96,6 @@ equivalent to the \fB-t\fR command-line option. The default value for
 .RE
 
 .SH OPTIONS
-.sp
-.LP
 The following options are supported:
 .sp
 .ne 2
@@ -168,7 +163,6 @@ messages. See \fBEXAMPLES\fR.
 .RE
 
 .SH EXAMPLES
-.LP
 \fBExample 1 \fR\fBsyslogd\fR Output Without Message ID Generation Enabled
 .sp
 .LP
@@ -189,7 +183,7 @@ Sep 29 21:41:18 cathy unix: alloc /: file system full
 .LP
 The following example shows the output from \fBsyslogd\fR when message \fBID\fR
 generation \fBis\fR enabled. The message \fBID\fR is displayed when writing to
-log file\fB/var/adm/messages\fR.
+log file \fB/var/adm/messages\fR.
 
 .sp
 .in +2
@@ -233,7 +227,6 @@ systems.
 .sp
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/etc/syslog.conf\fR\fR
@@ -305,14 +298,10 @@ Network services for each transport
 .RE
 
 .SH SEE ALSO
-.sp
-.LP
 \fBlogger\fR(1), \fBsvcs\fR(1), \fBmsgid\fR(1M), \fBsvcadm\fR(1M),
 \fBsvccfg\fR(1M), \fBsyslog\fR(3C), \fBsyslog.conf\fR(4), \fBattributes\fR(5),
 \fBsignal.h\fR(3HEAD), \fBsmf\fR(5), \fBlog\fR(7D)
 .SH NOTES
-.sp
-.LP
 The \fBmark\fR message is a system time stamp, and so it is only defined for
 the system on which \fBsyslogd\fR is running. It can not be forwarded to other
 systems.