Architecture section in Read the Docs

Added first draft for architecture section

Change-Id: I53f273f87c50e03b6c1621958e21f89e152539c2
Issue-Id: SDC-508
Signed-off-by: Idan Amit <ia096e@intl.att.com>

diff --git a/docs/architecture.rst b/docs/architecture.rst
index 4e20a3e..232bbf0 100644 (file)
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -30,21 +30,21 @@ The following diagram shows the high-level relationship between the system compo
 
 The SDC architecture uses the Jetty server as an application server.
 
-- The *Jetty front end*:
+- The **Jetty front end**:
    - supplies the static content of web pages, and all resources that required by the GUI
    - serves as a proxy for the REST API requests coming from the GUI
    
   Every request originating from the GUI is passed to the Jetty front-end server before it is executed.
 
-- The *Jetty back end* containes all the logic for the SDC.
+- The **Jetty back end** containes all the logic for the SDC.
 
 SDC uses two storage components: Elastic Search(ES) and Cassandra
 
-- *Elastic Search* is used to index the auditing data received from different operations in the SDC.
+- **Elastic Search** is used to index the auditing data received from different operations in the SDC.
 
-  This information can then be analyzed with Kibana. The *Kibana server* enables statistical analysis of the operations done, according to the business logic.
+  This information can then be analyzed with Kibana. The **Kibana server** enables statistical analysis of the operations done, according to the business logic.
   
-- *Cassandra* is used to store auditing data, artifacts and data model objects.
+- **Cassandra** is used to store auditing data, artifacts and data model objects.
 
 
 Capabilities