From: Daniel Stenberg <daniel@haxx.se>
Date: Fri, 24 Oct 2014 07:16:06 +0000 (+0200)
Subject: curl_easy_pause.3: minor wording edit
X-Git-Tag: curl-7_39_0~99
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=019c95f566a42570836866837da2f3a0fba58733;p=thirdparty%2Fcurl.git

curl_easy_pause.3: minor wording edit
---

diff --git a/docs/libcurl/curl_easy_pause.3 b/docs/libcurl/curl_easy_pause.3
index d8412957a9..0f6ad5a322 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.