[
https://issues.apache.org/jira/browse/LOG4J2-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634023#comment-17634023
]
Volkan Yazici commented on LOG4J2-3510:
---------------------------------------
[~Chealer], sources to the website and the manual are available in
[GitHub|https://github.com/apache/logging-log4j2/tree/release-2.x/src/site].
For instance, you can simply click on the _"Edit this file"_ button of the
[faq.md.vm|https://github.com/apache/logging-log4j2/blob/release-2.x/src/site/markdown/faq.md.vm],
commit your changes, and create a PR. We really value website and manual
improvements. I would personally really appreciate it if you can help us with
it.
> Broken titles/sections
> ----------------------
>
> Key: LOG4J2-3510
> URL: https://issues.apache.org/jira/browse/LOG4J2-3510
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
> Reporter: Philippe Cloutier
> Assignee: Ralph Goers
> Priority: Major
> Fix For: 2.18.0
>
>
> Log4j's website contains several broken titles (section headers). This seems
> most prevalent in [the _Migrating from Log4j 1.x to 2.x_
> page|https://logging.apache.org/log4j/2.x/manual/migration.html], but can
> also be seen on the homepage. For example, the following, which is presumably
> supposed to generate a level 4 "API Compatibility" header, shows raw:
> {code:java}
> #### API Compatibility
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
