diff --git a/spec/src/main/asciidoc/appendixes.adoc b/spec/src/main/asciidoc/appendixes.adoc
index a6805d69..a5a3dda1 100644
--- a/spec/src/main/asciidoc/appendixes.adoc
+++ b/spec/src/main/asciidoc/appendixes.adoc
@@ -100,3 +100,4 @@ Clarified definition of the _Basic_ type
 
 Clarified the order of parameters in the _LOCATE_ function
 
+Clarified `SqlResultSetMapping` with multiple ``EntityResult``s and conflicting aliases
diff --git a/spec/src/main/asciidoc/ch03-entity-operations.adoc b/spec/src/main/asciidoc/ch03-entity-operations.adoc
index 8281edba..3a2be5a5 100644
--- a/spec/src/main/asciidoc/ch03-entity-operations.adoc
+++ b/spec/src/main/asciidoc/ch03-entity-operations.adoc
@@ -1,5 +1,5 @@
 //
-// Copyright (c) 2017, 2021 Contributors to the Eclipse Foundation
+// Copyright (c) 2017, 2022 Contributors to the Eclipse Foundation
 //
 
 == Entity Operations [[a1060]]
@@ -5625,8 +5625,9 @@ Query q = em.createNativeQuery(
 ----
 
 When the column names of the SQL result do
-not correspond to those of the object/relational mapping metadata, more
-explicit SQL result mapping metadata must be provided to enable the
+not correspond to those of the object/relational mapping metadata
+or introduce a conflict in mapping column defaults as in the example code above,
+more explicit SQL result mapping metadata must be provided to enable the
 persistence provider runtime to map the JDBC results into the expected
 objects. This might arise, for example, when column aliases must be used
 in the SQL SELECT clause when the SQL result would otherwise contain