Better style with <code> tags.
@@ -138,13 +138,14 @@ logger.trace(&quot;Some long-running operation returned {}&quot;, () -> expensiv
<h4>Logger Names</h4>
<p>
Most logging implementations use a hierarchical scheme for matching logger names with logging
- configuration. In this scheme the logger name hierarchy is represented by '.' characters in the
- logger name, in a fashion very similar to the hierarchy used for Java package names. For example,
- org.apache.logging.appender and org.apache.logging.filter both have org.apache.logging as their parent.
- In most cases, applications name their loggers by passing the current class's name to
- LogManager.getLogger. Because this usage is so common, Log4j 2 provides that as the default when
- the logger name parameter is either omitted or is null. For example, in all examples below the Logger will
- have a name of "org.apache.test.MyTest".
+ configuration. In this scheme the logger name hierarchy is represented by <code>'.'</code> characters
+ in the logger name, in a fashion very similar to the hierarchy used for Java package names. For example,
+ <code>org.apache.logging.appender</code> and <code>org.apache.logging.filter</code> both have
+ <code>org.apache.logging</code> as their parent. In most cases, applications name their loggers by
+ passing the current class's name to <code>LogManager.getLogger(...)</code>. Because this usage is so
+ common, Log4j 2 provides that as the default when the logger name parameter is either omitted or is
+ null. For example, in all examples below the Logger will have a name of
+ <code>"org.apache.test.MyTest"</code>.
</p>
<pre class="prettyprint linenums">package org.apache.test;
