[i660] canEqual is now protected instead of public.

Also fixed the total lack of canEqual in the usage examples.

1 files changed, 2 insertions, 3 deletions

diff --git a/website/features/EqualsAndHashCode.html b/website/features/EqualsAndHashCode.html
index 2ef88676..6b2507c6 100644
--- a/website/features/EqualsAndHashCode.html
+++ b/website/features/EqualsAndHashCode.html
@@ -65,9 +65,8 @@
 				return false. This is analogous to <code>java.lang.Double</code>'s equals method, and is in fact required to ensure that comparing an object
 				to an exact copy of itself returns <code>true</code> for equality.
 				</p><p>
-				If there is <em>any</em> method named either <code>hashCode</code>, <code>equals</code> or <code>canEqual</code>, regardless of
-				parameters or return type, no methods will be generated, and a warning is emitted instead. These 3 methods need to be in sync with
-				each other, which lombok cannot guarantee unless it generates all the methods, hence you always get a warning if one <em>or</em> more
+				If there is <em>any</em> method named either <code>hashCode</code> or <code>equals</code>, regardless of return type, no methods will be generated, and a warning is emitted instead. These 2 methods need to be in sync with
+				each other, which lombok cannot guarantee unless it generates all the methods, hence you always get a warning if one <em>or</em> both
 				of the methods already exist.
 				</p><p>
 				Attempting to exclude fields that don't exist or would have been excluded anyway (because they are static or transient) results in warnings on the named fields.