Index: head/lib/libc/sys/kqueue.2
===================================================================
--- head/lib/libc/sys/kqueue.2
+++ head/lib/libc/sys/kqueue.2
@@ -190,7 +190,7 @@
 .Fa ext[2]
 and
 .Fa ext[3]
-members are always passed throught the kernel as-is,
+members are always passed through the kernel as-is,
 making additional context available to application.
 .El
 .Pp
Index: head/lib/libc/sys/sendfile.2
===================================================================
--- head/lib/libc/sys/sendfile.2
+++ head/lib/libc/sys/sendfile.2
@@ -190,7 +190,7 @@
 A macro
 .Fn SF_FLAGS
 is provided to combine readahead amount and flags.
-Example shows specifing readahead of 16 pages and
+An example showing specifying readahead of 16 pages and
 .Dv SF_NOCACHE
 flag:
 .Pp
Index: head/lib/libopenbsd/imsg_init.3
===================================================================
--- head/lib/libopenbsd/imsg_init.3
+++ head/lib/libopenbsd/imsg_init.3
@@ -347,7 +347,7 @@
 returns a pointer to the buffer; on failure it returns NULL.
 .Pp
 .Fn ibuf_dynamic
-allocates a resizeable buffer of initial length
+allocates a resizable buffer of initial length
 .Fa len
 and maximum size
 .Fa max .
Index: head/sbin/ipfw/ipfw.8
===================================================================
--- head/sbin/ipfw/ipfw.8
+++ head/sbin/ipfw/ipfw.8
@@ -3020,7 +3020,7 @@
 Stateful NAT64 translation allows IPv6-only clients to contact IPv4 servers
 using unicast TCP, UDP or ICMP protocols.
 One or more IPv4 addresses assigned to a stateful NAT64 translator are shared
-among serveral IPv6-only clients.
+among several IPv6-only clients.
 When stateful NAT64 is used in conjunction with DNS64, no changes are usually
 required in the IPv6 client or the IPv4 server.
 The kernel module
Index: head/usr.sbin/ntp/doc/ntp.conf.5
===================================================================
--- head/usr.sbin/ntp/doc/ntp.conf.5
+++ head/usr.sbin/ntp/doc/ntp.conf.5
@@ -2550,7 +2550,7 @@
 as it allows for quick recovery if a server key has changed,
 a properly forged and appropriately delivered crypto\-NAK packet
 can be used in a DoS attack.
-If you have active noticable problems with this type of DoS attack
+If you have active noticeable problems with this type of DoS attack
 then you should consider
 disabling this option.
 You can check your
@@ -2598,7 +2598,7 @@
 as it allows for quick recovery if a server key has changed,
 a properly forged and appropriately delivered crypto\-NAK packet
 can be used in a DoS attack.
-If you have active noticable problems with this type of DoS attack
+If you have active noticeable problems with this type of DoS attack
 then you should consider
 disabling this option.
 You can check your
@@ -2618,7 +2618,7 @@
 as it allows for quick recovery,
 if this type of packet is carefully forged and sent
 during an appropriate window it can be used for a DoS attack.
-If you have active noticable problems with this type of DoS attack
+If you have active noticeable problems with this type of DoS attack
 then you should consider
 disabling this option.
 You can check your