diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
index 2725c330983356ae32990f7e359748507d934602..e4b73ea2360e6459b17d3b49400f9e193473510e 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
@@ -90,5 +90,9 @@ A few things are noteworthy here:
   then, one had to define a mapping by columns instead of properties, which means, the mapping directions was reversed,
   forcing you to map database table fields on properties. This was quite confusing and the configuration is now eased as
   one can always think in the model to table mapping direction.
+- The load order of these files is determined by the load order of extensions. If multiple extensions override mapping
+  configuration of the same extbase domain classes, extension load order should be specified by :file:`ext_emconf.php`
+  constraints or dependencies using the :php:`suggests` or :php:`depends` keywords. See
+  :ref:`ext_emconf.php file<t3coreapi:extension-declaration>` for details.
 
 .. index:: TypoScript, NotScanned, ext:extbase