diff --git a/baremetal.rst b/baremetal.rst
index 370eb95..7e6eede 100644
--- a/baremetal.rst
+++ b/baremetal.rst
@@ -6,7 +6,7 @@
 
 :Author: Tim Daneliuk (tundra@tundraware.com)
 
-:Version: ``$Id: baremetal.rst,v 1.104 2014/08/22 23:39:02 tundra Exp $``
+:Version: ``$Id: baremetal.rst,v 1.105 2014/08/22 23:43:04 tundra Exp $``
 
 
 Précis
@@ -41,7 +41,7 @@
       http://sourceforge.net/projects/systemrescuecd/
 
 You will also need access to a place to store and retrieve your images.
-In the examples below, we used a NAS nfs share, though you could also
+In the examples below, we used a NAS NFS share, though you could also
 use another local hard drive, SAN connected storage or even a USB-connected
 drive.
 
@@ -137,10 +137,8 @@
              the place to find these ways.
 
 
-Conclusions & Limitations
--------------------------
-
-- This seems to work fine in the limited configuration that was tested.
+Observations
+------------
 
 - Upside:
 
@@ -157,6 +155,12 @@
     2) Every block in the partition gets copied whether it is used or
        not.
 
+- These tests were conducted on slow, consumer grade servers connected
+  via 1Ge through an unmanaged switch. In an Enterprise class
+  networking and NAS environment, we'd expect to see considerably
+  faster backup and reimaging times, thereby minimizing server outage
+  times.
+
 - In *theory* this should also work on SAN-booted machines so long as
   the exact same LUN (WWID and size) is presented for the restore as
   was used for the backup.  However, this was not tested and theory