From: Daniel Stenberg <daniel@haxx.se>
Date: Thu, 2 Dec 2021 11:05:48 +0000 (+0100)
Subject: CURLMOPT_TIMERFUNCTION.3: call it expire time, not interval
X-Git-Tag: curl-7_81_0~114
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c8a3046555378f81b22d51e3887df8a5cf1ab5bf;p=thirdparty%2Fcurl.git

CURLMOPT_TIMERFUNCTION.3: call it expire time, not interval

Since we say it is a non-repating timer
---

diff --git a/docs/libcurl/opts/CURLMOPT_TIMERFUNCTION.3 b/docs/libcurl/opts/CURLMOPT_TIMERFUNCTION.3
index cacc23548d..bea24e293b 100644
--- a/docs/libcurl/opts/CURLMOPT_TIMERFUNCTION.3
+++ b/docs/libcurl/opts/CURLMOPT_TIMERFUNCTION.3
@@ -40,9 +40,9 @@ Certain features, such as timeouts and retries, require you to call libcurl
 even when there is no activity on the file descriptors.
 
 Your callback function \fBtimer_callback\fP should install a non-repeating
-timer with an interval of \fBtimeout_ms\fP. When that timer fires, call
-either \fIcurl_multi_socket_action(3)\fP or \fIcurl_multi_perform(3)\fP,
-depending on which interface you use.
+timer with an expire time of \fBtimeout_ms\fP milliseconds. When that timer
+fires, call either \fIcurl_multi_socket_action(3)\fP or
+\fIcurl_multi_perform(3)\fP, depending on which interface you use.
 
 A \fBtimeout_ms\fP value of -1 passed to this callback means you should delete
 the timer. All other values are valid expire times in number of milliseconds.