diff --git a/docs/static/advanced-pipeline.asciidoc b/docs/static/advanced-pipeline.asciidoc
index c5e209c5b..7687e67ef 100644
--- a/docs/static/advanced-pipeline.asciidoc
+++ b/docs/static/advanced-pipeline.asciidoc
@@ -47,7 +47,6 @@ filebeat.inputs:
 output.logstash:
   hosts: ["localhost:5044"]
 --------------------------------------------------------------------------------
-
 <1> Absolute path to the file or files that Filebeat processes.
 
 Save your changes.
@@ -732,7 +731,6 @@ filebeat.inputs:
 output.logstash:
   hosts: ["localhost:5044"]
 --------------------------------------------------------------------------------
-
 <1> Absolute path to the file or files that Filebeat processes.
 <2> Adds a field called `type` with the value `syslog` to the event.
 
diff --git a/docs/static/azure-module.asciidoc b/docs/static/azure-module.asciidoc
index b558d7eb9..1f2028771 100644
--- a/docs/static/azure-module.asciidoc
+++ b/docs/static/azure-module.asciidoc
@@ -125,7 +125,6 @@ modules:
       - "Endpoint=sb://...EntityPath=insights-logs-querystorewaitstatistics"
       - "Endpoint=sb://...EntityPath=insights-logs-timeouts"
 -----
-
 <1> The `consumer_group` (optional) is highly recommended. See <<azure_best_practices>>.
 <2> The `storage_connection` (optional) sets the Azure Blob Storage connection for tracking processing state for Event Hubs when scaling out a deployment with multiple Logstash instances. See <<scaling-blob>> for additional details.
 <3> See <<azure_best_practices>> for guidelines on choosing an appropriate number of threads.
@@ -177,7 +176,6 @@ modules:
       - ["insights-logs-querystorewaitstatistics",    "TAIL",              "dbstorewaitstats",  "true",             "Endpoint=sb://...EntityPath=insights-logs-querystorewaitstatistics"]
       - ["insights-logs-timeouts",                    "TAIL",              "dbtimeouts",        "true",             "Endpoint=sb://...EntityPath=insights-logs-timeouts"]
 -----
-
 <1> You can specify global Event Hub options. They will be overridden by any configurations specified in the event_hubs option.
 <2> See <<azure_best_practices>> for guidelines on choosing an appropriate number of threads.
 <3> The header array must be defined with name in the first position. Other options can be defined in any order. The per Event Hub configuration takes precedence. Any values not defined per Event Hub use the global config value.
diff --git a/docs/static/dead-letter-queues.asciidoc b/docs/static/dead-letter-queues.asciidoc
index 5b63cd7c5..9bb3b7936 100644
--- a/docs/static/dead-letter-queues.asciidoc
+++ b/docs/static/dead-letter-queues.asciidoc
@@ -103,7 +103,6 @@ output {
   }
 }
 --------------------------------------------------------------------------------
-
 <1> The path to the top-level directory containing the dead letter queue. This
 directory contains a separate folder for each pipeline that writes to the dead
 letter queue. To find the path to this directory, look at the `logstash.yml`
@@ -212,7 +211,6 @@ output {
   } 
 }
 --------------------------------------------------------------------------------
-
 <1> The <<plugins-inputs-dead_letter_queue,`dead_letter_queue` input>> reads from the dead letter queue.
 <2> The `mutate` filter removes the problem field called `location`.
 <3> The clean event is sent to Elasticsearch, where it can be indexed because
diff --git a/docs/static/security/logstash.asciidoc b/docs/static/security/logstash.asciidoc
index a86a24dc7..d52f494f2 100644
--- a/docs/static/security/logstash.asciidoc
+++ b/docs/static/security/logstash.asciidoc
@@ -150,7 +150,6 @@ POST _xpack/security/user/logstash_user
   "full_name" : "Kibana User for Logstash"
 }
 ---------------------------------------------------------------
-
 <1> `logstash_admin` is a built-in role that provides access to `.logstash-*`
 indices for managing configurations.
 
@@ -258,6 +257,5 @@ You configure the user and password in the `logstash.yml` configuration file:
 xpack.management.elasticsearch.username: logstash_admin_user <1>
 xpack.management.elasticsearch.password: t0p.s3cr3t
 ----------------------------------------------------------
-
 <1> The user you specify here must have the built-in `logstash_admin` role as
 well as the `logstash_writer` role that you created earlier.