README.md in dev-lxc-1.4.0 vs README.md in dev-lxc-1.5.0

@@ -73,12 +73,11 @@
 ├── cs
 ├── ec
 ├── manage
 ├── osc
 ├── push-jobs-server
-├── reporting
-└── sync
+└── reporting
 ```
 
 ## Update dev-lxc gem
 
 Run `gem update dev-lxc` inside the Vagrant VM platform to ensure you have the latest version.
@@ -510,15 +509,11 @@
   packages:
     server: /root/dev/chef-packages/cs/chef-server-core_12.3.1-1_amd64.deb
     manage: /root/dev/chef-packages/manage/chef-manage_2.1.1-1_amd64.deb
 #    reporting: /root/dev/chef-packages/reporting/opscode-reporting_1.5.5-1_amd64.deb
 #    push-jobs-server: /root/dev/chef-packages/push-jobs-server/opscode-push-jobs-server_1.1.6-1_amd64.deb
-#    sync: /root/dev/chef-packages/sync/chef-sync_1.0.0~rc.6-1_amd64.deb
 
-##   The chef-sync package will only be installed.
-##   chef-sync will NOT be configured since we don't know whether it should be a master or replica.
-
   api_fqdn: chef.lxc
   topology: tier
   servers:
     chef-be.lxc:
       role: backend
@@ -676,10 +671,10 @@
 	"s-" prefix on the image name.
 
     `DevLXC::Server#create_shared_image` controls the creation of a shared image.
 
     Chef packages that are common to all servers in a Chef cluster, such as chef-server-core,
-	opscode-reporting, opscode-push-jobs-server and chef-sync are installed using `dpkg` or `rpm`.
+	opscode-reporting and opscode-push-jobs-server are installed using `dpkg` or `rpm`.
 
     Note the manage package will not be installed at this point since it is not common to all
 	servers (i.e. it does not get installed on backend servers).
 
     The name of this image is built from the names and versions of the Chef packages that