From 3b11d7c39274375df00f176e9807be77b18e5705 Mon Sep 17 00:00:00 2001
From: cj <cj@univie.ac.at>
Date: Mon, 13 Feb 2017 11:57:36 +0100
Subject: [PATCH] edit information on network diagram

---
 architecture.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/architecture.md b/architecture.md
index 26eb0a0..e9c41d3 100644
--- a/architecture.md
+++ b/architecture.md
@@ -2,6 +2,10 @@
 
 network diagram of the basic structure of the OEA platform
 
+Applications (**webserver**, **search**, **api gateway**, .. **ingest**) are represented as blocks
+representing container technology for easy engineering, deployment and scalability.
+Technology suggested to be used is noted inside and at the upper right corners of the container blocks.
+
 ## discover
 
 Clients (mobile, laptop, desktop) can request the **search** application via a **webserver**.
@@ -9,11 +13,7 @@ The **search** application is crafted to allow calls from the client to the **ap
 The **api gateway** provides an abstraction layer to the individual API of the engine used within the **index** application,
 and is also responsible for tasks as authentication and authorization.
 
-Servers might utilize direct requests to the **index** application via **webserver** and **api gateway**.
-
-**webserver**, **search**, **api gateway** and **index** are represented as blocks representing container technology for easy engineering, deployment and scalability.
-
-Technology suggested to be used is noted inside and at the upper right corners of the container blocks.
+Clients (servers) also might utilize direct requests to the **index** application via **webserver** and **api gateway**.
 
 The **metaharvest** application is configured to fetch metadata and information on LTI connectors from repositories.
 These repositories provide digital objects whose metadata and LTI connectivity is provided thru the **index** application.
-- 
GitLab