Adjusted introduction section of the documentation.
@@ -30,17 +30,17 @@ library supports several of these possibilities.
To demonstrate how storing and retrieving domain events can be used effectively
as a persistence mechanism in an event-sourced application, this library includes
base classes for event-sourced domain entities and applications of different kinds.
-A style is suggested for event-sourced aggregates: to have command methods which
-"trigger" domain events. Triggered domain events are used to mutate the state of
-the aggregate, and then stored. The stored events of an aggregate can be retrieved
-and used to obtain the current state of the aggregate. The stored events of an
-application can also be propagated and used to project the state of the application
-into the materialised views needed by users. Stored events can also be processed
-further by other applications in the same system, and by other systems.
-
-Using this library, it is possible to define an event-sourced domain independently
-of infrastructure. It is also possible to define an entire distributed system of
-event-sourced applications independently of infrastructure. That means system
+An domain model developed using these classes will not depend on infrastructure
+("onion" archictecture). A style is suggested for event-sourced aggregates: to have
+command methods which "trigger" domain events. Triggered domain events are used to
+mutate the state of the aggregate, and then stored. The stored events of an aggregate
+can be retrieved and used to obtain the current state of the aggregate. The stored
+events of an application can also be propagated and used to project the state of
+the application into the materialised views needed by users. Stored events can also
+be processed further by other applications in the same system, and by other systems.
+
+It is also possible to define an entire application, and indeed an entire distributed
+system of event-sourced applications, independently of infrastructure. That means system
behaviours can be rapidly developed whilst running the entire system synchronously
in a single thread with a single in-memory database. And then, the system can be run
asynchronously on a cluster with durable databases, with the system effecting exactly
