tidy-up: typos, comment nits

Closes #22294

docs/INFRASTRUCTURE.md

@@ -191,7 +191,7 @@ chat about curl and related topics. This done in the `#curl` channel on the
 `libra.chat` IRC network. **Daniel Stenberg** (`bagder`) is registered owner
 of the channel. We do not run any IRC servers or services ourselves.
 
-`curelbot` is a service in the channel that shows details about GitHub issues
+`curlbot` is a service in the channel that shows details about GitHub issues
 and pull requests when publicly mentioned using #[number]. The bot is run by
 user `TheAssassin`.
 

docs/TODO.md

@@ -57,7 +57,7 @@ to share data in more powerful ways.
 ## updated DNS server while running
 
 If `/etc/resolv.conf` gets updated while a program using libcurl is running, it
-is may cause name resolves to fail unless `res_init()` is called. We should
+may cause name resolves to fail unless `res_init()` is called. We should
 consider calling `res_init()` + retry once unconditionally on all name resolve
 failures to mitigate against this. Firefox works like that. Note that Windows
 does not have `res_init()` or an alternative.
@@ -269,7 +269,7 @@ This is not detailed in any FTP specification.
 
 ## Passive transfer could try other IP addresses
 
-When doing FTP operations through a proxy at localhost, the reported spotted
+When doing FTP operations through a proxy at localhost, the reporter spotted
 that curl only tried to connect once to the proxy, while it had multiple
 addresses and a failed connect on one address should make it try the next.
 
@@ -284,8 +284,8 @@ See [curl issue 1508](https://github.com/curl/curl/issues/1508)
 
 When curl receives a body response from a CONNECT request to a proxy, it
 always reads and ignores it. It would make some users happy if curl instead
-optionally would be able to make that responsible available. Via a new
-callback? Through some other means?
+optionally would be able to make that response available. Via a new callback?
+Through some other means?
 
 See [curl issue 9513](https://github.com/curl/curl/issues/9513)
 
@@ -763,7 +763,7 @@ backed up from those that are either not ready or have not changed.
 
 Downloads in progress are neither ready to be backed up, nor should they be
 opened by a different process. Only after a download has been completed it is
-sensible to include it in any integer snapshot or backup of the system.
+sensible to include it in any incremental snapshot or backup of the system.
 
 See [curl issue 3354](https://github.com/curl/curl/issues/3354)
 
@@ -825,7 +825,7 @@ one, which then could make curl decide to rather retry the transfer on that
 URL only instead of the original operation to the original URL.
 
 Perhaps extra emphasized if the original transfer is a large POST that
-redirects to a separate GET, and that GET is what gets the 529
+redirects to a separate GET, and that GET is what gets the 429
 
 See [curl issue 5462](https://github.com/curl/curl/issues/5462)
 

docs/VULN-DISCLOSURE-POLICY.md

@@ -363,7 +363,7 @@ A *legacy dependency* is here defined as:
 - there are modern versions of equivalent or better functionality offered and
   in common use
 
-## weak algorithms required for functionality
+## Weak algorithms required for functionality
 
 curl supports several algorithms that are considered weak, like DES and MD5.
 These algorithms are still not curl security vulnerabilities or security

docs/cmdline-opts/MANPAGE.md

@@ -114,12 +114,12 @@ During rendering, the generator expands them as follows:
 
 ## Generate
 
-`managen mainpage [list of markdown option file names]`
+`managen mainpage [list of markdown option filenames]`
 
 This command outputs a single huge nroff file, meant to become `curl.1`. The
 full curl man page.
 
-`managen ascii [list of markdown option file names]`
+`managen ascii [list of markdown option filenames]`
 
 This command outputs a single text file, meant to become `curl.txt`. The full
 curl man page in text format, used to build `tool_hugehelp.c`.

docs/internals/CREDENTIALS.md

@@ -12,7 +12,7 @@ Authorization credentials are kept in `struct Curl_creds`. This contains:
 * `passwd`: the password, maybe the empty string
 * `sasl_authzid`: the SASL `authz` value, maybe the empty string
 * `oauth_bearer`: the OAUTH bearer token, maybe the empty string
-* `source`: where the credentials from
+* `source`: where the credentials come from
 * `refcount`: a reference counter to link/unlink `creds`
 
 With reference counting, `creds` can be linked in several places.
@@ -54,12 +54,12 @@ password and `netrc` is consulted as well (when built in).
 ### `conn->creds`
 
 Once `data->state.creds` is known, the connection credentials are
-determined. For protocols that tie authorization to everything send
+determined. For protocols that tie authorization to everything sent
 on a connection (protocols without flag `PROTOPT_CREDSPERREQUEST`),
 `conn->creds` is linked to `data->state.creds`. Only connections
 carrying the same credentials may be reused.
 
-Protocol with flag `PROTOPT_CREDSPERREQUEST` leave `conn->creds` empty,
+Protocols with flag `PROTOPT_CREDSPERREQUEST` leave `conn->creds` empty,
 as connections for such protocols may be reused with different
 credentials.
 

docs/tests/FILEFORMAT.md

@@ -421,7 +421,7 @@ issue.
 
 Commands for the test DNS server.
 
-- `A: [dotted ipv4 address]` - set IPv4 address to return
+- `A: [dotted IPv4 address]` - set IPv4 address to return
 - `AAAA: [numerical IPv6 address]` - set IPv6 address to return, with or
   without `[]`