code: language cleanup in comments

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

View file

@ -582,7 +582,7 @@ void ourWriteOut(struct OperationConfig *config, struct per_transfer *per,
switch(wv->id) {
case VAR_ONERROR:
if(per_result == CURLE_OK)
/* this isn't error so skip the rest */
/* this is not error so skip the rest */
done = TRUE;
break;
case VAR_STDOUT:
@ -645,7 +645,7 @@ void ourWriteOut(struct OperationConfig *config, struct per_transfer *per,
}
end = strchr(ptr, '}');
if(end) {
char fname[512]; /* holds the longest file name */
char fname[512]; /* holds the longest filename */
size_t flen = end - ptr;
if(flen < sizeof(fname)) {
FILE *stream2;