Fix a bunch of typos and spelling mistakes.

3 files changed, 4 insertions, 4 deletions

diff --git a/share/man/man9/VOP_VPTOCNP.9 b/share/man/man9/VOP_VPTOCNP.9
index 7858215..794d6e5 100644
--- a/share/man/man9/VOP_VPTOCNP.9
+++ b/share/man/man9/VOP_VPTOCNP.9
@@ -50,7 +50,7 @@ The vnode to translate.
 The vnode of the parent directory of
 .Fa vp .
 .It Fa buf
-The buffer into which to preprend the component name.
+The buffer into which to prepend the component name.
 .It Fa buflen
 The remaining size of the buffer.
 .El
diff --git a/share/man/man9/locking.9 b/share/man/man9/locking.9
index 8457e25..005f476 100644
--- a/share/man/man9/locking.9
+++ b/share/man/man9/locking.9
@@ -53,12 +53,12 @@ the two is that spin mutexes never sleep - instead, they spin, waiting
 for the thread holding the lock, which runs on another CPU, to release it.
 Differently from ordinary mutex, spin mutexes disable interrupts when acquired.
 Since disabling interrupts is expensive, they are also generally slower.
-Spin mutexes should be used only when neccessary, e.g. to protect data shared
+Spin mutexes should be used only when necessary, e.g. to protect data shared
 with interrupt filter code (see
 .Xr bus_setup_intr 9
 for details).
 .Ss Pool mutexes
-With most synchronisaton primitives, such as mutexes, programmer must
+With most synchronization primitives, such as mutexes, programmer must
 provide a piece of allocated memory to hold the primitive.
 For example, a mutex may be embedded inside the structure it protects.
 Pool mutex is a variant of mutex without this requirement - to lock or unlock
diff --git a/share/man/man9/netisr.9 b/share/man/man9/netisr.9
index 37fd367..c6d5ead 100644
--- a/share/man/man9/netisr.9
+++ b/share/man/man9/netisr.9
@@ -173,7 +173,7 @@ Both accept a protocol number and
 .Vt mbuf
 argument, but while
 .Fn netisr_queue
-will always execute the protocol handler asynchonously in a deferred
+will always execute the protocol handler asynchronously in a deferred
 context,
 .Fn netisr_dispatch
 will optionally direct dispatch if permitted by global and per-protocol