diff --git a/README.md b/README.md
index f0edbba..0f5eef8 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ Real Entity-Component-System for c#. Enables to write encapsulated, decoupled, m
 
 ## Why using Svelto.ECS with Unity?
 
-_Svelto.ECS wasn’t born just from the needs of a large team using Unity on several projects, but also as result of years of reasoning behind software engineering applied to game development and that’s why the main Svelto.ECS goals are currently different than the ones set by Unity ECS. They may converge one day, but at the moment they are different enough to justify the on going development of Svelto.ECS. The biggest difference is that Svelto.ECS primary objective is not performance. Performance gain is just one of the benefits in using Svelto.ECS, as the ECS design in general helps to write cache-friendly code. All that said the main reasons why Svelto.ECS has been written orbit around the shifting of paradigm from Object Oriented Programming, the consequent improvement of the code design and maintainability, the approachability by junior programmers that won’t need to worry too much about the architecture and can focus on the solution of the problems thanks to the rigid directions that the framework gives. Svelto.ECS is the result of years of iterating the ECS design applied to real game development, with the intent to be "junior coder proof"._
+_Svelto.ECS wasn't born just from the needs of a large team, but also as result of years of reasoning behind software engineering applied to game development(*). Compared to Unity.ECS the main goals and reasons to exist of Svelto.ECS are different enough to justify its on going development. Svelto.ECS hasn't been built just to develop faster code, it has been built to help develop better code. Performance gain is one of the benefits in using Svelto.ECS, as ECS in general is a great way to write cache-friendly code, but the main reasons why Svelto.ECS has been written orbit around the shifting of paradigm from Object Oriented Programming, the consequent improvement of the code design and maintainability, the approachability by junior programmers that won't need to worry too much about the architecture and can focus on the solution of the problems thanks to the rigid directions that the framework gives. Svelto.ECS is the result of years of iterating the ECS design applied to real game development, with the intent to be "junior coder proof"._
 
 You can find a working example to learn how to use the framework here: