docs: improve clarity and readability of migration squashing ADR with PR review suggestions

Author: dlachaume

docs/website/adr/009-database-migration-squashing.md

@@ -14,17 +14,17 @@ Accepted
 
 ## Context
 
-Many database migrations have accumulated over time for the Mithril nodes. As the migrations are done sequentially, the resulting scheme of the database is hard to understand and maintain.
+Over time, many database migrations have accumulated in Mithril nodes. Since these migrations are applied sequentially, the resulting database schema has become difficult to understand and maintain.
 
 ## Decision
 
-To mitigate these concerns, we have decided to implement a migration squashing once we have stacked too many migrations for a store: all the existing migrations are consolidated and replaced by the equivalent new migration.
+To address this, the team decided to implement migration squashing once too many migrations have accumulated for a store. This process consolidates all existing migrations into a single, equivalent migration.
 
 ## Consequences
 
-- This applies to the migrations of all the stores of the Mithril nodes
+- This applies to the migrations of all Mithril node stores
 - A squashed migration will be applied when a database is initialized for the first time
-- A squashed migration must be optional and run only if not already applied previously with the equivalent migration sequence
-- Some nodes may have only partially applied the equivalent sequence of migrations and thus can not apply the squashed migration right away:
-  - They need to first run the migration with the latest distribution that does not ship the squashed migration so that their database is ready to play the squashed migration
-  - This distribution is associated to a squashed migration to provide a smooth user experience.
+- A squashed migration must be optional and should only run if it has not been previously applied with the equivalent migration sequence
+- Some nodes may have only partially applied the equivalent sequence of migrations and cannot apply the squashed migration immediately:
+  - They must first run the migration using the latest distribution that does not include the squashed migration, ensuring their database is prepared to apply it
+  - This distribution is associated with a squashed migration to provide a smooth user experience.