diff --git a/Multi-machine deployment of CLAW.md b/Multi-machine deployment of CLAW.md
index ce54051..ad62b8e 100644
--- a/Multi-machine deployment of CLAW.md	
+++ b/Multi-machine deployment of CLAW.md	
@@ -1,12 +1,19 @@
 Though claw-playbook aims to be deployable to multiple machines out of the box, there is still work to be done to fully implement that. This guide describes a two machine deployment process of CLAW. 
 
-* machine_1 - Drupal (Front End)
-* machine_2 - Everything Else (Back End: Crayfish, Tomcat: Fedora, Blazegraph, Solr)
+It's suggested to create/install each service in a HOST based configuration rather than LOCALHOST or 127.0.0.1 for everything. This gives flexibility to move or expand services to different host if needed.
 
+* machine_1 - Drupal 8 (Front End)
+* machine_2 - Everything Else (Back End: Crayfish, Tomcat: Fedora, Blazegraph, Solr)
 
 ## Configuration
 ### Fedora Root URL
-One possible way to separate the fedora entries for a site or collection is to configure a unique fedora root resource.  Create that resource under too in Fedora and configure the crayfish configuration to point to it.
+If you are running mutiple sites or seperate collections, it's necessary to create seperate Root collection.
+
+I.e. http://dsu.utsc.utoronto.ca:8080/fcrepo/rest/dragomans
+     http://dsu.utsc.utoronto.ca:8080/fcrepo/rest/UTSC-Collection
+     http://dsu.utsc.utoronto.ca:8080/fcrepo/rest/20thCenturyArt
+
+One possible way to separate the fedora entries for a site or collection is to configure a unique fedora root resource. Create that resource under too in Fedora and configure the crayfish configuration to point to it.
 
 https://github.com/Islandora-Devops/claw-playbook/blob/master/inventory/vagrant/group_vars/crayfish.yml
 
@@ -18,11 +25,11 @@ crayfish_milliner_fedora_base_url: http://localhost:8080/fcrepo/rest/dragomans
 ```
 
 ### Triplestore namespace
-You may also want to separate the triplestore entries by site or collection.  There does not exist a recommended way to do this now.  You would have to modify the https://github.com/Islandora-Devops/ansible-role-blazegraph role to do this.
+You may also want to separate the triplestore entries by site or collection. There is not a recommended way to do this as of now. You would have to modify the https://github.com/Islandora-Devops/ansible-role-blazegraph role to do this.
 
-The namespace gets defined here: https://github.com/Islandora-Devops/ansible-role-blazegraph/blob/master/files/blazegraph.properties#L6 and https://github.com/Islandora-Devops/ansible-role-blazegraph/blob/master/tasks/namespace.yml#L33
+The namespace defined here: https://github.com/Islandora-Devops/ansible-role-blazegraph/blob/master/files/blazegraph.properties#L6 and https://github.com/Islandora-Devops/ansible-role-blazegraph/blob/master/tasks/namespace.yml#L33
 
-In addition, the karaf configuration need to be updated to point to this namespace:
+In addition, the karaf configuration needs to be updated to point to this namespace:
 ```
 ---
 
@@ -56,15 +63,20 @@ apix_config:
 ```
 
 
-## Deployment 
+## Deployment
+
+Deployment can be done in defferent stages.
+
+In our priliminary case, we installed/deployed everything into one HOST (Machine2-Backend), then simply move Drupal related data (site folder and sql db) to frontend host.
+
 * Deploy CLAW-PLaybook on machine_2
 * Copy the `/var/www/html/drupal` to machine_1
 
+Islandora Auth needs to be recreated.
 * Create private/public key in `/opt/islandora/auth` in machine_1
 * Replace the public key in machine_2 with the public key from machine_1 in the following places: crayfish, tomcat
 
+By default, each service listens on which ever IP is avaiable on the host (does not bind to 127.0.0.1 or local link only), all you need to do is open up or close firewall ports as needed.
+
 * In machine_2, open the tcp connection port
 * Update the activemq tcp connection
-
-
-