Skip to content

Commit e373890

Browse files
committed
Moved footnote to the end of the section
1 parent ef17a01 commit e373890

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

components/lock.rst

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -161,12 +161,6 @@ a lock, you can use the ``isAcquired()`` method::
161161
// We (still) own the lock
162162
}
163163

164-
165-
.. [1] Technically, the true owners of the lock are the ones that share the same instance of ``Key``,
166-
not ``Lock``. But from a user perspective, ``Key`` is internal and you will likely only be working
167-
with the ``Lock`` instance so it's easier to think of the ``Lock`` instance as being the one that
168-
is the owner of the lock.
169-
170164
Because of the fact that some lock stores have expiring locks (as seen and explained
171165
above), it is possible for an instance to lose the lock it acquired automatically::
172166

@@ -196,6 +190,11 @@ above), it is possible for an instance to lose the lock it acquired automaticall
196190
you have to use ``acquire()`` for this. The ``isAcquired()`` method is used to check
197191
if the lock has been acquired by the **current process** only!
198192

193+
.. [1] Technically, the true owners of the lock are the ones that share the same instance of ``Key``,
194+
not ``Lock``. But from a user perspective, ``Key`` is internal and you will likely only be working
195+
with the ``Lock`` instance so it's easier to think of the ``Lock`` instance as being the one that
196+
is the owner of the lock.
197+
199198
Available Stores
200199
----------------
201200

0 commit comments

Comments
 (0)