From 4094910a363c19e13e4f9f6f156fc1efd0f25078 Mon Sep 17 00:00:00 2001
From: Richard van Laak <rvanlaak@gmail.com>
Date: Fri, 14 Nov 2025 12:42:08 +0100
Subject: [PATCH 1/2] Explain 'retry' of lock stores over explicit 'no'

The documented 'no' is quite explicit with regards to whether a store does not allow userland to use the lock's blocking behavior. Using 'retry' as more subtle wording, and reiterating the rationale behind retry below the table, explains that it's the lock class itself that handles blocking support.
---
 components/lock.rst | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/components/lock.rst b/components/lock.rst
index e9fe61ecd1a..b247e785e42 100644
--- a/components/lock.rst
+++ b/components/lock.rst
@@ -390,17 +390,20 @@ The component includes the following built-in store types:
 Store                                                       Scope   Blocking  Expiring Sharing Serialization
 ==========================================================  ======  ========  ======== ======= =============
 :ref:`FlockStore <lock-store-flock>`                        local   yes       no       yes     no
-:ref:`MemcachedStore <lock-store-memcached>`                remote  no        yes      no      yes
-:ref:`MongoDbStore <lock-store-mongodb>`                    remote  no        yes      no      yes
-:ref:`PdoStore <lock-store-pdo>`                            remote  no        yes      no      yes
-:ref:`DoctrineDbalStore <lock-store-dbal>`                  remote  no        yes      no      yes
+:ref:`MemcachedStore <lock-store-memcached>`                remote  retry     yes      no      yes
+:ref:`MongoDbStore <lock-store-mongodb>`                    remote  retry     yes      no      yes
+:ref:`PdoStore <lock-store-pdo>`                            remote  retry     yes      no      yes
+:ref:`DoctrineDbalStore <lock-store-dbal>`                  remote  retry     yes      no      yes
 :ref:`PostgreSqlStore <lock-store-pgsql>`                   remote  yes       no       yes     no
 :ref:`DoctrineDbalPostgreSqlStore <lock-store-dbal-pgsql>`  remote  yes       no       yes     no
-:ref:`RedisStore <lock-store-redis>`                        remote  no        yes      yes     yes
+:ref:`RedisStore <lock-store-redis>`                        remote  retry     yes      yes     yes
 :ref:`SemaphoreStore <lock-store-semaphore>`                local   yes       no       no      no
-:ref:`ZookeeperStore <lock-store-zookeeper>`                remote  no        no       no      no
+:ref:`ZookeeperStore <lock-store-zookeeper>`                remote  retry     no       no      no
 ==========================================================  ======  ========  ======== ======= =============
 
+When the store does not support blocking locks, the Lock class will retry to acquire 
+the lock in a non-blocking way until the lock is acquired.
+
 .. tip::
 
     Symfony includes two other special stores that are mostly useful for testing:

From 5860356de1e28d9c81de8466a6a6ceccab008e05 Mon Sep 17 00:00:00 2001
From: Richard van Laak <rvanlaak@gmail.com>
Date: Fri, 14 Nov 2025 12:47:57 +0100
Subject: [PATCH 2/2] Fix formatting issue in lock.rst

---
 components/lock.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/components/lock.rst b/components/lock.rst
index b247e785e42..bc4b9504c5c 100644
--- a/components/lock.rst
+++ b/components/lock.rst
@@ -401,7 +401,7 @@ Store                                                       Scope   Blocking  Ex
 :ref:`ZookeeperStore <lock-store-zookeeper>`                remote  retry     no       no      no
 ==========================================================  ======  ========  ======== ======= =============
 
-When the store does not support blocking locks, the Lock class will retry to acquire 
+When the store does not support blocking locks, the Lock class will retry to acquire
 the lock in a non-blocking way until the lock is acquired.
 
 .. tip::