aboutsummaryrefslogtreecommitdiff
path: root/docs/man/nng_thread_create.3supp.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'docs/man/nng_thread_create.3supp.adoc')
-rw-r--r--docs/man/nng_thread_create.3supp.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/man/nng_thread_create.3supp.adoc b/docs/man/nng_thread_create.3supp.adoc
index 359dabab..b458cf96 100644
--- a/docs/man/nng_thread_create.3supp.adoc
+++ b/docs/man/nng_thread_create.3supp.adoc
@@ -42,7 +42,7 @@ programs that use simple sequential execution, using functions in the
_NNG_ suite that would otherwise normally "`block`".
When the thread is no longer needed, the
-<<nng_thread_destroy.3supp#,`nng_thread_destroy()`>>
+`<<nng_thread_destroy.3supp#,nng_thread_destroy()>>`
function should be used to reap it.
(This function will block waiting for _func_ to return.)
@@ -61,7 +61,7 @@ TIP: The system may impose limits on the number of threads that can be
created.
Typically applications should not create more than a few dozen of these.
If greater concurrency or scalability is needed, consider instead using
-an asynchronous model using <<nng_aio.5#,`nng_aio`>> structures.
+an asynchronous model using `<<nng_aio.5#,nng_aio>>` structures.
TIP: Threads can be synchronized using
<<nng_mtx_alloc.3supp#,mutexes>> and