minor message correction: at user level we say method binding, not method mappin.
diff --git a/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/problem/messages.properties b/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/problem/messages.properties
index 93d1bce..c8a69d6 100644
--- a/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/problem/messages.properties
+++ b/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/problem/messages.properties
@@ -858,8 +858,8 @@
### CALLIN
1401001 = Method binding not allowed here, {0} is not a role (OTJLD 4.1(b)).
1401002 = Method binding not allowed here, role {0} is not played by a base class (OTJLD 4.1(b)).
-1401003 = Unsafe callin mapping, because lifting to role {0} may fail due to a reported binding ambiguity (OTJLD 2.3.5(c)).
-1401004 = Unsafe callin mapping, because lifting to role {0} may fail due to abstractness (OTJLD 2.3.5(c)).
+1401003 = Unsafe callin binding, because lifting to role {0} may fail due to a reported binding ambiguity (OTJLD 2.3.5(c)).
+1401004 = Unsafe callin binding, because lifting to role {0} may fail due to abstractness (OTJLD 2.3.5(c)).
1401005 = No method {0} found in type {1} to resolve method designator (OTJLD 4.1(c)).
1401006 = Method specifier "{0}" is ambiguous for the type {1}. Please use the exact method signature to disambiguate (OTJLD 4.1(c)).
1401007 = Method designator binds to a method returning {0} whereas return type {1} is specified (OTJLD 4.1(c)).