diff --git a/Imaging-SUSE-Linux-With-tbku.txt b/Imaging-SUSE-Linux-With-tbku.txt
index 16e91e3..1d996bc 100644
--- a/Imaging-SUSE-Linux-With-tbku.txt
+++ b/Imaging-SUSE-Linux-With-tbku.txt
@@ -61,8 +61,9 @@
 
 As a practical matter, production Data Centers tend to keep a separate
 restore image around *for each different system variant*.  So, for
-example, you might have a separate image for your IBM servers, your
-Dell servers, your Toshiba laptops, and so on.
+example, you might find a separate image for IBM web servers, IBM
+applications servers, Dell database servers, Toshiba laptops, and so
+on.
 
 Imaging may- or may not make sense when initially installing a new
 configuration.  Say you have a system that is a web server, but you
@@ -227,7 +228,7 @@
 
               # Now it's time to mount your backup medium.  Depending
               # on your backup medium this can be one of several
-              # devices.  CD/DVDs are often found at /dev/hdc1.  USB
+              # devices.  CD/DVDs are often found at /dev/hdc.  USB
               # drives show up as SCSI drives such as /dev/sda1, and
               # so on.  You'll also need to know the type of the
               # backup medium (see: man mount for the details):
@@ -512,7 +513,7 @@
 to take some digging on your part.  Generally, you'll find
 the compiled driver modules under::
 
-    ./modules/<kernel-name>/kernel/
+    /lib/modules/<kernel-name>/kernel
 
 But, it's going to be up to you to figure out which of these your
 particular hardware actually needs.
@@ -556,4 +557,4 @@
 modifying it in any way.
 
 
-``$Id: Imaging-SUSE-Linux-With-tbku.txt,v 1.109 2008/03/13 21:25:13 tundra Exp $``
+``$Id: Imaging-SUSE-Linux-With-tbku.txt,v 1.110 2008/03/13 21:38:07 tundra Exp $``