From 8ee8dd2fd89c989d2efeebd61fa11f002b5bf3f6 Mon Sep 17 00:00:00 2001
From: Jason Boxman <jasonb@edseek.com>
Date: Thu, 6 Aug 2020 13:04:05 -0400
Subject: [PATCH] Update code block styling

---
 modules/accessing-hosts-on-aws.adoc                | 1 +
 modules/annotating-a-route-with-a-cookie-name.adoc | 5 ++++-
 modules/certificate-injection-using-operators.adoc | 4 ++--
 modules/modifying-template-for-new-projects.adoc   | 3 +++
 modules/using-wildcard-routes.adoc                 | 1 +
 5 files changed, 11 insertions(+), 3 deletions(-)

diff --git a/modules/accessing-hosts-on-aws.adoc b/modules/accessing-hosts-on-aws.adoc
index 356775bfc5..c45fbd0dff 100644
--- a/modules/accessing-hosts-on-aws.adoc
+++ b/modules/accessing-hosts-on-aws.adoc
@@ -44,6 +44,7 @@ master. The host name looks similar to `ip-10-0-1-163.ec2.internal`.
 master host. Ensure that you use the same SSH key you specified during the
 installation:
 +
+[source,terminal]
 ----
 $ ssh -i <ssh-key-path> core@<master-hostname>
 ----
diff --git a/modules/annotating-a-route-with-a-cookie-name.adoc b/modules/annotating-a-route-with-a-cookie-name.adoc
index c2a1f4e8f4..f2bef5522a 100644
--- a/modules/annotating-a-route-with-a-cookie-name.adoc
+++ b/modules/annotating-a-route-with-a-cookie-name.adoc
@@ -15,6 +15,7 @@ client and redistribute them.
 
 . Annotate the route with the desired cookie name:
 +
+[source,terminal]
 ----
 $ oc annotate route <route_name> router.openshift.io/<cookie_name>="-<cookie_annotation>"
 ----
@@ -22,12 +23,14 @@ $ oc annotate route <route_name> router.openshift.io/<cookie_name>="-<cookie_ann
 For example, to annotate the cookie name of `my_cookie` to the `my_route` with
 the annotation of `my_cookie_anno`:
 +
+[source,terminal]
 ----
 $ oc annotate route my_route router.openshift.io/my_cookie="-my_cookie_anno"
 ----
 
 . Save the cookie, and access the route:
 +
+[source,terminal]
 ----
 $ curl $my_route -k -c /tmp/my_cookie
-----
\ No newline at end of file
+----
diff --git a/modules/certificate-injection-using-operators.adoc b/modules/certificate-injection-using-operators.adoc
index 95ed1c537c..b2dad4bbcb 100644
--- a/modules/certificate-injection-using-operators.adoc
+++ b/modules/certificate-injection-using-operators.adoc
@@ -41,9 +41,9 @@ metadata:
   name: my-example-custom-ca-deployment
   namespace: my-example-custom-ca-ns
 spec:
-  . . .
+  ...
     spec:
-      . . .
+      ...
       containers:
         - name: my-container-that-needs-custom-ca
           volumeMounts:
diff --git a/modules/modifying-template-for-new-projects.adoc b/modules/modifying-template-for-new-projects.adoc
index 755c1442ca..2185e7ec89 100644
--- a/modules/modifying-template-for-new-projects.adoc
+++ b/modules/modifying-template-for-new-projects.adoc
@@ -16,6 +16,7 @@ To create your own custom project template:
 
 . Generate the default project template:
 +
+[source,terminal]
 ----
 $ oc adm create-bootstrap-project-template -o yaml > template.yaml
 ----
@@ -26,6 +27,7 @@ objects or modifying existing objects.
 . The project template must be created in the `openshift-config` namespace. Load
 your modified template:
 +
+[source,terminal]
 ----
 $ oc create -f template.yaml -n openshift-config
 ----
@@ -40,6 +42,7 @@ $ oc create -f template.yaml -n openshift-config
 ** Using the CLI:
 ... Edit the `project.config.openshift.io/cluster` resource:
 +
+[source,terminal]
 ----
 $ oc edit project.config.openshift.io/cluster
 ----
diff --git a/modules/using-wildcard-routes.adoc b/modules/using-wildcard-routes.adoc
index bea77ec9f7..c122cb465d 100644
--- a/modules/using-wildcard-routes.adoc
+++ b/modules/using-wildcard-routes.adoc
@@ -14,6 +14,7 @@ The default behavior of the Ingress Controller is to admit routes with a wildcar
 . Configure the wildcard policy.
 .. Use the following command to edit the `IngressController` resource:
 +
+[source,terminal]
 ----
 $ oc edit IngressController
 ----