diff --git a/docs/sections/services/mapper/installation.rst b/docs/sections/services/mapper/installation.rst
index d8d0039..af4189f 100644
--- a/docs/sections/services/mapper/installation.rst
+++ b/docs/sections/services/mapper/installation.rst
@@ -11,12 +11,10 @@
 
 VES-Mapper can be deployed individually though it will throw errors if it can't reach to DMaaP instance's APIs. To test it functionally, DMaaP is the only required prerequisite outside DCAE. As VES-Mapper is integrated with Consul / CBS, it fetches the initial configuration from Consul.
 
-**Note:** Currently VES-Mapper fetches configuration from Consul only during initialization. It does not periodically refresh the local configuration by getting updates from Consul. This is planned for E release.
-
 **Blueprint/model/image**
 
 VES-Mapper blueprint is available @ 
-https://git.onap.org/dcaegen2/services/mapper/tree/UniversalVesAdapter/dpo/blueprints/k8s-vesmapper.yaml-template.yaml?h=elalto
+https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-ves-mapper.yaml?h=guilin
 
 VES-Mapper docker image is available in Nexus repo @ `nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:latest <nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:latest>`_
 
@@ -37,13 +35,26 @@
 
 For this step, DCAE's Cloudify instance should be in running state. Transfer blueprint file in DCAE bootstrap POD under /blueprints directory. Log-in to the DCAE bootstrap POD's main container.
 
+.. note::
+  For doing this, we should run the below commands
+
+  * To get the bootstrap pod name, run this: kubectl get pods -n onap | grep bootstrap
+  * To transfer blueprint file in bootstrap pod, run this: kubectl cp <source file path> <bootstrap pod>:/blueprints -n onap
+  * To login to bootstrap pod name, run this: kubectl exec -it <bootstrap pod> bash -n onap
+
+.. note::
+  Verify the below versions before validate blueprint
+
+  * The version of the plugin used is different from "cfy plugins list", update the blueprint import to match.
+  * If the tag_version under inputs is old, update with the latest
+
 Validate blueprint
 
-    ``cfy blueprints validate /blueprints/k8s-vesmapper.yaml-template.yaml``
+    ``cfy blueprints validate /blueprints/k8s-ves-mapper.yaml``
 
 Use following command for validated blueprint to upload:
 
-	``cfy blueprints upload -b ves-mapper /blueprints/k8s-vesmapper.yaml-template.yaml``
+	``cfy blueprints upload -b ves-mapper /blueprints/k8s-ves-mapper.yaml``
 
 *d. Create the Deployment* 
 After VES-Mapper's validated blueprint is uploaded,  create Cloudify Deployment by following command
@@ -54,10 +65,25 @@
 
   ``cfy executions start -d ves-mapper install``
 
+To undeploy running ves-mapper, follow the below steps
+
+*a.  cfy uninstall ves-mapper -f*
+
+.. note::
+  The deployment uninstall will also delete the blueprint. In some case you might notice 400 error reported indicating active deployment exist such as below.
+
+  Ex: An error occurred on the server: 400: Can't delete deployment ves-mapper - There are running or queued executions for this deployment. Running executions ids:      d89fdd0c-8e12-4dfa-ba39-a6187fcf2f18
+
+*b.  In that case, cancel the execution ID then run uninstall as below*
+
+.. code-block:: bash
+
+  cfy executions cancel <Running executions ID>
+  cfy uninstall ves-mapper
 
 **2.To run on standalone mode**
 
 Though this is not a preferred way, to run VES-Mapper container on standalone mode using local configuration file carried in the docker image, following docker run command can be used.
  
-    ``docker run -d   nexus3.onap.org:10003/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.0.1``
+    ``docker run -d   nexus3.onap.org:10003/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.1.0``