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

misc: Fix typos in docs and lib

Browse source 
This fixes miscellaneous typos and duplicated words in the docs, lib
and test comments and a few user facing errorstrings.

Author: RainRat on Github
Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
Reviewed-by: Dan Fandrich <dan@coneharvesters.com>
Closes: #13019
This commit is contained in:
RainRat 2024-02-29 11:55:28 -08:00 • committed by Daniel Gustafsson
parent 89733e2dd2
commit 2cd78f525c
26 changed files with 26 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/CONNECTION-FILTERS.md
View file

@ -267,7 +267,7 @@ conn[curl.se] --> SETUP[TCP] --> HAPPY-EYEBALLS --> TCP[2a04:4e42:c00::347]:443
The modular design of connection filters and that we can plug them into each other is used to control the parallel attempts. When a `TCP` filter does not connect (in time), it is torn down and another one is created for the next address. This keeps the `TCP` filter simple.
The `HAPPY-EYEBALLS` on the other hand stays focused on its side of the problem. We can use it also to make other type of connection by just giving it another filter type to try and have happy eyeballing for QUIC:
The `HAPPY-EYEBALLS` on the other hand stays focused on its side of the problem. We can use it also to make other type of connection by just giving it another filter type to try to have happy eyeballing for QUIC:
```
* create connection for --http3-only https://curl.se

2
docs/cmdline-opts/MANPAGE.md
View file

@ -88,7 +88,7 @@ Angle brackets (`<>`) need to be escaped when used in text like `\<` and
### Headers
The `#` header can be used by non-option files and it produces produces a
The `#` header can be used by non-option files and it produces a
`.SH` output.
If the `#` header is used for a command line option file, that header is

2
docs/cmdline-opts/_VARIABLES.md
View file

@ -41,4 +41,4 @@ as POST data:
--expand-data "{{fix:trim:url}}"
https://example.com/
Command line variables and expansions were added in in 8.3.0.
Command line variables and expansions were added in 8.3.0.

2
docs/cmdline-opts/gen.pl
View file

@ -897,7 +897,7 @@ HEADER
my $f = $_;
chomp $f;
if($f =~ /^#/) {
# stardard comment
# standard comment
next;
}
if(/^%options/) {

2
docs/cmdline-opts/resolve.md
View file

@ -43,4 +43,4 @@ Support for providing multiple IP addresses per entry was added in 7.59.0.
Support for resolving with wildcard was added in 7.64.0.
Support for the '+' prefix was was added in 7.75.0.
Support for the '+' prefix was added in 7.75.0.

2
docs/examples/ghiper.c
View file

@ -22,7 +22,7 @@
*
***************************************************************************/
/* <DESC>
* multi socket API usage together with with glib2
* multi socket API usage together with glib2
* </DESC>
*/
/* Example application source code using the multi socket interface to

2
docs/libcurl/libcurl.m4
View file

@ -169,7 +169,7 @@ AC_DEFUN([LIBCURL_CHECK_CONFIG],
LIBS="$LIBCURL $LIBS"
AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include <curl/curl.h>]],[[
/* Try and use a few common options to force a failure if we are
/* Try to use a few common options to force a failure if we are
missing symbols or cannot link. */
int x;
curl_easy_setopt(NULL,CURLOPT_URL,NULL);

2
docs/libcurl/opts/CURLOPT_DEBUGFUNCTION.md
View file

@ -73,7 +73,7 @@ The data is header (or header-like) data sent to the peer.
## CURLINFO_DATA_IN
The data is the unprocessed protocol data received from the peer. Even if the
data is encoded or compressed, it is not not provided decoded nor decompressed
data is encoded or compressed, it is not provided decoded nor decompressed
to this callback. If you need the data in decoded and decompressed form, use
CURLOPT_WRITEFUNCTION(3).

2
docs/libcurl/opts/CURLSHOPT_SHARE.md
View file

@ -27,7 +27,7 @@ CURLSHcode curl_share_setopt(CURLSH *share, CURLSHOPT_SHARE, long type);
The *type* parameter specifies what specific data that should be shared
and kept in the share object that was created with curl_share_init(3).
The given *type* must be be one of the values described below. You can set
The given *type* must be one of the values described below. You can set
CURLSHOPT_SHARE(3) multiple times with different data arguments to have
the share object share multiple types of data. Unset a type again by setting
CURLSHOPT_UNSHARE(3).

2
docs/libcurl/opts/CURLSHOPT_UNSHARE.md
View file

@ -28,7 +28,7 @@ CURLSHcode curl_share_setopt(CURLSH *share, CURLSHOPT_UNSHARE, long type);
The *type* parameter specifies what specific data that should no longer be
shared and kept in the share object that was created with
curl_share_init(3). In other words, stop sharing that data in this
shared object. The given *type* must be be one of the values described
shared object. The given *type* must be one of the values described
below. You can set CURLSHOPT_UNSHARE(3) multiple times with different
data arguments to remove multiple types from the shared object. Add data to
share again with CURLSHOPT_SHARE(3).