I finally finished going over all the man pages. some fixes are typos,
others are changes that need review, in case I have changed the
meaning of a sentence.

there were also a few places I had questions that I'd like input on. I
put the text, the my comment/question after it.

from curl_easy_setopt

Note the CURLOPT_
USERNAME option is an alternative way to set the user name. There is
no meaning to use
it together with the CURLOPT_USERPWD option.

what does this 2nd sentence mean?

Note that libcurl will still act and assume the keyword it would use
if you didn't set your custom
one is the one in use and it will act according to that.

a better way to phrase this?

but colons are normally used, \!, \- and \+ can be used as operators.

shows up in the PDF as
but colons are normally used, , $B!](Band + can be used as operators.

CURLOPT_KRBLEVEL
Pass a char * as parameter. Set the kerberos security level for FTP;
this also enables kerberos
awareness. This is a string, 'clear', 'safe', of these, 'private' will be used.

I don't understand the last sentence...should it be:
This is a string. 'clear', 'safe', or 'private' can be used.

You can control what data your function get in the forth argument by
setting another property:
curl_easy_setopt(easyhandle, CURLOPT_WRITEDATA, &internal_struct);

is this a typo of 'fourth' or do you mean "...in the following
argument ? also, should be "...function gets..."

         Unfortunately, c-ares does not yet fully support IPv6. On
some platforms, libcurl simply will not
function properly multi-threaded unless this option is set.

is that still accurate? from the c-ares page it seems to suggest IPv6
support, but maybe not fully supported?

Set header file to read cookies from
with CURLOPT_COOKIEFILE.

Set the header file to read cookies from
with CURLOPT_COOKIEFILE.
?

Note that the file you specify to CURLOPT_
COOKIEFILE doesn't have to exist to enable the parser, so a common way
to just enable the parser
and not read able might be to use a file name you know doesn't exist.

I don't understand the end - "and not read able might be to use a file
name you know doesn't exist."

HTTP Digest authentication allows this too, but isn't supported
by libcurl as of this writing.

does libcurl now support digest? if yes, should this be removed?

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads

-------------------------------------------------------------------
List admin: http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html