Add arch overview page

docs/understanding-airbyte/high-level-view.md

@@ -2,7 +2,15 @@
 description: A high level view of Airbyte's components.
 ---
 
-# High-level View
+# Architecture overview
+
+Airbyte is conceptually composed of two parts: platform and connectors. 
+
+The platform provides all the horizontal services required to configure and run data movement operations e.g: the UI, configuration API, job scheduling, logging, alerting, etc. and is structured as a set of microservices. 
+
+Connectors are independent modules which push/pull data to/from sources and destinations. Connectors are built in accordance with the [Airbyte Specification](./airbyte-specification.md), which describes the interface with which data can be moved between a source and a destination using Airbyte. Connectors are packaged as Docker images, which allows total flexibility over the technologies used to implement them. 
+
+A more concrete diagram can be seen below:
 
 ![3.048-Kilometer view](../.gitbook/assets/understanding_airbyte_high_level_architecture.png)
 
@@ -13,6 +21,6 @@ description: A high level view of Airbyte's components.
 * `Config API`: Airbyte's main control plane. All operations in Airbyte such as creating sources, destinations, connections, managing configurations, etc.. are configured and invoked from the API.
 * `Scheduler`: The scheduler takes work requests from the API and sends them to the Temporal service to parallelize. It is responsible for tracking success/failure and for triggering syncs based on the configured frequency.
 * `Temporal Service`: Manages the task queue and workflows for the Scheduler. 
-* `Worker`: The worker connects to a source, pulls the data and writes it to a destination.
+* `Worker`: The worker connects to a source connector, pulls the data and writes it to a destination.
 * `Temporary Storage`: A storage that workers can use whenever they need to spill data on a disk.