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_ctx_recv.3.adoc b/docs/man/nng_ctx_recv.3.adoc
index d4e84b00..03aa5de8 100644
--- a/docs/man/nng_ctx_recv.3.adoc
+++ b/docs/man/nng_ctx_recv.3.adoc
@@ -29,9 +29,9 @@ The `nng_ctx_recv()` receives a <<nng_msg.5#,message>> using the
 
 When a message is successfully received by the context, it is
 stored in the _aio_ by an internal call equivalent to
-<<nng_aio_set_msg.3#,`nng_aio_set_msg()`>>, then the completion
+`<<nng_aio_set_msg.3#,nng_aio_set_msg()>>`, then the completion
 callback on the _aio_ is executed.
-In this case, <<nng_aio_result.3#,`nng_aio_result()`>> will
+In this case, `<<nng_aio_result.3#,nng_aio_result()>>` will
 return zero.
 The callback function is responsible for retrieving the message
 and disposing of it appropriately.
@@ -42,7 +42,7 @@ case can lead to memory leaks.
 If for some reason the asynchronous receive cannot be completed
 successfully (including by being canceled or timing out), then
 the callback will still be executed,
-but <<nng_aio_result.3#,`nng_aio_result()`>> will be non-zero.
+but `<<nng_aio_result.3#,nng_aio_result()>>` will be non-zero.
 
 NOTE: The semantics of what receiving a message means varies from protocol to
 protocol, so examination of the protocol documentation is encouraged.