*:http://prefetch.net/articles/yumchrootlinux
 
+This solution has a couple of trade offs the administrator should take into account.  It does come with the added performance boost of being native but there are several configuration issues which need to be taken into account:
+
+*: Consistent UID's into images (recommend using service ID's for consistency)
+*: Firewall configurations.
+
 Once your chroot image is created you will need to configure
 
 {code}
@@ -41,7 +46,7 @@
 NAMED_CHROOT= httpd=/your/chroot/loc
 {endcode}
 
-Once your startd's have been
+Once your startd's have been configured you can run jobs.
 
 {code}
 executable=your_scriptwrapper_to_kick_httpd_in_chroot.sh