Apply suggestions from code review

docs/usage.md

@@ -153,9 +153,9 @@ public function onUpdatePassword(UpdatePasswordEvent $event): void
 
 Please note that when using API Platform validator, there is a slight difference between version 3.3 and 3.4+.  
 
-**In version 3.3 and lower**, the validation system overwrite Symfony's. In case of a constraint violation Exception thrown, it will always respond in JSON with Hydra / JsonLD / JsonProblem, according to your configuration. This, even if the Request has been sent through a classic form. _You might want to prefer one or the other accordingly to your situation._  
+**In version 3.3 and lower**, the validation system overwrite Symfony's. In case of a constraint violation Exception thrown, it will always respond in JSON with Hydra / JSON-LD / JSON Problem, according to your configuration. This, even if the Request has been sent through a classic form. _You might want to prefer one or the other accordingly to your use-case._  
 
-**In version 3.4 and above**, this unwanted behaviour has been fixed and API Platform's validation system will check if the object (here the user) is an API Platform resource. If not, It will fallback to Symfony's error system, as it should. _Using API Platform validator is then completely fine._
+**In version 3.4 and above**, this unwanted behaviour has been fixed and API Platform validation system will check if the object (here: the user) is an API Platform resource. If not, It will fallback to Symfony's error system, as it should. _Using API Platform validator is then completely fine._
 
 ## Use your own business rules when the user is not found