@@ -106,7 +106,7 @@ with the ``release()`` method.
106106
107107The trickiest part when working with expiring locks is choosing the right TTL.
108108If it's too short, other processes could acquire the lock before finishing the
109- job; it it's too long and the process crashes before calling the ``release() ``
109+ job; if it's too long and the process crashes before calling the ``release() ``
110110method, the resource will stay locked until the timeout::
111111
112112 // ...
@@ -388,8 +388,8 @@ Some file systems (such as some types of NFS) do not support locking.
388388 always be locked on the same machine or to use a well configured shared file
389389 system.
390390
391- Files on file system can be removed during a maintenance operation. For instance
392- to cleanup the ``/tmp `` directory or after a reboot of the machine when directory
391+ Files on the file system can be removed during a maintenance operation. For instance,
392+ to clean up the ``/tmp `` directory or after a reboot of the machine when a directory
393393uses tmpfs. It's not an issue if the lock is released when the process ended, but
394394it is in case of ``Lock `` reused between requests.
395395
@@ -418,7 +418,7 @@ needs space to add new items.
418418
419419.. caution ::
420420
421- Number of items stored in the Memcached must be under control. If it's not
421+ The number of items stored in Memcached must be under control. If it's not
422422 possible, LRU should be disabled and Lock should be stored in a dedicated
423423 Memcached service away from Cache.
424424
0 commit comments