mirror of
https://github.com/curl/curl.git
synced 2026-04-14 22:21:41 +03:00
docs: reduce/avoid English contractions
You're => You are Hasn't => Has not Doesn't => Does not Don't => Do not You'll => You will etc Closes #7930
This commit is contained in:
parent
d3d079c138
commit
a28464ae77
265 changed files with 926 additions and 925 deletions
|
|
@ -101,7 +101,7 @@ int main(void)
|
|||
* than smtp:// to request a SSL based connection. */
|
||||
curl_easy_setopt(curl, CURLOPT_URL, "smtps://mainserver.example.net");
|
||||
|
||||
/* If you want to connect to a site who isn't using a certificate that is
|
||||
/* If you want to connect to a site who is not using a certificate that is
|
||||
* signed by one of the certs in the CA bundle you have, you can skip the
|
||||
* verification of the server's certificate. This makes the connection
|
||||
* A LOT LESS SECURE.
|
||||
|
|
@ -113,7 +113,7 @@ int main(void)
|
|||
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0L);
|
||||
#endif
|
||||
|
||||
/* If the site you're connecting to uses a different host name that what
|
||||
/* If the site you are connecting to uses a different host name that what
|
||||
* they have mentioned in their server certificate's commonName (or
|
||||
* subjectAltName) fields, libcurl will refuse to connect. You can skip
|
||||
* this check, but this will make the connection less secure. */
|
||||
|
|
@ -121,7 +121,7 @@ int main(void)
|
|||
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0L);
|
||||
#endif
|
||||
|
||||
/* Note that this option isn't strictly required, omitting it will result
|
||||
/* Note that this option is not strictly required, omitting it will result
|
||||
* in libcurl sending the MAIL FROM command with empty sender data. All
|
||||
* autoresponses should have an empty reverse-path, and should be directed
|
||||
* to the address in the reverse-path which triggered them. Otherwise,
|
||||
|
|
@ -137,7 +137,7 @@ int main(void)
|
|||
recipients = curl_slist_append(recipients, CC_MAIL);
|
||||
curl_easy_setopt(curl, CURLOPT_MAIL_RCPT, recipients);
|
||||
|
||||
/* We're using a callback function to specify the payload (the headers and
|
||||
/* We are using a callback function to specify the payload (the headers and
|
||||
* body of the message). You could just use the CURLOPT_READDATA option to
|
||||
* specify a FILE pointer to read from. */
|
||||
curl_easy_setopt(curl, CURLOPT_READFUNCTION, payload_source);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue