diff options
author | Daniel Stenberg <daniel@haxx.se> | 2021-11-01 13:43:11 +0100 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2021-11-01 13:50:27 +0100 |
commit | 0d979544fe2b6f9ebc687302bbd993274ad31616 (patch) | |
tree | e70d292fedf9a512b07cb7dc80c14ea81cf123ab /docs/libcurl/curl_multi_timeout.3 | |
parent | f907faec790f6bb5dc46102f1efa7e0faeef99ee (diff) | |
download | curl-bagder/less-very.tar.gz |
docs: reduce use of "very"bagder/less-very
"Very" should be avoided in most texts. If intensifiers are needed, try
find better words instead.
Diffstat (limited to 'docs/libcurl/curl_multi_timeout.3')
-rw-r--r-- | docs/libcurl/curl_multi_timeout.3 | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/libcurl/curl_multi_timeout.3 b/docs/libcurl/curl_multi_timeout.3 index 4f169332c..125738783 100644 --- a/docs/libcurl/curl_multi_timeout.3 +++ b/docs/libcurl/curl_multi_timeout.3 @@ -38,9 +38,8 @@ to CURL_SOCKET_TIMEOUT, or call \fIcurl_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 -immediately without waiting for anything. If it returns -1, there's no timeout -at all set. +of milliseconds at this moment. If 0, it means you should proceed immediately +without waiting for anything. If it returns -1, there's no timeout at all set. An application that uses the multi_socket API SHOULD NOT use this function, but SHOULD instead use \fIcurl_multi_setopt(3)\fP and its |