diff --git a/SVVP/02.overview/00.overview.adoc b/SVVP/02.overview/00.overview.adoc
index c799971..58d3e23 100644
--- a/SVVP/02.overview/00.overview.adoc
+++ b/SVVP/02.overview/00.overview.adoc
@@ -1,64 +1,4 @@
 [[mainOverview]]
 = Overview
 
-This section provides an overview of the {project} {component-name}. It highlights the services identified by the functionalities which they provide together with a comprehensive overview of the information model forming the foundation of the developed software. The figure below outlines the architectural overview of the services.
-
-.VS System architecture overview
-image::architecture.png[]
-
-== Software services
-
-An overview of services is given in the following subchapters. For a broader description of these services refer to the link:https://esa.pages.eox.at/pdgs/documentation/SDD/index.html[Software Design Document].
-
-=== Web Client
-
-The Web Client is a browser based interactive web application which consumes the Renderer and Cache services in order to portray imagery, display metadata, enable download, and query functionality.
-
-=== Cache
-
-The purpose of this service is to provide a caching layer for the WMS interface of the Renderer service, as visualizations may be computationally costly to produce.
-
-=== Renderer
-
-The Renderer service renders the imagery to visualizations for clients and provides OGC Web Services using OpenSearch, WMS, & WCS. The WMS requests are also rendered using this service if received from the Cache. It is based on the core image like the Registrar and uses the EOxServer rendering and service capabilities.
-
-=== Registrar
-
-The purpose of the Registrar service is to register data products from different data sources. It is based on the core image like the Renderer and in addition to using EOxServer as a backend it can be extended to support different backends.
-
-=== Harvester
-
-The Harvester is a separate service based on the harvester image, and its purpose is to fetch data from existing systems, such as Spatio-Temporal asset Catalog and API, OpenSearch, S3, Swift and Local files.
-This data is collected in a STAC item form and sent down the processing pipeline.
-
-=== Scheduler
-
-The Scheduler is its own service and enables sending a signal to any component on a fixed schedule.
-
-=== Preprocessor
-
-The Preprocessor is based on the preprocessor image and it receives preprocess requests coming from the Harvester in order to translate data to a COG. After that the files are sent to the Registrar.
-
-=== Fluentd
-
-Stream oriented data collector for a unified logging layer.
-Forms a part of the EFK (Elasticsearch, Fluentd, Kibana) log storage, aggregation and visualization stack.
-
-=== Elasticsearch
-
-Real-time, distributed search engine which allows for full-text and structured search.
-Forms a part of the EFK (Elasticsearch, Fluentd, Kibana) log storage, aggregation and visualization stack.
-
-=== Kibana
-
-Data visualization frontend and dashboard for Elasticsearch.
-Forms a part of the EFK (Elasticsearch, Fluentd, Kibana) log storage, aggregation and visualization stack.
-
-=== Curator
-
-Elasticsearch Curator allows to manage Elasticsearch indices and snapshots and via filters to progressively remove indices.
-
-=== Reverse Proxy
-
-As a configured instance of Traefik software, this service provides a unified interface and routing to the provided services together with authentication and authorization facilities.
-It provides the main HTTP interface for the whole system. All requests are internally routed via a mapping configuration.
+This section provides an overview of the {project} {component-name}. It highlights ...