or later -> higher

docs/HTTPSRR.md

@@ -65,7 +65,7 @@ returned, curl parses it and stores the retrieved information.
 
 If DoH is not used for name resolving in an HTTPS RR enabled build, we must
 provide the ability using the regular resolver backends. We use the c-ares DNS
-library for the HTTPS RR lookup. Version 1.28.0 or later.
+library for the HTTPS RR lookup. Version 1.28.0 or higher.
 
 ### c-ares
 

docs/INSTALL.md

@@ -206,8 +206,8 @@ Building for Windows Vista/Server 2008 is required as a minimum.
 
 You can build curl with:
 
-- Microsoft Visual Studio 2010 v10.0 or later (`_MSC_VER >= 1600`)
-- MinGW-w64 3.0 or later (`__MINGW64_VERSION_MAJOR >= 3`)
+- Microsoft Visual Studio 2010 v10.0 or higher (`_MSC_VER >= 1600`)
+- MinGW-w64 3.0 or higher (`__MINGW64_VERSION_MAJOR >= 3`)
 
 ## Building Windows DLLs and C runtime (CRT) linkage issues
 

docs/INTERNALS.md

@@ -24,7 +24,7 @@ want it to remain functional and buildable with these and later versions
 
 ## Dependencies
 
-We aim to support these or later versions.
+We aim to support these or higher versions.
 
 - brotli       1.0.0 (2017-09-21)
 - c-ares       1.16.0 (2020-03-13)
@@ -51,7 +51,7 @@ When writing code (mostly for generating stuff included in release tarballs)
 we use a few "build tools" and we make sure that we remain functional with
 these versions:
 
-- clang-tidy     17.0.0 (2023-09-19), recommended: 19.1.0 or later (2024-09-17)
+- clang-tidy     17.0.0 (2023-09-19), recommended: 19.1.0 or higher (2024-09-17)
 - cmake          3.18 (2020-07-15)
 - GNU autoconf   2.59 (2003-11-06)
 - GNU automake   1.7 (2002-09-25)

docs/SSL-PROBLEMS.md

@@ -47,7 +47,7 @@ An additional complication can be that modern SSL libraries sometimes are
 built with support for older SSL and TLS versions disabled.
 
 All versions of SSL and the TLS versions before 1.2 are considered insecure
-and should be avoided. Use TLS 1.2 or later.
+and should be avoided. Use TLS 1.2 or higher.
 
 ## Ciphers
 

docs/cmdline-opts/proxy-tls13-ciphers.md

@@ -26,8 +26,8 @@ Read up on TLS 1.3 cipher suite details on this URL:
 
 https://curl.se/docs/ssl-ciphers.html
 
-This option is used when curl is built to use OpenSSL 1.1.1 or later,
-Schannel, wolfSSL, or mbedTLS 3.6.0 or later.
+This option is used when curl is built to use OpenSSL 1.1.1 or higher,
+Schannel, wolfSSL, or mbedTLS 3.6.0 or higher.
 
 Before curl 8.10.0 with mbedTLS or wolfSSL, TLS 1.3 cipher suites were set
 by using the --proxy-ciphers option.

docs/cmdline-opts/tls13-ciphers.md

@@ -24,8 +24,8 @@ suite details on this URL:
 
 https://curl.se/docs/ssl-ciphers.html
 
-This option is used when curl is built to use OpenSSL 1.1.1 or later,
-wolfSSL, or mbedTLS 3.6.0 or later.
+This option is used when curl is built to use OpenSSL 1.1.1 or higher,
+wolfSSL, or mbedTLS 3.6.0 or higher.
 
 Before curl 8.10.0 with mbedTLS or wolfSSL, TLS 1.3 cipher suites were set
 by using the --ciphers option.

docs/cmdline-opts/tlsv1.0.md

@@ -15,7 +15,8 @@ Example:
 
 # `--tlsv1.0`
 
-Force curl to use TLS version 1.0 or later when connecting to a remote TLS server.
+Force curl to use TLS version 1.0 or higher when connecting to a remote TLS
+server.
 
 In old versions of curl this option was documented to allow _only_ TLS 1.0.
 That behavior was inconsistent depending on the TLS library. Use --tls-max if

docs/cmdline-opts/tlsv1.1.md

@@ -16,7 +16,8 @@ Example:
 
 # `--tlsv1.1`
 
-Force curl to use TLS version 1.1 or later when connecting to a remote TLS server.
+Force curl to use TLS version 1.1 or higher when connecting to a remote TLS
+server.
 
 In old versions of curl this option was documented to allow _only_ TLS 1.1.
 That behavior was inconsistent depending on the TLS library. Use --tls-max if

docs/cmdline-opts/tlsv1.2.md

@@ -16,7 +16,8 @@ Example:
 
 # `--tlsv1.2`
 
-Force curl to use TLS version 1.2 or later when connecting to a remote TLS server.
+Force curl to use TLS version 1.2 or higher when connecting to a remote TLS
+server.
 
 In old versions of curl this option was documented to allow _only_ TLS 1.2.
 That behavior was inconsistent depending on the TLS library. Use --tls-max if

docs/cmdline-opts/tlsv1.3.md

@@ -16,7 +16,7 @@ Example:
 
 # `--tlsv1.3`
 
-Force curl to use TLS version 1.3 or later when connecting to a remote TLS
+Force curl to use TLS version 1.3 or higher when connecting to a remote TLS
 server.
 
 If the connection is done without TLS, this option has no effect. This

docs/cmdline-opts/tlsv1.md

@@ -21,4 +21,4 @@ Example:
 # `--tlsv1`
 
 Use at least TLS version 1.x when negotiating with a remote TLS server. That
-means TLS version 1.0 or higher
+means TLS version 1.0 or higher.

docs/examples/parseurl.c

@@ -30,7 +30,7 @@
 #include <curl/curl.h>
 
 #if !CURL_AT_LEAST_VERSION(7, 62, 0)
-#error "this example requires curl 7.62.0 or later"
+#error "this example requires curl 7.62.0 or higher"
 #endif
 
 int main(void)

docs/examples/urlapi.c

@@ -29,7 +29,7 @@
 #include <curl/curl.h>
 
 #if !CURL_AT_LEAST_VERSION(7, 80, 0)
-#error "this example requires curl 7.80.0 or later"
+#error "this example requires curl 7.80.0 or higher"
 #endif
 
 int main(void)

docs/libcurl/libcurl-ws.md

@@ -117,7 +117,7 @@ callback configured in CURLOPT_WRITEFUNCTION(3), whenever an incoming chunk
 of WebSocket data is received. The callback is handed a pointer to the payload
 data as an argument and can call curl_ws_meta(3) to get relevant metadata.
 
-With libcurl 8.16.0 or later, sending of WebSocket frames via a
+With libcurl 8.16.0 or higher, sending of WebSocket frames via a
 CURLOPT_READFUNCTION(3) is supported. To use that on such a connection,
 register a callback via CURLOPT_READFUNCTION(3) and set CURLOPT_UPLOAD(3)
 as well. Once, the WebSocket connection is established, your callback is

docs/libcurl/opts/CURLOPT_PROXY_SSLVERSION.md

@@ -105,7 +105,7 @@ int main(void)
     CURLcode result;
     curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
 
-    /* ask libcurl to use TLS version 1.0 or later */
+    /* ask libcurl to use TLS version 1.0 or higher */
     curl_easy_setopt(curl, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1);
 
     /* Perform the request */

docs/libcurl/opts/CURLOPT_SSLVERSION.md

@@ -46,7 +46,7 @@ default TLS v1.2 since 8.16.0 (unless the TLS library has a stricter rule).
 
 ## CURL_SSLVERSION_TLSv1
 
-TLS v1.0 or later
+TLS v1.0 or higher
 
 ## CURL_SSLVERSION_SSLv2
 
@@ -58,19 +58,19 @@ SSL v3 - refused
 
 ## CURL_SSLVERSION_TLSv1_0
 
-TLS v1.0 or later
+TLS v1.0 or higher
 
 ## CURL_SSLVERSION_TLSv1_1
 
-TLS v1.1 or later
+TLS v1.1 or higher
 
 ## CURL_SSLVERSION_TLSv1_2
 
-TLS v1.2 or later
+TLS v1.2 or higher
 
 ## CURL_SSLVERSION_TLSv1_3
 
-TLS v1.3 or later
+TLS v1.3 or higher
 
 ##
 
@@ -117,7 +117,7 @@ int main(void)
     CURLcode result;
     curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
 
-    /* ask libcurl to use TLS version 1.0 or later */
+    /* ask libcurl to use TLS version 1.0 or higher */
     curl_easy_setopt(curl, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1);
 
     /* Perform the request */

docs/tests/TEST-SUITE.md

@@ -136,7 +136,7 @@ set to identify the IP address and port number of the DNS server to use.
   host information
 
 - curl built to use `getaddrinfo()` for resolving *and* is built with c-ares
-  1.26.0 or later, gets a special workaround. In such builds, when the
+  1.26.0 or higher, gets a special workaround. In such builds, when the
   environment variable is set, curl instead invokes a getaddrinfo wrapper
   that emulates the function and acknowledges the DNS server environment
   variable. This way, the getaddrinfo-using code paths in curl are verified,