13890 Some manual pages miss spaces next to formatting

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

4 files changed, 30 insertions, 40 deletions

diff --git a/usr/src/man/man4/NISLDAPmapping.4 b/usr/src/man/man4/NISLDAPmapping.4
index e0aacf05eb..e1b30af0e0 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 "September 12, 2020"
+.TH NISLDAPMAPPING 4 "June 20, 2021"
 .SH NAME
 NISLDAPmapping \- mapping file used by the NIS server components
 .SH SYNOPSIS
@@ -33,7 +33,7 @@ customize your \fBNISLDAPmapping\fR file as you require.
 .sp
 .LP
 Each attribute defined below can be specified
-in\fB/var/yp/NISLDAPmappingLDAP\fR or as an LDAP attribute. If both are
+in \fB/var/yp/NISLDAPmapping\fR or as an LDAP attribute. If both are
 specified, then the attribute in \fB/var/yp/NISLDAPmapping\fR (including empty
 values) takes precedence.
 .sp
@@ -700,7 +700,7 @@ below, including examples of complex attribute to field conversions.
 .ad
 .sp .6
 .RS 4n
- Specifies how an LDAP attribute value is derived from a NIS entriy field
+ Specifies how an LDAP attribute value is derived from a NIS entry field
 value.
 .sp
 The syntax for the \fBnisLDAPattributeFromField\fR attribute is as follows:
diff --git a/usr/src/man/man4/power.conf.4 b/usr/src/man/man4/power.conf.4
index 0fdb2be5ad..56f841fe23 100644
--- a/usr/src/man/man4/power.conf.4
+++ b/usr/src/man/man4/power.conf.4
@@ -3,17 +3,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 POWER.CONF 4 "May 13, 2017"
+.TH POWER.CONF 4 "June 20, 2021"
 .SH NAME
 power.conf \- Power Management configuration information file
 .SH SYNOPSIS
-.LP
 .nf
 \fB/etc/power.conf\fR
 .fi
 
 .SH DESCRIPTION
-.LP
 The \fBpower.conf\fR file is used by the Power Management configuration program
 \fBpmconfig\fR(1M), to initialize the settings for Power Management. If you
 make changes to this file, you must run \fBpmconfig\fR(1M) manually for the
@@ -30,7 +28,6 @@ power when the device is idle.
 All entries in the \fBpower.conf\fR file are processed in the order that they
 occur in the file.
 .SS "Automatic Device Power Management"
-.LP
 Devices with drivers that use the automatic device Power Management interfaces
 are automatically power managed if the \fBautopm\fR entry is enabled. The
 \fBautopm\fR entry is described near the end of this section. The
@@ -198,7 +195,7 @@ device-thresholds \fI/pci@f0000/xfb@0 (0) (3m 5m 15m)\fR
 .LP
 would set the \fIthreshold\fR time for the \fBMonitor\fR component of the
 specific \fBxfb\fR card to go from \fBOn\fR to \fBStandby in\fR 15 minutes, the
-\fIthreshold\fR for \fBMonitor\fR to go from \fBStandby\fR to \fBSuspend\fRin 5
+\fIthreshold\fR for \fBMonitor\fR to go from \fBStandby\fR to \fBSuspend\fR in 5
 minutes, and the \fIthreshold\fR for \fBMonitor\fR to go from \fBSuspend\fR to
 \fBOff\fR in 3 minutes. The threshold for \fBFrame Buffer\fR to go from
 \fBOn\fR to \fBOff\fR is 0 seconds.
@@ -451,7 +448,6 @@ Once every device is at its lowest possible power state, additional power
 savings can be obtained by putting the system into a sleep state (if the
 platform hardware is capable of doing so).
 .SS "S3 Support"
-.LP
 Because of reliability problems encountered in BIOS implementations of X86
 systems not produced by Sun Microsystems, by default, only X86 workstation
 products produced by Sun are considered to support S3 (suspend to RAM). To
@@ -483,7 +479,6 @@ The system does not support entry into S3 state.
 .RE
 
 .SS "Automatic Entry Into S3"
-.LP
 If supported by your platform, an autoS3 entry can be used to enable or disable
 automatic entry into the S3 state. When in the S3 state, the power button,
 keyboard and mouse activity or network traffic (depending upon the capabilities
@@ -528,7 +523,6 @@ The system does not automatically enter the S3 state.
 .RE
 
 .SS "System Power Management"
-.LP
 The system Power Management entries control Power Management of the entire
 system using the suspend-resume feature. When the system is suspended, the
 complete current state is saved on the disk before power is removed. On reboot,
@@ -725,7 +719,6 @@ been locked down. It is recommended that statefile be placed on a file system
 with at least 10 Mbytes of free space. In case there is no statefile entry at
 boot time, an appropriate new entry is automatically created by the system.
 .SH EXAMPLES
-.LP
 \fBExample 1 \fRDisabling Automatic Device Power Management
 .sp
 .LP
@@ -755,7 +748,6 @@ autopm disable
 Then run \fBpmconfig\fR or reboot. See \fBpmconfig\fR(1M) for more information.
 
 .SH ATTRIBUTES
-.LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
 
@@ -766,11 +758,10 @@ c | c
 l | l .
 ATTRIBUTE TYPE	ATTRIBUTE VALUE
 _
-Interface stability 	Committed
+Interface stability	Committed
 .TE
 
 .SH SEE ALSO
-.LP
 \fBpmconfig\fR(1M), \fBpowerd\fR(1M), \fBuadmin\fR(2),
 \fBlibdevinfo\fR(3LIB), \fBattributes\fR(5), \fBcpr\fR(7), \fBldterm\fR(7M),
 \fBpm\fR(7D), \fBpm-components\fR(9P), \fBremovable-media\fR(9P)
@@ -778,7 +769,6 @@ Interface stability 	Committed
 .LP
 \fIWriting Device Drivers\fR
 .SH NOTES
-.LP
 SPARC desktop models first shipped after October 1, 1995 and before July 1,
 1999 comply with the United States Environmental Protection Agency's \fIEnergy
 Star Memorandum of Understanding #2\fR guidelines and have \fBautoshutdown\fR
diff --git a/usr/src/man/man4/terminfo.4 b/usr/src/man/man4/terminfo.4
index cadbccc0ef..1666d8e3f9 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 "December 28, 2020"
+.TH TERMINFO 4 "June 20, 2021"
 .SH NAME
 terminfo \- terminal and printer capability database
 .SH SYNOPSIS
@@ -56,15 +56,15 @@ escaped by using a backslash. Each device entry has the following format:
 .LP
 The first line, commonly referred to as the header line, must begin in column
 one and must contain at least two aliases separated by vertical bars. The last
-field in the header line must be the  long name of the device and it may
+field in the header line must be the long name of the device and it may
 contain any string. Alias names must be unique in the \fBterminfo\fR database
-and they must conform to system file naming  conventions. See \fBtic\fR(1M).
+and they must conform to system file naming conventions. See \fBtic\fR(1M).
 They cannot, for example, contain white space or slashes.
 .sp
 .LP
 Every device must be assigned a name, such as "vt100". Device names (except the
 long name) should be chosen using the following conventions. The name should
-not contain hyphens because hyphens are  reserved for use when adding suffixes
+not contain hyphens because hyphens are reserved for use when adding suffixes
 that indicate special modes.
 .sp
 .LP
@@ -107,7 +107,7 @@ The \fBterminfo\fR reference manual page is organized in two sections:
 \fBPART 2: PRINTER CAPABILITIES\fR
 .RE
 .SS "PART 1: DEVICE CAPABILITIES"
-Capabilities in \fBterminfo\fR are of three types:  Boolean capabilities (which
+Capabilities in \fBterminfo\fR are of three types: Boolean capabilities (which
 show that a device has or does not have a particular feature), numeric
 capabilities (which quantify particular features of a device), and string
 capabilities (which provide sequences that can be used to perform particular
@@ -942,7 +942,7 @@ complex entries in the \fBterminfo\fR file as of this writing.
 
 .SS "Types of Capabilities in the Sample Entry"
 The sample entry shows the formats for the three types of \fBterminfo\fR
-capabilities listed:  Boolean, numeric, and string. All capabilities specified
+capabilities listed: Boolean, numeric, and string. All capabilities specified
 in the \fBterminfo\fR source file must be followed by commas, including the
 last capability in the source file. In \fBterminfo\fR source files,
 capabilities are referenced by their capability names (as shown in the previous
@@ -964,7 +964,7 @@ sequence) are listed by a two- to five-character capname, an `=', and a string
 ended by the next occurrence of a comma. A delay in milliseconds may appear
 anywhere in such a capability, preceded by \fB$\fR and enclosed in angle
 brackets, as in \fBel=\eEK$<3>\fR. Padding characters are supplied by
-\fBtput\fR. The delay can be any of the following:  a number, a number followed
+\fBtput\fR. The delay can be any of the following: a number, a number followed
 by an asterisk, such as \fB5*\fR, a number followed by a slash, such as
 \fB5/\fR, or a number followed by both, such as \fB5*/\fR. A `\fB*\fR\fB\&'\fR
 shows that the padding required is proportional to the number of lines affected
@@ -1240,7 +1240,7 @@ push strlen(pop)
 .ad
 .sp .6
 .RS 4n
-arithmetic (\fB%m\fR is mod):  push(pop integer2 op pop integer1)
+arithmetic (\fB%m\fR is mod): push(pop integer2 op pop integer1)
 .RE
 
 .sp
@@ -1250,7 +1250,7 @@ arithmetic (\fB%m\fR is mod):  push(pop integer2 op pop integer1)
 .ad
 .sp .6
 .RS 4n
-bit operations:  push(pop integer2 op pop integer1)
+bit operations: push(pop integer2 op pop integer1)
 .RE
 
 .sp
@@ -1260,7 +1260,7 @@ bit operations:  push(pop integer2 op pop integer1)
 .ad
 .sp .6
 .RS 4n
-logical operations:  push(pop integer2 op pop integer1)
+logical operations: push(pop integer2 op pop integer1)
 .RE
 
 .sp
@@ -1270,7 +1270,7 @@ logical operations:  push(pop integer2 op pop integer1)
 .ad
 .sp .6
 .RS 4n
-logical operations:  and, or
+logical operations: and, or
 .RE
 
 .sp
@@ -1280,7 +1280,7 @@ logical operations:  and, or
 .ad
 .sp .6
 .RS 4n
-unary operations:  push(op pop)
+unary operations: push(op pop)
 .RE
 
 .sp
@@ -1828,7 +1828,7 @@ 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"
-Let us define two methods of color manipulation:  the Tektronix method and the
+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)
 from which a user can select "current" foreground and background colors. Thus a
 terminal can support up to N colors mixed into N*N color-pairs to be displayed
@@ -1844,7 +1844,7 @@ and color-pairs that can be displayed on the screen at the same time. If a
 terminal can change the definition of a color (for example, the Tektronix 4100
 and 4200 series terminals), this should be specified with \fBccc\fR (can change
 color). To change the definition of a color (Tektronix 4200 method), use
-\fBinitc\fR (initialize color). It requires four arguments:  color number
+\fBinitc\fR (initialize color). It requires four arguments: color number
 (ranging from 0 to \fBcolors\fR\(mi1) and three RGB (red, green, and blue)
 values or three HLS colors (Hue, Lightness, Saturation). Ranges of RGB and HLS
 values are terminal dependent.
@@ -1863,9 +1863,9 @@ different from RGB and HLS, a mapping to either RGB or HLS must be developed.
 .LP
 To set current foreground or background to a given color, use \fBsetaf\fR (set
 ANSI foreground) and \fBsetab\fR (set ANSI background). They require one
-parameter:  the number of the color. To initialize a color-pair (HP method),
-use \fBinitp\fR (initialize pair). It requires seven parameters:  the number of
-a color-pair (range=0 to \fBpairs\fR\(mi1), and six RGB values:  three for the
+parameter: the number of the color. To initialize a color-pair (HP method),
+use \fBinitp\fR (initialize pair). It requires seven parameters: the number of
+a color-pair (range=0 to \fBpairs\fR\(mi1), and six RGB values: three for the
 foreground followed by three for the background. (Each of these groups of three
 should be in the order RGB.) When \fBinitc\fR or \fBinitp\fR are used, RGB or
 HLS arguments should be in the order "red, green, blue" or "hue, lightness,
@@ -2209,8 +2209,8 @@ Using any of the control sequences in these strings will imply a change in some
 of the values of \fBorc\fR, \fBorhi\fR, \fBorl\fR, and \fBorvi\fR. Also, the
 distance moved when a wide character is printed, \fBwidcs\fR, changes in
 relation to \fBorc\fR. The distance moved when a character is printed in micro
-mode, \fBmcs\fR, changes similarly, with one exception:  if the distance is 0
-or 1, then no change is assumed (see items marked with  * in the following
+mode, \fBmcs\fR, changes similarly, with one exception: if the distance is 0
+or 1, then no change is assumed (see items marked with * in the following
 table).
 .sp
 .LP
@@ -2336,7 +2336,7 @@ mode.
 .LP
 The movement made when a character is printed in the rightmost position varies
 among printers. Some make no movement, some move to the beginning of the next
-line, others move to the beginning of the same line. \fBterminfo\fRhas boolean
+line, others move to the beginning of the same line. \fBterminfo\fR has boolean
 capabilities for describing all three cases.
 .sp
 .in +2
@@ -2425,7 +2425,7 @@ Miscellaneous Motion Strings
 .sp
 
 .SS "Margins"
-\fBterminfo\fR provides two strings for setting margins on terminals:  one for
+\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
 margins, for the top and bottom margins of each page. Furthermore, some
 printers require not using motion strings to move the current position to a
@@ -2912,6 +2912,6 @@ 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
 description gradually, using partial descriptions with a screen oriented
 editor, such as \fBvi\fR, to check that they are correct. To easily test a new
-terminal description the environment variable \fBTERMINFO\fR  can be set to the
+terminal description the environment variable \fBTERMINFO\fR can be set to the
 pathname of a directory containing the compiled description, and programs will
 look there rather than in \fB/usr/share/lib/terminfo\fR.
diff --git a/usr/src/man/man4/tnf_kernel_probes.4 b/usr/src/man/man4/tnf_kernel_probes.4
index b7c84e1e41..12ab068ccb 100644
--- a/usr/src/man/man4/tnf_kernel_probes.4
+++ b/usr/src/man/man4/tnf_kernel_probes.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 TNF_KERNEL_PROBES 4 "May 16, 2020"
+.TH TNF_KERNEL_PROBES 4 "June 20, 2021"
 .SH NAME
 tnf_kernel_probes \- TNF kernel probes
 .SH DESCRIPTION
@@ -438,7 +438,7 @@ Pagein start event.  This event signals the initiation of pagein I/O.
 .sp
 .ne 2
 .na
-\fB\fIvnode\fRand\fIoffset\fR\fR
+\fB\fIvnode\fR and \fIoffset\fR\fR
 .ad
 .RS 18n
 Identifies the file and offset to be paged in.