README.md in dev-lxc-2.1.0 vs README.md in dev-lxc-2.2.0

@@ -112,25 +112,25 @@
 Create the [dev-lxc.yml config file](docs/configuration.md) for the cluster.
 
 First, create an arbitrary directory to hold the dev-lxc.yml file.
 
 ```
-mkdir -p /root/dev/clusters/automate
+mkdir -p /root/work/clusters/automate
 ```
 
 Then use the `init` subcommand to generate a sample configuration using the available options. Run `dl help init` to see what options are available.
 
 The following command configures a standalone Chef Server, a Chef Automate server and a build node.
 
 ```
-dl init --chef --automate --build-nodes -f /root/dev/clusters/automate/dev-lxc.yml
+dl init --chef --automate --build-nodes -f /root/work/clusters/automate/dev-lxc.yml
 ```
 
 We can easily append additional configurations to this file. For example, the following command appends an infrastructure node.
 
 ```
-dl init --nodes -a -f /root/dev/clusters/automate/dev-lxc.yml
+dl init --nodes -a -f /root/work/clusters/automate/dev-lxc.yml
 ```
 
 Edit the dev-lxc.yml file:
 
 * Delete the `reporting` product from the Chef Server config since we will be using Chef Automate's Visibility.
@@ -148,13 +148,13 @@
 The right pane updates every 0.5 seconds with the cluster's status provided by `dev-lxc status`.
 
 The session's second window is named "shell". It opens in the same directory as the
 cluster's `dev-lxc.yml` file and is useful for attaching to a server to perform system administration tasks.
 
-See the [Usage docs](docs/usage.md) for more information about how to close/kill Byobu sessions.
+See the [usage docs](docs/usage.md) for more information about how to close/kill Byobu sessions.
 
 ```
-cluster-view /root/dev/clusters/automate
+cluster-view /root/work/clusters/automate
 ```
 
 #### Specifying a Subset of Servers
 
 Many dev-lxc subcommands can act on a subset of the cluster's servers by specifying a regular expression that matches the desired server names.