Fix repeating information about submodules

Second attamept after some Jenkins problem - fixed repeating information
about Holmes submodules and some rewording

ISSUE_ID: DOC-151

Change-Id: Idfdb0aff2fcb8227be3c7483e202917e7bdaef1c
Signed-off-by: Pawel Pawlak <pawel.pawlak3@orange.com>

diff --git a/docs/platform/architecture.rst b/docs/platform/architecture.rst
index 2fca78b..8a852e9 100644 (file)
--- a/docs/platform/architecture.rst
+++ b/docs/platform/architecture.rst
@@ -1,16 +1,6 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 
 
-Architecture
-------------
-
-Holmes comprises three modules: the rule management module, the engine management module and the data source adapter.
-
-- Holmes
-    - Rule Management Module
-    - Engine Management Module
-    - Data Source Adapter
-       
 ONAP-level Architecture
 ^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -21,11 +11,11 @@ Basically, Holmes itself is an independent component in ONAP, which means it cou
 Holmes Architecture
 ^^^^^^^^^^^^^^^^^^^
 
-Take a deep dive into Holmes, we could see it mainly consists of three modules, which are the rule management module, the engine management module and the data source adapter module respectively. 
+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.
 
 The rule management module provides interfaces for the operations (e.g. creating, updating and deleting) on the rules.
 
-The data source adapter consists of subscribers and publishers, which are used to convert the data format into the one that could be digested by Holmes and vice versa. 
+The data source adapter consists of subscribers and publishers, which are used to convert the data format into the one that could be digested by Holmes and vice versa.
 
 The engine management module is the core of Holmes. All the rules are deployed here. When alarms gets into Holmes, they will be pushed into the Drools engine and analyzed by the enabled rules one after another. When processing the alarms, a couple of attributes, such as the alarm name, the occurrence time of the alarm and so on, are utilized. Also, the topological information from A&AI is used in combination of the alarm attributes. After the root cause is identified, it will be converted into a control loop event and published to a specific DMaaP topic which is subscribed to by the Policy component.