aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2014-10-24 09:16:06 +0200
committerDaniel Stenberg <daniel@haxx.se>2014-10-24 09:16:06 +0200
commit019c95f566a42570836866837da2f3a0fba58733 (patch)
tree85373b5e4a97b4ced81ee110b6d0d3a863f996ac
parent40be9a1c1deea8d7f23a7ff5508fb4b3baa8fed5 (diff)
curl_easy_pause.3: minor wording edit
-rw-r--r--docs/libcurl/curl_easy_pause.35
1 files changed, 2 insertions, 3 deletions
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.