cmdline-opts: formatting fixes

docs/cmdline-opts/data.d

@@ -24,7 +24,7 @@ chunk that looks like \&'name=daniel&skill=lousy'.
 If you start the data with the letter @, the rest should be a file name to
 read the data from, or - if you want curl to read the data from
 stdin. Multiple files can also be specified. Posting data from a file named
-'foobar' would thus be done with \fI--data\fP @foobar. When --data is told to
-read from a file like that, carriage returns and newlines will be stripped
-out. If you don't want the @ character to have a special interpretation use
---data-raw instead.
+'foobar' would thus be done with --data @foobar. When --data is told to read
+from a file like that, carriage returns and newlines will be stripped out. If
+you don't want the @ character to have a special interpretation use --data-raw
+instead.

docs/cmdline-opts/engine.d

@@ -3,6 +3,6 @@ Arg: <name>
 Help: Crypto engine to use
 Protocols: TLS
 ---
-Select the OpenSSL crypto engine to use for cipher operations. Use \fI--engine
-list\fP to print a list of build-time supported engines. Note that not all (or
+Select the OpenSSL crypto engine to use for cipher operations. Use --engine
+list to print a list of build-time supported engines. Note that not all (or
 none) of the engines may be available at run-time.

docs/cmdline-opts/page-footer

@@ -1,14 +1,14 @@
 .SH FILES
 .I ~/.curlrc
 .RS
-Default config file, see \fI-K, --config\fP for details.
+Default config file, see --config for details.
 .SH ENVIRONMENT
 The environment variables can be specified in lower case or upper case. The
 lower case version has precedence. http_proxy is an exception as it is only
 available in lower case.
 
 Using an environment variable to set the proxy has the same effect as using
-the \fI--proxy\fP option.
+the --proxy option.
 
 .IP "http_proxy [protocol://]<host>[:port]"
 Sets the proxy server to use for HTTP.
@@ -32,13 +32,13 @@ a supported one, the proxy will be treated as an HTTP proxy.
 
 The supported proxy protocol prefixes are as follows:
 .IP "socks4://"
-Makes it the equivalent of \fI--socks4\fP
+Makes it the equivalent of --socks4
 .IP "socks4a://"
-Makes it the equivalent of \fI--socks4a\fP
+Makes it the equivalent of --socks4a
 .IP "socks5://"
-Makes it the equivalent of \fI--socks5\fP
+Makes it the equivalent of --socks5
 .IP "socks5h://"
-Makes it the equivalent of \fI--socks5-hostname\fP
+Makes it the equivalent of --socks5-hostname
 .SH EXIT CODES
 There are a bunch of different error codes and their corresponding error
 messages that may appear during bad conditions. At the time of this writing,
@@ -85,7 +85,7 @@ FTP quote error. A quote command returned error from the server.
 .IP 22
 HTTP page not retrieved. The requested url was not found or returned another
 error with the HTTP error code being 400 or above. This return code only
-appears if \fI-f, --fail\fP is used.
+appears if --fail is used.
 .IP 23
 Write error. Curl couldn't write data to a local filesystem or similar.
 .IP 25

docs/cmdline-opts/proxy-pass.d

@@ -3,4 +3,4 @@ Arg: <phrase>
 Help: Pass phrase for the private key for HTTPS proxy
 Added: 7.52.0
 ---
-Same as \fI--pass\fP but used in HTTPS proxy context.
+Same as --pass but used in HTTPS proxy context.

docs/cmdline-opts/write-out.d

@@ -27,8 +27,8 @@ The Content-Type of the requested document, if there was any.
 .TP
 .B 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 \fI--remote-name\fP or \fI--output\fP
-option. It's most useful in combination with the \fI--remote-header-name\fP
+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