doc: Consistency and formatting cleanups

Signed-off-by: Dan McGee <dan@archlinux.org>

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/pacman.8.txt b/doc/pacman.8.txt
index 6f071bac..c5748724 100644
--- a/doc/pacman.8.txt
+++ b/doc/pacman.8.txt
@@ -22,8 +22,8 @@ hooks, and the ability to sync your local machine with a remote ftp server to
 automatically upgrade packages. Pacman packages are a zipped tar format.
 
 Since version 3.0.0, pacman has been the frontend to linkman:libalpm[3], the
-"Arch Linux Package Management" library. This library allows alternative front
-ends to be written (for instance, a GUI front end).
+``Arch Linux Package Management'' library. This library allows alternative
+front ends to be written (for instance, a GUI front end).
 
 
 Operations
@@ -73,7 +73,7 @@ to determine which packages need upgrading. This behavior operates as follows:
 
 *-U, \--upgrade*::
 	Upgrade or add a package to the system. Either a URL or file path can be
-	specified. This is a "remove-then-add" process. See <<HCF,Handling Config
+	specified. This is a ``remove-then-add'' process. See <<HCF,Handling Config
 	Files>> for an explanation on how pacman takes care of config files.
 
 *-V, \--version*::
@@ -141,7 +141,7 @@ Options
 	the installation root setting.
 
 *\--noconfirm*::
-	Bypass any and all "Are you sure?" messages. It's not a good idea to do
+	Bypass any and all ``Are you sure?'' messages. It's not a good idea to do
 	this unless you want to run pacman from a script.
 
 *\--noprogressbar*::