docs: Fix various typos in documentation

Closes #6171
Reviewed-by: Daniel Stenberg <daniel@haxx.se>

diff --git a/docs/FAQ b/docs/FAQ
index 7881d6c4e247094542d0949acf64cee4370c5a16..c4f2d53ff9d9e2aeaed1190a7cf3f5b1df8334d7 100644 (file)
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -318,7 +318,7 @@ FAQ
   We don't know how many users that downloaded or installed curl and then
   never use it.
 
-  In 2020, we estimate that curl runs in rougly ten billion installations
+  In 2020, we estimate that curl runs in roughly ten billion installations
   world wide.
 
   1.11 Why don't you update ca-bundle.crt

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index cfc68ac8333d3294b58e212f9513cf0a1c440d38..4284f23a457ee2850e9a612a2afff059cf55e6bf 100644 (file)
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -110,7 +110,7 @@ problems may have been fixed or changed somewhat since this was written!
  11.9 DoH doesn't inherit all transfer options
  11.10 Blocking socket operations in non-blocking API
  11.11 A shared connection cache is not thread-safe
- 11.12 'no_proxy' string-matches IPv6 numerical addreses
+ 11.12 'no_proxy' string-matches IPv6 numerical addresses
 
  12. LDAP and OpenLDAP
  12.1 OpenLDAP hangs after returning results
@@ -789,7 +789,7 @@ problems may have been fixed or changed somewhat since this was written!
 
  See https://github.com/curl/curl/issues/4915 and lib1541.c
 
-11.12 'no_proxy' string-matches IPv6 numerical addreses
+11.12 'no_proxy' string-matches IPv6 numerical addresses
 
  This has the downside that "::1" for example doesn't match "::0:1" even
  though they are in fact the same address.

diff --git a/docs/TheArtOfHttpScripting.md b/docs/TheArtOfHttpScripting.md
index fcec0de0c98e3ba206b18c7a8d04d61ae261fb05..21a50f3650ee41cb93a102933f27ebd119feee3f 100644 (file)
--- a/docs/TheArtOfHttpScripting.md
+++ b/docs/TheArtOfHttpScripting.md
@@ -11,7 +11,7 @@
 
  Curl is a command line tool for doing all sorts of URL manipulations and
  transfers, but this particular document will focus on how to use it when
- doing HTTP requests for fun and profit. I willl assume that you know how to
+ doing HTTP requests for fun and profit. I will assume that you know how to
  invoke `curl --help` or `curl --manual` to get basic information about it.
 
  Curl is not written to do everything for you. It makes the requests, it gets

diff --git a/docs/cmdline-opts/header.d b/docs/cmdline-opts/header.d
index 99248ce80fb40e590f1b69f34a6ef1794e8f5492..980467d5b0c5cd8cb34e8170be92e26fc238a067 100644 (file)
--- a/docs/cmdline-opts/header.d
+++ b/docs/cmdline-opts/header.d
@@ -30,7 +30,7 @@ You need --proxy-header to send custom headers intended for a HTTP
 proxy. Added in 7.37.0.
 
 Passing on a "Transfer-Encoding: chunked" header when doing a HTTP request
-with a requst body, will make curl send the data using chunked encoding.
+with a request body, will make curl send the data using chunked encoding.
 
 Example:
 

diff --git a/docs/cmdline-opts/page-header b/docs/cmdline-opts/page-header
index 91b0becf81fb435a9bd8ce0bb867134009403478..dcc299f73f193a582ad9b042b63c948143de4ce1 100644 (file)
--- a/docs/cmdline-opts/page-header
+++ b/docs/cmdline-opts/page-header
@@ -106,7 +106,7 @@ instructed to instead save that data into a local file, using the --output or
 command line, it similarly needs multiple options for where to save them.
 
 curl does not parse or otherwise "understand" the content it gets or writes as
-output. It does no encoding or decoding, unless explictly asked so with
+output. It does no encoding or decoding, unless explicitly asked so with
 dedicated command line options.
 .SH PROTOCOLS
 curl supports numerous protocols, or put in URL terms: schemes. Your