Harmonize the use of NNG in documentation.

NNG is always a noun, never an adjective, and should always
be capitalized.  We also reduced some unnecessary usages of it.

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/man/nn_getsockopt.3compat.adoc b/docs/man/nn_getsockopt.3compat.adoc
index 743808b4..0c476cca 100644
--- a/docs/man/nn_getsockopt.3compat.adoc
+++ b/docs/man/nn_getsockopt.3compat.adoc
@@ -57,8 +57,8 @@ thus size 4, unless otherwise indicated.)
 `NN_SNDBUF`::
 Send buffer size in bytes.
 
-NOTE: In _nng_ buffers are sized as a count of messages rather than
-bytes; accordingly this value is the _nng_ queue depth multiplied by 1024
+NOTE: In _NNG_ buffers are sized as a count of messages rather than
+bytes; accordingly this value is the queue depth multiplied by 1024
 (representing an estimate that the average message size is 1kB).
 Applications that have unusual message sizes may wish to adjust the value
 used here accordingly.
@@ -108,7 +108,7 @@ The default is zero.
 This option is always zero and exists only for compatibility.
 
 NOTE: This option was unreliable in early releases of _libnanomsg_, and
-is unsupported in _nng_ and recent _libnanomsg_ releases.
+is unsupported in _NNG_ and recent _libnanomsg_ releases.
 Applications needing assurance of message delivery should either include an
 explicit notification (automatic with the `NN_REQ` protocol) or allow
 sufficient time for the socket to drain before closing the socket or exiting.
@@ -200,7 +200,7 @@ This `NN_IPC` option is not supported at this time.
 This `NN_TCP` option is not supported at this time.
 
 `NN_WS_MSG_TYPE`::
-This `NN_WS` option is not supported, as _nng_ only supports binary messages
+This `NN_WS` option is not supported, as _NNG_ only supports binary messages
 in this implementation.
 
 == RETURN VALUES