romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-24 22:23:58 +03:00
Code Issues Projects Releases Packages Wiki Activity

code: language cleanup in comments

Browse source 
Based on the standards and guidelines we use for our documentation.

 - expand contractions (they're => they are etc)
 - host name = > hostname
 - file name => filename
 - user name = username
 - man page => manpage
 - run-time => runtime
 - set-up => setup
 - back-end => backend
 - a HTTP => an HTTP
 - Two spaces after a period => one space after period

Closes #14073
This commit is contained in:
Daniel Stenberg 2024-07-01 16:47:21 +02:00
parent 9b683577e1
commit c074ba64a8
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
213 changed files with 1719 additions and 1715 deletions
Download patch file Download diff file Expand all files Collapse all files

37
lib/strerror.c
View file

@ -74,13 +74,13 @@ curl_easy_strerror(CURLcode error)
" this libcurl due to a build-time decision.";
case CURLE_COULDNT_RESOLVE_PROXY:
return "Couldn't resolve proxy name";
return "Could not resolve proxy name";
case CURLE_COULDNT_RESOLVE_HOST:
return "Couldn't resolve host name";
return "Could not resolve hostname";
case CURLE_COULDNT_CONNECT:
return "Couldn't connect to server";
return "Could not connect to server";
case CURLE_WEIRD_SERVER_REPLY:
return "Weird server reply";
@ -107,19 +107,19 @@ curl_easy_strerror(CURLcode error)
return "FTP: unknown 227 response format";
case CURLE_FTP_CANT_GET_HOST:
return "FTP: can't figure out the host in the PASV response";
return "FTP: cannot figure out the host in the PASV response";
case CURLE_HTTP2:
return "Error in the HTTP2 framing layer";
case CURLE_FTP_COULDNT_SET_TYPE:
return "FTP: couldn't set file type";
return "FTP: could not set file type";
case CURLE_PARTIAL_FILE:
return "Transferred a partial file";
case CURLE_FTP_COULDNT_RETR_FILE:
return "FTP: couldn't retrieve (RETR failed) the specified file";
return "FTP: could not retrieve (RETR failed) the specified file";
case CURLE_QUOTE_ERROR:
return "Quote command returned error";
@ -158,10 +158,10 @@ curl_easy_strerror(CURLcode error)
return "SSL connect error";
case CURLE_BAD_DOWNLOAD_RESUME:
return "Couldn't resume download";
return "Could not resume download";
case CURLE_FILE_COULDNT_READ_FILE:
return "Couldn't read a file:// file";
return "Could not read a file:// file";
case CURLE_LDAP_CANNOT_BIND:
return "LDAP: cannot bind";
@ -212,7 +212,7 @@ curl_easy_strerror(CURLcode error)
return "Problem with the local SSL certificate";
case CURLE_SSL_CIPHER:
return "Couldn't use specified SSL cipher";
return "Could not use specified SSL cipher";
case CURLE_PEER_FAILED_VERIFICATION:
return "SSL peer certificate or SSH remote key was not OK";
@ -345,16 +345,15 @@ curl_easy_strerror(CURLcode error)
/*
* By using a switch, gcc -Wall will complain about enum values
* which do not appear, helping keep this function up-to-date.
* By using gcc -Wall -Werror, you can't forget.
* By using gcc -Wall -Werror, you cannot forget.
*
* A table would not have the same benefit. Most compilers will
* generate code very similar to a table in any case, so there
* is little performance gain from a table. And something is broken
* for the user's application, anyways, so does it matter how fast
* it _doesn't_ work?
* A table would not have the same benefit. Most compilers will generate
* code very similar to a table in any case, so there is little performance
* gain from a table. Something is broken for the user's application,
* anyways, so does it matter how fast it _does not_ work?
*
* The line number for the error will be near this comment, which
* is why it is here, and not at the start of the switch.
* The line number for the error will be near this comment, which is why it
* is here, and not at the start of the switch.
*/
return "Unknown error";
#else
@ -823,9 +822,9 @@ get_winapi_error(int err, char *buf, size_t buflen)
* The 'err' argument passed in to this function MUST be a true errno number
* as reported on this system. We do no range checking on the number before
* we pass it to the "number-to-message" conversion function and there might
* be systems that don't do proper range checking in there themselves.
* be systems that do not do proper range checking in there themselves.
*
* We don't do range checking (on systems other than Windows) since there is
* We do not do range checking (on systems other than Windows) since there is
* no good reliable and portable way to do it.
*
* On Windows different types of error codes overlap. This function has an