9842 man page typos and spelling

@@ -13,11 +13,10 @@
      [\fB-f\fR \fIflags\fR] [\fB-i\fR \fIname\fR] [\fB-I\fR \fIname\fR] [\fB-g\fR \fIname\fR] [\fB-G\fR \fIname\fR]
      [\fB-l\fR \fIdir\fR] [\fB-o\fR \fIdir\fR] [\fB-s\fR \fIdir\fR] [\fB-t\fR [ ELF | AOUT]] [\fB-u\fR] [\fB-v\fR]
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBcrle\fR utility provides for the creation and display of a runtime
 linking configuration file. The configuration file is read and interpreted by
 the runtime linker, \fBld.so.1\fR(1), during process startup. The runtime
 linker attempts to read a default configuration file for all processes. For

@@ -46,11 +45,11 @@
 appropriate class of process, is recommended.
 .sp
 .LP
 Creating an incorrect configuration file in the standard location,
 \fB/var/ld\fR, can prevent programs from running, and can therefore be
-difficult to recover from. To guard against this situation, it is recommented
+difficult to recover from. To guard against this situation, it is recommended
 that new configuration files first be created in a temporary location. Then set
 the appropriate \fBLD_CONFIG\fR environment variable to this new configuration
 file. This setting causes the new configuration file to be used by the runtime
 linker instead of any default. After verification, the new configuration file
 can be moved to the default location if desired. At any time, the environment

@@ -181,11 +180,10 @@
 alternate object is created in the directory specified by the preceding
 \fB-o\fR option, or defaults to the directory in which the configuration file
 is created. The flags used by \fBdldump()\fR are specified using the \fB-f\fR
 option, or default to \fBRTLD_REL_RELATIVE\fR.
 .SH OPTIONS
-.sp
 .LP
 The following options are supported.
 .sp
 .ne 2
 .na

@@ -792,17 +790,15 @@
 With this configuration file, a replaceable search path has been specified
 together with a permanent preload object which becomes appended to the process
 environment definition.
 
 .SH EXIT STATUS
-.sp
 .LP
 The creation or display of a configuration file results in a \fB0\fR being
 returned. Otherwise, any error condition is accompanied with a diagnostic
 message and a non-zero value being returned.
 .SH NOTES
-.sp
 .LP
 The ability to tag an alternative application to use an application-specific
 configuration file, is possible if the original application contains one of the
 \fI\&.dynamic\fR tags \fBDT_FLAGS_1\fR or \fBDT_FEATURE_1\fR. Without these
 entries, a configuration file must be specified using the \fBLD_CONFIG\fR

@@ -846,11 +842,10 @@
 without the identification and error checking that would otherwise be possible.
 When processing an update (\fB-u\fR) operation for an older file that lacks
 system information, \fBcrle\fR does not add system identification information
 to the result.
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/var/ld/ld.config\fR\fR
 .ad
 .sp .6

@@ -917,11 +912,10 @@
 .RS 4n
 Audit library that is employed to \fBdldump\fR(3C) 64-bit objects.
 .RE
 
 .SH ENVIRONMENT VARIABLES
-.sp
 .LP
 There are no environment variables that are referenced by \fBcrle\fR. However,
 several environment variables affect the runtime linkers behavior in regard to
 the processing of configuration files that are created by \fBcrle\fR.
 .sp

@@ -973,11 +967,10 @@
 .RS 4n
 Disable alternative object processing from a configuration file.
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes.
 .sp
 
 .sp

@@ -989,11 +982,10 @@
 _
 Interface Stability     Committed
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBfile\fR(1), \fBld\fR(1), \fBld.so.1\fR(1), \fBdldump\fR(3C),
 \fBtempnam\fR(3C), \fBattributes\fR(5)
 .sp
 .LP