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/nng_recv.3.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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

diff --git a/docs/man/nng_recv.3.adoc b/docs/man/nng_recv.3.adoc
index 47ce4cbe..5ab180f0 100644
--- a/docs/man/nng_recv.3.adoc
+++ b/docs/man/nng_recv.3.adoc
@@ -38,13 +38,13 @@ In this case the caller must set the value of _data_ to the location
 of another pointer (of type `void *`), and the _sizep_ pointer must be set
 to a location to receive the size of the message body.
 The function will then allocate a message buffer
-(as if by <<nng_alloc.3#,`nng_alloc()`>>), fill it with
+(as if by `<<nng_alloc.3#,nng_alloc()>>`), fill it with
 the message body, and store it at the address referenced by _data_, and update
 the size referenced by _sizep_.
 When this flag is present, the caller assumes
 responsibility for disposing of the received buffer either by the function
-<<nng_free.3#,`nng_free()`>> or reusing the message for sending (with the same
-size) in a call to <<nng_send.3#,`nng_send()`>>.
+`<<nng_free.3#,nng_free()>>` or reusing the message for sending (with the same
+size) in a call to `<<nng_send.3#,nng_send()>>`.
 
 NOTE: The semantics of what receiving a message means vary from protocol to
 protocol, so examination of the protocol documentation is encouraged.
-- 
cgit v1.2.3-70-g09d2

