The entire section 4.3.1. About Per-deployment Logging is not too clear. I'd suggest to rephrase it. In particular:

(1) Per-deployment logging allows a developer to configure in advance the logging configuration for their application. When the application is deployed, logging begins according to the defined configuration.
– it is not clear that without per-deployment logging configuration, the configuration from logging subsystem is used for all the applications and the server, too.

(2) An advantage is that the administrator of the JBoss EAP instance does not need to configure logging.
– this is not 100% true as the administrator must configure server logging

(3) A disadvantage is that the per-deployment logging configuration is read only on startup and so cannot be changed at runtime.
– it is not specified if startup/runtime means the server or the application startup