Markup fixes, ensuring links are colored properly.

It turns out that when creating cross references, we need to
make any text styling (generally literal characters) outside of
the link, to avoid having the styling override the link color.
(We prefer to have links colored for ease of use.)

While here a few other markup, and actual content, errors were fixed.

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/man/nng_mtx_lock.3supp.adoc b/docs/man/nng_mtx_lock.3supp.adoc
index 54aacd37..8ea4bdd6 100644
--- a/docs/man/nng_mtx_lock.3supp.adoc
+++ b/docs/man/nng_mtx_lock.3supp.adoc
@@ -27,7 +27,7 @@ void nng_mtx_lock(nng_mtx *mtx);
 
 The `nng_mtx_lock()` acquires exclusive ownership of the mutex _mtx_.
 If the lock is already owned, this function will wait until the current
-owner releases it with <<nng_mtx_unlock.3supp#,`nng_mtx_unlock()`>>.
+owner releases it with `<<nng_mtx_unlock.3supp#,nng_mtx_unlock()>>`.
 
 If multiple threads are waiting for the lock, the order of acquisition
 is not specified.
@@ -40,8 +40,8 @@ It is a programming error for the owner of a mutex to attempt to
 reacquire it.
 
 ****
-_NNG_ offers neither a "`trylock`" operation, nor recursive mutexes. 
-This is by design, as _NNG_ itself does not use such things,
+_nng_ offers neither a "`trylock`" operation, nor recursive mutexes. 
+This is by design, as _nng_ itself does not use such things,
 and most often the need for them is the result of poor design.
 If such capabilities are needed, they may be synthesized fairly
 easily from mutexes and condition variables.