diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 803e8fd..4662f63 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -722,7 +722,7 @@
     <action issue="LANG-978" type="fix" dev="sebb">Failing tests with Java 8 b128</action>
   </release>
 
-  <release version="3.3" date="2014-03-04" description="Bug fixes and and new features including: DifferenceBuilder, ClassPathUtils, RandomUtils and Jaro-Winkler String distance metric">
+  <release version="3.3" date="2014-03-04" description="Bug fixes and new features including: DifferenceBuilder, ClassPathUtils, RandomUtils and Jaro-Winkler String distance metric">
     <action issue="LANG-621" type="fix" dev="kinow" due-to="Philip Hodges, Thomas Neidhart">ReflectionToStringBuilder.toString does not debug 3rd party object fields within 3rd party object</action>
     <action issue="LANG-955" type="add" dev="britter" due-to="Adam Hooper">Add methods for removing all invalid characters according to XML 1.0 and XML 1.1 in an input string to StringEscapeUtils</action>
     <action issue="LANG-977" type="fix" dev="britter" due-to="Chris Karcher">NumericEntityEscaper incorrectly encodes supplementary characters</action>
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 a283a86..08d97f6 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.