From 01fe91839a86c675e312293095956c07d87e935c Mon Sep 17 00:00:00 2001 From: Benedikt Ritter Date: Tue, 6 May 2014 17:57:38 +0000 Subject: [PATCH] Correct wrong documentation regarding extensibility of ImmutablePair and ImmutableTriple. This closes #13 from github. git-svn-id: https://svn.apache.org/repos/asf/commons/proper/lang/trunk@1592817 13f79535-47bb-0310-9956-ffa450edef68 --- .../java/org/apache/commons/lang3/tuple/ImmutablePair.java | 4 ++-- .../java/org/apache/commons/lang3/tuple/ImmutableTriple.java | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/main/java/org/apache/commons/lang3/tuple/ImmutablePair.java b/src/main/java/org/apache/commons/lang3/tuple/ImmutablePair.java index 0496e66d6..3e0a74065 100644 --- a/src/main/java/org/apache/commons/lang3/tuple/ImmutablePair.java +++ b/src/main/java/org/apache/commons/lang3/tuple/ImmutablePair.java @@ -21,8 +21,8 @@ package org.apache.commons.lang3.tuple; * *

Although the implementation is immutable, there is no restriction on the objects * that may be stored. If mutable objects are stored in the pair, then the pair - * itself effectively becomes mutable. The class is also not {@code final}, so a subclass - * could add undesirable behaviour.

+ * itself effectively becomes mutable. The class is also {@code final}, so a subclass + * can not add undesirable behaviour.

* *

#ThreadSafe# if both paired objects are thread-safe

* diff --git a/src/main/java/org/apache/commons/lang3/tuple/ImmutableTriple.java b/src/main/java/org/apache/commons/lang3/tuple/ImmutableTriple.java index 423c76bb3..7e4660c22 100644 --- a/src/main/java/org/apache/commons/lang3/tuple/ImmutableTriple.java +++ b/src/main/java/org/apache/commons/lang3/tuple/ImmutableTriple.java @@ -21,8 +21,8 @@ package org.apache.commons.lang3.tuple; * *

Although the implementation is immutable, there is no restriction on the objects * that may be stored. If mutable objects are stored in the triple, then the triple - * itself effectively becomes mutable. The class is also not {@code final}, so a subclass - * could add undesirable behaviour.

+ * itself effectively becomes mutable. The class is also {@code final}, so a subclass + * can not add undesirable behaviour.

* *

#ThreadSafe# if all three objects are thread-safe

*