docs: introduction

docs/content/_index.md

@@ -2,16 +2,20 @@
 
 ## Goals of the project
 
-> Develop a few examples (not too complex) using asynchronous constructs and try to implement these examples in the two variants: using the current implementation of futures based on monadic constructs and the style that adopts gears (direct style).
-Analyze aspects such as:
+> In the realm of asynchronous programming, the Scala ecosystem offers a set of solid monads constructs to tackle complex task functionally with elegance and efficiency, like [Monix Tasks]( and [Cats ](
 >
+> However, we are assisting to the increase in adoption of continuation and coroutines in modern runtimes, either exploiting some kind of fibers support, like the project Loom with Virtual Thread in the JVM ecosystem, or via code generation, like Kotlin Coroutines.
+>
+> The goal of this project is to delve into this field through the lens of direct style, developing few examples (not too complex) leveraging the new *strawman* library [Scala Gears](https://github.com/lampepfl/gears), comparing it with Kotlin's Coroutines and the current implementation of monadic Futures, seeking to analyze aspects such as:
 > - ergonomicity of the two styles (which one results more thoughtful and/or verbose)
-> - which of the two approaches has a real advantage in adoption, and when
-> - Pros and cons of the two styles
+> - which of the two approaches has a real advantage in adoption
+> - pros and cons of the two styles
 > - how and when to use one approach rather than the other 
 > - any limitations and difficulties encountered in using them
 
-## Table of contents
+## Overview
+
+The project is built around three main example, delving from the fundamentals of the direct style framweork for simple asynchronous computation to reactive like systems. 
 
 1. [`Boundary` and `break`](./docs/01-boundaries)
 2. [Basic asynchronous constructs](./docs/02-basics)