[Shekharrajak]

Fixes: #2689

This how it will be rendered in UI:

Checklist

• Base your changes on 2.x branch if you are targeting Log4j 2; use main otherwise
• ./mvnw verify succeeds (the build instructions)
• Non-trivial changes contain an entry file in the src/changelog/.2.x.x directory
• Tests are provided

[rgoers]

I am not sure if our doc says it anywhere but log4j-web is not required for apps using Spring Boot.

[ramanathan1504]

The WARNING block just above already says to register Log4jServletContextListener first so it runs last at shutdown.

Suggested change

	Context listeners are destroyed in reverse initialization order.
	Registering the Log4j listener first allows other listeners to log during their `contextDestroyed()` callbacks before Log4j shuts down.
	Since Log4j 2.21.0, this works alongside automatic listener registration;
	you do not need to set `isLog4jAutoShutdownDisabled` to `true`.

[ramanathan1504]

This points back to the same WARNING block. The paragraph above already covers what to do when the parameter is true.

Suggested change

	If you only need logging during other listeners' `contextDestroyed()` callbacks,
	leave this parameter at its default value and follow the
	<<log4j-jakarta-web-installation,listener-ordering guidance>>.

[ramanathan1504]

The Log4jServletContainerInitializer fix, the Log4jShutdownOnContextDestroyedListener note and the Spring Boot note are all missing from the page today.
The listener ordering is already covered by the WARNING block in jakarta.adoc. Can we drop the two paragraphs marked inline that repeat it?