docs(config/configuration_file.md): specify the error

Author: BelpHegoR17

docs/config/configuration_file.md

@@ -21,8 +21,8 @@ Configuration files are typically located in the root of your project directory.
 The first valid configuration file found will be used. If no configuration file is found, Commitizen will use its default settings.
 
 !!! note
-    Commitizen supports  explicitly specifying a configuration file using the `--config` option, which is useful when the configuration file is not located in the project root directory.
-    When `--config` is provided, Commitizen will only load configuration from the specified file and will not search for configuration files using the default search order described above. If the specified configuration file does not exist, Commitizen will raise an error.
+    Commitizen supports explicitly specifying a configuration file using the `--config` option, which is useful when the configuration file is not located in the project root directory.
+    When `--config` is provided, Commitizen will only load configuration from the specified file and will not search for configuration files using the default search order described above. If the specified configuration file does not exist, Commitizen raises the `ConfigFileNotFound` error.If the specified configuration file exists but is empty, Commitizen raises the `ConfigFileIsEmpty` error.
 
     ```bash
     cz --config <PATH> <command>