Update README.md

README.md

@@ -77,9 +77,9 @@ 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 take the right decision when it's about state managements. Handling entities states just with components can quickly lead to very intensive structural changes operation, so groups have been introduced to avoid the wild explosion of states permutations.
+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 state managements. Handling entities states just with components can quickly lead to very intensive structural changes operation, so groups have been introduced to avoid the wild explosion of states permutations.
 
-Filters have been added to make the states handling even more flexibile, avoiding incurring in heave structural changes that can happen with Svelto.ECS too.
+Filters have been added to make the states handling even more flexibile, avoiding incurring in heave structural changes that can happen with Svelto.ECS too. DOTS engineers realised this too and for this reason they have introduced the new *Enableable components* which are still less flexible than the Svelto.ECS filters.
 
 Thanks for the explicit user of Groups and Filters, the Svelto user is able to find the right trade off to handle entities states.