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, 2 insertions, 2 deletions

diff --git a/docs/man/nng_sendmsg.3.adoc b/docs/man/nng_sendmsg.3.adoc
index e6d653b3..dffb042f 100644
--- a/docs/man/nng_sendmsg.3.adoc
+++ b/docs/man/nng_sendmsg.3.adoc
@@ -36,13 +36,13 @@ to dispose of the _msg_, which may include freeing it, sending it to
 another socket, or simply trying again later.
 
 TIP: Using this function gives access to the message structure, and may
-offer more functionality than the simpler <<nng_send.3#,`nng_send()`>> function.
+offer more functionality than the simpler `<<nng_send.3#,nng_send()>>` function.
 
 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 a <<nng_pub.7#,_pub_>> socket the data is broadcast, so that
 any peers who have a suitable subscription will be able to receive it using
-<<nng_recv.3#,`nng_recv()`>> or a similar function.)
+`<<nng_recv.3#,nng_recv()>>` or a similar function.)
 Furthermore, some protocols may not support sending (such as
 <<nng_sub.7#,_sub_>>) or may require other conditions.
 (For example, <<nng_rep.7#,_rep_>> sockets cannot normally send data, which