- mention curl_multi_socket_action() rather than the deprecated

  curl_multi_socket()
- don't claim that it has an argument named 'easy' because it doesn't!

diff --git a/docs/libcurl/curl_multi_timeout.3 b/docs/libcurl/curl_multi_timeout.3
index 7302e0ac40be57a5466f79f7e0cda0d436b642c2..b4da9af896e3cead7955443330d4e752dced6b05 100644 (file)
--- a/docs/libcurl/curl_multi_timeout.3
+++ b/docs/libcurl/curl_multi_timeout.3
@@ -14,10 +14,9 @@ An application using the libcurl multi interface should call
 actions \- at most \- before proceeding.
 
 Proceeding means either doing the socket-style timeout action: call the
-\fBcurl_multi_socket(3)\fP function with the \fBsockfd\fP argument set to
-CURL_SOCKET_TIMEOUT and the \fBeasy\fP argument set to CURL_EASY_TIMEOUT, or
-simply calling \fBcurl_multi_perform(3)\fP if you're using the simpler and
-older multi interface approach.
+\fBcurl_multi_socket_action(3)\fP function with the \fBsockfd\fP argument set
+to CURL_SOCKET_TIMEOUT, or call \fBcurl_multi_perform(3)\fP if you're using
+the simpler and older multi interface approach.
 
 The timeout value returned in the long \fBtimeout\fP points to, is in number
 of milliseconds at this very moment. If 0, it means you should proceed