OSDOCS#17381: Adding blank lines after includes

security/audit-log-view.adoc

@@ -22,6 +22,7 @@ include::modules/security-audit-log-filtering.adoc[leveloffset=+1]
 
 // Gathering audit logs
 include::modules/gathering-data-audit-logs.adoc[leveloffset=+1]
+
 //removed xrefs for hcp migration local test builds. Will update conditionals once hcp docs can be tested with live builds.
 ifndef::openshift-rosa-hcp[]
 [id="viewing-audit-logs-additional-resources"]

security/certificate_types_descriptions/etcd-certificates.adoc

@@ -15,7 +15,9 @@ etcd certificates are signed by the etcd-signer; they come from a certificate au
 The CA certificates are valid for 10 years. The peer, client, and server certificates are valid for three years.
 
 include::modules/rotating-certificate-authority.adoc[leveloffset=+1]
+
 include::modules/removing-unused-ca-bundle.adoc[leveloffset=+1]
+
 include::modules/etcd-cert-alerts-metrics-signer.adoc[leveloffset=+1]
 
 == Management

security/compliance_operator/co-management/compliance-operator-updating.adoc

@@ -28,7 +28,9 @@ Updating your {product-title} cluster to version 4.14 might cause the Compliance
 // ====
 
 include::modules/olm-preparing-upgrade.adoc[leveloffset=+1]
+
 include::modules/olm-changing-update-channel.adoc[leveloffset=+1]
+
 include::modules/olm-approving-pending-upgrade.adoc[leveloffset=+1]
 
 // [id="additional-resources-updating-the-compliance-operator"]

security/compliance_operator/compliance-operator-release-notes.adoc

@@ -262,6 +262,7 @@ This update addresses a CVE in an underlying dependency.
 +
 --
 include::snippets/fips-snippet.adoc[]
+
 --
 
 [id="compliance-operator-1-3-1-known-issue"]

security/container_security/security-compliance.adoc

@@ -13,6 +13,7 @@ standards or the organization's corporate governance framework.
 
 // Compliance and the NIST risk management model
 include::modules/security-compliance-nist.adoc[leveloffset=+1]
+
 ifndef::openshift-origin[]
 
 [role="_additional-resources"]

security/file_integrity_operator/file-integrity-operator-release-notes.adoc

@@ -72,6 +72,7 @@ This update addresses a CVE in an underlying dependency.
 +
 --
 include::snippets/fips-snippet.adoc[]
+
 --
 
 [id="file-integrity-operator-1-3-3-bug-fixes"]

security/file_integrity_operator/file-integrity-operator-understanding.adoc

@@ -14,10 +14,17 @@ Currently, only {op-system-first} nodes are supported.
 ====
 
 include::modules/file-integrity-understanding-file-integrity-cr.adoc[leveloffset=+1]
+
 include::modules/checking-file-intergrity-cr-status.adoc[leveloffset=+1]
+
 include::modules/file-integrity-CR-phases.adoc[leveloffset=+1]
+
 include::modules/file-integrity-understanding-file-integrity-node-statuses-object.adoc[leveloffset=+1]
+
 include::modules/file-integrity-node-status.adoc[leveloffset=+1]
+
 include::modules/file-integrity-node-status-success.adoc[leveloffset=+2]
+
 include::modules/file-integrity-node-status-failure.adoc[leveloffset=+2]
+
 include::modules/file-integrity-events.adoc[leveloffset=+1]

security/file_integrity_operator/file-integrity-operator-updating.adoc

@@ -9,7 +9,9 @@ toc::[]
 As a cluster administrator, you can update the File Integrity Operator on your {product-title} cluster.
 
 include::modules/olm-preparing-upgrade.adoc[leveloffset=+1]
+
 include::modules/olm-changing-update-channel.adoc[leveloffset=+1]
+
 include::modules/olm-approving-pending-upgrade.adoc[leveloffset=+1]
 
 // [id="additional-resources-updating-the-compliance-operator"]

security/pod-vulnerability-scan.adoc

@@ -28,8 +28,10 @@ namespace, so it is available to all namespaces on your {product-title} cluster.
 
 //
 include::modules/security-pod-scan-cso.adoc[leveloffset=+1]
+
 include::modules/security-pod-scan-cso-using.adoc[leveloffset=+1]
 
 //
 include::modules/security-pod-scan-query-cli.adoc[leveloffset=+1]
+
 include::modules/removing-cso-operator.adoc[leveloffset=+1]

security/seccomp-profiles.adoc

@@ -27,7 +27,9 @@ You can configure a custom seccomp profile, which allows you to update the filte
 Seccomp security profiles list the system calls (syscalls) a process can make. Permissions are broader than SELinux, which restrict operations, such as `write`, system-wide.
 
 include::modules/creating-custom-seccomp-profile.adoc[leveloffset=+2]
+
 include::modules/setting-custom-seccomp-profile.adoc[leveloffset=+2]
+
 include::modules/applying-custom-seccomp-profile.adoc[leveloffset=+2]
 
 During deployment, the admission controller validates the following: