From 3e0ecffbd60ac2a6f50643adc07b0d2fea0cb22b Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Wed, 30 May 2018 18:10:59 -0700 Subject: Fix numerous spelling errrors. These were found with the help of "aspell". Additionally, while reviewing the output from the spell checker, several content errors were noticed and fixed. --- docs/man/nng_device.3.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 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 807d8e54..fed4ef7c 100644 --- a/docs/man/nng_device.3.adoc +++ b/docs/man/nng_device.3.adoc @@ -41,9 +41,9 @@ is closed. === Reflectors -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 +One of the sockets passed may be an unopened socket initialized with +the `NNG_SOCKET_INITIALIZER` special value. +If this is the case, then the other socket must be valid, and must use a protocol that is bidirectional and can peer with itself (such as <> or <>.) @@ -73,7 +73,7 @@ header of the output bound message. The underlying raw mode protocols supply the necessary header adjustments to add or remove routing headers as needed. This allows replies to be -returned to requestors, and responses to be routed back to surveyors. +returned to requesters, and responses to be routed back to surveyors. Additionally, some protocols have a maximum ((time-to-live)) to protect against forwarding loops and especially amplification loops. @@ -85,7 +85,7 @@ This is controlled via the `<>` option. IMPORTANT: Not all protocols have support for guarding against forwarding loops, -and even for those that do, forwarding loops can be extremely determintal +and even for those that do, forwarding loops can be extremely detrimental to network performance. NOTE: Devices (forwarders and reflectors) act in best effort delivery mode only. @@ -93,7 +93,7 @@ If a message is received from one socket that cannot be accepted by the other (due to backpressure or other issues), then the message is discarded. TIP: Use the request/reply pattern, which includes automatic retries by -the requestor, if reliable delivery is needed. +the requester, if reliable delivery is needed. == RETURN VALUES -- cgit v1.2.3-70-g09d2