[GNUnet-SVN] [gnurl] 03/09: docs: fix man page syntax to make test 1140 OK again

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 96186de1f740b332b66cc979d482f6dd505941fd
Author: Daniel Stenberg <address@hidden>
AuthorDate: Tue Jan 23 01:28:18 2018 +0100

    docs: fix man page syntax to make test 1140 OK again
---
 docs/libcurl/libcurl-env.3             | 4 ++--
 docs/libcurl/opts/CURLOPT_HTTPHEADER.3 | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/libcurl/libcurl-env.3 b/docs/libcurl/libcurl-env.3
index 6548cd4aa..3eb3b42e2 100644
--- a/docs/libcurl/libcurl-env.3
+++ b/docs/libcurl/libcurl-env.3
@@ -48,13 +48,13 @@ specific backend at first use. If no selection is done by 
the program using
 libcurl, this variable's selection will be used. It should be set to the full
 SSL backend name to use (case insensitve).
 .IP HOME
-When the netrc feature is used (\fBCURLOPT_NETRC(3)\fP), this variable is
+When the netrc feature is used (\fICURLOPT_NETRC(3)\fP), this variable is
 checked as the primary way to find the "current" home directory in which
 the .netrc file is likely to exist.
 .IP LOGNAME
 User name to use when invoking the ntlm-wb tool, if NTLMUSER wasn't set.
 .IP NO_PROXY
-This has the same functionality as the \fBCURLOPT_NOPROXY(3)\fP option: it
+This has the same functionality as the \fICURLOPT_NOPROXY(3)\fP option: it
 gives libcurl a comma-separated list of host name patterns for which libcurl
 should not use a proxy.
 .IP NTLMUSER
diff --git a/docs/libcurl/opts/CURLOPT_HTTPHEADER.3 
b/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
index c9f29e393..bc070915d 100644
--- a/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
+++ b/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
@@ -80,13 +80,13 @@ intend them to get sent.
 
 Custom headers are sent in all requests done by the easy handles, which
 implies that if you tell libcurl to follow redirects
-(\fBCURLOPT_FOLLOWLOCATION(3)\fP), the same set of custom headers will be sent
+(\fICURLOPT_FOLLOWLOCATION(3)\fP), the same set of custom headers will be sent
 in the subsequent request. Redirects can of course go to other hosts and thus
 those servers will get all the contents of your custom headers too.
 
 Starting in 7.58.0, libcurl will specifically prevent "Authorization:" headers
 from being sent to other hosts than the first used one, unless specifically
-permitted with the \fBCURLOPT_UNRESTRICTED_AUTH(3)\fP option.
+permitted with the \fICURLOPT_UNRESTRICTED_AUTH(3)\fP option.
 .SH DEFAULT
 NULL
 .SH PROTOCOLS

-- 
To stop receiving notification emails like this one, please contact
address@hidden