Module Execution Config

prebid-server/pbs-modules/index.md

@@ -141,18 +141,17 @@ describe where the config file lives and what format it should take.
 
 ### 3.1 Admin Module Execution Configuration
 
-`hooks.admin.module-execution` is a key-value map, where a key is a module name and a value is a boolean. It defines whether module's hooks should be always executed or not if it's present in the execution plan. 
+`hooks.admin.module-execution` is a key-value map, where a key is a module name and a value is a boolean. It defines whether module's hooks should/should not be always executed. 
 This property can be configured on the host level at initialization as well as via account-config mechanism (a runtime config).
 The host level config has precedence over the account config.
 
 `settings.modules.require-config-to-invoke` is a host-level boolean property. When enabled it requires a runtime config to exist for a module.
 
 Both properties work together:
-
-- `hooks.admin.module-execution` is able to make the modules that doesn't require the runtime config to be always executed even if the `settings.modules.require-config-to-invoke` set to `true`
-- `hooks.admin.module-execution` allows to disable a module execution even if the module is present in the execution plan
-- if a module is not specified in the `hooks.admin.module-execution`, but present in the execution plan, it will be executed by default, except for the case when it requires a runtime config, the `settings.modules.require-config-to-invoke` set to `true`, but it doesn't have it
-- since the `settings.modules.require-config-to-invoke` does not have any impact on Entrypoint hooks, the only way to disable them altogether with other hooks of the module is disabling it configuring `hooks.admin.module-execution` on the host level
+* `hooks.admin.module-execution` is able to make the modules that doesn't require the runtime config to be always executed even if the `settings.modules.require-config-to-invoke` set to `true`
+* `hooks.admin.module-execution` allows to disable a module execution even if the module is present in the execution plan
+* if a module is not specified in the `hooks.admin.module-execution`, but present in the execution plan, it will be executed by default, except for the case when it requires a runtime config, the `settings.modules.require-config-to-invoke` set to `true`, but it doesn't have it
+* since the `settings.modules.require-config-to-invoke` does not have any impact on Entrypoint hooks, the only way to disable them altogether with other hooks of the module is disabling it configuring `hooks.admin.module-execution` on the host level
 
 Example:
 ```yaml