earlier -> lower/older

docs/HTTP3.md

@@ -49,7 +49,7 @@ placeholders for the version you build.
 
 ## Build with OpenSSL or fork
 
-OpenSSL v3.5.0+ requires *ngtcp2* v1.12.0+. Earlier versions do not work.
+OpenSSL v3.5.0+ requires *ngtcp2* v1.12.0+. Lower versions do not work.
 
 Build OpenSSL (v3.5.0+) or fork AWS-LC, BoringSSL, LibreSSL or quictls:
 
@@ -256,7 +256,7 @@ See this [list of public HTTP/3 servers](https://bagder.github.io/HTTP3-test/)
 
 ### HTTPS eyeballing
 
-With option `--http3` curl attempts earlier HTTP versions as well should the
+With option `--http3` curl attempts lower HTTP versions as well should the
 connect attempt via HTTP/3 fail "fast enough". This strategy is similar
 to IPv4/6 happy eyeballing where the alternate address family is used in
 parallel after a short delay.

docs/INSTALL.md

@@ -429,7 +429,7 @@ for dynamic import symbols.
 Schannel (from Windows SSPI), is the native SSL library in Windows. Schannel
 in Windows <= XP is unable to connect to servers that no longer support the
 legacy handshakes and algorithms used by those versions. If you are using curl
-in one of those earlier versions of Windows you should choose another SSL
+in one of those older versions of Windows you should choose another SSL
 backend such as OpenSSL.
 
 # Android

docs/cmdline-opts/http3-only.md

@@ -21,7 +21,7 @@ Example:
 # `--http3-only`
 
 Instruct curl to use HTTP/3 to the host in the URL, with no fallback to
-earlier HTTP versions. HTTP/3 can only be used for HTTPS and not for HTTP
+lower HTTP versions. HTTP/3 can only be used for HTTPS and not for HTTP
 URLs. For HTTP, this option triggers an error.
 
 This option allows a user to avoid using the Alt-Svc method of upgrading to

docs/cmdline-opts/http3.md

@@ -19,7 +19,7 @@ Example:
 
 # `--http3`
 
-Attempt HTTP/3 to the host in the URL, but fallback to earlier HTTP versions
+Attempt HTTP/3 to the host in the URL, but fallback to lower HTTP versions
 if the HTTP/3 connection establishment fails or is slow. HTTP/3 is only
 available for HTTPS and not for HTTP URLs.
 

docs/examples/http3.c

@@ -41,7 +41,7 @@ int main(void)
   if(curl) {
     curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
 
-    /* Use HTTP/3 but fallback to earlier HTTP if necessary */
+    /* Use HTTP/3 but fallback to lower HTTP if necessary */
     curl_easy_setopt(curl, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_3);
 
     /* Perform the request, result gets the return code */

docs/internals/TLS-SESSIONS.md

@@ -18,7 +18,7 @@ of data and even latency. In the case of QUIC, resumption may send
 application data without having seen any reply from the server, hence
 this is named 0-RTT data.
 
-The exact mechanism of session tickets in TLSv1.2 (and earlier) and
+The exact mechanism of session tickets in TLSv1.2 (and lower) and
 TLSv1.3 differs. TLSv1.2 tickets have several weaknesses (that can
 be exploited by attackers) which TLSv1.3 then fixed. See
 [Session Tickets in the real world](https://words.filippo.io/we-need-to-talk-about-session-tickets/)

docs/libcurl/opts/CURLOPT_HTTP_VERSION.md

@@ -80,7 +80,7 @@ that both HTTP/1.1 and HTTP/2 were offered.
 ## CURL_HTTP_VERSION_3
 
 (Added in 7.66.0) This option makes libcurl attempt to use HTTP/3 to the host
-given in the URL, with fallback to earlier HTTP versions if needed.
+given in the URL, with fallback to lower HTTP versions if needed.
 
 ## CURL_HTTP_VERSION_3ONLY
 

lib/cf-socket.c

@@ -1175,7 +1175,7 @@ static CURLcode cf_socket_open(struct Curl_cfilter *cf,
      * Linux kernel, NetBSD, FreeBSD, Darwin, lwIP: default is off;
      * Windows Vista and newer: default is on;
      * DragonFly BSD: acts like off, and dummy setting;
-     * OpenBSD and earlier Windows: unsupported.
+     * OpenBSD and older Windows: unsupported.
      * Linux: controlled by /proc/sys/net/ipv6/bindv6only.
      */
     int on = 0;

lib/curl_setup.h

@@ -381,7 +381,7 @@
 /* Override default printf mask check rules in "curl/mprintf.h" */
 #define CURL_TEMP_PRINTF CURL_PRINTF
 
-/* Workaround for mainline llvm v16 and earlier missing a built-in macro
+/* Workaround for mainline llvm v16 and lower missing a built-in macro
    expected by macOS SDK v14 / Xcode v15 (2023) and newer.
    gcc (as of v14) is also missing it. */
 #if defined(__APPLE__) &&                                   \

lib/vtls/openssl.c

@@ -2175,7 +2175,7 @@ static CURLcode ossl_verifyhost(struct Curl_easy *data,
       const ASN1_STRING *tmp =
         X509_NAME_ENTRY_get_data(X509_NAME_get_entry(name, i));
 
-      /* In OpenSSL 0.9.7d and earlier, ASN1_STRING_to_UTF8 fails if the input
+      /* In OpenSSL 0.9.7d and lower, ASN1_STRING_to_UTF8 fails if the input
          is already UTF-8 encoded. We check for this case and copy the raw
          string manually to avoid the problem. This code can be made
          conditional in the future when OpenSSL has been fixed. */

lib/vtls/schannel.c

@@ -505,7 +505,7 @@ static CURLcode get_client_cert(struct Curl_cfilter *cf,
       }
 
       /* CERT_FIND_HAS_PRIVATE_KEY is only available in Windows 8 / Server
-         2012, (NT v6.2). For earlier versions we use CURL_FIND_ANY. */
+         2012, (NT v6.2). For older versions we use CURL_FIND_ANY. */
       if(curlx_verify_windows_version(6, 2, 0, PLATFORM_WINNT,
                                       VERSION_GREATER_THAN_EQUAL))
         cert_find_flags = CERT_FIND_HAS_PRIVATE_KEY;

projects/Windows/README.md

@@ -141,8 +141,7 @@ that Visual Studio uses.
 ## Legacy Windows and SSL
 
 Some of the project configurations use Schannel (Windows SSPI), the native SSL
-library that comes with the Windows OS. Schannel in Windows 8 and earlier is
+library that comes with the Windows OS. Schannel in Windows 8 and older is
 not able to connect to servers that no longer support the legacy handshakes
 and algorithms used by those versions. If you are using curl in one of those
-earlier versions of Windows you should choose another SSL backend like
-OpenSSL.
+older versions of Windows you should choose another SSL backend like OpenSSL.