From dcb962389c5f71bc25cdb84f3363eed95bad9bdd Mon Sep 17 00:00:00 2001
From: Garrett D'Amore <garrett@damore.org>
Date: Sat, 6 Jul 2019 13:33:55 -0700
Subject: fixes #861 Man pages need to use .adoc suffix

---
 docs/man/nng_msg_get_pipe.3.adoc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 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 2f9a9c84..154f4c43 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 xref:nng_pipe.5.adoc[`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 xref:nng_pipe_getopt.3.adoc[`nng_pipe_getopt()`] function
 is useful in this situation.
 
 
@@ -54,7 +54,7 @@ None.
 == SEE ALSO
 
 [.text-left]
-<<nng_msg_alloc.3#,nng_msg_alloc(3)>>,
-<<nng_msg_set_pipe.3#,nng_msg_set_pipe(3)>>,
-<<nng_pipe_getopt.3#,nng_pipe_getopt(3)>>,
-<<nng.7#,nng(7)>>
+xref:nng_msg_alloc.3.adoc[nng_msg_alloc(3)],
+xref:nng_msg_set_pipe.3.adoc[nng_msg_set_pipe(3)],
+xref:nng_pipe_getopt.3.adoc[nng_pipe_getopt(3)],
+xref:nng.7.adoc[nng(7)]
-- 
cgit v1.2.3-70-g09d2

