diff --git a/doc/zmq_socket.txt b/doc/zmq_socket.txt
index 4f8309c2..a6ce453a 100644
--- a/doc/zmq_socket.txt
+++ b/doc/zmq_socket.txt
@@ -74,10 +74,6 @@ after which either peer can send messages asynchronously, to the other.
 
 The client-server pattern is formally defined by http://rfc.zeromq.org/spec:41.
 
-Note: this pattern is meant to eventually deprecate the use of 'ZMQ_DEALER' and
-'ZMQ_ROUTER' to build client-server architectures, as well as 'ZMQ_REP' and
-'ZMQ_REQ' for request-reply.
-
 ZMQ_CLIENT
 ^^^^^^^^^^
 A 'ZMQ_CLIENT' socket talks to a 'ZMQ_SERVER' socket. Either peer can connect,
@@ -166,9 +162,6 @@ Groups are matched using exact matching (vs prefix matching of PubSub).
 
 NOTE: Radio-dish is still in draft phase.
 
-Note: this pattern is meant to eventually deprecate the use of 'ZMQ_PUB' and
-'ZMQ_SUB' to build pub-sub architectures.
-
 ZMQ_RADIO
 ^^^^^^^
 A socket of type 'ZMQ_RADIO' is used by a _publisher_ to distribute data.
@@ -429,8 +422,6 @@ request sent.
 
 The request-reply pattern is formally defined by http://rfc.zeromq.org/spec:28.
 
-Note: this pattern will be deprecated in favor of the client-server pattern.
-
 ZMQ_REQ
 ^^^^^^^
 A socket of type 'ZMQ_REQ' is used by a _client_ to send requests to and