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_msg_get_pipe.3.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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

diff --git a/docs/man/nng_msg_get_pipe.3.adoc b/docs/man/nng_msg_get_pipe.3.adoc
index 4a38c9ff..e12a956c 100644
--- a/docs/man/nng_msg_get_pipe.3.adoc
+++ b/docs/man/nng_msg_get_pipe.3.adoc
@@ -24,7 +24,7 @@ nng_pipe nng_msg_get_pipe(nng_msg *msg);
 
 == DESCRIPTION
 
-The `nng_msg_get_pipe()` returns the <<nng_pipe.5#,`nng_pipe`>> object
+The `nng_msg_get_pipe()` returns the `<<nng_pipe.5#,nng_pipe>>` object
 associated with message _msg_.
 On receive, this is the pipe from which a message was received.
 On transmit, this would be the pipe that the message should be delivered
@@ -36,7 +36,7 @@ The most usual use case for this is to obtain information about the peer
 from which the message was received.
 This can be used to provide different behaviors for different peers, such as
 a higher level of authentication for peers located on an untrusted network.
-The <<nng_pipe_getopt.3#,`nng_pipe_getopt()`>> function
+The `<<nng_pipe_getopt.3#,nng_pipe_getopt()>>` function
 is useful in this situation.
 
 
-- 
cgit v1.2.3-70-g09d2

