Fix numerous spelling errrors.

These were found with the help of "aspell".

Additionally, while reviewing the output from the spell checker,
several content errors were noticed and fixed.

66 files changed, 109 insertions, 110 deletions

diff --git a/docs/man/libnng.3.adoc b/docs/man/libnng.3.adoc
index 95b270a9..21a34a6a 100644
--- a/docs/man/libnng.3.adoc
+++ b/docs/man/libnng.3.adoc
@@ -55,7 +55,7 @@ The following functions operate on sockets.
 === Connection Management
 
 The following functions are used with either listeners, or dialers.
-Listeners accept incoming connection requets, and dialers make them.
+Listeners accept incoming connection requests, and dialers make them.
 
 |===
 |<<nng_dial.3#,nng_dial()>>|create and start dialer
diff --git a/docs/man/nn_allocmsg.3compat.adoc b/docs/man/nn_allocmsg.3compat.adoc
index 50e0d9cf..9ceddb2a 100644
--- a/docs/man/nn_allocmsg.3compat.adoc
+++ b/docs/man/nn_allocmsg.3compat.adoc
@@ -27,7 +27,7 @@ void *nn_allocmsg(size_t size, int type);
 The `nn_allocmsg()` allocates a message structure of size _size_, and is
 primarily used to support zero-copy send operations, making use of the
 `NNG_MSG` special size indicator.
-The value returned is a pointer ot the start of the message payload buffer.
+The value returned is a pointer to the start of the message payload buffer.
 
 The value of _size_ must be positive, and small enough to hold reasonable
 message data plus book-keeping information.
diff --git a/docs/man/nn_cmsg.3compat.adoc b/docs/man/nn_cmsg.3compat.adoc
index fd541f8e..1b562c4f 100644
--- a/docs/man/nn_cmsg.3compat.adoc
+++ b/docs/man/nn_cmsg.3compat.adoc
@@ -65,7 +65,7 @@ This macro returns the amount of space required for a header, with _len_
 bytes of following data, and any necessary padding.
 
 `size_t NN_CMSG_LEN(size_t __len__)`::
-This macro evalutes to the length of the header (including alignment),
+This macro evaluates to the length of the header (including alignment),
 and the associated data of length _len_, but without any trailing padding
 to align for another header.
 
diff --git a/docs/man/nn_connect.3compat.adoc b/docs/man/nn_connect.3compat.adoc
index a5505347..01f8195a 100644
--- a/docs/man/nn_connect.3compat.adoc
+++ b/docs/man/nn_connect.3compat.adoc
@@ -25,7 +25,7 @@ int nn_connect(int sock, const char *url)
 == DESCRIPTION
 
 The `nn_connect()` function arranges for the socket _sock_ to
-inititate connection to a peer at the address specified by _url_.
+initiate connection to a peer at the address specified by _url_.
 An "`endpoint identifier`" for this socket's association with the _url_ is
 returned to the caller on success.
 This ID can be used with `<<nn_shutdown.3compat#,nn_shutdown()>>` to
diff --git a/docs/man/nn_device.3compat.adoc b/docs/man/nn_device.3compat.adoc
index 0d123911..4ca08819 100644
--- a/docs/man/nn_device.3compat.adoc
+++ b/docs/man/nn_device.3compat.adoc
@@ -44,7 +44,7 @@ one of the sockets is closed or an error occurs.
 
 == ERRORS
 
-[horizonal]
+[horizontal]
 `EBADF`:: One of the two sockets is invalid or not open, or has
 `EINVAL`:: The sockets are not compatible with each other, or not both raw.
 `ENOMEM`:: Insufficient memory is available.
diff --git a/docs/man/nn_getsockopt.3compat.adoc b/docs/man/nn_getsockopt.3compat.adoc
index 75adfb58..7701013a 100644
--- a/docs/man/nn_getsockopt.3compat.adoc
+++ b/docs/man/nn_getsockopt.3compat.adoc
@@ -97,10 +97,10 @@ The default is 100.
 `NN_RECONNECT_IVL_MAX`::
 Maximum reconnect interval in milliseconds.
 Subsequent reconnection attempts after a failed attempt are made at
-exponentially increasing intervals (backoff), but the interval is
+exponentially increasing intervals (back-off), but the interval is
 capped by this value.
 If this value is smaller than `NN_RECONNECT_IVL`, then no exponential
-backoff is performed, and each reconnect interval will be determined
+back-off is performed, and each reconnect interval will be determined
 solely by `NN_RECONNECT_IVL`.
 The default is zero.
 
diff --git a/docs/man/nn_poll.3compat.adoc b/docs/man/nn_poll.3compat.adoc
index 4ca52ff2..5a09b370 100644
--- a/docs/man/nn_poll.3compat.adoc
+++ b/docs/man/nn_poll.3compat.adoc
@@ -45,7 +45,7 @@ the socket, and the `events` field set to a mask that can contain either or both
 of the flags `NN_POLLIN` and `NN_POLLOUT`.
 
 The flag `NN_POLLIN` indicates that a socket is ready for receiving without
-blocking (a message is avaiable on the socket), and the flag `NN_POLLOUT`
+blocking (a message is available on the socket), and the flag `NN_POLLOUT`
 indicates that a socket is ready for sending without blocking.
 
 Upon success, the function returns the number of updates the `revents`
diff --git a/docs/man/nn_recvmsg.3compat.adoc b/docs/man/nn_recvmsg.3compat.adoc
index 7bd2e34a..ae70585d 100644
--- a/docs/man/nn_recvmsg.3compat.adoc
+++ b/docs/man/nn_recvmsg.3compat.adoc
@@ -24,7 +24,7 @@ int nn_recvmsg(int sock, struct nn_msghdr *hdr, int flags);
 
 == DESCRIPTION
 
-The `nn_recvmsg()` function receives a message into the heade described by
+The `nn_recvmsg()` function receives a message into the header described by
 _hdr_ using the socket _sock_.
 
 NOTE: This function is provided for API
@@ -67,7 +67,7 @@ or similar when it is no longer needed.
 
 The values of `msg_control` and `msg_controllen` describe a buffer
 of ancillary data associated with the message.
-This is currenly only useful to obtain the message headers
+This is currently only useful to obtain the message headers
 used with <<nng.7#raw_mode,raw mode>> sockets.
 In all other circumstances these fields should be zero.
 Details about this structure are covered in
diff --git a/docs/man/nn_sendmsg.3compat.adoc b/docs/man/nn_sendmsg.3compat.adoc
index 8a3487c8..67b3ddc8 100644
--- a/docs/man/nn_sendmsg.3compat.adoc
+++ b/docs/man/nn_sendmsg.3compat.adoc
@@ -72,7 +72,7 @@ at its choice.)
 
 The values of `msg_control` and `msg_controllen` describe a buffer
 of ancillary data to send the message.
-This is currenly only useful to provide the message headers
+This is currently only useful to provide the message headers
 used with <<nng.7#raw_mode,raw mode>> sockets.
 In all other circumstances these fields should be zero.
 Details about this structure are covered in
diff --git a/docs/man/nn_setsockopt.3compat.adoc b/docs/man/nn_setsockopt.3compat.adoc
index 8fc5aeeb..cfee6d08 100644
--- a/docs/man/nn_setsockopt.3compat.adoc
+++ b/docs/man/nn_setsockopt.3compat.adoc
@@ -53,7 +53,7 @@ Send buffer size in bytes.
 NOTE: In _nng_ buffers are sized as a count of messages rather than
 bytes, and so an attempt to estimate a conversion based upon a predetermined
 message size of 1kB is made.
-The value supplied is rouned up to the nearest value divisible by 1024, and
+The value supplied is rounded up to the nearest value divisible by 1024, and
 then divided by 1024 to convert to a message count.
 Applications that have unusual message sizes may wish to adjust the value
 used here accordingly.
@@ -92,10 +92,10 @@ The default is 100.
 `NN_RECONNECT_IVL_MAX`::
 Maximum reconnect interval in milliseconds.
 Subsequent reconnection attempts after a failed attempt are made at
-exponentially increasing intervals (backoff), but the interval is
+exponentially increasing intervals (back-off), but the interval is
 capped by this value.
 If this value is smaller than `NN_RECONNECT_IVL`, then no exponential
-backoff is performed, and each reconnect interval will be determined
+back-off is performed, and each reconnect interval will be determined
 solely by `NN_RECONNECT_IVL`.
 The default is zero.
 
diff --git a/docs/man/nng_aio.5.adoc b/docs/man/nng_aio.5.adoc
index e47fefae..db0860e3 100644
--- a/docs/man/nng_aio.5.adoc
+++ b/docs/man/nng_aio.5.adoc
@@ -24,7 +24,7 @@ typedef struct nng_aio nng_aio;
 
 == DESCRIPTION
 
-An `nng_aio`(((aio))) is an opaque structure used in conjuction with
+An `nng_aio`(((aio))) is an opaque structure used in conjunction with
 ((asynchronous I/O)) operations.
 Every asynchronous operation uses one of these structures, each of which
 can only be used with a single operation at a time.
diff --git a/docs/man/nng_aio_result.3.adoc b/docs/man/nng_aio_result.3.adoc
index f6c6f406..f7a2a969 100644
--- a/docs/man/nng_aio_result.3.adoc
+++ b/docs/man/nng_aio_result.3.adoc
@@ -46,7 +46,7 @@ number on failure.
 `NNG_ETIMEDOUT`:: The operation timed out.
 `NNG_ECANCELED`:: The operation was canceled.
 
-Various other return values are possible dependending on the operation.
+Various other return values are possible depending on the operation.
 
 == SEE ALSO
 
diff --git a/docs/man/nng_bus.7.adoc b/docs/man/nng_bus.7.adoc
index eba870c7..aa8ed2ce 100644
--- a/docs/man/nng_bus.7.adoc
+++ b/docs/man/nng_bus.7.adoc
@@ -72,7 +72,7 @@ identified in the header.
 This behavior is intended for use with <<nng_device.3#device,device>>
 configurations consisting of just a single socket.
 Such configurations are useful in the creation of rebroadcasters, and this
-capaibility prevents a message from being routed back to its source.
+capability prevents a message from being routed back to its source.
 If no header is present, then a message is sent to all connected pipes.
 
 When using "`cooked`" _bus_ sockets, no message headers are present.
diff --git a/docs/man/nng_compat.3compat.adoc b/docs/man/nng_compat.3compat.adoc
index 05fe1383..0276663c 100644
--- a/docs/man/nng_compat.3compat.adoc
+++ b/docs/man/nng_compat.3compat.adoc
@@ -38,7 +38,7 @@ nng_compat - compatibility with nanomsg 1.0
 The <<nng.7#,_nng_>> library provides source-level compatibility for
 most _nanomsg_ 1.0 applications.
 
-IMPORTANT: This is intended to faciliate converting ((legacy applications)) to
+IMPORTANT: This is intended to facilitate converting ((legacy applications)) to
 use the _nng_ library.
 New applications should use the newer <<nng.7#,_nng_>> API instead.
 
diff --git a/docs/man/nng_ctx_getopt.3.adoc b/docs/man/nng_ctx_getopt.3.adoc
index 2cdfaee5..6dd190e5 100644
--- a/docs/man/nng_ctx_getopt.3.adoc
+++ b/docs/man/nng_ctx_getopt.3.adoc
@@ -63,10 +63,10 @@ _valszp_.
 
 When the function returns, the actual size of the data copied (or that
 would have been copied if sufficient space were present) is stored at
-the location referened by _valszp_.
+the location referenced by _valszp_.
 If the caller's buffer is not large enough to hold the entire object,
 then the copy is truncated.
-Therefore the caller should check for truncation by verifyng that the
+Therefore the caller should check for truncation by verifying that the
 returned size in _valszp_ does not exceed the original buffer size.
 
 It is acceptable to pass `NULL` for _val_ if the value in _valszp_ is zero.
@@ -74,7 +74,7 @@ This can be used to determine the size of the buffer needed to receive
 the object.
 
 ==== `nng_ctx_getopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The value will be stored at _ivalp_.
 
 ==== `nng_ctx_getopt_int()`
diff --git a/docs/man/nng_ctx_send.3.adoc b/docs/man/nng_ctx_send.3.adoc
index b2b14d35..b7c264ad 100644
--- a/docs/man/nng_ctx_send.3.adoc
+++ b/docs/man/nng_ctx_send.3.adoc
@@ -46,7 +46,7 @@ socket, or in flight over physical media.
 If the operation fails for any reason (including cancellation or timeout),
 then the _aio_ callback will be executed and
 `<<nng_aio_result.3#,nng_aio_result()>>` will return a non-zero error status.
-In this case, the callback has a responsibity to retrieve the message from
+In this case, the callback has a responsibility to retrieve the message from
 the _aio_ with `<<nng_aio_get_msg.3#,nng_aio_get_msg()>>` and dispose of
 it appropriately.
 (This may include retrying the send operation on the same or a different
diff --git a/docs/man/nng_ctx_setopt.3.adoc b/docs/man/nng_ctx_setopt.3.adoc
index 49ac3742..e9becd75 100644
--- a/docs/man/nng_ctx_setopt.3.adoc
+++ b/docs/man/nng_ctx_setopt.3.adoc
@@ -58,7 +58,7 @@ The _val_ pointer addresses the data to copy, and _valsz_ is the
 size of the objected located at _val_.
 
 ==== `nng_ctx_setopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The _bval_ is passed to the option.
 
 ==== `nng_ctx_setopt_int()`
diff --git a/docs/man/nng_device.3.adoc b/docs/man/nng_device.3.adoc
index 807d8e54..fed4ef7c 100644
--- a/docs/man/nng_device.3.adoc
+++ b/docs/man/nng_device.3.adoc
@@ -41,9 +41,9 @@ is closed.
 
 === Reflectors
 
-One of the sockets may be passed an inititalize `-1` (cast to an,
-`<<nng_socket.5#,nng_socket>>` of course).
-If this is the case, then the other socket must be valid, and must be
+One of the sockets passed may be an unopened socket initialized with
+the `NNG_SOCKET_INITIALIZER` special value.
+If this is the case, then the other socket must be valid, and must use
 a protocol that is bidirectional and can peer with itself (such as
 <<nng_pair.7#,_pair_>> or
 <<nng_bus.7#,_bus_>>.)
@@ -73,7 +73,7 @@ header of the output bound message.
 The underlying raw mode protocols supply the necessary header
 adjustments to add or remove routing headers as needed.
 This allows replies to be
-returned to requestors, and responses to be routed back to surveyors.
+returned to requesters, and responses to be routed back to surveyors.
 
 Additionally, some protocols have a maximum ((time-to-live)) to protect
 against forwarding loops and especially amplification loops.
@@ -85,7 +85,7 @@ This is controlled via the `<<nng_options.5#NNG_OPT_MAXTTL,NNG_OPT_MAXTTL>>`
 option.
 
 IMPORTANT: Not all protocols have support for guarding against forwarding loops,
-and even for those that do, forwarding loops can be extremely determintal
+and even for those that do, forwarding loops can be extremely detrimental
 to network performance.
 
 NOTE: Devices (forwarders and reflectors) act in best effort delivery mode only.
@@ -93,7 +93,7 @@ If a message is received from one socket that cannot be accepted by the
 other (due to backpressure or other issues), then the message is discarded.
 
 TIP: Use the request/reply pattern, which includes automatic retries by
-the requestor, if reliable delivery is needed.
+the requester, if reliable delivery is needed.
 
 == RETURN VALUES
 
diff --git a/docs/man/nng_dialer_close.3.adoc b/docs/man/nng_dialer_close.3.adoc
index 7c516bdf..5ec1a5fe 100644
--- a/docs/man/nng_dialer_close.3.adoc
+++ b/docs/man/nng_dialer_close.3.adoc
@@ -25,7 +25,7 @@ int nng_dialer_close(nng_dialer d);
 == DESCRIPTION
 
 The `nng_dialer_close()` function closes the listener _d_.
-This also closes any `<<nng_pipe.5#,nng_pipe>>` ojects that have
+This also closes any `<<nng_pipe.5#,nng_pipe>>` objects that have
 been created by the dialer.
 
 Once this function returns, the dialer _d_ and any of its resources
diff --git a/docs/man/nng_dialer_getopt.3.adoc b/docs/man/nng_dialer_getopt.3.adoc
index f657a530..7d8b03ab 100644
--- a/docs/man/nng_dialer_getopt.3.adoc
+++ b/docs/man/nng_dialer_getopt.3.adoc
@@ -68,7 +68,7 @@ by _valszp_.
 
 When the function returns, the actual size of the data copied (or that
 would have been copied if sufficient space were present) is stored at
-the location referened by _valszp_.
+the location referenced by _valszp_.
 If the caller's buffer is not large
 enough to hold the entire object, then the copy is truncated.
 Therefore the caller should validate that the returned size in _valszp_ does not
@@ -79,7 +79,7 @@ This can be used to determine the size of the buffer needed to receive
 the object.
 
 ==== `nng_dialer_getopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The value will be stored at _bvalp_.
 
 ==== `nng_dialer_getopt_int()`
diff --git a/docs/man/nng_dialer_setopt.3.adoc b/docs/man/nng_dialer_setopt.3.adoc
index 6ac67639..d90ed247 100644
--- a/docs/man/nng_dialer_setopt.3.adoc
+++ b/docs/man/nng_dialer_setopt.3.adoc
@@ -66,7 +66,7 @@ The _val_ pointer addresses the data to copy, and _valsz_ is the
 size of the objected located at _val_.
 
 ==== `nng_dialer_setopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The _bval_ is passed to the option.
 
 ==== `nng_dialer_setopt_int()`
diff --git a/docs/man/nng_duration.5.adoc b/docs/man/nng_duration.5.adoc
index de486419..9d0b075a 100644
--- a/docs/man/nng_duration.5.adoc
+++ b/docs/man/nng_duration.5.adoc
@@ -30,7 +30,7 @@ typedef int32_t nng_duration;
 
 An `nng_duration`(((duration))) is a relative time, measured in
 milliseconds.
-This type is most often used in conjuction with timers and timeouts.
+This type is most often used in conjunction with timers and timeouts.
 
 A couple of special values have been set aside, and carry special meanings.
 
diff --git a/docs/man/nng_getopt.3.adoc b/docs/man/nng_getopt.3.adoc
index 4d6ae868..1117d72b 100644
--- a/docs/man/nng_getopt.3.adoc
+++ b/docs/man/nng_getopt.3.adoc
@@ -65,10 +65,10 @@ _valszp_.
 
 When the function returns, the actual size of the data copied (or that
 would have been copied if sufficient space were present) is stored at
-the location referened by _valszp_.
+the location referenced by _valszp_.
 If the caller's buffer is not large enough to hold the entire object,
 then the copy is truncated.
-Therefore the caller should check for truncation by verifyng that the
+Therefore the caller should check for truncation by verifying that the
 returned size in _valszp_ does not exceed the original buffer size.
 
 It is acceptable to pass `NULL` for _val_ if the value in _valszp_ is zero.
@@ -76,7 +76,7 @@ This can be used to determine the size of the buffer needed to receive
 the object.
 
 ==== `nng_getopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The value will be stored at _ivalp_.
 
 ==== `nng_getopt_int()`
diff --git a/docs/man/nng_http_client_alloc.3http.adoc b/docs/man/nng_http_client_alloc.3http.adoc
index de659549..d1e96514 100644
--- a/docs/man/nng_http_client_alloc.3http.adoc
+++ b/docs/man/nng_http_client_alloc.3http.adoc
@@ -26,7 +26,7 @@ int nng_http_client_alloc(nng_http_client *clientp, const nng_url *url);
 == DESCRIPTION
 
 The `nng_http_client_alloc()` allocates an HTTP client suitable for
-connecting to the server identifyed by _url_ and stores a pointer to
+connecting to the server identified by _url_ and stores a pointer to
 it in the location referenced by _clientp_.
 
 == RETURN VALUES
diff --git a/docs/man/nng_http_conn_read_all.3http.adoc b/docs/man/nng_http_conn_read_all.3http.adoc
index a091edfa..078170fe 100644
--- a/docs/man/nng_http_conn_read_all.3http.adoc
+++ b/docs/man/nng_http_conn_read_all.3http.adoc
@@ -46,7 +46,7 @@ It is still possible for a partial read to complete in the event of an error.
 The actual number of bytes read can be determined with
 `<<nng_aio_count.3#,nng_aio_count()>>`.
 
-TIP: The main purpose for this function is to faciliate reading HTTP
+TIP: The main purpose for this function is to facilitate reading HTTP
 body content, after first determining the length of the body content
 from the relevant HTTP headers (typically `Content-Length`).
 
diff --git a/docs/man/nng_http_conn_write_all.3http.adoc b/docs/man/nng_http_conn_write_all.3http.adoc
index 4c25412f..ea982e54 100644
--- a/docs/man/nng_http_conn_write_all.3http.adoc
+++ b/docs/man/nng_http_conn_write_all.3http.adoc
@@ -46,7 +46,7 @@ It is still possible for a partial write to complete in the event of an error.
 The actual number of bytes written can be determined with
 `<<nng_aio_count.3#,nng_aio_count()>>`.
 
-TIP: The main purpose for this function is to faciliate writing HTTP
+TIP: The main purpose for this function is to facilitate writing HTTP
 body content.
 
 TIP: Usually an HTTP request or response will have been written immediately
@@ -56,7 +56,7 @@ In that case the request or response should have also contained
 an `Content-Length` header, and possibly a `Content-Type` header.
 
 TIP: An easier solution to sending HTTP content data, is to include the
-conten with the request or reply using a function like
+content with the request or reply using a function like
 `<<nng_http_req_copy_data.3http#,nng_http_req_copy_data()>>`.
 In that case, the body data will be written automatically by the
 `<<nng_http_conn_write_req.3http#,http_conn_write_req()>>` or
diff --git a/docs/man/nng_http_conn_write_req.3http.adoc b/docs/man/nng_http_conn_write_req.3http.adoc
index 453f0397..0384e7b1 100644
--- a/docs/man/nng_http_conn_write_req.3http.adoc
+++ b/docs/man/nng_http_conn_write_req.3http.adoc
@@ -37,7 +37,7 @@ including headers, and if present, the request body data.
 This function returns immediately, with no return value.
 Completion of the operation is signaled via the _aio_, and the final result
 may be obtained via `<<nng_aio_result.3#,nng_aio_result()>>`.
-That result willeither be zero or an error code.
+That result will either be zero or an error code.
 
 == RETURN VALUES
 
diff --git a/docs/man/nng_http_handler_alloc.3http.adoc b/docs/man/nng_http_handler_alloc.3http.adoc
index 630871cc..187b91b6 100644
--- a/docs/man/nng_http_handler_alloc.3http.adoc
+++ b/docs/man/nng_http_handler_alloc.3http.adoc
@@ -93,14 +93,14 @@ a handler configured to serve a directory tree.
 The _uri_ is taken as the root, and files are served from the directory
 tree rooted at _path_.
 
-When the client Request-URI resolves to a directory in the filesystem,
+When the client Request-URI resolves to a directory in the file system,
 the handler looks first for a file named `index.html` or `index.htm`.
 If one is found, then that file is returned back to the client.
 If no such index file exists, then an `NNG_HTTP_STATUS_NOT_FOUND` (404) error is
 sent back to the client.
 
 The `Content-Type` will be set automatically based upon the extension
-of the requsted file name.
+of the requested file name.
 If a content type cannot be determined from
 the extension, then `application/octet-stream` is used.
 
@@ -111,7 +111,7 @@ a handler to serve up a single file; it does not traverse directories
 or search for `index.html` or `index.htm` files.
 
 The `Content-Type` will be set automatically based upon the extension
-of the requsted file name.
+of the requested file name.
 If a content type cannot be determined from
 the extension, then `application/octet-stream` is used.
 
diff --git a/docs/man/nng_http_handler_set_host.3http.adoc b/docs/man/nng_http_handler_set_host.3http.adoc
index 9c3acb80..73cf3b93 100644
--- a/docs/man/nng_http_handler_set_host.3http.adoc
+++ b/docs/man/nng_http_handler_set_host.3http.adoc
@@ -34,7 +34,7 @@ hosting.
 
 The value of the _host_ can include a colon and port, and should match
 exactly the value of the `Host` header sent by the client.
-(Canonicaliztion of the host name is performed though.)
+(Canonicalization of the host name is performed though.)
 
 TIP: As the server framework does not support listening on multiple
 ports, the port number can be elided.
diff --git a/docs/man/nng_http_req_get_uri.3http.adoc b/docs/man/nng_http_req_get_uri.3http.adoc
index e7412c5b..22ac1acb 100644
--- a/docs/man/nng_http_req_get_uri.3http.adoc
+++ b/docs/man/nng_http_req_get_uri.3http.adoc
@@ -28,8 +28,8 @@ const char *nng_http_req_get_method(nng_http_req *req);
 The `nng_http_req_get_uri()` returns the URI (path) associated with the HTTP
 the request _req_.
 The value returned includes the path, as well as any query information or
-fragment.  The value will look like a filesystem path
-with those optional components appened, such as `/api/get_info.cgi?name=garrett`.
+fragment.  The value will look like a file system path
+with those optional components appended, such as `/api/get_info.cgi?name=garrett`.
 
 == RETURN VALUES
 
diff --git a/docs/man/nng_http_res_set_reason.3http.adoc b/docs/man/nng_http_res_set_reason.3http.adoc
index 955256f4..804b951b 100644
--- a/docs/man/nng_http_res_set_reason.3http.adoc
+++ b/docs/man/nng_http_res_set_reason.3http.adoc
@@ -33,7 +33,7 @@ phrase is supplied based upon the value of the status code (see
 `<<nng_http_res_set_status.3http#,nng_http_res_set_status()>>`).
 
 TIP: The _reason_ is never parsed automatically, but it can be a hint for humans
-     to help them understand the nature of any erroroneous result.
+     to help them understand the nature of any erroneous result.
 
 A local copy of the _reason_ is made in the response _res_.
 
diff --git a/docs/man/nng_http_server_start.3http.adoc b/docs/man/nng_http_server_start.3http.adoc
index fde77008..c8b7b542 100644
--- a/docs/man/nng_http_server_start.3http.adoc
+++ b/docs/man/nng_http_server_start.3http.adoc
@@ -36,7 +36,7 @@ This function returns 0 on success, and non-zero otherwise.
 == ERRORS
 
 [horizontal]
-`NNG_EADDRINUSE`:: The TCP port is unavaialble.
+`NNG_EADDRINUSE`:: The TCP port is unavailable.
 `NNG_EADDRINVAL`:: The server is configured with an invalid address.
 `NNG_ENOMEM`:: Insufficient free memory exists.
 `NNG_ENOTSUP`:: HTTP not supported.
diff --git a/docs/man/nng_ipc.7.adoc b/docs/man/nng_ipc.7.adoc
index 6a7f3972..9b49c87c 100644
--- a/docs/man/nng_ipc.7.adoc
+++ b/docs/man/nng_ipc.7.adoc
@@ -91,7 +91,7 @@ TIP: The best practice for limiting access is to place the socket in a
 directory writable only by the server, and only readable and searchable
 by clients.
 All mainstream POSIX systems will fail to permit a client to connect
-to a socket located in a diretor for which the client lacks search (execute)
+to a socket located in a directory for which the client lacks search (execute)
 permission.
 
 TIP: Also consider using the `NNG_OPT_IPC_PEER_UID` property from within a
diff --git a/docs/man/nng_listener_getopt.3.adoc b/docs/man/nng_listener_getopt.3.adoc
index 74717e5a..9ffcafa0 100644
--- a/docs/man/nng_listener_getopt.3.adoc
+++ b/docs/man/nng_listener_getopt.3.adoc
@@ -68,7 +68,7 @@ by _valszp_.
 
 When the function returns, the actual size of the data copied (or that
 would have been copied if sufficient space were present) is stored at
-the location referened by _valszp_.
+the location referenced by _valszp_.
 If the caller's buffer is not large
 enough to hold the entire object, then the copy is truncated.  Therefore
 the caller should validate that the returned size in _valszp_ does not
@@ -79,7 +79,7 @@ This can be used to determine the size of the buffer needed to receive
 the object.
 
 ==== `nng_listener_getopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The value will be stored at _bvalp_.
 
 ==== `nng_listener_getopt_int()`
diff --git a/docs/man/nng_listener_setopt.3.adoc b/docs/man/nng_listener_setopt.3.adoc
index 4c151c76..00490e06 100644
--- a/docs/man/nng_listener_setopt.3.adoc
+++ b/docs/man/nng_listener_setopt.3.adoc
@@ -64,7 +64,7 @@ The _val_ pointer addresses the data to copy, and _valsz_ is the
 size of the objected located at _val_.
 
 ==== `nng_listener_setopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The _bval_ is passed to the option.
 
 ==== `nng_listener_setopt_int()`
diff --git a/docs/man/nng_msg.5.adoc b/docs/man/nng_msg.5.adoc
index baf6410f..45b04e03 100644
--- a/docs/man/nng_msg.5.adoc
+++ b/docs/man/nng_msg.5.adoc
@@ -26,7 +26,7 @@ typedef struct nng_msg nng_msg;
 
 An `nng_msg` represents a single ((message)) sent between Scalability Protocols
 peers.
-Messages internally have a ((body)), containining the application supplied
+Messages internally have a ((body)), containing the application supplied
 payload, and a ((header)), containing protocol specific routing and similar
 related information.
 
diff --git a/docs/man/nng_msg_get_pipe.3.adoc b/docs/man/nng_msg_get_pipe.3.adoc
index 357d0ec4..2f9a9c84 100644
--- a/docs/man/nng_msg_get_pipe.3.adoc
+++ b/docs/man/nng_msg_get_pipe.3.adoc
@@ -45,7 +45,7 @@ is useful in this situation.
 This function returns the pipe associated with this message, which will
 be a positive value.
 If the pipe is non-positive, then that indicates that
-no specific pipe is associated with the messsage.
+no specific pipe is associated with the message.
 
 == ERRORS
 
diff --git a/docs/man/nng_msg_insert.3.adoc b/docs/man/nng_msg_insert.3.adoc
index ddc8d46d..911dabbb 100644
--- a/docs/man/nng_msg_insert.3.adoc
+++ b/docs/man/nng_msg_insert.3.adoc
@@ -35,7 +35,7 @@ The second function prepends the value _val32_ in network-byte order
 TIP: This function makes use of pre-allocated "`headroom`" in the message if
 available, so it can often avoid performing any reallocation.
 Applications should use this instead of reallocating and copying message
-content themselves, in order to benefit from this capabilitiy.
+content themselves, in order to benefit from this capability.
 
 == RETURN VALUES
 
diff --git a/docs/man/nng_mtx_unlock.3supp.adoc b/docs/man/nng_mtx_unlock.3supp.adoc
index e0742a55..4f2d219e 100644
--- a/docs/man/nng_mtx_unlock.3supp.adoc
+++ b/docs/man/nng_mtx_unlock.3supp.adoc
@@ -25,7 +25,7 @@ void nng_mtx_unlock(nng_mtx *mtx);
 
 == DESCRIPTION
 
-The `nng_mtx_unlock()` reqlinquishes ownership of the mutex _mtx_ that
+The `nng_mtx_unlock()` relinquishes ownership of the mutex _mtx_ that
 was previously acquired via `<<nng_mtx_lock.3supp#,nng_mtx_lock()>>`.
 
 IMPORTANT: A mutex can _only_ be unlocked by the thread that locked it.
diff --git a/docs/man/nng_options.5.adoc b/docs/man/nng_options.5.adoc
index 6a155953..00a5e011 100644
--- a/docs/man/nng_options.5.adoc
+++ b/docs/man/nng_options.5.adoc
@@ -123,7 +123,7 @@ If this is non-zero, then the time between successive connection attempts
 will start at the value of `NNG_OPT_RECONNMINT`,
 and grow exponentially, until it reaches this value.
 If this value is zero, then no exponential
-backoff between connection attempts is done, and each attempt will wait
+back-off between connection attempts is done, and each attempt will wait
 the time specified by `NNG_OPT_RECONNMINT`.
 This can be set on a socket, but it can also be overridden on an individual
 dialer.
@@ -156,7 +156,7 @@ on the socket.
 When no message is ready for receiving, then this file descriptor will *not*
 be readable.
 
-IMPORTANT: Appplications should never attempt to read or write to the
+IMPORTANT: Applications should never attempt to read or write to the
 returned file descriptor.
 
 TIP: While this option may help applications integrate into existing polling
@@ -228,7 +228,7 @@ message for sending without blocking.
 When the socket is no longer able to accept such messages without blocking,
 the descriptor will *not* be readable.
 
-IMPORTANT: Appplications should never attempt to read or write to the
+IMPORTANT: Applications should never attempt to read or write to the
 returned file descriptor.
 
 TIP: While this option may help applications integrate into existing polling
diff --git a/docs/man/nng_opts_parse.3supp.adoc b/docs/man/nng_opts_parse.3supp.adoc
index c932d514..048f992f 100644
--- a/docs/man/nng_opts_parse.3supp.adoc
+++ b/docs/man/nng_opts_parse.3supp.adoc
@@ -32,7 +32,7 @@ int nng_opts_parse(int argc, const char **argv, const nng_optspec *spec, int *va
 
 == DESCRIPTION
 
-The `nng_opts_parse()` is function is a supplemental funtion intened to
+The `nng_opts_parse()` is function is a supplemental function intended to
 facilitate parsing command line arguments.
 This function exists largely to stand in for `getopt()` from POSIX
 systems, but it is available everywhere that _NNG_ is, and it includes
diff --git a/docs/man/nng_pair.7.adoc b/docs/man/nng_pair.7.adoc
index 7d5fd435..4fefeb61 100644
--- a/docs/man/nng_pair.7.adoc
+++ b/docs/man/nng_pair.7.adoc
@@ -51,7 +51,7 @@ _devices_ (see `<<nng_device.3#,nng_device()>>`) or raw mode sockets
 messages may be discarded.
 Applications that require reliable delivery semantics should consider using
 <<nng_req.7#,_req_>> sockets, or
-implement their own acknowledgement layer on top of _pair_ sockets.
+implement their own acknowledgment layer on top of _pair_ sockets.
 
 In order to avoid head-of-line blocking conditions, _polyamorous_ mode _pair_
 sockets (version 1 only) discard messages if they are unable to deliver them
@@ -83,7 +83,7 @@ peer.
 In ((_polyamorous_ mode)), which is only available with version 1, a socket can
 support many one-to-one connections.
 In this mode, the application must
-choose the remote peer to receive an ougoing message by setting the
+choose the remote peer to receive an outgoing message by setting the
 `<<nng_pipe.5#,nng_pipe>>` to use for the outgoing message with
 the `<<nng_msg_set_pipe.3#,nng_msg_set_pipe()>>` function.
 
@@ -103,7 +103,7 @@ The following protocol-specific options are available.
 ((`NNG_OPT_PAIR1_POLY`))::
 
    (`bool`, version 1 only)  This option enables the use of _polyamorous_ mode.
-   The value is read-write, and takes an integer boolean value.  The default
+   The value is read-write, and takes an integer Boolean value.  The default
    false value (0) indicates that legacy monogamous mode should be used.
 
 `<<nng_options.5#NNG_OPT_MAXTTL,NNG_OPT_MAXTTL>>`::
@@ -116,7 +116,7 @@ Version 0 of the pair protocol has no protocol-specific headers.
 
 Version 1 of the pair protocol uses a single 32-bit unsigned value.  The
 low-order (big-endian) byte of this value contains a "hop" count, and is
-used in conjuction with the
+used in conjunction with the
 `<<nng_options.5#NNG_OPT_MAXTTL,NNG_OPT_MAXTTL>>` option to guard against
 device forwarding loops.
 This value is initialized to 1, and incremented each time the message is
diff --git a/docs/man/nng_pipe_getopt.3.adoc b/docs/man/nng_pipe_getopt.3.adoc
index e4eb5223..5fc3a1ce 100644
--- a/docs/man/nng_pipe_getopt.3.adoc
+++ b/docs/man/nng_pipe_getopt.3.adoc
@@ -46,7 +46,7 @@ the <<nng_pipe.5#,pipe>> _p_.
 The actual options that may be retrieved in this way
 vary, and many are documented in <<nng_options.5#,nng_options(5)>>.
 Additionally some transport-specific options and protocol-specific options are
-documented with the transports andp protocols themselves.
+documented with the transports and protocols themselves.
 
 NOTE: All "`options`" on a pipe are read-only values, and intended to
 facilitate understanding the identity of an associated peer.
@@ -72,10 +72,10 @@ buffer shall be stored at the location referenced by _valszp_.
 
 When the function returns, the actual size of the data copied (or that
 would have been copied if sufficient space were present) is stored at
-the location referened by _valszp_.
+the location referenced by _valszp_.
 If the caller's buffer is not large enough to hold the entire object,
 then the copy is truncated.
-Therefore the caller should check for trncation by verifying that the
+Therefore the caller should check for truncation by verifying that the
 size returned in _valszp_ does not exceed the original buffer size.
 
 It is acceptable to pass `NULL` for _val_ if the value in _valszp_ is zero.
@@ -86,14 +86,13 @@ TIP: Generally, it will be easier to use one of the typed forms instead.
 
 ==== `nng_pipe_getopt_bool()`
 
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The value will be stored at _bvalp_.
 
 ==== `nng_pipe_getopt_int()`
 
-This function is for options which take an integer (`int`) or boolean (`bool`).
-The value will be stored at _ivalp_.  For booleans the value will be eiher 0
-(`false`) or 1 (`true`).
+This function is for options which take an integer (`int`).
+The value will be stored at _ivalp_.
 
 ==== `nng_pipe_getopt_ms()`
 
@@ -126,7 +125,7 @@ and consequently must be freed by the caller using
 
 ==== `nng_pipe_getopt_uint64()`
 
-This function is used to retriev a 64-bit unsigned value into the value
+This function is used to retrieve a 64-bit unsigned value into the value
 referenced by _u64p_.
 This is typically used for options
 related to identifiers, network numbers, and similar.
diff --git a/docs/man/nng_pipe_listener.3.adoc b/docs/man/nng_pipe_listener.3.adoc
index 11246cab..6742867d 100644
--- a/docs/man/nng_pipe_listener.3.adoc
+++ b/docs/man/nng_pipe_listener.3.adoc
@@ -24,7 +24,7 @@ nng_listener nng_pipe_listener(nng_pipe p);
 
 == DESCRIPTION
 
-The `nng_pipe_listener()` function returns the `<<nng_listener.5#,nng_lisener>>`
+The `nng_pipe_listener()` function returns the `<<nng_listener.5#,nng_listener>>`
 that created the pipe _p_.
 If the pipe was not created by a listener, then the returned value will
 have an identifier (`<<nng_listener_id.3#,nng_listener_id()>>`) of `-1`.
diff --git a/docs/man/nng_push.7.adoc b/docs/man/nng_push.7.adoc
index bff41e89..f227cc2f 100644
--- a/docs/man/nng_push.7.adoc
+++ b/docs/man/nng_push.7.adoc
@@ -45,7 +45,7 @@ wait until one is available, or the operation times out.
 
 NOTE: Although the pipeline protocol honors flow control, and attempts
 to avoid dropping messages, no guarantee of delivery is made.
-Furthermore, as there is no capability for message acknowledgement,
+Furthermore, as there is no capability for message acknowledgment,
 applications that need reliable delivery are encouraged to consider the
 <<nng_req.7#,_req_>> protocol instead.
 
diff --git a/docs/man/nng_req.7.adoc b/docs/man/nng_req.7.adoc
index 42abe843..4b8e75d3 100644
--- a/docs/man/nng_req.7.adoc
+++ b/docs/man/nng_req.7.adoc
@@ -114,7 +114,7 @@ This form uses a "`stack`" of 32-bit big-endian identifiers.
 There *must* be at least one identifier, the __request ID__, which will be the
 last element in the array, and *must* have the most significant bit set.
 
-There may be additional __peer ID__s preceeding the request ID.
+There may be additional __peer ID__s preceding the request ID.
 These will be distinguishable from the request ID by having their most
 significant bit clear.
 
@@ -138,7 +138,7 @@ that the request contained.
 A forwarding node can "`pop`" the peer ID it originally pushed on the
 message, stripping it from the front of the message as it does so.
 
-When the reply finally arrives back at the initiating requestor, it
+When the reply finally arrives back at the initiating requester, it
 should have only a single element in the message, which will be the
 request ID it originally used for the request.
 
diff --git a/docs/man/nng_send.3.adoc b/docs/man/nng_send.3.adoc
index 20d3ae4d..03367893 100644
--- a/docs/man/nng_send.3.adoc
+++ b/docs/man/nng_send.3.adoc
@@ -63,14 +63,14 @@ increasing performance.
 NOTE: Regardless of the presence or absence of `NNG_FLAG_NONBLOCK`, there may
 be queues between the sender and the receiver.
 Furthermore, there is no guarantee that the message has actually been delivered.
-Finally, with some protocols, the semantic is implictly `NNG_FLAG_NONBLOCK`,
+Finally, with some protocols, the semantic is implicitly `NNG_FLAG_NONBLOCK`,
 such as with <<nng_pub.7#,_pub_>> sockets, which are best-effort delivery only.
 
 IMPORTANT: When using `NNG_FLAG_ALLOC`, it is important that the value of _size_
 match the actual allocated size of the data.
 Using an incorrect size results
 in unspecified behavior, which may include heap corruption, program crashes,
-or transdimensional mutation of the program's author.
+or trans-dimensional mutation of the program's author.
 
 == RETURN VALUES
 
diff --git a/docs/man/nng_send_aio.3.adoc b/docs/man/nng_send_aio.3.adoc
index c82d1a79..ae6b6b7d 100644
--- a/docs/man/nng_send_aio.3.adoc
+++ b/docs/man/nng_send_aio.3.adoc
@@ -47,7 +47,7 @@ If the operation fails for any reason (including cancellation or timeout),
 then the _aio_ callback will be executed and
 `<<nng_aio_result.3#,nng_aio_result()>>`
 will return a non-zero error status.
-In this case, the callback has a responsibity to retrieve the message from
+In this case, the callback has a responsibility to retrieve the message from
 the _aio_ with
 `<<nng_aio_get_msg.3#,nng_aio_get_msg()>>` and dispose of it appropriately.
 (This may include retrying the send operation on the same or a different
diff --git a/docs/man/nng_sendmsg.3.adoc b/docs/man/nng_sendmsg.3.adoc
index f3f2992c..68351647 100644
--- a/docs/man/nng_sendmsg.3.adoc
+++ b/docs/man/nng_sendmsg.3.adoc
@@ -63,7 +63,7 @@ The _flags_ may contain the following value:
 NOTE: Regardless of the presence or absence of `NNG_FLAG_NONBLOCK`, there may
 be queues between the sender and the receiver.
 Furthermore, there is no guarantee that the message has actually been delivered.
-Finally, with some protocols, the semantic is implictly `NNG_FLAG_NONBLOCK`,
+Finally, with some protocols, the semantic is implicitly `NNG_FLAG_NONBLOCK`,
 such as with <<nng_pub.7#,_pub_>> sockets, which are best-effort delivery only.
 
 == RETURN VALUES
diff --git a/docs/man/nng_setopt.3.adoc b/docs/man/nng_setopt.3.adoc
index 40bb820a..7bb92271 100644
--- a/docs/man/nng_setopt.3.adoc
+++ b/docs/man/nng_setopt.3.adoc
@@ -61,7 +61,7 @@ The _val_ pointer addresses the data to copy, and _valsz_ is the
 size of the objected located at _val_.
 
 ==== `nng_setopt_bool()`
-This function is for options which take a boolean (`bool`).
+This function is for options which take a Boolean (`bool`).
 The _bval_ is passed to the option.
 
 ==== `nng_setopt_int()`
diff --git a/docs/man/nng_sockaddr.5.adoc b/docs/man/nng_sockaddr.5.adoc
index 7d595c22..fea434bb 100644
--- a/docs/man/nng_sockaddr.5.adoc
+++ b/docs/man/nng_sockaddr.5.adoc
@@ -47,14 +47,14 @@ addresses, IPC paths, and so forth.
 
 ****
 The name `sockaddr` is based on it's similarity with POSIX `struct sockaddr`,
-but in the _nng_ library, these addreses are more closely affiliated with
+but in the _nng_ library, these addresses are more closely affiliated with
 instances of `<<nng_pipe.5#,nng_pipe>>`
 than of `<<nng_socket.5#,nng_socket>>`.
 The naming confusion is unfortunate.
 ****
 
 This structure is actually a union, with different members for different
-types of addreses.
+types of addresses.
 
 Every member structure has as its first element a `uint16_t` field
 containing the "`((address family))`".
diff --git a/docs/man/nng_sockaddr_in.5.adoc b/docs/man/nng_sockaddr_in.5.adoc
index d47f77d4..0bdf5006 100644
--- a/docs/man/nng_sockaddr_in.5.adoc
+++ b/docs/man/nng_sockaddr_in.5.adoc
@@ -51,16 +51,16 @@ The following structure members are present:
     A zero value here is used when no specific port number is indicated.
 
 `sa_addr`::
-    This field holds the ((IP addresss))(((address, IPv4))) in
+    This field holds the ((IP address))(((address, IPv4))) in
     network-byte order.
 
 TIP: The `sa_port` and `sa_addr` fields are in network-byte order to
 facilitate their use with system APIs such as `inet_ntop()`.
 Most platforms use some form of BSD-derived network API, which uses
-network-byte order in the various structurs (such as `sockaddr_in`).
+network-byte order in the various structures (such as `sockaddr_in`).
 
 IMPORTANT: This field appears similar to BSD `sockaddr_in`, but it is
-_not_ the same, and they may not be used interchangeabley.
+_not_ the same, and they may not be used interchangeably.
 
 == SEE ALSO
 
diff --git a/docs/man/nng_sockaddr_in6.5.adoc b/docs/man/nng_sockaddr_in6.5.adoc
index 2d2a8a8b..cd967296 100644
--- a/docs/man/nng_sockaddr_in6.5.adoc
+++ b/docs/man/nng_sockaddr_in6.5.adoc
@@ -51,16 +51,16 @@ The following structure members are present:
     A zero value here is used when no specific port number is indicated.
 
 `sa_addr`::
-    This field holds the ((IP addresss))(((address, IPv6))) in
+    This field holds the ((IP address))(((address, IPv6))) in
     network-byte order.
 
 TIP: The `sa_port` and `sa_addr` fields are in network-byte order to
 facilitate their use with system APIs such as `inet_ntop()`.
 Most platforms use some form of BSD-derived network API, which uses
-network-byte order in the various structurs (such as `sockaddr_in6`).
+network-byte order in the various structures (such as `sockaddr_in6`).
 
 IMPORTANT: This field appears similar to BSD `sockaddr_in6`, but it is
-_not_ the same, and they may not be used interchangeabley.
+_not_ the same, and they may not be used interchangeably.
 
 == SEE ALSO
 
diff --git a/docs/man/nng_sockaddr_inproc.5.adoc b/docs/man/nng_sockaddr_inproc.5.adoc
index 428ddc1b..b3dafd1a 100644
--- a/docs/man/nng_sockaddr_inproc.5.adoc
+++ b/docs/man/nng_sockaddr_inproc.5.adoc
@@ -47,7 +47,7 @@ The following structure members are present:
     The string must be `NUL` terminated, but no other restrictions exist.
 
 TIP: In order to ensure maximum compatibility, applications should avoid
-hard coding the sizeof the `sa_name` member explicitly, but use the
+hard coding the size of the `sa_name` member explicitly, but use the
 `sizeof` operator to determine its actual size at compile time.
 Furthermore, the size is guaranteed to be at least 128.
 
diff --git a/docs/man/nng_sockaddr_ipc.5.adoc b/docs/man/nng_sockaddr_ipc.5.adoc
index 8e598144..569d8694 100644
--- a/docs/man/nng_sockaddr_ipc.5.adoc
+++ b/docs/man/nng_sockaddr_ipc.5.adoc
@@ -42,17 +42,17 @@ The following structure members are present:
     This field will always have the value ((`NNG_AF_IPC`)).
 
 `sa_path`::
-    This field holds the C string corresponding to pathname where the
+    This field holds the C string corresponding to path name where the
     IPC socket is located.
     For systems using UNIX domain sockets, this will be an absolute
-    pathname in the filesystem, where the UNIX domain socket is located.
-    For Windows systems, this is the pathname of the Named Pipe, without
+    path name in the file system, where the UNIX domain socket is located.
+    For Windows systems, this is the path name of the Named Pipe, without
     the leading `\\.pipe\` portion, which will be automatically added.
 
 NOTE: At this time, there is no support for Linux "`abstract sockets`".
 
 TIP: In order to ensure maximum compatibility, applications should avoid
-hard coding the sizeof the `sa_path` member explicitly, but use the
+hard coding the size of the `sa_path` member explicitly, but use the
 `sizeof` operator to determine its actual size at compile time.
 Furthermore, the size is guaranteed to be at least 128, but paths of
 this length may not be supported on all systems.
diff --git a/docs/man/nng_sockaddr_zt.5.adoc b/docs/man/nng_sockaddr_zt.5.adoc
index 9491823e..0019116a 100644
--- a/docs/man/nng_sockaddr_zt.5.adoc
+++ b/docs/man/nng_sockaddr_zt.5.adoc
@@ -49,7 +49,7 @@ The following structure members are present:
 
 `sa_nwid`::
     (((network number, ZeroTier)))
-    This field holds the ZeroTiero network number (or ID).
+    This field holds the ZeroTier network number (or ID).
     This value is in native byte order.
 
 `sa_nodeid`::
diff --git a/docs/man/nng_strdup.3.adoc b/docs/man/nng_strdup.3.adoc
index 24a56ada..9c2eda4f 100644
--- a/docs/man/nng_strdup.3.adoc
+++ b/docs/man/nng_strdup.3.adoc
@@ -26,7 +26,7 @@ char *nng_strdup(const char *src);
 
 The `nng_strdup()` duplicates the string _src_ and returns it.
 
-This is logically equiavlent to using `<<nng_alloc.3#,nng_alloc()>>`
+This is logically equivalent to using `<<nng_alloc.3#,nng_alloc()>>`
 to allocate a region of memory of `strlen(s) + 1` bytes, and then
 using `strcpy()` to copy the string into the destination before
 returning it.
diff --git a/docs/man/nng_surveyor.7.adoc b/docs/man/nng_surveyor.7.adoc
index 41ce8fe0..8bee4fd9 100644
--- a/docs/man/nng_surveyor.7.adoc
+++ b/docs/man/nng_surveyor.7.adoc
@@ -95,7 +95,7 @@ The following protocol-specific options is available.
 ((`NNG_OPT_SURVEYOR_SURVEYTIME`))::
 
    This read/write option is an `<<nng_duration.5#,nng_duration>>`
-   representing a postive number of milliseconds that following surveys
+   representing a positive number of milliseconds that following surveys
    will last.
    When a new survey is started, a timer of this duration is also started.
    Any responses arriving this time will be discarded.
@@ -111,7 +111,7 @@ This form uses a "`stack`" of 32-bit big-endian identifiers.
 There *must* be at least one identifier, the __survey ID__, which will be the
 last element in the array, and *must* have the most significant bit set.
 
-There may be additional __peer ID__s preceeding the survey ID.
+There may be additional __peer ID__s preceding the survey ID.
 These will be distinguishable from the survey ID by having their most
 significant bit clear.
 
diff --git a/docs/man/nng_tls.7.adoc b/docs/man/nng_tls.7.adoc
index 78a87b86..61d0b220 100644
--- a/docs/man/nng_tls.7.adoc
+++ b/docs/man/nng_tls.7.adoc
@@ -174,7 +174,7 @@ more details.
 
 ((`NNG_OPT_TLS_VERIFIED`))::
 
-This is a read-only option which returns a boolean value (integer 0 or 1).
+This is a read-only option which returns a Boolean value (integer 0 or 1).
 It will true (1) if the remote peer has been properly verified using TLS
 authentication, or false (0) otherwise.
 This option may return incorrect
diff --git a/docs/man/nng_tls_config_alloc.3tls.adoc b/docs/man/nng_tls_config_alloc.3tls.adoc
index 3c898383..c68fac05 100644
--- a/docs/man/nng_tls_config_alloc.3tls.adoc
+++ b/docs/man/nng_tls_config_alloc.3tls.adoc
@@ -40,7 +40,7 @@ client (`NNG_TLS_MODE_CLIENT`) or as a server (`NNG_TLS_MODE_SERVER`),
 depending on the value of _mode_.
 
 A TLS object can be further modified by functions that set the security
-keys used, peeer certificates, protocol policies, and so forth.
+keys used, peer certificates, protocol policies, and so forth.
 
 A single TLS configuration object can be used with multiple TLS streams
 or services.
diff --git a/docs/man/nng_tls_config_auth_mode.3tls.adoc b/docs/man/nng_tls_config_auth_mode.3tls.adoc
index edd4235b..da9ee0c4 100644
--- a/docs/man/nng_tls_config_auth_mode.3tls.adoc
+++ b/docs/man/nng_tls_config_auth_mode.3tls.adoc
@@ -44,7 +44,7 @@ TLS servers, which most typically do not authenticate their clients.
 ((`NNG_TLS_AUTH_MODE_OPTIONAL`))::
 If a certificate is presented by the peer, then it is validated.
 However, if the peer does not present a valid certificate,
-then the sesssion is allowed to proceed without authentication.
+then the session is allowed to proceed without authentication.
 
 ((`NNG_TLS_AUTH_MODE_REQUIRED`))::
 A check is made to ensure that the peer has presented a valid certificate
diff --git a/docs/man/nng_url_parse.3.adoc b/docs/man/nng_url_parse.3.adoc
index ec44ccf5..f26d522d 100644
--- a/docs/man/nng_url_parse.3.adoc
+++ b/docs/man/nng_url_parse.3.adoc
@@ -38,7 +38,7 @@ struct nng_url {
     char *u_rawurl;   // Unparsed URL, with minimal canonicalization.
     char *u_userinfo; // Userinfo component, or NULL.
     char *u_host;     // Full host, including port if present.
-    char *u_hostname; // Hostname only (or address), or empy string.
+    char *u_hostname; // Hostname only (or address), or empty string.
     char *u_port;     // Port number, may be default or empty string.
     char *u_path;     // Path if present, empty string otherwise.
     char *u_query;    // Query info if present, NULL otherwise.
diff --git a/docs/man/nng_ws_register.3.adoc b/docs/man/nng_ws_register.3.adoc
index 414f6a8e..54dc154d 100644
--- a/docs/man/nng_ws_register.3.adoc
+++ b/docs/man/nng_ws_register.3.adoc
@@ -11,7 +11,7 @@
 
 == NAME
 
-nng_ws_register - register websocket transport
+nng_ws_register - register WebSocket transport
 
 == SYNOPSIS
 
diff --git a/docs/man/nng_wss_register.3.adoc b/docs/man/nng_wss_register.3.adoc
index 946ffbf1..e822c4d6 100644
--- a/docs/man/nng_wss_register.3.adoc
+++ b/docs/man/nng_wss_register.3.adoc
@@ -11,7 +11,7 @@
 
 == NAME
 
-nng_ws_register - register websocket secure transport
+nng_ws_register - register WebSocket secure transport
 
 == SYNOPSIS
 
diff --git a/docs/man/nng_zerotier.7.adoc b/docs/man/nng_zerotier.7.adoc
index 9142139c..6a3c238c 100644
--- a/docs/man/nng_zerotier.7.adoc
+++ b/docs/man/nng_zerotier.7.adoc
@@ -142,7 +142,7 @@ The following transport options are available:
   identity, and federation membership.
   This option must be set before the ZeroTier transport is first used.
   If this value is empty, then an ephemeral ZeroTier node is created,
-  nd no persistent state is used.
+  and no persistent state is used.
   The default is to use an ephemeral node.
 +
 NOTE: If this option is set to different values on different sockets,
diff --git a/docs/man/nngcat.1.adoc b/docs/man/nngcat.1.adoc
index fec20c72..2b895471 100644
--- a/docs/man/nngcat.1.adoc
+++ b/docs/man/nngcat.1.adoc
@@ -11,7 +11,7 @@
 
 == NAME
 
-nngcat - command line access to Scalabity Protocols
+nngcat - command line access to Scalability Protocols
 
 == SYNOPSIS
 
@@ -130,7 +130,7 @@ NOTE: At least one protocol must be selected.
   messages from <<nng_push.7#,_push_>> version 0 peers.
 
 *--pair0*::
-  Select the <<nng_pair.7#,_pair_>> veresion 0 protocol.
+  Select the <<nng_pair.7#,_pair_>> version 0 protocol.
   This protocol can send and receive messages with one connected _pair_
   version 0 peer.
 
@@ -270,7 +270,7 @@ when using addresses that are not secured with TLS.
 
 *--key*=_FILE_::
   Load own key from _FILE_.
-  Should be used in conjuction with *--cert*.
+  Should be used in conjunction with *--cert*.
   If not specified, and *--cert* is specified, then a single file containing both
   the private key and the associated certificate is assumed.