From be527afad05aeb8177de111f0fbd282c2983ce9d Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 4 Jun 2019 20:25:39 +0200 Subject: curl_share_setopt.3: improve wording [ci ship] Reported-by: Carlos ORyan --- docs/libcurl/curl_share_setopt.3 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/libcurl/curl_share_setopt.3 b/docs/libcurl/curl_share_setopt.3 index 6c209eb00..12ee4b0dc 100644 --- a/docs/libcurl/curl_share_setopt.3 +++ b/docs/libcurl/curl_share_setopt.3 @@ -5,7 +5,7 @@ .\" * | (__| |_| | _ <| |___ .\" * \___|\___/|_| \_\_____| .\" * -.\" * Copyright (C) 1998 - 2018, Daniel Stenberg, , et al. +.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, , et al. .\" * .\" * This software is licensed as described in the file COPYING, which .\" * you should have received as part of this distribution. The terms @@ -37,8 +37,8 @@ prototype: void lock_function(CURL *handle, curl_lock_data data, curl_lock_access access, void *userptr); -\fIdata\fP defines what data libcurl wants to lock, and you must make sure that -only one lock is given at any time for each kind of data. +The \fIdata\fP argument tells what kind of data libcurl wants to lock. Make +sure that the callback uses a different lock for each kind of data. \fIaccess\fP defines what access type libcurl wants, shared or single. -- cgit v1.2.1