Use single quote instead of double quote in javadoc generation due to wonky

behaviour of javadoc tool

Worked on feature documentation

Renamed all "link to issue" to "Issue #n"

2 files changed, 4 insertions, 1 deletions

diff --git a/website/features/EqualsAndHashCode.html b/website/features/EqualsAndHashCode.html
index 3e19814c..2d2b7ec7 100644
--- a/website/features/EqualsAndHashCode.html
+++ b/website/features/EqualsAndHashCode.html
@@ -63,7 +63,7 @@
 				each other, which lombok cannot guarantee if it is only generating one of the two 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) results in warnings on the named fields.
+				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.
 				You therefore don't have to worry about typos.
 				</p>
 			</div>
diff --git a/website/features/GetterSetter.html b/website/features/GetterSetter.html
index 8b42146f..07affd69 100644
--- a/website/features/GetterSetter.html
+++ b/website/features/GetterSetter.html
@@ -46,6 +46,9 @@
 				will not be generated if there's already a method <code>getFoo(int x)</code> even though it is technically possible to make the method. This caveat
 				exists to prevent confusion. If the generation of a method is skipped for this reason, a warning is emitted instead.
 				</p><p>
+				For <code>boolean</code> fields that start with <code>is</code> or <code>has</code> immediately followed by a title-case letter, nothing is prefixed
+				to generate the getter name.
+				</p><p>
 				Any variation on <code>boolean</code> will <em>not</em> result in using the <code>is</code> prefix instead of the <code>get</code> prefix; for example,
 				returning <code>java.lang.Boolean</code> results in a <code>get</code> prefix, not an <code>is</code> prefix.
 				</p>