diff --git a/docs/en/concepts-and-designs/overview.md b/docs/en/concepts-and-designs/overview.md
index df413375c41f25133672fe08230b7fc9dd2ccd26..bb9a976f9b8ab773f6dfa58723c3359a1d636b1d 100644
--- a/docs/en/concepts-and-designs/overview.md
+++ b/docs/en/concepts-and-designs/overview.md
@@ -39,12 +39,12 @@ In addition, you can integrate
## Architecture
SkyWalking is logically split into four parts: Probes, Platform backend, Storage and UI.
-
+
-- **Probe**s collect data and reformat them for SkyWalking requirements (different probes support different sources).
-- **Platform backend** supports data aggregation, analysis and streaming process covers traces, metrics, and logs.
+- **Probe**s collect telemetry data, including metrics, traces, logs and events in various formats(SkyWalking, Zipkin, OpenTelemetry, Prometheus, Zabbix, etc.)
+- **Platform backend** supports data aggregation, analysis and streaming process covers traces, metrics, logs and events. Work as Aggregator Role, Receiver Role or both.
- **Storage** houses SkyWalking data through an open/plugable interface. You can choose an existing implementation, such as
- ElasticSearch, H2, MySQL, TiDB, InfluxDB, or implement your own. Patches for new storage implementors welcome!
+ ElasticSearch, H2, MySQL, TiDB, BanyanDB, or implement your own.
- **UI** is a highly customizable web based interface allowing SkyWalking end users to visualize and manage SkyWalking data.