diff --git a/docs/static/logging.asciidoc b/docs/static/logging.asciidoc
index 7cc55b02e..c4ba77b4b 100644
--- a/docs/static/logging.asciidoc
+++ b/docs/static/logging.asciidoc
@@ -1,5 +1,5 @@
 [[logging]]
-== Logging
+=== Logging
 
 Logstash emits internal logs during its operation, which are placed in `LS_HOME/logs`. The default logging level is `INFO`. 
 Logstash's logging framework is based on http://logging.apache.org/log4j/2.x/[Log4j2 framework], and many of its functionality 
@@ -11,17 +11,17 @@ Starting with 5.0, you can configure logging for a particular subsystem in Logst
 debugging issues with Elasticsearch Output, you can increase log levels just for that component. This way 
 you can reduce noise due to excessive logging and focus on the problem area effectively.
 
-=== Log file location
+==== Log file location
 
 You can specify the log file location using `--path.logs` setting.
 
-=== Log4j2 Configuration
+==== Log4j2 Configuration
 
 Logstash ships with a `log4j2.properties` file with out of the box settings. Users can modify this file directly to change the 
 rotation policy, type and other https://logging.apache.org/log4j/2.x/manual/configuration.html#Loggers[log4j2 configuration]. 
 Any change made to this file is only effective after a process restart.
 
-=== Logging APIs
+==== Logging APIs
 
 You could modify the `log4j2.properties` file and restart your Logstash, but that is both tedious and leads to unnecessary 
 downtime. Instead, you can dynamically update logging levels through the settings API. These settings are effective