From 3d3fa690c4f81bf4ed0a2de42c3c8fbb9f4cca5c Mon Sep 17 00:00:00 2001
From: Garrett D'Amore <garrett@damore.org>
Date: Tue, 1 May 2018 17:11:32 -0700
Subject: 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.
---
 docs/man/libnng.3.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'docs/man/libnng.3.adoc')

diff --git a/docs/man/libnng.3.adoc b/docs/man/libnng.3.adoc
index 149dc9f4..61ceacc7 100644
--- a/docs/man/libnng.3.adoc
+++ b/docs/man/libnng.3.adoc
@@ -124,7 +124,7 @@ mode may need to access the header of messages.
 === Asynchronous Operations
 
 Most applications will interact with _nng_ synchronously; that is that
-functions such as <<nng_send.3#,`nng_send()`>> will block the calling
+functions such as `<<nng_send.3#,nng_send()>>` will block the calling
 thread until the operation has completed.
 
 NOTE: Synchronous operations which send messages may return before the
@@ -136,9 +136,9 @@ Asynchronous operations behave differently.  These operations are
 initiated by the calling thread, but control returns immediately to
 the calling thread.  When the operation is subsequently completed (regardless
 of whether this was successful or not), then a user supplied function
-("callback") is executed.
+("`callback`") is executed.
 
-A context structure, an <<nng_aio.5#,`nng_aio`>>, is allocated and
+A context structure, an `<<nng_aio.5#,nng_aio>>`, is allocated and
 associated with each asynchronous operation.
 Only a single asynchronous operation may be associated with an
 `nng_aio` at any time.
-- 
cgit v1.2.3-70-g09d2

