Fix 181 typos in user-facing documentation

(cherry picked from commit fe365afb433bb39d4f3a6b68b3fd8e8daf5370c8)

src/lib/libast/man/aso.3

@@ -218,7 +218,7 @@ The default value \f50\fP disables the test.
 If \f5errorf\fP != \f50\fP then it is called for each \fIASO\fP fatal library condition.
 \f5type\fP may be one of: \f5ASO_METHOD\fP - a method error; \f5ASO_HUNG\fP - \f5asoloop\fP() was called
 \f52**Asometh_t.hung\fP times with no access to the loop resource.
-\f5mesg\fP is a 0-terminated messsage description.
+\f5mesg\fP is a 0-terminated message description.
 .Ss "  void ASODISC(Asodisc_t* disc, Asoerror_f errorf);"
 .PP
 This function-like-macro initializes \f5disc->version = ASO_VERSION\fP, \f5disc->errorf = errorf\fP,
@@ -248,7 +248,7 @@ When supported by the hardware / compiler, the library provides the "\fBintrinsi
 .Tp
 \f5ASO_SIGNAL\fP:
 This method type is suitable only for single-process single-thread applications.
-It can be used to provide locking between asyncronous \fBsignal\fP(2) handlers
+It can be used to provide locking between asynchronous \fBsignal\fP(2) handlers
 and the main program.
 The library provides the "\fBsignal\fP" method with type \f5ASO_SIGNAL\fP.
 This is the default method type when \f5ASO_INTRINSIC\fP is not supported.
@@ -265,7 +265,7 @@ The \fB-ltaso\fP library provides the "\fBspin\fP" (using \fBpthread_spin_lock\f
 \f5ASO_PROCESS\fP:
 This method type is suitable for single-process single-thread, and multi-process applications.
 Some \f5ASO_PROCESS\fP methods may also be suitable for multi-thread applications (if they have the \f5ASO_THREAD\fP type.)
-These methods are typically and noticably \fIslow\fP, up to 2 orders of magnitude slower than
+These methods are typically and noticeably \fIslow\fP, up to 2 orders of magnitude slower than
 \f5ASO_INTRINSIC\fP for some applications.
 They are provided as a last resort when other methods are not available.
 The library provides the "\fBsemaphore\fP" method with type \f5ASO_PROCESS|ASO_THREAD|ASO_SIGNAL\fP
@@ -343,7 +343,7 @@ Unlike other \fIAST\fP library discipline/method functions which can instantiate
 multiple discpline/method handles within a single process, the \fIASO\fP
 library allows only one discipline and method to be set at a time, with the additional
 restriction that it may only be set by the main and only thread of the calling process.
-For this reason there is no open/close interface with an instantation handle;
+For this reason there is no open/close interface with an instantiation handle;
 instead the global discipline/method is simply initialized by \f5asoinit()\fP.
 
 \f5ASO_THREAD\fP and \f5ASO_PROCESS\fP methods rely on the \f5Asometh_t.lockf()\fP

src/lib/libast/man/compat.3

@@ -100,4 +100,4 @@ and then call
 .L foo
 you may end up with the local implementation of
 .LR foo ,
-and then you get what you payed for.
+and then you get what you paid for.

src/lib/libast/man/hash.3

@@ -525,7 +525,7 @@ must be called to terminate the scan.
 is returned on error.
 .TP
 .L "Hash_bucket_t* hashnext(Hash_position_t* pos)"
-Returnes a pointer to the next bucket in the sequential scan set up by
+Returns a pointer to the next bucket in the sequential scan set up by
 .L hashscan()
 on
 .LR pos .

src/lib/libast/man/magic.3

@@ -139,7 +139,7 @@ on
 .IR st .
 .L magictype
 always returns a non-null string.
-If errors are encounterd on
+If errors are encountered on
 .I path
 then the return value will contain information on those errors, e.g.,
 .LR "cannot stat" .
@@ -431,7 +431,7 @@ The
 field is the most important because it is this field that is presented
 to the outside world.
 When constructing description
-fields one must be very careful to follow the style layed out in the
+fields one must be very careful to follow the style laid out in the
 magic file, lest yet another layer of inconsistency creep into the system.
 The description for each matching record in an entry are concatenated
 to form the complete magic type.

src/lib/libast/man/mime.3

@@ -109,7 +109,7 @@ returns the type string for
 .IR path .
 .L mimetype
 always returns a non-null string.
-If errors are encounterd on
+If errors are encountered on
 .I path
 then the return value will be
 .LR "error" .

src/lib/libast/man/path.3

@@ -291,7 +291,7 @@ specific
 .IR probe (1)
 information file for the
 .I lang
-langauge processor
+language processor
 .IR proc .
 If
 .I "path == 0"

src/lib/libast/man/preroot.3

@@ -58,7 +58,7 @@ All pathnames rooted at
 .L /
 are first searched for in the process preroot directory
 and then in the system root directory.
-Setting the process preroot is a priveleged operation controlled by the
+Setting the process preroot is a privileged operation controlled by the
 .IR /etc/preroot (1)
 command.
 .PP

src/lib/libast/man/proc.3

@@ -212,7 +212,7 @@ The child effective group id is set to the real group id.
 Parent pipe errors are ignored.
 .TP
 .L PROC_OVERLAY
-The current process is overlayed by
+The current process is overlaid by
 .I command
 if possible
 (i.e., the

src/lib/libast/man/sfio.3

@@ -443,7 +443,7 @@ This flag guarantees that data written in any single \f5sfwrite()\fP or
 \f5sfputr()\fP call will always be output as a whole to the output device.
 This is useful in certain applications (e.g., networking) where a complex object
 must be output without being split in different system calls.
-Note that the respective stream still buffers data as much as the buffer can accomodate.
+Note that the respective stream still buffers data as much as the buffer can accommodate.
 .Tp
 \f5SF_MTSAFE\fP:
 This flag indicates that the respective stream may be accessed by more than one threads.
@@ -692,7 +692,7 @@ As with \f5SFMTX_LOCK\fP,
 an attempt to clear the lock count without a previously successful lock
 may result in undefined behavior.
 .PP
-.Ss "INPUT/OUPUT OPERATIONS"
+.Ss "INPUT/OUTPUT OPERATIONS"
 .PP
 .Ss "  int sfgetc(Sfio_t* f)"
 .Ss "  int sfputc(Sfio_t* f, int c)"
@@ -903,7 +903,7 @@ If \f5n > 0\fP, the stream I/O position is advanced by \f5n\fP.
 If \f5n < 0\fP, the stream I/O position is advanced by the amount
 of available data.
 For example, a successful \f5sfreserve(f, -1, -1)\fP call will return a
-buffer of data and simultanously advance the stream I/O position by the amount
+buffer of data and simultaneously advance the stream I/O position by the amount
 indicated by \f5sfvalue(f)\fP.
 .Tp
 \f5type == SF_LOCKR\fP:
@@ -1008,7 +1008,7 @@ can be modified by this function to redirect formatting or scanning.
 For example, consider a call from a \f5sfprintf()\fP function to process an
 unknown pattern \f5%t\fP (which we may take to mean ``time'') based on a
 formatting environment \f5fe\fP.
-\f5fe->extf\fP may reset \f5fe->fmt\fP to `\f5d\fP' upon returing
+\f5fe->extf\fP may reset \f5fe->fmt\fP to `\f5d\fP' upon returning
 to cause \f5sfprintf()\fP to process the value being formatted as an integer.
 
 Below are the fields of \f5Sffmt_t\fP:

src/lib/libast/man/vmalloc.3

@@ -235,7 +235,7 @@ Additional space will be set to zero.
 is similar to \fIvmnewof\fP but it neither copies data nor clears space.
 .PP
 .I vmgetmem
-provides a handy function to creat/close regions and allocate/free memory
+provides a handy function to create/close regions and allocate/free memory
 based on chunks of memory obtained from the heap region \fIVmheap\fP.
 .TP
 .MW "vmgetmem(0,0,0)"
@@ -530,7 +530,7 @@ A \f5Vmstat_t\fP structure has at least these members:
 .fi
 .in -.5i
 .PP
-Bookeeping overhead is counted in \f5extent\fP,
+Bookkeeping overhead is counted in \f5extent\fP,
 but not in \f5s_busy\fP or \f5s_free\fP.
 .PP
 .I vmtrace