docs/cmdline-opts: spellfixes, typos and polish

To make them accepted by the spell checker

Closes #11562

docs/cmdline-opts/cert.d

@@ -38,12 +38,12 @@ private key. If you want to use a file from the current directory, please
 precede it with "./" prefix, in order to avoid confusion with a nickname.
 
 (Schannel only) Client certificates must be specified by a path
-expression to a certificate store. (Loading PFX is not supported; you can
+expression to a certificate store. (Loading *PFX* is not supported; you can
 import it to a store first). You can use
 "<store location>\\<store name>\\<thumbprint>" to refer to a certificate
 in the system certificates store, for example,
-"CurrentUser\\MY\\934a7ac6f8a5d579285a74fa61e19f23ddfe8d7a". Thumbprint is
+*"CurrentUser\\MY\\934a7ac6f8a5d579285a74fa61e19f23ddfe8d7a"*. Thumbprint is
 usually a SHA-1 hex string which you can see in certificate details. Following
-store locations are supported: CurrentUser, LocalMachine, CurrentService,
-Services, CurrentUserGroupPolicy, LocalMachineGroupPolicy,
-LocalMachineEnterprise.
+store locations are supported: *CurrentUser*, *LocalMachine*, *CurrentService*,
+*Services*, *CurrentUserGroupPolicy*, *LocalMachineGroupPolicy* and
+*LocalMachineEnterprise*.

docs/cmdline-opts/config.d

@@ -56,22 +56,22 @@ When curl is invoked, it (unless --disable is used) checks for a default
 config file and uses it if found, even when --config is used. The default
 config file is checked for in the following places in this order:
 
-1) "$CURL_HOME/.curlrc"
+1) **"$CURL_HOME/.curlrc"**
 
-2) "$XDG_CONFIG_HOME/curlrc" (Added in 7.73.0)
+2) **"$XDG_CONFIG_HOME/curlrc"** (Added in 7.73.0)
 
-3) "$HOME/.curlrc"
+3) **"$HOME/.curlrc"**
 
-4) Windows: "%USERPROFILE%\\.curlrc"
+4) Windows: **"%USERPROFILE%\\.curlrc"**
 
-5) Windows: "%APPDATA%\\.curlrc"
+5) Windows: **"%APPDATA%\\.curlrc"**
 
-6) Windows: "%USERPROFILE%\\Application Data\\.curlrc"
+6) Windows: **"%USERPROFILE%\\Application Data\\.curlrc"**
 
 7) Non-Windows: use getpwuid to find the home directory
 
-8) On Windows, if it finds no .curlrc file in the sequence described above, it
+8) On Windows, if it finds no *.curlrc* file in the sequence described above, it
 checks for one in the same dir the curl executable is placed.
 
-On Windows two filenames are checked per location: .curlrc and _curlrc,
-preferring the former. Older versions on Windows checked for _curlrc only.
+On Windows two filenames are checked per location: *.curlrc* and *_curlrc*,
+preferring the former. Older versions on Windows checked for *_curlrc* only.

docs/cmdline-opts/create-dirs.d

@@ -14,6 +14,6 @@ directories mentioned with the --output option, nothing else. If the --output
 file name uses no directory, or if the directories it mentions already exist,
 no directories will be created.
 
-Created dirs 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/crlf.d

@@ -9,6 +9,7 @@ Added: 5.7
 See-also: use-ascii
 Multi: boolean
 ---
-Convert LF to CRLF in upload. Useful for MVS (OS/390).
+Convert line feeds to carriage return plus line feeds in upload. Useful for
+**MVS (OS/390)**.
 
 (SMTP added in 7.40.0)

docs/cmdline-opts/curves.d

@@ -19,5 +19,5 @@ in the "openssl s_client/s_server" utilities.
 the (EC) curve requested by the client, avoiding nontransparent client/server
 negotiations.
 
-If this option is set, the default curves list built into openssl will be
+If this option is set, the default curves list built into OpenSSL will be
 ignored.

docs/cmdline-opts/dns-ipv4-addr.d

@@ -11,6 +11,6 @@ Category: dns
 Example: --dns-ipv4-addr 10.1.2.3 $URL
 Multi: single
 ---
-Tell curl to bind to <ip-address> when making IPv4 DNS requests, so that
-the DNS requests originate from this address. The argument should be a
+Tell curl to bind to a specific IP address when making IPv4 DNS requests, so
+that the DNS requests originate from this address. The argument should be a
 single IPv4 address.

docs/cmdline-opts/dns-ipv6-addr.d

@@ -11,6 +11,6 @@ Category: dns
 Example: --dns-ipv6-addr 2a04:4e42::561 $URL
 Multi: single
 ---
-Tell curl to bind to <ip-address> when making IPv6 DNS requests, so that
-the DNS requests originate from this address. The argument should be a
+Tell curl to bind to a specific IP address when making IPv6 DNS requests, so
+that the DNS requests originate from this address. The argument should be a
 single IPv6 address.

docs/cmdline-opts/form.d

@@ -36,7 +36,7 @@ before the transfer starts, such data is sent as chunks by HTTP and rejected
 by IMAP.
 
 Example: send an image to an HTTP server, where 'profile' is the name of the
-form-field to which the file portrait.jpg will be the input:
+form-field to which the file **portrait.jpg** will be the input:
 
  curl -F profile=@portrait.jpg https://example.com/upload.cgi
 

docs/cmdline-opts/help.d

@@ -10,9 +10,12 @@ Added: 4.0
 See-also: verbose
 Multi: custom
 ---
-Usage help. This lists all commands of the <category>.
-If no arg was provided, curl will display the most important
-command line arguments.
-If the argument "all" was provided, curl will display all options available.
-If the argument "category" was provided, curl will display all categories and
-their meanings.
+Usage help. This lists all curl command line options within the given
+**category**.
+
+If no argument is provided, curl displays only the most important command line
+arguments.
+
+For category **all**, curl displays help for all options.
+
+If **category** is specified, curl displays all available help categories.

docs/cmdline-opts/http0.9.d

@@ -12,8 +12,8 @@ Multi: boolean
 ---
 Tells curl to be fine with HTTP version 0.9 response.
 
-HTTP/0.9 is a completely headerless response and therefore you can also
-connect with this to non-HTTP servers and still get a response since curl will
-simply transparently downgrade - if allowed.
+HTTP/0.9 is a response without headers and therefore you can also connect with
+this to non-HTTP servers and still get a response since curl will simply
+transparently downgrade - if allowed.
 
 Since curl 7.66.0, HTTP/0.9 is disabled by default.

docs/cmdline-opts/interface.d

@@ -14,6 +14,6 @@ name, IP address or host name. An example could look like:
 
  curl --interface eth0:1 https://www.example.com/
 
-On Linux it can be used to specify a VRF, but the binary needs to either
-have CAP_NET_RAW or to be run as root. More information about Linux VRF:
-https://www.kernel.org/doc/Documentation/networking/vrf.txt
+On Linux it can be used to specify a **VRF**, but the binary needs to either
+have **CAP_NET_RAW** or to be run as root. More information about Linux
+**VRF**: https://www.kernel.org/doc/Documentation/networking/vrf.txt

docs/cmdline-opts/login-options.d

@@ -15,7 +15,7 @@ Specify the login options to use during server authentication.
 You can use login options to specify protocol specific options that may be
 used during authentication. At present only IMAP, POP3 and SMTP support
 login options. For more information about login options please see RFC
-2384, RFC 5092 and IETF draft draft-earhart-url-smtp-00.txt
+2384, RFC 5092 and the IETF draft **draft-earhart-url-smtp-00.txt**.
 
 Since 8.2.0, IMAP supports the login option "AUTH=+LOGIN". With this option,
 curl uses the plain (not SASL) LOGIN IMAP command even if the server advertises

docs/cmdline-opts/mail-rcpt.d

@@ -13,7 +13,7 @@ Multi: append
 Specify a single email address, user name or mailing list name. Repeat this
 option several times to send to multiple recipients.
 
-When performing an address verification (VRFY command), the recipient should be
+When performing an address verification (*VRFY* command), the recipient should be
 specified as the user name or user name and domain (as per Section 3.5 of
 RFC 5321). (Added in 7.34.0)
 

docs/cmdline-opts/metalink.d

@@ -8,5 +8,5 @@ Example: --metalink file $URL
 See-also: parallel
 Multi: single
 ---
-This option was previously used to specify a metalink resource. Metalink
+This option was previously used to specify a Metalink resource. Metalink
 support has been disabled in curl since 7.78.0 for security reasons.

docs/cmdline-opts/noproxy.d

@@ -18,7 +18,7 @@ not www.notlocal.com.
 
 Since 7.53.0, This option overrides the environment variables that disable the
 proxy ('no_proxy' and 'NO_PROXY'). If there's an environment variable
-disabling a proxy, you can set the noproxy list to "" to override it.
+disabling a proxy, you can set the no proxy list to "" to override it.
 
 Since 7.86.0, IP addresses specified to this option can be provided using CIDR
 notation: an appended slash and number specifies the number of "network bits"

docs/cmdline-opts/output.d

@@ -44,6 +44,6 @@ To suppress response bodies, you can redirect output to /dev/null:
 
   curl example.com -o /dev/null
 
-Or for Windows use nul:
+Or for Windows use **nul**:
 
   curl example.com -o nul

docs/cmdline-opts/page-footer

@@ -60,19 +60,20 @@ the case insensitive name of the particular backend to use when curl is
 invoked. Setting a name that is not a built-in alternative will make curl
 stay with the default.
 
-SSL backend names (case-insensitive): bearssl, gnutls, gskit, mbedtls,
-nss, openssl, rustls, schannel, secure-transport, wolfssl
+SSL backend names (case-insensitive): **bearssl**, **gnutls**, **gskit**,
+**mbedtls**, **openssl**, **rustls**, **schannel**, **secure-transport**,
+**wolfssl**
 .IP "HOME <dir>"
 If set, this is used to find the home directory when that is needed. Like when
 looking for the default .curlrc. *CURL_HOME* and *XDG_CONFIG_HOME*
 have preference.
 .IP "QLOGDIR <directory name>"
 If curl was built with HTTP/3 support, setting this environment variable to a
-local directory will make curl produce qlogs in that directory, using file
+local directory will make curl produce **qlogs** in that directory, using file
 names named after the destination connection id (in hex). Do note that these
 files can become rather large. Works with both QUIC backends.
 .IP 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.
 .IP "SSL_CERT_DIR <dir>"
 If set, will be used as the --capath value.
 .IP "SSL_CERT_FILE <path>"
@@ -86,7 +87,7 @@ BoringSSL, GnuTLS and wolfSSL.
 .IP "USERPROFILE <dir>"
 On Windows, this variable is used when trying to find the home directory. If
 the other, primary, variable are all unset. If set, curl will use the path
-"$USERPROFILE\\Application Data".
+**"$USERPROFILE\\Application Data"**.
 .IP "XDG_CONFIG_HOME <dir>"
 If *CURL_HOME* is not set, this variable is checked when looking for a
 default .curlrc file.
@@ -243,7 +244,7 @@ Requested FTP SSL level failed.
 .IP 65
 Sending the data requires a rewind that failed.
 .IP 66
-Failed to initialise SSL Engine.
+Failed to initialize SSL Engine.
 .IP 67
 The user name, password, or similar was not accepted and curl failed to log in.
 .IP 68

docs/cmdline-opts/page-header

@@ -112,7 +112,7 @@ You an access and expand environment variables by first importing them. You
 can select to either require the environment variable to be set or you can
 provide a default value in case it is not already set. Plain --variable %name
 imports the variable called 'name' but exits with an error if that environment
-variable is not alreadty set. To provide a default value if it is not set, use
+variable is not already set. To provide a default value if it is not set, use
 --variable %name=content or --variable %name@content.
 
 Example. Get the USER environment variable into the URL, fail if USER is not
@@ -123,11 +123,11 @@ set:
 
 When expanding variables, curl supports a set of functions that can make the
 variable contents more convenient to use. It can trim leading and trailing
-white space with "trim", it can output the contents as a JSON quoted string
-with "json" and it can URL encode the string with "urlencode". You apply
-function to a variable expansion, add them colon separated to the right side
-of the variable. Variable content holding null bytes that are not encoded when
-expanded, will cause error.
+white space with *trim*, it can output the contents as a JSON quoted string
+with *json*, URL encode the string with *url* or base64 encode it with
+*b64*. You apply function to a variable expansion, add them colon separated to
+the right side of the variable. Variable content holding null bytes that are
+not encoded when expanded, will cause error.
 
 Example: get the contents of a file called $HOME/.secret into a variable
 called "fix". Make sure that the content is trimmed and percent-encoded sent
@@ -179,7 +179,7 @@ not supported (yet).
 Downloading from a pop3 server means getting a mail. With or without using
 TLS.
 .IP RTMP(S)
-The Realtime Messaging Protocol is primarily used to server streaming media
+The **Realtime Messaging Protocol** is primarily used to serve streaming media
 and curl can download it.
 .IP RTSP
 curl supports RTSP 1.0 downloads.
@@ -240,12 +240,12 @@ between it and its value.
 
 Short version options that do not need any additional values can be used
 immediately next to each other, like for example you can specify all the
-options -O, -L and -v at once as -OLv.
+options *-O*, *-L* and *-v* at once as *-OLv*.
 
 In general, all boolean options are enabled with --**option** and yet again
 disabled with --**no-**option. That is, you use the same option name but
 prefix it with "no-". However, in this list we mostly only list and show the
---option version of them.
+*--option* version of them.
 
 When --next is used, it resets the parser state and you start again with a
 clean option state, except for the options that are "global". Global options

docs/cmdline-opts/pinnedpubkey.d

@@ -27,12 +27,12 @@ PEM/DER support:
 
 7.43.0: wolfSSL
 
-7.47.0: mbedtls
+7.47.0: mbedTLS
 
 sha256 support:
 
 7.44.0: OpenSSL, GnuTLS and wolfSSL
 
-7.47.0: mbedtls
+7.47.0: mbedTLS
 
 Other SSL backends not supported.

docs/cmdline-opts/quote.d

@@ -12,9 +12,9 @@ See-also: request
 Multi: append
 ---
 Send an arbitrary command to the remote FTP or SFTP server. Quote commands are
-sent BEFORE the transfer takes place (just after the initial PWD command in an
-FTP transfer, to be exact). To make commands take place after a successful
-transfer, prefix them with a dash '-'.
+sent BEFORE the transfer takes place (just after the initial **PWD** command
+in an FTP transfer, to be exact). To make commands take place after a
+successful transfer, prefix them with a dash '-'.
 
 (FTP only) To make commands be sent after curl has changed the working
 directory, just before the file transfer command(s), prefix the command with a
@@ -36,52 +36,52 @@ shell-style to embed spaces or special characters. Following is the list of
 all supported SFTP quote commands:
 .RS
 .TP
-.B "atime date file"
+**"atime date file"**
 The atime command sets the last access time of the file named by the file
 operand. The <date expression> can be all sorts of date strings, see the
 *curl_getdate(3)* man page for date expression details. (Added in 7.73.0)
 .TP
-.B "chgrp group file"
+**"chgrp group file"**
 The chgrp command sets the group ID of the file named by the file operand to
 the group ID specified by the group operand. The group operand is a decimal
 integer group ID.
 .TP
-.B "chmod mode file"
+**"chmod mode file"**
 The chmod command modifies the file mode bits of the specified file. The
 mode operand is an octal integer mode number.
 .TP
-.B "chown user file"
+**"chown user file"**
 The chown command sets the owner of the file named by the file operand to the
 user ID specified by the user operand. The user operand is a decimal
 integer user ID.
 .TP
-.B "ln source_file target_file"
+**"ln source_file target_file"**
 The ln and symlink commands create a symbolic link at the target_file location
 pointing to the source_file location.
 .TP
-.B "mkdir directory_name"
+**"mkdir directory_name"**
 The mkdir command creates the directory named by the directory_name operand.
 .TP
-.B "mtime date file"
+**"mtime date file"**
 The mtime command sets the last modification time of the file named by the
 file operand. The <date expression> can be all sorts of date strings, see the
 *curl_getdate(3)* man page for date expression details. (Added in 7.73.0)
 .TP
-.B "pwd"
-The pwd command returns the absolute pathname of the current working directory.
+**"pwd"**
+The pwd command returns the absolute path name of the current working directory.
 .TP
-.B "rename source target"
+**"rename source target"**
 The rename command renames the file or directory named by the source
 operand to the destination path named by the target operand.
 .TP
-.B "rm file"
+**"rm file"**
 The rm command removes the file specified by the file operand.
 .TP
-.B "rmdir directory"
+**"rmdir directory"**
 The rmdir command removes the directory entry specified by the directory
 operand, provided it is empty.
 .TP
-.B "symlink source_file target_file"
+**"symlink source_file target_file"**
 See ln.
 .RE
 .IP

docs/cmdline-opts/request.d

@@ -13,13 +13,13 @@ Multi: single
 ---
 (HTTP) Specifies a custom request method to use when communicating with the
 HTTP server. The specified request method will be used instead of the method
-otherwise used (which defaults to GET). Read the HTTP 1.1 specification for
-details and explanations. Common additional HTTP requests include PUT and
-DELETE, but related technologies like WebDAV offers PROPFIND, COPY, MOVE and
-more.
+otherwise used (which defaults to *GET*). Read the HTTP 1.1 specification for
+details and explanations. Common additional HTTP requests include *PUT* and
+*DELETE*, but related technologies like WebDAV offers *PROPFIND*, *COPY*,
+*MOVE* and more.
 
-Normally you do not need this option. All sorts of GET, HEAD, POST and PUT
-requests are rather invoked by using dedicated command line options.
+Normally you do not need this option. All sorts of *GET*, *HEAD*, *POST* and
+*PUT* requests are rather invoked by using dedicated command line options.
 
 This option only changes the actual word used in the HTTP request, it does not
 alter the way curl behaves. So for example if you want to make a proper HEAD
@@ -31,15 +31,15 @@ does not change request method according to the HTTP 30x response codes - and
 similar.
 
 (FTP)
-Specifies a custom FTP command to use instead of LIST when doing file lists
+Specifies a custom FTP command to use instead of *LIST* when doing file lists
 with FTP.
 
 (POP3)
-Specifies a custom POP3 command to use instead of LIST or RETR.
+Specifies a custom POP3 command to use instead of *LIST* or *RETR*.
 (Added in 7.26.0)
 
 (IMAP)
-Specifies a custom IMAP command to use instead of LIST. (Added in 7.30.0)
+Specifies a custom IMAP command to use instead of *LIST*. (Added in 7.30.0)
 
 (SMTP)
-Specifies a custom SMTP command to use instead of HELP or VRFY. (Added in 7.34.0)
+Specifies a custom SMTP command to use instead of *HELP* or *VRFY*. (Added in 7.34.0)

docs/cmdline-opts/retry-all-errors.d

@@ -11,10 +11,10 @@ Multi: boolean
 Retry on any error. This option is used together with --retry.
 
 This option is the "sledgehammer" of retrying. Do not use this option by
-default (eg in curlrc), there may be unintended consequences such as sending or
-receiving duplicate data. Do not use with redirected input or output. You'd be
-much better off handling your unique problems in shell script. Please read the
-example below.
+default (for example in your **curlrc**), there may be unintended consequences
+such as sending or receiving duplicate data. Do not use with redirected input
+or output. You'd be much better off handling your unique problems in shell
+script. Please read the example below.
 
 **WARNING**: For server compatibility curl attempts to retry failed flaky
 transfers as close as possible to how they were started, but this is not

docs/cmdline-opts/sasl-authzid.d

@@ -9,10 +9,11 @@ Example: --sasl-authzid zid imap://example.com/
 See-also: login-options
 Multi: single
 ---
-Use this authorization identity (authzid), during SASL PLAIN authentication,
-in addition to the authentication identity (authcid) as specified by --user.
+Use this authorization identity (**authzid**), during SASL PLAIN
+authentication, in addition to the authentication identity (**authcid**) as
+specified by --user.
 
-If the option is not specified, the server will derive the authzid from the
-authcid, but if specified, and depending on the server implementation, it may
-be used to access another user's inbox, that the user has been granted access
-to, or a shared mailbox for example.
+If the option is not specified, the server will derive the **authzid** from
+the **authcid**, but if specified, and depending on the server implementation, it
+may be used to access another user's inbox, that the user has been granted
+access to, or a shared mailbox for example.

docs/cmdline-opts/service-name.d

@@ -10,5 +10,3 @@ See-also: negotiate proxy-service-name
 Multi: single
 ---
 This option allows you to change the service name for SPNEGO.
-
-Examples: --negotiate --service-name sockd would use sockd/server-name.

docs/cmdline-opts/socks5-gssapi-service.d

@@ -9,10 +9,5 @@ Example: --socks5-gssapi-service sockd --socks5 hostname:4096 $URL
 See-also: socks5
 Multi: single
 ---
-The default service name for a socks server is rcmd/server-fqdn. This option
+The default service name for a socks server is **rcmd/server-fqdn**. This option
 allows you to change it.
-
-Examples: --socks5 proxy-name --socks5-gssapi-service sockd would use
-sockd/proxy-name --socks5 proxy-name --socks5-gssapi-service sockd/real-name
-would use sockd/real-name for cases where the proxy-name does not match the
-principal name.

docs/cmdline-opts/telnet-option.d

@@ -12,8 +12,12 @@ Multi: append
 ---
 Pass options to the telnet protocol. Supported options are:
 
-TTYPE=<term> Sets the terminal type.
-
-XDISPLOC=<X display> Sets the X display location.
-
-NEW_ENV=<var,val> Sets an environment variable.
+.RS
+.TP 15
+**TTYPE**=<term> Sets the terminal type.
+.TP
+**XDISPLOC**=<X display> Sets the X display location.
+.TP
+**NEW_ENV**=<var,val> Sets an environment variable.
+.RE
+.IP

docs/cmdline-opts/tftp-blksize.d

@@ -10,6 +10,6 @@ Example: --tftp-blksize 1024 tftp://example.com/file
 See-also: tftp-no-options
 Multi: single
 ---
-Set TFTP BLKSIZE option (must be >512). This is the block size that curl will
-try to use when transferring data to or from a TFTP server. By default 512
-bytes will be used.
+Set the TFTP **BLKSIZE** option (must be >512). This is the block size that
+curl will try to use when transferring data to or from a TFTP server. By
+default 512 bytes will be used.

docs/cmdline-opts/variable.d

@@ -26,7 +26,7 @@ require the environment variable to be set or provide a default value for the
 variable in case it is not already set.
 
 --variable %name imports the variable called 'name' but exits with an error if
-that environment variable is not alreadty set. To provide a default value if
+that environment variable is not already set. To provide a default value if
 the environment variable is not set, use --variable %name=content or
 --variable %name@content. Note that on some systems - but not all -
 environment variables are case insensitive.
@@ -34,7 +34,7 @@ environment variables are case insensitive.
 When expanding variables, curl supports a set of functions that can make the
 variable contents more convenient to use. You apply a function to a variable
 expansion by adding a colon and then list the desired functions in a
-comma-separted list that is evaluated in a left-to-right order. Variable
+comma-separated list that is evaluated in a left-to-right order. Variable
 content holding null bytes that are not encoded when expanded, will cause
 error.
 

docs/cmdline-opts/write-out.d

@@ -38,7 +38,7 @@ created, curl will leave the output to the one used prior to the *%output{}*
 instruction. Use *%output{>>name}* to append data to an existing file. Added in
 curl 8.3.0.
 
-.B NOTE:
+**NOTE:**
 In Windows the %-symbol is a special symbol used to expand environment
 variables. In batch files all occurrences of % must be doubled when using this
 option to properly escape. If this option is used at the command prompt then
@@ -47,30 +47,30 @@ the % cannot be escaped and unintended expansion is possible.
 The variables available are:
 .RS
 .TP 15
-.B certs
+**certs**
 Output the certificate chain with details. Supported only by the OpenSSL,
 GnuTLS, Schannel, GSKit and Secure Transport backends. (Added in 7.88.0)
 .TP
-.B content_type
+**content_type**
 The Content-Type of the requested document, if there was any.
 .TP
-.B errormsg
+**errormsg**
 The error message. (Added in 7.75.0)
 .TP
-.B exitcode
-The numerical exitcode of the transfer. (Added in 7.75.0)
+**exitcode**
+The numerical exit code of the transfer. (Added in 7.75.0)
 .TP
-.B filename_effective
+**filename_effective**
 The ultimate filename that curl writes out to. This is only meaningful if curl
 is told to write to a file with the --remote-name or --output
 option. It's most useful in combination with the --remote-header-name
 option. (Added in 7.26.0)
 .TP
-.B ftp_entry_path
+**ftp_entry_path**
 The initial path curl ended up in when logging on to the remote FTP
 server. (Added in 7.15.4)
 .TP
-.B header_json
+**header_json**
 A JSON object with all HTTP response headers from the recent transfer. Values
 are provided as arrays, since in the case of multiple headers there can be
 multiple values. (Added in 7.83.0)
@@ -79,213 +79,213 @@ The header names provided in lowercase, listed in order of appearance over the
 wire. Except for duplicated headers. They are grouped on the first occurrence
 of that header, each value is presented in the JSON array.
 .TP
-.B http_code
+**http_code**
 The numerical response code that was found in the last retrieved HTTP(S) or
 FTP(s) transfer.
 .TP
-.B http_connect
+**http_connect**
 The numerical code that was found in the last response (from a proxy) to a
 curl CONNECT request. (Added in 7.12.4)
 .TP
-.B http_version
+**http_version**
 The http version that was effectively used. (Added in 7.50.0)
 .TP
-.B json
+**json**
 A JSON object with all available keys.
 .TP
-.B local_ip
+**local_ip**
 The IP address of the local end of the most recently done connection - can be
 either IPv4 or IPv6. (Added in 7.29.0)
 .TP
-.B local_port
+**local_port**
 The local port number of the most recently done connection. (Added in 7.29.0)
 .TP
-.B method
+**method**
 The http method used in the most recent HTTP request. (Added in 7.72.0)
 .TP
-.B num_certs
+**num_certs**
 Number of server certificates received in the TLS handshake. Supported only by
 the OpenSSL, GnuTLS, Schannel, GSKit and Secure Transport backends. (Added
 in 7.88.0)
 .TP
-.B num_connects
+**num_connects**
 Number of new connects made in the recent transfer. (Added in 7.12.3)
 .TP
-.B num_headers
+**num_headers**
 The number of response headers in the most recent request (restarted at each
 redirect). Note that the status line IS NOT a header. (Added in 7.73.0)
 .TP
-.B num_redirects
+**num_redirects**
 Number of redirects that were followed in the request. (Added in 7.12.3)
 .TP
-.B onerror
+**onerror**
 The rest of the output is only shown if the transfer returned a non-zero error.
 (Added in 7.75.0)
 .TP
-.B proxy_ssl_verify_result
+**proxy_ssl_verify_result**
 The result of the HTTPS proxy's SSL peer certificate verification that was
 requested. 0 means the verification was successful. (Added in 7.52.0)
 .TP
-.B redirect_url
+**redirect_url**
 When an HTTP request was made without --location to follow redirects (or when
 --max-redirs is met), this variable will show the actual URL a redirect
 *would* have gone to. (Added in 7.18.2)
 .TP
-.B referer
+**referer**
 The Referer: header, if there was any. (Added in 7.76.0)
 .TP
-.B remote_ip
+**remote_ip**
 The remote IP address of the most recently done connection - can be either
 IPv4 or IPv6. (Added in 7.29.0)
 .TP
-.B remote_port
+**remote_port**
 The remote port number of the most recently done connection. (Added in 7.29.0)
 .TP
-.B response_code
+**response_code**
 The numerical response code that was found in the last transfer (formerly
 known as "http_code"). (Added in 7.18.2)
 .TP
-.B scheme
+**scheme**
 The URL scheme (sometimes called protocol) that was effectively used. (Added in 7.52.0)
 .TP
-.B size_download
+**size_download**
 The total amount of bytes that were downloaded. This is the size of the
 body/data that was transferred, excluding headers.
 .TP
-.B size_header
+**size_header**
 The total amount of bytes of the downloaded headers.
 .TP
-.B size_request
+**size_request**
 The total amount of bytes that were sent in the HTTP request.
 .TP
-.B size_upload
+**size_upload**
 The total amount of bytes that were uploaded. This is the size of the
 body/data that was transferred, excluding headers.
 .TP
-.B speed_download
+**speed_download**
 The average download speed that curl measured for the complete download. Bytes
 per second.
 .TP
-.B speed_upload
+**speed_upload**
 The average upload speed that curl measured for the complete upload. Bytes per
 second.
 .TP
-.B ssl_verify_result
+**ssl_verify_result**
 The result of the SSL peer certificate verification that was requested. 0
 means the verification was successful. (Added in 7.19.0)
 .TP
-.B stderr
+**stderr**
 From this point on, the --write-out output will be written to standard
 error. (Added in 7.63.0)
 .TP
-.B stdout
+**stdout**
 From this point on, the --write-out output will be written to standard output.
 This is the default, but can be used to switch back after switching to stderr.
 (Added in 7.63.0)
 .TP
-.B time_appconnect
+**time_appconnect**
 The time, in seconds, it took from the start until the SSL/SSH/etc
 connect/handshake to the remote host was completed. (Added in 7.19.0)
 .TP
-.B time_connect
+**time_connect**
 The time, in seconds, it took from the start until the TCP connect to the
 remote host (or proxy) was completed.
 .TP
-.B time_namelookup
+**time_namelookup**
 The time, in seconds, it took from the start until the name resolving was
 completed.
 .TP
-.B time_pretransfer
+**time_pretransfer**
 The time, in seconds, it took from the start until the file transfer was just
 about to begin. This includes all pre-transfer commands and negotiations that
 are specific to the particular protocol(s) involved.
 .TP
-.B time_redirect
+**time_redirect**
 The time, in seconds, it took for all redirection steps including name lookup,
 connect, pretransfer and transfer before the final transaction was
 started. time_redirect shows the complete execution time for multiple
 redirections. (Added in 7.12.3)
 .TP
-.B time_starttransfer
+**time_starttransfer**
 The time, in seconds, it took from the start until the first byte was just
 about to be transferred. This includes time_pretransfer and also the time the
 server needed to calculate the result.
 .TP
-.B time_total
+**time_total**
 The total time, in seconds, that the full operation lasted.
 .TP
-.B url
+**url**
 The URL that was fetched. (Added in 7.75.0)
 .TP
-.B url.scheme
+**url.scheme**
 The scheme part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.user
+**url.user**
 The user part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.password
+**url.password**
 The password part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.options
+**url.options**
 The options part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.host
+**url.host**
 The host part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.port
+**url.port**
 The port number of the URL that was fetched. If no port number was specified,
 but the URL scheme is known, that scheme's default port number is
 shown. (Added in 8.1.0)
 .TP
-.B url.path
+**url.path**
 The path part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.query
+**url.query**
 The query part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.fragment
+**url.fragment**
 The fragment part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B url.zoneid
-The zoneid part of the URL that was fetched. (Added in 8.1.0)
+**url.zoneid**
+The zone id part of the URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.scheme
+**urle.scheme**
 The scheme part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.user
+**urle.user**
 The user part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.password
+**urle.password**
 The password part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.options
+**urle.options**
 The options part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.host
+**urle.host**
 The host part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.port
+**urle.port**
 The port number of the effective (last) URL that was fetched. If no port
 number was specified, but the URL scheme is known, that scheme's default port
 number is shown. (Added in 8.1.0)
 .TP
-.B urle.path
+**urle.path**
 The path part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.query
+**urle.query**
 The query part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.fragment
+**urle.fragment**
 The fragment part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urle.zoneid
-The zoneid part of the effective (last) URL that was fetched. (Added in 8.1.0)
+**urle.zoneid**
+The zone id part of the effective (last) URL that was fetched. (Added in 8.1.0)
 .TP
-.B urlnum
-The URL index number of this transfer, 0-indexed. De-globbed URLs share the
+**urlnum**
+The URL index number of this transfer, 0-indexed. Unglobbed URLs share the
 same index number as the origin globbed URL. (Added in 7.75.0)
 .TP
-.B url_effective
+**url_effective**
 The URL that was fetched last. This is most meaningful if you have told curl
 to follow location: headers.
 .RE