README.md in dev-lxc-1.1.2 vs README.md in dev-lxc-1.1.3

@@ -620,11 +620,11 @@
 The cluster's LXC config_path can be configured by setting `lxc_config_path` at the top of the
 `dev-lxc.yml` file to the desired directory.
 
 There are four image categories.
 
-1. Platform
+1. Platform Image
 
     The platform image is the first to get created and is identified by the
 	"p-" prefix on the image name.
 
     `DevLXC#create_platform_image` controls the creation of a platform image.
@@ -635,11 +635,11 @@
 	installed to provide a more typical server environment.
 	A few additional packages are also installed.
 
     *Once this platform image is created there is rarely a need to delete it.*
 
-2. Shared
+2. Shared Image
 
     The shared image is the second to get created and is identified by the
 	"s-" prefix on the image name.
 
     `DevLXC::Server#create_shared_image` controls the creation of a shared image.
@@ -654,11 +654,11 @@
 	get installed which makes this image easy to be reused by another cluster that is
 	configured to use the same Chef packages.
 
     *Since no configuration actually happens yet there is rarely a need to delete this image.*
 
-3. Unique
+3. Unique Image
 
     The unique image is the last to get created and is identified by the
 	"u-" prefix on the image name.
 
     `DevLXC::Server#create` controls the creation of a unique image.
@@ -674,10 +674,10 @@
 
     After each server is fully configured a clone of it is made resulting in the server's
 	unique image. These unique images make it very easy to quickly recreate
 	a Chef cluster from a clean starting point.
 
-4. Custom
+4. Custom Image
 
     The custom image is only created when the `snapshot` command is used and is identified
 	by the "c-" prefix on the image name.
 
     `DevLXC::Server#snapshot` controls the creation of a custom image.