diff --git a/baremetal.rst b/baremetal.rst
index a78ea3d..c09050f 100644
--- a/baremetal.rst
+++ b/baremetal.rst
@@ -6,7 +6,7 @@
 
 :Author: Tim Daneliuk (tundra@tundraware.com)
 
-:Version: ``$Id: baremetal.rst,v 1.111 2014/08/23 15:31:28 tundra Exp $``
+:Version: ``$Id: baremetal.rst,v 1.112 2014/08/23 15:35:10 tundra Exp $``
 
 
 Précis
@@ -136,20 +136,26 @@
 restoring *partitions*, not disks - you can actually restore to a
 physical disk that is a different size than the one from which the
 image was taken.  Obviously, there has to be enough room for all the
-data on the new disk.  This makes it easy to lay your operating system
-down on a new, larger disk.  Do an image of the old disk, restore it
-to the new disk, and then, while still running under the ``System
-Rescue CD``, run ``parted`` or ``gparted`` to expand the partitions to
-use the additional disk space.
+data on the new disk. You can even restore to a *smaller* disk overall,
+so long as your full partitions will fit on it.  This might be the
+case if, say, you original installation's partitions did not use
+all of the disk's space.
 
-.. warning:: **Do NOT try this with a machine that boots from SAN!!!**
-             SAN-booted machines put information into their
-             bootloaders about the boot LUN's WWID and the necessary
-             configuration of HBAs to see those LUNs.  If you present
-             a bigger LUN with a different WWID, the OS bootstrap will
-             probably fail, even though you can properly restore the
-             image.  There are ways around this.  This document is not
-             the place to find these ways.
+More commonly, thought, this makes it easy to lay your operating
+system down on a new, larger disk.  Do an image of the old disk,
+restore it to the new disk, and then, while still running under the
+``System Rescue CD``, run ``parted`` or ``gparted`` to expand the
+partitions to use the additional disk space.
+
+.. warning:: **Do NOT try restoring to anything other than the original
+             disk with a machine that boots from SAN!!!** SAN-booted
+             machines put information into their bootloaders about the
+             boot LUN's WWID and the necessary configuration of HBAs
+             to see those LUNs.  If you present a bigger LUN with a
+             different WWID, the OS bootstrap will probably fail, even
+             though you can properly restore the image.  There are
+             ways around this.  This document is not the place to find
+             these ways.
 
 
 Observations