diff --git a/docs/lcdproc-user/configuration.docbook b/docs/lcdproc-user/configuration.docbook
index 50b48de..aba33b2 100644
--- a/docs/lcdproc-user/configuration.docbook
+++ b/docs/lcdproc-user/configuration.docbook
@@ -33,8 +33,8 @@ has a section which defines how the driver acts. Those sections start with
 [drivername].
 </para>
 <para>
-<anchor id="which-driver">The drivers are activated by specifiying them in a driver= line in the
-server section, like:</anchor>
+<anchor id="which-driver" />The drivers are activated by specifiying them in a driver= line in the
+server section, like:
 </para>
 
 <example>
diff --git a/docs/lcdproc-user/drivers/lircin.docbook b/docs/lcdproc-user/drivers/lircin.docbook
index 4fdeebb..2a1ed19 100644
--- a/docs/lcdproc-user/drivers/lircin.docbook
+++ b/docs/lcdproc-user/drivers/lircin.docbook
@@ -82,9 +82,9 @@ settings for the lircin LCDproc driver.
 <term>lircrc=</term>
 <listitem>
 <para>
-<anchor id="which-lircrc">Normally all LIRC clients scan the file <filename>~/.lircrc</filename>.
+<anchor id="which-lircrc" />Normally all LIRC clients scan the file <filename>~/.lircrc</filename>.
 However, you might want to have a separate file to configure the
-LCDproc lircin driver only.</anchor>
+LCDproc lircin driver only.
 </para>
 <para>
 This option enables you to specify the file you want the lircin
diff --git a/docs/lcdproc-user/drivers/mtxorb.docbook b/docs/lcdproc-user/drivers/mtxorb.docbook
index 3d9d135..ba4484e 100644
--- a/docs/lcdproc-user/drivers/mtxorb.docbook
+++ b/docs/lcdproc-user/drivers/mtxorb.docbook
@@ -166,7 +166,7 @@
             <para>
               If the module does not immediately display its initial BIOS screen and light
               up its backlight (or light up the screen if a VFD module is being used),
-              <EMPHASIS>immediately</EMPHASIS> power down the system, disconnect the module
+              <emphasis>immediately</emphasis> power down the system, disconnect the module
 	      and connector, and double-check the modification before trying again. Do NOT
 	      leave the system on if the module does not immediately respond; module or
 	      system damage could result.