@TimvdLippe should this issue be closed now that the PR is merged, or should this fix be backported to the 2.x branch too? @mureinik Oh right it was to the wrong branch 😭 That's my mistake. I will backport it manually
Grammar issue in ArgumentMatchers' javadoc.
[`ArgumentMatchers`' javadoc](https://static.javadoc.io/org.mockito/mockito-core/2.6.1/org/mockito/ArgumentMatchers.html) states that:

> This implementation is due static type safety imposed by java compiler. 

There's a word missing there. It should read:

> This implementation is due **to** static type safety imposed by java compiler. 

Version info:
- First noticed this on 2.5.5
- Confirmed it still existed in 2.5.6, 2.5.7 and 2.6.1
- Probably also existed in previous versions.
src/main/java/org/mockito/ArgumentMatchers.java
src/main/java/org/mockito/ArgumentMatchers.java
diff --git a/src/main/java/org/mockito/ArgumentMatchers.java b/src/main/java/org/mockito/ArgumentMatchers.java
index 56ff53311f..a28eaafe36 100644
--- a/src/main/java/org/mockito/ArgumentMatchers.java
+++ b/src/main/java/org/mockito/ArgumentMatchers.java
@@ -91,7 +91,7 @@
  * <p>
  * Matcher methods like <code>anyObject()</code>, <code>eq()</code> <b>do not</b> return matchers.
  * Internally, they record a matcher on a stack and return a dummy value (usually null).
- * This implementation is due static type safety imposed by java compiler.
+ * This implementation is due to static type safety imposed by java compiler.
  * The consequence is that you cannot use <code>anyObject()</code>, <code>eq()</code> methods outside of verified/stubbed method.
  * </p>
  *
