minor symfony#14972 [Lock] Update lock documentation for more clarity (Mohameth)

This PR was submitted for the 5.2 branch but it was merged into the 4.4 branch instead.

Discussion
----------

[Lock] Update lock documentation for more clarity

In response to symfony#9367, I also had some trouble understanding the meaning.

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `5.x` for features of unreleased versions).

-->

Commits
-------

6c8bbd6 Update lock documentation for more clarity

Author: javiereguiluz

components/lock.rst

@@ -62,9 +62,10 @@ method can be safely called repeatedly, even if the lock is already acquired.
 .. note::
 
     Unlike other implementations, the Lock Component distinguishes locks
-    instances even when they are created for the same resource. If a lock has
-    to be used by several services, they should share the same ``Lock`` instance
-    returned by the ``LockFactory::createLock`` method.
+    instances even when they are created for the same resource. It means that for
+    a given scope and resource one lock instance can be acquired multiple times. 
+    If a lock has to be used by several services, they should share the same ``Lock``
+    instance returned by the ``LockFactory::createLock`` method.
 
 .. tip::