Merge pull request #80747 from jab-rh/remove-trailing-colon-from-block-header

Omit trailing colon from block headers

Author: jab-rh

_unused_topics/sts-mode-installing-manual-config.adoc

@@ -394,7 +394,7 @@ EOF
 
 .. For each `CredentialsRequest` CR that is extracted from the release image, create a secret with the target namespace and target name that is indicated in each `CredentialsRequest`, substituting the AWS IAM role ARN created previously for each component:
 +
-.Example secret manifest for `openshift-machine-api`:
+.Example secret manifest for `openshift-machine-api`
 +
 [source,terminal]
 ----

modules/agent-installer-architectures.adoc

@@ -43,7 +43,7 @@ $ oc adm release info <release_image> -o jsonpath="{ .metadata.metadata}" <1>
 ----
 <1> Replace `<release_image>` with the release image. For example: `quay.io/openshift-release-dev/ocp-release@sha256:123abc456def789ghi012jkl345mno678pqr901stu234vwx567yz0`.
 +
-.Example output when the release image uses the `multi` payload:
+.Example output when the release image uses the `multi` payload
 [source,terminal]
 ----
 {"release.openshift.io architecture":"multi"}

modules/creating-a-service-account-in-your-project.adoc

@@ -58,7 +58,7 @@ metadata:
 $ oc create -f test-service-account.yaml
 ----
 +
-.Example output:
+.Example output
 [source,terminal]
 ----
 serviceaccount/<service_account_name> created
@@ -72,7 +72,7 @@ $ oc describe serviceaccount <service_account_name> <1>
 ----
 <1> Replace `<service_account_name>` with the name of your service account.
 +
-.Example output:
+.Example output
 +
 [source,terminal]
 ----

modules/creating-instance-aws-load-balancer-controller.adoc

@@ -91,7 +91,7 @@ spec:
 
 . Create a YAML file that defines the `Service` resource:
 +
-.Example `service-albo.yaml` file:
+.Example `service-albo.yaml` file
 [source,yaml]
 ----
 apiVersion: v1
@@ -113,7 +113,7 @@ spec:
 
 . Create a YAML file that defines the `Ingress` resource:
 +
-.Example `ingress-albo.yaml` file:
+.Example `ingress-albo.yaml` file
 [source,yaml]
 ----
 apiVersion: networking.k8s.io/v1

modules/deploying-a-pod-that-includes-an-aws-sdk.adoc

@@ -67,7 +67,7 @@ spec:
 $ oc create -f awsboto3sdk-pod.yaml
 ----
 +
-.Example output:
+.Example output
 +
 [source,terminal]
 ----

modules/developer-cli-odo-adding-storage-to-a-specific-container.adoc

@@ -38,7 +38,7 @@ components:
 $ odo storage create store --path /data --size 1Gi --container runtime
 ----
 +
-.Output of the command:
+.Output of the command
 +
 [source,terminal]
 ----

modules/developer-cli-odo-openshift-cluster-objects.adoc

@@ -17,7 +17,7 @@ The pod created by {odo-title} executes two Init Containers:
 
 The `copy-supervisord` Init container copies necessary files onto an `emptyDir` volume. The main application container utilizes these files from the `emptyDir` volume.
 
-.Files that are copied onto the `emptyDir` volume:
+.Files that are copied onto the `emptyDir` volume
 * Binaries:
 ** `go-init` is a minimal init system. It runs as the first process (PID 1) inside the application container. go-init starts the `SupervisorD` daemon which runs the developer code. go-init is required to handle orphaned processes.
 ** `SupervisorD` is a process control system. It watches over configured processes and ensures that they are running. It also restarts services when necessary. For {odo-title}, `SupervisorD` executes and monitors the developer code.

modules/developer-cli-odo-ref-link.adoc

@@ -124,7 +124,7 @@ The correct path for the URL would be \http://8080-tcp.192.168.39.112.nip.io/api
 $  odo describe
 ----
 +
-.Example output:
+.Example output
 [source,terminal]
 ----
 Component Name: backend
@@ -207,7 +207,7 @@ To see this, unlink the component from the PostgreSQL service first:
 $ odo unlink PostgresCluster/hippo
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
  ✓  Successfully unlinked component "backend" from service "PostgresCluster/hippo"
@@ -230,7 +230,7 @@ Next, use the `--inlined` flag to create a link:
 $ odo link PostgresCluster/hippo --inlined
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
  ✓  Successfully created link between component "backend" and service "PostgresCluster/hippo"
@@ -290,7 +290,7 @@ After a link operation, run `odo push` as usual. Upon successful completion of t
 $ odo exec -- env | grep pgVersion
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 pgVersion=13
@@ -310,7 +310,7 @@ and then run `odo push`. To validate if both the mappings got injected correctly
 $ odo exec -- env | grep -e "pgVersion\|pgImage"
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 pgVersion=13
@@ -353,7 +353,7 @@ $ odo link PostgresCluster/hippo --bind-as-files
 $ odo push
 ----
 
-.Example `odo describe` output:
+.Example `odo describe` output
 [source,terminal]
 ----
 $ odo describe
@@ -414,37 +414,37 @@ Linked Services:
 
 Everything that was an environment variable in the `key=value` format in the earlier `odo describe` output is now mounted as a file. Use the `cat` command to view the contents of some of these files:
 
-.Example command:
+.Example command
 [source,terminal]
 ----
 $ odo exec -- cat /bindings/backend-postgrescluster-hippo/password
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 q({JC:jn^mm/Bw}eu+j.GX{k
 ----
 
-.Example command:
+.Example command
 [source,terminal]
 ----
 $ odo exec -- cat /bindings/backend-postgrescluster-hippo/user
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 hippo
 ----
 
-.Example command:
+.Example command
 [source,terminal]
 ----
 $ odo exec -- cat /bindings/backend-postgrescluster-hippo/clusterIP
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 10.101.78.56
@@ -466,25 +466,25 @@ $ odo push
 
 These custom bindings get mounted as files instead of being injected as environment variables. To validate that this worked, run the following command:
 
-.Example command:
+.Example command
 [source,terminal]
 ----
 $ odo exec -- cat /bindings/backend-postgrescluster-hippo/pgVersion
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 13
 ----
 
-.Example command:
+.Example command
 [source,terminal]
 ----
 $ odo exec -- cat /bindings/backend-postgrescluster-hippo/pgImage
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 registry.developers.crunchydata.com/crunchydata/crunchy-postgres-ha:centos8-13.4-0

modules/developer-cli-odo-ref-registry.adoc

@@ -18,7 +18,7 @@ To list the registries currently contacted by `odo`, run the command:
 $ odo registry list
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 NAME                       URL                             SECURE
@@ -37,7 +37,7 @@ To add a registry, run the command:
 $ odo registry add
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 $ odo registry add StageRegistry https://registry.stage.devfile.io
@@ -62,7 +62,7 @@ To delete a registry, run the command:
 $ odo registry delete
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 $ odo registry delete StageRegistry
@@ -81,7 +81,7 @@ To update the URL or the personal access token of a registry already registered,
 $ odo registry update
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
  $ odo registry update MyRegistry https://otherregistry.example.com --token <other_access_token>

modules/developer-cli-odo-ref-storage.adoc

@@ -14,7 +14,7 @@ To add a storage volume to the cluster, run the command:
 $ odo storage create
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 $ odo storage create store --path /data --size 1Gi
@@ -38,7 +38,7 @@ To check the storage volumes currently used by the component, run the command:
 $ odo storage list
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 $ odo storage list
@@ -57,7 +57,7 @@ To delete a storage volume, run the command:
 $ odo storage delete
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 $ odo storage delete store -f
@@ -98,7 +98,7 @@ In the example, there are two containers,`nodejs1` and `nodejs2`. To attach stor
 $ odo storage create --container
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 $ odo storage create store --path /data --size 1Gi --container nodejs2
@@ -114,7 +114,7 @@ You can list the storage resources, using the `odo storage list` command:
 $ odo storage list
 ----
 
-.Example output:
+.Example output
 [source,terminal]
 ----
 The component 'nodejs-testing-xnfg' has the following storage attached: