minor #6893 Update entity_provider.rst (asandjivy)

This PR was submitted for the 3.1 branch but it was merged into the 2.7 branch instead (closes #6893).

Discussion
----------

Update entity_provider.rst

Commits
-------

e2c2e19 Update entity_provider.rst

security/entity_provider.rst

@@ -561,10 +561,10 @@ above). This gives us a "fresh" User object.
 But Symfony also uses the ``username``, ``salt``, and ``password`` to verify
 that the User has not changed between requests (it also calls your ``AdvancedUserInterface``
 methods if you implement it). Failing to serialize these may cause you to
-be logged out on each request. If your User implements the
+be logged out on each request. If your user implements the
 :class:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface`,
-then instead of these properties being checked, your ``isEqualTo`` method
-is simply called, and you can check whatever properties you want. Unless
+then instead of these properties being checked, your :method:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface::isEqualTo` method
+is called, and you can check whatever properties you want. Unless
 you understand this, you probably *won't* need to implement this interface
 or worry about it.