It's its not it's

doc/zmq_pgm.txt

@@ -54,7 +54,7 @@ and a port number.
 An 'interface' may be specified by either of the following:
 
 * The interface name as defined by the operating system.
-* The primary IPv4 address assigned to the interface, in it's numeric
+* The primary IPv4 address assigned to the interface, in its numeric
   representation.
 
 NOTE: Interface names are not standardised in any way and should be assumed to
@@ -63,7 +63,7 @@ names exist, thus only the primary IPv4 address may be used to specify an
 'interface'. The 'interface' part can be omitted, in that case the default one
 will be selected.
 
-A 'multicast address' is specified by an IPv4 multicast address in it's numeric
+A 'multicast address' is specified by an IPv4 multicast address in its numeric
 representation.
 
 

doc/zmq_socket_monitor.txt

@@ -45,14 +45,14 @@ ZMQ_EVENT_CONNECTED: connection established
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_CONNECTED' event triggers when a connection has been established
 to a remote peer. This can happen either synchronous or asynchronous.
-value is the FD of the newly connected socket.
+Value is the FD of the newly connected socket.
 
 
 ZMQ_EVENT_CONNECT_DELAYED: synchronous connect failed, it's being polled
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_CONNECT_DELAYED' event triggers when an immediate connection
-attempt is delayed and it's completion's being polled for.
-value has no meaning.
+attempt is delayed and its completion is being polled for.
+Value has no meaning.
 
 
 ZMQ_EVENT_CONNECT_RETRIED: asynchronous connect / reconnection attempt
@@ -60,56 +60,56 @@ ZMQ_EVENT_CONNECT_RETRIED: asynchronous connect / reconnection attempt
 The 'ZMQ_EVENT_CONNECT_RETRIED' event triggers when a connection attempt
 is being handled by reconnect timer. The reconnect interval's recomputed
 for each attempt.
-value is the reconnect interval.
+Value is the reconnect interval.
 
 
 ZMQ_EVENT_LISTENING: socket bound to an address, ready to accept connections
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_LISTENING' event triggers when a socket's successfully bound
 to a an interface.
-value is the FD of the newly bound socket.
+Value is the FD of the newly bound socket.
 
 
 ZMQ_EVENT_BIND_FAILED: socket could not bind to an address
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_BIND_FAILED' event triggers when a socket could not bind to
 a given interface.
-value is the errno generated by the bind call.
+Value is the errno generated by the bind call.
 
 
 ZMQ_EVENT_ACCEPTED: connection accepted to bound interface
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_ACCEPTED' event triggers when a connection from a remote peer
 has been established with a socket's listen address.
-value is the FD of the accepted socket.
+Value is the FD of the accepted socket.
 
 
 ZMQ_EVENT_ACCEPT_FAILED: could not accept client connection
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_ACCEPT_FAILED' event triggers when a connection attempt to
 a socket's bound address fails.
-value is the errno generated by accept.
+Value is the errno generated by accept.
 
 
 ZMQ_EVENT_CLOSED: connection closed
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_CLOSED' event triggers when a connection's underlying descriptor
 has been closed.
-value is the former FD of the for the closed socket. FD has been closed already!
+Value is the former FD of the for the closed socket. FD has been closed already!
 
 
 ZMQ_EVENT_CLOSE_FAILED: connection couldn't be closed
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_CLOSE_FAILED' event triggers when a descriptor could not be
 released back to the OS. Implementation note: ONLY FOR IPC SOCKETS.
-value is the errno generated by unlink.
+Value is the errno generated by unlink.
 
 
 ZMQ_EVENT_DISCONNECTED: broken session
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The 'ZMQ_EVENT_DISCONNECTED' event triggers when the stream engine (tcp and ipc
 specific) detects a corrupted / broken session.
-value is the FD of the socket.
+Value is the FD of the socket.
 
 
 RETURN VALUE