From 58fd3f8c1d761e69426618802d16f20e13ff886d Mon Sep 17 00:00:00 2001 From: Martin Sustrik Date: Sun, 29 Apr 2012 14:51:22 +0200 Subject: Leftover references to ZMQ removed from xs_setsockopt(3) man page Signed-off-by: Martin Sustrik --- doc/xs_getsockopt.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/xs_getsockopt.txt b/doc/xs_getsockopt.txt index 681015c..a60ee4b 100644 --- a/doc/xs_getsockopt.txt +++ b/doc/xs_getsockopt.txt @@ -354,10 +354,10 @@ necessarily indicate that messages are available to be read from, or can be written to, the underlying socket; applications must retrieve the actual event state with a subsequent retrieval of the 'XS_EVENTS' option. -NOTE: The returned file descriptor is also used internally by the 'zmq_send' -and 'zmq_recv' functions. As the descriptor is edge triggered, applications -must update the state of 'ZMQ_EVENTS' after each invocation of 'zmq_send' -or 'zmq_recv'.To be more explicit: after calling 'zmq_send' the socket may +NOTE: The returned file descriptor is also used internally by the 'xs_send' +and 'xs_recv' functions. As the descriptor is edge triggered, applications +must update the state of 'XS_EVENTS' after each invocation of 'xs_send' +or 'xs_recv'.To be more explicit: after calling 'xs_send' the socket may become readable (and vice versa) without triggering a read event on the file descriptor. -- cgit v1.2.3