symfony
diff --git a/‎components/lock.rst
Copy file name to clipboardExpand all lines: components/lock.rst
+18-18Lines changed: 18 additions & 18 deletions b/‎components/lock.rst
Copy file name to clipboardExpand all lines: components/lock.rst
+18-18Lines changed: 18 additions & 18 deletions
@@ -87,7 +87,7 @@ you can decorate it with the ``RetryTillSaveStore``.
 
     $lock->acquire(true);
 
-Expirable Locks
+Expiring Locks
 ---------------
 
 Working with a remote ``Store`` is hard. There is now way for the remote
@@ -96,12 +96,12 @@ Due to bugs, fatal errors or segmentation fault, we can't guarantee that the
 ``release()`` method will be called, which would cause a ``resource`` to be locked
 infinitely.
 
-To fill this gap, the remote ``Stores`` provide an expirable mechanism: The lock
-is acquired for a defined amount of time (named TTL for Time To Live).
+To fill this gap, the remote ``Stores`` provide an expiration mechanism: The
+lock is acquired for a defined amount of time (named TTL for Time To Live).
 When the timeout occurred, the lock is automatically released even if the locker
 don't call the ``release()`` method.
 
-That's why, when you create a lock on an expirable ``Store``. You have to choose
+That's why, when you create a lock on an expiring ``Store``. You have to choose
 carefully the correct TTL. When too low, you take the risk to "lose" the lock
 (and someone else acquire it) whereas you don't finish your task.
 When too high and the process crash before you call the ``release()`` method,
@@ -126,7 +126,7 @@ the ``resource`` will stay lock till the timeout.
 .. tip::
 
     To avoid letting the Lock in a locking state, try to always release an
-    expirable lock by wrapping the job in a try/catch block for instance.
+    expiring lock by wrapping the job in a try/catch block for instance.
 
 When you have to work on a really long task, you should not set the TTL to
 overlap the duration of this task. Instead, the Lock Component expose a
@@ -162,22 +162,22 @@ This component provides several adapters ready to use in your applications.
 
 Here is a small summary of available ``Stores`` and their capabilities.
 
-+----------------------------------------------+--------+----------+-----------+
-| Store                                        | Scope  | Blocking | Expirable |
-+==============================================+========+==========+===========+
-| :ref:`FlockStore <lock-store-flock>`         | local  | yes      | no        |
-+----------------------------------------------+--------+----------+-----------+
-| :ref:`MemcachedStore <lock-store-memcached>` | remote | no       | yes       |
-+----------------------------------------------+--------+----------+-----------+
-| :ref:`RedisStore <lock-store-redis>`         | remote | no       | yes       |
-+----------------------------------------------+--------+----------+-----------+
-| :ref:`SemaphoreStore <lock-store-semaphore>` | local  | yes      | no        |
-+----------------------------------------------+--------+----------+-----------+
++----------------------------------------------+--------+----------+----------+
+| Store                                        | Scope  | Blocking | Expiring |
++==============================================+========+==========+==========+
+| :ref:`FlockStore <lock-store-flock>`         | local  | yes      | no       |
++----------------------------------------------+--------+----------+----------+
+| :ref:`MemcachedStore <lock-store-memcached>` | remote | no       | yes      |
++----------------------------------------------+--------+----------+----------+
+| :ref:`RedisStore <lock-store-redis>`         | remote | no       | yes      |
++----------------------------------------------+--------+----------+----------+
+| :ref:`SemaphoreStore <lock-store-semaphore>` | local  | yes      | no       |
++----------------------------------------------+--------+----------+----------+
 
 .. tip::
 
     Calling the :method:`Symfony\\Component\\Lock\\LockInterface::refresh`
-    method on a Lock created from a non expirable ``Store`` like
+    method on a Lock created from a non expiring ``Store`` like
     :ref:`FlockStore <lock-store-flock>` will do nothing.
 
 .. _lock-store-flock:
@@ -257,7 +257,7 @@ classes::
 SemaphoreStore
 ~~~~~~~~~~~~~~
 
-The SemaphoreStore uses the PHP semaphore function to lock a ``resources``.
+The SemaphoreStore uses the PHP semaphore functions to lock a ``resources``.
 
 .. code-block:: php