From 7de892eeb4203e5a41b8943cd108e7c4d1e02883 Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <daniel@haxx.se>
Date: Mon, 15 Mar 2004 12:41:24 +0000
Subject: [PATCH] more formatting fixes

---
 docs/libcurl/libcurl.3 | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/docs/libcurl/libcurl.3 b/docs/libcurl/libcurl.3
index 422d56f297..54c7d0a54d 100644
--- a/docs/libcurl/libcurl.3
+++ b/docs/libcurl/libcurl.3
@@ -8,8 +8,8 @@ libcurl \- client-side URL transfers
 .SH DESCRIPTION
 This is an overview on how to use libcurl in your C programs. There are
 specific man pages for each function mentioned in here. There are also the
-\fIlibcurl-easy\fP man page, the \fIlibcurl-multi\fP man page, the
-\fIlibcurl-share\fP man page and the \fIlibcurl-the-guide\fP document for
+\fIlibcurl-easy(3)\fP man page, the \fIlibcurl-multi(3)\fP man page, the
+\fIlibcurl-share(3)\fP man page and the \fIlibcurl-the-guide\fP document for
 further reading on how to do programming with libcurl.
 
 There exist more than a dozen custom bindings that bring libcurl access to
@@ -25,10 +25,9 @@ To transfer files, you always set up an "easy handle" using
 option of using the "easy" interface, or the "multi" interface.
 
 The easy interface is a synchronous interface with which you call
-\fIcurl_easy_perform\fP and let it perform the transfer. When it is completed,
-the function return and you can continue. More details are found in the
-.BR "libcurl-easy (3)"
-man page.
+\fIcurl_easy_perform(3)\fP and let it perform the transfer. When it is
+completed, the function return and you can continue. More details are found in
+the \fIlibcurl-easy(3)\fP man page.
 
 The multi interface on the other hand is an asynchronous interface, that you
 call and that performs only a little piece of the tranfer on each invoke. It
@@ -38,7 +37,7 @@ even to easily download multiple files simultaneously using a single thread.
 
 You can have multiple easy handles share certain data, even if they are used
 in different threads. This magic is setup using the share interface, as
-described in the \fIlibcurl-share\fP man page.
+described in the \fIlibcurl-share(3)\fP man page.
 
 There is also a series of other helpful functions to use. They are:
 
@@ -102,12 +101,12 @@ Never ever call curl-functions simultaneously using the same handle from
 several threads. libcurl is thread-safe and can be used in any number of
 threads, but you must use separate curl handles if you want to use libcurl in
 more than one thread simultaneously.
-.SH "PERSISTANT CONNECTIONS"
+.SH "PERSISTENT CONNECTIONS"
 Persistent connections means that libcurl can re-use the same connection for
 several transfers, if the conditions are right.
 
-libcurl will *always* attempt to use persistent connections. Whenever you use
-\fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP, libcurl will
+libcurl will \fBalways\fP attempt to use persistent connections. Whenever you
+use \fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP, libcurl will
 attempt to use an existing connection to do the transfer, and if none exists
 it'll open a new one that will be subject for re-use on a possible following
 call to \fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP.
-- 
GitLab