ispell sweep of share/man/man9/*.

27 files changed, 38 insertions, 38 deletions

diff --git a/share/man/man9/BUF_TIMELOCK.9 b/share/man/man9/BUF_TIMELOCK.9
index ece1ead..2c9c6d4 100644
--- a/share/man/man9/BUF_TIMELOCK.9
+++ b/share/man/man9/BUF_TIMELOCK.9
@@ -62,7 +62,7 @@ See
 .Xr lockmgr 9
 for details.
 .It Fa wmesg
-The wmesg used in any sleeps while aquiring the lock.
+The wmesg used in any sleeps while acquiring the lock.
 .It Fa catch
 Priority OR'd into the sleep's priority.
 .It Fa timo
diff --git a/share/man/man9/BUS_SETUP_INTR.9 b/share/man/man9/BUS_SETUP_INTR.9
index 33daa42..1124147 100644
--- a/share/man/man9/BUS_SETUP_INTR.9
+++ b/share/man/man9/BUS_SETUP_INTR.9
@@ -101,6 +101,6 @@ otherwise an appropriate error is returned.
 This man page was written by
 .An Jeroen Ruigrok van der Werven
 .Aq asmodai@FreeBSD.org
-based on the manpages for BUS_CREATE_INTR and BUS_CONNECT_INTR written by
+based on the man pages for BUS_CREATE_INTR and BUS_CONNECT_INTR written by
 .An Doug Rabson
 .Aq dfr@FreeBSD.org .
diff --git a/share/man/man9/DEVICE_IDENTIFY.9 b/share/man/man9/DEVICE_IDENTIFY.9
index d2b8b71..f08bfce 100644
--- a/share/man/man9/DEVICE_IDENTIFY.9
+++ b/share/man/man9/DEVICE_IDENTIFY.9
@@ -42,7 +42,7 @@
 .Sh DESCRIPTION
 The identify function for a device is only needed for devices on busses
 that cannot identify their childs independently, e.g. the ISA bus.
-It is used to recognize the device (usually done by accessing non-ambigous
+It is used to recognize the device (usually done by accessing non-ambiguous
 registers in the hardware) and to tell the kernel about it and thus
 creating a new device instance.
 .Pp
diff --git a/share/man/man9/DEVICE_PROBE.9 b/share/man/man9/DEVICE_PROBE.9
index 64c5a2d..32304f1 100644
--- a/share/man/man9/DEVICE_PROBE.9
+++ b/share/man/man9/DEVICE_PROBE.9
@@ -50,7 +50,7 @@ For
 cases where more than one driver matches a device, a priority value can
 be returned.  In this case, success codes are values less than or equal
 to zero with the highest value representing the best match.  Failure
-codes are represented by positive values and the regular unix error
+codes are represented by positive values and the regular Unix error
 codes should be used for the purpose.
 .Pp
 If a driver returns a success code which is less than zero, it must
diff --git a/share/man/man9/VFS_VGET.9 b/share/man/man9/VFS_VGET.9
index b9af8b7..1fbe48e 100644
--- a/share/man/man9/VFS_VGET.9
+++ b/share/man/man9/VFS_VGET.9
@@ -53,7 +53,7 @@ The inode representing the file.
 Return parameter for the vnode.
 .El
 .Pp
-This is an optional filesystem entrypoint for filesystems which have a
+This is an optional filesystem entry-point for filesystems which have a
 unique id number for every file in the filesystem.  It is used
 internally by the UFS filesystem and also by the NFSv3 server to
 implement the
diff --git a/share/man/man9/VOP_ATTRIB.9 b/share/man/man9/VOP_ATTRIB.9
index 1671e08..5a7c334 100644
--- a/share/man/man9/VOP_ATTRIB.9
+++ b/share/man/man9/VOP_ATTRIB.9
@@ -147,7 +147,7 @@ The file is immutable
 .It Bq Er EACCES
 Permission denied
 .It Bq Er EROFS
-The filesystem is readonly
+The filesystem is read-only
 .El
 .Sh SEE ALSO
 .Xr vnode 9 ,
diff --git a/share/man/man9/accf_http.9 b/share/man/man9/accf_http.9
index aac2919..865b64b 100644
--- a/share/man/man9/accf_http.9
+++ b/share/man/man9/accf_http.9
@@ -58,7 +58,7 @@ before performing the initial parsing of the request.
 This effectively reduces the amount of required CPU utilization
 to handle incoming requests be keeping active
 processes in preforking servers such as Apache low
-and reducing the size of the filedescriptor set that needs
+and reducing the size of the file descriptor set that needs
 to be managed by interfaces such as
 .Fn select ,
 .Fn poll
diff --git a/share/man/man9/atomic.9 b/share/man/man9/atomic.9
index 54be4b9..a07388b 100644
--- a/share/man/man9/atomic.9
+++ b/share/man/man9/atomic.9
@@ -279,7 +279,7 @@ and
 .Fn atomic_subtract
 operations were first introduced in
 .Fx 3.0 .
-This first set only suppored the types char, short, int, and long.
+This first set only supported the types char, short, int, and long.
 The
 .Fn atomic_cmpset ,
 .Fn atomic_load ,
diff --git a/share/man/man9/buf.9 b/share/man/man9/buf.9
index c68f7f9..9d8b643 100644
--- a/share/man/man9/buf.9
+++ b/share/man/man9/buf.9
@@ -80,11 +80,11 @@ they are no longer needed but often keeps the 'struct buf' structure
 instantiated and even bp->b_pages array instantiated despite having unmapped
 them from KVM.  If a page making up a VM buffer is about to undergo I/O, the
 system typically unmaps it from KVM and replaces the page in the b_pages[]
-array with a placemarker called bogus_page.  The placemarker forces any kernel
+array with a place-marker called bogus_page.  The place-marker forces any kernel
 subsystems referencing the associated struct buf to re-lookup the associated
-page.  I believe the placemarker hack is used to allow sophisticated devices
+page.  I believe the place-marker hack is used to allow sophisticated devices
 such as filesystem devices to remap underlying pages in order to deal with,
-for example, remapping a file fragment into a file block.
+for example, re-mapping a file fragment into a file block.
 .Pp
 VM buffers are used to track I/O operations within the kernel.  Unfortunately,
 the I/O implementation is also somewhat of a hack because the kernel wants
@@ -94,7 +94,7 @@ can create confusion within filesystem devices that use delayed-writes because
 you wind up with pages marked clean that are actually still dirty.  If not
 treated carefully, these pages could be thrown away!  Indeed, a number of
 serious bugs related to this hack were not fixed until the 2.2.8/3.0 release.
-The kernel uses an instantiated VM buffer (i.e. struct buf) to placemark pages
+The kernel uses an instantiated VM buffer (i.e. struct buf) to place-mark pages
 in this special state.  The buffer is typically flagged B_DELWRI.  When a
 device no longer needs a buffer it typically flags it as B_RELBUF.  Due to
 the underlying pages being marked clean, the B_DELWRI|B_RELBUF combination must
diff --git a/share/man/man9/critical_enter.9 b/share/man/man9/critical_enter.9
index 673be96..5abc0e7 100644
--- a/share/man/man9/critical_enter.9
+++ b/share/man/man9/critical_enter.9
@@ -45,7 +45,7 @@
 .Ft void
 .Fn critical_exit "void"
 .Sh DESCRIPTION
-These functions are used to prevent preemption in a critcal region of code.
+These functions are used to prevent preemption in a critical region of code.
 All that is guaranteed is that the thread currently executing on a CPU will
 not be preempted.
 Specifically, a thread in a critical region will not migrate to another
diff --git a/share/man/man9/device.9 b/share/man/man9/device.9
index 3c40756..632bca3 100644
--- a/share/man/man9/device.9
+++ b/share/man/man9/device.9
@@ -43,7 +43,7 @@ into, disk drives attached to the expansion card etc.
 The system defines one device,
 .Dv root_bus
 and all other devices are created dynamically during
-autoconfiguration.  Normally devices representing toplevel busses in
+autoconfiguration.  Normally devices representing top-level busses in
 the system (ISA, PCI etc.) will be attached directly to
 .Dv root_bus
 and other devices will be added as children of their relevant bus.
diff --git a/share/man/man9/device_enable.9 b/share/man/man9/device_enable.9
index 515d688..a2b4070 100644
--- a/share/man/man9/device_enable.9
+++ b/share/man/man9/device_enable.9
@@ -51,7 +51,7 @@ enabled by default when it is created but may be disabled (for
 instance to prevent a destructive or time consuming probe attempt).
 To disable a device, call
 .Xr device_disable 9 ,
-to reenable it, call
+to re-enable it, call
 .Xr device_enable 9
 and to test to see if a device is enabled, call
 .Xr device_is_enabled 9 .
diff --git a/share/man/man9/device_quiet.9 b/share/man/man9/device_quiet.9
index 0a3bdc0..c975085 100644
--- a/share/man/man9/device_quiet.9
+++ b/share/man/man9/device_quiet.9
@@ -51,7 +51,7 @@ verbose by default when it is created but may be quieted to prevent
 the device identification string to be printed during probe.
 To quiet a device, call
 .Xr device_quiet 9 ,
-to reenable to probe message (to make the message appear again, for
+to re-enable to probe message (to make the message appear again, for
 example after a
 .Xr device_detach 9 )
 call
diff --git a/share/man/man9/devstat.9 b/share/man/man9/devstat.9
index a5d5b20..ea52d0a 100644
--- a/share/man/man9/devstat.9
+++ b/share/man/man9/devstat.9
@@ -103,7 +103,7 @@ below for details.
 .It device_type
 The device type.  This is broken into three sections:  base device type
 (e.g. direct access, CDROM, sequential access), interface type (IDE, SCSI
-or other) and a passthrough flag to indicate pasthrough devices.  See below
+or other) and a pass-through flag to indicate pas-through devices.  See below
 for a complete list of types.
 .It priority
 The device priority.  The priority is used to determine how devices are
@@ -246,7 +246,7 @@ to userland programs that decipher the statistics.
 .It device_type
 This is the device type.  It consists of three parts:  the device type
 (e.g. direct access, CDROM, sequential access, etc.), the interface (IDE,
-SCSI or other) and whether or not the device in question is a passthrough
+SCSI or other) and whether or not the device in question is a pass-through
 driver.  See below for a complete list of device types.
 .It priority
 This is the priority.  This is the first parameter used to determine where
@@ -256,9 +256,9 @@ list.  The second parameter is attach order.  See below for a list of
 available priorities.
 .El
 .Pp
-Each device is given a device type.  Passthrough devices have the same
+Each device is given a device type.  Pass-through devices have the same
 underlying device type and interface as the device they provide an
-interface for, but they also have the passthrough flag set.  The base
+interface for, but they also have the pass-through flag set.  The base
 device types are identical to the
 .Tn SCSI
 device type numbers, so with
@@ -266,7 +266,7 @@ device type numbers, so with
 peripherals, the device type returned from an inquiry is usually ORed with
 the
 .Tn SCSI
-interface type and the passthrough flag if appropriate.  The device type
+interface type and the pass-through flag if appropriate.  The device type
 flags are as follows:
 .Bd -literal -offset indent
 typedef enum {
diff --git a/share/man/man9/ifnet.9 b/share/man/man9/ifnet.9
index 8550bcb..2a44bf3 100644
--- a/share/man/man9/ifnet.9
+++ b/share/man/man9/ifnet.9
@@ -281,7 +281,7 @@ Flags describing operational parameters of this interface (see below).
 Flags describing the capabilities the interface supports (see below).
 .It Li "if_capenable"
 .Pq Li "int"
-Flags describing the enabled capabilties of the interface (see below).
+Flags describing the enabled capabilities of the interface (see below).
 .\" .It Li "if_ipending"
 .\" Interrupt-pending bits for polled operation:
 .\" .Dv IFI_XMIT
diff --git a/share/man/man9/ithread.9 b/share/man/man9/ithread.9
index f69d853..3f7e559 100644
--- a/share/man/man9/ithread.9
+++ b/share/man/man9/ithread.9
@@ -111,7 +111,7 @@ The functions receive the vector corresponding to the thread's interrupt
 source as their only argument.
 The remaining arguments form a
 .Xr printf 9
-agument list that is used to build the base name of the new ithread.
+argument list that is used to build the base name of the new ithread.
 The full name of an interrupt thread is formed by concatenating the base
 name of an interrupt thread with the names of all of its interrupt handlers.
 .Pp
diff --git a/share/man/man9/kthread.9 b/share/man/man9/kthread.9
index 873edda..6091404 100644
--- a/share/man/man9/kthread.9
+++ b/share/man/man9/kthread.9
@@ -269,7 +269,7 @@ The
 .Fn kthread_suspend ,
 and
 .Fn kthread_suspend_check
-functions were introducted in
+functions were introduced in
 .Fx 4.0 .
 Prior to
 .Fx 5.0 ,
diff --git a/share/man/man9/make_dev.9 b/share/man/man9/make_dev.9
index 74e6494..95215cd 100644
--- a/share/man/man9/make_dev.9
+++ b/share/man/man9/make_dev.9
@@ -120,7 +120,7 @@ of the parent device will also result in the destruction of the
 child device(s),
 if any exist.
 A device may simultaneously be a parent and a child,
-so it is possible to build a complete hierachy.
+so it is possible to build a complete hierarchy.
 .Sh HISTORY
 The
 .Fn make_dev
diff --git a/share/man/man9/mbchain.9 b/share/man/man9/mbchain.9
index f9aa41d..c7cdf3a 100644
--- a/share/man/man9/mbchain.9
+++ b/share/man/man9/mbchain.9
@@ -112,7 +112,7 @@ total number of bytes placed in the mbuf chain
 .Vt ( "mb_copy_t *" )
 user-defined function to perform a copy into mbuf;
 useful if any unusual
-data conversion is necessesary
+data conversion is necessary
 .It Va mb_udata
 .Vt ( "void *" )
 user-supplied data which can be used in the
diff --git a/share/man/man9/mutex.9 b/share/man/man9/mutex.9
index 84257c3..f87b8c5 100644
--- a/share/man/man9/mutex.9
+++ b/share/man/man9/mutex.9
@@ -352,12 +352,12 @@ pointed to by the first argument.
 .It Dv MA_RECURSED
 Assert that the current thread has recursed on the mutex
 pointed to by the first argument.
-This assertion is only valid in conjuction with
+This assertion is only valid in conjunction with
 .Dv MA_OWNED .
 .It Dv MA_NOTRECURSED
 Assert that the current thread has not recursed on the mutex
 pointed to by the first argument.
-This assertion is only valid in conjuction with
+This assertion is only valid in conjunction with
 .Dv MA_OWNED .
 .El
 .Ss The Default Mutex Type
diff --git a/share/man/man9/pfil.9 b/share/man/man9/pfil.9
index 9f301b0..38356165 100644
--- a/share/man/man9/pfil.9
+++ b/share/man/man9/pfil.9
@@ -92,7 +92,7 @@ packet.  The
 is the direction; 0 for incoming packets and 1 for outgoing packets.  if the function
 returns non-zero, this signals an error and no further processing of this packet is
 performed.  The function should set errno to indicate the nature of the error.
-It is the hook's responsibiliy to free the chain if the packet is being dropped.
+It is the hook's responsibility to free the chain if the packet is being dropped.
 .Pp
 The
 .Nm
diff --git a/share/man/man9/sysctl_add_oid.9 b/share/man/man9/sysctl_add_oid.9
index 0987521..7cdd49e 100644
--- a/share/man/man9/sysctl_add_oid.9
+++ b/share/man/man9/sysctl_add_oid.9
@@ -215,7 +215,7 @@ this pointer can be obtained with the
 .Fn SYSCTL_STATIC_CHILDREN
 macro, where the
 .Fa OID_NAME
-argumwent is name of the parent oid of type
+argument is name of the parent oid of type
 .Dv CTLTYPE_NODE
 (i.e. the name displayed by
 .Xr sysctl 8 ,
@@ -232,7 +232,7 @@ argument points to the parent oid of type
 The
 .Fn sysctl_add_oid
 function creates raw oids of any type.
-If the oid is successfuly created,
+If the oid is successfully created,
 the function returns a pointer to it;
 otherwise it returns
 .Dv NULL .
@@ -278,7 +278,7 @@ Oids created dynamically always have the
 flag set.
 Access flags specify whether this oid is read-only or read-write,
 and whether it may be modified by all users
-or by the supseruser only.
+or by the superuser only.
 .It Fa arg1
 A pointer to any data that the oid should reference, or
 .Dv NULL .
diff --git a/share/man/man9/sysctl_ctx_init.9 b/share/man/man9/sysctl_ctx_init.9
index 3e223ad..fffecb1 100644
--- a/share/man/man9/sysctl_ctx_init.9
+++ b/share/man/man9/sysctl_ctx_init.9
@@ -110,7 +110,7 @@ Newly created oids are always inserted in the front of the list.
 The
 .Fn sysctl_ctx_free
 function removes the context and associated oids it manages.
-If the function completes successfuly,
+If the function completes successfully,
 all managed oids have been unregistered
 (removed from the tree)
 and freed,
@@ -171,7 +171,7 @@ The
 .Fn sysctl_ctx_entry_find
 function searches for a given
 .Fa oidp
-witin a context list,
+within a context list,
 either returning a pointer to the
 .Fa struct sysctl_ctx_entry
 found,
diff --git a/share/man/man9/vaccess.9 b/share/man/man9/vaccess.9
index 4e5291b..fd05071 100644
--- a/share/man/man9/vaccess.9
+++ b/share/man/man9/vaccess.9
@@ -75,7 +75,7 @@ privilege information, or it may point to an integer that will be set to
 .Pp
 This call is intended to support implementations of
 .Xr VOP_ACCESS 9 ,
-which will use their own accessor methods to retrieve the vnode properties,
+which will use their own access methods to retrieve the vnode properties,
 and then invoke
 .Fn vaccess
 in order to perform the actual check.
diff --git a/share/man/man9/vaccess_acl_posix1e.9 b/share/man/man9/vaccess_acl_posix1e.9
index 62765d6..3284ec6 100644
--- a/share/man/man9/vaccess_acl_posix1e.9
+++ b/share/man/man9/vaccess_acl_posix1e.9
@@ -75,7 +75,7 @@ privilege information, or it may point to an integer that will be set to
 .Pp
 This call is intended to support implementations of
 .Xr VOP_ACCESS 9 ,
-which will use their own accessor methods to retrieve the vnode properties,
+which will use their own access methods to retrieve the vnode properties,
 and then invoke
 .Fn vaccess_acl_posix1e
 in order to perform the actual check.
diff --git a/share/man/man9/vfs_timestamp.9 b/share/man/man9/vfs_timestamp.9
index d4b41d7..7675d98 100644
--- a/share/man/man9/vfs_timestamp.9
+++ b/share/man/man9/vfs_timestamp.9
@@ -54,7 +54,7 @@ seconds only; nanoseconds are zeroed.
 .It 1
 seconds and nanoseconds, accurate within 1/HZ.
 .It 2
-seconds and nanoseconds, trucated to microseconds.
+seconds and nanoseconds, truncated to microseconds.
 .It \(>=3
 seconds and nanoseconds, maximum precision.
 .El
diff --git a/share/man/man9/vfs_unbusy.9 b/share/man/man9/vfs_unbusy.9
index b1a4582..8de15ba 100644
--- a/share/man/man9/vfs_unbusy.9
+++ b/share/man/man9/vfs_unbusy.9
@@ -40,7 +40,7 @@
 .Sh DESCRIPTION
 The
 .Fn vfs_unbusy
-function unbusies a mount point by unlocking
+function un-busies a mount point by unlocking
 .Fa mp->mnt_lock .
 The lock is typically acquired by calling
 .Xr vfs_busy 9