Update pad-best-practices.md

Author: katarzyna-koltun-mx

content/en/docs/deployment/general/pad/pad-best-practices.md

@@ -16,6 +16,18 @@ The core concept governing configuration file processing is *last definition win
 
 This principle is crucial when managing both standard configuration files and environment variables. If a custom file is processed after environment variables, its settings will take precedence.
 
+By default, the configurations are loaded in the following order:
+
+```text
+include file("etc/StudioPro.conf")
+include file("etc/constants/defaults.conf")
+include file("etc/configurations/Default.conf")
+include file("etc/variables.conf")
+include file("etc/constants/variables.conf")
+```
+
+Because of that, for example, if the same setting is present in `StudioPro.conf` and `etc/variables.conf`, the version from `etc/variables.conf` takes precedence.
+
 ## Managing the Configuration Order
 
 To ensure your desired configuration values are applied correctly, especially when custom settings must override or be overridden by environment variables, you have two primary approaches:
@@ -42,4 +54,4 @@ In a typical Cloud deployment, it is often recommended to replace files like `St
 
 ## Supported Configuration File Formats
 
-You do not need to use the `.conf` extension for your configuration files. You can use any extension you prefer, or no extension at all. The content of the file determines how it is parsed.
+You do not need to use the `.conf` extension for your configuration files. You can use any extension you prefer, or no extension at all. The content of the file determines how it is parsed.