effect-mongodb: rephrase Design decisions Document-based and Schema-based API

Author: devmatteini

packages/effect-mongodb/README.md

@@ -54,18 +54,23 @@ Here is a list of design decisions made and principles followed while developing
    1. `Option` is used instead of `null` or `undefined` values.
    2. Some operation options, which have an impact on the shape of API response, may be replaced with stricter functions
       (e.g. `projection` in `find` operation).
-3. **Schema-based vs Document-based**: the package provides two sets of functions.
-
-   The first set is based on MongoDB's `Document` type, therefore, without any runtime validation on the shape of the
-   document, and signatures mostly identical to those of the original APIs.
+3. **Document-based API**: these API are based on MongoDB's `Document` type, therefore, without any runtime validation
+   on the shape of the document. 
+   
+   Signatures are mostly identical to those of the original APIs.
+   
    All modules belonging to this set are prefixed with `Document`, e.g. `DocumentCollection` or `DocumentFindCursor`.
-
-   The second set is based on Schema, therefore, provides runtime validation.
-   Its functions may have slightly different signatures than the original APIs, since they enforce stricter types than
-   the first set.
+   
+   These API are mainly useful for incremental adoption in existing codebases, and to allow quick prototyping when validation is redundant. 
+4. **Schema-based API**: these API are based on Schema, therefore, provides runtime validation.
+   
+   Functions may have slightly different signatures than the original APIs, since they enforce stricter types than
+   the Document-based API.
+   
    All modules belonging to this set don't have any prefix, e.g. `Collection` or `FindCursor`.
+   
    While developing the package, this set of functions is the one we put more effort into.
-4. **Error handling**: we introduced a new error type `MongoError`, derived from 
+5. **Error handling**: we introduced a new error type `MongoError`, derived from 
    [`TaggedError`](https://effect.website/docs/data-types/data/#taggederror), to wrap the original MongoDB errors.
    The current implementation is basic, but it will be extended to provide more detailed information and a finer error
    handling.