3 files changed, 12 insertions, 12 deletions
diff --git a/doc/client/tools/apt.txt b/doc/client/tools/apt.txt
index dba359e4a..8ce997007 100644
--- a/doc/client/tools/apt.txt
+++ b/doc/client/tools/apt.txt
@@ -2,9 +2,9 @@
 
 .. _client-tools-apt:
 
-=====================
-Bcfg2 APT Client Tool
-=====================
+===============
+APT Client Tool
+===============
 
 The APT tool allows you to configure custom options in ``bcfg2.conf``
 for systems where the tools reside in non-standard locations. The
diff --git a/doc/client/tools/index.txt b/doc/client/tools/index.txt
index a613b9d40..878a221ee 100644
--- a/doc/client/tools/index.txt
+++ b/doc/client/tools/index.txt
@@ -5,7 +5,7 @@
 Client Tool Drivers
 ===================
 
-Client tool drivers allow bcfg2 to execute configuration operations by
+Client tool drivers allow Bcfg2 to execute configuration operations by
 interfacing with platform and distribution specific tools.
 
 Tool drivers handle any reconfiguration or verification operation. So
@@ -16,21 +16,21 @@ operations.
 To write your own tool driver, to handle a new packaging format, or new
 service architecture see :ref:`development-index-writingtooldrivers`
 
-When the bcfg2 client is run, it attempts to instantiate each of these
+When the Bcfg2 client is run, it attempts to instantiate each of these
 drivers. The succeeding list of drivers are printed as a debug message
 after this process has completed. Drivers can supercede one another,
 for example, the Yum driver conflicts (and unloads) the RPM driver. This
-behavior can be overridden by running the bcfg2 client with the -D
+behavior can be overridden by running the Bcfg2 client with the -D
 flag. This flag takes a colon delimited list of drivers to use on
 the system.
 
-Currently these are the tool drivers that are distributed with bcfg2:
+Currently these are the tool drivers that are distributed with Bcfg2:
 
 Action
 ------
 
 Pre and post-install tests and actions. This driver executes commands
-and supplies status information to the bcfg2 server via the statistics
+and supplies status information to the Bcfg2 server via the statistics
 mechanism. It can also be used to prevent bundle installation when
 pre-conditions are not met. See the UsingActions page for more details.
 
diff --git a/doc/client/tools/yumng.txt b/doc/client/tools/yumng.txt
index 07706ad8b..c3b645a4f 100644
--- a/doc/client/tools/yumng.txt
+++ b/doc/client/tools/yumng.txt
@@ -74,7 +74,7 @@ RPMng.VerifyPackages()
 ----------------------
 
 The RPMng.VerifyPackages method generates a number of structures that
-record the state of the of the system compared to the bcfg2 literal
+record the state of the of the system compared to the Bcfg2 literal
 configuration retrieved from the server. These structures are mainly
 used by the RPMng.Install method.
 
@@ -150,7 +150,7 @@ From the command line::
 This produces quite a bit of output so you may want to redirect the
 output to a file for review.
 
-In the bcfg2.conf file::
+In the ``bcfg2.conf`` file::
 
     [client]
     #drivers = Action,Chkconfig,POSIX,YUMng
@@ -411,7 +411,7 @@ the clients abstract configuration. The gpg-pubkey package/instance is
 treated as an install only package. gpg-pubkey packages are installed
 by the RPMng driver with the rpm -import command.
 
-gpg-pubkey packages will be removed by bcfg2 -r packages if they are
+gpg-pubkey packages will be removed by ``bcfg2 -r packages`` if they are
 not in the clients configuration.
 
 .. code-block:: xml
@@ -752,7 +752,7 @@ For RPMng a minimal entry is
 verify_fail_action
 ^^^^^^^^^^^^^^^^^^
 
-The way I have bcfg2 configured for my development systems. This way
+The way I have Bcfg2 configured for my development systems. This way
 it reports bad, but doesn't do anything about it.
 
 .. code-block:: xml