diff options
| author | Sylvestre Ledru <sledru@mozilla.com> | 2017-03-04 15:50:33 +0100 | 
|---|---|---|
| committer | Dan Fandrich <dan@coneharvesters.com> | 2017-03-04 15:50:33 +0100 | 
| commit | 658b9a200ae2b31dfe7ede957fb5aaa127386205 (patch) | |
| tree | 621b4fc473aba07da67289ae163b05f158e001b6 /docs/TODO | |
| parent | 97a04145efcfa7c6a3864e37aa58d1d69e1bbf69 (diff) | |
fix some typos in the doc (#1306)
Diffstat (limited to 'docs/TODO')
| -rw-r--r-- | docs/TODO | 10 | 
1 files changed, 5 insertions, 5 deletions
@@ -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 @@ This is not detailed in any FTP specification.   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 @@ that doesn't exist on the server, just like --ftp-create-dirs.  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  | 
