README.md in dev-lxc-3.1.0 vs README.md in dev-lxc-3.2.0

@@ -107,14 +107,14 @@
 ```
 mkdir -p /root/clusters/automate
 ```
 
 The following command creates a dev-lxc.yml file that defines a standalone Chef Server, Supermarket server, Compliance server,
-Chef Automate server a Job Dispatch Runner and an infrastructure node.
+Chef Automate server a Job Dispatch Runner and an infrastructure node and removes the "reporting" product from the generated configuration.
 
 ```
-dl init --chef --compliance --supermarket --automate --runners --nodes > /root/clusters/automate/dev-lxc.yml
+dl init --chef --compliance --supermarket --automate --runners --nodes --product-versions reporting:none > /root/clusters/automate/dev-lxc.yml
 ```
 
 Copy your delivery.license file to the `/root/clusters` directory.
 
 ### cluster-view
@@ -170,10 +170,10 @@
 
 ```
 dl print
 ```
 
-If you enabled local port forwarding for port 8888 in your workstation's SSH config file and configured your web browser to use `127.0.0.1:8888` for HTTP and HTTPS proxies as described in the [dev-lxc-platform README.md](https://github.com/jeremiahsnapp/dev-lxc-platform) then you should be able to browse from your workstation to any server that has a web interface using its FQDN.
+If you enabled local port forwarding for port 8888 in your workstation's SSH config file and configured your web browser to use `127.0.0.1:8888` for HTTP and HTTPS proxies as described in the [dev-lxc-platform README.md](https://github.com/jeremiahsnapp/dev-lxc-platform#accessing-the-containers-using-a-web-proxy) then you should be able to browse from your workstation to any server that has a web interface using its FQDN.
 
 For example, browse to https://automate.lxc and login with the credentials provided by `dl print-automate-credentials`.
 
 ### Manage the Cluster