1 files changed, 6 insertions, 6 deletions
diff --git a/doc/appendix/guides/authentication.txt b/doc/appendix/guides/authentication.txt
index b9efbb929..0a324b718 100644
--- a/doc/appendix/guides/authentication.txt
+++ b/doc/appendix/guides/authentication.txt
@@ -1,6 +1,6 @@
 .. -*- mode: rst -*-
 
-.. _guide-authentication:
+.. _appendix-guides-authentication:
 
 ==============
 Authentication
@@ -14,7 +14,7 @@ Scenarios
    Default settings work well; machines do not float, and a per-client
    password is not required.
 
-2. :ref:`NAT Howto nat_howto`
+2. :ref:`appendix-guides-nat_howto`
 
  * Build client records in advance with ``bcfg2-admin``, setting a uuid
    for each new client.
@@ -33,7 +33,7 @@ Building bcfg2.conf automatically
 =================================
 
 This is a TCheetah template that automatically constructs per-client
-`bcfg2.conf` from the per-client metadata::
+bcfg2.conf from the per-client metadata::
 
     [communication]
     protocol = xmlrpc/ssl
@@ -43,14 +43,14 @@ This is a TCheetah template that automatically constructs per-client
     #if $self.metadata.password != None
     password = $self.metadata.password
     #else
-    password = my-password-foobar
+    password = my-password-foobat
     #end if
 
     [components]
     bcfg2 = https://localhost:6789
 
 In this setup, this will cause any clients that have uuids established
-to be set to use them in `bcfg2.conf`. It will also cause any clients
+to be set to use them in ``bcfg2.conf``. It will also cause any clients
 with passwords set to use them instead of the global password.
 
 How Authentication Works
@@ -123,7 +123,7 @@ or password only. Also a bootstrap mode will be added shortly; this
 will allow a client to authenticate with a password its first time,
 requiring a certificate all subsequent times. This behavior can be
 controlled through the use of the auth attribute in
-`Metadata/clients.xml`::
+``Metadata/clients.xml``::
 
     <Clients>
       <Client name='testclient' auth='cert'/>