symfony
diff --git a/‎components/filesystem/lock_handler.rst
Copy file name to clipboardExpand all lines: components/filesystem/lock_handler.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎components/filesystem/lock_handler.rst
Copy file name to clipboardExpand all lines: components/filesystem/lock_handler.rst
+2-2Lines changed: 2 additions & 2 deletions
diff --git a/‎console/lockable_trait.rst
Copy file name to clipboardExpand all lines: console/lockable_trait.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎console/lockable_trait.rst
Copy file name to clipboardExpand all lines: console/lockable_trait.rst
+2-2Lines changed: 2 additions & 2 deletions
@@ -3,8 +3,8 @@ LockHandler
 
 .. versionadded:: 3.4
     The ``LockHandler`` class was deprecated in Symfony 3.4 and it will be
-    removed in Symfony 4.0. Use ``SemaphoreStore`` or ``FlockStore`` from the
-    ``Lock`` component  instead.
+    removed in Symfony 4.0. Use :ref:`SemaphoreStore <lock-store-semaphore>`
+    or :ref:`FlockStore <lock-store-flock>` from the Lock component instead.
 
 What is a Lock?
 ---------------
 
@@ -6,8 +6,8 @@ Prevent Multiple Executions of a Console Command
 
 A simple but effective way to prevent multiple executions of the same command in
 a single server is to use `locks`_. The :doc:`Lock component </components/lock>`
-provides multiple classes to create locks based on the filesystem (:ref:`FlockStore <_lock-store-flock>`),
-shared memory (:ref:`SemaphoreStore <_lock-store-semaphore>`) and even databases
+provides multiple classes to create locks based on the filesystem (:ref:`FlockStore <lock-store-flock>`),
+shared memory (:ref:`SemaphoreStore <lock-store-semaphore>`) and even databases
 and Redis servers.
 
 In addition, the Console component provides a PHP trait called ``LockableTrait``