tidy-up: OS names

Use these words and casing more consistently across text, comments and
one curl tool output:
AIX, ALPN, ANSI, BSD, Cygwin, Darwin, FreeBSD, GitHub, HP-UX, Linux,
macOS, MS-DOS, MSYS, MinGW, NTLM, POSIX, Solaris, UNIX, Unix, Unicode,
WINE, WebDAV, Win32, winbind, WinIDN, Windows, Windows CE, Winsock.

Mostly OS names and a few more.

Also a couple of other minor text fixups.

Closes #14360

docs/CODE_STYLE.md

@@ -271,7 +271,7 @@ DEBUGF(infof(data, "Curl_pp_readresp_ %d bytes of trailing "
 
 Use **#ifdef HAVE_FEATURE** to do conditional code. We avoid checking for
 particular operating systems or hardware in the #ifdef lines. The HAVE_FEATURE
-shall be generated by the configure script for unix-like systems and they are
+shall be generated by the configure script for Unix-like systems and they are
 hard-coded in the `config-[system].h` files for the others.
 
 We also encourage use of macros/functions that possibly are empty or defined

docs/DEPRECATE.md

@@ -32,6 +32,6 @@ May 2025 are: BearSSL and Secure Transport.
  - Support for systems without 64-bit data types
  - NSS
  - gskit
- - mingw v1
+ - MinGW v1
  - NTLM_WB
  - space-separated `NOPROXY` patterns

docs/FAQ

@@ -84,8 +84,8 @@ FAQ
   5.1 Is libcurl thread-safe?
   5.2 How can I receive all data into a large memory chunk?
   5.3 How do I fetch multiple files with libcurl?
-  5.4 Does libcurl do Winsock initialization on win32 systems?
-  5.5 Does CURLOPT_WRITEDATA and CURLOPT_READDATA work on win32 ?
+  5.4 Does libcurl do Winsock initialization on Win32 systems?
+  5.5 Does CURLOPT_WRITEDATA and CURLOPT_READDATA work on Win32 ?
   5.6 What about Keep-Alive or persistent connections?
   5.7 Link errors when building libcurl on Windows
   5.8 libcurl.so.X: open failed: No such file or directory
@@ -424,7 +424,7 @@ FAQ
 
   curl can be built to use one of the following SSL alternatives: OpenSSL,
   LibreSSL, BoringSSL, AWS-LC, GnuTLS, wolfSSL, mbedTLS, Secure Transport
-  (native iOS/OS X), Schannel (native Windows), BearSSL or Rustls. They all
+  (native iOS/macOS), Schannel (native Windows), BearSSL or Rustls. They all
   have their pros and cons, and we try to maintain a comparison of them here:
   https://curl.se/docs/ssl-compared.html
 
@@ -566,7 +566,7 @@ FAQ
   3.10 What about SOAP, WebDAV, XML-RPC or similar protocols over HTTP?
 
   curl adheres to the HTTP spec, which basically means you can play with *any*
-  protocol that is built on top of HTTP. Protocols such as SOAP, WEBDAV and
+  protocol that is built on top of HTTP. Protocols such as SOAP, WebDAV and
   XML-RPC are all such ones. You can use -X to set custom requests and -H to
   set custom headers (or replace internally generated ones).
 
@@ -604,7 +604,7 @@ FAQ
    curl -d ' with spaces ' example.com
 
   Exactly what kind of quotes and how to do this is entirely up to the shell
-  or command line interpreter that you are using. For most unix shells, you
+  or command line interpreter that you are using. For most Unix shells, you
   can more or less pick either single (') or double (") quotes. For
   Windows/DOS command prompts you must use double (") quotes, and if the
   option string contains inner double quotes you can escape them with a
@@ -1174,11 +1174,11 @@ FAQ
   only reusable, but you are even encouraged to reuse it if you can, as that
   will enable libcurl to use persistent connections.
 
-  5.4 Does libcurl do Winsock initialization on win32 systems?
+  5.4 Does libcurl do Winsock initialization on Win32 systems?
 
   Yes, if told to in the curl_global_init() call.
 
-  5.5 Does CURLOPT_WRITEDATA and CURLOPT_READDATA work on win32 ?
+  5.5 Does CURLOPT_WRITEDATA and CURLOPT_READDATA work on Win32 ?
 
   Yes, but you cannot open a FILE * and pass the pointer to a DLL and have
   that DLL use the FILE * (as the DLL and the client application cannot access
@@ -1352,7 +1352,7 @@ FAQ
   then you have to work with what you are given. The LIST output format is
   entirely at the server's own liking and the NLST output does not reveal any
   types and in many cases does not even include all the directory entries.
-  Also, both LIST and NLST tend to hide unix-style hidden files (those that
+  Also, both LIST and NLST tend to hide Unix-style hidden files (those that
   start with a dot) by default so you need to do "LIST -a" or similar to see
   them.
 

docs/FEATURES.md

@@ -44,7 +44,7 @@ SPDX-License-Identifier: curl
  - TCP Fast Open
  - DNS cache (that can be shared between transfers)
  - non-blocking single-threaded parallel transfers
- - unix domain sockets to server or proxy
+ - Unix domain sockets to server or proxy
  - DNS-over-HTTPS
  - uses non-blocking name resolves
  - selectable name resolver backend

docs/INSTALL.md

@@ -253,7 +253,7 @@ Note: The pre-processor settings can be found using the Visual Studio IDE
 under "Project -> Properties -> Configuration Properties -> C/C++ ->
 Preprocessor".
 
-## Using BSD-style lwIP instead of Winsock TCP/IP stack in Win32 builds
+## Using BSD-style lwIP instead of Winsock TCP/IP stack in Windows builds
 
 In order to compile libcurl and curl using BSD-style lwIP TCP/IP stack it is
 necessary to make the definition of the preprocessor symbol `USE_LWIPSOCK`
@@ -521,14 +521,14 @@ disabling support for some feature (run `./configure --help` to see them all):
  - `--disable-mime` (MIME API)
  - `--disable-netrc`  (.netrc file)
  - `--disable-ntlm` (NTLM authentication)
- - `--disable-ntlm-wb` (NTLM WinBind)
+ - `--disable-ntlm-wb` (NTLM winbind)
  - `--disable-progress-meter` (graphical progress meter in library)
  - `--disable-proxy` (HTTP and SOCKS proxies)
  - `--disable-pthreads` (multi-threading)
  - `--disable-socketpair` (socketpair for asynchronous name resolving)
  - `--disable-threaded-resolver`  (threaded name resolver)
  - `--disable-tls-srp` (Secure Remote Password authentication for TLS)
- - `--disable-unix-sockets` (UNIX sockets)
+ - `--disable-unix-sockets` (Unix sockets)
  - `--disable-verbose` (eliminates debugging strings and error code strings)
  - `--disable-versioned-symbols` (versioned symbols)
  - `--enable-symbol-hiding` (eliminates unneeded symbols in the shared library)

docs/INTERNALS.md

@@ -35,7 +35,7 @@ versions of libs and build tools.
  - MIT Kerberos 1.2.4
  - Heimdal      ?
  - nghttp2      1.15.0
- - WinSock      2.2 (on Windows 95+ and Windows CE .NET 4.1+)
+ - Winsock      2.2 (on Windows 95+ and Windows CE .NET 4.1+)
 
 ## Build tools
 

docs/KNOWN_BUGS

@@ -41,7 +41,7 @@ problems may have been fixed or changed somewhat since this was written.
  5.2 curl-config --libs contains private details
  5.3 building for old macOS fails with gcc
  5.5 cannot handle Unicode arguments in non-Unicode builds on Windows
- 5.6 cygwin: make install installs curl-config.1 twice
+ 5.6 Cygwin: make install installs curl-config.1 twice
  5.11 configure --with-gssapi with Heimdal is ignored on macOS
  5.12 flaky CI builds
  5.13 long paths are not fully supported on Windows
@@ -49,7 +49,7 @@ problems may have been fixed or changed somewhat since this was written.
  5.15 Unicode on Windows
 
  6. Authentication
- 6.1 NTLM authentication and unicode
+ 6.1 NTLM authentication and Unicode
  6.2 MIT Kerberos for Windows build
  6.3 NTLM in system context uses wrong name
  6.5 NTLM does not support password with § character
@@ -73,7 +73,7 @@ problems may have been fixed or changed somewhat since this was written.
  9.2 wolfssh: publickey auth does not work
  9.3 Remote recursive folder creation with SFTP
  9.4 libssh blocking and infinite loop problem
- 9.5 cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!"
+ 9.5 Cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!"
 
  10. SOCKS
  10.3 FTPS over SOCKS
@@ -274,7 +274,7 @@ problems may have been fixed or changed somewhat since this was written.
   https://curl.se/bug/?i=731
   https://curl.se/bug/?i=3747
 
-5.6 cygwin: make install installs curl-config.1 twice
+5.6 Cygwin: make install installs curl-config.1 twice
 
  https://github.com/curl/curl/issues/8839
 
@@ -315,19 +315,19 @@ problems may have been fixed or changed somewhat since this was written.
 
 5.15 Unicode on Windows
 
- Passing in a unicode filename with -o:
+ Passing in a Unicode filename with -o:
 
  https://github.com/curl/curl/issues/11461
 
- Passing in unicode character with -d:
+ Passing in Unicode character with -d:
 
  https://github.com/curl/curl/issues/12231
 
 6. Authentication
 
-6.1 NTLM authentication and unicode
+6.1 NTLM authentication and Unicode
 
- NTLM authentication involving unicode username or password only works
+ NTLM authentication involving Unicode username or password only works
  properly if built with UNICODE defined together with the Schannel
  backend. The original problem was mentioned in:
  https://curl.se/mail/lib-2009-10/0024.html
@@ -471,9 +471,9 @@ problems may have been fixed or changed somewhat since this was written.
 
  https://github.com/curl/curl/issues/8632
 
-9.5 cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!"
+9.5 Cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!"
 
- Running SCP and SFTP tests on cygwin makes this warning message appear.
+ Running SCP and SFTP tests on Cygwin makes this warning message appear.
 
  https://github.com/curl/curl/issues/11244
 

docs/SSLCERTS.md

@@ -16,7 +16,7 @@ Native SSL
 ----------
 
 If libcurl was built with Schannel or Secure Transport support (the native SSL
-libraries included in Windows and Mac OS X), then this does not apply to
+libraries included in Windows and macOS), then this does not apply to
 you. Scroll down for details on how the OS-native engines handle SSL
 certificates. If you are not sure, then run "curl -V" and read the results. If
 the version string says `Schannel` in it, then it was built with Schannel
@@ -140,12 +140,12 @@ Transport (Apple's native TLS engine) support, then libcurl still performs
 peer certificate verification, but instead of using a CA cert bundle, it uses
 the certificates that are built into the OS. These are the same certificates
 that appear in the Internet Options control panel (under Windows) or Keychain
-Access application (under OS X). Any custom security rules for certificates
+Access application (under macOS). Any custom security rules for certificates
 are honored.
 
 Schannel runs CRL checks on certificates unless peer verification is disabled.
 Secure Transport on iOS runs OCSP checks on certificates unless peer
-verification is disabled. Secure Transport on OS X runs either OCSP or CRL
+verification is disabled. Secure Transport on macOS runs either OCSP or CRL
 checks on certificates if those features are enabled, and this behavior can be
 adjusted in the preferences of Keychain Access.
 

docs/TODO

@@ -153,7 +153,7 @@
  18.6 Option to make -Z merge lined based outputs on stdout
  18.7 specify which response codes that make -f/--fail return error
  18.9 Choose the name of file in braces for complex URLs
- 18.10 improve how curl works in a windows console window
+ 18.10 improve how curl works in a Windows console window
  18.11 Windows: set attribute 'archive' for completed downloads
  18.12 keep running, read instructions from pipe/socket
  18.13 Acknowledge Ratelimit headers
@@ -202,7 +202,7 @@
 1.1 TFO support on Windows
 
  libcurl supports the CURLOPT_TCP_FASTOPEN option since 7.49.0 for Linux and
- Mac OS. Windows supports TCP Fast Open starting with Windows 10, version 1607
+ macOS. Windows supports TCP Fast Open starting with Windows 10, version 1607
  and we should add support for it.
 
  TCP Fast Open is supported on several platforms but not on Windows. Work on
@@ -465,7 +465,7 @@
  Make sure we do not ever loop because of non-blocking sockets returning
  EWOULDBLOCK or similar. Blocking cases include:
 
- - Name resolves on non-windows unless c-ares or the threaded resolver is used.
+ - Name resolves on non-Windows unless c-ares or the threaded resolver is used.
 
  - The threaded resolver may block on cleanup:
  https://github.com/curl/curl/issues/4852
@@ -758,7 +758,7 @@
 
 10.4 Certificate-Based Authentication
 
- LDAPS not possible with MAC and Windows with Certificate-Based Authentication
+ LDAPS not possible with macOS and Windows with Certificate-Based Authentication
 
  https://github.com/curl/curl/issues/9641
 
@@ -1078,7 +1078,7 @@
 
  See https://github.com/curl/curl/issues/221
 
-18.10 improve how curl works in a windows console window
+18.10 improve how curl works in a Windows console window
 
  If you pull the scrollbar when transferring with curl in a Windows console
  window, the transfer is interrupted and can get disconnected. This can
@@ -1334,7 +1334,7 @@
 
 20.4 more platforms supported
 
- Make the test suite work on more platforms. OpenBSD and Mac OS. Remove
+ Make the test suite work on more platforms. OpenBSD and macOS. Remove
  fork()s and it should become even more portable.
 
 20.6 Use the RFC 6265 test suite

docs/URL-SYNTAX.md

@@ -197,7 +197,7 @@ Transitional Processing. The two standards have a huge overlap but differ
 slightly, perhaps most famously in how they deal with the German "double s"
 (`ß`).
 
-When winidn is used, curl uses IDNA 2003 Transitional Processing, like the rest
+When WinIDN is used, curl uses IDNA 2003 Transitional Processing, like the rest
 of Windows.
 
 ## Port number

docs/cmdline-opts/_ENVIRONMENT.md

@@ -87,7 +87,7 @@ names named after the destination connection id (in hex). Do note that these
 files can become rather large. Works with the ngtcp2 and quiche QUIC backends.
 
 ## `SHELL`
-Used on VMS when trying to detect if using a **DCL** or a **unix** shell.
+Used on VMS when trying to detect if using a **DCL** or a **Unix** shell.
 
 ## `SSL_CERT_DIR` <dir>
 If set, it is used as the --capath value. This environment variable is ignored

docs/cmdline-opts/cacert.md

@@ -27,7 +27,7 @@ curl recognizes the environment variable named 'CURL_CA_BUNDLE' if it is set
 and the TLS backend is not Schannel, and uses the given path as a path to a CA
 cert bundle. This option overrides that variable.
 
-The windows version of curl automatically looks for a CA certs file named
+The Windows version of curl automatically looks for a CA certs file named
 'curl-ca-bundle.crt', either in the same directory as curl.exe, or in the
 Current Working Directory, or in any folder along your PATH.
 

docs/cmdline-opts/create-dirs.md

@@ -21,6 +21,6 @@ mentioned with the --output option combined with the path possibly set with
 --output-dir. If the combined output filename uses no directory, or if the
 directories it mentions already exist, no directories are created.
 
-Created directories are made with mode 0750 on unix style file systems.
+Created directories are made with mode 0750 on Unix-style file systems.
 
 To create remote directories when using FTP or SFTP, try --ftp-create-dirs.

docs/cmdline-opts/false-start.md

@@ -20,4 +20,4 @@ client starts sending application data before verifying the server's Finished
 message, thus saving a round trip when performing a full handshake.
 
 This functionality is currently only implemented in the Secure Transport (on
-iOS 7.0 or later, or OS X 10.9 or later) backend.
+iOS 7.0 or later, or macOS 10.9 or later) backend.

docs/cmdline-opts/socks4.md

@@ -21,7 +21,7 @@ Use the specified SOCKS4 proxy. If the port number is not specified, it is
 assumed at port 1080. Using this socket type make curl resolve the hostname
 and passing the address on to the proxy.
 
-To specify proxy on a unix domain socket, use localhost for host, e.g.
+To specify proxy on a Unix domain socket, use localhost for host, e.g.
 `socks4://localhost/path/to/socket.sock`
 
 This option overrides any previous use of --proxy, as they are mutually

docs/cmdline-opts/socks4a.md

@@ -20,7 +20,7 @@ Example:
 Use the specified SOCKS4a proxy. If the port number is not specified, it is
 assumed at port 1080. This asks the proxy to resolve the hostname.
 
-To specify proxy on a unix domain socket, use localhost for host, e.g.
+To specify proxy on a Unix domain socket, use localhost for host, e.g.
 `socks4a://localhost/path/to/socket.sock`
 
 This option overrides any previous use of --proxy, as they are mutually

docs/cmdline-opts/socks5-hostname.md

@@ -19,7 +19,7 @@ Example:
 Use the specified SOCKS5 proxy (and let the proxy resolve the hostname). If
 the port number is not specified, it is assumed at port 1080.
 
-To specify proxy on a unix domain socket, use localhost for host, e.g.
+To specify proxy on a Unix domain socket, use localhost for host, e.g.
 `socks5h://localhost/path/to/socket.sock`
 
 This option overrides any previous use of --proxy, as they are mutually

docs/cmdline-opts/socks5.md

@@ -19,7 +19,7 @@ Example:
 Use the specified SOCKS5 proxy - but resolve the hostname locally. If the
 port number is not specified, it is assumed at port 1080.
 
-To specify proxy on a unix domain socket, use localhost for host, e.g.
+To specify proxy on a Unix domain socket, use localhost for host, e.g.
 `socks5://localhost/path/to/socket.sock`
 
 This option overrides any previous use of --proxy, as they are mutually

docs/cmdline-opts/use-ascii.md

@@ -19,4 +19,4 @@ Example:
 
 Enable ASCII transfer mode. For FTP, this can also be enforced by using a URL
 that ends with `;type=A`. This option causes data sent to stdout to be in text
-mode for win32 systems.
+mode for Win32 systems.

docs/examples/anyauthput.c

@@ -100,7 +100,7 @@ int main(int argc, char **argv)
   fp = fopen(file, "rb");
   fstat(FILENO(fp), &file_info);
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   curl_global_init(CURL_GLOBAL_ALL);
 
   /* get a curl handle */

docs/examples/ephiperfifo.c

@@ -33,7 +33,7 @@
  *
  * Written by Jeff Pohlmeyer, converted to use epoll by Josh Bialkowski
 
-Requires a linux system with epoll
+Requires a Linux system with epoll
 
 When running, the program creates the named pipe "hiper.fifo"
 

docs/examples/ftpgetresp.c

@@ -48,17 +48,17 @@ int main(void)
   FILE *respfile;
 
   /* local filename to store the file as */
-  ftpfile = fopen(FTPBODY, "wb"); /* b is binary, needed on win32 */
+  ftpfile = fopen(FTPBODY, "wb"); /* b is binary, needed on Windows */
 
   /* local filename to store the FTP server's response lines in */
-  respfile = fopen(FTPHEADERS, "wb"); /* b is binary, needed on win32 */
+  respfile = fopen(FTPHEADERS, "wb"); /* b is binary, needed on Windows */
 
   curl = curl_easy_init();
   if(curl) {
     /* Get a file listing from sunet */
     curl_easy_setopt(curl, CURLOPT_URL, "ftp://ftp.example.com/");
     curl_easy_setopt(curl, CURLOPT_WRITEDATA, ftpfile);
-    /* If you intend to use this on windows with a libcurl DLL, you must use
+    /* If you intend to use this on Windows with a libcurl DLL, you must use
        CURLOPT_WRITEFUNCTION as well */
     curl_easy_setopt(curl, CURLOPT_HEADERFUNCTION, write_response);
     curl_easy_setopt(curl, CURLOPT_HEADERDATA, respfile);

docs/examples/ftpupload.c

@@ -90,7 +90,7 @@ int main(void)
   /* get a FILE * of the same file */
   hd_src = fopen(LOCAL_FILE, "rb");
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   curl_global_init(CURL_GLOBAL_ALL);
 
   /* get a curl handle */

docs/examples/ftpuploadfrommem.c

@@ -76,7 +76,7 @@ int main(void)
   upload.readptr = data;
   upload.sizeleft = strlen(data);
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   res = curl_global_init(CURL_GLOBAL_DEFAULT);
   /* Check for errors */
   if(res != CURLE_OK) {

docs/examples/http-post.c

@@ -33,7 +33,7 @@ int main(void)
   CURL *curl;
   CURLcode res;
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   curl_global_init(CURL_GLOBAL_ALL);
 
   /* get a curl handle */

docs/examples/http2-upload.c

@@ -32,7 +32,7 @@
 #include <sys/stat.h>
 #include <errno.h>
 
-/* somewhat unix-specific */
+/* somewhat Unix-specific */
 #ifndef _MSC_VER
 #include <sys/time.h>
 #include <unistd.h>

docs/examples/httpput-postfields.c

@@ -58,7 +58,7 @@ int main(int argc, char **argv)
 
   url = argv[1];
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   curl_global_init(CURL_GLOBAL_ALL);
 
   /* get a curl handle */

docs/examples/httpput.c

@@ -82,7 +82,7 @@ int main(int argc, char **argv)
      an example! */
   hd_src = fopen(file, "rb");
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   curl_global_init(CURL_GLOBAL_ALL);
 
   /* get a curl handle */

docs/examples/multi-legacy.c

@@ -30,7 +30,7 @@
 #include <stdio.h>
 #include <string.h>
 
-/* somewhat unix-specific */
+/* somewhat Unix-specific */
 #ifndef _WIN32
 #include <sys/time.h>
 #include <unistd.h>

docs/examples/post-callback.c

@@ -73,7 +73,7 @@ int main(void)
   wt.readptr = data;
   wt.sizeleft = strlen(data);
 
-  /* In windows, this inits the winsock stuff */
+  /* In Windows, this inits the Winsock stuff */
   res = curl_global_init(CURL_GLOBAL_DEFAULT);
   /* Check for errors */
   if(res != CURLE_OK) {

docs/examples/unixsocket.c

@@ -22,7 +22,7 @@
  *
  ***************************************************************************/
 /* <DESC>
- * Access HTTP server over unix domain socket
+ * Access HTTP server over Unix domain socket
  * </DESC>
  */
 #include <stdio.h>

docs/libcurl/curl_getenv.md

@@ -27,7 +27,7 @@ char *curl_getenv(const char *name);
 
 curl_getenv() is a portable wrapper for the getenv() function, meant to
 emulate its behavior and provide an identical interface for all operating
-systems libcurl builds on (including win32).
+systems libcurl builds on (including Windows).
 
 You must curl_free(3) the returned string when you are done with it.
 
@@ -55,6 +55,6 @@ specified name.
 
 # NOTE
 
-Under unix operating systems, there is no point in returning an allocated
+Under Unix operating systems, there is no point in returning an allocated
 memory, although other systems does not work properly if this is not done. The
-unix implementation thus suffers slightly from the drawbacks of other systems.
+Unix implementation thus suffers slightly from the drawbacks of other systems.

docs/libcurl/curl_global_init.md

@@ -89,7 +89,7 @@ unexpected behaviors.
 Initialize the Win32 socket libraries.
 
 The implication here is that if this bit is not set, the initialization of
-winsock has to be done by the application or you risk getting undefined
+Winsock has to be done by the application or you risk getting undefined
 behaviors. This option exists for when the initialization is handled outside
 of libcurl so there is no need for libcurl to do it again.
 

docs/libcurl/libcurl-env-dbg.md

@@ -98,7 +98,7 @@ the current.
 
 ## CURL_TIME
 
-Fake unix timestamp to use for AltSvc, HSTS and CURLINFO variables that are
+Fake Unix timestamp to use for AltSvc, HSTS and CURLINFO variables that are
 time related.
 
 This variable can also be used to fake the data returned by some CURLINFO

docs/libcurl/libcurl-tutorial.md

@@ -112,7 +112,7 @@ specified are:
 ## CURL_GLOBAL_WIN32
 
 which only does anything on Windows machines. When used on a Windows machine,
-it makes libcurl initialize the win32 socket stuff. Without having that
+it makes libcurl initialize the Win32 socket stuff. Without having that
 initialized properly, your program cannot use sockets properly. You should
 only do this once for each application, so if your program already does this
 or of another library in use does it, you should not tell libcurl to do this
@@ -235,7 +235,7 @@ to make your program run fine virtually everywhere.
 (CURLOPT_WRITEDATA(3) was formerly known as *CURLOPT_FILE*. Both names still
 work and do the same thing).
 
-If you are using libcurl as a win32 DLL, you MUST use the
+If you are using libcurl as a Windows DLL, you MUST use the
 CURLOPT_WRITEFUNCTION(3) if you set CURLOPT_WRITEDATA(3) - or experience
 crashes.
 

docs/libcurl/libcurl.md

@@ -95,7 +95,7 @@ See libcurl-ws(3)
 
 # LINKING WITH LIBCURL
 
-On unix-like machines, there is a tool named curl-config that gets installed
+On Unix-like machines, there is a tool named curl-config that gets installed
 with the rest of the curl stuff when 'make install' is performed.
 
 curl-config is added to make it easier for applications to link with libcurl

docs/libcurl/opts/CURLOPT_CONNECTTIMEOUT.md

@@ -53,7 +53,7 @@ to 2, the operation can never last longer than 2 seconds. Including the
 connection phase.
 
 This option may cause libcurl to use the SIGALRM signal to timeout system
-calls on builds not using asynch DNS. In unix-like systems, this might cause
+calls on builds not using asynch DNS. In Unix-like systems, this might cause
 signals to be used unless CURLOPT_NOSIGNAL(3) is set.
 
 # DEFAULT

docs/libcurl/opts/CURLOPT_CONNECTTIMEOUT_MS.md

@@ -54,7 +54,7 @@ With CURLOPT_CONNECTTIMEOUT_MS(3) set to 4000 and CURLOPT_TIMEOUT_MS(3) set to
 the connection phase.
 
 This option may cause libcurl to use the SIGALRM signal to timeout system
-calls on builds not using asynch DNS. In unix-like systems, this might cause
+calls on builds not using asynch DNS. In Unix-like systems, this might cause
 signals to be used unless CURLOPT_NOSIGNAL(3) is set.
 
 # DEFAULT

docs/libcurl/opts/CURLOPT_HEADERDATA.md

@@ -36,7 +36,7 @@ If CURLOPT_WRITEFUNCTION(3) or CURLOPT_HEADERFUNCTION(3) is used,
 If neither of those options are set, *pointer* must be a valid FILE * and
 it is used by a plain fwrite() to write headers to.
 
-If you are using libcurl as a win32 DLL, you **MUST** use a
+If you are using libcurl as a Windows DLL, you **MUST** use a
 CURLOPT_WRITEFUNCTION(3) or CURLOPT_HEADERFUNCTION(3) if you set
 this option or you might experience crashes.
 

docs/libcurl/opts/CURLOPT_NOSIGNAL.md

@@ -27,7 +27,7 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_NOSIGNAL, long onoff);
 
 If *onoff* is 1, libcurl uses no functions that install signal handlers or
 any functions that cause signals to be sent to the process. This option is
-here to allow multi-threaded unix applications to still set/use all timeout
+here to allow multi-threaded Unix applications to still set/use all timeout
 options etc, without risking getting signals.
 
 If this option is set and libcurl has been built with the standard name

docs/libcurl/opts/CURLOPT_PROXY_SSLCERTTYPE.md

@@ -39,7 +39,7 @@ the format of your client certificate used when connecting to an HTTPS proxy.
 
 Supported formats are "PEM" and "DER", except with Secure Transport or
 Schannel. OpenSSL (versions 0.9.3 and later), Secure Transport (on iOS 5 or
-later, or OS X 10.7 or later) and Schannel support "P12" for PKCS#12-encoded
+later, or macOS 10.7 or later) and Schannel support "P12" for PKCS#12-encoded
 files.
 
 The application does not have to keep the string around after setting this

docs/libcurl/opts/CURLOPT_PROXY_SSLKEY.md

@@ -39,7 +39,7 @@ the filename of your private key used for connecting to the HTTPS proxy. The
 default format is "PEM" and can be changed with
 CURLOPT_PROXY_SSLKEYTYPE(3).
 
-(Windows, iOS and Mac OS X) This option is ignored by Secure Transport and
+(Windows, iOS and macOS) This option is ignored by Secure Transport and
 Schannel SSL backends because they expect the private key to be already
 present in the key chain or PKCS#12 file containing the certificate.
 

docs/libcurl/opts/CURLOPT_SSLCERTTYPE.md

@@ -38,7 +38,7 @@ the format of your certificate.
 
 Supported formats are "PEM" and "DER", except with Secure Transport or
 Schannel. OpenSSL (versions 0.9.3 and later), Secure Transport (on iOS 5 or
-later, or OS X 10.7 or later) and Schannel support "P12" for PKCS#12-encoded
+later, or macOS 10.7 or later) and Schannel support "P12" for PKCS#12-encoded
 files.
 
 The application does not have to keep the string around after setting this

docs/libcurl/opts/CURLOPT_SSLKEY.md

@@ -36,7 +36,7 @@ Pass a pointer to a null-terminated string as parameter. The string should be
 the filename of your private key. The default format is "PEM" and can be
 changed with CURLOPT_SSLKEYTYPE(3).
 
-(Windows, iOS and Mac OS X) This option is ignored by Secure Transport and
+(Windows, iOS and macOS) This option is ignored by Secure Transport and
 Schannel SSL backends because they expect the private key to be already present
 in the key-chain or PKCS#12 file containing the certificate.
 

docs/libcurl/opts/CURLOPT_TIMEOUT.md

@@ -55,7 +55,7 @@ With CURLOPT_CONNECTTIMEOUT(3) set to 4 and CURLOPT_TIMEOUT(3) set
 to 2, the operation can never last longer than 2 seconds.
 
 This option may cause libcurl to use the SIGALRM signal to timeout system
-calls on builds not using asynch DNS. In unix-like systems, this might cause
+calls on builds not using asynch DNS. In Unix-like systems, this might cause
 signals to be used unless CURLOPT_NOSIGNAL(3) is set.
 
 # DEFAULT

docs/libcurl/opts/CURLOPT_TRANSFERTEXT.md

@@ -26,7 +26,7 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_TRANSFERTEXT, long text);
 # DESCRIPTION
 
 A parameter set to 1 tells the library to use ASCII mode for FTP transfers,
-instead of the default binary transfer. For win32 systems it does not set the
+instead of the default binary transfer. For Win32 systems it does not set the
 stdout to binary mode. This option can be usable when transferring text data
 between systems with different views on certain characters, such as newlines
 or similar.

docs/libcurl/opts/CURLOPT_URL.md

@@ -81,7 +81,7 @@ expected to be a sequence of characters using an ASCII compatible encoding.
 
 If libcurl is built with IDN support, the server name part of the URL can use
 an "international name" by using the current encoding (according to locale) or
-UTF-8 (when winidn is used; or a Windows Unicode build using libidn2).
+UTF-8 (when WinIDN is used; or a Windows Unicode build using libidn2).
 
 If libcurl is built without IDN support, the server name is used exactly as
 specified when passed to the name resolver functions.