diff --git a/Writerside/topics/Overview.md b/Writerside/topics/Overview.md
index 703084f..179789c 100644
--- a/Writerside/topics/Overview.md
+++ b/Writerside/topics/Overview.md
@@ -7,7 +7,7 @@ Services, enabling the creation of gRPC-like services directly from `.proto` fil
 essential core components for both server and client-side development, making it easier to build scalable and efficient
 RPC services.
 
-### Why Not gRPC or Other Solutions?
+## Why Not gRPC or Other Solutions?
 
 While gRPC is a widely adopted solution for RPC services, it comes with certain limitations, particularly for Kotlin
 Multiplatform development. Currently, gRPC does not have near-future support for Kotlin Multiplatform, and though
@@ -22,14 +22,14 @@ communication mechanisms or dealing with complex request schemas. It reuses exis
 makes it easier in adopting and supporting.Developers can even write clients using plain RSocket and Protobuf
 serialization libraries, making the framework more accessible and easier to implement.
 
-### Why Choose RSP?
+## Why Choose RSP?
 
 The primary goal of RSP is to support a wide range of platforms and languages. Currently, the framework supports
 Kotlin (at the moment of prototyping, for convenience), with plans to extend support to Java (via a bridge), JavaScript,
 and Python in the near future. The RSP team is actively seeking feedback before the 1.0.0 release to refine the
 framework's mental model and deliver a stable, user-friendly solution.
 
-### Why Protobuf?
+## Why Protobuf?
 
 RSP is tightly integrated with Protobuf for serialization. We believe it's the most efficient in terms of compactness
 and versioning for now. In addition, it's one of the most popular formats. While supporting other serialization