minor clarification what is meant with jit-compiled code

Author: wirthi

docs/reference-manual/native-image/MemoryManagement.md

@@ -42,7 +42,7 @@ The exact values may depend on the system configuration and the used GC.
 
 * The *maximum Java heap size* defines the upper limit for the size of the whole Java heap.
 If the Java heap is full and the GC is unable reclaim sufficient memory for a Java object allocation, the allocation will fail with the `OutOfMemoryError`.
-Note: The maximum heap size is only the upper limit for the Java heap and not necessarily the upper limit for the total amount of consumed memory, as Native Image places some data such as thread stacks, just-in-time compiled code, and internal data structures in memory that is separate from the Java heap.
+Note: The maximum heap size is only the upper limit for the Java heap and not necessarily the upper limit for the total amount of consumed memory, as Native Image places some data such as thread stacks, just-in-time compiled code (for Truffle runtime compilation), and internal data structures in memory that is separate from the Java heap.
 * The *minimum Java heap size* defines how much memory the GC may always assume as reserved for the Java heap, no matter how little of that memory is actually used.
 * The *young generation size* determines the amount of Java memory that can be allocated without triggering a garbage collection.
 
@@ -234,4 +234,4 @@ Which data is printed in detail depends on the used GC.
 
 ### Further Reading
 
-* [Memory Configuration for Native Image Build](BuildConfiguration.md#memory-configuration-for-native-image-build)
+* [Memory Configuration for Native Image Build](BuildConfiguration.md#memory-configuration-for-native-image-build)