3 files changed, 5 insertions, 3 deletions

diff --git a/docs/architecture.rst b/docs/architecture.rst
index fc9e6c322..c98680a2b 100644
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -12,10 +12,12 @@ update the loop with new parameters during runtime, as well as suspending and
 restarting it.
 
 It interacts with other systems to deploy and execute the control loop. For
-example, it gets the control loop blueprint from SDC - DCAE-DS.
+example, it extracts the control loop blueprint and Policy Model(Model Driven Control Loop) 
+from CSAR distributed by SDC/DCAE-DS.
 It requests from DCAE the instantiation of microservices
 to manage the control loop flow.  Furthermore, it creates and updates multiple
-policies in the Policy Engine that define the closed loop flow.
+policies (for DCAE mS configuration and actual Control Operations) in the Policy Engine 
+that define the closed loop flow.
 
 |clamp-flow|
 
diff --git a/docs/images/architecture/distdepl.png b/docs/images/architecture/distdepl.png
index 5593f4986..0016a859c 100644
--- a/docs/images/architecture/distdepl.png
+++ b/docs/images/architecture/distdepl.png
diff --git a/docs/index.rst b/docs/index.rst
index fc0118ac9..4915722e9 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -36,7 +36,7 @@ CLAMP uses the API's exposed by the following ONAP components:
 
 - SDC : REST based interface exposed by the SDC, Distribution of service to DCAE
 - DCAE: REST based interface exposed by DCAE, Common Controller Framework, DCAE microservices onboarded (TCA, Stringmatch, Holmes (optional))
-- Policy: REST based interface (the Policy team provide a "jar" to handle the communication), both XACML and Drools PDP, APIs to App-C/VF-C/SDN-C
+- Policy: REST based interface, Policy engine target both XACML and Drools PDP, Policy Engine trigger operations to App-C/VF-C/SDN-C
 
 
 Delivery