Bug 516946: Add documentation for unlikely argument type compile
problems
Change-Id: Ibd42e0df7250dcdfe5687592e021f568b761e148
diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
index d34c329..56c1c67 100644
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
+++ b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
@@ -222,7 +222,7 @@
</td>
<td valign="top">
<p>When enabled, the compiler will issue an error or warning when certain well-known Collection methods
- that take an 'Object', like e.g. 'Map#get(Object)', are used with an argument type,
+ that take an 'Object', e.g. 'Map#get(Object)', are used with an argument type,
that seems to be not related to the corresponding type argument of the Collection.</p>
</td>
<td valign="top">
@@ -234,8 +234,8 @@
<p>Perform strict analysis against the expected type</p>
</td>
<td valign="top">
- <p>By default, this analysis will apply some heuristics to determine whether or not two
- types may or may not be related, which can be changed via this option. When enabled, the heuristics will be replaced with strict compatibility checks,
+ <p>By default, this analysis will apply some heuristics to determine whether two
+ types may be related, which can be changed via this option. When enabled, the heuristics will be replaced with strict compatibility checks,
i.e., each argument that is not strictly compatible with the expected type will trigger an error or warning.</p>
</td>
<td valign="top">
