Update README.md

README.md

@@ -4,20 +4,19 @@
 |--|--|
 |![Warning](./images/warning_icon.png)| DISCLAIMER <p> This setup has been tested on Linux and OSX; it __may__ not work on Windows.            |
 
-Vagrantfile and additional configuration to deploy a development environment like the one shown in the picture:
-
 ![Dev_Environment_Topology](./images/DevEnvironment.png)
 
-The full environment consists of:
-- 1 Ubuntu VM for the Ansible control node
+The full mini-lab consists of:
+
+- 1 Ubuntu VM (for the Ansible control node)
 - 3 fully-interconnected Juniper vSRXs
 
 The VM specifications are as follows:
 
-* vSRXs have 2 vCPUs and 4GB  RAM
-* The Ansible control node has 2vCPUs and 1GB RAM
+* The vSRXs each have 2 vCPUs and 4GB  RAM
+* The Ansible control node has 2 vCPUs and 1GB RAM
 
-In order to keep the initial demands on the host machine low, only one vSRX will be spun up; the second and third vSRX's are commented out in the relevant Vagrant control file.
+In order to keep the initial demands on the host machine low, only one vSRX will be spun up; the second and third vSRX's are commented out in the relevant Vagrant control file (imaginatively called `Vagrantfile`).
 
 ## What's in this repository?
 
@@ -66,9 +65,12 @@ This is the framework which allows users to run virtual devices on Windows, Linu
 Download and install VirtualBox from: 
 https://www.virtualbox.org/wiki/Downloads
 
+|![Warning](./images/warning_icon.png)| DISCLAIMER <p> VirtualBox does not work on M1 Macs.            |
+
 ### Vagrant
 
-Vagrant uses node and connectivity definitions in a `Vagrantfile` to orchestrate the creation - using Virtualbox - of the test network.
+Vagrant uses node and connectivity definitions in a control file (by default called `Vagrantfile`) to orchestrate the creation of multi-device virtual environments. It can use several such environments - we are going to use VirtualBox.
+
 
 Download Vagrant from:
 https://www.vagrantup.com/downloads.html