From d0ac83e34bde86e1fa888677adf7c99217e3205a Mon Sep 17 00:00:00 2001
From: Garrett D'Amore <garrett@damore.org>
Date: Thu, 18 Jun 2020 20:31:18 -0700
Subject: 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.
---
 docs/man/nng_msg.5.adoc | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

(limited to 'docs/man/nng_msg.5.adoc')

diff --git a/docs/man/nng_msg.5.adoc b/docs/man/nng_msg.5.adoc
index 61332fd7..6244116d 100644
--- a/docs/man/nng_msg.5.adoc
+++ b/docs/man/nng_msg.5.adoc
@@ -30,9 +30,8 @@ Messages internally have a ((body)), containing the application supplied
 payload, and a ((header)), containing protocol specific routing and similar
 related information.
 
-TIP: Using the message-oriented functions in the xref:nng.7.adoc[_nng_] API is
-a good way to reduce the likelihood of data copies and improve application
-performance.
+TIP: Using message-oriented functions is a good way to reduce the likelihood
+of data copies and improve application performance.
 
 Messages are allocated using the xref:nng_msg_alloc.3.adoc[`nng_msg_alloc()`]
 function, and are deallocated using the xref:nng_msg_free.3.adoc[`nng_msg_free()`]
-- 
cgit v1.2.3-70-g09d2

