symfony
diff --git a/‎components/filesystem/lock_handler.rst
Copy file name to clipboardExpand all lines: components/filesystem/lock_handler.rst
+7Lines changed: 7 additions & 0 deletions b/‎components/filesystem/lock_handler.rst
Copy file name to clipboardExpand all lines: components/filesystem/lock_handler.rst
+7Lines changed: 7 additions & 0 deletions
diff --git a/‎console/lockable_trait.rst
Copy file name to clipboardExpand all lines: console/lockable_trait.rst
+4-3Lines changed: 4 additions & 3 deletions b/‎console/lockable_trait.rst
Copy file name to clipboardExpand all lines: console/lockable_trait.rst
+4-3Lines changed: 4 additions & 3 deletions
@@ -1,6 +1,13 @@
 LockHandler
 ===========
 
+.. versionadded:: 3.4
+
+    The ``LockHandler`` class has been deprecated in Symfony 3.4
+    and it will be removed in Symfony 4.0. Use ``SemaphoreStore`` or
+    ``FlockStore`` from the `Lock` component  instead.
+
+
 What is a Lock?
 ---------------
 
 
@@ -5,9 +5,10 @@ Prevent Multiple Executions of a Console Command
     The ``LockableTrait`` was introduced in Symfony 3.2.
 
 A simple but effective way to prevent multiple executions of the same command in
-a single server is to use **file locks**. The Filesystem component provides a
-:doc:`LockHandler </components/filesystem/lock_handler>` class that eases the
-creation and release of these locks.
+a single server is to use **locks**. The Lock component provides a
+:ref:`SemaphoreStore <_lock-store-semaphore>` class and a
+:ref:`FlockStore <_lock-store-flock>` class and that eases the creation and
+release of these locks.
 
 In addition, the Console component provides a PHP trait called ``LockableTrait``
 that adds two convenient methods to lock and release commands::