Fix documentation.

Author: GillesTourreau

README.md

@@ -18,9 +18,9 @@ The main approach of these tools is to perform unit tests without using mocking
 ### Why is this approach recommended?
 
 - Around 30% to 40% of the code in applications is located in the Data Access layer or repository components. Because it is hard to unit test, developers often skip testing,
-- resulting in lower code coverage (30%-40%).
+resulting in lower code coverage.
 - When using a mock or in-memory approach for a `DbContext`, you don't truly test the Entity Framework mapping to your database, especially additional SQL constraints like nullability, uniqueness, foreign key cascades, etc.
-- You also miss technical behaviors like transactions, connection management, etc.
+You also miss technical behaviors like transactions, connection management, etc.
 - When inserting data, it is crucial to ensure that the data in the columns are stored correctly (null/not null values, enum values to numerical values, custom or JSON serialized data, etc.).
 - If you use Entity Framework, you can detect warnings/errors raised by the `DbContext` that might not appear in logs when deploying the application.
 - You perform unit test cases, meaning you write simple tests to validate small features instead of writing complex integration tests.