This is an automated email from the ASF dual-hosted git repository.
rpopma pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/release-2.x by this push:
new 06fa8d8 [DOC] Fix copy-paste error in migration page
06fa8d8 is described below
commit 06fa8d882582e0f8045d3ff4e31e55f6801b83a2
Author: rpopma <rp...@apache.org>
AuthorDate: Sat Dec 25 13:08:16 2021 +0900
[DOC] Fix copy-paste error in migration page
---
src/site/xdoc/manual/migration.xml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/site/xdoc/manual/migration.xml b/src/site/xdoc/manual/migration.xml
index e976a76..c769bf3 100644
--- a/src/site/xdoc/manual/migration.xml
+++ b/src/site/xdoc/manual/migration.xml
@@ -95,7 +95,10 @@
</p>
</subsection>
<subsection name="Option 2: convert your application to the Log4j 2 API (log4j-api)">
- <p>For the most part, converting from the Log4j 1.x API to Log4j 2 should be fairly simple. Many
+ <p>
+ The other migration option involves changing your application code to use
+ the Log4j 2 API.
+ For the most part, converting from the Log4j 1.x API to Log4j 2 should be fairly simple. Many
of the log statements will require no modification. However, where necessary the following changes must be
made.</p>
<p><img src="../images/whichjar-log4j-api.png" alt="Using log4j 2 via the log4j 2.x API" /></p>
@@ -165,8 +168,6 @@
</subsection>
<subsection name="Migrating logging configurations to the Log4j 2 format">
<p>
- The other migration option involves changing your application code to use
- the Log4j 2 API.
Although the Log4j 2 configuration syntax is different than that of Log4j 1.x, most, if not all, of
the same functionality is available.
</p>