Cleanup listing blocks

Author: jboxman

modules/adding-custom-notification-banners.adoc

@@ -30,7 +30,6 @@ spec:
     text: Optional link text
   color: '#fff'
   backgroundColor: '#0088ce'
-
 ----
 <1> Valid location settings are `BannerTop`, `BannerBottom`, and `BannerTopBottom`.
 

modules/builds-strategy-custom-environment-variables.adoc

@@ -21,7 +21,6 @@ customStrategy:
   env:
     - name: "HTTP_PROXY"
       value: "http://myproxy.net:5187/"
-
 ----
 +
 . To manage environment variables defined in the build configuration, enter the following command:

modules/builds-strategy-pipeline-environment-variables.adoc

@@ -26,7 +26,6 @@ jenkinsPipelineStrategy:
   env:
     - name: "FOO"
       value: "BAR"
-
 ----
 
 You can also manage environment variables defined in the build configuration with the `oc set env` command.

modules/cluster-logging-deploying-about.adoc

@@ -26,6 +26,7 @@ Memory and CPU::
 You can adjust both the CPU and memory limits for each component by modifying the `resources`
 block with valid memory and CPU values:
 
+[source,yaml]
 ----
 spec:
   logStore:
@@ -73,6 +74,7 @@ spec:
 Elasticsearch storage::
 You can configure a persistent storage class and size for the Elasticsearch cluster using the `storageClass` `name` and `size` parameters. The Red Hat OpenShift Logging Operator creates a persistent volume claim (PVC) for each data node in the Elasticsearch cluster based on these parameters.
 
+[source,yaml]
 ----
   spec:
     logStore:
@@ -91,6 +93,7 @@ requests "200G" of "gp2" storage. Each primary shard will be backed by a single
 ====
 Omitting the `storage` block results in a deployment that includes ephemeral storage only.
 
+[source,yaml]
 ----
   spec:
     logStore:
@@ -135,6 +138,7 @@ You can select which log collector is deployed as a daemon set to each node in t
 Curator schedule::
 You specify the schedule for Curator in the link:https://en.wikipedia.org/wiki/Cron[cron format].
 
+[source,yaml]
 ----
   spec:
     curation:
@@ -150,6 +154,7 @@ You specify the schedule for Curator in the link:https://en.wikipedia.org/wiki/C
 The following is an example of a `ClusterLogging` custom resource modified using the options previously described.
 
 .Sample modified `ClusterLogging` custom resource
+[source,yaml]
 ----
 apiVersion: "logging.openshift.io/v1"
 kind: "ClusterLogging"

modules/cluster-logging-kibana-limits.adoc

@@ -43,7 +43,6 @@ spec:
           requests:
             cpu: 100m
             memory: 100Mi
-
 ---- 
 <1> Specify the CPU and memory limits to allocate for each node.
 <2> Specify the CPU and memory limits to allocate to the Kibana proxy.

modules/cluster-logging-updating-logging.adoc

@@ -102,7 +102,6 @@ $ oc exec -n openshift-logging -c elasticsearch elasticsearch-cdm-1pbrl44l-1-55b
   "status" : "green",
 }
 ...
-
 ----
 
 .. Ensure that the Elasticsearch cron jobs are created:

modules/cnf-gathering-data-about-cluster-using-must-gather.adoc

@@ -20,7 +20,6 @@ The Performance Profile Creator (PPC) tool requires `must-gather` data. As a clu
 . Run `must-gather` on your cluster:
 +
 [source,terminal]
-
 ----
 $ oc adm must-gather --image=<PAO_image> --dest-dir=<dir>
 ----

modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc

@@ -80,6 +80,7 @@ Currently, not all tests run selectively on the nodes belonging to the pool.
 == Running the tests
 Assuming the `kubeconfig` file is in the current folder, the command for running the test suite is:
 
+[source,terminal]
 ----
 $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/test-run.sh
 ----
@@ -101,6 +102,7 @@ Additionally, you can set the following environment variables for latency tests:
 
 To perform the latency tests, run the following command:
 
+[source,termina]
 ----
 $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/test-run.sh
 ----
@@ -117,7 +119,7 @@ You must run the latency test in discovery mode. For more information, see the D
 running /0_config.test -ginkgo.focus=Latency
 ----
 .Example output
-[source, terminal]
+[source,terminal]
 ----
 I1106 15:09:08.087085       7 request.go:621] Throttling request took 1.037172581s, request: GET:https://api.cnf12.kni.lab.eng.bos.redhat.com:6443/apis/autoscaling.openshift.io/v1?timeout=32s
 Running Suite: Performance Addon Operator configuration
@@ -191,7 +193,7 @@ You can run only the latency test using the `-ginkgo.focus` parameter.
 
 To run only the latency test, you must provide the `-ginkgo.focus` parameter and the `PERF_TEST_PROFILE` environment variable that contains the name of the performance profile that needs to be tested. For example:
 
-[source, terminal]
+[source,terminal]
 ----
 $ docker run --rm -v $KUBECONFIG:/kubeconfig -e KUBECONFIG=/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=20 -e PERF_TEST_PROFILE=<performance_profile_name> registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test"
 ----

modules/compliance-anatomy.adoc

@@ -186,7 +186,6 @@ $ oc describe cm/rhcos4-e8-worker-ip-10-0-169-90.eu-north-1.compute.internal-pod
       ----
       <?xml version="1.0" encoding="UTF-8"?>
       ...
-
 ----
 
 Scanner pods for `Platform` scans are similar, except:

modules/dedicated-admin-granting-permissions.adoc

@@ -8,6 +8,7 @@
 To grant permissions to other users or groups, you can add, or _bind_, a role to
 them using the following commands:
 
+[source,terminal]
 ----
 $ oc adm policy add-role-to-user <role> <user_name>
 $ oc adm policy add-role-to-group <role> <group_name>