romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-25 06:23:30 +03:00
Code Issues Projects Releases Packages Wiki Activity

docs: replace instances of the vague qualifier 'quite'

Browse source 
in documentation and comments

Closes #20841
This commit is contained in:
dbalsom 2026-03-06 12:58:44 -05:00 • committed by Daniel Stenberg
parent 13f48dfb52
commit 9a674ee6f7
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
7 changed files with 22 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/CONTRIBUTE.md
View file

@ -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

4
docs/FAQ.md
View file

@ -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/

5
docs/HISTORY.md
View file

@ -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.

10
docs/internals/CHECKSRC.md
View file

@ -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:

18
docs/libcurl/libcurl-tutorial.md
View file

@ -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