fix some typos in the doc (#1306)
diff --git a/docs/BUGS b/docs/BUGS
index 8cabbd2..2936c54 100644
--- a/docs/BUGS
+++ b/docs/BUGS
@@ -210,7 +210,7 @@
This is a list of known bugs. Bugs we know exist and that have been pointed
out but that haven't yet been fixed. The reasons for why they haven't been
fixed can involve anything really, but the primary reason is that nobody has
- considered these problems to be important enough to spend the necesary time
+ considered these problems to be important enough to spend the necessary time
and effort to have them fixed.
The KNOWN_BUGS are always up for grabs and we will always love the ones who
@@ -238,7 +238,7 @@
2.8 Closing off stalled bugs
The issue and pull request trackers on https://github.com/curl/curl will
- only hold "active" entries (using a non-precise defintion of what active
+ only hold "active" entries (using a non-precise definition of what active
actually is, but they're at least not completely dead). Those that are
abandonded or in other ways dormant will be closed and sometimes added to
TODO and KNOWN_BUGS instead.
diff --git a/docs/FAQ b/docs/FAQ
index f8cb644..d1a8a1f 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -602,7 +602,7 @@
In October 2009, there were interfaces available for the following
languages: Ada95, Basic, C, C++, Ch, Cocoa, D, Dylan, Eiffel, Euphoria,
Ferite, Gambas, glib/GTK+, Haskell, ILE/RPG, Java, Lisp, Lua, Mono, .NET,
- Object-Pascal, O'Caml, Pascal, Perl, PHP, PostgreSQL, Python, R, Rexx, Ruby,
+ Object-Pascal, OCaml, Pascal, Perl, PHP, PostgreSQL, Python, R, Rexx, Ruby,
Scheme, S-Lang, Smalltalk, SP-Forth, SPL, Tcl, Visual Basic, Visual FoxPro,
Q, wxwidgets and XBLite. By the time you read this, additional ones may have
appeared!
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 12eeedd..5974821 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -184,7 +184,7 @@
It can also be noted that while adding a trailing dot to the host name in
most (all?) cases will make the name resolve to the same set of IP addresses,
many HTTP servers will not happily accept the trailing dot there unless that
- has been specificly configured to be a fine virtual host.
+ has been specifically configured to be a fine virtual host.
If URLs with trailing dots for host names become more popular or even just
used more than for just plain fun experiments, I'm sure we will have reason
diff --git a/docs/TODO b/docs/TODO
index 15c1b27..158d3c3 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -25,7 +25,7 @@
1.7 Detect when called from within callbacks
1.8 CURLOPT_RESOLVE for any port number
1.9 Cache negative name resolves
- 1.11 minimize dependencies with dynamicly loaded modules
+ 1.11 minimize dependencies with dynamically loaded modules
1.12 have form functions use CURL handle argument
1.14 Typesafe curl_easy_setopt()
1.15 Monitor connections in the connection pool
@@ -259,7 +259,7 @@
A name resolve that has failed is likely to fail when made again within a
short period of time. Currently we only cache positive responses.
-1.11 minimize dependencies with dynamicly loaded modules
+1.11 minimize dependencies with dynamically loaded modules
We can create a system with loadable modules/plug-ins, where these modules
would be the ones that link to 3rd party libs. That would allow us to avoid
@@ -531,7 +531,7 @@
RFC 7616 introduces an update to the HTTP Digest authentication
specification, which amongst other thing defines how new digest algorithms
- can be used instead of MD5 which is considered old and not recommanded.
+ can be used instead of MD5 which is considered old and not recommended.
See https://tools.ietf.org/html/rfc7616 and
https://github.com/curl/curl/issues/1018
@@ -1046,9 +1046,9 @@
18.15 --retry should resume
When --retry is used and curl actually retries transfer, it should use the
- already transfered data and do a resumed transfer for the rest (when
+ already transferred data and do a resumed transfer for the rest (when
possible) so that it doesn't have to transfer the same data again that was
- already tranfered before the retry.
+ already transferred before the retry.
See https://github.com/curl/curl/issues/1084
diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3
index 3144da3..cbfb081 100644
--- a/docs/libcurl/libcurl-tutorial.3
+++ b/docs/libcurl/libcurl-tutorial.3
@@ -1147,7 +1147,7 @@
.IP "IPv6 Addresses"
libcurl will normally handle IPv6 addresses transparently and just as easily
as IPv4 addresses. That means that a sanitizing function that filters out
-addressses like 127.0.0.1 isn't sufficient--the equivalent IPv6 addresses ::1,
+addresses like 127.0.0.1 isn't sufficient--the equivalent IPv6 addresses ::1,
::, 0:00::0:1, ::127.0.0.1 and ::ffff:7f00:1 supplied somehow by an attacker
would all bypass a naive filter and could allow access to undesired local
resources. IPv6 also has special address blocks like link-local and site-local
