Fix incorrect section numbers.

2 files changed, 7 insertions, 7 deletions

diff --git a/docs/man/nng_recv.adoc b/docs/man/nng_recv.adoc
index e12d0b53..f9f8f1dd 100644
--- a/docs/man/nng_recv.adoc
+++ b/docs/man/nng_recv.adoc
@@ -45,11 +45,11 @@ size) via <<nng_send#,nng_send(3)>>.
 
 NOTE: The semantics of what receiving a message means vary from protocol to
 protocol, so examination of the protocol documentation is encouraged.  (For
-example, with an <<nng_req#,nng_req(3)>> socket a message may only be received
-after a request has been sent, and an <<nng_sub#,nng_sub(3)>> socket
+example, with an <<nng_req#,nng_req(7)>> socket a message may only be received
+after a request has been sent, and an <<nng_sub#,nng_sub(7)>> socket
 may only receive messages corresponding to topics to which it has subscribed.)
 Furthermore, some protocols may not support receiving data at all, such as
-<<nng_pub#,nng_pub(3)>>.
+<<nng_pub#,nng_pub(7)>>.
 
 TIP: The `NNG_FLAG_ALLOC` flag can be used to reduce data copies, thereby
 increasing performance, particularly if the buffer is reused to send
diff --git a/docs/man/nng_send.adoc b/docs/man/nng_send.adoc
index 53a87de3..19034f33 100644
--- a/docs/man/nng_send.adoc
+++ b/docs/man/nng_send.adoc
@@ -29,11 +29,11 @@ using the socket _s_.
 
 NOTE: The semantics of what sending a message means vary from protocol to
 protocol, so examination of the protocol documentation is encouraged.  (For
-example, with an <<nng_pub#,nng_pub(3)>> socket the data is broadcast, so that
+example, with an <<nng_pub#,nng_pub(7)>> socket the data is broadcast, so that
 any peers who have a suitable subscription will be able to receive it using
 <<nng_recv#,nng_recv(3)>> or a similar function.)  Furthermore, some protocols
-may not support sending data (such as <<nng_sub#,nng_sub(3)>>) or may
-require other conditions.  (For example, <<nng_rep#,nng_rep(3)>> sockets
+may not support sending data (such as <<nng_sub#,nng_sub(7)>>) or may
+require other conditions.  (For example, <<nng_rep#,nng_rep(7)>> sockets
 cannot normally send data, which are responses to requests, until they have
 first received a request.)
 
@@ -63,7 +63,7 @@ NOTE: Regardless of the presence or absence of `NNG_FLAG_NONBLOCK`, there may
 be queues between the sender and the receiver.  Furthermore, there is no
 guarantee that the message has actually been delivered.  Finally, with some
 protocols, the semantic is implictly `NNG_FLAG_NONBLOCK`, such as with
-<<nng_pub#,nng_pub(3)>> sockets, which are best-effort delivery only.
+<<nng_pub#,nng_pub(7)>> sockets, which are best-effort delivery only.
 
 WARNING: When using `NNG_FLAG_ALLOC`, it is important that the value of _size_
 match the actual allocated size of the data.  Using an incorrect size results