Update README.md

README.md

@@ -79,7 +79,7 @@ Svelto.ECS wasn't born just from the needs of a large team, but also as a result
 ## Why using Svelto.ECS with Unity?
 Svelto.ECS doens't use a traditional archetype model like DOTS ECS does. The novel hybrid approach based on groups instead than archetypes has been designed to allow the user to take the right decision when it comes to states management. Svelto.ECS doesn't allow archetypes to change dynamically, the user cannot add or remove components after the entity is created. Handling entities states with components can quickly lead to very intensive structural changes operations, so groups have been introduced to avoid the wild explosion of states permutations and let the user see explicitly the cost of their decisions.
 
-Filters have been added to make the states handling even more flexible adding a new dimension to sets creation. Using filters is possible to subset groups while avoiding structural changes that can happen with Svelto.ECS too. Even DOTS engineers realised this and consequentially introduced the new *Enableable components* which are still less flexible than the Svelto.ECS filters.
+Filters have been added to make the handling of multiple states even more flexible by adding a new dimension to subset creation. Using filters it's possible to subset groups while avoiding structural changes (that happens when changing groups in Svelto.ECS too). DOTS engineers also realised this and consequentially introduced the new *Enableable components* which are less flexible than the Svelto.ECS filters as they implicitly tie the subsets to enabled/disabled components, while Filters in Svelto.ECS don't
 
 Thanks to the explicit use of Groups and Filters, the Svelto user is able to find the right trade off to handle entities states.