This is an automated email from the ASF dual-hosted git repository.
chtompki pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-lang.git
The following commit(s) were added to refs/heads/master by this push:
new 669f683 (docs) formatting nit
669f683 is described below
commit 669f6833e3356f210dd463c56d2f6544bda7439b
Author: Rob Tompkins <chtom...@apache.org>
AuthorDate: Sat Jul 11 17:24:29 2020 -0400
(docs) formatting nit
---
.../java/org/apache/commons/lang3/concurrent/locks/LockingVisitors.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/src/main/java/org/apache/commons/lang3/concurrent/locks/LockingVisitors.java
b/src/main/java/org/apache/commons/lang3/concurrent/locks/LockingVisitors.java
index 4904472..c3dce37 100644
---
a/src/main/java/org/apache/commons/lang3/concurrent/locks/LockingVisitors.java
+++
b/src/main/java/org/apache/commons/lang3/concurrent/locks/LockingVisitors.java
@@ -32,7 +32,7 @@ import org.apache.commons.lang3.function.FailableFunction;
* objects are an alternative to synchronization.
*
* Locking is preferable, if there is a distinction between read access
(multiple threads may have read access
- * concurrently), and write access (only one thread may have write access at
any given time. In comparison,
+ * concurrently), and write access (only one thread may have write access at
any given time). In comparison,
* synchronization doesn't support read access, because synchronized access is
exclusive.
*
* Using this class is fairly straightforward:
