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

diff --git a/docs/man/nng_socket.5.adoc b/docs/man/nng_socket.5.adoc
index 2d8d7256..35a6a3c6 100644
--- a/docs/man/nng_socket.5.adoc
+++ b/docs/man/nng_socket.5.adoc
@@ -27,9 +27,9 @@ typedef struct nng_socket_s nng_socket;
 An `nng_socket`(((socket))) is a handle to an underlying "`socket`" object.
 All communication between the application and remote Scalability Protocol
 peers is done through sockets.
-A given socket can have multiple dialers (<<nng_dialer.5#,`nng_dialer`>>)
-and/or (<<nng_listener.5#,`nng_listener`>>), and multiple
-pipes (<<nng_pipe.5#,`nng_pipe`>>), and
+A given socket can have multiple dialers (`<<nng_dialer.5#,nng_dialer>>`)
+and/or listeners (`<<nng_listener.5#,nng_listener>>`), and multiple
+pipes (`<<nng_pipe.5#,nng_pipe>>`), and
 may be connected to multiple transports at the same time.
 However, a given socket will have exactly one "`protocol`" associated with it,
 and is responsible for any state machines or other protocol-specific logic.
@@ -40,9 +40,9 @@ Passing structures this way ensures gives the compiler a chance to perform
 accurate type checks in functions passing values of this type.
 
 Each `nng_socket` is created by a protocol-specific constructor, such as
-<<nng_rep_open.3#,`nng_rep_open()`>>.
+`<<nng_rep_open.3#,nng_rep_open()>>`.
 When the socket is no longer needed, it can be closed with
-<<nng_close.3#,`nng_close()`>>.
+`<<nng_close.3#,nng_close()>>`.
 
 [[NNG_SOCKET_INITIALIZER]]
 === Initialization