README.md in kitchen-lxd_cli-2.0.0 vs README.md in kitchen-lxd_cli-2.0.1

@@ -63,11 +63,10 @@
 #  lxd_proxy_destroy: true
 #  lxd_proxy_verify: true
 #  lxd_proxy_update: true
 #  lxd_proxy_path: "~/.lxd_proxy"
 #  lxd_proxy_github_url: "-b development --single-branch https://github.com/bradenwright/cookbook-lxd_polipo
-#  enable_wait_for_ssh_login: true
   mount:
     rails_mongodb_app:
       local_path: "/mylocalpath"
       container_path: "/mnt/rails_mongodb_app"
   domain_name: localdomain
@@ -77,10 +76,11 @@
   verifier_path: "/opt/verifier"
   publish_image_name: "kitchen-base-ubuntu-1404"
   use_publish_image: true
   publish_image_before_destroy: true
   publish_image_overwrite: true
+  lxd_unique_name: true
   enable_wait_for_ssh_login: false
   username: kitchen-user
 
 
 
@@ -158,10 +158,11 @@
 *  lxd_proxy_destroy
 *  lxd_proxy_verify
 *  lxd_proxy_update
 *  lxd_proxy_path
 *  lxd_proxy_github_url
+*  lxd_unique_name
 
 ### public_key_path
 
 can be manual set otherwise is derived by default based 
 ~/.ssh/ directory, specifically the setting is derived by searching for:
@@ -354,9 +355,13 @@
 Default is https://github.com/bradenwright/cookbook-lxd_polipo basically if can be overridden so that whatever repo is used.  Idea being that someone can customize the polipo install I have setup.  Or try to use a completely different type of proxy (not polipo) as long as the git-repo would create a proxy by running `bundle install` and `bundle exec kitchen converge`.  Also if you don't want to use github if you setup a container named proxy-ubuntu-1404, ie `lxc info proxy-ubuntu-1404` returns a box it will be used.
 
 ```yaml
 lxd_proxy_github_url: "-b development --single-branch https://github.com/bradenwright/cookbook-lxd_polipo"
 ```
+
+### lxd_unique_name
+
+Default is true.  If true a file is written to .kitchen/<instance_name>.lxd with the unique name.  This file is used to identify the lxd instance.  If you don't want this feature, set to false
 
 ### enable_wait_for_ssh_login
 
 Default is false.  If set to true container will loop until it can login to ssh, this ensures that ssh is ready before kitchen moves on to converging.  It's false by default b/c it slows things down, and I only seemed to need it after using publishing option.  Specifically if I didn't remove /root/.ssh, if I did remove /root/.ssh before publishing, then the sleep/time to setup ssh_public_key seemed to wait long enough that kitchen converge was not timing out.