diff --git a/docs/features/README.md b/docs/features/README.md
index 25c2761d8..b8fe7c6cd 100644
--- a/docs/features/README.md
+++ b/docs/features/README.md
@@ -916,7 +916,7 @@ Starting from Imunify360 v.5.8, we introduce the overridable config which provid
 **Configs organization**:
 
 * A new directory for custom configs. The local overrides of Imunify360 config are put there: <span class="notranslate">`/etc/sysconfig/imunify360/imunify360.config.d/`</span>
-* The old config <span class="notranslate">`/etc/sysconfig/imunify360/imunify360.config`</span> is now linked to the <span class="notranslate">`imunify360.config.d/90-local.config`</span>. It contains changes made through UI as well as through CLI.
+* The old config <span class="notranslate">`/etc/sysconfig/imunify360/imunify360.config`</span> is now linked to the <span class="notranslate">`imunify360.config.d/90-local.config`</span>. It contains changes made through UI as well as through CLI. Custom config files are loaded in a lexicographical order e.g., `10_on_first_install.config` is loaded before `90-local.config` and therefore UI/CLI config updates override values from `10_on_first_install.config`, and correspondingly values put into `99-highest-priority.config` won't be overriden by UI/CLI. Note: `100-likely-an-error.config` is loaded *before* `90-local.config` (according to the lexicographical order).
 * Default Imunify360 configuration is written at `imunify360.config.defaults.example`. Modifying this config won't affect config merging behavior in any way, so please refrain from changing it.
 * Configs in that directory will override the <span class="notranslate">`imunify360.config.defaults.example`</span> and each other in lexical order. First-level "sections" (such as <span class="notranslate">`FIREWALL`</span>) are merged, while second-level "options" (such as <span class="notranslate">`FIREWALL.TCP_IN_IPv4`</span>) are replaced completely.
 * <span class="notranslate">`imunify360.config.d/10_on_first_install.config`</span> is a config that is supplied by Imunify360. Its purpose is to let us - Imunify360 developers - enable new features only on new installations without forcing existing installation to see new feature enabled on the update. This config should not be modified manually.