aboutsummaryrefslogtreecommitdiff
path: root/src/main/java/org/apache/commons/lang3/concurrent/package-info.java
diff options
context:
space:
mode:
Diffstat (limited to 'src/main/java/org/apache/commons/lang3/concurrent/package-info.java')
-rw-r--r--src/main/java/org/apache/commons/lang3/concurrent/package-info.java2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/main/java/org/apache/commons/lang3/concurrent/package-info.java b/src/main/java/org/apache/commons/lang3/concurrent/package-info.java
index a283a86d0..08d97f6d2 100644
--- a/src/main/java/org/apache/commons/lang3/concurrent/package-info.java
+++ b/src/main/java/org/apache/commons/lang3/concurrent/package-info.java
@@ -138,7 +138,7 @@
* </p>
*
* <p>
- * Now, which one of the lazy initializer implementations should you use? First of all we have to state that is is
+ * Now, which one of the lazy initializer implementations should you use? First of all we have to state that is
* problematic to give general recommendations regarding the performance of these classes. The initializers make use of
* low-level functionality whose efficiency depends on multiple factors including the target platform and the number of
* concurrent threads. So developers should make their own benchmarks in scenarios close to their specific use cases.