docs: rewrite to present tense

... instead of using future tense.

+ numerous cleanups and improvements
+ stick to "reuse" not "re-use"
+ fewer contractions

Closes #11713

docs/examples/Makefile.example

@@ -34,7 +34,7 @@ CC = gcc
 # Compiler flags, -g for debug, -c to make an object file
 CFLAGS = -c -g
 
-# This should point to a directory that holds libcurl, if it isn't
+# This should point to a directory that holds libcurl, if it is not
 # in the system's standard lib dir
 # We also set a -L to include the directory where we have the openssl
 # libraries

docs/examples/Makefile.inc

@@ -129,7 +129,7 @@ check_PROGRAMS = \
   websocket-cb
 
 # These examples require external dependencies that may not be commonly
-# available on POSIX systems, so don't bother attempting to compile them here.
+# available on POSIX systems, so do not bother attempting to compile them here.
 COMPLICATED_EXAMPLES = \
   cacertinmem.c \
   crawler.c \

docs/examples/anyauthput.c

@@ -60,7 +60,7 @@ static int my_seek(void *userp, curl_off_t offset, int origin)
   FILE *fp = (FILE *) userp;
 
   if(-1 == fseek(fp, (long) offset, origin))
-    /* couldn't seek */
+    /* could not seek */
     return CURL_SEEKFUNC_CANTSEEK;
 
   return CURL_SEEKFUNC_OK; /* success! */

docs/examples/ftpget.c

@@ -66,7 +66,7 @@ int main(void)
      */
     curl_easy_setopt(curl, CURLOPT_URL,
                      "ftp://ftp.example.com/curl/curl-7.9.2.tar.gz");
-    /* Define our callback to get called when there's data to be written */
+    /* Define our callback to get called when there is data to be written */
     curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, my_fwrite);
     /* Set a pointer to our struct to pass to the callback */
     curl_easy_setopt(curl, CURLOPT_WRITEDATA, &ftpfile);

docs/examples/ftpsget.c

@@ -70,7 +70,7 @@ int main(void)
      */
     curl_easy_setopt(curl, CURLOPT_URL,
                      "ftp://user@server/home/user/file.txt");
-    /* Define our callback to get called when there's data to be written */
+    /* Define our callback to get called when there is data to be written */
     curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, my_fwrite);
     /* Set a pointer to our struct to pass to the callback */
     curl_easy_setopt(curl, CURLOPT_WRITEDATA, &ftpfile);

docs/examples/http2-pushinmemory.c

@@ -92,7 +92,7 @@ static void setup(CURL *hnd)
   curl_easy_setopt(hnd, CURLOPT_PIPEWAIT, 1L);
 }
 
-/* called when there's an incoming push */
+/* called when there is an incoming push */
 static int server_push_callback(CURL *parent,
                                 CURL *easy,
                                 size_t num_headers,

docs/examples/http2-serverpush.c

@@ -161,7 +161,7 @@ static int setup(CURL *hnd, const char *url)
   return 0; /* all is good */
 }
 
-/* called when there's an incoming push */
+/* called when there is an incoming push */
 static int server_push_callback(CURL *parent,
                                 CURL *easy,
                                 size_t num_headers,

docs/examples/persistent.c

@@ -22,7 +22,7 @@
  *
  ***************************************************************************/
 /* <DESC>
- * re-using handles to do HTTP persistent connections
+ * reusing handles to do HTTP persistent connections
  * </DESC>
  */
 #include <stdio.h>

docs/examples/sftpget.c

@@ -77,7 +77,7 @@ int main(void)
      */
     curl_easy_setopt(curl, CURLOPT_URL,
                      "sftp://user@server/home/user/file.txt");
-    /* Define our callback to get called when there's data to be written */
+    /* Define our callback to get called when there is data to be written */
     curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, my_fwrite);
     /* Set a pointer to our struct to pass to the callback */
     curl_easy_setopt(curl, CURLOPT_WRITEDATA, &ftpfile);

docs/examples/smtp-authzid.c

@@ -148,7 +148,7 @@ int main(void)
     curl_slist_free_all(recipients);
 
     /* curl will not send the QUIT command until you call cleanup, so you
-     * should be able to re-use this connection for additional messages
+     * should be able to reuse this connection for additional messages
      * (setting CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and
      * calling curl_easy_perform() again. It may not be a good idea to keep
      * the connection open for a very long time though (more than a few

docs/examples/smtp-expn.c

@@ -69,7 +69,7 @@ int main(void)
     curl_slist_free_all(recipients);
 
     /* curl will not send the QUIT command until you call cleanup, so you
-     * should be able to re-use this connection for additional requests. It
+     * should be able to reuse this connection for additional requests. It
      * may not be a good idea to keep the connection open for a very long time
      * though (more than a few minutes may result in the server timing out the
      * connection) and you do want to clean up in the end.

docs/examples/smtp-mail.c

@@ -136,7 +136,7 @@ int main(void)
     curl_slist_free_all(recipients);
 
     /* curl will not send the QUIT command until you call cleanup, so you
-     * should be able to re-use this connection for additional messages
+     * should be able to reuse this connection for additional messages
      * (setting CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and
      * calling curl_easy_perform() again. It may not be a good idea to keep
      * the connection open for a very long time though (more than a few

docs/examples/smtp-mime.c

@@ -151,7 +151,7 @@ int main(void)
     curl_slist_free_all(headers);
 
     /* curl will not send the QUIT command until you call cleanup, so you
-     * should be able to re-use this connection for additional messages
+     * should be able to reuse this connection for additional messages
      * (setting CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and
      * calling curl_easy_perform() again. It may not be a good idea to keep
      * the connection open for a very long time though (more than a few

docs/examples/smtp-vrfy.c

@@ -69,7 +69,7 @@ int main(void)
     curl_slist_free_all(recipients);
 
     /* curl will not send the QUIT command until you call cleanup, so you
-     * should be able to re-use this connection for additional requests. It
+     * should be able to reuse this connection for additional requests. It
      * may not be a good idea to keep the connection open for a very long time
      * though (more than a few minutes may result in the server timing out the
      * connection) and you do want to clean up in the end.