anchor.diff:  
   // Type: procedure
   // ModuleID: changing-the-debezium-logging-level
  -// Title: Changing the {prodname} logging level
  +// Title: Changing the {prodname} logging level by configuring loggers
   [id="changing-logging-level"]
  -=== Changing the logging level
  +=== Setting the logging level by configuring loggers
   
   The default {prodname} logging level provides sufficient information to show whether a connector is healthy or not.
  -However, if a connector is not healthy,
  -you can change its logging level to troubleshoot the issue.
  +However, if a connector is not healthy, you can change its logging level to troubleshoot the issue.
   
   In general, {prodname} connectors send their log messages to loggers with names that match the fully-qualified name of the Java class that is generating the log message.
   {prodname} uses packages to organize code with similar or related functions.
   This means that you can control all of the log messages for a specific class or for all of the classes within or under a specific package.
   
   .Procedure
  -. Dynamically changing logging level
  -
  -Kafka Connect allows to change logging level dynamically without restarting your server. For doing that, you can send a PUT request to the admin/loggers endpoint providing the package name for which you want to change log level. For example, if by any reason you wanted to get debug information for the {prodname} Oracle connector you could send this request to your Kafka Connect:
  -
  -[source,shell,options="nowrap"]
  -----
  -curl -s -X PUT -H "Content-Type:application/json" http://localhost:8083/admin/loggers/io.debezium.connector.oracle.logminer -d '{"level": "DEBUG"}'
  -----
  -
  -.Changing logging level permanently
   
   . Open the `log4j.properties` file.
   
  
positive.code: == Configuring logging
  
  By default, {prodname} connectors write all `INFO`, `WARN`, and `ERROR` messages to the console.
  However, you can change this configuration in the following ways:
  
  * xref:changing-logging-level[Changing the logging level]
  * xref:adding-mapped-diagnostic-contexts[Adding mapped diagnostic contexts]
  
  [NOTE]
  ====
  
negative.code: 
  The containers use a `LOG_LEVEL` environment variable to set the log level for the root logger.
  You can use this environment variable to set the log level for the service running in the container.
  When you start the container and set the value of this environment variable to a log level (for example, `-e LOG_LEVEL=DEBUG`),
  all of the code within the container then uses that log level.
  
  There is also an option to override other log4j properties.  If you want to configure `log4j.rootLogger`
  