diff options
| author | Garrett D'Amore <garrett@damore.org> | 2018-05-01 17:11:32 -0700 |
|---|---|---|
| committer | Garrett D'Amore <garrett@damore.org> | 2018-05-01 19:18:37 -0700 |
| commit | 3d3fa690c4f81bf4ed0a2de42c3c8fbb9f4cca5c (patch) | |
| tree | d670fc9ac327e017c62a72cbaeda4bcacda5f9dd /docs/man/nng_device.3.adoc | |
| parent | 1ef281a7fbd544c6d3384fd8a71d10dc4bb081e8 (diff) | |
| download | nng-3d3fa690c4f81bf4ed0a2de42c3c8fbb9f4cca5c.tar.gz nng-3d3fa690c4f81bf4ed0a2de42c3c8fbb9f4cca5c.tar.bz2 nng-3d3fa690c4f81bf4ed0a2de42c3c8fbb9f4cca5c.zip | |
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.
Diffstat (limited to 'docs/man/nng_device.3.adoc')
| -rw-r--r-- | docs/man/nng_device.3.adoc | 8 |
1 files changed, 4 insertions, 4 deletions
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 <<nng_options.5#NNG_OPT_RAW,raw>> mode sockets may be used with this function. These can be created using `_raw` forms of the various socket constructors, -such as <<nng_req_open.3#,`nng_req0_open_raw()`>>. +such as `<<nng_req_open.3#,nng_req0_open_raw()>>`. 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, -<<nng_socket.5#,`nng_socket`>> of course). +One of the sockets may be passed an inititalize `-1` (cast to an, +`<<nng_socket.5#,nng_socket>>` 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 <<nng_pair.7#,_pair_>> 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 <<nng_options.5#NNG_OPT_MAXTTL,`NNG_OPT_MAXTTL`>> +This is controlled via the `<<nng_options.5#NNG_OPT_MAXTTL,NNG_OPT_MAXTTL>>` option. IMPORTANT: Not all protocols have support for guarding against forwarding loops, |