X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fplatform%2Farchitecture.rst;h=0a5ed6cd7f9b7397c1344622ee7f1a68b08ec852;hb=3c0ce0f85b34392dd50608e7440f10a20b0279cd;hp=8a852e9588e93eaf645598c2850c9b1c9a680bab;hpb=d2491cd6801ecd030c904d2a404df65de9024126;p=holmes%2Frule-management.git

diff --git a/docs/platform/architecture.rst b/docs/platform/architecture.rst
index 8a852e9..0a5ed6c 100644
--- a/docs/platform/architecture.rst
+++ b/docs/platform/architecture.rst
@@ -1,15 +1,14 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. _architecture:
 
 
-ONAP-level Architecture
-^^^^^^^^^^^^^^^^^^^^^^^
+Holmes Architecture
+-------------------
 
-Basically, Holmes itself is an independent component in ONAP, which means it could be deployed as an ONAP-level component. In the Amsterdam release, Holmes is more generally a DCAE analytic application. It is deployed by DCAE and run as an analytic application on top of it. Also, it could be considered as a filter of the Policy component because it reduces the number of the input messages of Policy.
+Basically, Holmes itself is an independent component in ONAP, which means it could be deployed as an ONAP-level component. In the Istanbul release, Holmes is more generally a DCAE analytic application. It is deployed by DCAE and run as an analytic application on top of it. Also, it could be considered as a filter of the Policy component because it reduces the number of the input messages of Policy.
 
 .. image:: images/overall-architecture-in-onap.png
 
-Holmes Architecture
-^^^^^^^^^^^^^^^^^^^
 
 Taking a deep dive into Holmes, could observe that it mainly consists of three modules, which are: the rule management module, the engine management module and the data source adapter module respectively.