[Contracts] clarify the README

Author: nicolas-grekas

README.md

@@ -26,7 +26,7 @@ FAQ
 
 The abstractions in this package are useful to achieve loose coupling and
 interoperability. By using the provided interfaces as type hints, you are able
-to reuse any implementation that matches their contracts. It could be a Symfony
+to reuse any implementations that match their contracts. It could be a Symfony
 component, or another one provided by the PHP community at large.
 
 Depending on their semantics, some interfaces can be combined with autowiring to
@@ -38,13 +38,11 @@ any other means provided by your framework.)
 
 ### How is this different from PHP-FIG's PSRs?
 
-When applicable, the provided contracts are built on top of PHP-FIG's PSRs. We
-encourage relying on them and won't duplicate the effort. Still, the FIG has
-different goals and different processes. Here, we don't need to seek universal
-standards. Instead, we're providing abstractions that are compatible with the
-implementations provided by Symfony. This should actually also contribute
-positively to the PHP-FIG (of which Symfony is a member), by hinting the group
-at some abstractions the PHP world might like to take inspiration from.
+When applicable, the provided contracts are built on top of PHP-FIG's PSRs. But
+the group has different goals and different processes. Here, we're focusing on
+providing abstractions that are useful on their own while still compatible with
+implementations provided by Symfony. Although not the main target, we hope that
+the declared contracts will directly or indirectly contribute to the PHP-FIG.
 
 ### Why isn't this package split into several packages?