aboutsummaryrefslogtreecommitdiff
path: root/docs/man/libnng.3.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'docs/man/libnng.3.adoc')
-rw-r--r--docs/man/libnng.3.adoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/man/libnng.3.adoc b/docs/man/libnng.3.adoc
index 149dc9f4..61ceacc7 100644
--- a/docs/man/libnng.3.adoc
+++ b/docs/man/libnng.3.adoc
@@ -124,7 +124,7 @@ mode may need to access the header of messages.
=== Asynchronous Operations
Most applications will interact with _nng_ synchronously; that is that
-functions such as <<nng_send.3#,`nng_send()`>> will block the calling
+functions such as `<<nng_send.3#,nng_send()>>` will block the calling
thread until the operation has completed.
NOTE: Synchronous operations which send messages may return before the
@@ -136,9 +136,9 @@ Asynchronous operations behave differently. These operations are
initiated by the calling thread, but control returns immediately to
the calling thread. When the operation is subsequently completed (regardless
of whether this was successful or not), then a user supplied function
-("callback") is executed.
+("`callback`") is executed.
-A context structure, an <<nng_aio.5#,`nng_aio`>>, is allocated and
+A context structure, an `<<nng_aio.5#,nng_aio>>`, is allocated and
associated with each asynchronous operation.
Only a single asynchronous operation may be associated with an
`nng_aio` at any time.