9a674ee6f7
dbalsom
2026-03-07
Subject
docs: replace instances of the vague qualifier 'quite'
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/CONTRIBUTE.md +1 -1docs/FAQ.md +2 -2docs/HISTORY.md +3 -2docs/internals/CHECKSRC.md +5 -5docs/libcurl/libcurl-tutorial.md +9 -9lib/asyn-ares.c +1 -1lib/multi.c +1 -1
docs/CONTRIBUTE.md+1 -1
| @@ -102,7 +102,7 @@ and regression in the future. | |
| Please try to get the latest available sources to make your patches against. | |
| It makes the lives of the developers so much easier. The best is if you get | |
| the most up-to-date sources from the git repository, but the latest release | |
| - | archive is quite OK as well. |
| + | archive is OK as well. |
| ### Documentation | |
docs/FAQ.md+2 -2
| @@ -562,8 +562,8 @@ the first path part. List the `/tmp` directory like this: | |
| curl ftp://ftp.example.com/%2ftmp/ | |
| - | or the not-quite-kosher-but-more-readable way, by simply starting the path |
| - | section of the URL with a slash: |
| + | The second way is non-standard but more readable; start the path section of the |
| + | URL with a slash: |
| curl ftp://ftp.example.com//tmp/ | |
docs/HISTORY.md+3 -2
| @@ -67,8 +67,9 @@ code, we switched over to the MPL license to restrict the effects of | |
| "copyleft". | |
| November: configure script and reported successful compiles on several | |
| - | major operating systems. The never-quite-understood -F option was added and |
| - | curl could now simulate quite a lot of a browser. TELNET support was added. |
| + | major operating systems. The often-misunderstood -F option was added, and |
| + | curl could now simulate significant browser functionality. TELNET support was |
| + | added. |
| curl 5 was released in December 1998 and introduced the first ever curl man | |
| page. People started making Linux RPM packages out of it. | |
docs/internals/CHECKSRC.md+5 -5
| @@ -131,11 +131,11 @@ warnings are: | |
| ### Extended warnings | |
| - | Some warnings are quite computationally expensive to perform, so they are |
| - | turned off by default. To enable these warnings, place a `.checksrc` file in |
| - | the directory where they should be activated with commands to enable the |
| - | warnings you are interested in. The format of the file is to enable one |
| - | warning per line like so: `enable <EXTENDEDWARNING>` |
| + | Some warnings are computationally expensive to perform, so they are turned off |
| + | by default. To enable these warnings, place a `.checksrc` file in the directory |
| + | where they should be activated with commands to enable the warnings you are |
| + | interested in. The format of the file is to enable one warning per line like |
| + | so: `enable <EXTENDEDWARNING>` |
| Currently these are the extended warnings which can be enabled: | |
docs/libcurl/libcurl-tutorial.md+9 -9
| @@ -291,11 +291,11 @@ a better understanding why the server behaves the way it does. Include headers | |
| in the normal body output with CURLOPT_HEADER(3) set 1. | |
| Of course, there are bugs left. We need to know about them to be able to fix | |
| - | them, so we are quite dependent on your bug reports. When you do report |
| - | suspected bugs in libcurl, please include as many details as you possibly can: |
| - | a protocol dump that CURLOPT_VERBOSE(3) produces, library version, as |
| - | much as possible of your code that uses libcurl, operating system name and |
| - | version, compiler name and version etc. |
| + | them, so we are dependent on your bug reports. When you do report suspected |
| + | bugs in libcurl, please include as many details as you possibly can: a protocol |
| + | dump that CURLOPT_VERBOSE(3) produces, library version, as much as possible of |
| + | your code that uses libcurl, operating system name and version, compiler name |
| + | and version etc. |
| If CURLOPT_VERBOSE(3) is not enough, you increase the level of debug | |
| data your application receive by using the CURLOPT_DEBUGFUNCTION(3). | |
| @@ -377,8 +377,8 @@ char * to a string in the format "user:password". In a manner like this: | |
| Another case where name and password might be needed at times, is for those | |
| users who need to authenticate themselves to a proxy they use. libcurl offers | |
| - | another option for this, the CURLOPT_PROXYUSERPWD(3). It is used quite similar |
| - | to the CURLOPT_USERPWD(3) option like this: |
| + | another option for this, the CURLOPT_PROXYUSERPWD(3). Its use is similar to the |
| + | CURLOPT_USERPWD(3) option, like this: |
| ~~~c | |
| curl_easy_setopt(handle, CURLOPT_PROXYUSERPWD, "myname:thesecret"); | |
| @@ -826,8 +826,8 @@ libcurl supports SOCKS and HTTP proxies. When a given URL is wanted, libcurl | |
| asks the proxy for it instead of trying to connect to the actual remote host | |
| identified in the URL. | |
| - | If you are using a SOCKS proxy, you may find that libcurl does not quite support |
| - | all operations through it. |
| + | If you are using a SOCKS proxy, you may find that libcurl does not support all |
| + | operations through it. |
| For HTTP proxies: the fact that the proxy is an HTTP proxy puts certain | |
| restrictions on what can actually happen. A requested URL that might not be a | |
lib/asyn-ares.c+1 -1
| @@ -559,7 +559,7 @@ static void async_ares_hostbyname_cb(void *user_data, | |
| request came back quickly, that need not be the case. It might be that | |
| this completing request did not get a result from the first DNS | |
| server or even the first round of the whole DNS server pool. So it | |
| - | could already be quite some time after we issued the DNS queries in |
| + | could already be a long time after we issued the DNS queries in |
| the first place. Without modifying c-ares, we cannot know exactly | |
| where in its retry cycle we are. We could guess based on how much | |
| time has gone by, but it does not really matter. Happy Eyeballs tells | |
lib/multi.c+1 -1
| @@ -375,7 +375,7 @@ static CURLMcode multi_xfers_add(struct Curl_multi *multi, | |
| if(capacity < max_capacity) { | |
| /* We want `multi->xfers` to have "sufficient" free rows, so that we do | |
| * have to reuse the `mid` from a removed easy right away. | |
| - | * Since uint_tbl and uint_bset are quite memory efficient, |
| + | * Since uint_tbl and uint_bset are memory efficient, |
| * regard less than 25% free as insufficient. | |
| * (for low capacities, e.g. multi_easy, 4 or less). */ | |
| uint32_t used = Curl_uint32_tbl_count(&multi->xfers); | |