diff --git a/doc/zmq_bind.txt b/doc/zmq_bind.txt
index 7ce96edb..79ec10aa 100644
--- a/doc/zmq_bind.txt
+++ b/doc/zmq_bind.txt
@@ -28,6 +28,7 @@ The 'endpoint' is a string consisting of a 'transport'`://` followed by an
 'inproc':: local in-process (inter-thread) communication transport, see linkzmq:zmq_inproc[7]
 'pgm', 'epgm':: reliable multicast transport using PGM, see linkzmq:zmq_pgm[7]
 'vmci':: virtual machine communications interface (VMCI), see linkzmq:zmq_vmci[7]
+'udp':: unreliable unicast and multicast using UDP, see linkzmq:zmq_udp[7]
 
 Every 0MQ socket type except 'ZMQ_PAIR' supports one-to-many and many-to-one
 semantics. The precise semantics depend on the socket type and are defined in
diff --git a/doc/zmq_connect.txt b/doc/zmq_connect.txt
index f23e7af6..bf21736d 100644
--- a/doc/zmq_connect.txt
+++ b/doc/zmq_connect.txt
@@ -28,6 +28,7 @@ The 'endpoint' is a string consisting of a 'transport'`://` followed by an
 'inproc':: local in-process (inter-thread) communication transport, see linkzmq:zmq_inproc[7]
 'pgm', 'epgm':: reliable multicast transport using PGM, see linkzmq:zmq_pgm[7]
 'vmci':: virtual machine communications interface (VMCI), see linkzmq:zmq_vmci[7]
+'udp':: unreliable unicast and multicast using UDP, see linkzmq:zmq_udp[7]
 
 Every 0MQ socket type except 'ZMQ_PAIR' supports one-to-many and many-to-one
 semantics. The precise semantics depend on the socket type and are defined in