diff --git a/content/en/docs/refguide/modeling/domain-model/associations/query-over.md b/content/en/docs/refguide/modeling/domain-model/associations/query-over.md
index 6298a3c9287..bc820df495b 100644
--- a/content/en/docs/refguide/modeling/domain-model/associations/query-over.md
+++ b/content/en/docs/refguide/modeling/domain-model/associations/query-over.md
@@ -104,9 +104,9 @@ Here is an example inheritance:
 
 {{< figure src="/attachments/refguide/modeling/domain-model/associations/query-over/limitation.png" class="no-border" >}}
 
-In this example, a list of **Specializations** cannot be retrieved when using a standard by-association retrieve in a microflow if the input is the specialization.
+In this example, if a standard by-association retrieve in a microflow is used starting from a `Specialization` this will return the `Specialization` that the starting point `Specialization` points to and not the list of `Generalization` which are associated via the `Generalization_Specialization` association.
 
-However, there is a workaround for this limitation: The list of Specializations can be retrieved with a Java action using the Java API. This Java action needs two parameters: the **Specialization** and a Boolean **Reverse** via this code snippet:
+The list of `Generalization`'s that points to `Specialization` can be retrieved with a Java action using the [Runtime API](https://apidocs.rnd.mendix.com/11/runtime/com/mendix/core/Core.html#retrieveByPath(com.mendix.systemwideinterfaces.core.IContext,com.mendix.systemwideinterfaces.core.IMendixObject,java.lang.String,boolean)), as shown in this Java action which takes the `Specialization` object and a Boolean `Reverse` to indicate that the object instance is the child of the path of a self association:
 
 ```java
 public class RetrieveAsAssociatedWithB extends CustomJavaAction<java.util.List<IMendixObject>>