From 3d3fa690c4f81bf4ed0a2de42c3c8fbb9f4cca5c Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Tue, 1 May 2018 17:11:32 -0700 Subject: 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. --- docs/man/nng_device.3.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/man/nng_device.3.adoc') diff --git a/docs/man/nng_device.3.adoc b/docs/man/nng_device.3.adoc index aaf71af6..4f036d03 100644 --- a/docs/man/nng_device.3.adoc +++ b/docs/man/nng_device.3.adoc @@ -34,15 +34,15 @@ reliability, and isolation. Only <> mode sockets may be used with this function. These can be created using `_raw` forms of the various socket constructors, -such as <>. +such as `<>`. The `nng_device()` function does not return until one of the sockets is closed. === Reflectors -One of the sockets may be passed the special value `-1` (cast to an, -<> of course). +One of the sockets may be passed an inititalize `-1` (cast to an, +`<>` of course). If this is the case, then the other socket must be valid, and must be a protocol that is bidirectional and can peer with itself (such as <> or @@ -81,7 +81,7 @@ In these cases, the default limit (usually 8), ensures that messages will self-terminate when they have passed through too many forwarders, protecting the network from unlimited message amplification that can arise through misconfiguration. -This is controlled via the <> +This is controlled via the `<>` option. IMPORTANT: Not all protocols have support for guarding against forwarding loops, -- cgit v1.2.3-70-g09d2