From 019c95f566a42570836866837da2f3a0fba58733 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 24 Oct 2014 09:16:06 +0200 Subject: curl_easy_pause.3: minor wording edit --- docs/libcurl/curl_easy_pause.3 | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'docs/libcurl/curl_easy_pause.3') diff --git a/docs/libcurl/curl_easy_pause.3 b/docs/libcurl/curl_easy_pause.3 index d8412957a..0f6ad5a32 100644 --- a/docs/libcurl/curl_easy_pause.3 +++ b/docs/libcurl/curl_easy_pause.3 @@ -40,9 +40,8 @@ the writing is later unpaused. While it may feel tempting, take care and notice that you cannot call this function from another thread. To unpause, you may for example call it from the -progress callback (see \fIcurl_easy_setopt(3)\fP's -\fICURLOPT_PROGRESSFUNCTION(3)\fP), which gets called at least once per -second, even if the connection is paused. +progress callback (\fICURLOPT_PROGRESSFUNCTION(3)\fP), which gets called at +least once per second, even if the connection is paused. When this function is called to unpause reading, the chance is high that you will get your write callback called before this function returns. -- cgit v1.2.3