diff --git a/docs/lcdproc-user/drivers/IOWarrior.docbook b/docs/lcdproc-user/drivers/IOWarrior.docbook
index b545029..4577128 100644
--- a/docs/lcdproc-user/drivers/IOWarrior.docbook
+++ b/docs/lcdproc-user/drivers/IOWarrior.docbook
@@ -97,9 +97,11 @@ as well as Darwin/MacOS X.
     Newer Linux kernels (2.6.20 and higher) provide a kernel module
     <filename>iowarrior.ko</filename> that allows controlling IOWarrior
     chips using device files.
-    Having this module loaded may hinder <application>LCDd</application>
+    <application>LCDd</application> tries to unload this kernel module
+    for <filename>libusb</filename> to be able to control IOWarrior devices.
+    If this fails, this may hinder <application>LCDd</application>
     from starting using the <code>IOWarrior</code> driver.
-    In this case, simply unload the kernel module.
+    In this case, simply unload the kernel module by hand.
   </para>
 </note>
 </para>
diff --git a/docs/lcdproc-user/drivers/lis.docbook b/docs/lcdproc-user/drivers/lis.docbook
index f56b103..c2d1a19 100644
--- a/docs/lcdproc-user/drivers/lis.docbook
+++ b/docs/lcdproc-user/drivers/lis.docbook
@@ -72,6 +72,7 @@ USB library.
     But who knowns &hellip;
   </para></listitem>
 </varlistentry>
+
 <varlistentry>
   <term>
     <command>VendorID</command> =
@@ -92,6 +93,7 @@ USB library.
     </para>
   </listitem>
 </varlistentry>
+
 <varlistentry>
   <term>
     <command>ProductID</command> =
@@ -112,6 +114,7 @@ USB library.
     </para>
   </listitem>
 </varlistentry>
+
 <varlistentry>
   <term>
     <command>Brightness</command> =
@@ -127,7 +130,6 @@ USB library.
   </para>
   </listitem>
 </varlistentry>
-
 </variablelist>
 
 </sect3>