From 3f90bcbbf6b2b16d167b30fc6c39a3494ad94d2d Mon Sep 17 00:00:00 2001
From: Alexander Jacocks <alexander@redhat.com>
Date: Mon, 29 Jul 2024 11:23:45 -0400
Subject: [PATCH] update public site

---
 404.html                                      |    2 +-
 about/index.html                              |    2 +-
 contact/index.html                            |    2 +-
 events/index.html                             |    2 +-
 events/index.xml                              |    9 +-
 images/Logo-Red_Hat-C-Standard-RGB-small.png  |  Bin 0 -> 13609 bytes
 images/Logo-Red_Hat-C-Standard-RGB.png        |  Bin 0 -> 14314 bytes
 index.html                                    |    6 +-
 index.xml                                     | 1722 +++--------------
 jr-sa/index.html                              |    2 +-
 sitemap.xml                                   | 1302 ++++---------
 workshops/agile_integrations_ci/index.html    |    2 +-
 workshops/agile_integrations_ci/index.xml     |   65 +-
 .../agile_integrations_ci/lab01/index.html    |  194 +-
 .../agile_integrations_ci/lab02/index.html    |   32 +-
 .../agile_integrations_ci/lab03/index.html    |   82 +-
 .../agile_integrations_ci/lab04/index.html    |   36 +-
 .../agile_integrations_ci/lab05/index.html    |   56 +-
 .../agile_integrations_ci/lab06/index.html    |   10 +-
 .../agile_integrations_ci/lab07/index.html    |   40 +-
 .../openshift/index.html                      |   10 +-
 .../prerequisites/index.html                  |    2 +-
 workshops/agile_integrations_dev/index.html   |    2 +-
 workshops/agile_integrations_dev/index.xml    |   70 +-
 .../agile_integrations_dev/lab01/index.html   |   26 +-
 .../agile_integrations_dev/lab02/index.html   |   60 +-
 .../agile_integrations_dev/lab03/index.html   |  523 +++--
 .../agile_integrations_dev/lab04/index.html   |  119 +-
 .../agile_integrations_dev/lab05/index.html   |   82 +-
 .../agile_integrations_dev/lab06/index.html   |   12 +-
 .../agile_integrations_dev/lab07/index.html   |   10 +-
 .../agile_integrations_dev/lab08/index.html   |   30 +-
 .../openshift/index.html                      |   10 +-
 .../prerequisites/index.html                  |    2 +-
 .../exercise1.0/index.html                    |   48 +-
 .../exercise1.1/index.html                    |   20 +-
 .../exercise1.2/index.html                    |   44 +-
 .../exercise2.0/index.html                    |   40 +-
 .../exercise2.1/index.html                    |   30 +-
 .../exercise3.0/index.html                    |   40 +-
 .../exercise3.1/index.html                    |   36 +-
 .../exercise3.2/index.html                    |   18 +-
 .../exercise3.3/index.html                    |   26 +-
 .../exercise4.0/index.html                    |   32 +-
 .../alpha/ansible_with_rhocp_edge/index.html  |   32 +-
 .../alpha/ansible_with_rhocp_edge/index.xml   |   76 +-
 .../ansible_with_rhocp_edge/setup/index.html  |   46 +-
 .../ansible_with_rhocp_edge/wrapup/index.html |    6 +-
 workshops/ansible_ansible/index.html          |    6 +-
 workshops/ansible_ansible/index.xml           |   25 +-
 .../ansible_automation/exercise1.0/index.html |   78 +-
 .../ansible_automation/exercise1.1/index.html |   30 +-
 .../ansible_automation/exercise1.2/index.html |   28 +-
 .../ansible_automation/exercise1.3/index.html |   66 +-
 .../ansible_automation/exercise1.4/index.html |   16 +-
 .../ansible_automation/exercise1.5/index.html |   46 +-
 .../ansible_automation/exercise2.0/index.html |   32 +-
 .../ansible_automation/exercise2.1/index.html |   64 +-
 .../ansible_automation/exercise2.2/index.html |   62 +-
 .../ansible_automation/exercise3.0/index.html |   44 +-
 workshops/ansible_automation/index.html       |   10 +-
 workshops/ansible_automation/index.xml        |   72 +-
 workshops/ansible_automation/setup/index.html |   24 +-
 .../ansible_automation/wrapup/index.html      |    6 +-
 .../exercise1.0/index.html                    |   56 +-
 .../exercise1.1/index.html                    |   18 +-
 .../exercise1.2/index.html                    |   24 +-
 .../exercise1.3/index.html                    |   60 +-
 .../exercise1.4/index.html                    |   14 +-
 .../exercise1.5/index.html                    |   42 +-
 .../exercise2.0/index.html                    |   26 +-
 .../exercise2.1/index.html                    |   64 +-
 .../exercise2.2/index.html                    |   60 +-
 .../exercise3.0/index.html                    |   44 +-
 workshops/ansible_tower_azure/index.html      |    4 +-
 workshops/ansible_tower_azure/index.xml       |   74 +-
 .../ansible_tower_azure/setup/index.html      |   16 +-
 .../ansible_tower_azure/wrapup/index.html     |    6 +-
 .../exercise1.0/index.html                    |   46 +-
 .../exercise1.1/index.html                    |   62 +-
 workshops/ansible_tower_intro/index.html      |   10 +-
 workshops/ansible_tower_intro/index.xml       |   35 +-
 .../ansible_tower_intro/setup/index.html      |   16 +-
 .../ansible_tower_intro/wrapup/index.html     |    6 +-
 workshops/cloudforms41/exercise1.0/index.html |    2 +-
 workshops/cloudforms41/exercise1.1/index.html |    2 +-
 .../cloudforms41/exercise1.10/index.html      |    2 +-
 .../cloudforms41/exercise1.11/index.html      |    2 +-
 .../cloudforms41/exercise1.12/index.html      |    2 +-
 .../cloudforms41/exercise1.13/index.html      |    2 +-
 .../cloudforms41/exercise1.14/index.html      |    2 +-
 .../cloudforms41/exercise1.15/index.html      |    2 +-
 .../cloudforms41/exercise1.16/index.html      |    2 +-
 .../cloudforms41/exercise1.17/index.html      |   72 +-
 .../cloudforms41/exercise1.18/index.html      |   16 +-
 .../cloudforms41/exercise1.19/index.html      |   30 +-
 workshops/cloudforms41/exercise1.2/index.html |    2 +-
 .../cloudforms41/exercise1.20/index.html      |   24 +-
 workshops/cloudforms41/exercise1.3/index.html |    2 +-
 workshops/cloudforms41/exercise1.4/index.html |    2 +-
 workshops/cloudforms41/exercise1.5/index.html |    2 +-
 workshops/cloudforms41/exercise1.6/index.html |    2 +-
 workshops/cloudforms41/exercise1.7/index.html |    2 +-
 workshops/cloudforms41/exercise1.8/index.html |    2 +-
 workshops/cloudforms41/exercise1.9/index.html |    2 +-
 workshops/cloudforms41/index.html             |    2 +-
 workshops/cloudforms41/index.xml              |  147 +-
 .../cloudforms41/prerequisites/index.html     |    2 +-
 workshops/cloudforms41/wrapup/index.html      |    2 +-
 .../containers_101/exercise1.0/index.html     |   12 +-
 .../containers_101/exercise1.1/index.html     |   16 +-
 .../containers_101/exercise1.2/index.html     |   82 +-
 .../containers_101/exercise1.3/index.html     |   22 +-
 .../containers_101/exercise1.4/index.html     |   24 +-
 workshops/containers_101/index.html           |   12 +-
 workshops/containers_101/index.xml            |   48 +-
 workshops/containers_101/setup/index.html     |   26 +-
 workshops/containers_101/wrapup/index.html    |    2 +-
 .../exercise1/index.html                      |   16 +-
 .../exercise2/index.html                      |   32 +-
 .../exercise3/index.html                      |   20 +-
 .../exercise4/index.html                      |   28 +-
 .../exercise5/index.html                      |   14 +-
 .../exercise6/index.html                      |   32 +-
 .../exercise7/index.html                      |   26 +-
 workshops/containers_the_hard_way/index.html  |   12 +-
 workshops/containers_the_hard_way/index.xml   |   48 +-
 .../containers_the_hard_way/intro/index.html  |   46 +-
 .../containers_the_hard_way/wrapup/index.html |    6 +-
 workshops/dynatrace_openshift/index.html      |    6 +-
 workshops/dynatrace_openshift/index.xml       |   84 +-
 workshops/index.html                          |    6 +-
 workshops/index.xml                           |  173 +-
 workshops/jdv_dev/exercise1/index.html        |   18 +-
 workshops/jdv_dev/exercise10/index.html       |    2 +-
 workshops/jdv_dev/exercise2/index.html        |    6 +-
 workshops/jdv_dev/exercise3/index.html        |    6 +-
 workshops/jdv_dev/exercise4/index.html        |    2 +-
 workshops/jdv_dev/exercise5/index.html        |    2 +-
 workshops/jdv_dev/exercise6/index.html        |    2 +-
 workshops/jdv_dev/exercise7/index.html        |    2 +-
 workshops/jdv_dev/exercise8/index.html        |    8 +-
 workshops/jdv_dev/exercise9/index.html        |    4 +-
 workshops/jdv_dev/index.html                  |    2 +-
 workshops/jdv_dev/index.xml                   |   94 +-
 workshops/jdv_dev/prerequisites/index.html    |    2 +-
 workshops/jdv_dev/wrapup/index.html           |    2 +-
 .../openshift_101_dcmetromap/fin/index.html   |   10 +-
 workshops/openshift_101_dcmetromap/index.html |   10 +-
 workshops/openshift_101_dcmetromap/index.xml  |   69 +-
 .../lab1-welcome/index.html                   |   32 +-
 .../lab2-byodocker/index.html                 |   36 +-
 .../lab3-s2i/index.html                       |   40 +-
 .../lab4-devmanage/index.html                 |   80 +-
 .../lab5-rollbacks/index.html                 |   28 +-
 .../lab6-replicationrecovery/index.html       |   56 +-
 .../lab7-labels/index.html                    |   32 +-
 .../lab8-cicd/index.html                      |  338 ++--
 .../lab9-bluegreen/index.html                 |   38 +-
 .../login_tour_wetty/index.html               |   14 +-
 .../prerequisites/index.html                  |   10 +-
 workshops/openshift_4_101/fin/index.html      |   10 +-
 workshops/openshift_4_101/index.html          |   10 +-
 workshops/openshift_4_101/index.xml           |  100 +-
 workshops/openshift_4_101/keyterms/index.html |    2 +-
 .../openshift_4_101/lab1-welcome/index.html   |   28 +-
 .../lab2-byocontainer/index.html              |   16 +-
 .../lab2.1-byocontainer/index.html            |   26 +-
 .../lab2.2-byocontainer/index.html            |   16 +-
 workshops/openshift_4_101/lab3-s2i/index.html |   10 +-
 .../openshift_4_101/lab3.1-s2i/index.html     |   30 +-
 .../openshift_4_101/lab4-devmanage/index.html |   78 +-
 .../openshift_4_101/lab5-rollbacks/index.html |   48 +-
 .../lab6-replicationrecovery/index.html       |   22 +-
 .../lab6.1-replicationrecovery/index.html     |   26 +-
 .../lab6.2-replicationrecovery/index.html     |   28 +-
 .../openshift_4_101/lab7-labels/index.html    |   64 +-
 .../openshift_4_101/lab8-cicd/index.html      |   42 +-
 .../openshift_4_101/lab9-bluegreen/index.html |   54 +-
 .../openshift_4_101/prerequisites/index.html  |   10 +-
 .../openshift_4_101_dynatrace/fin/index.html  |   10 +-
 .../openshift_4_101_dynatrace/index.html      |   10 +-
 workshops/openshift_4_101_dynatrace/index.xml |    9 +-
 .../lab1-welcome/index.html                   |   40 +-
 .../lab10-labels/index.html                   |   64 +-
 .../lab11-cicd/index.html                     |   46 +-
 .../lab12-bluegreen/index.html                |   58 +-
 .../lab2-byocontainer/index.html              |  102 +-
 .../lab3-installagent/index.html              |  160 +-
 .../lab4-configdynatraceactivegate/index.html |   46 +-
 .../lab5-s2i/index.html                       |   42 +-
 .../lab6-deploy3tierapp/index.html            |   10 +-
 .../lab7-devmanage/index.html                 |   82 +-
 .../lab8-rollbacks/index.html                 |   46 +-
 .../lab9-replicationrecovery/index.html       |   56 +-
 .../prerequisites/index.html                  |   10 +-
 workshops/openshift_serverless/index.html     |    2 +-
 workshops/openshift_serverless/index.xml      |    9 +-
 workshops/openshift_service_mesh/index.html   |    2 +-
 workshops/openshift_service_mesh/index.xml    |    9 +-
 .../fin/index.html                            |   10 +-
 .../openshift_service_mesh_v1.0/index.html    |   10 +-
 .../openshift_service_mesh_v1.0/index.xml     |  118 +-
 .../lab1.1_welcome/index.html                 |   10 +-
 .../lab1.2_terminal/index.html                |   14 +-
 .../lab1.3_installing/index.html              |   32 +-
 .../lab1.4_deploymsa/index.html               |   36 +-
 .../lab2.1_userprofile/index.html             |   34 +-
 .../lab2.2_deployuserprofile/index.html       |   32 +-
 .../lab2.3_kiali/index.html                   |   18 +-
 .../lab3.1_featureupdate/index.html           |   32 +-
 .../lab3.2_grafana/index.html                 |   18 +-
 .../lab3.3_jaeger/index.html                  |   24 +-
 .../lab4.1_routingtraffic/index.html          |   42 +-
 .../lab4.2_trafficsplitting/index.html        |   56 +-
 .../lab4.3_faultinjection/index.html          |   28 +-
 .../lab4.4_circuitbreaking/index.html         |   24 +-
 .../lab5.1_intromtls/index.html               |   58 +-
 .../lab5.2_verifymtls/index.html              |   16 +-
 .../lab5.3_prep/index.html                    |   40 +-
 .../lab5.4_authpolicy/index.html              |   46 +-
 .../lab5.5_secureingressegress/index.html     |   32 +-
 workshops/pki_workshop/readme/index.html      |    2 +-
 .../unit_lessons/unit_1/index.html            |    2 +-
 .../unit_lessons/unit_10/index.html           |    2 +-
 .../unit_lessons/unit_11/index.html           |    2 +-
 .../unit_lessons/unit_12/index.html           |    2 +-
 .../unit_lessons/unit_2/index.html            |    2 +-
 .../unit_lessons/unit_3/index.html            |    2 +-
 .../unit_lessons/unit_4/index.html            |    2 +-
 .../unit_lessons/unit_5/index.html            |    2 +-
 .../unit_lessons/unit_6/index.html            |    2 +-
 .../unit_lessons/unit_7/index.html            |    2 +-
 .../unit_lessons/unit_8/index.html            |    2 +-
 .../unit_lessons/unit_9/index.html            |    2 +-
 workshops/rhel_8/exercise1.0/index.html       |   12 +-
 workshops/rhel_8/exercise1.1/index.html       |   10 +-
 workshops/rhel_8/exercise1.2/index.html       |   90 +-
 workshops/rhel_8/exercise1.3/index.html       |   38 +-
 workshops/rhel_8/exercise1.4/index.html       |   40 +-
 workshops/rhel_8/exercise1.5/index.html       |   26 +-
 workshops/rhel_8/exercise1.6/index.html       |   10 +-
 workshops/rhel_8/exercise1.7/index.html       |   54 +-
 workshops/rhel_8/exercise1.8/index.html       |   84 +-
 workshops/rhel_8/exercise1.9/index.html       |   60 +-
 workshops/rhel_8/index.html                   |   14 +-
 workshops/rhel_8/index.xml                    |   75 +-
 workshops/rhel_8/setup/index.html             |   28 +-
 workshops/rhel_8/wrapup/index.html            |   14 +-
 workshops/rhosp_101/10_storage/index.html     |   85 +-
 workshops/rhosp_101/1_introduction/index.html |   15 +-
 .../rhosp_101/2_login_to_horizon/index.html   |   22 +-
 .../rhosp_101/3_managing_networks/index.html  |   78 +-
 .../index.html                                |   36 +-
 .../5_managing_security_groups/index.html     |   85 +-
 .../rhosp_101/6_managing_images/index.html    |   29 +-
 .../rhosp_101/7_managing_instances/index.html |  106 +-
 .../rhosp_101/8_using_the_cli/index.html      |   60 +-
 workshops/rhosp_101/9_heat/index.html         |   49 +-
 workshops/rhosp_101/fin/index.html            |    2 +-
 workshops/rhosp_101/index.html                |    8 +-
 workshops/rhosp_101/index.xml                 |   67 +-
 .../secure_software_factory/fin/index.html    |    2 +-
 workshops/secure_software_factory/index.html  |   10 +-
 workshops/secure_software_factory/index.xml   |  140 +-
 .../secure_software_factory/lab01/index.html  |   20 +-
 .../secure_software_factory/lab02/index.html  |   14 +-
 .../secure_software_factory/lab03/index.html  |   10 +-
 .../secure_software_factory/lab04/index.html  |   20 +-
 .../secure_software_factory/lab05/index.html  |   36 +-
 .../secure_software_factory/lab06/index.html  |   36 +-
 .../secure_software_factory/lab07/index.html  |   24 +-
 .../secure_software_factory/lab08/index.html  |   22 +-
 .../secure_software_factory/lab09/index.html  |   22 +-
 .../secure_software_factory/lab10/index.html  |   28 +-
 .../secure_software_factory/lab11/index.html  |   26 +-
 .../secure_software_factory/lab12/index.html  |   38 +-
 .../secure_software_factory/lab13/index.html  |   38 +-
 .../secure_software_factory/lab14/index.html  |   98 +-
 .../secure_software_factory/lab15/index.html  |   12 +-
 .../secure_software_factory/lab16/index.html  |   10 +-
 .../secure_software_factory/lab17/index.html  |   46 +-
 .../secure_software_factory/lab18/index.html  |   38 +-
 .../login_tour_wetty/index.html               |   18 +-
 .../prerequisites/index.html                  |   10 +-
 .../secure_software_factory/readme/index.html |    2 +-
 workshops/security_container_intro/index.html |   14 +-
 workshops/security_container_intro/index.xml  |   47 +-
 .../lab01-intro/index.html                    |   40 +-
 .../lab02-registry/index.html                 |   49 +-
 .../lab03-podman/index.html                   |   70 +-
 .../lab04-isolation/index.html                |   52 +-
 .../lab05-selinux/index.html                  |   37 +-
 .../lab06-inspecting/index.html               |   38 +-
 .../lab07-signing/index.html                  |   45 +-
 .../lab08-builds/index.html                   |   34 +-
 .../lab99-conclusion/index.html               |   10 +-
 .../exercise1.0/index.html                    |   62 +-
 .../exercise1.1/index.html                    |   88 +-
 .../exercise1.2/index.html                    |   24 +-
 .../exercise1.3/index.html                    |   16 +-
 .../exercise1.4/index.html                    |   16 +-
 .../exercise1.5/index.html                    |   68 +-
 .../exercise1.6/index.html                    |   16 +-
 .../exercise1.7/index.html                    |  130 +-
 .../exercise1.8/index.html                    |   34 +-
 .../exercise1.9/index.html                    |   16 +-
 workshops/security_containers/index.html      |   10 +-
 workshops/security_containers/index.xml       |   77 +-
 .../security_containers/setup/index.html      |   22 +-
 .../security_containers/wrapup/index.html     |    4 +-
 .../security_openshift/exercise1.0/index.html |   32 +-
 .../security_openshift/exercise1.1/index.html |   46 +-
 .../security_openshift/exercise1.2/index.html |   16 +-
 .../security_openshift/exercise1.3/index.html |   22 +-
 .../security_openshift/exercise1.4/index.html |   18 +-
 .../security_openshift/exercise1.5/index.html |   28 +-
 .../security_openshift/exercise1.6/index.html | 1252 ++++++------
 .../security_openshift/exercise1.7/index.html |   50 +-
 .../security_openshift/exercise1.8/index.html |  166 +-
 .../security_openshift/exercise1.9/index.html |   36 +-
 workshops/security_openshift/index.html       |    6 +-
 workshops/security_openshift/index.xml        |   71 +-
 workshops/security_openshift/setup/index.html |   14 +-
 .../security_openshift/wrapup/index.html      |    4 +-
 .../selinux_policy/exercise1.0/index.html     |   23 +-
 .../selinux_policy/exercise1.1/index.html     |  212 +-
 .../selinux_policy/exercise1.2/index.html     |   89 +-
 .../selinux_policy/exercise1.3/index.html     | 1035 ++++++++++
 .../selinux_policy/exercise1.4/index.html     | 1043 ++++++++++
 .../selinux_policy/exercise2.0/index.html     |   63 +-
 .../selinux_policy/exercise2.1/index.html     |   95 +-
 .../selinux_policy/exercise2.2/index.html     |  145 +-
 .../selinux_policy/exercise2.3/index.html     |   98 +-
 .../selinux_policy/exercise2.4/index.html     |  132 +-
 .../selinux_policy/exercise2.5/index.html     |  967 +++++++++
 workshops/selinux_policy/index.html           |   50 +-
 workshops/selinux_policy/index.xml            |   95 +-
 workshops/selinux_policy/setup/index.html     |   32 +-
 workshops/selinux_policy/wrapup/index.html    |   56 +-
 .../source_to_image/conclusion/index.html     |    2 +-
 .../containerize_app/index.html               |   30 +-
 workshops/source_to_image/dice/index.html     |   92 +-
 .../source_to_image/gochat_s2i/index.html     |  354 ++--
 workshops/source_to_image/index.html          |   10 +-
 workshops/source_to_image/index.xml           |   59 +-
 .../source_to_image/prerequisites/index.html  |   10 +-
 .../source_to_image/run_the_app/index.html    |   34 +-
 workshops/source_to_image/setup/index.html    |   18 +-
 .../source_to_image/index.html                |  164 +-
 workshops/strangling_the_monolith/index.html  |    2 +-
 workshops/strangling_the_monolith/index.xml   |   43 +-
 .../strangling_the_monolith/lab1/index.html   |  122 +-
 .../strangling_the_monolith/lab2/index.html   |  146 +-
 .../strangling_the_monolith/lab3/index.html   |  169 +-
 .../login_tour_oc/index.html                  |   30 +-
 .../login_tour_wetty/index.html               |    8 +-
 .../prerequisites/index.html                  |    2 +-
 358 files changed, 10318 insertions(+), 10375 deletions(-)
 create mode 100644 images/Logo-Red_Hat-C-Standard-RGB-small.png
 create mode 100644 images/Logo-Red_Hat-C-Standard-RGB.png
 create mode 100644 workshops/selinux_policy/exercise1.3/index.html
 create mode 100644 workshops/selinux_policy/exercise1.4/index.html
 create mode 100644 workshops/selinux_policy/exercise2.5/index.html

diff --git a/404.html b/404.html
index 700bfeae9..9c7061093 100644
--- a/404.html
+++ b/404.html
@@ -290,7 +290,7 @@ <h1>404</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/about/index.html b/about/index.html
index 48041d06d..31ad999b1 100644
--- a/about/index.html
+++ b/about/index.html
@@ -294,7 +294,7 @@ <h1>About</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/contact/index.html b/contact/index.html
index 53361436d..926fb133e 100644
--- a/contact/index.html
+++ b/contact/index.html
@@ -298,7 +298,7 @@ <h1 id="we-are-here-to-help-you">We are here to help you</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/events/index.html b/events/index.html
index 2311cd35b..f637a17e7 100644
--- a/events/index.html
+++ b/events/index.html
@@ -345,7 +345,7 @@ <h1></h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/events/index.xml b/events/index.xml
index a1a0917d5..5aa7ab627 100644
--- a/events/index.xml
+++ b/events/index.xml
@@ -4,11 +4,8 @@
     <title>Red Hat | Public Sector</title>
     <link>/events/</link>
     <description>Recent content on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/events/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/events/index.xml" rel="self" type="application/rss+xml" />
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/images/Logo-Red_Hat-C-Standard-RGB-small.png b/images/Logo-Red_Hat-C-Standard-RGB-small.png
new file mode 100644
index 0000000000000000000000000000000000000000..84f7df2a15d39b98d6aea5ca7540620067f8827e
GIT binary patch
literal 13609
zcmZ|WWl$VVxG3Po3C<VXCAbE6hv4q+?(Xgy2<}0{;_gle?(XjHEOwUr<5b-rr=Obb
zs-AkctGaf&XL{a^Qk4IJjDUv#005AsB*m1$wITR0MuP=^e)J$Xf-4deNo6?zz?%{P
z2n+=PK;WjpBLKjS82~sj1ORx_0RU{r>^3Dn@CjIBnIB>w|F3+}d|U&!z`07viNhVi
z5u)%Q96Ni1zmWA<N=#VQbLBk8%TWHu<3GViuiUdJw02GFa!PU9Kg!VsjRWe9bNYVe
zbJa~NHa02N20*pslbDr9ir>Fe7nBPY#9~NDqarEls1%YcGB$}l>^VqlVaFfye)+I^
zT&#IbWN^DoWUxm6+<F$rvjQv`rS02iB|p%d3unid5vdS5s=L#)3wf0-`TX60dL^LZ
zksoUmU^NFI;aoiH2d$JNNT+6**bi(*Ml?JT%e-nr&e&<7YVrdr1Qx^f@L@rB+TC*?
zm^;Qsg$02x;U>uac;P{$!0G0=E|?s@V$zgw0P9)bSsy~1O`ae1WF-JzSqcW@tQIbs
zN?o=B{&<!%XTudw_WNpK(~qG2rDL1YY6vyg2Ogg(jYr^-8ak3(*11&^oUMJ+`kedM
zqfGUO$}_~Z;U{j~^<WqPKWI#3LC5Gve|+$D|8`<Od9UkWb+ds3+A4!Y3_3L<;zkmi
z6vc?v58@xhQ^-u*?R&OU|2p-z?-2}VtGq4`I(w&p8GfujQz^i?-^y_LX>uM}7p)JH
zRp+2ZQN94luT~k@3;Ie>g|G;Trf1ykhqk1~o3-2yF8Yz_jVFu$UMY^1q&R_WO)VE@
z>!TtAOg>gmGW}u9@wxx8Q%J+h%+^Ot5@CsCH?h^Q4YhwiXvm)zE)SE`y-|N@UO_~6
z5$mE7nZdEG#U!Jo+|?Eyb|$1e{vu`8Zqj)d1QH_MF{WKnYxqjmD%1Vse=SnPsrUG=
zO)#_urK767YE&aYE37d;pf0%omJQ03IEt$DUhWi;Ml`&cXajGCk^Zc)23t`-m66f{
z)~;kI6q!Q^k5X1Bvg5SuzZ|{43bg)^9AE5gnkv7*W(}U>HAB61;NjcYLYI`tNoD~`
z%Hcr7N2tf8>K!dR;x(!~oUdz+`L2UH4T+lg8MlZ!wh-jUMNo_T>!Y+v@yqyU$oYaN
zPAj`?OS<;EQ-ct;-fkBgt-MEWjna#>$g=gT_Rai@pi0eo1#yij!Q<V3x8DHEhTdlD
zf~W66d({Fh_q_~g^GR7$oN&^nf0#2F^RVY`D76HXH|B9BHXnfJYKq1&OIWoq@|xN7
z@`lLq>v-*$T*6G=5KJS7uDG$q-&YF7gNrm+HcFESi`|Od438Fl^>4ilc|X?IFE3z4
zyASHKCSi-abj+GZS{I&l%jG9?0FghJj+QJXFIJZ4mZ3`~AJSG0P%MMU;{!>;k|Vss
zN>0mJ<LBmCaTHAc<CL<y(AgrwR28n57LG~sU>Zqy`sd&M=FjY__F?^2Zm3iBIJUvs
zTarEbEl(={jA^k^cTxA$ugW~~P#z%L{nB;tg7*#XacRK>KXPG^WsoJ%M!5N`ENG<V
zIw^6oj5B38d?tJ*zk0{))C{r7;htf+`P&ks?<1&vQJ7nuu};^t>VDt)+*|#MV5nw5
z{uccfomu>;@x}(GK$moP6NYxz=Itiang~m0oO6t`hwn;kAPSz@pL^#Ky<1edF#e7A
zA>vLVMo{||J+j+);&1k-dfwpEN#-$b$o6(QHM1$cR|Od#4<FuG-o<jO1yv1ep{{#M
zF&g)8kQBjwN^{!~Rzzi$x(4%yU-oX`zOLbO&y68h^R#&(@)9u~z5oXSQcl*TT^IJB
zif?qofjyDvijF<M^930k_&8}5L7~M&GW;YIhFcFotHKq`8mt=Rw-F2jA;PzX-=uAp
zweFiHnpLxu?Rqxs*Isrv;M!M1$Y8|*-CVJ*IKw&q>7^KxT?lOC=h7>f%$*;rC7T>U
zIO)Alz}6ZxRJgdroPAjk(0g^|vE)N8fH^f?(L#h!vT=-$^%jYl!Om~RyN>03x7MAX
zj4y^&$bG(a{JD9e8zyR2`@*sns)8f2DX~fDZ?OG=3yR#|FDhz86eGt)vr>-q^;i92
z#KGruoe7Tu`crXZ_>((GKgU-LK}MH-oruD&vD*JNhRXg>AthpB)9X&M*2g*?-WcBa
z>29lk)S-yRY9GFV#Bd~W5NDwTP;HPqPMm=n)AL7sVL%$-J0&?K>5=z#M!Yu7e^%?5
zlaY~Cv{s}|=QicJL(&Y(rGOYJk<q3!c-rcNGrVxTizpNX%(K4V%VzH8dSNI<{V`_4
zi!-cp+Y9*dt}zuif<KuAFumo=^f~wUcx*R(yBoZ~Zx2$2S?>toSDkP8<8AbO;yH4S
zffjY`Fwm_uCD+ai?nBWikD1H}I-Te8W^*5vfHLY^T{r<ofnh!#)t-<kE*2lHCq^W(
zLr$k#Q+}4a2OlEjPrZAux3jr=mEIi>>yxrFp_JGF{$tH7kv-UBBdp_V{9VrA;@8d5
z5B=QA0hRrqzF5#CStlmI?(&_gXhS{BdR}u*#e)1SjY!+61;{FzLKTS+v)f^Bs#7z%
zYt_F<{D_c%K<2+2(VZ{{VLq#ucBpHqA5(&PMs1Vy7{go63r!8&n>W5PhK|<zb0erK
z*So#5bby63eDN`P3-jy@hy$Q-yl}iwWo*FuWq6VZpZ*_Od6@e?mh<$@?}BKj1rFky
z-haG_5py@p3grox8S28m4-&e#k3p=ads65J#XcpKE{(rehsQ{Zx#}9~l4w>LSUDBL
z;85q)(p*~g%yL3Sp2ZZEH<NuO|7!G4{{!#=FwFNh@H&28`gy%p@JG5rV~1zZ4O%9z
zkUSxt{zzgysx%=i85|?1ztL>J$@BEwyyf5fM$%SF&!MCpfxsZBK-IuM$wI%*vcGc_
zQyBDB-RD#VgAjE0B~a`pMKzJuQ0BFyD+|<zPVpuJg3;s^MRuzhNu}f8gHlMeszeKH
z;wb;dG)U|saDcR98f!PEf>HePv<Sc-w>RfBY;me`VvN*Cil-oiI#p;sb65_s^op|y
zbh{YG<+KR2kEI#GfLUx4i;pINDIL8KZ2O?Ts?=Ujn4edS;2}D3o9(A%x8cp+q40~A
zwfnFh>YQGfLFXs)4!jTfV^H7^!B3HkfavZIy|v*Z5YX(Y(;+O|Hhm$%%UsRt^|t3$
zBi}Iv60xbt{vwMk3lp=r8SyRvU7#a<oxDR*kYxUC98gPAC9aEz#zcvmgp{B5o&WdD
z$gd@hE{o_kH>Q(<wh*iAvn4No+IxXN%A==sz6C{L!HPB1!2i&3Ioa%~HA{#tojVYZ
zy8ko+7l6U`Yn_i!mcnMs1$5%7YZ^`lLC<|bDsb{a$FU9?n^lHY?k!{6EQXz)6nE0p
zk$8jegYTv+`B?cS#Z+?=whTVOuK7zHWsLUS4izU)UjsTG;pP&RB3-P9PMOrKQy%}S
zoy#D$m47rUimGyy=X(46Q$Y3g1`upy&6}$K3bxn2U=74l&S!ZC><aG+GZ$Z^H<{oS
zaeo{=780kQ614j6u|!HspccZJo^_p&l$EbB|Na|y2q9hqixH<fm_SJXk*ES_P>W#;
z$VE^+rjn=4(K9HnmKb&3HSNqBJ}s5}cuf=9r?Pr!5X;T*G$&K!yO!R;+-j0Zmw`Co
zV&C(g1oV+RTka_`qhu=kN;^q1)eV}(Ax8d3^FZ@p%2N=%L9r<>fGY^aG>Ve+V6v;g
z{azinwLq}we8EG$2ua*oGIPzTwjxzUXj?3#wU4Ak4X=RXT$oh6Bq;cH`&Cn8jmQ6#
z>&S6h7ZwH*io1?b$E44=&$uW3Nh(L-M9ABw8^Rx|&M)$-d>{!fJ7P~iWhSK1(78+a
z8?D>4h~=RbjI#iV70Ud9bD;DOb~UTWdTGHV2(7>Se&qyiVx|}O7(3{qG3W>h#9swr
zD@-P^xecIQ?aJ?fGcmFs2{)!DVXl@u+EHQ&VyKb~x64#{evrq!6uYD0D$=R5I3G%)
z<u2vY`UK_5?L=ODRL+VSFl3~<#UCj#d%fhU-gVjZ9{TQq?m6$8pk_3@25P0pZ=2r?
zB+moxK+~rrd$MmuxCWx(#3X*b2l?Z|KQHS2UqRP_b7i#wB4uxT|8$D2XC$@Z^<zhs
z7@68rIPizPE7a85WVE9|cIwB$!?bZJ+jAhzWu);FRUCsmOH!8t+K9Q)t8?LBA(SDt
z8YA(^gfL6=PApAgwqGP44Z3We8PPtz&$G-!Mw@E}<XUETYF5wGC6R9a%E)qCG=->S
z@QTAaZcRgEDw&~S`Ed}i^2fEh-Pblr`kr|BpTP{?!yaghI}DTVNTM7&XgVka5>9xm
zF<tz73__I>k4;E@+yn>Y=z0ECz9R{%X`|4?LNv+q4~G<2Kb7KfgApy}Zp?$0RCCQ+
z^pp$m7(oyNUB}o`azS#%>Q=znN0l<=dx1>@cuZ#!<)VNC?dzqD+Rkm|?om3%>LK-;
zDEsv3jB+A(zB70-4n_t>WNP&uLJE_YN`vx-J0@B}@~<pvN6Ce+Z{~rLqfQKJ#Vu~M
zZ{i1ImozXY(XL}KZYpJFQMM%wJT&KK{9%wz3e+r=)X#(|M9z^}Xq*u7johARTeWB6
zE@LYRY9y`;v>GYp2$50;i3f>+>ni`5(fqKEVe{$o)-L`E{-st_(5KDzx_7t40A1xI
zawf9MW{4=%c=QqW(78p6hckMogxoC)*G^v+Mc)0}3{!G-fUv_bLpY@V&t?A<_<K6e
zZ4#>ad)ioCy^ro}+4&as+Ie=u+8qze-g*a=p8qMPxTctoO5FrTlLd@^*pR=3Ac#yT
zQT_-J8)@v@siZxp*nCXX{bieY-pV*$F``4u&X&B`ZYmC1I}NxX@e|_VZlfBJ^}7X?
z2|F(a^kHg5wqm&Ro^jw{$G3A|P=0F#&0Uv4S-HLAzi&FC<rF^rC@Z<ne$JgC4%?Ui
zM+R3Ok}@{Fzfek_R@eZ7w<GSEq&=tN?=kQ!pR?<tul~~4Z~tpdl*E4Y?{iav8pwz}
z#r+pn+~mIMM+BcSO_lwFJMNyxQ3H<GIR0G)<$V%g;aqAS&7$HL7M3j?ZnUTKVNbGL
zPp+3b9`bKF6yZ2E?@m?gt?q`eK4(3(P^81{yOr_HJ#7B<tLB_r5qDw7h!8B!-6iY4
z7dGIMUDM_*)br5EmILxXgaXj^lLo)Vk&;IqmxUyIi?d|@j9D1J1iEIP#nuoz^QDo8
z?j#D|Qg52EIcMZ6C$!SqJ*7w+q%EMKax16e7Axahz0Dw}ZBkhfmCJIHy(eSZKxXFd
zf}BM0HQB<`So8G5vx{UPxEL0bHb)_LG;n{Jm8EpH;W-ChrLdYF-?FUv6{vdcAr&OM
z(OfDMo#8!Z%v)eBrQuw1Z+uOzxoI4+sJ`uzuTi4+n+R}vM<h*Z>R3NImoVf;TVSc6
zxa#|QG6fel2bY3-qdk~O@QZu`yG{jV-&B^t;_WTeiVxm7)Os&82V-r7#YcO-jMh(X
z!jnl#qMSsnJGxZWy8M|TTAD|<OJ0DfXjgGAQ8hdcu`JUH_zmCXE`&fRS?)%g=&fkh
zoYD(Ac`0AHzFT_tU7=X`hO7A8ndu7U*rPR9Wqwvwm0K|-1!YvvnX<YCd_5+_`nwL|
zMkYPynU1CRHaSHNQuOp*lm{6gLx+g&9>>*J6W+Mx){{x#ipG+P6!|{p{r<p3usYQ^
z*KCBc9IS^pu2HrIsxqlXI^tqHhP=kBv1qfExy2t6FOE5K?%nz|>8NU(H%X7mV3wOI
zrF69j6*CS0(MXG@bxRK3_Z2M`7f4%l#!d|}rN_6@S2ukt5me2j|8e!SsfI`A_BbFz
z+exVq@#W_W<3zQZRSia{>0!I?lpbv8OdUTjsJtN)tKO~ja`-2DiwSIzsGMMxbIb@s
z&vrX^{~;1wRtcep>ly^tO(9ZIM=6PEsA$%K!*aVB(>LC`+-V=!NKTc9;<MdlUSmo8
zR#V$VDQ)7{y?a#U6s{E35w?FrcVj}ZkGOj@$tcbeu1V@FRILk+Nf8#S28sLomSvKd
z<7`UB61Y4`IKO8+y#%Fz-X#-W4L?*8Z;qur@_;jX&O+2o7LYdj#~6(n+sQnvM>`|z
zbc;v?f-g-Q&G$VA)fZ`P29VjyeOSu{y7KK~Yp8}<Q%t{!zvY}?n<X&yy7qP#1c>Kv
zlY@TevNbgJ;iQ}t*Hg#>rDOKt>mCqOHpViB)OfWH(4j$?WQfjVf%gGw$2`YD9>3n~
z-dOYQX;|={WAT#9+LfwgTUoX&GcP$eQEfL)RjXAV26UG>Jk1!t&cwVb?_t+G;_?_D
z!7FOF>$`Nq>W)%h+ZGe1k*7Y%7a!2kR+1FTluDvr0^e!RNkiUQ#(><oAGlnXCmBL0
z^VP*`Xlk;I!QwM-YH8?kx-#nl#ti=FpvF_fSL3~c#F!r6x2>cQnL7T&@#zxsh|+Q9
z;=cn}UwiE@;AREWQ9MVm({ryIcAdXlq_Aenv%HqG99{YxPrsSfN^d68CZ5_qzpi7A
zPqy=aD3Shqk2!G;_x}-dpA=)^bOUj^_>ecJlwe*b+x~jHpVzBtEfVvEL5QvEVZO1t
zj^C)S2qBOX9cZ%6pQT}|5AniZ7#&Ls$<dg}Xw?SImA<c%yFdOd(_lMLnn78kDFx}H
zq#=p^C(-(RQtwNwhSjowhpVqU->Ba$SN?c*(zc#D&^0tcx_tO=quMIo%hfyny)0{M
zICCknw!0;65onx{(}TcqM0*1W?B!V6+l^(G*$rfZ><Zii`N`Zfz@(yJ!x<1Dbrjeu
zACeNHD-iBAQ>&-~(_)5PkJ|*P&Ntp~;MOTph647El6a08@2#;S5BU?O^(u6$-oR_l
zpzGT|jbd-Bxc@FkgA*7h%Yk(f!-*TscQ-Smz0a$1IUH_~eru<U)$MElNWBh>yQ2+Y
zzU2|Ax+u!kNQh;}aUsqnmqJ)4J$4AQRFI7Wd7ee1)M+~@V741{d7nmc_y05q=&b-}
z8cf#ky`GSBwfBq`Dk%t!$gBP|gp95H4iNXRIv@?uWi4IEb1uzaPeFwgfCv0o4+bIv
zH*^5b_kS{Y?5@_g5NXyUFp1R(DliN1ez3z@Z){RNSrD;QXi$}E=VbSdD~CnTm?I4@
zb<5Q6&>UN~ku>{TOBGab4ih6tE8g4~NX{R?wE8vuGCg~raZ=Ob)xQt5?P@xFxyDyl
z#T3-lJ3U#WZK#~W%1&@#wP!tWfE~J!lr+NW@0oMz|KNB<Rqn#o@;CLW88krd!b9qC
zPLsQt<aNHwmk)P2ZD8AWrj$xX3Xr;RfY$@gkk_r5mC=R`PeoF58{?T-22pQ`H_Ibf
zmno=et6bFBP`n|GN0c>W>Z%;?O$d}@1VXMtREwjisxQ!;_P*yxy-=NZce@1FBL=H_
z$r`QN*jIlU)bIBVe-1RWJ$n4T2^F`mB0Y$7;|jCPZzXxJh{!&Lob<RqWStmeTaSbl
z^OIFf6+2~cr12kjs~M{+P}-y@k6g_=_-nCs>XZn0dP%n6A>SnD{~PTJe^Ly$F0b9L
zn^xA4J~pFdS}k4f1#GCgqwXdlbeJy|;<A1rD;i&?jicO=c(|k&`s3@Pzi+ZSC_p4Y
zgzB#7UPZ)yTl<#wXaH-nYUCGw4{^KEBM9{YZA!rZfV)um<G(@BnlK{cFH+QKRZQ0v
zf30J!MoTS*B0<ride6$6o}bXeKd+TZVv~Yq&Gf&;#9}Is`~gq>STE+Z478lEn7<&c
zejfT9o3T~t55B^;dNwj9FKXLP&tA|aX-8d*D$mQP1+@IyanU2!^nq<gw1*p1|8+*W
z9CW-JS8eZ$Iq?0vek|O`s2FqbK<r&u*pQ$zQ0OL2WiQu!+^K9piWWCnKWQY9--Kh~
zK}RxtkxO`pT_#*l|0OQ3Q5=+`_&i^9bJ-6c7_RFQ5j|VmXksI3J??N2z)C!mgJrMV
zf?mP9b1*m#b7E>G|2tYWk_zq|o+`+b4e}@9%8o|N^i%&$+rArf&V9}<FI+5C$*aJ=
zM@?uBu7^26hWqA!-2d5Q7N8|St;A|6msQUB6F~lq(*1R+ZDC;TQifcV`r>`F_=|Mi
zJZ=(?7_Dmf`|x+u2_z6za>5_955^%sWS&EWG&)`X4#<4c$GZ~~m9HvadmEfjPb$kv
z=l4(j3@)K=^GX-<^ieHo5b1zEKhRIG+C(sRAb#W7O_WOztdbJ`$NNnH7h>oOgKHn-
zDXhCqY#TQZgLUsK%q^+kcHQVGW5|7F)~G!rxy$u|`X5@%9f<sM1xI5flOBD}s+ksP
z7?YfN9D^*}qKGQxYw5qey;muZ8XH?|KC}2)8vvbl`{uTF$o-C4+ETS1qv5B_Uvi1R
zal)tvI!R{tPko~ks0AQxMOKQMq!`k1x9o@JyL)(PglU8gtvhT^s>*(133PA2h8uP{
z_v{A3MGBWZlsp8k;YGf=;1y{^!iBY^@)cE4*x@zt&pse=b=Ms1WX33j1TcQ(R`Aup
zp3Wk);az~uO3dN(*g%qp;?(5O?3uQ>zWUqWtJpd{A;BwrY_Dmg2>~rRILSvg{M(Ur
zwEMr4Ojdm}-~Adtua_Ic#e&Q8uI8X3vYZ%K|2Ff$j-M}ya&(2*;!Kb#dk@pAKSV({
zX5^`H0GG5vjRbv|X%aW7lmCQDxQbMNlV2FXWc1BE#Khn8EI^eaj-oOMLJwfo(iuP6
zei4%21F}T9)Q%db1$p)5BKXh>f&Qj^RJ_8;Mm$b#3K9<lJt1CW4<Swe{0+A<e5ZB7
zFi;O~Hz-&rL2=qa_fWC)HM?_xNZ$wNE)7rL-jiGA+Cmd>6M;e#ql^{w+(<qi&lYkg
zZKF`lk9+{pj(RD8lzLUuYUBbjzRxsUilLpA``t2rQO4Qj6<<7n9z@P%`{Lj82-VZ1
zX0Y1TddBUUxd2Fj>xw7l_J<Dt!eHI-2O^${K2{qCX2R`t@;MLcpZ&-EN3|f1E#3+K
ziSQS<CXXh#c*(&u8k~CD2d}2)Pyq+UB55CaGv8uh`3^Af?XHZfBp0AloaR@3rru}E
z`g$t}wfA+$*w)dOSyP+X@BGNdP<mCs=7pa5t;S)$E5-2b!8jp?Ur3f2l?9cI)h-$d
zkulcY&v=MkIF+$r%)_h;Dk5k0J^O)b$$xIMxEpb5`bsb)^G4!DuMXKT4APNPw}z;W
z2=dx_?{4VW(4D8@c#4wQ>wK-%g(}?u6$h93zltBCA1H75132|D%VA@da_1z-%_8+@
zq9Rl-X@7c?ZcK?8GU~T4!#9vSdyPQJP%0>aMzgC-U2kMt(nYb9Ln+tn7zjOYI~up<
zx8^kq@w&vVMD*uSUC2*ZV-~2g+{`dzi~+f?x8F3~BQ}sazmPFrTkoi`uufRb)>4u%
zPCn<JyhQNy>FmKXseHG#SU5ga1L~HsEV-XrtWIK`$s^Nq)(}wlUc9V5nw3*|bStBP
zyDRM5T-aXNCP68;(ARp%uFI_p-XE}PpLI6`-9NH-S3{gOr?u&yAb@wj^vK(SEi>Er
z+_*i=V}2f<6#RY0&*h~{v7T7CksGF;9y(iM`%Q{0EZ7R#Itl45(I~CTX$!8*0?wZ5
zS$}A~DC8I2wB2|&dAlU=w<99JY)Ng;&TXm$z@1uf>bGCxX}+Tn{Ko}dAsP|^iwfhi
zPM%7RRWsJ&xxE8}Mps}VF$sMdc{*Cf1ckB{$C(jaP|4bWTl}ZUxtu&h%9>rmQ`y3y
zjJ!oEerv@%Ag;tLSs8y(W>I<(A$jPga5Mq7A5s6q^9_oF#tyET5GlO1@}Myjt}Ru~
zRn1jM%Pf?IZ1v@Wj?h~kJSell4zrtb0oY<;136K=y?Cyz=le~D$IkCF&oU%D`a1r0
z+?uxU7gru|HFNJ4r-C}dt_n1n${1p`(5uioXg>Bj4&Wwv7X_EYiCd_K<$mw9({`s|
zj!bLWl1X8gGaQu_S_3+RkeT9v*8dKLthN?<Dj|+al8JP@>5riByB4n4r>N$As}Fn(
z(-o_wJ8ARFZ-O&30-E0NAG|1r{Gh2Z0xghFWxto;82V}tHzbjqP^C!GLM?1BS{URZ
zFPs|1^kD@pdGT(!10p?snfx*l{`Su!{u0S}(yn>cp2S^@DOMkT0lWqo+XOkvMao7(
z3rKROJEL*gT{n3`RpaS%bRfMRp<SS%NINH1iMIt`xHT);7YccG@5Lwa3LUEz$VGAF
zw_qSs;{l|Bry5lTLGSk?<g^JxNbafxG5!X3K8A7q1}Fg#e=$OwFYEIzWr|x3z$4p@
z+`GWPz~AE}6HEcYWmjfXhN#;Bs|giI{at1ZQu!~zcQ{AI5^9w|mJuN{lB<HM)++9;
z%7mF85XeXlcpK2Pbj>NNFmFze2_g{G1KoI&-Bc}TVJ&b7F!^X7)))vvr0?_K!4Y{a
zPizK6QXL3Adyri-;=2&t_1v_->7#;p1?=ET1%a1IL*1B`5Qv(9R1Jn|ZGD*6>wm=T
z1Jr`sy~Ea?wf~h4&^YC1m4o>t++ZEwEN=3q?v{yW;@zcg@OS!nd$e31$0<1YA}9@i
za&#YGX17=jTqLOG)_2K|*CA}?vG=H!cSR!<gRAk@=C8~Z`W~%>B&lW+k^FbW*zEh!
z!7&&_&XHKDPlE${xfXJ&`lp_R8!n}DkL2^kuoDrt-}$cvU^mbpImD=%;a&PRP2(sS
ztlCKN9<IUf7rh2HLk_)rz+tst<$cZQn-aeG5WTgZ@_9>mOGZzx-~#d2wqU6vQu;@X
z96kSS6GnLCt6yq&+T4e8<TX7vjF&3zJEx4QG5#8UI%dga>JC=#VQ&5o7UX4dn3Lmy
zg+;+At(y$5bX#yBJ`Oc)aEJY7lsHRPDlQM+D93H>aqdsO)tPYMM$Ho846{do@%#R%
z=H2dX6~sALZcy#t31VI{srhG!%Dx}I&VLf4g<H>JPT@Oo=!-Hi7M+2~il{lrk{YB(
z(Jt+tV(56;+X?p=-Zodvr~pX19%mf`BQe$+Xp3}1>!SD7dSZc(L;wq3<#%}OSpPa$
ziQ8<xhUeIi+#KOmJw#>P74yt^z)OnfZokxObQp^PM3r;%a|H|av|5wd)yJb6`0tQn
zLMA(mS%DpFd<GCx125yRqvI%9nXAp;*oL-l*S_lB+<EJB{%-SV(Efo?Tk?>(Vq<-%
zw`qYaX!E4i-~MRuf^yE=a7iNO{JeKFynkE8M9%`I966&W?Lo7?KLN5$TVkx$BO5sQ
zIZm1-n(O<a*VJtru&fVXU9WG^If1b4xpCdG`#koLLZs%cdaNWOrW*MNO=)|3Gwnm%
z(MEd~@6PWY%;mYep0DLez)0^C#GyrQo|iu*l8@KYXup1VT!7uH&8~qK!ih69uNDzA
z?Tx?N;0uFbQerIhx<%WhYu^6NN5WHN!jKPeQJ_7qDz9pD{iC{harN{(D08mJeB+*G
zHsyH4mH7zSTa*!4{JRm1{b*yhv()Dj0>s(<W;MaTZw9)#+dm%N22W*rRUSdfY0CQ2
zUNkZ<8=M^up2W!l(!|A+{2L|{2GZj{EMTOS70wvFD~}or7V}3UX~}`Hfg@COc@@6@
z(Nd|(|H%ei5U%mIcmO)%HYD;=Ac_DKL~?wYo)}$%*Kbjm3O(n~&4-)0d803Em{tfX
z>5$W+1rcJXK{9ZRge|UszK^f(c~>8SPLW`esfQT2Dg|Gr)^T)C`f&FfSO3k%ml8%q
zrl8Z2tM?V}$qc6@k@7Hup$%9$X=lS0=gi1kJ;H+;p(&`Zhy06Q$rDVR{zmMGUXu=R
zMA`kf3eEVU`_Os@g?-MrqSp`-*^2H$ejs99KWAPx?tB~&g2!%sVh4si2yYVl9a7n+
z_(A#{M%MVhRst?+_b5GM>~E-2L`i(mu@;|5xY@ukWZx+Reg&And690~1itS0Wj)$$
zGzZnbe7>?ol_ky+;P68lIkjGM-=T}D{?-K<bB4XlR2T6qaO-#Q5@;0zCS%Tjh?*nl
z`i>TAi?U2mha0Vuy%X3%V;`M$wK&tA`re449?%LJoj2(FerPiBFPpT;Me^|H#MXZo
zU?`2Wi$L9SmJa^c^KA#zhzrJby|#9tTC2Y$m{}4f087=E?P8W3E`BHP9oHq$^+H0k
zKN4@nC&#++VGgQQp<oX%PSy9eo5hsw@V3*_s_J&4g0sT2LL%`&p7Z`o*tp*W`z2Q$
z`IW^tnakSK(drrdqL81A^3DZT{hF@QUJNb*TKoS7VZ-SYz?0I6sE1Yn3Ja&FkKpak
z*H&5^L$vj*-OA=+v>hxvf8WC%*>A3Qwew?G85H>?KGbZObpG>3)#UX(ziR9!wUb}T
zZs11iX7JZ}ZQ{+s+{FQd&x?ICJ)<(|-45=Di9pO(m@Yk1F?3w))r0d0OSRK(vRbAj
zeoHjaqdD*$drrR<VcVGTl-XtQSd<d<0IeOnly;o9v%SsS$;^gP&$h{)vQ%DH{ImKw
zOHwK<@`Q3rc)%+QucV8C{WmN<z~nvdnKP7Hqg(gQ`Tn+hfw{xnbNnh3jWFC5XT~TJ
zjTGgR7M>}Fgwa?*3`fh_mNOJ-oBoA&>!}&(nHxCoXWg%3a&*h=YQzlrr(v358p%Lr
z+vgKYmWQAmLM8?q&C$i>@vF*V9?!=&v6G-Vs4}>lDkc^#FirT!Ul&yC3L9E^yX^mL
z;uk}&^iJCsJSx#j@$#&FfwgGt-Br(S<JDn`YFjS`r^{o_84j!lkwLd`6U1Bwk>4i4
z6i6x0@@fM5-hKESA_(2Jj`T*3wU5ByYh4d!GGr_c0+6qUEC9FkpI9W6U7$YY^URl_
z97D~*m7s>cm4H!7F6Gwn8}WL`YH^T$+B&!ZL!pbQrthlbie=z!I$NsyX)0GoxgO!S
zLSTr(3>WC|34kN<sYkgV3<~2rHkjz^#nbwAyOC<Q(woG6h+GP%+J@>g1c-Esz!K%#
zEd8&CK%d~-bckSY=zI7Rh{CFbHh~kKCEdnWYZuI?jJ#*=`fO);?$Yd#P`59q|1Ajn
zraduU>s{zq|Dgp&0~H^HmZ8j01N~~im^BBr!8SfD(!)RXC`S~d$PnfW$G|e+H30Oe
zz)Inc(z06y*{jTcKM#;&12)CGVtlcM2ZAGE&=Gr9hQQ!Gvzoo|jl&0#;&2h*c2Nh3
zV<VEwXjD{6Amv$56Yj88{n}4f)iz<<-P}*l7J8enHwOdo1E_ZKyO@2Ao*-B5?HAki
z94wR8zO_oR=stE_c&&d`uL;KNL4HGii=&Sb=vH_WxPQUmNZ91_zx6y)2mnFh``Dkg
z)>1viUlZ=~9!y-$-p_yqhx6k<*e-qDz_}ev=NuH$9&gCBVmIpE_5b%4?+Cms>na5W
zH@1R3i@F}IpZVVSOD6s#BNaC!x=l~Z11;3&-fLB{&(l!6l;s+y;$i7|+Z{I+FN%D`
zyfHm=!;{X70K-&6tg*}WD%{cW;5bq236RVvlQR^}A&b71fb}iZR2u2@lU#{xh4mn2
z+-Js877oL|N4%lF5QkSWv^5>AK*GKtJ>Z@}Nws~`OG4pLSmm?3Ws~em_x=8Cd~hqD
zmd(hm7i=%r#(um2o&AF+!IkI>4|Yz>1dMe<<#dz8>dVpQj}pj~qHh$$Jp@3}A6WB!
zUe&kyhn*r7S329xeF~9zBK`=^G-B|6N?_Bxc@D0>r^6($L%C+2B@fAS!r)&>&O&NX
zLtE}niZz%zX$KA$CM)xF!fMt{+W)yv=1h9z%)6;CYKg2>_|-p*uZT1dZFqa0ZhJU5
zIOJ^zbozz1TzIeFx7nnkfb?D&{jteZzo>~|l4iDWIyvmTU(rsPMhv6;A|%RL=4Jwx
z3F(~LSGKduycC2Kf`xHyx%3<cCZKVKZ{qlyw4gb$?wAjZqmli#7MTwPir~z~9S^#a
zHhHXXxcO+1MxW8uRS$LXZmPIgjTf`0A)vd_ov6=Mjy-0V2UNYcf<%(7v`Wk}QauC?
z-^*S~FY*x37sx8aH4#Zeo3F4oL^S#6iLg*fEBq?K5Jh05$1T)D2*^7RteJT8&jRb9
z3_Er`|6RvVt#`Kvcm&`Cn7qbabN2ja5mi5s*c$l@rLIQ-Qt-<wG!Nr(OVRFsXlZ}V
zoN$vfMr6$>HTA%mQj4;1YVz4nTLW-Z0)dEs88O-wk>1fiA_JVY2vTWPfU;#Q%m-WP
zAtopy$1O8X#k+MFmJ+O)K`-`?>lf|6MXnM4(qT|JC}`+UnFkKVvJunj?)Q>jqk1_;
zc8*CW-ad{RnJ>&wfdx*r{&o>PG@qzIZzQu8p9@Y_qbXNb4?2}zOsS&l^(wzrKddx7
zHah;DBb$LaIQxmjI!e0$3wME0&*IY-k_Fc<8K2E<!VQS^v^FL;1M?=q(iA@OP*IP|
z&b|bBfT^s^vawlA3Ipsu--uW8Enw92Q_IYq^emkm=>!;Kn(erNH*seI5$rs^s)Hhb
zO{=lX-vflAI7$4(RJX4U2e|G^ticqQ(i<rqh)L_ez%Hk|vQ@etM1AdESDx6vg;Rh9
z6^DZj=Ij$lb0<4f!%*O*T51*;r3P3oU|7YW*Z;Nsjz4g^<95x1ipp?DS_+UHtgdYu
zT*0&Xeb|<J>RkoZ4(pD5h8KuKHyBOd);6JUQC%OgbWl5PlGPtfiI_=m3Hc?D!Z-Ej
zya6e$fmU&avU+cv6=%tMIxLhQEC}f?h%lFz&%-mg__LTXo)h)}U`<;uM6lZcC@dDG
zO5@8>r~*#_qfm5-l2I>2oh3-sd`L{^G6R+Qh1z&GAwf`LR-RZ|x7<yFFY=Uyd>*&o
zL61eJ;OU!|1M`ne^6^CG_LsAZ`u2V#b7u0iL;tt)#ZCV=<cT>!l@D3JD}jB#krxau
z|I4S&-NzocDwiDDmu?KM9|~ZTW9Zr@7~h3u(Y^|OQRz!&o|>NqgP2xw#USi0(8P#=
zG-FEcRD6KsYI3&SUqY}wT$yMbr;wm2Q&lc2Qg)ob1a7JcQn%Nf_0=J^_ABI<1HlkR
zn9b5zkkW_5C<VkK4z^FL1%87<Pre$SA(|NAyg)9+HR9W(t&*w5Unxz0sv$EIABj%p
zg%R=+2ZO<x^c?Ju-lt2g)<o$_^JRM0hit0PInRIn1OV?<9iH=a?%u`E@)}l}gTdAk
z|MMq!`96ReO^hKJDLXiM^rxNq569Q_@oB9D?>VUbNM|u_=LG**0wb>{C?YSehQggc
zT(pW}24JZ6nCrA{YN78`puD31Nd2=b;|OftwP#&ZO)wn#wGPMIzHyQ+^vy_zp3#0V
z@)$SrAODg;RdXK2T_Fx#po4OUu3$l^ccdp)K)eE<!1a^ZlAr72^!g8@f<>|FDE*q>
z7vXLACw)#YyAS`)dmTzPWxF%B-s&GGHv~oX+S}aST)vdFb{;<DuKF0>JPfZ=IYeyz
z0i$M)$m$>8Hl(!z`(lBer|0Yb9ohro0%PqM-PKYl+PsKw7-oT~(m=Z#`d7qo|6Zbp
z+X2m|9`GE%lLlF?`IlDG{?{61D>4D^XAVS&2iC3bLF<?c?wO)HH7^Dio;TZ_C3SWr
zFS-XA%Dcn#2Lq^E9QCSm{YZlI0x!%u*B%VTiFnWt=h5ikZ7vWDz#PW`R<cE4gsY-#
z07{}TEdb4*Xp|d-3B<h6U)1AJ#-+0v&%oz%j}IGDEEBYFJGzkEZ7lfcT-sed3^Y@9
z@uTaXUt1?=`1Itx4(Dm<d+b-zIp}#IN@x)2dAXWd`jy{TE;RR4M(Ch66QSASgCY8?
zp4&Ay6Lz4#OFZFkUxgf^<_da>6rZF3HGn7thg|=DuXfqLw4Fl*FnyAwNmM4Ih@o;X
zeU!h<*_axh0fVfr^s*bbu_1X2IR23NAcoFH=E8Tx60wMwK*@Q72dSt8<zf`Isy~Z>
zLAsjfXr;+W2Gy2<(TKg{J=^S6Z=Gy|K}?f=a%}2bMzEk;`#81hZhqT%@R>TF27`FL
z>SwzBnD+m~+;BeCB)S@W7?aE7-331^|B3mVtK`wosTcSiA5(P_sZy4dGA$eSFTa@0
zz&Qyh+=R~Bk!kDt?mo-s7x%8W7YFO(I`F#$pGf`ZKY$-<Ok%@<Ne~oJL>nv9#tJd~
z3=i<=7X)D0%L2QepGd<|aCi)l0%hSwp}Hp_;0TEN5ZG*QYKHqS^aEDs?KGP87{qpd
z4v<EPg71A_cdruq1+n@%vwS!o?OVA>a<aiCbSbri!AqwOZFByk>fPhfk*m$s@px-S
zIC5rOnv-r_HnLzf+McdW4xZ5|N=9qsbh>b|qpGd>WCQ3E*3xvmQeu<EvYK|K-ly}$
z;mh^HaI<`u8_UPrnXOY3mrm%DNk1|E`_j(<I>mRje8;{o-7ZckUl*Wlg4sz&;|Nrg
zFso_x)jIMwEBxz0<B-Kw${NGss&D?cFXNY-OI;Q(x#vFlajjsuSd%(@4%d8t3`+bn
zKxRS)5@3{@2EtL1|DjWm_0)%1AWmXs7%k(SSu9P~<Uy!>EuoZ^3v?3R4IYFM9yXy!
zNE!RF)NB_D2F>Nk1LhoYVbiF|ppF<xR1k5L=;3!V>6-AtgoZc(Ns?)KPSWCI%;d9-
zsGg%{F}}apd{zqvVXYW~H+7qndwJ&z$K$4^^7TaKNam=1EHbL=ljCjze!$uj)MsXA
z>?u6QU)$(qQ@xHuMLlui=^u9x!SH0%w_T%*X?l$9TVK-@bOoFs9#=1#*KZT;#Wf7T
z^2Ws71QH!Ehs>kK|I4D7TABfa{M#AhgZ&7rSH!4{{pBF#)0WmkeT9V<OYknsPZOn?
zO3&t<_2_;<st@kx$zj>kpF6-7+A72A+9yrlE$t8+<SKT6Ou(n3mV({rc)I+B0__-U
zhT!>qjWh#2qKCE%xAjwmpmV5IxTZ<n2K7}vJCDZosXtDIgK>DGi=6FU%lC4Y8+Bfz
z2MoOr*sBJ%0i?6^bd@}RIWSfgZJ}iC1RLMx9;O;RW;f(~`ooivY4DXvYBUXNdyLVD
zKLO@9E8p$!J${R)Vd-hR1{LKc`AdVo#3%3yTs(0p!UDbAY~7d6YL+4P7gBUI><O8p
zm15g`x_yXl`3}60d>>xU9+y$W?LQfQse{%E&cB#w<2}8A_WLOyNi3G@XnV3WS4-o%
zG;5>~!H>pI=dFH6ugF1{l`?Ml7`M*pzA0o?J)>XTnZMVPv@0DSLcIBO9Y?$w2vWK)
zJoypyA@LFSj!#NW1NH@p7*~MB7aBR0U30+@mrcqpY2_OxBpe(H3IWpf_9r2awpqdv
zm=r`>Y-soW^O4n*ZtzkDY${)=qOG{m+OHphQ-A9?IaCuAof^td6eiz(pldd0eM3l=
zq)*f&L+`-zV!yG5-k(en)Ogq3c+21ZfGB0+Ed74oLl6ER5QVF_rmLxus~L}pvl+Mo
zurRZ*F)(v7uyCt>XX9b#;`z=@#|+-3VcuGbu>Ai5>>Nz3%)S2afW$DtIdA~=|MuW&
zWoPE%YGmj5f5!~|BtitoV0^~7xLfeJTDjVq0Z9J0crw>rgU<t`#O1}RL=1!f2PHAr
A(f|Me

literal 0
HcmV?d00001

diff --git a/images/Logo-Red_Hat-C-Standard-RGB.png b/images/Logo-Red_Hat-C-Standard-RGB.png
new file mode 100644
index 0000000000000000000000000000000000000000..3dbfa2366802da607d75a6df6b2ff24cac026fee
GIT binary patch
literal 14314
zcmbu`XH*kU{3!elp^4H2q&F4$AyPzYXb})lsvy0K^b%U=B`64@6sby=A}A&F4nYv<
zy@cL-=)H57|8veg&wX)U-F!~ib26FC&g^7o@}1$6x~c*x2?GfL0HiM!<ut%!Blv8l
zAO!ygjW(@=2R3s>4HW?JegpuhAOJW6UqY<{0Foa7)=dEb_6-1Nosw%_OMnT4Z<Q3}
zuK(w8OZRvZ0EFvb$~}MMIleh%1*gVh33sg4n6tPtbn!x870HE@`fS%97Z$%&u`iZ0
zkE|!8@_8~!@Pd-^wmbYe0seD!^~3{*egAKBh-tb9MYWSgM;8rD!BgK?$cn72+${@3
zsZbO=_YpMo6!bu7w!-^JeCYgC&Qi`2s?K2XpluDMnz`;cJOxM+^?If51N9>XsTJNN
zs}43*HFLJ`*3z@1^$Ey@ebs;y2d<w&L*TwGfDf<*N?$;L(>9{?$gR~LSnOS)p0(sb
z`nGCGvxy)Fl<0owKBZL)ZC+*8pB=(xNb?F+ud2lD)lI}qwVxHdb<`$vP#zG@2+Ih|
zCsJ#}WD=(HoGtxa{0V5J81z&oLyB9AV_H@5qT{4Q{2cN2D(ShOT^*@vbB^!EEpWq4
zMubZ29-8vkRGJ{9;c6onFZVeC<3xh*1jQ^v*ml;x%dN}M?=x>i3LOp4a3U2~{aXs+
zaB0NO`#-mVsU3YkyF-FL^~x|unh}E#YjIn^V))r9-YH)C?6A9|IMJeTT7&zU{u0l0
zqiI_sI~1}Yf7^(*1`pP2%Y!aYK1`SX+7fgx=pMjYfMXaIdYiKBDo<;*omhXHKUuWH
zDV9BbzwC&-JOEHviG9#vmJ(ro8!Y0E2dv!B)`!im_4xS=5u{|{={#NWIyO(_hri>c
zVdGz0tF0bGxQ9n(vb-4JHjAG#z=#oCT3$=a34C&S&rkn=tN!ru=iU7{B5fAn4%5d=
zi47}wj%^&RmN5Vvq_@JDx$JTwv6PdOiwW&~fnU-d59O+VKr+BRBDq&OAdh5^4#%)W
zeS?VUY%f}XMs7iFAy&+3k)52vL~3WX@d4Y)`PXg*VJk`RrT$w;`}t9Pe#g3s^YJZI
zpk8I^R1aR1{$zPoCycq@Z3qyY`c`M>g++a#Ukc#4=57?TFzT-9fDNt4Z60<Vc0pon
z&OdH460QbdWd~&OLMJ;nc`7SUI%5=CIa)cO)$?2mIZOl($r?(1t%_MJ)}B^LrT3s<
zsQ%7sk(FtDw-8_KTCFOOELSO4shjg4@jV0TV`qxw^76MN_@9hRo})_Bl%FSVKH4)n
zeypbaUT?Zz3qhvzkpaKYsnQ3V&eU+y5J$P`jJg*nL%s$*-)HG;Uai&4E5O=ONCUZ_
zUXG6R&kAwO#3^(7wUg;pqc8kT<>a7?nqJQR^)Rrk=;>NYzXuF$E;dU89l=P3jKVw9
z<TaA3!lv(z7mlU<$yXD-l8;5n;jEJVF-TYwgAkzN`qEq1n@$mtA*~!hhvSzUTzyiU
zW-U$0Z&NnmRrxIax<Sb_0S*`w(%#`MQdM}xC<Kr`=ocT~v6f{!zl<W1WhqjX?I4M{
z!c`%eOpE;Or;3q~*HbQP9g=1#VYxR&I4iizxZ^2$3^JyRppbMLBlP9p&%D>|8vpb6
zA3Rloytd62iJLA`eG#h?f&?@K2c{r45Sx5W3Wu+(MFkxdkKyueOMg2)!Bt0R8$O)l
z?U_F{duo<HNNMqdFr9sGC-W-u?B?AZg}z-Y-^ioJ`l};cnc1waQK?XGyuGN=+G01!
z_y00v;kFTWF|prbiQgr=<S*)eLNdr)rI>9~>c|^HzGUZZ7c>xszUSu6uZluG-V-V#
zN?-naskWG$?$b;mq~ml34}mhHzU)VQW}=0hYTc94JpoXz?k)B;jK9Y-BmrdHhp%+E
z-U(t2vMWhu@!rL~D<gsn#_C})^4CHPeHd7y3yK4vvTu4c@{4#AlFM~kliTq+ZY?-1
zmUN7kXp6OqwM~Dbt?sK><9E)<SLp`Y{0gLSl}`w!Rp)df9Cgrt32y%`X^wRO`d!uT
zltgHB1Lu8Jxgyo<`c;ak8m}klM`*$<o#F7oaC7F5Q3Gaf0X-992*?7=4vHnj`;U*|
zA;Vvo)|i41U@L#b>xQttwH5I)^ie0GYTB$G8ny4c^W#qlP!}s5H5j+`7%aP+`pryA
zy?7FmL}rx2=K{Hl{tS0K$(oMwE>+b$>St#|7Qd9xmbj<LYO(6D+6}wIzW(Q6DX<Y5
zi28HfY(R!+hpCLog2l;<A8w7-n(O7T$<;4bMOX`E&@>jPzEpW>k@9l`yoirTw6Ej$
z3`oFA=H}G(EA>8+Y=*rUlMO-X+9eNi<lK(hvRk&3e`ZLzmzG~LFp*sel~dKe(!R<c
zw3Zr&nku_oo$cW|Z$AH-B1`I^m;ze=6<F{Wi+Wqf(MgJ^_*#wz4$G8}6o)?<btZmP
zKuuq7+YAgo9I+8(6$0d|Le|dK&fxM$yI<w8V6PBVswUKn*NX?<b_sL|=;rhrmOX0;
zU1T(QX7X%=i@0A|AjK)fiD-oDe{%0}^3w3o6stZDwTvFxCEX=8OOe@s4gJr;aHf(H
z@c<YrTs>HI8?gcN%?}bukb9P>{x}8ic>=rBgEPrjAHn7oOxkG16=BVQN6SeoNu{cp
z)nNKPuC00AsDv`pqxWO^%@i8KZG0_EVPbz_!OH{Y%y5IY<^{qQQoO3)dgxN)QdL>S
zF}64&42eGhUAnMsDOqNqHF<h$C`QcEuPYHOqvM|Q`2tOZj%kXFYd;eB9p7ZMPzYH&
zgKfHv7n6ax-|*_6sh*L+WvBLPmh^J^nZR$r+dXH#`zCTFs?Qb2{viWu7dP*MwI&w=
zXsBjjClh~WbaU9U>|-1QJWuB={=XEhTM3b|k@$NVIxYEOW?)Y&QMv0XbuQ7JrDHz?
zyphx1)EjtKqesJ@ond;h{R@+W7d1;#SfrXMmJ7*ktCdYsMZmgY1nlF%J~2;4&G~WE
zi60nH(JyNhzi|9RwKrZapRbX;ka-n1c{x^LHKCi+$20`QJ}F8Ihzg(pdyq9}dvabR
zTFMfvr#e)<gf-y&*Rq<>P3I8*gl6WKGVKCeFr6^{A=(7ve|aXf!!I!;F~mfC+cYJV
zV)KFcwe4x%5>U6tw`gLTB7gZBsvbRsaL0^YE)QN~>;C6W9OMxxl;R(dB!}SF<T*j}
z?T@r~h_pparhJk6Y9<&NtNRp9Uxoxv(6bob9QA-9fO>Ho2Rc8+S`43#8>Jy-WXd9|
zwm<!)`joGkD{Tvq?CEcpPupE4U;>mxX%2cv@?-91NIsOk^f^7oqj<FaWV;I%ewIPF
z!|~lIm>ZB@^IP)+n)l=v!+|OhdRc*wK(Wy_Z+$Iw=&yT1FxvwxZKWx#iS)qbD`GC8
z$*4-B8Fz~m8NaytiRVg`C;%`%wc6_i4As~BhJK*x^akp(yigKSg)a<m!z;LKWrpzK
zQfDn=v{n#3%nBkE19_+Nz*4RY5M9{_8>7KAz>aVEs=)NhJR_QjH0PA`5dX<^NR^Jd
zF7?I{9pF3yu$Rm@!F2^!2DsFSDQTmm@-x+Egp18-kpWUHQQp&2ejXxhHUVRMB^+#P
z-WFYPPk%>JNv5I0kK#8@Sr$$hsw&)sS=q<icBW6-cE6%twn{qsOzP&mmR`pK_9e-s
z$&j^gQQYi0z;0+vrz$U$<ng9d(K&!~N>iR_!!~o%7^n{F`PLVGI}9b}s_oEonllsy
zjH;SbkPL@^993s)#?(sF@S@wV;x4!$r~m9K^2hKLGiBe(oJ?>Ad_d?TQu%6;nqr;R
z^`Fp^+`EVNlu~MJLDb|4-{+#|@IvzoOj}@I7`Vy_*^a%m&b1uaX1od}^hMHV&m7aH
zr1C>dTo7>*o0HvRzMD*)Ix|c83W|zj><9+2$1c?A=XLG<j}-KBUb8+HzpdEtX#C+g
zep|f9=k0ss?<%ey%_kA3r<Yh_c4!}arYA0aB=!)nXX)_{3W{ZpUeY->oN9&zpS?DQ
zTBlIOQxPum?A-PGgzCD*>&5GZdbs~K?z5IIxu#b%;`X&?_V}S(*<#)~Ps6>@A{H_B
zL?z$t+0qZaV5gKO5dp@^&ds+Y2?qSS*1ruy_Er$!*p#X9Blcv#$V9`V0aiJOLq5gv
zz(be6@_ezqJB;5r|K6YA61)zq9FD;Jr)lqL@5a`p@H$4XQWp8OVp8+c>0~?KO_5YI
z=AzA8i6X;m@kep@+oWREA5vjcz#c2wMSlr@@dBnTto;w>zvimjqC=VKK{@Hw;5gci
zou<-7P|65~49y))PPppjsI$Is1PFX8Rvr4Gd%t;=b-y*jgnhL0bUA0IC<@_)TpRR3
zAtkDEp=Wm^rJR@l(vNTrwdydU+?L8wb`ZGZHGK)a{z=5OQiDMw?9X+AZy36uV;4DR
zIr544wRALt|I}p-bdPeNP@_hnF9D6e{B}S(D*zD4FWAiA)NOqujSVL3)9F^@$=ek-
zxeTg{7ko|1-quZ=@KFiUYP(glRg*thwBI6$s-xY9E)SM{G#NV6X&B#no3e<hr|Z<A
zrE1_6vI6faN2%_&cv<roKZ^<VTam(3_s*Jdx8cuY>Y>ME@0ist!_j|W&-)ck_K|t~
z&$~UEwzdaX@?$79&I-x*OOH#fQr_41GQj`*;0dW<ddsZj+Evi3lcdog1%F-aaWXDb
zHSf8|57voGGH1S5J~bSlpZEiRD3ZZlN(d$Wu=!y#>Y|_VdR)=f=H7&WN<H>Ot|1xo
z7uzAdgM8q(CEHPSq3wIwcPu+|Gs!et2_S`QZ~fZUG#_ym#8Ox_2)n#Zk$WoE6keiD
zV&&`gW(n7#@y$FiY9M+#9R1_;#!Wk52-#BBFg*dxIMKx3?OP_@>m{lgObDqx<OzL)
zu-Xc4LGPwcE@DmP$_YnC;~qAwIKhnzG(<7caLY&Uvqx~OL+y?k_j-|Ph9PAW6RAUR
zyVrR3?qN$Mm~Rgma0}a+E^KmCHa=*p#y#?Dl+u|gp?AsE(7UEh@!emT>e#civ`IoA
zMzGkoO;fLMl`FW9INt)Qb{HLdnwxGDmZ-@A%RRDUw|H7vgFr$)htXuwWaVqdvoK3U
zISU+qrzq*tdr)WYC=!XhOQW>ZnQ89pkkW;<Y~p$BE2~TNa9o+!uyTKgHH4Rum^QHe
z3-dcN0XEEFbi9&2-emmo#0<hJMgP!kM_I~5Dh>IiWV_0V!_kjNd`duLbctpBJ9<m#
zw8nxE_f9V9PTK<aaioo9^Of_nmby&t_uBXn`sU4?aW#THePwCkOS;Bx75}*Wc`>*y
zg)`>fD$T01;TgW{uOIg|&x)4ClF_}qC8|yFFBKZxSz559O;{dSiK=|Z`_E02Q_Tt_
zCT%CzGa{mGSdSNVd{JLp-V@zs0pz0zu(XCma`N%6PgaUpEZRSbnzZw@^F%0J8)Lpp
zO>x!^l~WWx^gl~Q-W7Tp&gV$)n{pD1et<3}lNbCn`T@<Wb(%<XF%ua{adq{WdcOhw
zQ})PxY=VIQn>ftYjT$9f!-q5}Ve#u<OAnr=tbdSiZjEM}TehFE*{yE7?$vIPpq>8S
z?cIe9YvSQ1JlPY<;=rZLr3}+BG-8cUZm00fO_94qe8C7_-Hmb{82USeAEi=1bL}56
zlF3(dJw<x(VCC!lSG+cXrp}N-mFREu|0PQ<sO2o)`xLjMCzEG#0@FNM*ca`B(Q~Q%
zXtKfj9qkMGdGDsqXnAHjtH0b&VC;A#nRIZ6f32v;IpqOL!7|=5KEHBc<;sH@<?owt
z&q%*0LiWnG8~ZdzkF);{eN!EgRoBV*t5Mn9kxyvZpg~P^UtE{Pz+E%7qJkYf<4M{p
znXd-1NqKM&olT?izyrHw?PYCL*Y45J30qOUvmC;roO%ZzgAr%NABRnRNAhz&9nQja
zIR~D6KR#LKOrDomy<@^nd<?TaWi-*b{VX>-@3f9AXhr-z8W|LWUvW$1SuFR-@?pw%
zTh{>J@vgk@v{BOTHf;kG0DFn49woWjuYqeai1X_;z5x?}zGB32#4+FeYk;@pCv*yC
z0VfVa>To;>qGGqbmDXNHMHWJK&oOG1%`8Q|mWg6ZtwOKLiCbH1|8#m;NuR6!XiX}w
zylh0H@xpO-t#J@#9buHq{9(;dI*D>);XT8$P#0wEB4LcLR7skGD^aTH^dPW3KgOE&
z!JIc)P7`+uVz<0p+QdhNlI1uGsnPAC;`yOeVKlWeXn)@|A>J_})XKMDR=oySUUh0c
zlBtJsjPz#2IXtO9^dA8pR<zo(=8?WrAdR47dR@a9NIi2D>}$ksID3C&)-}5GZgY)q
zdFPy+*4&dA{U-4)!ln>xcrd2!m93|*?)O6C)=|G;1HMU`>GoFreJ$S*q>S;mzBX>Z
zR?ACEwH{&737`)#wcsCl{@Y|`#T8GdJFGJdI>2i1rZo4T<%6jC7`GKWT#9e_4miQ1
z4zcDp2@eu6S{^>N<?(%G#cjy?+IVz7H;UuJ#1m5BB;%Rv)XT*<cXpS1u8Zo~oD8St
zoUw|xjQIeiWlMC#f?eT`-e9Y4!%wXxocNrPO@>o^7vr4!99m&t=*Rn=Dv0kTe;C>;
znDZHvRekX1N5!{H!s$)YZN^<Hw;fFy+3aO<Zl%1bOyyH0NfYt3y!?I`c)^^+itz7p
zH;<Y>*AnH~tK@G8yVT>nFX#6u<0R3x8P<MnCEz35_mQo!Z=!RsQ<GrfN&`B({_u?R
z3`!pu2Ya*L=>3f11(JHYf6A)NPAL>tO5O7~OtJ&kj(Mh6SA6~N3N=@u*J{P(jCi%8
zG(!;#tMITVr}H~+{=-UE!Xov0$YRcE+IUX(m3T@t-{+{3pZ`QhZe1B{k)WxJIRWPx
zKlE|E_OuJ8iby?F{D}QRRy3-=zo$7Of;&M>`rj@R<1`ZHDS?v<ifuS-vf?v;T%@WY
zXh}#bZ%7AOO>)01#ienW^yo0c*^B!Ny=s>sVhB!jlCq{kyk4{aVje=W!6il)tTFOS
zkmP(;Tz*XKmlxIiykDShyF9N1xJ<q>0$c4e7C+$27OkGGo^UClY6Tbak!H@{(Oi>K
z9#u}XJ+o;+h$nATzECXD|2LFklOOZnzgMX&aV!L(_W8*L$)B(4GFWdpW*I0{l9~E*
zIt9%7k2G`qw&dE-PW5TVs?P~F{k+!%?I}@JRBZoVv6S}{oTYW#qC413M?gZIDOygt
zDn?le)(u_uo%bQiC6&ihsvh}63~|Bx7{0%|hrvz_Zb@Oj!(1(Sw6|Ul%>yI1VwDEA
zT&|XU;l4|aAyC$^n=`;W%ZaoO{RlsrCX;9W0<_azn+6C~Ra2VTMbnz}uIve^$?^jC
z$A6f^Od{iVz4{71K01844h`iMOLh@GTxyN0gAj|pdnLdDm#>KnjDz6JsF0=4zuoc2
zIAz;u5aQ(I7>6mP7VD*gk<kM`5F^9rJXX`60Y4UkufG{<&6WOnQ8ZLJMD(OpZu(1I
zyZ5NvRM%B1S}piixnI)$a4ECN;p$Htx!`qT+G5+z+X3t^k6Kh|#UUjl9<o~>eNUZ9
zwjmcW2d#ET*p0w^ug&SoOfScmlnxZjSCaQ92?Q#3d^g}D?V*p>>HcCfxAJ3(vSSRq
zWR`BBEUG<YJgI<3qd}M{PxUp@^eE9;)9w#Kfyv$vQX@Tkzz(bu!&7H>s^>}N{IZH=
z&WINrOquDc_6~FQeN!A;VPCzAi^#X`O_KJ-35w5bT;!nh@*&iZbx#aRXA&XRu9j1&
z$fQF{wnSb%YXCQY;w=`9{`9>Gy6QfvpB>2my31nD(lJ9LRT{3jx@moqJNKZ`cdp+1
zc-`-;rh^gw;{s)p?C*@Xx6boQH@4B+HLAomlfPiC+QQebI1x=ywxa&%4ej(A`rfj?
zqe%qve)n4~DgQSY|G^&?)?xPiIedu?-^e@M`^Wc%=u0GDr(yiBlRe^75#uJYzQCqQ
z3?lgU7_ZS1PJK@J(eUGaE%Z~|-^H2GAg?<Tg*%5qMLEZ_ye4bGn0F*nEQRhTi2b_Q
zah67_=Ns4xg9)-Wzo*yZ7k2p~xBJ~am`~RiI4>}~CgwA{LODBcYD7m~cG5j)ctbJW
z??JWIdY$L=pV|r?4rQS!X1-;$W%Utk?onUtp%FGP`J~<9QKebE9`PwcYT1{xt`+NK
zHn4|pX4|7Y_f}Ew9xiLW#hS<@C2z01zG%vlgzsQk(CqcE5{Bf(?~A_(!B2YE)Set8
z20u!?vb^lp&0&{&x*a4-D<ZOUSlq{!5!9T9h(1kxJa1P)ZgM+*Cl1%;jeo78a8fi}
zcF$z9;6z_mbOHUzY0d;K>5CjH+20vX8B20C?+w?=Bve;?OddfRK~N$fndhTz1%`Em
zvqDbKG(4aCrSxJeWik~hjn$t8Ri~E*Nk&hO`|?m2f8%JnqvK*G;4U%$d5f}vftczC
z-R<p0p5WFAlC(Hc5?3Pe+pXbK!9HY3wI$Osa+LC#R(DdKz99u~MyDgIANq*`yUchW
z7|MguPGWY8kS(#wF~`#3DhT!bfIx{r32MV9MOHinZ(w`dds^$yVp|YJhQpA*rS8}A
zxav4DQ{%ajE`w)~2m1t-w0#5?U@Cw44D{sg%f4!}m5-3InInnGeSVxEnBXN?0ilj2
z`d9JA;nuru#J354+NkqvDMi0V7!7++u5`IH{=qP$?6-U7IBBDc+(2TM5UT&5UcKev
z+mtX0nW40Q+YsMRZhwR_?d0Jj7w!a`Bw+IgQ5<IO`T!;w$95AJ6{jdI&-KxvV$}0s
z$A#K(tDB6YR2KT8dZKZ2lBj^!C_H#cW9wuqQ(Nkc&VWu6>@Isytkh*x#2@AlojWXz
z82%vk^lLj-XV#~tNWmrl4!_36`t$fL16_p&K~V#lRvXoSTtB#PLM}LMR4_07V^H}M
zDIOlv-7r$H4iTpjHxZhVLP^wh7VVggPL2`0T3D}NuOHR#kKQt#0wdZ%6ib7bt5@OY
zB4tE7T6@2H=TloCW0F4C)8`)WBiEsh+_-#AN*TrWxWTz(QO<Gb$>Wr&aV<L?f+z8H
zCvz?2sIll6Dpgg}o4SSdu2$;pTXhqee!_aH_y8POVNOX-=C<vUAJ~t^@ab>a&y_yt
zhTIQ|;w!B>{%`&@e)>eQaksaS4SD)v;rIAwJVbQe#xCaVq>aDr=12b)qyB_EfBhjt
zHw3J0@0xag>F=K3YS%enP$^@A=2&Zz=vxgFQfmE<uCS-&MHgLPZGV-*0t*<kmMQz*
z{!yhsq?~Z4pyzqYhqMOO5Y($r`G-?QwPtYDWr`4XGSr5CzF)p1?oAMdgXy6Z&wo6`
z6xH$jPmU{3-`vFXR*exG{iD#Ls!Q9}JZ98sJ&q5J!FSW1uo|@jWAwyapTF2$m+j@m
zrGcXp7?~asFeSBvdtZ3}JG{e2BzyRA9kO?Y;6SWt(*#iv=vw3)t8SBqJ~lYjJ@viv
z1LLXPBsPlBgGXiYmGRJc*=QIC60ggdN(8dHl{cr+9E?<y34Qc*YIUl!7Moyla=V`e
zRkN@IVFkv1C@8QnL-w?NT6|id(FP*IlcS9=CU&`$)k0UK2a@Q?Kgocr3o+FC{ZFgX
z5f9a&ed>G6{goLA$f;T0$9x7n>ilU|jC3mUu?(?NJiW8KvpY(){4tl7M#GgSxEh7;
zvD(~2E*|(k@VsH{m^3Qk(!7;byhQZ{F&C+&e-3MkKmIEDmKIv4K0`W^0j^hG!&bmX
z8ueyh<yeKt<%OnO&MMv>86vN~;NQ(@(SJGSEj6$NudP9JNfz<;$@M2GeBL~N!7|}8
z!ULkiv!7TIlm#X$KkG?j$=tILD>BsF(CZHhq?XLl6dHFwPMeEIZr-6&F%Yn6&x+;?
zIReU3c3X#8b)aw4o*{dNATD_-Drt#iPD`a9ElACoBPjMfJ_^e+hrsY2^^$do^OM6>
zQr2LDN(~aWz#_OHWob{ixcNZkflA<ea&hBLPlCmn@e1z=+mSiqe$|glk2)W90x?ya
zLKRp*U5lDSqe-$g7ZR1Br>l-mXJPYW9um!c8g*@}HT_!x?(%e}w^3Rz<Uy9b0DXi1
z_?ZoA?sQDaijRQpJ*j<crLQd@$8M<Wop8X5$_m@QJwpq>%FjMe*dltzm|-Aa`7R}b
zqWfJ#8|Fg*5gg%D+qub`=O{S@guZgpjAnc!g8z_fr8ij`y69ls;C*TfcZ@EQG!w_U
z1?AG#Ympj@c#?i=NgWi=AqrK6y>ZLUJv-EZvSo+uzmoduix(w$gj>dvwxR1CcWYWu
z`SYcuy{jFT85YWZ*HwG1G>z%Fw$~37AVqTb?<yfK!BX{SqXq6+KEco0oBca02RHON
z-ka)#I8O#Yru_|e`cN0TRMtwjNsUHb1Ttn=1?Z=kh^V;3H=0EVADVcy>$K|xU%try
zSIU5Thg<8;5rLjM+7T5p6FYU1RM7UZb7cHHK-SiPeN<T(appDHi|Tos(7+4EL(YO2
zfPQ6{x+ZSa#QF4GJ(O+p?tn-ZA6o@1(OZy)LMd`m+$9pJnBi~-N2<gWPfT}NRJJzo
z6V+q5BDx|v@~hzs1HhGJ?EEkJX`_&uVPX~aO$5}*1IotY{C4S69I9$<_hl<h)%$1)
zfWNxjVk#bq3iMU%ilT!LHCyI%tB(8%ivZ6-wSCfTi@(u9c`aptG3rIIe2_d4ZLHH{
zBt{gP#%$>CB*tbEb^jG*F`1I?GkuurpDqH_pS`CBt@Z?NrISguB1GzXi=2DrDTRx<
z5Q;q$|F-S;8PX_Ri^yjLVOybu|NaRn+v(|gNnR(=4u)0Lc!?Ib1u87<EtunDV<RFz
z)P4{*Ei?T&r7RAgDe#%u@`I#=7hW2jL#=b|&<2DnJ3k5Gp#u55id>42#r^0R4h(d0
z-`KLQ3wSrdlIrP+7d45YbbUY=_2%gC@X&%;`+Rjc|Jkpehw$qWR5(-^?`&ZrtL!Dj
zEe$L6=9~fyW(F_c*2{U~Hv|xKsW6p%B{eM=HMA#lQX8xrr~|y}|5p7Kg>Nx$(r?~s
zGfXS@9l0AtAW47z?g?9pC;2hZw(?L~)xXP|Vq<MpR17ADcNQn1=9P-)W}c)E-hdA_
z)`#*m$@{*q=5ObdhZ2sCkB$S@nT!RD-LUerA7EV`y<Apx;sosPl2ejHs+Py>O0jr`
z#>*F7rvPp8nfZDo;IY#@PHqP|{k@pA_z;!Us&l$Wy-kfk8KmtQb$FnBXU;pexuMA>
zwu-jIjoB880uKS5EAyF1KS-fbgrEY6sotNF_XXh37M4yHXwh9iYCrtG=jh+YTEK?`
zyHzY8_rubmYaGZRvixrO9hKW~D30?$<z{ztC2691lxvyY#eseVP2FQp2+W`Z@fdTf
zPt2$o*)oE%j`J(?6HG7tDbWF?5UN;n9Au`T*Xt=sCNM4C6<DwUeut)prIuWoSxeah
z;H)FtT82)BxL*ToYIZrL*HE?~3Z56FC<>V}Y9ZkNC1I_Y4D1w3EFF@uKE$DZbm#m>
z>`o$=j%QPDv-yX5xY7~$Y3mYeLcpDk`iA4PX<Yu`-KKbOs;wOIjqE8i@UrNk?%giO
z^p9$H(&(fhPvUi-6zk%BTm24#{0sR)PS5%_;WKsbxy5!uy$RvuggauQ-l1_xHi6to
z3ZJRYb*JZ#IQ(D97Yq8%hKmd5f`8=<*jK03sYwzdUXB`jD+Y>B9^Si~o{<HTLr$pm
zC;!w@K_?m$JQgXKEOXHuUV6g4cXuBYh@A($Z7fJM5URAz*SsXndFy9>_U|B^E7?i@
z(zZaV{A_5w**S^Go~6hOXw5#$0_A$=MMa<at!#@2%;@c<iOc}82|1>(|75&>5q8Z|
z2nNK<I$k0tR9s|k>?Yr?eX>zf^m#p?XI-`CHR$WYbWq(bFRCWzgr7!<?lugq-TM4?
zfAR^Ktd9R|eV7XAtxS`Ev#^nyrd&}KNaIt_QGuXcjd!{L{)Lk-3(q2;u3KHz&%nJk
zdj}nZ+-lH|c6YFJg=Q)7x!@XoXjr~1g_crktOS?W-9GMg9XJ}8bsU<?t$lsH8)UM}
z?QfBChFg`L<<p&c=NEIR0{Gm%!M5z&wLq8nCFz1n2q<7Xj5~Yf_j#uYZI%o1ZE1bM
zO6zBcFN*aj+%{xYyy7@bSTxbixo_JHA#*ZiejgS6gHT<$yl}Wi8^^##9!=E#0i30F
z^|Ju|rb9p&*QWRQVHvLRQz#WB=l%a*$}8)>#pf|ZDuh*xlcZbnT>1Q@Hj3twwlq;P
zBwRQO4o(*evCv$|f2>4gOeg|f6ag?#8R<Flqk|<}4BW|cQn@e_!FRR4=drxqHFHbu
z`rf6%0itok#PV9;oR;m0B*<vjuz10|wKan1Hzxn8<g9aEIxVTSdtn*!)%C%Od=CNd
zaoyy;i`uMA<?Sh6H|SQ|4OAV6m(pH5ApF6BaN-W3t&31~B2(YsuN+M^&U8)noOIRa
z@J*5OnIV5@=v}#68TfJ6x(&*Ap8kbjgq_grasvT=H)icm#&$~Q8oRSa5~dAF-uWi&
zI{d3dy^#FueeV#p{WC!1vUUyLI>Kz=VNdF|zq;Jt4b3gD9$D5;qK{ZnA~^=87bK^_
z)!(ZUHLJ89DbhNLqrK5i^Tw&49!b*<Btg120P?IG@V`N!w<xKuj{XYieh@-k8lG1l
zxdzsJM?S+@;?={B)<^Rm^gSujdsnL1_~0Li5G7JKcX=pL(tM+_|4aeLT5!!ue(-_y
z0vM9v8G3wrLarlfIOjwFd<~Ub#IhnPM(vBo-lk*QjX8Z%-uxk#8(#VT7zYEg*Zv_F
zYMc$PTQ6CU1M)o!%?VrYM9@?F9qv(hg-Qf1sA`Mq&AlUt80;PaX<r?ZO1b(jpLETM
zR_9D=Zv9$M+v9xRe}idd83)R{aQ-!c1m+`dxG^_M`;G3Ib%yXTRbs}jEYFjilW}jb
zzX~<A0*oTZ{7Ww_&&9UvvrFT8w9mYIHa?HhmhzQgSk{!vcMdhR%Fqzv`QFyFNNKcZ
z;qdFcOl<`}Kfha$8%!(FvmkYE4E*rtP?83Mq?JP+bdTN2*{|#5+wRj33upG5rRBZa
zM*;jMd9M(_gBH*)NRSapEw%fn1@E!rl5LCLs})0CpZc}KpIF8S?p%HK^7QqU>hgMs
z^`;fzUb*2oHl^V!wk=-2eb6wNfVt*BHQQ@`m+q3(;qbT;lJQtUE8@4I_kwTT!fr&X
zIG{j#gU!}ps3O-Pj8A0u`0or=0MV2D8$g<k)S&Orxaq1Pd4e}^f)VynaVAgE9Va%Y
zM@z~b->FAzq{KAWl(V13p;CRkx7MnOqP#lmEMABTX7LCvKLae3%3guM6Cz7u5*D*R
zyTDO8JQ$ZRBVfQ6B(|n#^e#)QQguyPhLI{3tAU6%2uDea7}XC}a@^H6Q^%Qe-F^%N
zzoONRlqdbK8ltH7O6`@FbG}ZCB~cGqGV=*W_RzK!{lSC?Lxwum*v_6-3f!fOyz85#
zdz9<A@;=8g1m)7RnA|Sb>?}k+Eb(SPYQ7qe>V_1LG|qUWKHq1<gBhcZQ_T}E*b<Cb
zuylG>MQ<|WxcA})6SnAevpgwdaj(h1?*m!5LJMdtGOuhMD+T@5?;u}EKQ+2?q2K+g
z4U{emXK*E6t+;ZyoH%PiU&&sEoRJgwPo3cYnTX*1tXKB=euQ^F<OSJhrk|dLu-0{^
zJlBoE>x6Qn5qCX<5d$19)!wh<uwA>cbp&*Ti<EZRYO8**f;vCmnyC$lM0yL!grKg{
zPA66nX_ypb7}|$_`%fLwzHW}GnmHLnC`LF&n7jRSUcm`p;YvF$%Oi6-+*<@Me_6M?
zI1yTBaN;;u8{ByIKSSuNhRLvP?gsS9)nKqCX&*oe&<zRaI;b<Yh4+Gp3KLC)Ft%g|
zZfk1;gV~EXTmbsI{^}U8;k*F{Cxuj}erF9;fglL~6MNm!BK{=@jD=AAu&y?A)p1}d
ztM-<uU*j3-5CWf601<^cGEIrrJasBs`IAcIgQsxLyy;Pvwl{(nTzbv2q!*&jN~U_F
zG3f8DPgHjUB_n*8jz#^is{AuR_e~q)AqIr@ko8)u2YQ=q^tfW%VTO_4Sp-D1_h?C_
zBMCptUUe+FgkE>oy9Gys4wTloQaqIn>}811Wi6I^OIp@u|8?v>mFT9=_;J}bHVs?r
zy4_PRp5R+gOJu_2>+ICeim2=MOxhI&7>g+xl^Uk`G^Tn8)TR(bMgt51kFJz2zN;-5
zY8Cx9)q38Zuu?VboVTDI(J7VeCwlJGUx^4)0ENsicu}0P?LA*y>6E@+y~x~;q&8`&
z%>!|_X1l4bB@a}eU=*Bx-e6j(YIlxVcq9bFkA194lT&i-_oP67Xb?{2{pdh>wcWW;
z#0XI{y(l^p+;H2E*2VC7^?MhBCF+?i^Lr6`qLyaut^L1k@_rU1-t+TABu|UhJ8Sr!
z|C-oL{{^8gy`n$0T1*QF_)*tnG*|dv!{m<69J<NGIk~DD<h5(p))|$+&ZpFHRjut>
zu&nQQwQq;(AIU7hBbB%M+H*hU1=F!Jw$+H$gX`)%%MlAvJb37RSMmsxkgYXrA%!xy
zL>yv<F^dcTA#|sU>dgAFI@*k=e@u999l8sJYDYHk<g3D+80U`GaBJ~5!uYNy)@QV@
zD{Am=gPT$em97rzRee&9U=X|Fdv=gE<Wh}`(QM)csBW>d-sPxcjN1yb&%e*_%E2O|
z!5AEZx(kjHBW6Ro0?}XZJd}Lt9escwx_)<<<M-{I*^>_o<Pp$cu9_=9dkCg;>eYPG
z2v>d9L3r*@Z@}Y1v{<ygh^u_6L6EotZUdbPUN5Hazq;O7c6etNDUi-`_mGK-&u#$e
zt$$gle3UOP&f7mk6LFBgP0?_sH@krneZ|BPfw$+rve`318r++(Uv><#l7!KK+ilSA
zoJ&OYn4Ct}iU!R%O-Ew&G%Zyi1HLz|jvD<}Ljun2SMYdew{z%|8u3Y#EnZ$R3!wsX
zYxA}WYid!9yCU<5ztDRa-HW%otjE{ao(Bv4kqQt&d2>O_6l3Sp0biR2>Ne7D5YMSg
zmt|tNVA3r*dx6n+MV}6H-?XtD{ntra`0cJGN7t)w1pjlXtAT3i#jB`uDDKUolHjtS
zy2sbrHlu?>Tc44m{LQgw^h$dcXH2Rx9!r6D*?RwPw6rny4fajtoy}MGl%IUl<)@q-
zaj~l|=P-#F)!KNhJsTDKPhA804THQIIW@Sg)}ijdgdq4))4kJkk#Z{T+PEf?Gn4F}
zN$aoj<0&bdAqy{gLO^}0wR1+xr+Z;&^x(c~uec=9qP)w4>iz^)E3qk;nkBap0|l=|
ze;4U$R@0-Aje@a>Xg&pr7a)SR((cl3?j|H5gVMw?An^5*vT5Jwb916_3+9j13I7C9
z8MaGP9kp>H>VBSwbHgDCzG4K9HyU?;w1%*-o-MVC1&M=7S<3gmW1a?>U&-$-8G3uJ
z&1Hw=D`d*(PXqJJ3!p&8B!qp#kG~U01Hn>j%l<Eis~rsjSYVcb&l3`I#4_$<jh_F^
zxFI>}QzQ~q$&Qen{@9B_B$|Q%-7J03V+x-zEH#?zw>ZA~kp6U5-AgYj_>c?;j}GRr
zTK0ova<RZ<*dN>lL=dg^FilZ=j-A-DtPWym=TopLL{R99`RSu_oX8t>&3|onC5!U;
zQ$K4AeE)L;IR4`EPZIhtlLHjEsNG%=Z2+Nh;a=2kvyeQSkC|w5SQO6J^wl_GK&5}m
z0^#TGTct?jF2H32cl+sLuU1Tb^V9c~Ur@+H?68RrX7uxATDZ9I)@T(}SHx^82uTHG
z-KXKO{*S$0);r{YP~xYL^6@vacgt3w1PScoZ2O;>4>U9WWWR2}53*KY_Q!->UvSE%
z-SHEkrW5ztSS*gA>CF^$FZ#fYqu7x1xj}vH72~b8F8NEOPktOkLN_9kkI-dJOY3=}
z+?cUa03sbVsl+%2q#WidZGD&^sw8&|<5SS<u!o}PyG#i^SA14{xOeb$tyP<ngT!vZ
z*JFpcerZZwU!e}6Bjmd16Yu5CluD0j<Hqb%CCLPDI7$UX8dV~0;nCrk&Q=3rXe;go
z5y|Y|K=nV(G?#A$!g~d!22bu#Gzj_HooF{YMo&GgeF@Kyc%7>Ie*ZM-$Ywmph82!M
z`<q-gaIn&fd{639AvAQa-Ebcxz4Kk<-E@>!V@uU%XW9i+2oFnz=O|v4-|5lPL;_^H
zbvm-16{_McG&cN>R()Hs{=s3aCpUR^{~lrbLcv0T=KBe5&PqkcuZGdR>m)g0Pb~hG
zhFdZAYWs?9QjK$#sR51+HK*&#+_M&)2|Okh_!$zJpuk4Iz;nD~$Y=5=Qbi|#)8n%@
z2fwUo$dre55`T40!ISuG8*)$Yx40_ji4;tid7BvbCXNaf+r1q#DL&0UvmY+i>eZ$R
zI44*o0+sfnt+meL8jGWKKi&18zR-hrbRO!d(x?zG)DQS%A9qCaA?6Q04RWfkRD}{y
z-oAg&$*|-l=vJ$r)Aj7tpOgjT2!FA&CF=<BgZ&?A<d<E}<%704!>XFTOcf(HUd;Gc
zzr2xseeV76O7Y^W=kTSmwF;D&oD`%rO};$LioWtZY+b>9)oagxr_Ho-F>sn)idSi=
zjwBstC=<%X=M$Bc2=OG_eV2yG(pn>BGl=GS-4vUeI1Wsg`3!EUh#yH~=SSv+Q8Gd+
zL&=)1s$({Q#W6*nbd}EyAY}lSjeMo)>!n%!YjP-HjAr;H7DTl5q^5MW=l%%zBk10s
zzOvm@Qqd)sj-@wGw;t78?_G7C^Ffgg>*GUOndGIqlw)D`FDy<4v1q3Q4-gUTk-PFn
zE`g5B^~PB#uGeDq>|TKl5G<TF;p@0B){@|AbCBJiAP<dPm->C4yR|Y?dD(fyH-SNA
z{d%bx^ApdVXG4FKYwir+qS(C>M8qIzdyw0onIYZVI0~Yx@>*a1m6U_3*q`V@h^HM|
z(+z-oF-bPXDpw|1I4+ES)%rg>@7@rhDw4GJ={sV>35E^U5YEB|kXbmzbQ6Efh5xG)
zCr{JNz;HrgJbs4Er)T@y;`YeV^&%Qi$?d~B>^^}0XiQqqP{Mef;qbYFXPodM!6Oh}
zTsL=;jxgVqOP79PxuD%GLp@)M-ME&<@o(i%?aW8RKhqnG%6vWsNW@fJ5*Gz;5j(Jq
zOO%P>1b=77+<?kChEFn7#~~RwzJQzcwMX>wOLeV&oVa8h%WsEI-!?p|-S8OO?u>l4
zWji@s#a%Qv{n3YU3(~6~!Mf{<-v_QG4d`UlIIB(zdJQhBz%TMo^ma>8G}8GeX5f;|
zk8sdkvboi7>mWSWyxsz-N*Kj8+tu?6sOj17wY;CSbJ`3q%I7b__PKkY{@WMRr}dgs
zM~{VVf$PXtmB=I(k-)Mj5QXW%a(|Kn_by(sOioTps=Iz5PLtY#@hu2%QKT1<I>Yo0
zV|kT$x-Lq;rxQvdeMfzmq|nFcxMquBvA)wMA*YemG2wwxgxl*sHmHP;h72w?q4S-^
zOy*+$T<-Mc8<o0ukJDVAvO=W@eeVE{S1$VrNf_X{{|!_?2}mHSh}%r3iI>g6aJ;I_
z8MVu{@ciEg)EN<uH9vsDTC-ebSXe8tLUUZzMx4N!0?StToXK<p0YYDFYQGVCdZTfl
zw%0@=0CHk=4uTeQnydXw#m_i@ar}9U=#6vUymkv|?r@QIvp#8{@cww0-7|8h?e*#5
zdTwx3O)q|K&X)RlWnOG{tuIG5jf}^iWj}FQsM`)N^|K_c53hC;U=j74(2&93=7fWw
zP@?i>1&FW#b97n0jsCUK8VJX~uO7H!KwidTElII+(z(DFi2-*hke{(0NUuUY?oI1?
zTCvZ%j<1yU+OT;W9#pM5!*>p5*ZvGbk{E?W>>Ys~@e~i(Hoo_ht>UWIx9OeVd97-a
zArkW5Uk>PQEk<-Pe;2<iin+eH+CTp+P1dh^!?f@B^E^VX-SAfp2oN7d#Up!_QHI%w
zOXhR&BY2P+h<r!*#9?Q`6wavxx}EEmIS~Fz1gL!KXg>K5Kt>KrY9G_hy7z6SPdsmQ
zZ`kymI0fX*sO7o%tbSZW<+diR7`m(c!GCSzaC@Qa_Rh@B0%q=F0UiJWegQ!qei0r4
zu{TczVM6>cAyICAei%Q$-0u*`|B=A~@y^E5>;IlX=vcZQ%<$j;F2T*l!NS$e%)#mZ
sp6Bg6%UduH^-UgEcPp5ijhnp%!1li%p8O@dU^?*fg{oYkjOqLT1w2+bsQ>@~

literal 0
HcmV?d00001

diff --git a/index.html b/index.html
index de4a24ac1..69b82bf09 100644
--- a/index.html
+++ b/index.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en-us">
   <head>
-	<meta name="generator" content="Hugo 0.72.0" />
+	<meta name="generator" content="Hugo 0.129.0">
     <meta charset="utf-8" />
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
@@ -116,7 +116,7 @@
         
         
           
-            <li class="active">
+            <li>
               <a href="/">Home</a>
             </li>
           
@@ -536,7 +536,7 @@ <h2 class="card-pf-title text-center">zOpenShift Service Mesh</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/index.xml b/index.xml
index 9736d09d4..7818ac8fa 100644
--- a/index.xml
+++ b/index.xml
@@ -4,3168 +4,2066 @@
     <title>Red Hat | Public Sector</title>
     <link>/</link>
     <description>Recent content on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title></title>
       <link>/jr-sa/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/jr-sa/</guid>
-      <description>.display-1 { font-size: 32px; font-family: var(--pfe-theme--font-family--heading,RedHatDisplay,Overpass,Arial,sans-serif); } p { font-size: 14px; } li { font-size: 14px; }  Graduating in 2021? Red Hat’s North American Public Sector Team is hiring! JUNIOR SOLUTIONS ARCHITECTS  Do rewarding work in an award-winning company                        What we are looking for:  Students graduating in May 2021 Strong desire to learn new skills and general curiosity for new technologies Excellent communication skills including written, verbal, and presentation skills Must be comfortable presenting to small and large groups of mixed audiences Experience with open source projects   The following are a plus:  US citizenship preferred, as the position may require working with US government customers Red Hat Certified System Administrator (RHCSA), VMware Certified Professional, or ITIL certifications Experience working Red Hat products or its upstream open source projects such as Linux, Ansible, and Kubernetes     Available work locations Raleigh, NC Washington, DC Relocation may be required.</description>
+      <description>Graduating in 2021? Red Hat’s North American Public Sector Team is hiring! JUNIOR SOLUTIONS ARCHITECTS Do rewarding work in an award-winning company What we are looking for: Students graduating in May 2021 Strong desire to learn new skills and general curiosity for new technologies Excellent communication skills including written, verbal, and presentation skills Must be comfortable presenting to small and large groups of mixed audiences Experience with open source projects The following are a plus: US citizenship preferred, as the position may require working with US government customers Red Hat Certified System Administrator (RHCSA), VMware Certified Professional, or ITIL certifications Experience working Red Hat products or its upstream open source projects such as Linux, Ansible, and Kubernetes Available work locations Raleigh, NC Washington, DC Relocation may be required.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/readme/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/readme/</guid>
-      <description>Introduction Red Hat Certificate System is an enterprise software system that gives you a scalable, secure framework to establish and maintain trusted identities and keep communications private.
-Red Hat Certificate System provides certificate life-cycle management-issue, renew, suspend, revoke, archive and recover, and manage single and dual-key X.509v3 certificates needed to handle strong authentication, single sign-on, and secure communications.
-The upstream release is called Dogtag.
-Curriculum overview  Unit 1: Installing Directory Server Unit 2: Installing a Certificate Authority Unit 3: Installing other subsytems Unit 4: Accessing the Web Interface Unit 5: CLI tools Unit 6: Issuing a certificate Unit 7: Recovering a certificate Unit 8: Revoking a certificate Unit 9: OCSP Responder Unit 10: Token Management System Unit 11: Certificate profiles Unit 12: Troubleshooting  Preparation Everything is installed on one (1) VM or physical machine but some preparation is needed prior to starting this workshop.</description>
+      <description>Introduction Red Hat Certificate System is an enterprise software system that gives you a scalable, secure framework to establish and maintain trusted identities and keep communications private.&#xA;Red Hat Certificate System provides certificate life-cycle management-issue, renew, suspend, revoke, archive and recover, and manage single and dual-key X.509v3 certificates needed to handle strong authentication, single sign-on, and secure communications.&#xA;The upstream release is called Dogtag.&#xA;Curriculum overview Unit 1: Installing Directory Server Unit 2: Installing a Certificate Authority Unit 3: Installing other subsytems Unit 4: Accessing the Web Interface Unit 5: CLI tools Unit 6: Issuing a certificate Unit 7: Recovering a certificate Unit 8: Revoking a certificate Unit 9: OCSP Responder Unit 10: Token Management System Unit 11: Certificate profiles Unit 12: Troubleshooting Preparation Everything is installed on one (1) VM or physical machine but some preparation is needed prior to starting this workshop.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_1/</guid>
-      <description>Unit 1: Installing Directory Server In this unit you will install Red Hat Directory Server. Red Hat Directory Server provides a centralized directory service for an intranet, network, and extranet information. Directory Server integrates with existing systems and acts as a centralized repository for the consolidation of employee, customer, supplier, and partner information. Directory Server can even be extended to manage user profiles, preferences, and authentication.
-Red Hat Directory Server is used as the backend for Red Hat Certificate System.</description>
+      <description>Unit 1: Installing Directory Server In this unit you will install Red Hat Directory Server. Red Hat Directory Server provides a centralized directory service for an intranet, network, and extranet information. Directory Server integrates with existing systems and acts as a centralized repository for the consolidation of employee, customer, supplier, and partner information. Directory Server can even be extended to manage user profiles, preferences, and authentication.&#xA;Red Hat Directory Server is used as the backend for Red Hat Certificate System.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_10/</guid>
-      <description>Unit 10: Token Management System In this unit you will login to the TPS web interface, add a new user, and generate a virtual token.
-TPS Web Interface The admin certificate needs to be in your browser. This was completed during Unit 4.
-  Open the TPS webpage.
-https://ca1.redhat.example.com:8443/tps/
-  Click the Log In button.
-  Go through the different tabs to become familiar with the interface. It will be mostly blank until we create users and tokens.</description>
+      <description>Unit 10: Token Management System In this unit you will login to the TPS web interface, add a new user, and generate a virtual token.&#xA;TPS Web Interface The admin certificate needs to be in your browser. This was completed during Unit 4.&#xA;Open the TPS webpage.&#xA;https://ca1.redhat.example.com:8443/tps/&#xA;Click the Log In button.&#xA;Go through the different tabs to become familiar with the interface. It will be mostly blank until we create users and tokens.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_11/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_11/</guid>
-      <description>Unit 11: Certificate profiles In this unit you will go over the caUserCert profile. This certificate profile is for enrolling user certificates.
-The CA (certificate authority) profiles are located here:
-/var/lib/pki/ca1/ca/profiles/ca  The caUserCert.cfg profile is located in the rhcs labs folder.
-Example caUserCert Profile The fields you will see in a CA User Profile are as follows:
-desc is a long description of the user certificate profile visible (true/false) controls whether the certificate will be visible to users enable, when selected (true), will allow the certificate to be used enableBy identifies the user who enabled the certificate name is the short name used for the certificate that will be viewable by users</description>
+      <description>Unit 11: Certificate profiles In this unit you will go over the caUserCert profile. This certificate profile is for enrolling user certificates.&#xA;The CA (certificate authority) profiles are located here:&#xA;/var/lib/pki/ca1/ca/profiles/ca The caUserCert.cfg profile is located in the rhcs labs folder.&#xA;Example caUserCert Profile The fields you will see in a CA User Profile are as follows:&#xA;desc is a long description of the user certificate profile visible (true/false) controls whether the certificate will be visible to users enable, when selected (true), will allow the certificate to be used enableBy identifies the user who enabled the certificate name is the short name used for the certificate that will be viewable by users</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_12/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_12/</guid>
-      <description>Unit 12: Troubleshooting In this unit you will troubleshoot common issues with maintaining a Certificate System. Each section has a shell script to run that will &amp;ldquo;break&amp;rdquo; the system. A hint will be offered to help you hone your troubleshooting skills.
-Instructions To solve, the CA should be accessible in a browser without errors in status output or logs.
-Run script to break CA (1st lab)   Change to labs troubleshooting directory.</description>
+      <description>Unit 12: Troubleshooting In this unit you will troubleshoot common issues with maintaining a Certificate System. Each section has a shell script to run that will &amp;ldquo;break&amp;rdquo; the system. A hint will be offered to help you hone your troubleshooting skills.&#xA;Instructions To solve, the CA should be accessible in a browser without errors in status output or logs.&#xA;Run script to break CA (1st lab) Change to labs troubleshooting directory.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_2/</guid>
-      <description>Unit 2: Installing a Certificate Authority In this unit you will install a Certificate Authority (CA), or Certificate Manager. The CA is the core of the PKI; it issues and revokes all certificates. The Certificate Manager is also the core of the Certificate System. By establishing a security domain of trusted subsystems, it establishes and manages relationships between the other subsystems.
-The pkispawn setup script can be used interactively but we are going to use an automated install with pre-configured settings.</description>
+      <description>Unit 2: Installing a Certificate Authority In this unit you will install a Certificate Authority (CA), or Certificate Manager. The CA is the core of the PKI; it issues and revokes all certificates. The Certificate Manager is also the core of the Certificate System. By establishing a security domain of trusted subsystems, it establishes and manages relationships between the other subsystems.&#xA;The pkispawn setup script can be used interactively but we are going to use an automated install with pre-configured settings.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_3/</guid>
-      <description>Unit 3: Installing other subsytems In this unit you will install the other subsystems associated with Certificate System. Key Recovery Authority (KRA), Online Certificate Status Protocol (OCSP), Token Key Service (TKS), and Token Processing System (TPS).
-KRA A Key Recovery Authority (KRA). Certificates are created based on a specific and unique key pair. If a private key is ever lost, then the data which that key was used to access (such as encrypted emails) is also lost because it is inaccessible.</description>
+      <description>Unit 3: Installing other subsytems In this unit you will install the other subsystems associated with Certificate System. Key Recovery Authority (KRA), Online Certificate Status Protocol (OCSP), Token Key Service (TKS), and Token Processing System (TPS).&#xA;KRA A Key Recovery Authority (KRA). Certificates are created based on a specific and unique key pair. If a private key is ever lost, then the data which that key was used to access (such as encrypted emails) is also lost because it is inaccessible.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_4/</guid>
-      <description>Unit 4: Accessing the Web Interface In this unit you will access the web interface of each subsystem. Each Certificate System instance is a Tomcat server instance and each Certificate System subsystem (such as CA or KRA) is deployed as a web application in Tomcat.
-All subsystems share a common administrative interface and have an agent interface that allows for agents to perform the tasks assigned to them. A CA Subsystem has an end-entity interface that allows end-entities to enroll in the PKI.</description>
+      <description>Unit 4: Accessing the Web Interface In this unit you will access the web interface of each subsystem. Each Certificate System instance is a Tomcat server instance and each Certificate System subsystem (such as CA or KRA) is deployed as a web application in Tomcat.&#xA;All subsystems share a common administrative interface and have an agent interface that allows for agents to perform the tasks assigned to them. A CA Subsystem has an end-entity interface that allows end-entities to enroll in the PKI.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_5/</guid>
-      <description>Unit 5: CLI tools In this unit you will access the Certificate System using various command-line interface (CLI) tools. Red Hat Certificate System provides a client command-line interface to access various services on the server.
-Prerequisites Your environment needs to be configured to use the ca_admin certificate to interact with the subsystems via the CLI. The root user does not have be to used but access to /root/.dogtag is required to use the ca_admin certificate.</description>
+      <description>Unit 5: CLI tools In this unit you will access the Certificate System using various command-line interface (CLI) tools. Red Hat Certificate System provides a client command-line interface to access various services on the server.&#xA;Prerequisites Your environment needs to be configured to use the ca_admin certificate to interact with the subsystems via the CLI. The root user does not have be to used but access to /root/.dogtag is required to use the ca_admin certificate.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_6/</guid>
-      <description>Unit 6: Issuing a certificate In this unit we will generate different certificates using the web interface and CLI.
-The purpose of certificates is to establish trust. Their usage varies depending on the kind of trust they are used to ensure. Some kinds of certificates are used to verify the identity of the presenter; others are used to verify that an object or item has not been tampered with.
-Certificate Request Message Format (CLI)   Ensure the labs were completed in Unit 5.</description>
+      <description>Unit 6: Issuing a certificate In this unit we will generate different certificates using the web interface and CLI.&#xA;The purpose of certificates is to establish trust. Their usage varies depending on the kind of trust they are used to ensure. Some kinds of certificates are used to verify the identity of the presenter; others are used to verify that an object or item has not been tampered with.&#xA;Certificate Request Message Format (CLI) Ensure the labs were completed in Unit 5.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_7/</guid>
-      <description>Unit 7. Recovering a certificate In this unit we will simulate recovering a user&amp;rsquo;s private key.
-Recover Private Key The URL is different in the images. I&amp;rsquo;m lazy.
-  In new tab, open KRA webpage.
-https://ca1.redhat.example.com:8443/kra/agent/kra
-  Select PKI Administrator certificate (if prompted).
-  Add Exception for insecure connection (if prompted).
-  Click Search for Keys.
-![Alt text](images/keyrecover_lab_1.png)    Check Key Identifiers box and click Show Key (scroll down).</description>
+      <description>Unit 7. Recovering a certificate In this unit we will simulate recovering a user&amp;rsquo;s private key.&#xA;Recover Private Key The URL is different in the images. I&amp;rsquo;m lazy.&#xA;In new tab, open KRA webpage.&#xA;https://ca1.redhat.example.com:8443/kra/agent/kra&#xA;Select PKI Administrator certificate (if prompted).&#xA;Add Exception for insecure connection (if prompted).&#xA;Click Search for Keys.&#xA;![Alt text](images/keyrecover_lab_1.png) Check Key Identifiers box and click Show Key (scroll down).&#xA;![Alt text](images/keyrecover_lab_2.png) Click Details button.&#xA;![Alt text](images/keyrecover_lab_3.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_8/</guid>
-      <description>Unit 8: Revoking a certificate In this unit we will revoke a certificate generated during the last unit using the web interface and CLI.
-Revoke Certificate (web-based) The URL is different in the images. I&amp;rsquo;m lazy.
-  Open CA webpage.
-https://ca1.redhat.example.com:8443/ca/agent/ca
-  Select PKI Administrator certificate (if prompted).
-  Add Exception for insecure connection (if prompted).
-  Click List Certificates.
-![Alt text](images/revoke_lab_1.png)    Click Find button.</description>
+      <description>Unit 8: Revoking a certificate In this unit we will revoke a certificate generated during the last unit using the web interface and CLI.&#xA;Revoke Certificate (web-based) The URL is different in the images. I&amp;rsquo;m lazy.&#xA;Open CA webpage.&#xA;https://ca1.redhat.example.com:8443/ca/agent/ca&#xA;Select PKI Administrator certificate (if prompted).&#xA;Add Exception for insecure connection (if prompted).&#xA;Click List Certificates.&#xA;![Alt text](images/revoke_lab_1.png) Click Find button.&#xA;![Alt text](images/revoke_lab_2.png) Copy Serial Number of UID= cert.&#xA;![Alt text](images/revoke_lab_3.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/pki_workshop/unit_lessons/unit_9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/pki_workshop/unit_lessons/unit_9/</guid>
-      <description>Unit 9: OCSP Responder In this unit you will interact with the OCSP Responder using the web interface and CLI tool OCSPClient. You will also issue a CRL to verify the revoked certificate is listed there.
-Check Certificate Revocation List (Web-based) The URL is different in the images. I&amp;rsquo;m lazy.
-  Open CA webpage.
-https://ca1.redhat.example.com:8443/ca/agent/ca/
-  Select PKI Administrator certificate (if prompted).
-  Add Exception for insecure connection (if prompted).</description>
+      <description>Unit 9: OCSP Responder In this unit you will interact with the OCSP Responder using the web interface and CLI tool OCSPClient. You will also issue a CRL to verify the revoked certificate is listed there.&#xA;Check Certificate Revocation List (Web-based) The URL is different in the images. I&amp;rsquo;m lazy.&#xA;Open CA webpage.&#xA;https://ca1.redhat.example.com:8443/ca/agent/ca/&#xA;Select PKI Administrator certificate (if prompted).&#xA;Add Exception for insecure connection (if prompted).&#xA;Click Update Revocation List.</description>
     </item>
-    
     <item>
       <title></title>
       <link>/workshops/secure_software_factory/readme/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/readme/</guid>
-      <description>Must have existing OpenShift Environment You can use either of the OpenShift provsioners from RedHatGov
- https://github.com/RedHatGov/redhatgov.workshops/tree/master/openshift-aws-setup https://github.com/RedHatGov/redhatgov.workshops/tree/master/openshift_terraform https://github.com/gnunn1/openshift-aws-setup https://github.com/jaredhocutt/openshift-provision https://github.com/bit4man/ansible_agnostic_deployer  Environment Setup If you&amp;rsquo;d like to setup an individual environment, use the commands below to set it up or delete the single environment.
-Help $ scripts/provision.sh &amp;ndash;help
-Individual Environment $ scripts/provision.sh deploy &amp;ndash;deploy-che &amp;ndash;ephemeral
-Individual Delete $ scripts/provision.sh delete
-Batch Setup If you&amp;rsquo;d like to setup the workshop for numerous users, go into the provision-batch-setup.</description>
+      <description>Must have existing OpenShift Environment You can use either of the OpenShift provsioners from RedHatGov&#xA;https://github.com/RedHatGov/redhatgov.workshops/tree/master/openshift-aws-setup https://github.com/RedHatGov/redhatgov.workshops/tree/master/openshift_terraform https://github.com/gnunn1/openshift-aws-setup https://github.com/jaredhocutt/openshift-provision https://github.com/bit4man/ansible_agnostic_deployer Environment Setup If you&amp;rsquo;d like to setup an individual environment, use the commands below to set it up or delete the single environment.&#xA;Help $ scripts/provision.sh &amp;ndash;help&#xA;Individual Environment $ scripts/provision.sh deploy &amp;ndash;deploy-che &amp;ndash;ephemeral&#xA;Individual Delete $ scripts/provision.sh delete&#xA;Batch Setup If you&amp;rsquo;d like to setup the workshop for numerous users, go into the provision-batch-setup.</description>
     </item>
-    
     <item>
       <title>About</title>
       <link>/about/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/about/</guid>
       <description>Open source is not only behind many of the technology industry&amp;rsquo;s most significant innovations, but it is also pervasive across the U.S. government. For more than a decade, Red Hat has been working closely with federal government customers to help them embrace open source technologies.</description>
     </item>
-    
     <item>
       <title>CloudForms Workshop Prerequisites</title>
       <link>/workshops/cloudforms41/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/prerequisites/</guid>
-      <description>If we have provided a laptop or cloud environment to you for this workshop, the following steps are already set up for you. Please jump to Exercise 1.0
- Install git We will use a few git commands directly in some of the advanced labs, please make sure git is installed on your system. You can download the latest version here.
-Create GitHub account Create a FREE GitHub account by going to this link and following their step-by-step instructions.</description>
+      <description>If we have provided a laptop or cloud environment to you for this workshop, the following steps are already set up for you. Please jump to Exercise 1.0&#xA;Install git We will use a few git commands directly in some of the advanced labs, please make sure git is installed on your system. You can download the latest version here.&#xA;Create GitHub account Create a FREE GitHub account by going to this link and following their step-by-step instructions.</description>
     </item>
-    
     <item>
       <title>Conclusion</title>
       <link>/workshops/source_to_image/conclusion/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/conclusion/</guid>
-      <description>Congratulations You have gone through a methodical process to develop container technology that is custom to a framework, yet repeatable. We have:
-  Run the application from the command line to understand what it does and how it is supposed to behave.
-  Containerized the applicaiton.
-  Built Source-to-Image mechanisms that allow us to inject raw source code to be built inside the container.
-  Created an OpenShift template to make repeated deployments easier.</description>
+      <description>Congratulations You have gone through a methodical process to develop container technology that is custom to a framework, yet repeatable. We have:&#xA;Run the application from the command line to understand what it does and how it is supposed to behave.&#xA;Containerized the applicaiton.&#xA;Built Source-to-Image mechanisms that allow us to inject raw source code to be built inside the container.&#xA;Created an OpenShift template to make repeated deployments easier.</description>
     </item>
-    
     <item>
       <title>Conclusion - Closing thoughts &amp; homework</title>
       <link>/workshops/security_container_intro/lab99-conclusion/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab99-conclusion/</guid>
       <description>As a final homework assignment, we encourage you to watch a video entitled the State of Container Security that Sally and Urvashi presented at an OpenShift Commons briefing on March 27, 2020. Their talk goes into additional detail on many of the concepts covered in this lab along with a sneak peak at future work by the upstream community. They also show some great demos that you will want to see.</description>
     </item>
-    
     <item>
       <title>Contact</title>
       <link>/contact/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/contact/</guid>
-      <description>We are here to help you Are you curious about something? Do you have some kind of problem with our products?
-Please feel free to contact us, our customer service center is working for you 24 hours a day, 7 days a week.
-https://www.redhat.com/en/services/support
-If you find any issues with the content on this site, please file an issue on our GitHub project at https://github.com/RedHatGov/redhatgov.github.io/</description>
+      <description>We are here to help you Are you curious about something? Do you have some kind of problem with our products?&#xA;Please feel free to contact us, our customer service center is working for you 24 hours a day, 7 days a week.&#xA;https://www.redhat.com/en/services/support&#xA;If you find any issues with the content on this site, please file an issue on our GitHub project at https://github.com/RedHatGov/redhatgov.github.io/</description>
     </item>
-    
     <item>
       <title>Deploy Your Own Terminal</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/</guid>
-      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.
-Let&amp;rsquo;s Login to the Web Console  Use your browser to navigate to the below URI, and login with the username userYOUR#  and the password provided by your instructor:
- https://console-openshift-console.apps.example.redhatgov.io  Login Webpage
-Once logged in you should see your available projects - or a button to create a project if none exist already:</description>
+      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.&#xA;Let&amp;rsquo;s Login to the Web Console Use your browser to navigate to the below URI, and login with the username userYOUR# and the password provided by your instructor:&#xA;https://console-openshift-console.apps.example.redhatgov.io Login Webpage&#xA;Once logged in you should see your available projects - or a button to create a project if none exist already:</description>
     </item>
-    
     <item>
       <title>Exercise 1 - Install JDV and JBDS</title>
       <link>/workshops/jdv_dev/exercise1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise1/</guid>
-      <description>Table of Contents  Download JDV Download JBDS Install JDV  Run JDV   Install JBDS  Run JBDS Install teiid designer Configure server settings    Download JBoss Data Virtualization   jboss-dv-6.3.0-1-installer.jar  Download JBoss Developer Studio   devstudio-11.0.0.GA-installer-standalone.jar  Install JBoss Data Virtualization (JDV)   In the location where you downloaded the installer, run the following command  java -jar jboss-dv-6.3.0-1-installer.jar  Follow the default prompts with the following exceptions below</description>
+      <description>Table of Contents Download JDV Download JBDS Install JDV Run JDV Install JBDS Run JBDS Install teiid designer Configure server settings Download JBoss Data Virtualization jboss-dv-6.3.0-1-installer.jar Download JBoss Developer Studio devstudio-11.0.0.GA-installer-standalone.jar Install JBoss Data Virtualization (JDV) In the location where you downloaded the installer, run the following command java -jar jboss-dv-6.3.0-1-installer.jar Follow the default prompts with the following exceptions below Take note of the directory you use to install JDV, it will be helpful when installing JBoss Developer studio.</description>
     </item>
-    
     <item>
       <title>Exercise 1 - The Mount Namespace</title>
       <link>/workshops/containers_the_hard_way/exercise1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise1/</guid>
-      <description>Exercise 1.1: Unsharing is Caring New Linux Namespaces are typically spawned by using either the clone or unshare system calls. These exist as C functions but wrappers exist in many other languages. For our purposes today, we will be using the unshare command which is ostensibly a Bash wrapper to the unshare system call.
- unshare --help   Usage: unshare [options] [&amp;lt;program&amp;gt; [&amp;lt;argument&amp;gt;...]] Run a program with some namespaces unshared from the parent.</description>
+      <description>Exercise 1.1: Unsharing is Caring New Linux Namespaces are typically spawned by using either the clone or unshare system calls. These exist as C functions but wrappers exist in many other languages. For our purposes today, we will be using the unshare command which is ostensibly a Bash wrapper to the unshare system call.&#xA;unshare --help Usage: unshare [options] [&amp;lt;program&amp;gt; [&amp;lt;argument&amp;gt;...]] Run a program with some namespaces unshared from the parent.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - A Guided Tour of CloudForms</title>
       <link>/workshops/cloudforms41/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.0/</guid>
-      <description>Exercise 1.0: How to Access CloudForms Exercise Description This exercise provides a quick tour of the console to help you get familiar with the user interface, along with some key terminology we will use in subsequent workshop content. If you are already familiar with the basics of CloudForms you can skip this exercise — after making sure you can login.
-Key Terms Before sinking our teeth into Cloud Forms, it is important to understand some terminology.</description>
+      <description>Exercise 1.0: How to Access CloudForms Exercise Description This exercise provides a quick tour of the console to help you get familiar with the user interface, along with some key terminology we will use in subsequent workshop content. If you are already familiar with the basics of CloudForms you can skip this exercise — after making sure you can login.&#xA;Key Terms Before sinking our teeth into Cloud Forms, it is important to understand some terminology.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Configuring Ansible Tower</title>
       <link>/workshops/ansible_tower_intro/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/exercise1.0/</guid>
-      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.
- There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.
-   Credentials
-  Projects
-  Inventory
-  Job Template
-     Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password provided by your instructor.</description>
+      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.&#xA;There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.&#xA;Credentials&#xA;Projects&#xA;Inventory&#xA;Job Template&#xA;Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password provided by your instructor.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Deploy OpenShift</title>
       <link>/workshops/security_openshift/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.0/</guid>
-      <description>OpenShift v3 is a layered system designed to expose underlying Docker-formatted container image and Kubernetes concepts as accurately as possible, with a focus on easy composition of applications by a developer. For example, install Ruby, push code, and add MySQL.
-   OpenShift Step 1: Use the oc command
- These instances have been preconfigured with docker and the oc command. The oc command makes deploying OpenShift for development purposes incredibly easy.</description>
+      <description>OpenShift v3 is a layered system designed to expose underlying Docker-formatted container image and Kubernetes concepts as accurately as possible, with a focus on easy composition of applications by a developer. For example, install Ruby, push code, and add MySQL.&#xA;OpenShift Step 1: Use the oc command&#xA;These instances have been preconfigured with docker and the oc command. The oc command makes deploying OpenShift for development purposes incredibly easy. The oc cluster up command starts a OpenShift all-in-one cluster with a configured registry, router, image streams, and default templates.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Install buildah, skopeo, and podman</title>
       <link>/workshops/containers_101/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.0/</guid>
-      <description>Exercise 1.0: Installing Buildah, Skopeo and Podman Set up dependencies Elevate privileges
- In order to do any of the steps in the Containers 101 Workshop, you will need root privileges. There are two methods of doing this; the method you choose is up to you. Either method will work, but in a production environment, Method 2 is much more secure and auditable.
- Method 1: The first, and easiest, method is to start a root session, with sudo -i:</description>
+      <description>Exercise 1.0: Installing Buildah, Skopeo and Podman Set up dependencies Elevate privileges&#xA;In order to do any of the steps in the Containers 101 Workshop, you will need root privileges. There are two methods of doing this; the method you choose is up to you. Either method will work, but in a production environment, Method 2 is much more secure and auditable.&#xA;Method 1: The first, and easiest, method is to start a root session, with sudo -i:</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Intro to Cockpit</title>
       <link>/workshops/security_containers/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.0/</guid>
-      <description>Exercise 1.0 - Intro to Cockpit   Exercise Description In this workshop, you will learn to navigate Cockpit and examine its features and capabilities.
- What is Cockpit? A remote manager for GNU/Linux servers
- Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser.
- Cockpit makes it easy for any sysadmin to perform simple tasks, such as administering storage, inspecting journals and starting and stopping services.</description>
+      <description>Exercise 1.0 - Intro to Cockpit Exercise Description In this workshop, you will learn to navigate Cockpit and examine its features and capabilities.&#xA;What is Cockpit? A remote manager for GNU/Linux servers&#xA;Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser.&#xA;Cockpit makes it easy for any sysadmin to perform simple tasks, such as administering storage, inspecting journals and starting and stopping services.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Introduction to Security Enhanced Linux (SELinux)</title>
       <link>/workshops/selinux_policy/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise1.0/</guid>
-      <description>History In this exercise, we are going to introduce you to Security Enhanced Linux, commonly known as SELinux.
- SELinux is an implementation of the Flask system security architecture. The Flask architecture implements MAC, which focuses on providing an administratively-defined security policy that can control all subjects and objects, basing decisions on all security-relevant information. In addition, Flask focuses on the concept of least privilege, which gives a process exactly the rights it needs to perform its given task.</description>
+      <description>History In this workshop, we are going to introduce you to Security Enhanced Linux, commonly known as SELinux.&#xA;Standard Linux access policy based on the user, group, and other permissions, known as Discretionary Access Control (DAC), does not enable system administrators to create comprehensive and fine-grained security policies, such as restricting specific applications to only viewing log files, while allowing other applications to append new data to the log files.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Running Ad hoc commands</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/</guid>
       <description>Exercise Description For our first exercise, we are going to run some ad hoc commands to help you get a feel for how Red Hat Ansible Automation works. Ansible ad hoc commands enable you to perform repeatable tasks on local or remote nodes, without having to write a playbook. They are very useful when you simply need to do one or two tasks quickly and often, to many remote nodes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Running Ad hoc commands</title>
       <link>/workshops/ansible_automation/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.0/</guid>
       <description>Exercise Description For our first exercise, we are going to run some ad hoc commands to help you get a feel for how Red Hat Ansible Automation works. Ansible ad hoc commands enable you to perform repeatable tasks on local or remote nodes, without having to write a playbook. They are very useful when you simply need to do one or two tasks quickly and often, to many remote nodes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Running Ad-hoc commands</title>
       <link>/workshops/ansible_tower_azure/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.0/</guid>
       <description>Section 1: Ad hoc commands For our first exercise, we are going to run some ad hoc commands to help you get a feel for how Red Hat Ansible Tower works. Ansible ad hoc commands enable you to perform repeatable tasks on remote nodes, without having to write a playbook. They are very useful when you simply need to do one or two tasks quickly and often, to many remote nodes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - Welcome to RHEL!</title>
       <link>/workshops/rhel_8/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.0/</guid>
-      <description>Exercise Description Welcome to RHEL!
- Red Hat Enterprise Linux 8 is the intelligent enterprise Linux, providing a secure and consistent foundation across hybrid cloud deployments and the tools enterprises need to deliver services and workloads faster with less effort. RHEL 8 enables delivery of any application, on any architecture, on any cloud, physical, or virtual environment, at any time.
- With predictable release cadence and 10-year enterprise support, RHEL 8 is the safe and stable choice for your enterprise.</description>
+      <description>Exercise Description Welcome to RHEL!&#xA;Red Hat Enterprise Linux 8 is the intelligent enterprise Linux, providing a secure and consistent foundation across hybrid cloud deployments and the tools enterprises need to deliver services and workloads faster with less effort. RHEL 8 enables delivery of any application, on any architecture, on any cloud, physical, or virtual environment, at any time.&#xA;With predictable release cadence and 10-year enterprise support, RHEL 8 is the safe and stable choice for your enterprise.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Creating and Running a Job Template</title>
       <link>/workshops/ansible_tower_intro/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/exercise1.1/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.
- Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.&#xA;Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Explore Your First Infrastructure Provider</title>
       <link>/workshops/cloudforms41/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.1/</guid>
-      <description>Exercise 1.1: Working with Infrastructure Providers Exercise Description Learn to view, search and manage infrastructure providers, in Red Hat CloudForms.
-In Red Hat CloudForms, an infrastructure provider is a virtual infrastructure environment that you can add to a Red Hat CloudForms appliance, to manage and interact with the resources, in that environment.
-In other words, a infrastructure provider is a management platform for managing virtual machines from a single type of hypervisor.</description>
+      <description>Exercise 1.1: Working with Infrastructure Providers Exercise Description Learn to view, search and manage infrastructure providers, in Red Hat CloudForms.&#xA;In Red Hat CloudForms, an infrastructure provider is a virtual infrastructure environment that you can add to a Red Hat CloudForms appliance, to manage and interact with the resources, in that environment.&#xA;In other words, a infrastructure provider is a management platform for managing virtual machines from a single type of hypervisor.</description>
     </item>
-    
-    <item>
-      <title>Exercise 1.1 - Introduction to SELinux</title>
-      <link>/workshops/selinux_policy/exercise1.1/</link>
-      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
-      <guid>/workshops/selinux_policy/exercise1.1/</guid>
-      <description>Exercise Description To better understand SELinux basic concepts, see the following documentation:
-   The SELinux Coloring Book
-  SELinux Wiki FAQ
-  The SELinux Notebook
-   Step 1: Become root First, go ahead and switch users to root:
- sudo -i   Step 2: What mode are we in? Next, let&amp;#8217;s check to see what SELinux mode your host is in:
- getenforce  Enforcing    Step 3: Changing modes Now, we can change the mode that your host is in:</description>
-    </item>
-    
     <item>
       <title>Exercise 1.1 - OpenShift Templates</title>
       <link>/workshops/security_openshift/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.1/</guid>
       <description>What are OpenShift Templates A template describes a set of objects that can be parameterized and processed to produce a list of objects for creation by OpenShift Container Platform. A template can be processed to create anything you have permission to create within a project, for example services, build configurations, and deployment configurations. A template may also define a set of labels to apply to every object defined in the template.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Pulling and Running Container Images</title>
       <link>/workshops/containers_101/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.1/</guid>
-      <description>Exercise 1.1 - Pulling Container Images   Section 1: Pull RHEL Images Step 1. Use the following command to pull a RHEL image from the Red Hat repository: podman pull command podman pull registry.access.redhat.com/ubi8   Images are accessed using the container registry URL (registry.access.redhat.com). If the container registry URL is not specified in the pull command, it could result in the retrieval of an image that originates from an untrusted registry.</description>
+      <description>Exercise 1.1 - Pulling Container Images Section 1: Pull RHEL Images Step 1. Use the following command to pull a RHEL image from the Red Hat repository: podman pull command podman pull registry.access.redhat.com/ubi8 Images are accessed using the container registry URL (registry.access.redhat.com). If the container registry URL is not specified in the pull command, it could result in the retrieval of an image that originates from an untrusted registry.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles</title>
       <link>/workshops/security_containers/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.1/</guid>
-      <description>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles   Exercise Description Now that you&amp;#8217;ve gotten a sense of how Cockpit works, we are going to start digging in at the command line on Container security. You can use either the Terminal in Cockpit from your browser, a SSH terminal or Terminal client like PuTTy. The choice is yours.
-   Section 1: Best Practices Step 1.</description>
+      <description>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles Exercise Description Now that you’ve gotten a sense of how Cockpit works, we are going to start digging in at the command line on Container security. You can use either the Terminal in Cockpit from your browser, a SSH terminal or Terminal client like PuTTy. The choice is yours.&#xA;Section 1: Best Practices Step 1. Always specify a tag in FROM instructions. FROM redis is bad, because it pulls the latest tag, which changes over time and can be expected to move with major version changes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Running an Ansible playbook</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/</guid>
-      <description>Objective: Configure Edge node to run a Performance CoPilot agent As part of this exercise, you will be running a pre-existing Ansible playbook pre-loaded into your CodeReady Workspace.
- The playbook is written to showcase a series of basic Ansible concepts.
- Note: The following commands below need to be run from within the Ansible terminal
- Step 1: Checking a playbook playbook for correct syntax However, before you run the playbook, lets take a few moments to understand the options.</description>
+      <description>Objective: Configure Edge node to run a Performance CoPilot agent As part of this exercise, you will be running a pre-existing Ansible playbook pre-loaded into your CodeReady Workspace.&#xA;The playbook is written to showcase a series of basic Ansible concepts.&#xA;Note: The following commands below need to be run from within the Ansible terminal&#xA;Step 1: Checking a playbook playbook for correct syntax However, before you run the playbook, lets take a few moments to understand the options.</description>
     </item>
-    
     <item>
-      <title>Exercise 1.1 - What&#39;s New in RHEL 8</title>
-      <link>/workshops/rhel_8/exercise1.1/</link>
+      <title>Exercise 1.1 - SELinux policy in RHEL</title>
+      <link>/workshops/selinux_policy/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
-      <guid>/workshops/rhel_8/exercise1.1/</guid>
-      <description>Application streams Application streams deliver user space packages on a cadence that makes sense for the package rather than as a monolithic distribution. Streams also allow the consolidation of previous distribution channels to a single place.
-   Red Hat Insights Red Hat Insights is included with your Red Hat® Enterprise Linux® 8 subscription. It helps provide a security-focused, reliable, efficient, and scalable infrastructure environment.
-   Image builder Image builder lets customers build images from source RPMs that are deployable to multiple targets quickly and simply, and provides fine-grained control and visibility in to what’s included in a particular image and its history.</description>
+      <guid>/workshops/selinux_policy/exercise1.1/</guid>
+      <description>What are policies? A policy is a real-world application of SELinux controls. This chapter is an overview and examination of SELinux policy for Red Hat Enterprise Linux.&#xA;What is the Targeted Policy? The SELinux policy is highly configurable. Starting with Red Hat Enterprise Linux 5, Red Hat defaulted to the targeted policy. The goal of this policy is to lock down all processes that listen for network connections and pretty much all processes that start at boot.</description>
     </item>
-    
     <item>
-      <title>Exercise 1.1 - Writing Your First Playbook</title>
-      <link>/workshops/ansible_automation/exercise1.1/</link>
+      <title>Exercise 1.1 - What&#39;s New in RHEL 8</title>
+      <link>/workshops/rhel_8/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
-      <guid>/workshops/ansible_automation/exercise1.1/</guid>
-      <description>Exercise Description Now that you&amp;#8217;ve gotten a sense of how Red Hat Ansible Tower works, we are going to write our first Ansible playbook. The playbook is where you can take some of those ad hoc commands you just ran and put them into a repeatable set of plays and tasks.
- A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
+      <guid>/workshops/rhel_8/exercise1.1/</guid>
+      <description>Application streams Application streams deliver user space packages on a cadence that makes sense for the package rather than as a monolithic distribution. Streams also allow the consolidation of previous distribution channels to a single place.&#xA;Red Hat Insights Red Hat Insights is included with your Red Hat® Enterprise Linux® 8 subscription. It helps provide a security-focused, reliable, efficient, and scalable infrastructure environment.&#xA;Image builder Image builder lets customers build images from source RPMs that are deployable to multiple targets quickly and simply, and provides fine-grained control and visibility in to what’s included in a particular image and its history.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Writing Your First playbook</title>
       <link>/workshops/ansible_tower_azure/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.1/</guid>
-      <description>Now that you&amp;#8217;ve gotten a sense of how ansible works, we are going to write our first ansible playbook. The playbook is where you can take some of those ad-hoc commands you just ran and put them into a repeatable set of plays and tasks.
- A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
+      <description>Now that you’ve gotten a sense of how ansible works, we are going to write our first ansible playbook. The playbook is where you can take some of those ad-hoc commands you just ran and put them into a repeatable set of plays and tasks.&#xA;A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
+    </item>
+    <item>
+      <title>Exercise 1.1 - Writing Your First Playbook</title>
+      <link>/workshops/ansible_automation/exercise1.1/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/ansible_automation/exercise1.1/</guid>
+      <description>Exercise Description Now that you’ve gotten a sense of how Red Hat Ansible Tower works, we are going to write our first Ansible playbook. The playbook is where you can take some of those ad hoc commands you just ran and put them into a repeatable set of plays and tasks.&#xA;A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
     </item>
-    
     <item>
       <title>Exercise 1.10 - Explore Catalog Configuration</title>
       <link>/workshops/cloudforms41/exercise1.10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.10/</guid>
-      <description>Log in to CloudForms using the admin account (if not done already).
- Exercise 1.10 - Explore Catalog Configuration Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs.  Services Catalog
-Step 2. Select the Catalog Items accordion.  Services Catalog Items
-Step 3. Select All Catalog Items → VMware Operations → Deploy Ticket Monster on VMware  Services Catalog Ticket Monster
-Step 4. Explore the Details and Selected Resources tabs.</description>
+      <description>Log in to CloudForms using the admin account (if not done already).&#xA;Exercise 1.10 - Explore Catalog Configuration Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs. Services Catalog&#xA;Step 2. Select the Catalog Items accordion. Services Catalog Items&#xA;Step 3. Select All Catalog Items → VMware Operations → Deploy Ticket Monster on VMware Services Catalog Ticket Monster&#xA;Step 4. Explore the Details and Selected Resources tabs. In a live environment, this tab displays details about the item the user is ordering.</description>
     </item>
-    
     <item>
       <title>Exercise 1.11 - Explore Chargeback</title>
       <link>/workshops/cloudforms41/exercise1.11/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.11/</guid>
-      <description>Exercise 1.11 - Explore Chargeback Exercise Description In Red Hat CloudForms, the chargeback feature of CloudForms Management Engine (CFME) enables you to calculate monetary virtual machine charges, based on owner or company tag. In this exercise you will learn how to review chargebacks, and explore related reports, rates and assignments.
-Section 1: Explore Chargebacks CloudForms Management Engine provides a default set of rates for calculating chargeback costs, but you can create your own set of computing and storage costs, as well.</description>
+      <description>Exercise 1.11 - Explore Chargeback Exercise Description In Red Hat CloudForms, the chargeback feature of CloudForms Management Engine (CFME) enables you to calculate monetary virtual machine charges, based on owner or company tag. In this exercise you will learn how to review chargebacks, and explore related reports, rates and assignments.&#xA;Section 1: Explore Chargebacks CloudForms Management Engine provides a default set of rates for calculating chargeback costs, but you can create your own set of computing and storage costs, as well.</description>
     </item>
-    
     <item>
       <title>Exercise 1.12 - Explore Utilization</title>
       <link>/workshops/cloudforms41/exercise1.12/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.12/</guid>
-      <description>Exercise 1.12 - Explore Utilization Exercise Description CloudForms Management Engine server can collect and analyze capacity and utilization data from your virtual infrastructure. In this exercise, you will learn how to view utilization metrics.
-Section 1: Explore Utilization Step 1. Select Optimize → Utilization.  Utilization
-Step 2. Select Region 10 → Cloud/Infrastructure Providers → RHV-M.  Region 10 RHV-M Utilization
-Step 3. On the Summary tab, review the daily utilization chart.</description>
+      <description>Exercise 1.12 - Explore Utilization Exercise Description CloudForms Management Engine server can collect and analyze capacity and utilization data from your virtual infrastructure. In this exercise, you will learn how to view utilization metrics.&#xA;Section 1: Explore Utilization Step 1. Select Optimize → Utilization. Utilization&#xA;Step 2. Select Region 10 → Cloud/Infrastructure Providers → RHV-M. Region 10 RHV-M Utilization&#xA;Step 3. On the Summary tab, review the daily utilization chart. Step 4.</description>
     </item>
-    
     <item>
       <title>Exercise 1.13 - Explore Planning</title>
       <link>/workshops/cloudforms41/exercise1.13/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.13/</guid>
-      <description>Exercise 1.13 - Explore Planning Exercise Description In this exercise you will learn how to plan and optimize a deployment.
-Section 1: Explore Planning Step 1. Select Optimize → Planning.  Optimize Planning
-Step 2. Under Reference VM Selection, select All VMs.  Reference VM Selection
-Step 3. Choose the CFME027 VM. Step 4. Under VM Options, set the Source to Usage. Step 5. Under Target Options/Limits, set Show to Hosts.</description>
+      <description>Exercise 1.13 - Explore Planning Exercise Description In this exercise you will learn how to plan and optimize a deployment.&#xA;Section 1: Explore Planning Step 1. Select Optimize → Planning. Optimize Planning&#xA;Step 2. Under Reference VM Selection, select All VMs. Reference VM Selection&#xA;Step 3. Choose the CFME027 VM. Step 4. Under VM Options, set the Source to Usage. Step 5. Under Target Options/Limits, set Show to Hosts. Step 6.</description>
     </item>
-    
     <item>
       <title>Exercise 1.14 - Examine Policies</title>
       <link>/workshops/cloudforms41/exercise1.14/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.14/</guid>
-      <description>Exercise 1.14 - Examine Policies Exercise Description Policy profiles are groups of policies that you can apply to entities within CloudForms. Two common types of policies are Compliance policies, which check for a specific state in a host or VM, and Control policies, which control a host or VM, depending on certain criteria.
-In this exercise, you will learn how to work with policies, events, conditions, actions, alerts, and profiles.</description>
+      <description>Exercise 1.14 - Examine Policies Exercise Description Policy profiles are groups of policies that you can apply to entities within CloudForms. Two common types of policies are Compliance policies, which check for a specific state in a host or VM, and Control policies, which control a host or VM, depending on certain criteria.&#xA;In this exercise, you will learn how to work with policies, events, conditions, actions, alerts, and profiles.</description>
     </item>
-    
     <item>
       <title>Exercise 1.15 - Explore Network Topology</title>
       <link>/workshops/cloudforms41/exercise1.15/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.15/</guid>
       <description>Exercise 1.15 - Explore Network Topology Exercise Description When working in complex provider environments, with many objects, Red Hat CloudForms topology feature can be extremely useful, to quickly view and categorize information. The topology view enables you to view a container provider’s objects, plus their details, such as the properties, status, and relationships to other provider objects. In this exercise, you will learn how to explore the topology of a network.</description>
     </item>
-    
     <item>
       <title>Exercise 1.16 - Explore Containers</title>
       <link>/workshops/cloudforms41/exercise1.16/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.16/</guid>
-      <description>Exercise 1.16 - Explore Containers Exercise Description In this exercise we will take a general overview of containers and how you will work with them in Red Hat CloudForms.
-First, it is important to know the definition of a container: A container is an application sandbox that wraps your software in a complete filesystem, containing everything it needs to run.
- Traditional OS vs. Containers
-Exploring Containers Step 1. Go to Compute → Containers.</description>
+      <description>Exercise 1.16 - Explore Containers Exercise Description In this exercise we will take a general overview of containers and how you will work with them in Red Hat CloudForms.&#xA;First, it is important to know the definition of a container: A container is an application sandbox that wraps your software in a complete filesystem, containing everything it needs to run.&#xA;Traditional OS vs. Containers&#xA;Exploring Containers Step 1. Go to Compute → Containers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.17 - Introduction to the Automate Datastore</title>
       <link>/workshops/cloudforms41/exercise1.17/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.17/</guid>
-      <description>Exercise 1.17 - Introduction to the Automate Datastore Exercise Description In this exercise, you will learn about scripting actions, used to control automation datastore functions.
-When we use the Automate capability of CloudForms, we write scripts in the Ruby language and use objects that the CloudForms Automation Engine makes available to us. The Automate model is arranged to provide an object oriented hierarchy to control automation functions. The model uses the following organizational units arranged in a hierarchy:</description>
+      <description>Exercise 1.17 - Introduction to the Automate Datastore Exercise Description In this exercise, you will learn about scripting actions, used to control automation datastore functions.&#xA;When we use the Automate capability of CloudForms, we write scripts in the Ruby language and use objects that the CloudForms Automation Engine makes available to us. The Automate model is arranged to provide an object oriented hierarchy to control automation functions. The model uses the following organizational units arranged in a hierarchy:</description>
     </item>
-    
     <item>
       <title>Exercise 1.18 - “Hello, World!” Automation Script</title>
       <link>/workshops/cloudforms41/exercise1.18/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.18/</guid>
-      <description>Exercise 1.18 - “Hello, World!” Automation Script Exercise Description Let’s jump right in and start writing our first automation script. In time-honored fashion we’ll write “Hello, World!” to the Automate Engine logfile.
-Before we do anything, we need to ensure that the Automation Engine server role is selected on our CloudForms appliance. We do this from the Configure → Configuration menu, selecting the CloudForms server in the Settings accordion.
-  The Automation Engine server role is now enabled by default in CloudForms 4.</description>
+      <description>Exercise 1.18 - “Hello, World!” Automation Script Exercise Description Let’s jump right in and start writing our first automation script. In time-honored fashion we’ll write “Hello, World!” to the Automate Engine logfile.&#xA;Before we do anything, we need to ensure that the Automation Engine server role is selected on our CloudForms appliance. We do this from the Configure → Configuration menu, selecting the CloudForms server in the Settings accordion.&#xA;The Automation Engine server role is now enabled by default in CloudForms 4.</description>
     </item>
-    
     <item>
       <title>Exercise 1.19 - Ansible Inside</title>
       <link>/workshops/cloudforms41/exercise1.19/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.19/</guid>
-      <description>Exercise 1.19 - Ansible Inside Exercise Description Red Hat Ansible integration delivers out-of-the-box support for backing service, alert and policy actions using Ansible playbooks. Sync your existing playbook repositories with CloudForms, add credentials to access providers, and create service catalog items for actions ranging from creating and retiring VMs, updating security software, or adding additional disks when space runs low.
-Ansible integrates with Red Hat CloudForms to provide automation solutions, using playbooks, for Service, Policy and Alert actions.</description>
+      <description>Exercise 1.19 - Ansible Inside Exercise Description Red Hat Ansible integration delivers out-of-the-box support for backing service, alert and policy actions using Ansible playbooks. Sync your existing playbook repositories with CloudForms, add credentials to access providers, and create service catalog items for actions ranging from creating and retiring VMs, updating security software, or adding additional disks when space runs low.&#xA;Ansible integrates with Red Hat CloudForms to provide automation solutions, using playbooks, for Service, Policy and Alert actions.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Discovering Virtualization Host Systems</title>
       <link>/workshops/cloudforms41/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.2/</guid>
-      <description>Exercise 1.2 - Discovering Virtualization Host Systems Exercise Description In this exercise, you will learn how to view, search and manage host systems.
-In Red Hat CloudForms, hosts are hypervisors running on physical hardware providing virtual machines and infrastructure.
-The CloudForms Management Engine automatically adds hosts from discovered providers. However, you can also discover hosts directly if not using a provider. Discovering hosts is only supported for standalone VMware vSphere servers.</description>
+      <description>Exercise 1.2 - Discovering Virtualization Host Systems Exercise Description In this exercise, you will learn how to view, search and manage host systems.&#xA;In Red Hat CloudForms, hosts are hypervisors running on physical hardware providing virtual machines and infrastructure.&#xA;The CloudForms Management Engine automatically adds hosts from discovered providers. However, you can also discover hosts directly if not using a provider. Discovering hosts is only supported for standalone VMware vSphere servers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Docker `USER`</title>
       <link>/workshops/security_containers/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.2/</guid>
-      <description>Exercise 1.2 - Docker USER   Exercise Description Now that you&amp;#8217;ve gotten a sense of software provenance in Dockerfiles lets take a look at the USER in Dockerfiles.
- By default, containers run as root. A container running as root has full control of the host system. As container technology matures, more secure default options may become available. For now, requiring root is dangerous for others and may not be available in all environments.</description>
+      <description>Exercise 1.2 - Docker USER Exercise Description Now that you’ve gotten a sense of software provenance in Dockerfiles lets take a look at the USER in Dockerfiles.&#xA;By default, containers run as root. A container running as root has full control of the host system. As container technology matures, more secure default options may become available. For now, requiring root is dangerous for others and may not be available in all environments.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Linux Kernel Capabilities</title>
       <link>/workshops/security_openshift/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.2/</guid>
-      <description>Before we get into OpenShift lets explore what Linux Kernel Capabilities are and some of the steps that OpenShift has taken to remove certain capabilities by default.
-   What are Linux Capabilities? According to the capabilities man page;
- Capabilities are distinct units of privilege that can be independently enabled or disabled.
- Capabilities were added to the kernel around 15 or so years ago to try to divide up the power of root.</description>
+      <description>Before we get into OpenShift lets explore what Linux Kernel Capabilities are and some of the steps that OpenShift has taken to remove certain capabilities by default.&#xA;What are Linux Capabilities? According to the capabilities man page;&#xA;Capabilities are distinct units of privilege that can be independently enabled or disabled.&#xA;Capabilities were added to the kernel around 15 or so years ago to try to divide up the power of root.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Running Your Playbook</title>
       <link>/workshops/ansible_automation/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.2/</guid>
-      <description>Section 1: Running the playbook We are now going to run your brand-new playbook, on your two web nodes. To do this, you are going to use the ansible-playbook command.
- Step 1: Check your playbook However, before you run the playbook, lets take a few moments to understand the options.
-   install_apache.yml This is the name of the playbook that we are running.
-  -v Altough not used here, this increases verbosity.</description>
+      <description>Section 1: Running the playbook We are now going to run your brand-new playbook, on your two web nodes. To do this, you are going to use the ansible-playbook command.&#xA;Step 1: Check your playbook However, before you run the playbook, lets take a few moments to understand the options.&#xA;install_apache.yml This is the name of the playbook that we are running.&#xA;-v Altough not used here, this increases verbosity.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Running Your Playbook</title>
       <link>/workshops/ansible_tower_azure/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.2/</guid>
-      <description>Section 1: Running the Playbook We are now going to run your brand spankin&#39; new playbook on your two web nodes. To do this, you are going to use the ansible-playbook command.
- Step 1: Run your playbook From your playbook directory ( ~/apache_basic ), run your playbook.
- ansible-playbook -i ../hosts install_apache.yml --private-key=~/.ssh/example-tower   However, before you run that command, lets take a few moments to understand the options.</description>
+      <description>Section 1: Running the Playbook We are now going to run your brand spankin&amp;#39; new playbook on your two web nodes. To do this, you are going to use the ansible-playbook command.&#xA;Step 1: Run your playbook From your playbook directory ( ~/apache_basic ), run your playbook.&#xA;ansible-playbook -i ../hosts install_apache.yml --private-key=~/.ssh/example-tower However, before you run that command, lets take a few moments to understand the options.&#xA;--private-key This option ask for the private ssh key to connect to the remote machine.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - SELinux Contexts</title>
       <link>/workshops/selinux_policy/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise1.2/</guid>
-      <description>Exercise Description All processes and files are labeled with an SELinux context. The context contains information that SELinux needs to make control decisions. Contexts contain user, role, type, and level information,
- Step 1: Examine a context To get started, let&amp;#8217;s check the context of a file in the ec2-user user&amp;#8217;s home directory:
- ls -Z ~ec2-user/.vimrc  unconfined_u:object_r:user_home_t:s0 /home/ec2-user/.vimrc   As a side note, the -Z flag is present, in a wide variety of common CLI tools, including ls and ps.</description>
+      <description>Exercise Description Let’s peer under the hood a bit to see how SELinux works. All processes and files are labeled with an SELinux context; contexts contain user, role, type, and level information. This is information that SELinux needs to enforce the active policy (eg, make access decisions). But where do files and directories get their contexts?&#xA;Contexts are set when files are created, based on their parent directory’s context (with a few exceptions)</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Tour of the Web Console</title>
       <link>/workshops/rhel_8/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.2/</guid>
-      <description>Exercise Description To get started, we will take a tour of the web console. The web console (called cockpit) will be your primary interactive interface to RHEL. The console has a number of functions that enable you to manage most aspects of the installation.
- Connect to your personal lab environment. Ensure that the information in the footer of the page is correctly filled out and the URL for your environment should show up below</description>
+      <description>Exercise Description To get started, we will take a tour of the web console. The web console (called cockpit) will be your primary interactive interface to RHEL. The console has a number of functions that enable you to manage most aspects of the installation.&#xA;Connect to your personal lab environment. Ensure that the information in the footer of the page is correctly filled out and the URL for your environment should show up below</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Working with Container Images</title>
       <link>/workshops/containers_101/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.2/</guid>
-      <description>Exercise 1.2 - Working with Container Images   Exercise Description In this exercise, you&amp;#8217;ll learn the fundamentals of container images, including how to run them and how to see what is inside of a container. Container storage volumes will be discussed, showing how to mount external file systems, with useful functions and data. We will also discuss container metadata and explain what types of information you can get from them.</description>
+      <description>Exercise 1.2 - Working with Container Images Exercise Description In this exercise, you’ll learn the fundamentals of container images, including how to run them and how to see what is inside of a container. Container storage volumes will be discussed, showing how to mount external file systems, with useful functions and data. We will also discuss container metadata and explain what types of information you can get from them.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Writing a playbook to push podman to the edge</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/</guid>
-      <description>Objective This exercise showcases using Ansible to configure podman and the podman API on a standalone Red Hat Enterprise Linux edge server.
- As part of the execise, you will be exposed to the following elements:
-   Ansible modules and supporting parameters (example: &#39;package&#39; and &#39;service&#39; modules)
-  How to use loops to make your ansible more efficient and smaller
-     Section 1: Creating a directory structure and files for your own playbook For our playbook, we are only going to write one play with two tasks.</description>
+      <description>Objective This exercise showcases using Ansible to configure podman and the podman API on a standalone Red Hat Enterprise Linux edge server.&#xA;As part of the execise, you will be exposed to the following elements:&#xA;Ansible modules and supporting parameters (example: &amp;#39;package&amp;#39; and &amp;#39;service&amp;#39; modules)&#xA;How to use loops to make your ansible more efficient and smaller&#xA;Section 1: Creating a directory structure and files for your own playbook For our playbook, we are only going to write one play with two tasks.</description>
     </item>
-    
     <item>
       <title>Exercise 1.20 - Ansible Tower</title>
       <link>/workshops/cloudforms41/exercise1.20/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.20/</guid>
-      <description>Ansible Tower Exercise Description Ansible Tower is a management tool integrated with Red Hat CloudForms, designed to help automate infrastructure operations. Red Hat CloudForms allows you to execute Ansible Tower jobs using service catalogs and Automate. No custom configuration or Ruby scripting is needed in Red Hat CloudForms, as configuration is done in Ansible Tower using playbooks.
-You can use the large library of existing Ansible playbooks as Red Hat CloudForms state machines to automate tasks such as backups, package updates, and maintenance in your Red Hat CloudForms environment.</description>
+      <description>Ansible Tower Exercise Description Ansible Tower is a management tool integrated with Red Hat CloudForms, designed to help automate infrastructure operations. Red Hat CloudForms allows you to execute Ansible Tower jobs using service catalogs and Automate. No custom configuration or Ruby scripting is needed in Red Hat CloudForms, as configuration is done in Ansible Tower using playbooks.&#xA;You can use the large library of existing Ansible playbooks as Red Hat CloudForms state machines to automate tasks such as backups, package updates, and maintenance in your Red Hat CloudForms environment.</description>
+    </item>
+    <item>
+      <title>Exercise 1.3 - Altering behavior</title>
+      <link>/workshops/selinux_policy/exercise1.3/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/selinux_policy/exercise1.3/</guid>
+      <description>Exercise Description Let’s take a look at controlling SELinux behavior.&#xA;Exercise 1.3.1 Step 1: What mode are we in? Next, let’s check to see what SELinux mode your host is in:&#xA;getenforce Enforcing Step 2: Changing modes Now, we can change the mode that your host is in:&#xA;setenforce 0 getenforce Permissive And we can change it back:&#xA;setenforce 1 getenforce Enforcing Exercise 1.3.2 Booleans are if-then-else rules written in SELinux Policy.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Discovering VM Systems</title>
       <link>/workshops/cloudforms41/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.3/</guid>
-      <description>Exercise 1.3 - Discovering VM Systems Exercise Description In Red Hat CloudForms, infrastructure VMs are operating systems running under a hypervisor. This exercise will enable you to view and manage infrastructure VMs.
-Section 1: Explore Infrastructure VMs Step 1: Select Compute → Infrastructure → Virtual Machines.  Infrastructure VMs
-Step 2: View the list of your private datacenter’s infrastructure virtual machines. Section 2: Explore the Virtual Thumbnail for Infrastructure VMs The web interface uses virtual thumbnails to represent providers.</description>
+      <description>Exercise 1.3 - Discovering VM Systems Exercise Description In Red Hat CloudForms, infrastructure VMs are operating systems running under a hypervisor. This exercise will enable you to view and manage infrastructure VMs.&#xA;Section 1: Explore Infrastructure VMs Step 1: Select Compute → Infrastructure → Virtual Machines. Infrastructure VMs&#xA;Step 2: View the list of your private datacenter’s infrastructure virtual machines. Section 2: Explore the Virtual Thumbnail for Infrastructure VMs The web interface uses virtual thumbnails to represent providers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Managing Updates Using the Web Console</title>
       <link>/workshops/rhel_8/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.3/</guid>
-      <description>Exercise Description Now that you&amp;#8217;ve toured the web console, lets work through updating the system.
-   Section 1: Basic Updating As you did in the previous section, navigate to the Software Updates section of the Web Console, by clicking on the Software Updates link, in the left-hand menu. There will then be a brief interval where Refreshing package information will appear, along with a progress bar. Once that completes, you can proceed with the exercise.</description>
+      <description>Exercise Description Now that you’ve toured the web console, lets work through updating the system.&#xA;Section 1: Basic Updating As you did in the previous section, navigate to the Software Updates section of the Web Console, by clicking on the Software Updates link, in the left-hand menu. There will then be a brief interval where Refreshing package information will appear, along with a progress bar. Once that completes, you can proceed with the exercise.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Remove setuid/setgid Binaries</title>
       <link>/workshops/security_containers/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.3/</guid>
-      <description>Exercise 1.3 - Remove setuid/setgid Binaries   Exercise Description This exercise covers permissions that can be set for setuid and setgid binaries and best practices for managing them.
-   SETUID/SETGID Overview There are two special permissions that can be set on executable files: Set User ID (setuid) and Set Group ID (sgid). These permissions allow the file being executed to be executed with the privileges of the owner or the group.</description>
+      <description>Exercise 1.3 - Remove setuid/setgid Binaries Exercise Description This exercise covers permissions that can be set for setuid and setgid binaries and best practices for managing them.&#xA;SETUID/SETGID Overview There are two special permissions that can be set on executable files: Set User ID (setuid) and Set Group ID (sgid). These permissions allow the file being executed to be executed with the privileges of the owner or the group. For example, if a file was owned by the root user and has the setuid bit set, no matter who executed the file it would always run with root user privileges.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - SELinux</title>
       <link>/workshops/security_openshift/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.3/</guid>
-      <description>SELinux is primarily a labeling system that assigns a label (name) to every process and system object. This allows every aspect of kernel operations to be first labeled, second classified, and then ultimately enforced by a set of rules that the provider maintains.
- BENEFITS OF RUNNING SELINUX
-   All processes and files are labeled with a type. A type defines a domain for processes, and a type for files.</description>
+      <description>SELinux is primarily a labeling system that assigns a label (name) to every process and system object. This allows every aspect of kernel operations to be first labeled, second classified, and then ultimately enforced by a set of rules that the provider maintains.&#xA;BENEFITS OF RUNNING SELINUX&#xA;All processes and files are labeled with a type. A type defines a domain for processes, and a type for files. Processes are separated from each other by running in their own domains, and SELinux policy rules define how processes interact with files, as well as how processes interact with each other.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Using Variables, Loops, and Handlers</title>
       <link>/workshops/ansible_automation/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.3/</guid>
-      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.
- Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
+      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.&#xA;Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Using Variables, Loops, and Handlers</title>
       <link>/workshops/ansible_tower_azure/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.3/</guid>
-      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.
- Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
+      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.&#xA;Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Working with the Dockerfile</title>
       <link>/workshops/containers_101/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.3/</guid>
-      <description>Exercise 1.3 - Working with the Dockerfile   Exercise Description This exercise will enable you to use a Dockerfile to build a container. Once you understand how images and containers can be created from the command line, you can try building containers in a more permanent way.
- Building container images from Dockerfile files is, by far, the preferred way to create docker-formatted containers, as compared to modifying running containers and committing them to images.</description>
+      <description>Exercise 1.3 - Working with the Dockerfile Exercise Description This exercise will enable you to use a Dockerfile to build a container. Once you understand how images and containers can be created from the command line, you can try building containers in a more permanent way.&#xA;Building container images from Dockerfile files is, by far, the preferred way to create docker-formatted containers, as compared to modifying running containers and committing them to images.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - CGroups</title>
       <link>/workshops/security_containers/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.4/</guid>
-      <description>Exercise 1.4 - CGroups   Exercise Description The Device Cgroup is primary in isolating and limiting containers to their own shares of CPU, memory, disk I/O, network, etc., otherwise the container will be denied. This exercise covers management of memory and CPU limitations.
-   Section 1: Memory Limits Container technology uses Cgroups to control and limit the amount of system resources a container can use, and provide administrators with fine-grained control over allocating, prioritizing, denying, managing and monitoring system resources.</description>
+      <description>Exercise 1.4 - CGroups Exercise Description The Device Cgroup is primary in isolating and limiting containers to their own shares of CPU, memory, disk I/O, network, etc., otherwise the container will be denied. This exercise covers management of memory and CPU limitations.&#xA;Section 1: Memory Limits Container technology uses Cgroups to control and limit the amount of system resources a container can use, and provide administrators with fine-grained control over allocating, prioritizing, denying, managing and monitoring system resources.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Configuring Terminal Session Recording</title>
       <link>/workshops/rhel_8/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.4/</guid>
-      <description>Section 1. Deploying Session Recording To be able to deploy the Session Recording solution you need to have the following packages installed: tlog, SSSD, cockpit-session-recording.
-Note that session recording doesn&amp;#8217;t work for graphical desktop sessions or Cockpit terminal sessions.
- Step 1.1: Pre-Requisites In order to work with session recording, your system will need to have the following installed:
-   tlog
-  SSSD (System Security Services Deamon)</description>
+      <description>Section 1. Deploying Session Recording To be able to deploy the Session Recording solution you need to have the following packages installed: tlog, SSSD, cockpit-session-recording. Note that session recording doesn’t work for graphical desktop sessions or Cockpit terminal sessions.&#xA;Step 1.1: Pre-Requisites In order to work with session recording, your system will need to have the following installed:&#xA;tlog&#xA;SSSD (System Security Services Deamon)&#xA;cockpit-session-recording&#xA;For this workshop/lab the environment is already configured to have tlog and SSSD installed, but if you were to install these prerequisites yourself, you would run sudo yum install -y tlog cockpit-session-recording systemd-journal-remote</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Explore Reports</title>
       <link>/workshops/cloudforms41/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.4/</guid>
-      <description>Exercise 1.4 - Explore Reports Exercise Description In this exercise, you will learn how to view, search and customize reports.
-In Red Hat CloudForms, reports have been constructed to help you view the most commonly requested and significant data. With appropriate access credentials, you can also create reports. CloudForms Management Engine provides a large group of default reports, organized into categories. Each category has a set of subfolders.
-Section 1: Explore Reports Step 1: Select Cloud Intel → Reports.</description>
+      <description>Exercise 1.4 - Explore Reports Exercise Description In this exercise, you will learn how to view, search and customize reports.&#xA;In Red Hat CloudForms, reports have been constructed to help you view the most commonly requested and significant data. With appropriate access credentials, you can also create reports. CloudForms Management Engine provides a large group of default reports, organized into categories. Each category has a set of subfolders.&#xA;Section 1: Explore Reports Step 1: Select Cloud Intel → Reports.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Running the apache-basic-playbook</title>
       <link>/workshops/ansible_automation/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.4/</guid>
-      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let&amp;#8217;s do that now.
-   Section 1: Running your new apache playbook Step 1: Run your playbook Run your playbook, using the following command.
- cd ~/apache-basic-playbook ansible-playbook site.yml      Section 2: Review If successful, you should see standard output that looks very similar to the following.</description>
+      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let’s do that now.&#xA;Section 1: Running your new apache playbook Step 1: Run your playbook Run your playbook, using the following command.&#xA;cd ~/apache-basic-playbook ansible-playbook site.yml Section 2: Review If successful, you should see standard output that looks very similar to the following.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Running the apache-basic-playbook</title>
       <link>/workshops/ansible_tower_azure/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.4/</guid>
-      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let&amp;#8217;s do that now.
-   Section 1 - Running your new apache playbook Step 1: Create a host file Make sure you are in the right directory and create a host file.</description>
+      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let’s do that now.&#xA;Section 1 - Running your new apache playbook Step 1: Create a host file Make sure you are in the right directory and create a host file.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Skopeo</title>
       <link>/workshops/security_openshift/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.4/</guid>
-      <description>Skopeo is a command line utility for various operations on container images and image repositories.
- Skopeo is able to inspect a repository on a Docker registry and fetch images layers. By inspect I mean it fetches the repository&amp;#8217;s manifest and it is able to show you a docker inspect-like json output about a whole repository or a tag.
- This tool, in contrast to docker inspect, helps you gather useful information about a repository or a tag before pulling it (using disk space) - e.</description>
+      <description>Skopeo is a command line utility for various operations on container images and image repositories.&#xA;Skopeo is able to inspect a repository on a Docker registry and fetch images layers. By inspect I mean it fetches the repository’s manifest and it is able to show you a docker inspect-like json output about a whole repository or a tag.&#xA;This tool, in contrast to docker inspect, helps you gather useful information about a repository or a tag before pulling it (using disk space) - e.</description>
+    </item>
+    <item>
+      <title>Exercise 1.4 - Troubleshooting</title>
+      <link>/workshops/selinux_policy/exercise1.4/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/selinux_policy/exercise1.4/</guid>
+      <description>Exercise Description Let’s look at some techniques for examing SELinux, as these are useful for troubleshooting. We’ll build on this in Section 2 of the workshop.&#xA;Step 1: Changing modes for specific domains You can also set individual SELinux domains (like httpd_t, which controls web server access control) to permissve mode:&#xA;semanage permissive -a httpd_t semanage permissive -l Builtin Permissive Types Customized Permissive Types httpd_t And again, we can change it back:</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Working with a Container Registry</title>
       <link>/workshops/containers_101/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.4/</guid>
-      <description>Exercise 1.4 - Working with a Container Registry   Exercise Description In this exercise, you will learn container registry basics, what the registry offers and how to use it.
- What is container registry?
- A basic container registry is a stateless, highly scalable server side application that stores and distributes container images. The docker registry is an open-source project offered under the permissive Apache license.
- Why use container registries?</description>
+      <description>Exercise 1.4 - Working with a Container Registry Exercise Description In this exercise, you will learn container registry basics, what the registry offers and how to use it.&#xA;What is container registry?&#xA;A basic container registry is a stateless, highly scalable server side application that stores and distributes container images. The docker registry is an open-source project offered under the permissive Apache license.&#xA;Why use container registries?&#xA;You should use a private container registry if you want to:</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Atomic Scanner</title>
       <link>/workshops/security_openshift/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.5/</guid>
-      <description>The atomic command-line tool provides a way to interact and manage Atomic Host systems and containers. It provides a high level, coherent entrypoint to the system and makes it easier to interact with special kinds of containers, such as super-privileged containers, and debugging tools.
- The atomic command uses tools such as docker, ostree and skopeo to manage containers and container host systems. There are also a lot of features built into the atomic command that are not available in the docker command.</description>
+      <description>The atomic command-line tool provides a way to interact and manage Atomic Host systems and containers. It provides a high level, coherent entrypoint to the system and makes it easier to interact with special kinds of containers, such as super-privileged containers, and debugging tools.&#xA;The atomic command uses tools such as docker, ostree and skopeo to manage containers and container host systems. There are also a lot of features built into the atomic command that are not available in the docker command.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Examine Infrastructure Provisioning</title>
       <link>/workshops/cloudforms41/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.5/</guid>
-      <description>Exercise 1.5: Examine Infrastructure Provisioning Exercise Description Learn to provision infrastructures, using Red Hat CloudForms. CloudForms enables provisioning and management across physical, virtual, and private cloud platforms.
-Red Hat CloudForms Infrastructure Provisioning process (Summary) In Red Hat CloudForms, when a virtual machine or cloud instance is provisioned, it goes through multiple phases. First, the request must be made. The request includes ownership information, tags, virtual hardware requirements, the operating system, and any customization of the request.</description>
+      <description>Exercise 1.5: Examine Infrastructure Provisioning Exercise Description Learn to provision infrastructures, using Red Hat CloudForms. CloudForms enables provisioning and management across physical, virtual, and private cloud platforms.&#xA;Red Hat CloudForms Infrastructure Provisioning process (Summary) In Red Hat CloudForms, when a virtual machine or cloud instance is provisioned, it goes through multiple phases. First, the request must be made. The request includes ownership information, tags, virtual hardware requirements, the operating system, and any customization of the request.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Managing Cryptographic Policies</title>
       <link>/workshops/rhel_8/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.5/</guid>
-      <description>Exercise Description RHEL 8 makes it easy to enforce a strong and consistent cryptographic policy on your systems.
- In the following exercises we&amp;#8217;ll use the new commands for managing your crypto configurations and test them. We will be using the web site badssl.com to test connections using different versions of relevant protocols, such as TLS.
-   Section 1: Viewing and changing the crypto policy Show the current crypto policy.</description>
+      <description>Exercise Description RHEL 8 makes it easy to enforce a strong and consistent cryptographic policy on your systems.&#xA;In the following exercises we’ll use the new commands for managing your crypto configurations and test them. We will be using the web site badssl.com to test connections using different versions of relevant protocols, such as TLS.&#xA;Section 1: Viewing and changing the crypto policy Show the current crypto policy.&#xA;update-crypto-policies --show You should see something like …​</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Namespaces</title>
       <link>/workshops/security_containers/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.5/</guid>
-      <description>Exercise 1.5 - Namespaces   Exercise Description In this exercise, we will examine how to use namespaces to manage initialization processes, in multiple containers.
- PID namespaces enable processes in different containers to have the same PID (process identifier). This means each container can have its own init (PID1) process that manages various system initialization tasks, as well as the container life cycle.
- Also, each container has its unique /proc directory.</description>
+      <description>Exercise 1.5 - Namespaces Exercise Description In this exercise, we will examine how to use namespaces to manage initialization processes, in multiple containers.&#xA;PID namespaces enable processes in different containers to have the same PID (process identifier). This means each container can have its own init (PID1) process that manages various system initialization tasks, as well as the container life cycle.&#xA;Also, each container has its unique /proc directory. Note that from within the container, you can only monitor those processes running inside this container.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Roles: Making your playbooks reusable</title>
       <link>/workshops/ansible_automation/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.5/</guid>
-      <description>Exercise Description While it is possible to write a playbook in one file, as we&amp;#8217;ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.
- The &#34;role&#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
+      <description>Exercise Description While it is possible to write a playbook in one file, as we’ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.&#xA;The &amp;#34;role&amp;#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &amp;#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Roles: Making your playbooks reusable</title>
       <link>/workshops/ansible_tower_azure/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.5/</guid>
-      <description>Exercise Description While it is possible to write a playbook in one file as we&amp;#8217;ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.
- The &#34;role&#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
+      <description>Exercise Description While it is possible to write a playbook in one file as we’ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.&#xA;The &amp;#34;role&amp;#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &amp;#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - Explore Cloud Providers</title>
       <link>/workshops/cloudforms41/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.6/</guid>
-      <description>Exercise 1.6 - Explore Cloud Providers Exercise Description This exercise will explain how to view cloud providers and related details.
-In Red Hat CloudForms, a cloud provider is a computing platform that manages instances and enables the creation of multi-tenant infrastructure services, independently from underlying hypervisors.
-Section 1: Explore Cloud Providers Step 1: Select Compute → Clouds → Providers.  Cloud Providers
-A list of your private and public cloud providers, such as OpenStack and Amazon EC2, displays.</description>
+      <description>Exercise 1.6 - Explore Cloud Providers Exercise Description This exercise will explain how to view cloud providers and related details.&#xA;In Red Hat CloudForms, a cloud provider is a computing platform that manages instances and enables the creation of multi-tenant infrastructure services, independently from underlying hypervisors.&#xA;Section 1: Explore Cloud Providers Step 1: Select Compute → Clouds → Providers. Cloud Providers&#xA;A list of your private and public cloud providers, such as OpenStack and Amazon EC2, displays.</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - Managing Software in an Application Stream</title>
       <link>/workshops/rhel_8/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.6/</guid>
-      <description>Overview Application streams are new to RHEL 8 and provide access to the latest tools, languages and libraries, without affecting core system components. This capability gives users access to multiple versions of packages, with a known period of support. These application streams, usually provided as modules, can be thought of as package groups that represent an application, a set of tools, or runtime languages.
-   Section 1: Stream Availability Step 1: Check to see what PostgreSQL streams are available As root, use yum to see what streams are available, for PostgreSQL:</description>
+      <description>Overview Application streams are new to RHEL 8 and provide access to the latest tools, languages and libraries, without affecting core system components. This capability gives users access to multiple versions of packages, with a known period of support. These application streams, usually provided as modules, can be thought of as package groups that represent an application, a set of tools, or runtime languages.&#xA;Section 1: Stream Availability Step 1: Check to see what PostgreSQL streams are available As root, use yum to see what streams are available, for PostgreSQL:</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - Read Only Containers</title>
       <link>/workshops/security_containers/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.6/</guid>
-      <description>Exercise 1.6 - Read Only Containers   Exercise Description Let&amp;#8217;s move on to &#34;Read Only&#34; Containers. This exercise will examine read-only containers and how to manage them.
- Overview
- Imagine a scenario where an application gets compromised. The first thing the bad guy wants to do is to patch a backdoor into the application, so that the next time the application starts up, it starts up with the backdoor in place.</description>
+      <description>Exercise 1.6 - Read Only Containers Exercise Description Let’s move on to &amp;#34;Read Only&amp;#34; Containers. This exercise will examine read-only containers and how to manage them.&#xA;Overview&#xA;Imagine a scenario where an application gets compromised. The first thing the bad guy wants to do is to patch a backdoor into the application, so that the next time the application starts up, it starts up with the backdoor in place. If the container was read-­only it would prevent leaving a backdoor in place and be forced to start the cycle from the beginning.</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - SCC &amp; Seccomp</title>
       <link>/workshops/security_openshift/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.6/</guid>
       <description>In addition to authorization policies that control what a user can do, OpenShift Container Platform provides security context constraints (SCC) that control the actions that a pod can perform and what it has the ability to access. Administrators can manage SCCs using the CLI. This is a great way to lock down you individual application to make sure that they have hardened settings. This applies to applications running on OpenShift.</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - Explore Cloud Instances</title>
       <link>/workshops/cloudforms41/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.7/</guid>
-      <description>#Exercise 1.7 - Explore Cloud Instances
-Exercise Description In Red Hat CloudForms, a cloud instance is a virtual machine running under cloud infrastructure. In this exercise, you will learn how to search for cloud instances and review the details related to the cloud instance.
-Section 1: Explore Cloud Instances &amp;gt; Select Compute → Clouds → Instances.  Cloud Instances
-A list of your public and private cloud instances displays.
-Section 2: Explore the Virtual Thumbnail for Cloud Instances The web interface uses virtual thumbnails to represent providers.</description>
+      <description>#Exercise 1.7 - Explore Cloud Instances&#xA;Exercise Description In Red Hat CloudForms, a cloud instance is a virtual machine running under cloud infrastructure. In this exercise, you will learn how to search for cloud instances and review the details related to the cloud instance.&#xA;Section 1: Explore Cloud Instances &amp;gt; Select Compute → Clouds → Instances. Cloud Instances&#xA;A list of your public and private cloud instances displays.&#xA;Section 2: Explore the Virtual Thumbnail for Cloud Instances The web interface uses virtual thumbnails to represent providers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - OpenSCAP Security Compliance Scanning</title>
       <link>/workshops/rhel_8/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.7/</guid>
-      <description>Overview RHEL 8 makes it easy to maintain secure and compliant systems with OpenSCAP.  What is SCAP? SCAP (Security Content Automation Protocol) is a NIST project that standardizes the language for describing assessment criteria and findings. It also provides a vulnerability rating system. The project&amp;#8217;s home page is https://scap.nist.gov/
- The essential components of SCAP are:
-   XCCDF: The Extensible Configuration Checklist Description Format, to describe security checklists</description>
+      <description>Overview RHEL 8 makes it easy to maintain secure and compliant systems with OpenSCAP. What is SCAP? SCAP (Security Content Automation Protocol) is a NIST project that standardizes the language for describing assessment criteria and findings. It also provides a vulnerability rating system. The project’s home page is https://scap.nist.gov/&#xA;The essential components of SCAP are:&#xA;XCCDF: The Extensible Configuration Checklist Description Format, to describe security checklists&#xA;OVAL®: Open Vulnerability and Assessment Language, a declarative language for making logical assertions about the state of a system</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - Red Hat Container Catalog</title>
       <link>/workshops/security_openshift/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.7/</guid>
-      <description>Red Hat Container Catalog
-  While public registries and uncurated repositories are acceptable for some cloud-native development and proof-of-concept projects, they do not always provide content that is fit for production consumption; enterprise workloads require enterprise-ready tools.   MATTHEW HICKSVICE PRESIDENT, ENGINEERING, OPENSHIFT AND MANAGEMENT, RED HAT
- While container-based applications have begun moving into production, not all containers are created or maintained equally. Every container starts with a Linux base layer, which means that every ISV building container images is distributing Linux content.</description>
+      <description>Red Hat Container Catalog&#xA;While public registries and uncurated repositories are acceptable for some cloud-native development and proof-of-concept projects, they do not always provide content that is fit for production consumption; enterprise workloads require enterprise-ready tools. MATTHEW HICKSVICE PRESIDENT, ENGINEERING, OPENSHIFT AND MANAGEMENT, RED HAT&#xA;While container-based applications have begun moving into production, not all containers are created or maintained equally. Every container starts with a Linux base layer, which means that every ISV building container images is distributing Linux content.</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - Seccomp</title>
       <link>/workshops/security_containers/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.7/</guid>
-      <description>Exercise 1.7 - Seccomp   Exercise Description Secure Computing Mode (seccomp) is a kernel feature that enables you to filter system calls to the kernel from a container. The combination of restricted and allowed calls are arranged in profiles, and you can pass different profiles to different containers. Seccomp provides more fine-grained control than capabilities, giving an attacker a limited number of syscalls from the container. This exercise examines how seccomp works and how it can be employed to provide container security.</description>
+      <description>Exercise 1.7 - Seccomp Exercise Description Secure Computing Mode (seccomp) is a kernel feature that enables you to filter system calls to the kernel from a container. The combination of restricted and allowed calls are arranged in profiles, and you can pass different profiles to different containers. Seccomp provides more fine-grained control than capabilities, giving an attacker a limited number of syscalls from the container. This exercise examines how seccomp works and how it can be employed to provide container security.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - Explore Group and User Access Controls</title>
       <link>/workshops/cloudforms41/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.8/</guid>
-      <description>Exercise 1.8 - Explore Group and User Access Controls Exercise Description This exercise is designed to provide an understanding of Red Hat CloudForms group controls and access controls.
-Section 1: Explore Access Control Step 1. Go to Administrator (in the top right corner of the screen) → Configuration and select the Access Control accordion.  Configuration Dashboard
- Access Control
-Step 2. Add a role by modifying a copy of an existing role: Step 3.</description>
+      <description>Exercise 1.8 - Explore Group and User Access Controls Exercise Description This exercise is designed to provide an understanding of Red Hat CloudForms group controls and access controls.&#xA;Section 1: Explore Access Control Step 1. Go to Administrator (in the top right corner of the screen) → Configuration and select the Access Control accordion. Configuration Dashboard&#xA;Access Control&#xA;Step 2. Add a role by modifying a copy of an existing role: Step 3.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - Introduction to using buildah, podman and skopeo to work on containers</title>
       <link>/workshops/rhel_8/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.8/</guid>
-      <description>Exercise Description In this exercise, you will build a custom application container utilizing the Red Hat Universal Base Image, customize that image and test the image functionality. After that you will use skopeo to transfer that image from your user local repository to the system repository and configure it to start at boot.
- After completing this section, you will be able to build images from an existing base image using buildah and other host based tools.</description>
+      <description>Exercise Description In this exercise, you will build a custom application container utilizing the Red Hat Universal Base Image, customize that image and test the image functionality. After that you will use skopeo to transfer that image from your user local repository to the system repository and configure it to start at boot.&#xA;After completing this section, you will be able to build images from an existing base image using buildah and other host based tools.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - Red Hat Security API</title>
       <link>/workshops/security_openshift/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.8/</guid>
-      <description>Red Hat Product Security is committed to providing tools and security data to help you better understand security threats. This data has been available on our Security Data page and will now also be available in a machine-consumable format with the Security Data API. This tool will allow customers to programmatically query the API for data that was previously exposed only through files on our Security Data page.</description>
+      <description>Red Hat Product Security is committed to providing tools and security data to help you better understand security threats. This data has been available on our Security Data page and will now also be available in a machine-consumable format with the Security Data API. This tool will allow customers to programmatically query the API for data that was previously exposed only through files on our Security Data page.&#xA;The data provided by the Security Data API is the same as what is found on the Security Data page: OVAL definitions, Common Vulnerability Reporting Framework (CVRF) documents and CVE data.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - SELinux</title>
       <link>/workshops/security_containers/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.8/</guid>
-      <description>Exercise 1.8 - SELinux   Exercise Description Let&amp;#8217;s move on to Security Enhanced Linux (SELinux). We will cover SELinux basics, Docker SELinux security policy and the &#34;SELinux Coloring Book.&#34;
-   Section 1: Basics of SELINUX In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations, where the other security mechanisms fail. With SELinux on Docker, we write policy that says that the container process running as svirt_lxc_net_t can only read/write files with the svirt_sandbox_file_t label.</description>
+      <description>Exercise 1.8 - SELinux Exercise Description Let’s move on to Security Enhanced Linux (SELinux). We will cover SELinux basics, Docker SELinux security policy and the &amp;#34;SELinux Coloring Book.&amp;#34;&#xA;Section 1: Basics of SELINUX In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations, where the other security mechanisms fail. With SELinux on Docker, we write policy that says that the container process running as svirt_lxc_net_t can only read/write files with the svirt_sandbox_file_t label.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - Image Streams &amp; Secrets</title>
       <link>/workshops/security_openshift/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.9/</guid>
-      <description>Image Stream Image streams can be used to automatically perform an action when new images are created. Builds and deployments can watch an image stream to receive notifications when new images are added and react by performing a build or deployment, respectively.
- For example, if a deployment is using a certain image and a new version of that image is created, a deployment could be automatically performed.</description>
+      <description>Image Stream Image streams can be used to automatically perform an action when new images are created. Builds and deployments can watch an image stream to receive notifications when new images are added and react by performing a build or deployment, respectively.&#xA;For example, if a deployment is using a certain image and a new version of that image is created, a deployment could be automatically performed.&#xA;Secrets A Secret is an object that contains a small amount of sensitive data such as a password, a token, or a key.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - Introduction to Catalogs</title>
       <link>/workshops/cloudforms41/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.9/</guid>
-      <description>The following steps are initially run as a non-admin customer account.
- Exercise 1.9 - Introduction to Catalogs Exercise Description This exercise enables you to explore and verify the catalog configuration.
-Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs.  Services Catalog
-Step 2. On the right, select the Deploy Ticket Monster on VMware catalog item.  Ticket Monster
-Step 3. Click Order to order the service.</description>
+      <description>The following steps are initially run as a non-admin customer account.&#xA;Exercise 1.9 - Introduction to Catalogs Exercise Description This exercise enables you to explore and verify the catalog configuration.&#xA;Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs. Services Catalog&#xA;Step 2. On the right, select the Deploy Ticket Monster on VMware catalog item. Ticket Monster&#xA;Step 3. Click Order to order the service. Step 4. Enter values for DBName and App Server Name and click Submit.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - Linux Kernel Capabilities</title>
       <link>/workshops/security_containers/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.9/</guid>
-      <description>Exercise 1.9 - Linux Kernel Capabilities   Exercise Description In this exercise, we will examine Linux capabilities: how they are defined, their purpose,and how they affect security.
- Linux Capabilities Defined
- According to the capabilities man page;
- Capabilities are distinct units of privilege that can be independently enabled or disabled.
- Capabilities were added to the kernel around 15 or so years ago, to try to divide up the power of root.</description>
+      <description>Exercise 1.9 - Linux Kernel Capabilities Exercise Description In this exercise, we will examine Linux capabilities: how they are defined, their purpose,and how they affect security.&#xA;Linux Capabilities Defined&#xA;According to the capabilities man page;&#xA;Capabilities are distinct units of privilege that can be independently enabled or disabled.&#xA;Capabilities were added to the kernel around 15 or so years ago, to try to divide up the power of root. Originally the kernel allocated a 32-bit bitmask to define these capabilities.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - System Roles with Ansible</title>
       <link>/workshops/rhel_8/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.9/</guid>
       <description>Exercise Description RHEL System Roles, announced with the launch of RHEL 8, are a collection of Ansible roles and modules that provide a stable and consistent configuration interface for remote management of Red Hat Enterprise Linux. They address many commmon configuration, security and workload uses on RHEL systems. These roles can manage systems running RHEL 7 and above, easing management of 3 generations of RHEL. The effort is based on development of the Linux System Roles project (link: https://linux-system-roles.</description>
     </item>
-    
     <item>
       <title>Exercise 10 - View data in AngularJS client</title>
       <link>/workshops/jdv_dev/exercise10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise10/</guid>
-      <description>View the data services   Go back to the Angualar client at http://localhost:8181
-  View each of the data services we created by navigating the lefthand pane, including the combined data service for all 3 sources
-  Change users to view masking/filtering   In the upper right, click the user icon and change the user to maskUser
-  Go to the Federated page or click reload if already on the page.</description>
+      <description>View the data services Go back to the Angualar client at http://localhost:8181&#xA;View each of the data services we created by navigating the lefthand pane, including the combined data service for all 3 sources&#xA;Change users to view masking/filtering In the upper right, click the user icon and change the user to maskUser&#xA;Go to the Federated page or click reload if already on the page.&#xA;You will see only rows with Visibility public and email is masked as anon@email.</description>
     </item>
-    
     <item>
       <title>Exercise 2 - PID and IPC Namespaces</title>
       <link>/workshops/containers_the_hard_way/exercise2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise2/</guid>
-      <description>Exercise 2.1 - The PID Basics Before we start playing with PID namespaces, it is good to have some background on how PIDs in Linux work.
- Every process that runs on a Linux system gets a Process ID (PID). This exists as a 32-bit integer. Numbering starts at 1 and increments until there are none left. PIDs can be reused once the process terminates. If you run out of PIDs, you&amp;#8217;ll have a bad time.</description>
+      <description>Exercise 2.1 - The PID Basics Before we start playing with PID namespaces, it is good to have some background on how PIDs in Linux work.&#xA;Every process that runs on a Linux system gets a Process ID (PID). This exists as a 32-bit integer. Numbering starts at 1 and increments until there are none left. PIDs can be reused once the process terminates. If you run out of PIDs, you’ll have a bad time.</description>
     </item>
-    
     <item>
       <title>Exercise 2 - Prepare the datasources</title>
       <link>/workshops/jdv_dev/exercise2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise2/</guid>
-      <description>Get the course repositories   There are two repositories, one that contains a sample JDV project with helper data/scripts and another which is the AngularJS frontend.
-  Pull down the JDV project
-  git clone https://github.com/mechevarria/jdv-demo  Next pull down the AngularJS client  https://github.com/mechevarria/jdv-demo-client Add the workshop data to PostgreSQL  The script that needs to be run is  jdv-demo/assets/postgres/create_insert.sql
- If you are running the instance from TurnKey Linux, you can load the data via a browser.</description>
+      <description>Get the course repositories There are two repositories, one that contains a sample JDV project with helper data/scripts and another which is the AngularJS frontend.&#xA;Pull down the JDV project&#xA;git clone https://github.com/mechevarria/jdv-demo Next pull down the AngularJS client https://github.com/mechevarria/jdv-demo-client Add the workshop data to PostgreSQL The script that needs to be run is jdv-demo/assets/postgres/create_insert.sql&#xA;If you are running the instance from TurnKey Linux, you can load the data via a browser.</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Build a CI/CD pipeline and container in Red Hat OpenShift</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/</guid>
-      <description>Exercise Description As part of the Applied Ansible workshop, you will deploy (copy/transfer) a container built on top of Red Hat OpenShift to an edge node running only Red Hat Enterprise Linux utilizing Ansible Automation. Prior to that step, we need to actually &#34;create&#34; a container on Red Hat OpenShift.
-   Let&amp;#8217;s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console</description>
+      <description>Exercise Description As part of the Applied Ansible workshop, you will deploy (copy/transfer) a container built on top of Red Hat OpenShift to an edge node running only Red Hat Enterprise Linux utilizing Ansible Automation. Prior to that step, we need to actually &amp;#34;create&amp;#34; a container on Red Hat OpenShift.&#xA;Let’s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Creating Custom SELinux Policy</title>
       <link>/workshops/selinux_policy/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.0/</guid>
-      <description>Exercise Description In this exercise, we are going to download the code for the example application that we are going to write policy for, and build and install it onto our test system.
- Step 1: Change directories Create a src directory, in your home directory.
- cd ~ mkdir src cd src   Step 2: Check out the source code to the example application from GitHub Download the latest code release</description>
+      <description>Exercise Description In this exercise, we are going to download the code for the example application that we are going to write policy for, and build and install it onto our test system.&#xA;Step 1: Exit root shell If you haven’t already, exit the root shell we started in Section 1. Running whoami should not return root:&#xA;whoami ec2-user Step 2: Change directories Create a src directory, in your home directory.</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Installing Ansible Tower</title>
       <link>/workshops/ansible_automation/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise2.0/</guid>
-      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node.
- Step 1: Change directories Change directories to /tmp
- cd /tmp    Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package
- curl -O https://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-3.7.3-1.tar.gz    Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-3.7.3-1.tar.gz    Step 4: Change directories Change directories into the Ansible Tower setup package</description>
+      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node.&#xA;Step 1: Change directories Change directories to /tmp&#xA;cd /tmp Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package&#xA;curl -O https://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-3.7.3-1.tar.gz Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-3.7.3-1.tar.gz Step 4: Change directories Change directories into the Ansible Tower setup package&#xA;cd /tmp/ansible-tower-setup-*/ Step 5: Open inventory file Using an editor of your choice, open the inventory file</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Installing Ansible Tower</title>
       <link>/workshops/ansible_tower_azure/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise2.0/</guid>
-      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node
-   Installing Ansible Tower Step 1: Change directories Change directories to /tmp
- cd /tmp    Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package
- curl -O http://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-latest.tar.gz    Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-latest.tar.gz    Step 4: Change directories Change directories into the Ansible Tower package</description>
+      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node&#xA;Installing Ansible Tower Step 1: Change directories Change directories to /tmp&#xA;cd /tmp Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package&#xA;curl -O http://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-latest.tar.gz Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-latest.tar.gz Step 4: Change directories Change directories into the Ansible Tower package&#xA;cd /tmp/ansible-tower-setup-*/ Step 5: Open inventory file Using an editor of your choice, open the inventory file</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Configuring Ansible Tower</title>
       <link>/workshops/ansible_automation/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise2.1/</guid>
-      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.
- There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.
-   Credentials
-  Projects
-  Inventory
-  Job Template
-     Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password ansibleWS.</description>
+      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.&#xA;There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.&#xA;Credentials&#xA;Projects&#xA;Inventory&#xA;Job Template&#xA;Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password ansibleWS.</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Configuring Ansible Tower</title>
       <link>/workshops/ansible_tower_azure/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise2.1/</guid>
-      <description>Exercise Description In this exercise, we are going to configure Tower so that we can run a playbook.
-     There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on a few of the key concepts required for this workshop today.       Credentials
-  Projects
-  Inventory</description>
+      <description>Exercise Description In this exercise, we are going to configure Tower so that we can run a playbook.&#xA;There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on a few of the key concepts required for this workshop today. Credentials&#xA;Projects&#xA;Inventory&#xA;Job Template&#xA;Section 1: Logging into Ansible Tower and installing the license key To log in, use the username admin and the password ansibleWS.</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Generating a generic policy</title>
       <link>/workshops/selinux_policy/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.1/</guid>
-      <description>Exercise Description In this exercise, we are going to automatically generate an SELinux policy framework, and learn to handle AVC messages that are generated by SELinux, when the application violates the policy.
- Step 1: Generate an initial generic SELinux policy Create a policy directory, and generate an initial policy. Use sepolicy generate to generate a policy for the app that we want to enable.
- cd ~/src mkdir policy cd policy sepolicy generate --init /usr/local/sbin/testapp  Note the last few lines in the output from sepolicy generate:</description>
+      <description>Exercise Description In this exercise, we are going to automatically generate an SELinux policy framework, and learn to handle AVC messages that are generated by SELinux, when the application violates the policy.&#xA;Step 1: Generate an initial generic SELinux policy Create a policy directory, and generate an initial policy. Use sepolicy generate to generate a policy for the app that we want to enable.&#xA;cd ~/src mkdir policy cd policy sepolicy generate --init /usr/local/sbin/testapp Note the last few lines in the output from sepolicy generate:</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Run CI/CD pipeline (powered by Tekton) in Red Hat OpenShift</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/</guid>
-      <description>Exercise Description View the created pipeline and review the container that Ansible orchestrate deploying to the edge node.
- Let&amp;#8217;s review the container build Select Pipelines in the left menu:
-    === Click on Pipeline Runs in the menu, and then edge-?????? (where ?????? is some alphanumeric sequence):
-     Wait until pipeline details are green. Feel gree to watch the progress by selecting the Logs tab</description>
+      <description>Exercise Description View the created pipeline and review the container that Ansible orchestrate deploying to the edge node.&#xA;Let’s review the container build Select Pipelines in the left menu:&#xA;=== Click on Pipeline Runs in the menu, and then edge-?????? (where ?????? is some alphanumeric sequence):&#xA;Wait until pipeline details are green. Feel gree to watch the progress by selecting the Logs tab&#xA;View built container images …​ Select Topology in the left menu</description>
     </item>
-    
     <item>
       <title>Exercise 2.2 - Creating a Custom SELinux Application Policy</title>
       <link>/workshops/selinux_policy/exercise2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.2/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to handle AVC messages that are generated by SELinux, when an application violates existing policy. We will modify the already-created generic policy, in order to allow the application to run correctly, when we switch the policy to enforcing mode.
- Step 1: Check for AVC denials Now that our app is up and running, we can check the system logs for AVC (access vector cache, where SELinux caches decisions to grant or deny access) denial messages.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to handle AVC messages that are generated by SELinux, when an application violates existing policy. We will modify the already-created generic policy, in order to allow the application to run correctly, when we switch the policy to enforcing mode.&#xA;Step 1: Check for AVC denials Now that our app is up and running, we can check the system logs for AVC (access vector cache, where SELinux caches decisions to grant or deny access) denial messages.</description>
     </item>
-    
     <item>
       <title>Exercise 2.2 - Creating and Running a Job Template</title>
       <link>/workshops/ansible_automation/exercise2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise2.2/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.
- Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.&#xA;Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
     </item>
-    
     <item>
       <title>Exercise 2.2 - Creating and Running a Job Template</title>
       <link>/workshops/ansible_tower_azure/exercise2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise2.2/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it.
- A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package. Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it.&#xA;A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package. Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
     </item>
-    
     <item>
       <title>Exercise 2.3 - Creating Policy Rules for Network Access</title>
       <link>/workshops/selinux_policy/exercise2.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.3/</guid>
-      <description>Exercise Description In this exercise, we will continue the modification of the generic application polocy to allow network traffic to be generated by the test application. There are several rules that will be needed, to handle a variety of AVC denials.
-   Section 1: HTTP Port Connectivity Step 1: Check for AVC denials Let&amp;#8217;s restart our app, to get an updated list of denials.
- sudo systemctl restart testapp  Let&amp;#8217;s start with one of the denials that will be present in the audit search results, related to connecting on TCP port 80:</description>
+      <description>Exercise Description In this exercise, we will continue the modification of the generic application polocy to allow network traffic to be generated by the test application. There are several rules that will be needed, to handle a variety of AVC denials.&#xA;Section 1: HTTP Port Connectivity Step 1: Check for AVC denials Let’s restart our app, to get an updated list of denials.&#xA;sudo systemctl restart testapp Let’s start with one of the denials that will be present in the audit search results, related to connecting on TCP port 80:</description>
     </item>
-    
     <item>
       <title>Exercise 2.4 - Finishing the Policy</title>
       <link>/workshops/selinux_policy/exercise2.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.4/</guid>
-      <description>Exercise Description In this final exercise, we will finish the testapp SELinux policy.
-   Section 1: A Last-ish Interface Step 1: Check for AVC denials Let&amp;#8217;s again restart our app, to get an updated list of denials.
- systemctl restart testapp  We only have a few denials left, and you will see that they all (probably!) reference /etc/resolv.conf or to /etc/hosts.
- ausearch -m AVC -ts recent | egrep &amp;#39;^type=AVC&amp;#39;  type=AVC msg=audit(1553195947.</description>
+      <description>Exercise Description In this final exercise, we will finish the testapp SELinux policy.&#xA;Section 1: A Last-ish Interface Step 1: Check for AVC denials Let’s again restart our app, to get an updated list of denials.&#xA;sudo systemctl restart testapp We only have a few denials left, and you will see that they all (probably!) reference /etc/resolv.conf or to /etc/hosts.&#xA;sudo ausearch -m AVC -ts recent | egrep &amp;#39;^type=AVC&amp;#39; type=AVC msg=audit(1553195947.</description>
+    </item>
+    <item>
+      <title>Exercise 2.5 - Tips &amp; Tricks</title>
+      <link>/workshops/selinux_policy/exercise2.5/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/selinux_policy/exercise2.5/</guid>
+      <description>Tips &amp;amp; tricks This is the conclusion of the SELinux policy workshop. Here’s some closing tips to help you work with SELinux. Please ask any questions that you have left, and thanks so much for coming!&#xA;Set a folder’s context to mimic another:&#xA;mkdir -p /var/new_www/html matchpathcon /var/www/html /var/new_www/html semanage fcontext -a -e /var/www /var/new_www restorecon -Rv /var/ List ports associated with all service domains:&#xA;semanage port -l And then, add a port to an existing service’s domain, such as httpd:</description>
     </item>
-    
     <item>
       <title>Exercise 3 - Network and UTS Namespaces</title>
       <link>/workshops/containers_the_hard_way/exercise3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise3/</guid>
       <description>Exercise 3.1 - Network Stack Background The networking namespace in the Kernel is actually responsible for a surprisingly large number of things. It keeps tabs on all the network interfaces and their state, routing tables (Did you know there is more than one? By default, there are 4.), firewall rules, etc. All of these things are explored using the ip command. This command allows root to view and modify the networking stack.</description>
     </item>
-    
     <item>
       <title>Exercise 3 - Prepare Postman and AngularJS client</title>
       <link>/workshops/jdv_dev/exercise3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise3/</guid>
-      <description>Prepare the AngularJS client  In the jdv-demo-client folder run the following command  npm install  Afterwards run  npm run dev  To start a node webserver that will host the AngularJS application.  * To check go to http://localhost:8181 in your browser. You will get an error when checking the pages. That is ok since we are going to be building the data services for the web application.</description>
+      <description>Prepare the AngularJS client In the jdv-demo-client folder run the following command npm install Afterwards run npm run dev To start a node webserver that will host the AngularJS application. * To check go to http://localhost:8181 in your browser. You will get an error when checking the pages. That is ok since we are going to be building the data services for the web application. Prepare Postman Import the REST tests into Postman by going to file import Select jdv-demo/assets/demo-jdv.</description>
     </item>
-    
     <item>
       <title>Exercise 3.0 - Configure Red Hat Enterprise Linux to run containers</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/</guid>
-      <description>Exercise Description As part of the exercise, we are going to run a login command on the edge node to set a temporary token. This token will allow the edge node to log into the Red Hat OpenShift registry and download containers.
- As part of the exercise, we have built a playbook for you; however, no all of the variables are assigned. This allows us to distribute the playbook to multiple workshops and you the capability to understand how to run playbooks in Ansible tower and assign custom variables to those plays.</description>
+      <description>Exercise Description As part of the exercise, we are going to run a login command on the edge node to set a temporary token. This token will allow the edge node to log into the Red Hat OpenShift registry and download containers.&#xA;As part of the exercise, we have built a playbook for you; however, no all of the variables are assigned. This allows us to distribute the playbook to multiple workshops and you the capability to understand how to run playbooks in Ansible tower and assign custom variables to those plays.</description>
     </item>
-    
     <item>
       <title>Exercise 3.0 - Using Ansible to Implement Security</title>
       <link>/workshops/ansible_automation/exercise3.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise3.0/</guid>
-      <description>Exercise Description In this exercise, we are going to use Red Hat Ansible Tower to run a Operating System Protection Profile (OSPP) for RHEL 8.x for our environment
- Step 1: Generate a security profile using OpenSCAP. In your Web Console Terminal window (if you closed it, see the SETUP step, in your workbook), install OpenScap on the Tower node:
- ansible localhost -m package -a &#34;name=scap-security-guide state=present&#34; -b   Next, setup a local projects directory to stage a remediation playbook</description>
+      <description>Exercise Description In this exercise, we are going to use Red Hat Ansible Tower to run a Operating System Protection Profile (OSPP) for RHEL 8.x for our environment&#xA;Step 1: Generate a security profile using OpenSCAP. In your Web Console Terminal window (if you closed it, see the SETUP step, in your workbook), install OpenScap on the Tower node:&#xA;ansible localhost -m package -a &amp;#34;name=scap-security-guide state=present&amp;#34; -b Next, setup a local projects directory to stage a remediation playbook</description>
     </item>
-    
     <item>
       <title>Exercise 3.0 - Using Ansible to Implement Security</title>
       <link>/workshops/ansible_tower_azure/exercise3.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise3.0/</guid>
-      <description>In this exercise, we are going to use Ansible Tower to run DISA STIG and NIST 800-53 evaluations of our environment. Note that the NIST 800-53 role also includes the execution of DISA STIG evaluation against targeted hosts.
-   DISA STIG controls https://galaxy.ansible.com/MindPointGroup/RHEL7-STIG/
-  NIST 800-53 controls https://galaxy.ansible.com/rhtps/800-53/
-     Adding the DISA STIG and NIST 800-53 role to your Tower node Step 1: Download role to Ansible roles directory In your wetty window (if you closed it, see the SETUP step, in your workbook), type the following:</description>
+      <description>In this exercise, we are going to use Ansible Tower to run DISA STIG and NIST 800-53 evaluations of our environment. Note that the NIST 800-53 role also includes the execution of DISA STIG evaluation against targeted hosts.&#xA;DISA STIG controls https://galaxy.ansible.com/MindPointGroup/RHEL7-STIG/&#xA;NIST 800-53 controls https://galaxy.ansible.com/rhtps/800-53/&#xA;Adding the DISA STIG and NIST 800-53 role to your Tower node Step 1: Download role to Ansible roles directory In your wetty window (if you closed it, see the SETUP step, in your workbook), type the following:</description>
     </item>
-    
     <item>
       <title>Exercise 3.1 - Setup Ansible template to stage temporary access token on edge node</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/</guid>
-      <description>Exercise 3.1 - Setup a template to load a temporary token on the edge node Let&amp;#8217;s bring Projects, Inventories, and Crentials all together with &amp;#8230;&amp;#8203; Templates Select Templates
-  Templates tab - Left hand side of screen  Select the + sign to add a new template; then select Job Template
-  Add Job Template      NAME
- Setup edge authentication to registry - user1</description>
+      <description>Exercise 3.1 - Setup a template to load a temporary token on the edge node Let’s bring Projects, Inventories, and Crentials all together with …​ Templates Select Templates&#xA;Templates tab - Left hand side of screen Select the + sign to add a new template; then select Job Template&#xA;Add Job Template NAME&#xA;Setup edge authentication to registry - user1&#xA;DESCRIPTION&#xA;Podman login&#xA;JOB TYPE&#xA;Run&#xA;INVENTORY&#xA;user1-inventory&#xA;PROJECT</description>
     </item>
-    
     <item>
       <title>Exercise 3.2 - Running an Ansible Automation template</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/</guid>
-      <description>Exercise 3.2 - Retrieve user token from OpenShift and launch login template In a new tab, log into Red Hat OpenShift  https://console-openshift-console.apps.example.redhatgov.io 
-    Navigate to the user1 menu in the upper right hand corner and select Copy login command.
- You will be prompted to login again. Once complete, select Display Token
-    Highlight and copy the API token, it will look like sha256~ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopq</description>
+      <description>Exercise 3.2 - Retrieve user token from OpenShift and launch login template In a new tab, log into Red Hat OpenShift https://console-openshift-console.apps.example.redhatgov.io Navigate to the user1 menu in the upper right hand corner and select Copy login command.&#xA;You will be prompted to login again. Once complete, select Display Token&#xA;Highlight and copy the API token, it will look like sha256~ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopq&#xA;Return to the Ansible Tower interface tab or navigate to https://ansible-tower-web-svc-tower.</description>
     </item>
-    
     <item>
       <title>Exercise 3.3 - Create new template to stage containers on edge node</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/</guid>
-      <description>Exercise 3.3 - Configure podman, systemd, and pull a container from OpenShift Configure new template to field containers to edge node Select Templates
-  Templates tab - Left hand side of screen  Select the + sign to add a new template; then select Job Template
-  Add Job Template      NAME
- Field container to edge node - user1
-   DESCRIPTION</description>
+      <description>Exercise 3.3 - Configure podman, systemd, and pull a container from OpenShift Configure new template to field containers to edge node Select Templates&#xA;Templates tab - Left hand side of screen Select the + sign to add a new template; then select Job Template&#xA;Add Job Template NAME&#xA;Field container to edge node - user1&#xA;DESCRIPTION&#xA;Update to latest container release in OpenShift&#xA;JOB TYPE&#xA;Run&#xA;INVENTORY&#xA;user1-inventory&#xA;PROJECT</description>
     </item>
-    
     <item>
       <title>Exercise 4 - Create new teiid project</title>
       <link>/workshops/jdv_dev/exercise4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise4/</guid>
-      <description>Create a new JDV project   In JBDS, do window  perspective  open perspective  other  teiid designer
-  file  new  teiid model project
-  Name the project jdv-demo and its ok to leave the default location.
-  Do change the default folders to sources, views and federated
-  
-teiid is the the upstream community project for JBoss Data Virtualization</description>
+      <description>Create a new JDV project In JBDS, do window perspective open perspective other teiid designer&#xA;file new teiid model project&#xA;Name the project jdv-demo and its ok to leave the default location.&#xA;Do change the default folders to sources, views and federated&#xA;teiid is the the upstream community project for JBoss Data Virtualization&#xA;Create a VDB file New Teiid VDB&#xA;name the vdb demo-jdv&#xA;Deploy a VDB Double click the new vdb and then click the Deploy</description>
     </item>
-    
     <item>
       <title>Exercise 4 - User Namespace</title>
       <link>/workshops/containers_the_hard_way/exercise4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise4/</guid>
       <description>Exercise 4.1 - History Lesson The User Namespace is easily the newest namespce in the Linux Kernel. It was introduced to allow non-root users to run containers without a heavy root daemon. Typically, a non-priviledged user cannot spawn new namespaces. However, if a new User Namespace is created, then that same user can now spawn any type of namespace. Since this feature was introduced in the Kernel, you have seen newer container images come out that do not rely on daemons because they are no longer necessary.</description>
     </item>
-    
     <item>
       <title>Exercise 4.0 - Update to a new container on OpenShift and field to edge</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/</guid>
-      <description>Exercise Description Now that we can pull a container from OpenShift and move it to an edge node via Ansible Automation, let&amp;#8217;s repeat the process with a new release using the artifacts that we created.
-   Let&amp;#8217;s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console
-  https://console-openshift-console.apps.example.redhatgov.io 
-    Let&amp;#8217;s build the pipeline with a new release Select Pipelines in the left menu</description>
+      <description>Exercise Description Now that we can pull a container from OpenShift and move it to an edge node via Ansible Automation, let’s repeat the process with a new release using the artifacts that we created.&#xA;Let’s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console&#xA;https://console-openshift-console.apps.example.redhatgov.io Let’s build the pipeline with a new release Select Pipelines in the left menu</description>
     </item>
-    
     <item>
       <title>Exercise 5 - All Together Now</title>
       <link>/workshops/containers_the_hard_way/exercise5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise5/</guid>
-      <description>Let&amp;#8217;s put all of our new namespace skills to use! Again, we will be working as the rhel user.
- su - rhel # if neccessary unshare -mipfnuUr /bin/bash mount -t proc none /proc mount -t tmpfs none /tmp mount -t sysfs none /sys   With the call to unshare, we used all of the flags that we have used in the previous exercises. We also mounted three new filesystems after creating our sandbox.</description>
+      <description>Let’s put all of our new namespace skills to use! Again, we will be working as the rhel user.&#xA;su - rhel # if neccessary unshare -mipfnuUr /bin/bash mount -t proc none /proc mount -t tmpfs none /tmp mount -t sysfs none /sys With the call to unshare, we used all of the flags that we have used in the previous exercises. We also mounted three new filesystems after creating our sandbox.</description>
     </item>
-    
     <item>
       <title>Exercise 5 - Import PostgreSQL data</title>
       <link>/workshops/jdv_dev/exercise5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise5/</guid>
-      <description>Import JDBC datasource  file  import  teiid designer  JDBC Database &amp;raquo; source model    Under Connection Profile, select new
-  Select PostgreSQL as the Connection Profile Type, Next
-  In the next window, click the New Driver Definition icon
-  Under the Jar List tab, select Add JAR/Zip and then select jdv-demo/assets/postgres/postgresql-42.1.4.jar, then ok
-  In the New JDBC Connection Profile window make sure to use the IP address of your PostgreSQL instance and put the credentails for the postgres user and check Save Password.</description>
+      <description>Import JDBC datasource file import teiid designer JDBC Database &amp;raquo; source model Under Connection Profile, select new&#xA;Select PostgreSQL as the Connection Profile Type, Next&#xA;In the next window, click the New Driver Definition icon&#xA;Under the Jar List tab, select Add JAR/Zip and then select jdv-demo/assets/postgres/postgresql-42.1.4.jar, then ok&#xA;In the New JDBC Connection Profile window make sure to use the IP address of your PostgreSQL instance and put the credentails for the postgres user and check Save Password.</description>
     </item>
-    
     <item>
       <title>Exercise 6 - Changing the Filesystem</title>
       <link>/workshops/containers_the_hard_way/exercise6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise6/</guid>
-      <description>Exercise 6.1 - Some Background All of that is well and good. However, containers are great because they allow us to package and distribute software. All we&amp;#8217;ve done is isolate some Linux processes. Where&amp;#8217;s the beef?
- Containers get their root filesystem from a container image file. This is typically pulled from a registry. This file is, essentially, a TAR archive with the root filesystem contents and some metadata. Those contents are then made available to the running container through use of an Overlay Filesystem.</description>
+      <description>Exercise 6.1 - Some Background All of that is well and good. However, containers are great because they allow us to package and distribute software. All we’ve done is isolate some Linux processes. Where’s the beef?&#xA;Containers get their root filesystem from a container image file. This is typically pulled from a registry. This file is, essentially, a TAR archive with the root filesystem contents and some metadata. Those contents are then made available to the running container through use of an Overlay Filesystem.</description>
     </item>
-    
     <item>
       <title>Exercise 6 - Import REST data</title>
       <link>/workshops/jdv_dev/exercise6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise6/</guid>
-      <description>Import REST source   file  import  Web Service Source &amp;raquo; Source and View Model (REST)
-  Click New Connection Profile, then next
-  Connection URL https://jsonplaceholder.typicode.com/users
-  Response type JSON
-  Make sure Test Connection returns Ping Succeeded!, then Finish
-    Click Next
-  Set the following values like the screenshot below
-    Next and put JNDI as java:/RestDS, then Next</description>
+      <description>Import REST source file import Web Service Source &amp;raquo; Source and View Model (REST)&#xA;Click New Connection Profile, then next&#xA;Connection URL https://jsonplaceholder.typicode.com/users&#xA;Response type JSON&#xA;Make sure Test Connection returns Ping Succeeded!, then Finish&#xA;Click Next&#xA;Set the following values like the screenshot below&#xA;Next and put JNDI as java:/RestDS, then Next&#xA;In the Import from REST Web Service Source, expand the first response element then right click on the second response element and select Set as Root path</description>
     </item>
-    
     <item>
       <title>Exercise 7 - Container Networking</title>
       <link>/workshops/containers_the_hard_way/exercise7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise7/</guid>
-      <description>Exercise 7.1 - Some Background The Linux Kernel provides many useful primitives that can be used to construct very intricate network configurations. They are very flexible and powerful. Of particular interest today are Virtual Ethernet Adapaters, Bridges, and Taps.
- A Virtual Ethernet Adapater operates in the Kernel exactly the way a physical NIC would. The only difference is that instead of receiving data from a physical device, a virtual adapter recieves data from another network adapter in the stack.</description>
+      <description>Exercise 7.1 - Some Background The Linux Kernel provides many useful primitives that can be used to construct very intricate network configurations. They are very flexible and powerful. Of particular interest today are Virtual Ethernet Adapaters, Bridges, and Taps.&#xA;A Virtual Ethernet Adapater operates in the Kernel exactly the way a physical NIC would. The only difference is that instead of receiving data from a physical device, a virtual adapter recieves data from another network adapter in the stack.</description>
     </item>
-    
     <item>
       <title>Exercise 7 - Import Excel data</title>
       <link>/workshops/jdv_dev/exercise7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise7/</guid>
-      <description>Verify Settings   You need to first verify that the Excel extensions were imported correctly into the designer
-  window  show view  other 
-  Teiid Designer  Model Extension Registry
-   In the Model Extension Registry tab at the bottom, verify in the Namespace Prefix you see the value excel and a checkbox in the imported column. If not, close the designer, re-open, click the start button to mark the server as started, and check again.</description>
+      <description>Verify Settings You need to first verify that the Excel extensions were imported correctly into the designer&#xA;window show view other Teiid Designer Model Extension Registry&#xA;In the Model Extension Registry tab at the bottom, verify in the Namespace Prefix you see the value excel and a checkbox in the imported column. If not, close the designer, re-open, click the start button to mark the server as started, and check again.</description>
     </item>
-    
     <item>
       <title>Exercise 8 - Federate Data</title>
       <link>/workshops/jdv_dev/exercise8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise8/</guid>
-      <description>Create the combined view file -&amp;gt; new -&amp;gt; teiid metadata model
-  Location demo-jdv/federated
-  Model Name FedView
-  Model Type View Model
-  Do not select any options under model builder and click Finish
-  Right-click on the FedView Package diagram and select new -&amp;gt; child -&amp;gt; table
-  Select Option 1: Build with new table wizard
-  Name combined
-   Under the PK tab, check the include box then put id_pk in the name field.</description>
-    </item>
-    
+      <description>Create the combined view file -&amp;gt; new -&amp;gt; teiid metadata model&#xA;Location demo-jdv/federated&#xA;Model Name FedView&#xA;Model Type View Model&#xA;Do not select any options under model builder and click Finish&#xA;Right-click on the FedView Package diagram and select new -&amp;gt; child -&amp;gt; table&#xA;Select Option 1: Build with new table wizard&#xA;Name combined&#xA;Under the PK tab, check the include box then put id_pk in the name field. Click ok.</description>
+    </item>
     <item>
       <title>Exercise 9 - Secure Data Services</title>
       <link>/workshops/jdv_dev/exercise9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise9/</guid>
-      <description>Overview  To secure the services we created in our VDB, we need to create an additional user on the server.  Create the additional user  In $JBOSS_HOME/bin directory run the following script with the answers to the prompts below  ./add-user.sh 
-For windows users, the script will be add-user.bat
-   Type: b) Application User
-  Username: maskUser
-  Password: Password1! (same as the one used during installation</description>
+      <description>Overview To secure the services we created in our VDB, we need to create an additional user on the server. Create the additional user In $JBOSS_HOME/bin directory run the following script with the answers to the prompts below ./add-user.sh For windows users, the script will be add-user.bat&#xA;Type: b) Application User&#xA;Username: maskUser&#xA;Password: Password1! (same as the one used during installation&#xA;groups: odata,mask&#xA;Remoting: no&#xA;Back in JBDS open the demo-jdv.</description>
     </item>
-    
     <item>
       <title>Fin</title>
       <link>/workshops/secure_software_factory/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/fin/</guid>
       <description>That&amp;rsquo;s it! Hopefully, you understand how to build a Trusted Software Supply Chain on OpenShift.</description>
     </item>
-    
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_101_dcmetromap/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.
-Get even deeper While you&amp;rsquo;re here, we can help you install the Container Development Kit (CDK) on your laptop.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.&#xA;Get even deeper While you&amp;rsquo;re here, we can help you install the Container Development Kit (CDK) on your laptop.</description>
     </item>
-    
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_4_101/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.
- OpenShift Architecture OpenShift Developer&amp;rsquo;s Site   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.&#xA;OpenShift Architecture OpenShift Developer&amp;rsquo;s Site &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_4_101_dynatrace/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.
- OpenShift Architecture OpenShift Developer&amp;rsquo;s Site   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.&#xA;OpenShift Architecture OpenShift Developer&amp;rsquo;s Site &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_service_mesh_v1.0/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of why a service mesh is critical when developing and operating microservice applications. Istio is an emerging technology so keep checking the upstream announcements and blog for exciting news.
-Also, release notes are a great place to see changes that occurred between releases. You can find the OpenShift Service Mesh release notes here and the upstream Istio project release notes here.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of why a service mesh is critical when developing and operating microservice applications. Istio is an emerging technology so keep checking the upstream announcements and blog for exciting news.&#xA;Also, release notes are a great place to see changes that occurred between releases. You can find the OpenShift Service Mesh release notes here and the upstream Istio project release notes here.</description>
     </item>
-    
     <item>
       <title>Fin.</title>
       <link>/workshops/rhosp_101/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenStack environment. And hopefully, you have a deeper understanding of how Infrastructure-as-a-Service works.
-Get even deeper Here are some good resources to continue learning OpenStack:
- OpenStack Foundation RDO Project - Our midstream, open source OpenStack distrobution for RHEL variants Red Hat OpenStack Platform Official Docs  There are two ways to get started with RDO: TripleO Quickstart and PackStack</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenStack environment. And hopefully, you have a deeper understanding of how Infrastructure-as-a-Service works.&#xA;Get even deeper Here are some good resources to continue learning OpenStack:&#xA;OpenStack Foundation RDO Project - Our midstream, open source OpenStack distrobution for RHEL variants Red Hat OpenStack Platform Official Docs There are two ways to get started with RDO: TripleO Quickstart and PackStack</description>
     </item>
-    
     <item>
       <title>Intro to Service Mesh - Adding a New Service</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/</guid>
-      <description>Adding a New Service to the Mesh You need to deploy the new user profile application into the service mesh.
-Deploy Application The deployment file &amp;lsquo;userprofile-deploy-all.yaml&amp;rsquo; was created for you to deploy the application. The file creates the user profile service and an accompanying PostgreSQL database. Similar to the other source files, an annotation &amp;lsquo;sidecar.istio.io/inject&amp;rsquo; was added to tell Istio to inject a sidecar proxy and add this to the mesh.</description>
+      <description>Adding a New Service to the Mesh You need to deploy the new user profile application into the service mesh.&#xA;Deploy Application The deployment file &amp;lsquo;userprofile-deploy-all.yaml&amp;rsquo; was created for you to deploy the application. The file creates the user profile service and an accompanying PostgreSQL database. Similar to the other source files, an annotation &amp;lsquo;sidecar.istio.io/inject&amp;rsquo; was added to tell Istio to inject a sidecar proxy and add this to the mesh.</description>
     </item>
-    
     <item>
       <title>Intro to Service Mesh - Building a Microservice</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/</guid>
-      <description>Building a Microservice   In the browser, navigate to the &#39;Profile&#39; section in the header.   If you lost the URL, you can retrieve it via:
-`echo $GATEWAY_URL` You should see the following:
- Unknown Profile Page
-The UI shows an unknown user and that&amp;rsquo;s because there&amp;rsquo;s no profile service for your application. You are going to build a new microservice for user profiles and add this to your service mesh.</description>
+      <description>Building a Microservice In the browser, navigate to the &#39;Profile&#39; section in the header. If you lost the URL, you can retrieve it via:&#xA;`echo $GATEWAY_URL` You should see the following:&#xA;Unknown Profile Page&#xA;The UI shows an unknown user and that&amp;rsquo;s because there&amp;rsquo;s no profile service for your application. You are going to build a new microservice for user profiles and add this to your service mesh.&#xA;Application Code Your new application is written in Java, whereas the other backend components such as &amp;lsquo;app-ui&amp;rsquo; and &amp;lsquo;boards&amp;rsquo; are written in NodeJS.</description>
     </item>
-    
     <item>
       <title>Intro to Service Mesh - Deploying an App</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/</guid>
-      <description>Deploying an App into the Service Mesh It&amp;rsquo;s time to deploy your microservices application. The application you are working on is a paste board application in which users can post comments in shared boards. Here is a diagram of the architecture:
-
-App Architecture
-The microservices include single sign-on (SSO), user interface (UI), the boards application, and the context scraper. In this scenario, you are going to deploy these services and then add a new user profile service.</description>
+      <description>Deploying an App into the Service Mesh It&amp;rsquo;s time to deploy your microservices application. The application you are working on is a paste board application in which users can post comments in shared boards. Here is a diagram of the architecture:&#xA;App Architecture&#xA;The microservices include single sign-on (SSO), user interface (UI), the boards application, and the context scraper. In this scenario, you are going to deploy these services and then add a new user profile service.</description>
     </item>
-    
     <item>
       <title>Introduction</title>
       <link>/workshops/containers_the_hard_way/intro/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/intro/</guid>
-      <description>What is a container? It is a simple question without a simple answer. Search the internet for this question and you&amp;#8217;ll find an endless stream of blog posts explaining how containers differ from virtual machines. That&amp;#8217;s great, but that doesn&amp;#8217;t answer my question. What is a container? Does anybody really understand what is happening on their server what they podman run?
-   By the end of this workshop, you will feel confident answering this question and explaining it to your peers.</description>
+      <description>What is a container? It is a simple question without a simple answer. Search the internet for this question and you’ll find an endless stream of blog posts explaining how containers differ from virtual machines. That’s great, but that doesn’t answer my question. What is a container? Does anybody really understand what is happening on their server what they podman run?&#xA;By the end of this workshop, you will feel confident answering this question and explaining it to your peers.</description>
     </item>
-    
     <item>
       <title>Introduction to Red Hat OpenStack Platform</title>
       <link>/workshops/rhosp_101/1_introduction/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/1_introduction/</guid>
-      <description>Red Hat OpenStack Platform Overview Red Hat OpenStack Platform is implemented as a collection of interacting services that control compute, storage, and networking resources. The following diagram provides a high-level overview of the OpenStack core services.
-  OpenStack Services Overview    Horizon - User interface built to give a graphical way to interact with OpenStack services Keystone - Identity management service for projects, users, groups, roles, endpoints, etc.</description>
+      <description>Red Hat OpenStack Platform Overview Red Hat OpenStack Platform is implemented as a collection of interacting services that control compute, storage, and networking resources. The following diagram provides a high-level overview of the OpenStack core services.&#xA;OpenStack Services Overview Horizon - User interface built to give a graphical way to interact with OpenStack services Keystone - Identity management service for projects, users, groups, roles, endpoints, etc. Neutron - Software defined networking API service that can be backed by different SDN solutions.</description>
     </item>
-    
     <item>
       <title>Key Terms</title>
       <link>/workshops/openshift_4_101/keyterms/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/keyterms/</guid>
-      <description>Key Terms We will be using the following terms throughout the workshop labs; so, here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way; but, these are the basics to get you started.
- Container - Your software wrapped in a complete filesystem containing everything it needs to run Image - We are talking about docker images; read-only and used to create containers Image Stream - An image stream comprises one or more OCI images identified by tags.</description>
+      <description>Key Terms We will be using the following terms throughout the workshop labs; so, here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way; but, these are the basics to get you started.&#xA;Container - Your software wrapped in a complete filesystem containing everything it needs to run Image - We are talking about docker images; read-only and used to create containers Image Stream - An image stream comprises one or more OCI images identified by tags.</description>
     </item>
-    
     <item>
       <title>Lab - Building and Deploying a Fast-Moving Monolith</title>
       <link>/workshops/strangling_the_monolith/lab1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/lab1/</guid>
-      <description>FAST-MOVING MONOLITH  Large organizations have a tremendous amount of resources invested in existing monolith applications Looking for a sane way to capture the benefits of containers and orchestration without having to complete rewrite OpenShift provides the platform for their existing investment with the benefit of a path forward for microservice based apps in the future  FAST-MOVING MONOLITH ADVANTAGES  Easier to develop since all dependencies are included Single code base for teams to work on No API backwards compatibility issues since all logic is packaged with the application Single deployable unit  Step 1  In this lab, the coolstore monolith will be built and deployed to OpenShift from your local workstation demonstrating a typical Java application developer workflow A sample pipeline is included which will be used to deploy across dev and prod environment   First, deploy the coolstore monolith dev project (don’t forget to include -b app-partner when you run git clone - this is the branch in use for this lab!</description>
+      <description>FAST-MOVING MONOLITH Large organizations have a tremendous amount of resources invested in existing monolith applications Looking for a sane way to capture the benefits of containers and orchestration without having to complete rewrite OpenShift provides the platform for their existing investment with the benefit of a path forward for microservice based apps in the future FAST-MOVING MONOLITH ADVANTAGES Easier to develop since all dependencies are included Single code base for teams to work on No API backwards compatibility issues since all logic is packaged with the application Single deployable unit Step 1 In this lab, the coolstore monolith will be built and deployed to OpenShift from your local workstation demonstrating a typical Java application developer workflow A sample pipeline is included which will be used to deploy across dev and prod environment First, deploy the coolstore monolith dev project (don’t forget to include -b app-partner when you run git clone - this is the branch in use for this lab!</description>
     </item>
-    
     <item>
       <title>Lab - Containerize the App</title>
       <link>/workshops/source_to_image/containerize_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/containerize_app/</guid>
-      <description>Introduction Now we want to containerize the Gochat app. If you are using the CLI on your own computer, you could use the docker command. However, if you are in the Wetty terminal, remember you are actually in a container. We could have exposed the container socket on the host to your Wetty container. However, this would break the security model.
-Fortunately we can build from a Dockerfile using the oc command line tool.</description>
+      <description>Introduction Now we want to containerize the Gochat app. If you are using the CLI on your own computer, you could use the docker command. However, if you are in the Wetty terminal, remember you are actually in a container. We could have exposed the container socket on the host to your Wetty container. However, this would break the security model.&#xA;Fortunately we can build from a Dockerfile using the oc command line tool.</description>
     </item>
-    
     <item>
       <title>Lab - Gochat S2I</title>
       <link>/workshops/source_to_image/gochat_s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/gochat_s2i/</guid>
-      <description>Step 1 - Create a New Project Space In the Wetty terminal, create a new project.
-oc new-project gochat-s2i-userYOUR# Step 2 - Create the Golang S2I Builder Image Create a new build for the Golang S2I builder image
-cd ~ oc new-build golang-s2i/ --to=golang-s2i Start the new build for the Golang S2I builder image
-oc start-build golang-s2i --from-dir=golang-s2i/ Step 3 - Import YAML Template in to OpenShift In the OpenShift WebUI, on the catalog page, seclect Import YAML/JSON Import YAML/JSON        Step 4 - Configure the Import Select the project to which you want to import the template</description>
+      <description>Step 1 - Create a New Project Space In the Wetty terminal, create a new project.&#xA;oc new-project gochat-s2i-userYOUR# Step 2 - Create the Golang S2I Builder Image Create a new build for the Golang S2I builder image&#xA;cd ~ oc new-build golang-s2i/ --to=golang-s2i Start the new build for the Golang S2I builder image&#xA;oc start-build golang-s2i --from-dir=golang-s2i/ Step 3 - Import YAML Template in to OpenShift In the OpenShift WebUI, on the catalog page, seclect Import YAML/JSON Import YAML/JSON Step 4 - Configure the Import Select the project to which you want to import the template</description>
     </item>
-    
     <item>
       <title>Lab - Login &amp; Tour of OpenShift</title>
       <link>/workshops/strangling_the_monolith/login_tour_oc/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/login_tour_oc/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift you can skip this lab - after making sure you can login.
-Wetty Environment Links Your instructor will assign you an OpenShift environment and login.
-Please click &amp;ldquo;Return to Workshop&amp;rdquo; above to view the OpenShift Environment Links.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift you can skip this lab - after making sure you can login.&#xA;Wetty Environment Links Your instructor will assign you an OpenShift environment and login.&#xA;Please click &amp;ldquo;Return to Workshop&amp;rdquo; above to view the OpenShift Environment Links.</description>
     </item>
-    
     <item>
       <title>Lab - Login &amp; Tour of Wetty</title>
       <link>/workshops/strangling_the_monolith/login_tour_wetty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/login_tour_wetty/</guid>
-      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for rthe workshopname.
-https://&amp;lt;workshopname&amp;gt;.wetty.redhatgov.io:8888 After logging in, you should see a shell.
-The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
+      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for rthe workshopname.&#xA;https://&amp;lt;workshopname&amp;gt;.wetty.redhatgov.io:8888 After logging in, you should see a shell.&#xA;The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
     </item>
-    
     <item>
       <title>Lab - Microservice Integration Patterns</title>
       <link>/workshops/strangling_the_monolith/lab3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/lab3/</guid>
-      <description>Microservice Integration Patterns  In previous labs, we created two new microservices with the intention of replacing functionality (“strangling”) the monolithic application. Currently no traffic is routed to them. If you were to re-route traffic from the monolith’s /services/products API to the new catalog service’s /services/catalog endpoint, you would be missing the inventory data. In this lab we will consider different options and architectures for integrating the microservices’ functionality into our app.</description>
+      <description>Microservice Integration Patterns In previous labs, we created two new microservices with the intention of replacing functionality (“strangling”) the monolithic application. Currently no traffic is routed to them. If you were to re-route traffic from the monolith’s /services/products API to the new catalog service’s /services/catalog endpoint, you would be missing the inventory data. In this lab we will consider different options and architectures for integrating the microservices’ functionality into our app.</description>
     </item>
-    
     <item>
       <title>Lab - Roll Dice</title>
       <link>/workshops/source_to_image/dice/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/dice/</guid>
-      <description>In an attempt at nostalgia, we are going to once again create an S2I builder, this time for a Fortran app. Yes, Fortran. The objective is to make our little chat program a bit more interesting.
-Step 1 - Create the S2I Project cd ~ s2i create fortran-s2i fortran-s2i Step 2 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/fortran-s2i/Dockerfile vi ~/fortran-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
+      <description>In an attempt at nostalgia, we are going to once again create an S2I builder, this time for a Fortran app. Yes, Fortran. The objective is to make our little chat program a bit more interesting.&#xA;Step 1 - Create the S2I Project cd ~ s2i create fortran-s2i fortran-s2i Step 2 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/fortran-s2i/Dockerfile vi ~/fortran-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
     </item>
-    
     <item>
       <title>Lab - Run the App</title>
       <link>/workshops/source_to_image/run_the_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/run_the_app/</guid>
-      <description>Step 1 - Create a Route to the Gochat Service First we expose the pod with a service.
-oc expose dc wetty --port=8080 --target-port=8080 --name=gochat Then we expose the service with a route.
-oc expose svc gochat Step 2 - Download the App Source go get -d github.com/kevensen/openshift-gochat-client Step 3 - Build the App cd go/src/github.com/kevensen/openshift-gochat-client glide install -v &amp;amp;&amp;amp; go install Step 4 - Annotate the Service Account to Use OpenShift Authorization These annotations allow for the Gochat Client to communicate to the OpenShift API for user credential verification.</description>
+      <description>Step 1 - Create a Route to the Gochat Service First we expose the pod with a service.&#xA;oc expose dc wetty --port=8080 --target-port=8080 --name=gochat Then we expose the service with a route.&#xA;oc expose svc gochat Step 2 - Download the App Source go get -d github.com/kevensen/openshift-gochat-client Step 3 - Build the App cd go/src/github.com/kevensen/openshift-gochat-client glide install -v &amp;amp;&amp;amp; go install Step 4 - Annotate the Service Account to Use OpenShift Authorization These annotations allow for the Gochat Client to communicate to the OpenShift API for user credential verification.</description>
     </item>
-    
     <item>
       <title>Lab - Source-to-Image</title>
       <link>/workshops/source_to_image/source_to_image/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/source_to_image/</guid>
-      <description>Step 1 - Create a new Project Space In the Wetty terminal, create a new project.
-oc new-project s2i-userYOUR# Step 2 - Go Get S2I Library cd ~ go get github.com/openshift/source-to-image Step 3 - Build the S2I Tooling cd $GOPATH/src/github.com/openshift/source-to-image hack/build-go.sh export PATH=$PATH:${GOPATH}/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64/ Step 4 - Create the S2I Project cd ~ s2i create golang-s2i golang-s2i Now let&amp;rsquo;s inspect the project directory
-tree -a golang-s2i Step 5 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/golang-s2i/Dockerfile vi ~/golang-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
+      <description>Step 1 - Create a new Project Space In the Wetty terminal, create a new project.&#xA;oc new-project s2i-userYOUR# Step 2 - Go Get S2I Library cd ~ go get github.com/openshift/source-to-image Step 3 - Build the S2I Tooling cd $GOPATH/src/github.com/openshift/source-to-image hack/build-go.sh export PATH=$PATH:${GOPATH}/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64/ Step 4 - Create the S2I Project cd ~ s2i create golang-s2i golang-s2i Now let&amp;rsquo;s inspect the project directory&#xA;tree -a golang-s2i Step 5 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/golang-s2i/Dockerfile vi ~/golang-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
     </item>
-    
     <item>
       <title>Lab - Strangle Your Monolith</title>
       <link>/workshops/strangling_the_monolith/lab2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/lab2/</guid>
-      <description>Strangling the Monolith Design Pattern  Strangling - incrementally replacing functionality in app with something better (cheaper, faster, easier to maintain). As functionality is replaced, “dead” parts of monolith can be removed/retired. You can also wait for all functionality to be replaced before retiring anything! You can optionally include new functionality during strangulation to make it more attractive to business stakeholders.  
-https://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/
- Steps for Strangling the Monolith   Strangle Monolith   Strangle Monolith         Add a Microservice   Add a Microservice         And Another   And Another         Squeeze Monolith   Squeeze Monolith         And Remove Dead   And Remove Dead        Step 1  In this lab, you will begin to ‘strangle’ the coolstore monolith by implementing two of its services as external microservices, split along business boundaries Once implemented, traffic destined to the original monolith’s services will be redirected (via OpenShift software-defined routing) to the new services We will be using the Fabric8 Maven Plugin to automatically deploy to openshift    First, build and deploy the catalog microservice (Based on Spring Boot)   $ cd ~/coolstore $ git clone -b app-partner https://github.</description>
+      <description>Strangling the Monolith Design Pattern Strangling - incrementally replacing functionality in app with something better (cheaper, faster, easier to maintain). As functionality is replaced, “dead” parts of monolith can be removed/retired. You can also wait for all functionality to be replaced before retiring anything! You can optionally include new functionality during strangulation to make it more attractive to business stakeholders. https://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/&#xA;Steps for Strangling the Monolith Strangle Monolith Strangle Monolith Add a Microservice Add a Microservice And Another And Another Squeeze Monolith Squeeze Monolith And Remove Dead And Remove Dead Step 1 In this lab, you will begin to ‘strangle’ the coolstore monolith by implementing two of its services as external microservices, split along business boundaries Once implemented, traffic destined to the original monolith’s services will be redirected (via OpenShift software-defined routing) to the new services We will be using the Fabric8 Maven Plugin to automatically deploy to openshift First, build and deploy the catalog microservice (Based on Spring Boot) $ cd ~/coolstore $ git clone -b app-partner https://github.</description>
     </item>
-    
     <item>
       <title>Lab 01 - API Design</title>
       <link>/workshops/agile_integrations_ci/lab01/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab01/</guid>
-      <description>Lab 1 API Design Create an OpenAPI Specification using Apicurio Studio  Duration: 10 mins Audience: API Owner, Product Manager, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
+      <description>Lab 1 API Design Create an OpenAPI Specification using Apicurio Studio Duration: 10 mins Audience: API Owner, Product Manager, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
     </item>
-    
     <item>
       <title>Lab 01 - API Design</title>
       <link>/workshops/agile_integrations_dev/lab01/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab01/</guid>
-      <description>Lab 1 API Design Import an OpenAPI Specification using Apicurio Studio  Duration: 10 mins Audience: Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
+      <description>Lab 1 API Design Import an OpenAPI Specification using Apicurio Studio Duration: 10 mins Audience: Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
     </item>
-    
     <item>
       <title>Lab 01 - Welcome to OpenShift</title>
       <link>/workshops/secure_software_factory/lab01/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab01/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
     </item>
-    
     <item>
       <title>Lab 02 - API Mocking</title>
       <link>/workshops/agile_integrations_ci/lab02/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab02/</guid>
-      <description>Lab 2 API Mocking Bring your APIs to life  Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers  
-&amp;lt;img src=&amp;rdquo;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
+      <description>Lab 2 API Mocking Bring your APIs to life Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers &amp;lt;img src=&amp;quot;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
     </item>
-    
     <item>
       <title>Lab 02 - API Mocking</title>
       <link>/workshops/agile_integrations_dev/lab02/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab02/</guid>
-      <description>Lab 2 API Mocking Bring your APIs to life  Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers  
-&amp;lt;img src=&amp;rdquo;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
+      <description>Lab 2 API Mocking Bring your APIs to life Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers &amp;lt;img src=&amp;quot;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
     </item>
-    
     <item>
       <title>Lab 02 - Trusted Software Supply Chain</title>
       <link>/workshops/secure_software_factory/lab02/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab02/</guid>
-      <description>Trusted Software Supply Chain The notion of Trusted Software Supply Chain is that of applying an assembly line approach to software that includes building increasing levels of assurance before marking an artifact as ready to deploy to production.
-In this workshop, you will use build orchestration tools such as Jenkins, Kubernetes, and OpenShift to support implementing and integrating continuous delivery (CD) as the foundation of automating the various stages of the deployment lifecycle are represented – from development, multiple types of testing, user acceptance, staging, to production release.</description>
+      <description>Trusted Software Supply Chain The notion of Trusted Software Supply Chain is that of applying an assembly line approach to software that includes building increasing levels of assurance before marking an artifact as ready to deploy to production.&#xA;In this workshop, you will use build orchestration tools such as Jenkins, Kubernetes, and OpenShift to support implementing and integrating continuous delivery (CD) as the foundation of automating the various stages of the deployment lifecycle are represented – from development, multiple types of testing, user acceptance, staging, to production release.</description>
     </item>
-    
     <item>
       <title>Lab 03 - CI/CD Project and Pods</title>
       <link>/workshops/secure_software_factory/lab03/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab03/</guid>
-      <description>Before moving forward, it is important to understand the difference between Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment.
-Also, a part of this lab we’ll be using using Pipelines in OpenShift for CI/CD, which gives you control over building, deploying, and promoting your applications on OpenShift. Using a combination of the Jenkins Pipeline Build Strategy, Jenkinsfiles, and the OpenShift Domain Specific Language (DSL) (provided by the OpenShift Jenkins Client Plug-in), you can create advanced build, test, deploy, and promote pipelines for any scenario.</description>
+      <description>Before moving forward, it is important to understand the difference between Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment.&#xA;Also, a part of this lab we’ll be using using Pipelines in OpenShift for CI/CD, which gives you control over building, deploying, and promoting your applications on OpenShift. Using a combination of the Jenkins Pipeline Build Strategy, Jenkinsfiles, and the OpenShift Domain Specific Language (DSL) (provided by the OpenShift Jenkins Client Plug-in), you can create advanced build, test, deploy, and promote pipelines for any scenario.</description>
     </item>
-    
     <item>
       <title>Lab 03 - Fuse Online</title>
       <link>/workshops/agile_integrations_ci/lab03/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab03/</guid>
-      <description>Lab 3 Fuse Online  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop and deploy the APIs. Here is how to create a simple API with Fuse Online.
-Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
+      <description>Lab 3 Fuse Online Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop and deploy the APIs. Here is how to create a simple API with Fuse Online.&#xA;Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
     </item>
-    
     <item>
       <title>Lab 03 - Swagger to REST</title>
       <link>/workshops/agile_integrations_dev/lab03/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab03/</guid>
-      <description>Lab 3 Swagger to REST Contract-first API development with a database interface, implemented using Eclipse Che  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview In the context of defining API&amp;rsquo;s, it&amp;rsquo;s common for a Business Analyst (or Citizen Integrator) to first create an API specification or contract. By beginning the process with a clearly defined contract, a Developer can easily take the contract and auto-generate the underlying service to implement that API.</description>
+      <description>Lab 3 Swagger to REST Contract-first API development with a database interface, implemented using Eclipse Che Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview In the context of defining API&amp;rsquo;s, it&amp;rsquo;s common for a Business Analyst (or Citizen Integrator) to first create an API specification or contract. By beginning the process with a clearly defined contract, a Developer can easily take the contract and auto-generate the underlying service to implement that API.</description>
     </item>
-    
     <item>
       <title>Lab 04 - Jenkins and OpenShift</title>
       <link>/workshops/secure_software_factory/lab04/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab04/</guid>
-      <description>Jenkins can be integrated with OpenShift in 3 ways. Today, you&amp;rsquo;ll be working with a containerized Jenkins Server that&amp;rsquo;s fully integrated with OpenShift.
-Login through SSO with Jenkins Go into your CI/CD project and find the running Jenkins Pod.
-Click the external route (https://jenkins…) to go into your Jenkins Server
-Click Login with OpenShift.
-Login with your OpenShift Credentials. You maybe asked to accept authorizations. Go ahead and do so and re-login.</description>
+      <description>Jenkins can be integrated with OpenShift in 3 ways. Today, you&amp;rsquo;ll be working with a containerized Jenkins Server that&amp;rsquo;s fully integrated with OpenShift.&#xA;Login through SSO with Jenkins Go into your CI/CD project and find the running Jenkins Pod.&#xA;Click the external route (https://jenkins…) to go into your Jenkins Server&#xA;Click Login with OpenShift.&#xA;Login with your OpenShift Credentials. You maybe asked to accept authorizations. Go ahead and do so and re-login.</description>
     </item>
-    
     <item>
       <title>Lab 04 - Managing API Endpoints</title>
       <link>/workshops/agile_integrations_ci/lab04/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab04/</guid>
-      <description>Lab 4 Managing API Endpoints Take control of your APIs  Duration: 15 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them, and for what purpose. You also need to begin to track usage of these different users to know who is or is not succeeding in their usage.</description>
+      <description>Lab 4 Managing API Endpoints Take control of your APIs Duration: 15 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them, and for what purpose. You also need to begin to track usage of these different users to know who is or is not succeeding in their usage.</description>
     </item>
-    
     <item>
       <title>Lab 04 - SOAP to REST (Optional)</title>
       <link>/workshops/agile_integrations_dev/lab04/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab04/</guid>
-      <description>Lab 4 SOAP to REST (Optional) Contract-first API development wrapping an existing SOAP service, implemented using Eclipse Che  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Another important use case in developing API&amp;rsquo;s is to take an existing legacy SOAP service and wrap it with a new RESTful endpoint. This SOAP to REST transformation is implemented in the API service layer (Fuse). This lab will walk you through taking an existing SOAP contract (WSDL), converting it to Java POJO&amp;rsquo;s and exposing it using Camel REST DSL.</description>
+      <description>Lab 4 SOAP to REST (Optional) Contract-first API development wrapping an existing SOAP service, implemented using Eclipse Che Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Another important use case in developing API&amp;rsquo;s is to take an existing legacy SOAP service and wrap it with a new RESTful endpoint. This SOAP to REST transformation is implemented in the API service layer (Fuse). This lab will walk you through taking an existing SOAP contract (WSDL), converting it to Java POJO&amp;rsquo;s and exposing it using Camel REST DSL.</description>
     </item>
-    
     <item>
       <title>Lab 05 - API Security</title>
       <link>/workshops/agile_integrations_ci/lab05/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab05/</guid>
-      <description>Lab 5 API Security Securing APIs with OpenID Connect and Red Hat Single Sign On  Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Once you have APIs in your organization and have applications being written, you also want to be sure in many cases that the various types of users of the APIs are correctly authenticated. In this lab you will discover how to set up the widely used OpenID connect pattern for Authentication.</description>
+      <description>Lab 5 API Security Securing APIs with OpenID Connect and Red Hat Single Sign On Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Once you have APIs in your organization and have applications being written, you also want to be sure in many cases that the various types of users of the APIs are correctly authenticated. In this lab you will discover how to set up the widely used OpenID connect pattern for Authentication.</description>
     </item>
-    
     <item>
       <title>Lab 05 - Creating Your Pipeline</title>
       <link>/workshops/secure_software_factory/lab05/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab05/</guid>
-      <description>Today, you will be building your Trusted Software Supply Chain using a Jenkins Pipeline that is integrated with OpenShift.
-In addition to standard Jenkins Pipeline Syntax, the OpenShift Jenkins image provides the OpenShift Domain Specific Language (DSL) (through the OpenShift Jenkins Client Plug-in), which aims to provide a readable, concise, comprehensive, and fluent syntax for rich interactions with an OpenShift API server, allowing for even more control over the build, deployment, and promotion of applications on your OpenShift cluster.</description>
+      <description>Today, you will be building your Trusted Software Supply Chain using a Jenkins Pipeline that is integrated with OpenShift.&#xA;In addition to standard Jenkins Pipeline Syntax, the OpenShift Jenkins image provides the OpenShift Domain Specific Language (DSL) (through the OpenShift Jenkins Client Plug-in), which aims to provide a readable, concise, comprehensive, and fluent syntax for rich interactions with an OpenShift API server, allowing for even more control over the build, deployment, and promotion of applications on your OpenShift cluster.</description>
     </item>
-    
     <item>
       <title>Lab 05 - Fuse Online</title>
       <link>/workshops/agile_integrations_dev/lab05/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab05/</guid>
-      <description>Lab 5 Fuse Online  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop, deploy the APIs. Here is how to create a simple API with Fuse online.
-Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
+      <description>Lab 5 Fuse Online Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop, deploy the APIs. Here is how to create a simple API with Fuse online.&#xA;Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
     </item>
-    
     <item>
       <title>Lab 06 - API Developer Portal</title>
       <link>/workshops/agile_integrations_ci/lab06/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab06/</guid>
-      <description>Lab 6 API Developer Portal Publishing APIs to Developer Portal  Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview The focal point of your developers experience is the API developer portal, and the level of effort you put into it will directly correlate to the level of success of your API program, and API developer engagement.
-Why Red Hat? Red Hat 3scale API Management Solution provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions, and help increase API adoption.</description>
+      <description>Lab 6 API Developer Portal Publishing APIs to Developer Portal Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview The focal point of your developers experience is the API developer portal, and the level of effort you put into it will directly correlate to the level of success of your API program, and API developer engagement.&#xA;Why Red Hat? Red Hat 3scale API Management Solution provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions, and help increase API adoption.</description>
     </item>
-    
     <item>
       <title>Lab 06 - Build App Stage</title>
       <link>/workshops/secure_software_factory/lab06/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab06/</guid>
-      <description>Add Build App Stage to Pipeline Text File Next, you will add the Build App Stage to your pipeline.
-The git branch step will clone the openshift-tasks project with the git branch locally from your gogs server to your jenkins node. The jenkins node is leveraging the git jenkins plugin to communicate to gogs.
-Please note that we are leveraging the eap-7 branch in our git project and not the master branch.</description>
+      <description>Add Build App Stage to Pipeline Text File Next, you will add the Build App Stage to your pipeline.&#xA;The git branch step will clone the openshift-tasks project with the git branch locally from your gogs server to your jenkins node. The jenkins node is leveraging the git jenkins plugin to communicate to gogs.&#xA;Please note that we are leveraging the eap-7 branch in our git project and not the master branch.</description>
     </item>
-    
     <item>
       <title>Lab 06 - Managed API Endpoints</title>
       <link>/workshops/agile_integrations_dev/lab06/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab06/</guid>
-      <description>Lab 6 Managed API Endpoints Take control of your APIs  Duration: 5 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them and for what purpose. You also need to begin to track usage of these different users to know who is/is not succeeding in their usage.</description>
+      <description>Lab 6 Managed API Endpoints Take control of your APIs Duration: 5 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them and for what purpose. You also need to begin to track usage of these different users to know who is/is not succeeding in their usage. For this reason in this lab you will be adding management capabilities to the API to give you control and visibility of it&amp;rsquo;s usage.</description>
     </item>
-    
     <item>
       <title>Lab 07 - API Developer Portal</title>
       <link>/workshops/agile_integrations_dev/lab07/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab07/</guid>
-      <description>Lab 7 API Developer Portal Publishing APIs to Developer Portal  Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview The focal point of your developers’ experience is the API developer portal, and the level of effort you put into it will determine the level of decreased support costs and increased developer engagement.
-Why Red Hat? 3scale provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions and increase API adoption.</description>
+      <description>Lab 7 API Developer Portal Publishing APIs to Developer Portal Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview The focal point of your developers’ experience is the API developer portal, and the level of effort you put into it will determine the level of decreased support costs and increased developer engagement.&#xA;Why Red Hat? 3scale provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions and increase API adoption.</description>
     </item>
-    
     <item>
       <title>Lab 07 - Test Stage</title>
       <link>/workshops/secure_software_factory/lab07/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab07/</guid>
-      <description>Add Test Stage Add the configuration for the Test Stage below to your pipeline text file.
-Maven will run the test stage in the life cycle that we skipped at the previous stages.
-Maven will place the test results in the surefire-reports folder. The maven surefire-reports plugin allows for the generation of reports for your unit tests.
-Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
+      <description>Add Test Stage Add the configuration for the Test Stage below to your pipeline text file.&#xA;Maven will run the test stage in the life cycle that we skipped at the previous stages.&#xA;Maven will place the test results in the surefire-reports folder. The maven surefire-reports plugin allows for the generation of reports for your unit tests.&#xA;Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
     </item>
-    
     <item>
       <title>Lab 07 - Testing Your Application</title>
       <link>/workshops/agile_integrations_ci/lab07/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab07/</guid>
-      <description>Lab 7 Testing the International Inc. Locations webpage Testing your web application  Duration: 10 mins Audience: API Consumers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview This lab demonstrates the International Inc. Locations page using our newly authenticated locations API.
-Why Red Hat? Applications can be built from many technologies. In this case we use a simple web application, but a wide range of Red Hat and non-Red Hat technologies could be used.</description>
+      <description>Lab 7 Testing the International Inc. Locations webpage Testing your web application Duration: 10 mins Audience: API Consumers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview This lab demonstrates the International Inc. Locations page using our newly authenticated locations API.&#xA;Why Red Hat? Applications can be built from many technologies. In this case we use a simple web application, but a wide range of Red Hat and non-Red Hat technologies could be used.</description>
     </item>
-    
     <item>
       <title>Lab 08 - API Consumption</title>
       <link>/workshops/agile_integrations_dev/lab08/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab08/</guid>
-      <description>Lab 8 API Consumption Connect Applications and APIs  Duration: 15 mins Audience: API Consumers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview APIs provide the building blocks for applications, but it is applications which deliver functionality to the end users. hence to see APIs in action it helps to see how applications can call APIs to provide new functionality. In this lab you&amp;rsquo;ll be able to create a simple web application which consumes the API you built earlier in the exercises.</description>
+      <description>Lab 8 API Consumption Connect Applications and APIs Duration: 15 mins Audience: API Consumers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview APIs provide the building blocks for applications, but it is applications which deliver functionality to the end users. hence to see APIs in action it helps to see how applications can call APIs to provide new functionality. In this lab you&amp;rsquo;ll be able to create a simple web application which consumes the API you built earlier in the exercises.</description>
     </item>
-    
     <item>
       <title>Lab 08 - Static Application Security Testing</title>
       <link>/workshops/secure_software_factory/lab08/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab08/</guid>
-      <description>Static Application Security Testing Next we will add a Code Analysis Stage into the pipeline.
-We will leverage the Maven Sonar plugin to run SonarQube scanning against our source code.
-SonarQube is an open source static code analysis tool that we can use to automate running security scans against your source code to further improve the security of your application. Every time you check-in code, SonarQube will scan the quality and perform a threat analysis of that code.</description>
+      <description>Static Application Security Testing Next we will add a Code Analysis Stage into the pipeline.&#xA;We will leverage the Maven Sonar plugin to run SonarQube scanning against our source code.&#xA;SonarQube is an open source static code analysis tool that we can use to automate running security scans against your source code to further improve the security of your application. Every time you check-in code, SonarQube will scan the quality and perform a threat analysis of that code.</description>
     </item>
-    
     <item>
       <title>Lab 09 - Archive App</title>
       <link>/workshops/secure_software_factory/lab09/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab09/</guid>
-      <description>Add Archive Stage Archiving the built and tested application into a trusted repository is important to making sure you are building with trusted parts. You assume this application is built properly and all the previous stages have passed. With that confidence, your built and tested application should be immutable in a trusted repository. The repository will version or audit any changes to the application, configuration, and dependencies.
-Add Archive Stage Steps into your pipeline.</description>
+      <description>Add Archive Stage Archiving the built and tested application into a trusted repository is important to making sure you are building with trusted parts. You assume this application is built properly and all the previous stages have passed. With that confidence, your built and tested application should be immutable in a trusted repository. The repository will version or audit any changes to the application, configuration, and dependencies.&#xA;Add Archive Stage Steps into your pipeline.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Login to Horizon</title>
       <link>/workshops/rhosp_101/2_login_to_horizon/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/2_login_to_horizon/</guid>
-      <description>Welcome to Red Hat OpenStack Platform (RHOSP)! This lab provides a quick tour of the Horizon dashboard to help you get familiar with the user interface. If you are already familiar with the basics of Horizon simply ensure you can login and have access to your student project.
-Accessing Horizon RHOSP provides a web dashboard that allows you to perform various tasks via a web browser. Let&amp;rsquo;s get started by logging into Horizon and checking the status of the platform.</description>
+      <description>Welcome to Red Hat OpenStack Platform (RHOSP)! This lab provides a quick tour of the Horizon dashboard to help you get familiar with the user interface. If you are already familiar with the basics of Horizon simply ensure you can login and have access to your student project.&#xA;Accessing Horizon RHOSP provides a web dashboard that allows you to perform various tasks via a web browser. Let&amp;rsquo;s get started by logging into Horizon and checking the status of the platform.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Welcome</title>
       <link>/workshops/openshift_101_dcmetromap/lab1-welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab1-welcome/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Welcome</title>
       <link>/workshops/openshift_4_101/lab1-welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab1-welcome/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the OpenShift console to help you get familiar with the user interface. If you are already familiar with the basics of OpenShift, this will be easy in that we are simply ensuring you can login and create a project.
-Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.
-Let&amp;rsquo;s Login to the Web Console  Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the OpenShift console to help you get familiar with the user interface. If you are already familiar with the basics of OpenShift, this will be easy in that we are simply ensuring you can login and create a project.&#xA;Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.&#xA;Let&amp;rsquo;s Login to the Web Console Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Welcome</title>
       <link>/workshops/openshift_4_101_dynatrace/lab1-welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab1-welcome/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
     </item>
-    
     <item>
       <title>Lab 1.0 - Workshop introduction</title>
       <link>/workshops/security_container_intro/lab01-intro/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab01-intro/</guid>
-      <description>Table of Contents Important Conventions used in this lab Getting access to the servers     This lab session is a low-level, hands-on introduction to container security using the container tools included with Red Hat Enterprise Linux 8. It is intended to be consumed as a series of self paced exercises.
- Prerequisites   An introductory knowledge of Linux and containers is helpful.
-  Basic text editing skills using vim or nano.</description>
+      <description>This lab session is a low-level, hands-on introduction to container security using the container tools included with Red Hat Enterprise Linux 8. It is intended to be consumed as a series of self paced exercises.&#xA;Prerequisites An introductory knowledge of Linux and containers is helpful.&#xA;Basic text editing skills using vim or nano.&#xA;Lab Environment&#xA;Figure 1. Lab Environment Table 1. Lab Resources Server Function bastion&#xA;External ssh and container host</description>
     </item>
-    
     <item>
       <title>Lab 10 - Create Image Builder</title>
       <link>/workshops/secure_software_factory/lab10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab10/</guid>
-      <description>Containers Containers are an important foundation for your application in building a Trusted Software Supply Chain. You want a secure and blessed golden container image that your application will inherit security controls from.
-Containers are built using a layered approach. For example, to create a container of a Java web application, you could do so in multiple layers: the OS, the JVM, the web server, and the code itself.
-We can incorporate CVE and vulnerability scanning against images in an automated fashion.</description>
+      <description>Containers Containers are an important foundation for your application in building a Trusted Software Supply Chain. You want a secure and blessed golden container image that your application will inherit security controls from.&#xA;Containers are built using a layered approach. For example, to create a container of a Java web application, you could do so in multiple layers: the OS, the JVM, the web server, and the code itself.&#xA;We can incorporate CVE and vulnerability scanning against images in an automated fashion.</description>
     </item>
-    
     <item>
       <title>Lab 10 - Labels (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab10-labels/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab10-labels/</guid>
-      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.
-For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.
-Labels on a pod In a previous lab we added our web app using a S2I template.</description>
+      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.&#xA;For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.&#xA;Labels on a pod In a previous lab we added our web app using a S2I template.</description>
     </item>
-    
     <item>
       <title>Lab 11 - Build Image</title>
       <link>/workshops/secure_software_factory/lab11/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab11/</guid>
-      <description>Add Build Image Stage Add the Build Image Stage into your pipeline.
-The &amp;ldquo;sh&amp;rdquo; are shell commands in your pipeline that are executed on the Jenkins Slave. Maven built the openshift-tasks.war in it the target directory and it will be copied into the created oc-builds directory.
-The startBuild stage is kicked off from Openshift and pointing to the local directory &amp;ldquo;oc-build&amp;rdquo; on the Jenkins slave.
-# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
+      <description>Add Build Image Stage Add the Build Image Stage into your pipeline.&#xA;The &amp;ldquo;sh&amp;rdquo; are shell commands in your pipeline that are executed on the Jenkins Slave. Maven built the openshift-tasks.war in it the target directory and it will be copied into the created oc-builds directory.&#xA;The startBuild stage is kicked off from Openshift and pointing to the local directory &amp;ldquo;oc-build&amp;rdquo; on the Jenkins slave.&#xA;# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
     </item>
-    
     <item>
       <title>Lab 11 - Webhooks and Rollbacks (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab11-cicd/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab11-cicd/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 12 - Blue | Green Deployment (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab12-bluegreen/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab12-bluegreen/</guid>
       <description>Blue/Green deployments When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments. It addresses the desire to minimize downtime during the release of a new version of an application to production. Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified. Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.</description>
     </item>
-    
     <item>
       <title>Lab 12 - Create and Deploy to Dev</title>
       <link>/workshops/secure_software_factory/lab12/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab12/</guid>
-      <description>Add Create Dev Stage Add Create Dev Stage into the pipeline.
-We first check if an deployment config for the Dev Project already exists. If it does not exists, a new application is created and deployment config is defined for the Dev Project.
-Before a trigger is created, the pipeline sleeps for 10 seconds. A deployment configuration can contain triggers, which drive the creation of new deployment processes in response to events inside the cluster.</description>
+      <description>Add Create Dev Stage Add Create Dev Stage into the pipeline.&#xA;We first check if an deployment config for the Dev Project already exists. If it does not exists, a new application is created and deployment config is defined for the Dev Project.&#xA;Before a trigger is created, the pipeline sleeps for 10 seconds. A deployment configuration can contain triggers, which drive the creation of new deployment processes in response to events inside the cluster.</description>
     </item>
-    
     <item>
       <title>Lab 13 - Promote and Deploy to Stage</title>
       <link>/workshops/secure_software_factory/lab13/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab13/</guid>
-      <description>Add Promote to Stage Enter the Promote to STAGE below into your pipeline.
-We set an approval to promote to the application to the Stage Project. The approval process is a good feature for various gates of your deployments. We also set a 15 minute timeout on the approval. You also tag the tasks image with latest and the version from the pom file.
-# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
+      <description>Add Promote to Stage Enter the Promote to STAGE below into your pipeline.&#xA;We set an approval to promote to the application to the Stage Project. The approval process is a good feature for various gates of your deployments. We also set a 15 minute timeout on the approval. You also tag the tasks image with latest and the version from the pom file.&#xA;# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
     </item>
-    
     <item>
       <title>Lab 14 - Run Pipeline</title>
       <link>/workshops/secure_software_factory/lab14/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab14/</guid>
-      <description>Verify Completed Pipeline Before we kick off your pipeline, let&amp;rsquo;s verify it.
-In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit YAML
-Take a look and see if it matches the below text. If not, please correct it.
-apiVersion: v1 kind: BuildConfig metadata: annotations: pipeline.alpha.openshift.io/uses: &#39;[{&amp;quot;name&amp;quot;: &amp;quot;jenkins&amp;quot;, &amp;quot;namespace&amp;quot;: &amp;quot;&amp;quot;, &amp;quot;kind&amp;quot;: &amp;quot;DeploymentConfig&amp;quot;}]&#39; labels: app: cicd-pipeline name: cicd-pipeline name: tasks-pipeline spec: triggers: - type: GitHub github: secret: &amp;quot;secret101&amp;quot; - type: Generic generic: secret: &amp;quot;secret101&amp;quot; runPolicy: Serial source: type: None strategy: jenkinsPipelineStrategy: env: - name: DEV_PROJECT value: dev-userYOUR# - name: STAGE_PROJECT value: stage-userYOUR# jenkinsfile: |- def version, mvnCmd = &amp;quot;mvn -s configuration/cicd-settings-nexus3.</description>
+      <description>Verify Completed Pipeline Before we kick off your pipeline, let&amp;rsquo;s verify it.&#xA;In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit YAML&#xA;Take a look and see if it matches the below text. If not, please correct it.&#xA;apiVersion: v1 kind: BuildConfig metadata: annotations: pipeline.alpha.openshift.io/uses: &amp;#39;[{&amp;#34;name&amp;#34;: &amp;#34;jenkins&amp;#34;, &amp;#34;namespace&amp;#34;: &amp;#34;&amp;#34;, &amp;#34;kind&amp;#34;: &amp;#34;DeploymentConfig&amp;#34;}]&amp;#39; labels: app: cicd-pipeline name: cicd-pipeline name: tasks-pipeline spec: triggers: - type: GitHub github: secret: &amp;#34;secret101&amp;#34; - type: Generic generic: secret: &amp;#34;secret101&amp;#34; runPolicy: Serial source: type: None strategy: jenkinsPipelineStrategy: env: - name: DEV_PROJECT value: dev-userYOUR# - name: STAGE_PROJECT value: stage-userYOUR# jenkinsfile: |- def version, mvnCmd = &amp;#34;mvn -s configuration/cicd-settings-nexus3.</description>
     </item>
-    
     <item>
       <title>Lab 15 - Trigger the Software Supply Chain</title>
       <link>/workshops/secure_software_factory/lab15/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab15/</guid>
-      <description>Trigger the Trusted Software Supply Chain with Code Check-ins Through automation, you will trigger the Trusted Software Supply Chain with code check-ins.
-Verify Webhook in Gogs The Webhook is what triggers your pipeline upon code check-ins. You want your SCM to trigger the pipeline as opposed to Jenkins constantly polling the source code for changes.
-Click on the Gogs route url in the CI/CD project which takes you to the home page.</description>
+      <description>Trigger the Trusted Software Supply Chain with Code Check-ins Through automation, you will trigger the Trusted Software Supply Chain with code check-ins.&#xA;Verify Webhook in Gogs The Webhook is what triggers your pipeline upon code check-ins. You want your SCM to trigger the pipeline as opposed to Jenkins constantly polling the source code for changes.&#xA;Click on the Gogs route url in the CI/CD project which takes you to the home page.</description>
     </item>
-    
     <item>
       <title>Lab 16 - Create Quay Account</title>
       <link>/workshops/secure_software_factory/lab16/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab16/</guid>
-      <description>Create Quay Account Please go to the Quay Login with the link given to you by your instructor
-Click Create Account at the bottom of the page.
-
-Fill in the account information for Quay.
- Username: your assigned username i.e userYOUR# E-mail address: your email address Password: openshift Confirm Password: openshift  Click Create Account
-
- .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Create Quay Account Please go to the Quay Login with the link given to you by your instructor&#xA;Click Create Account at the bottom of the page.&#xA;Fill in the account information for Quay.&#xA;Username: your assigned username i.e userYOUR# E-mail address: your email address Password: openshift Confirm Password: openshift Click Create Account&#xA;&amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Lab 17 - Clair Vulnerability Scan</title>
       <link>/workshops/secure_software_factory/lab17/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab17/</guid>
-      <description>Add Clair Container Scan Add the configuration for the Container Vulnerability Scan below to your pipeline text file.
-
-Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit
-In your pipeline, add and update the following variables after the version and mvnCmd definitions. Please fill in the values between the quotes.
- ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor quayuser : the quay user you created previously quaypass : the quay password you created previously quayrepo : the quay repo you will push your app image to i.</description>
+      <description>Add Clair Container Scan Add the configuration for the Container Vulnerability Scan below to your pipeline text file.&#xA;Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit&#xA;In your pipeline, add and update the following variables after the version and mvnCmd definitions. Please fill in the values between the quotes.&#xA;ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor quayuser : the quay user you created previously quaypass : the quay password you created previously quayrepo : the quay repo you will push your app image to i.</description>
     </item>
-    
     <item>
       <title>Lab 18 - OpenSCAP DISA STIG Scan</title>
       <link>/workshops/secure_software_factory/lab18/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab18/</guid>
-      <description>Add OpenSCAP DISA STIG Scan Add the configuration for the OpenSCAP Scan below to your pipeline text file.
-
-Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit
-In your pipeline, verify the following variables are there after the version and mvnCmd definitions. Please fill in the values between the quotes if not done previously.
- ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor  def ocuser = &amp;quot; &amp;quot; def ocpass = &amp;quot; &amp;quot; def ocp = &amp;quot; &amp;quot; For Example:</description>
+      <description>Add OpenSCAP DISA STIG Scan Add the configuration for the OpenSCAP Scan below to your pipeline text file.&#xA;Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit&#xA;In your pipeline, verify the following variables are there after the version and mvnCmd definitions. Please fill in the values between the quotes if not done previously.&#xA;ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor def ocuser = &amp;#34; &amp;#34; def ocpass = &amp;#34; &amp;#34; def ocp = &amp;#34; &amp;#34; For Example:</description>
     </item>
-    
     <item>
       <title>Lab 2 - BYO Container</title>
       <link>/workshops/openshift_4_101/lab2-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab2-byocontainer/</guid>
-      <description>Bring your own OCI image It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image.
-Let&amp;rsquo;s point OpenShift to an existing built container image Choose either to complete the steps via CLI or Web Console.</description>
+      <description>Bring your own OCI image It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image.&#xA;Let&amp;rsquo;s point OpenShift to an existing built container image Choose either to complete the steps via CLI or Web Console.</description>
     </item>
-    
     <item>
       <title>Lab 2 - BYO Container</title>
       <link>/workshops/openshift_4_101_dynatrace/lab2-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab2-byocontainer/</guid>
-      <description>Bring your own docker It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image. And we will dig into the details to show how all that works.
-Let&amp;rsquo;s point OpenShift to an existing built container image CLI Steps      Verify you&#39;re still in the project we created at the end of the last lab by going to the terminal and typing the following:  $ oc projects  You should see something *similar* in the last line of the output:  $ Using project &amp;#34;demo-0&amp;#34; on server &amp;#34;https://172.</description>
+      <description>Bring your own docker It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image. And we will dig into the details to show how all that works.&#xA;Let&amp;rsquo;s point OpenShift to an existing built container image CLI Steps Verify you&#39;re still in the project we created at the end of the last lab by going to the terminal and typing the following: $ oc projects You should see something *similar* in the last line of the output: $ Using project &amp;#34;demo-0&amp;#34; on server &amp;#34;https://172.</description>
     </item>
-    
     <item>
       <title>Lab 2 - BYO Docker</title>
       <link>/workshops/openshift_101_dcmetromap/lab2-byodocker/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab2-byodocker/</guid>
       <description>Bring your own docker It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing docker assets. In this quick lab we will deploy an application using an exisiting docker image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image. And we will dig into the details to show how all that works.</description>
     </item>
-    
     <item>
       <title>Lab 2 - Managing Neutron Networks</title>
       <link>/workshops/rhosp_101/3_managing_networks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/3_managing_networks/</guid>
-      <description>Neutron - Overlay Networking for OpenStack Neutron is an OpenStack project to provide &amp;ldquo;networking as a service&amp;rdquo; between interface devices (e.g., vNICs) managed by other Openstack services (e.g., nova).
-Starting in the Folsom release, Neutron is a core and supported part of the OpenStack platform.
-Examining Project Network Topology  Navigate to Network -&amp;gt; Network Topology using the second level navigation tabs.
-   Lab 2 Figure 1: Neutron Network Topology   There are two ways to view the project network layout.</description>
+      <description>Neutron - Overlay Networking for OpenStack Neutron is an OpenStack project to provide &amp;ldquo;networking as a service&amp;rdquo; between interface devices (e.g., vNICs) managed by other Openstack services (e.g., nova).&#xA;Starting in the Folsom release, Neutron is a core and supported part of the OpenStack platform.&#xA;Examining Project Network Topology Navigate to Network -&amp;gt; Network Topology using the second level navigation tabs.&#xA;Lab 2 Figure 1: Neutron Network Topology There are two ways to view the project network layout.</description>
     </item>
-    
     <item>
       <title>Lab 2.0 - Container registries</title>
       <link>/workshops/security_container_intro/lab02-registry/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab02-registry/</guid>
-      <description>Table of Contents Configuring the registries Node 1 Testing the registries Node 2 Testing the registries Configuring and testing the bastion     During this module you will configure both nodes to host secure container registries. The registry software runs in a container and listens on port 5000. Configuring the registry consists of generating a self-signed SSL certificate and running the container. Two simple bash scripts are provided to do this.</description>
+      <description>During this module you will configure both nodes to host secure container registries. The registry software runs in a container and listens on port 5000. Configuring the registry consists of generating a self-signed SSL certificate and running the container. Two simple bash scripts are provided to do this. Once the registries are configured and running, the curl command can be used to test basic connectivity.&#xA;Configuring the registries Node 1 Login to node1-0.</description>
     </item>
-    
     <item>
       <title>Lab 2.1 - Reviewing container details</title>
       <link>/workshops/openshift_4_101/lab2.1-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab2.1-byocontainer/</guid>
-      <description>Now that we have a running container, we can browse our project details with the command line https://console-openshift-console.apps.example.redhatgov.io/terminal
-  Try typing the following to see what is available to &amp;lsquo;get&amp;rsquo;:
- $ oc project demo-YOUR# $ oc get all   Now let&amp;rsquo;s look at what our image stream has in it:
- $ oc get is $ oc describe is/nexus 
-An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</description>
+      <description>Now that we have a running container, we can browse our project details with the command line https://console-openshift-console.apps.example.redhatgov.io/terminal&#xA;Try typing the following to see what is available to &amp;lsquo;get&amp;rsquo;:&#xA;$ oc project demo-YOUR# $ oc get all Now let&amp;rsquo;s look at what our image stream has in it:&#xA;$ oc get is $ oc describe is/nexus An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</description>
     </item>
-    
     <item>
       <title>Lab 2.2 - Clean-up &amp; Summary</title>
       <link>/workshops/openshift_4_101/lab2.2-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab2.2-byocontainer/</guid>
-      <description>Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal
-Let&amp;rsquo;s clean this up   Let&amp;rsquo;s clean up all this to get ready for the next lab:
- $ oc project demo-YOUR# $ oc delete all --selector app=nexus Summary In this lab, you&amp;rsquo;ve deployed an example container image into a pod running in OpenShift. You exposed a route for clients to access that service via their web browsers. And you learned how to get and describe resources using the command line and the web console.</description>
+      <description>Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal&#xA;Let&amp;rsquo;s clean this up Let&amp;rsquo;s clean up all this to get ready for the next lab:&#xA;$ oc project demo-YOUR# $ oc delete all --selector app=nexus Summary In this lab, you&amp;rsquo;ve deployed an example container image into a pod running in OpenShift. You exposed a route for clients to access that service via their web browsers. And you learned how to get and describe resources using the command line and the web console.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Deploying an App with S2I</title>
       <link>/workshops/openshift_101_dcmetromap/lab3-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab3-s2i/</guid>
-      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.
-Let&amp;rsquo;s build a node.js web server using S2I We can do this either via the command line or the web console.</description>
+      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.&#xA;Let&amp;rsquo;s build a node.js web server using S2I We can do this either via the command line or the web console.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Deploying an App with S2I</title>
       <link>/workshops/openshift_4_101/lab3-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab3-s2i/</guid>
-      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.
-Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
+      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.&#xA;Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Install Dynatrace Agent</title>
       <link>/workshops/openshift_4_101_dynatrace/lab3-installagent/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab3-installagent/</guid>
-      <description>Deploy the Dynatrace OneAgent Operator on OpenShift 4.4+  Prerequisites: 1) If no existing account, sign-up for a trial with Dynatrace at https://www.dynatrace.com/trial/  Dynatrace API Token from Settings &amp;gt; Integration &amp;gt; Dynatrace API &amp;gt; Generate Token Activate the following settings:
- Access problem and event feed, metrics, and topology Read log content Write configuration    Dynatrace PaaS token PaaS (used to download OneAgent and ActiveGate installers) from Settings &amp;gt; Integration &amp;gt; Platform as a Service &amp;gt; Generate Token</description>
+      <description>Deploy the Dynatrace OneAgent Operator on OpenShift 4.4+ Prerequisites: 1) If no existing account, sign-up for a trial with Dynatrace at https://www.dynatrace.com/trial/ Dynatrace API Token from Settings &amp;gt; Integration &amp;gt; Dynatrace API &amp;gt; Generate Token Activate the following settings:&#xA;Access problem and event feed, metrics, and topology Read log content Write configuration Dynatrace PaaS token PaaS (used to download OneAgent and ActiveGate installers) from Settings &amp;gt; Integration &amp;gt; Platform as a Service &amp;gt; Generate Token</description>
     </item>
-    
     <item>
       <title>Lab 3 - Managing Floating IP Addresses</title>
       <link>/workshops/rhosp_101/4_managing_floating_ip_addresses/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/4_managing_floating_ip_addresses/</guid>
       <description>Floating IP vs. Private IP Addresses Private IP Address A private IP address is assigned to an instance&amp;rsquo;s network-interface by the DHCP server. The address is visible from within the instance by using a command like “ip a”. The address is typically part of a private network and is used for communication between instances in the same broadcast domain via virtual switch (L2 agent on each compute node). It can also be accessible from instances in other private networks via virtual router (L3 agent).</description>
     </item>
-    
     <item>
       <title>Lab 3.0 - Intro to Podman and base images</title>
       <link>/workshops/security_container_intro/lab03-podman/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab03-podman/</guid>
-      <description>Table of Contents What is a pod? The Universal Base Image Tagging and pushing images to a remote registry Working with root and rootless containers. Stopping and removing containers Container process information User Namespace Support Auditing containers UID Mapping Challenge References     What is a pod? A pod is a group of one or more containers with shared storage, network and a specification for how to run the containers.</description>
+      <description>What is a pod? A pod is a group of one or more containers with shared storage, network and a specification for how to run the containers. In this module you’ll be working at the container level. Since you are here to learn more about container security, we have a quick review of container basics then get right into the good stuff.&#xA;Podman (Pod Manager) is a fully featured container engine that is a simple daemon-less tool.</description>
     </item>
-    
     <item>
       <title>Lab 3.1 - Check out the build details</title>
       <link>/workshops/openshift_4_101/lab3.1-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab3.1-s2i/</guid>
-      <description>Check out the build details We can see the details of what the S2I builder did. This can be helpful to diagnose issues if builds are failing.
- TIP: For a node.js app, running &amp;ldquo;npm shrinkwrap&amp;rdquo; is a good practice to perform on your branch before releasing changes that you plan to build/deploy as an image with S2I
-CLI Steps    Terminal access  https://console-openshift-console.apps.example.redhatgov.io/terminal    Goto the terminal and type the following:  $ oc get builds  Note the name of your build from the above command output and use it to see the logs with:  $ oc logs builds/[BUILD_NAME] The console will print out the full log for your build.</description>
+      <description>Check out the build details We can see the details of what the S2I builder did. This can be helpful to diagnose issues if builds are failing.&#xA;TIP: For a node.js app, running &amp;ldquo;npm shrinkwrap&amp;rdquo; is a good practice to perform on your branch before releasing changes that you plan to build/deploy as an image with S2I&#xA;CLI Steps Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal Goto the terminal and type the following: $ oc get builds Note the name of your build from the above command output and use it to see the logs with: $ oc logs builds/[BUILD_NAME] The console will print out the full log for your build.</description>
     </item>
-    
     <item>
       <title>Lab 4 - Configuring Dynatrace ActiveGate (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/</guid>
-      <description>Connect your OpenShift clusters to Dynatrace with an ActiveGate to take advantage of the dedicated OpenShift overview page Connecting your OpenShift clusters to Dynatrace to take advantage of the dedicated OpenShift overview page requires that you run an ActiveGate in your environment (version 1.163+).
-See https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/monitoring/monitor-openshift-clusters-with-dynatrace/
-oc project dynatrace oc apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml serviceaccount/dynatrace-monitoring created clusterrole.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created clusterrolebinding.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created oc config view --minify -o jsonpath=&amp;#39;{.clusters[0].cluster.server}&amp;#39; https://api.ocp4.local:6443  Get the Bearer token for the OpenShift cluster using the following command: Copy the secret returned by the following command:</description>
+      <description>Connect your OpenShift clusters to Dynatrace with an ActiveGate to take advantage of the dedicated OpenShift overview page Connecting your OpenShift clusters to Dynatrace to take advantage of the dedicated OpenShift overview page requires that you run an ActiveGate in your environment (version 1.163+).&#xA;See https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/monitoring/monitor-openshift-clusters-with-dynatrace/&#xA;oc project dynatrace oc apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml serviceaccount/dynatrace-monitoring created clusterrole.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created clusterrolebinding.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created oc config view --minify -o jsonpath=&amp;#39;{.clusters[0].cluster.server}&amp;#39; https://api.ocp4.local:6443 Get the Bearer token for the OpenShift cluster using the following command: Copy the secret returned by the following command:</description>
     </item>
-    
     <item>
       <title>Lab 4 - Developing and Managing Your Application</title>
       <link>/workshops/openshift_101_dcmetromap/lab4-devmanage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab4-devmanage/</guid>
-      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.
-Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
+      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.&#xA;Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 4 - Developing and Managing Your Application</title>
       <link>/workshops/openshift_4_101/lab4-devmanage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab4-devmanage/</guid>
-      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.
-Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
+      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.&#xA;Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 4 - Managing Security Groups</title>
       <link>/workshops/rhosp_101/5_managing_security_groups/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/5_managing_security_groups/</guid>
-      <description>Security Groups in OpenStack A security group is a named collection of network access rules that are used to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group.
-The associated rules in each security group control the traffic to instances in the group.</description>
+      <description>Security Groups in OpenStack A security group is a named collection of network access rules that are used to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group.&#xA;The associated rules in each security group control the traffic to instances in the group.</description>
     </item>
-    
     <item>
       <title>Lab 4.0 - Linux kernel capabilities</title>
       <link>/workshops/security_container_intro/lab04-isolation/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab04-isolation/</guid>
-      <description>Table of Contents Capabilities Exploring the capabilities of containers. Examining container processes Capabilities Challenge #1 Capabilities Challenge #2 Capabilities Challenge #3 Example Solutions to Challenges     Containers provide a certain degree of process isolation via kernel namespaces. In this module, we’ll examine the capabilities of a process running in a containerized namespace. Specifically we&amp;#8217;ll look at how Linux capabilities can be used to grant a particular or subset of root privileges to a process running in a container.</description>
+      <description>Containers provide a certain degree of process isolation via kernel namespaces. In this module, we’ll examine the capabilities of a process running in a containerized namespace. Specifically we’ll look at how Linux capabilities can be used to grant a particular or subset of root privileges to a process running in a container.&#xA;It would be worth taking a few minutes to read this blog post before beginning this lab.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Deploying an App with S2I</title>
       <link>/workshops/openshift_4_101_dynatrace/lab5-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab5-s2i/</guid>
-      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.
-Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
+      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.&#xA;Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Managing Images</title>
       <link>/workshops/rhosp_101/6_managing_images/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/6_managing_images/</guid>
-      <description>Where Shall We Store Our Golden Images? Glance The Image service (glance) project provides a service where users can upload and discover data assets that are meant to be used with other services. This currently includes images and metadata definitions.
-Glance image services include discovering, registering, and retrieving virtual machine (VM) images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image.</description>
+      <description>Where Shall We Store Our Golden Images? Glance The Image service (glance) project provides a service where users can upload and discover data assets that are meant to be used with other services. This currently includes images and metadata definitions.&#xA;Glance image services include discovering, registering, and retrieving virtual machine (VM) images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Webhooks and Rollbacks</title>
       <link>/workshops/openshift_101_dcmetromap/lab5-rollbacks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab5-rollbacks/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Webhooks and Rollbacks</title>
       <link>/workshops/openshift_4_101/lab5-rollbacks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab5-rollbacks/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 5.0 - SELinux container integration</title>
       <link>/workshops/security_container_intro/lab05-selinux/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab05-selinux/</guid>
-      <description>Table of Contents !Namespaced Warmup Exercise Bind Mounts and Labeling Private Mounts Shared Mounts Read-Only Containers     In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations where the other security mechanisms fail. By default, podman processes are labeled with container_runtime_t and they are prevented from doing (almost) all SELinux operations. But processes within containers do not know that they are running within a container.</description>
+      <description>In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations where the other security mechanisms fail. By default, podman processes are labeled with container_runtime_t and they are prevented from doing (almost) all SELinux operations. But processes within containers do not know that they are running within a container. SELinux-aware applications are going to attempt to do SELinux operations, especially if they are running as root.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Application Replication</title>
       <link>/workshops/openshift_4_101/lab6-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab6-replicationrecovery/</guid>
-      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something completely out of your control. But, we can plan for such failures, thus minimizing their impact. OpenShift supports this via the replication and recovery functionality.
-Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state. Assuming you still have the dc-metro-map project running we can manually scale up our replicas to handle increased user load.</description>
+      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something completely out of your control. But, we can plan for such failures, thus minimizing their impact. OpenShift supports this via the replication and recovery functionality.&#xA;Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state. Assuming you still have the dc-metro-map project running we can manually scale up our replicas to handle increased user load.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Deploying a 3 Tier App</title>
       <link>/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/</guid>
-      <description>Deploying a 3 Tier App This builds on the work done in the labs so far to deploy a 3 Tier App. The reason for this lab are to highlight the capabilities of OpenShift to handle more complex application stacks and to show how Dynatrace automatically captures new applications and interactions between them.
- Instructions are located in a Red Hat blog post at:  https://developers.redhat.com/articles/deploy-a-NodeJS-app-OpenShift   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Deploying a 3 Tier App This builds on the work done in the labs so far to deploy a 3 Tier App. The reason for this lab are to highlight the capabilities of OpenShift to handle more complex application stacks and to show how Dynatrace automatically captures new applications and interactions between them.&#xA;Instructions are located in a Red Hat blog post at: https://developers.redhat.com/articles/deploy-a-NodeJS-app-OpenShift &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Managing Instances</title>
       <link>/workshops/rhosp_101/7_managing_instances/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/7_managing_instances/</guid>
-      <description>Now We are Ready to Launch an OpenStack Instance First, What is an Instance? Instances are virtual machines that run inside the OpenStack cloud. You can launch an instance from the following sources:
- Images uploaded to the Image service Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the cinder-volume API Instance snapshot that you took  Second. We need a key pair before we launch our first instance  Navigate to Compute -&amp;gt; Key Pairs using the second level navigation tabs</description>
+      <description>Now We are Ready to Launch an OpenStack Instance First, What is an Instance? Instances are virtual machines that run inside the OpenStack cloud. You can launch an instance from the following sources:&#xA;Images uploaded to the Image service Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the cinder-volume API Instance snapshot that you took Second. We need a key pair before we launch our first instance Navigate to Compute -&amp;gt; Key Pairs using the second level navigation tabs</description>
     </item>
-    
     <item>
       <title>Lab 6 - Replication and Recovery</title>
       <link>/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/</guid>
-      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.
-Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
+      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.&#xA;Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
     </item>
-    
     <item>
       <title>Lab 6.0 - Container inspection with Podman &amp; Skopeo</title>
       <link>/workshops/security_container_intro/lab06-inspecting/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab06-inspecting/</guid>
-      <description>Table of Contents Podman inspect Podman diff Podman live mounts Working with Skopeo Inspecting images     Container images can easily be pulled from any public registry and run on a container host but is this good practice? Can you trust this image and what are its contents? A better practice would be to inspect the image before running it.
- Podman inspect Use podman to inspect the registry.</description>
+      <description>Container images can easily be pulled from any public registry and run on a container host but is this good practice? Can you trust this image and what are its contents? A better practice would be to inspect the image before running it.&#xA;Podman inspect Use podman to inspect the registry.access.redhat.com/ubi8/ubi image. Remember, this image must be present in local storage. Examine the output to determine who is the maintainer and what is the version of that image?</description>
     </item>
-    
     <item>
       <title>Lab 6.1 - Application Recovery</title>
       <link>/workshops/openshift_4_101/lab6.1-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab6.1-replicationrecovery/</guid>
-      <description>Recovery Okay, now that we have a slightly more interesting replication state, we can test a service outages scenario. In this scenario, the dc-metro-map replication controller will ensure that other pods are created to replace those that become unhealthy. Let&amp;rsquo;s forcibly inflict an issue and see how OpenShift responds.
-CLI Steps    Terminal access  https://console-openshift-console.apps.example.redhatgov.io/terminal    Choose a random pod and delete it:  $ oc get pods $ oc delete pod/PODNAME $ oc get pods -w If you&amp;rsquo;re fast enough you&amp;rsquo;ll see the pod you deleted go &amp;ldquo;Terminating&amp;rdquo; and you&amp;rsquo;ll also see a new pod immediately get created and transition from &amp;ldquo;Pending&amp;rdquo; to &amp;ldquo;Running&amp;rdquo;.</description>
+      <description>Recovery Okay, now that we have a slightly more interesting replication state, we can test a service outages scenario. In this scenario, the dc-metro-map replication controller will ensure that other pods are created to replace those that become unhealthy. Let&amp;rsquo;s forcibly inflict an issue and see how OpenShift responds.&#xA;CLI Steps Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal Choose a random pod and delete it: $ oc get pods $ oc delete pod/PODNAME $ oc get pods -w If you&amp;rsquo;re fast enough you&amp;rsquo;ll see the pod you deleted go &amp;ldquo;Terminating&amp;rdquo; and you&amp;rsquo;ll also see a new pod immediately get created and transition from &amp;ldquo;Pending&amp;rdquo; to &amp;ldquo;Running&amp;rdquo;.</description>
     </item>
-    
     <item>
       <title>Lab 6.2 - Application Health</title>
       <link>/workshops/openshift_4_101/lab6.2-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab6.2-replicationrecovery/</guid>
-      <description>Application Health In addition to the health of your application&amp;rsquo;s pods, OpenShift will watch the containers inside those pods. Let&amp;rsquo;s forcibly inflict some issues and see how OpenShift responds.
-CLI Steps    Terminal access  https://console-openshift-console.apps.example.redhatgov.io/terminal    Choose a running pod and shell into it:  $ oc get pods $ oc exec PODNAME -it /bin/bash You are now executing a bash shell running in the container of the pod.</description>
+      <description>Application Health In addition to the health of your application&amp;rsquo;s pods, OpenShift will watch the containers inside those pods. Let&amp;rsquo;s forcibly inflict some issues and see how OpenShift responds.&#xA;CLI Steps Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal Choose a running pod and shell into it: $ oc get pods $ oc exec PODNAME -it /bin/bash You are now executing a bash shell running in the container of the pod. Let&amp;rsquo;s kill our webapp and see what happens.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Developing and Managing Your Application</title>
       <link>/workshops/openshift_4_101_dynatrace/lab7-devmanage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab7-devmanage/</guid>
-      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.
-Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
+      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.&#xA;Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Labels</title>
       <link>/workshops/openshift_101_dcmetromap/lab7-labels/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab7-labels/</guid>
-      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.
-For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.
-Labels on a pod In a previous lab we added our web app using a S2I template.</description>
+      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.&#xA;For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.&#xA;Labels on a pod In a previous lab we added our web app using a S2I template.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Labels</title>
       <link>/workshops/openshift_4_101/lab7-labels/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab7-labels/</guid>
-      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.
-For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.
-Labels on a pod In a previous lab we added our web app using a S2I template.</description>
+      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.&#xA;For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.&#xA;Labels on a pod In a previous lab we added our web app using a S2I template.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Using the OpenStack CLI(s)</title>
       <link>/workshops/rhosp_101/8_using_the_cli/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/8_using_the_cli/</guid>
-      <description>Okay. UIs Are Cool and All, But Can&amp;rsquo;t I Just Use the CLI? Absolutely! There are 3 ways to interact with OpenStack.
- API CLI GUI  In this lab, we are going to walk through some of the activities that we did in the previous labs via the CLI.
-
-When you see a CLI command starting with openstack, the command is part of the Unified CLI.
-When you see a CLI command that starts with a project name like nova, these are the individual CLIs.</description>
+      <description>Okay. UIs Are Cool and All, But Can&amp;rsquo;t I Just Use the CLI? Absolutely! There are 3 ways to interact with OpenStack.&#xA;API CLI GUI In this lab, we are going to walk through some of the activities that we did in the previous labs via the CLI.&#xA;When you see a CLI command starting with openstack, the command is part of the Unified CLI.&#xA;When you see a CLI command that starts with a project name like nova, these are the individual CLIs.</description>
     </item>
-    
     <item>
       <title>Lab 7.0 - Container image signing</title>
       <link>/workshops/security_container_intro/lab07-signing/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab07-signing/</guid>
-      <description>Table of Contents Configuring the signature claim store Generating key pairs Working with trust policies Pulling signed images Create a trust policy for Red Hat images. Blocking a registry     In this lab, you will use podman to sign container images and create trust policies to control access to registries.
- To begin the image signing procedure, a signature claim is generated by encrypting a container image manifest using a private gpg key.</description>
+      <description>In this lab, you will use podman to sign container images and create trust policies to control access to registries.&#xA;To begin the image signing procedure, a signature claim is generated by encrypting a container image manifest using a private gpg key. The signature claims are stored in a file system or web server where they can be decrypted later and used to pull signed images.&#xA;The procedure is reversed when pulling signed images.</description>
     </item>
-    
     <item>
       <title>Lab 8 - CI / CD Pipeline</title>
       <link>/workshops/openshift_101_dcmetromap/lab8-cicd/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab8-cicd/</guid>
-      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.
-In this lab we walk through creating a simple example of a CI/CD pipeline utlizing Jenkins, all running on top of OpenShift!</description>
+      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.&#xA;In this lab we walk through creating a simple example of a CI/CD pipeline utlizing Jenkins, all running on top of OpenShift!</description>
     </item>
-    
     <item>
       <title>Lab 8 - CI / CD Pipeline</title>
       <link>/workshops/openshift_4_101/lab8-cicd/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab8-cicd/</guid>
-      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.
-In this lab we walk through creating a simple example of a CI/CD [pipeline] utilizing Jenkins, all running on top of OpenShift!</description>
+      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.&#xA;In this lab we walk through creating a simple example of a CI/CD [pipeline] utilizing Jenkins, all running on top of OpenShift!</description>
     </item>
-    
     <item>
       <title>Lab 8 - Using Heat to Describe Stacks</title>
       <link>/workshops/rhosp_101/9_heat/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/9_heat/</guid>
-      <description>We Have Done a Ton of Stuff, But All Manually. How Do We Orchestrate? In OpenStack, the answer to that is Heat.
-Heat is the main project for orchestration in OpenStack. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code. A native Heat template format is evolving, but Heat also endeavours to provide compatibility with the AWS CloudFormation template format, so that many existing CloudFormation templates can be launched on OpenStack.</description>
+      <description>We Have Done a Ton of Stuff, But All Manually. How Do We Orchestrate? In OpenStack, the answer to that is Heat.&#xA;Heat is the main project for orchestration in OpenStack. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code. A native Heat template format is evolving, but Heat also endeavours to provide compatibility with the AWS CloudFormation template format, so that many existing CloudFormation templates can be launched on OpenStack.</description>
     </item>
-    
     <item>
       <title>Lab 8 - Webhooks and Rollbacks (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab8-rollbacks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab8-rollbacks/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 8.0 - Composing containers with Buildah</title>
       <link>/workshops/security_container_intro/lab08-builds/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab08-builds/</guid>
-      <description>Table of Contents Building from Universal Base Images Build using Docker (BuD)   This module will introduce Buildah, a command line tool for building Open Container Initiative compatible container images. Buildah is easy to incorporate into scripts and build pipelines, and best of all, it doesn&amp;#8217;t require a running container daemon to build its image. You can read more about Buildah at the buildah.io web site. Also, have a look at the buildah chapter in the RHEL 8 documentation.</description>
+      <description>This module will introduce Buildah, a command line tool for building Open Container Initiative compatible container images. Buildah is easy to incorporate into scripts and build pipelines, and best of all, it doesn’t require a running container daemon to build its image. You can read more about Buildah at the buildah.io web site. Also, have a look at the buildah chapter in the RHEL 8 documentation.&#xA;Building from Universal Base Images Below are the basic steps for building a container image from a UBI.</description>
     </item>
-    
     <item>
       <title>Lab 9 - Blue | Green Deployment</title>
       <link>/workshops/openshift_101_dcmetromap/lab9-bluegreen/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab9-bluegreen/</guid>
       <description>Blue/Green deployments When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments. It addresses the desire to minimize downtime during the release of a new version of an application to production. Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified. Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.</description>
     </item>
-    
     <item>
       <title>Lab 9 - Blue | Green Deployment</title>
       <link>/workshops/openshift_4_101/lab9-bluegreen/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab9-bluegreen/</guid>
       <description>Blue/Green deployments When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments. It addresses the desire to minimize downtime during the release of a new version of an application to production. Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified. Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.</description>
     </item>
-    
     <item>
       <title>Lab 9 - Managing Block and Object Storage</title>
       <link>/workshops/rhosp_101/10_storage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/10_storage/</guid>
-      <description>Working With Block and Object Storage in OpenStack Block Storage is Handled by Cinder The OpenStack Block Storage service works through the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. You can run all the binaries from a single node, or spread across multiple nodes. You can also run them on the same node as other OpenStack services.
-To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts.</description>
+      <description>Working With Block and Object Storage in OpenStack Block Storage is Handled by Cinder The OpenStack Block Storage service works through the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. You can run all the binaries from a single node, or spread across multiple nodes. You can also run them on the same node as other OpenStack services.&#xA;To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts.</description>
     </item>
-    
     <item>
       <title>Lab 9 - Replication and Recovery (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/</guid>
-      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.
-Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
+      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.&#xA;Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
     </item>
-    
     <item>
       <title>Login Tour - Butterfly</title>
       <link>/workshops/openshift_101_dcmetromap/login_tour_wetty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/login_tour_wetty/</guid>
-      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.
-Let&amp;rsquo;s Login to the Web Console  Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.
- https://master.example.redhatgov.io:8443  Login Webpage
-Once logged in you should see your available projects - or a button to create a project if none exist already.
-So this is what an empty project looks like First let&amp;rsquo;s create a new project to do our workshop work in.</description>
+      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.&#xA;Let&amp;rsquo;s Login to the Web Console Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.&#xA;https://master.example.redhatgov.io:8443 Login Webpage&#xA;Once logged in you should see your available projects - or a button to create a project if none exist already.&#xA;So this is what an empty project looks like First let&amp;rsquo;s create a new project to do our workshop work in.</description>
     </item>
-    
     <item>
       <title>Login Tour - Wetty</title>
       <link>/workshops/secure_software_factory/login_tour_wetty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/login_tour_wetty/</guid>
-      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-Accessing Wetty Ask your instructor for the wetty URL.
-Login Info login: userYOUR# Password: &amp;lt;Instructor Provided&amp;gt; After logging in, you should see a shell.
-The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
+      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Ask your instructor for the wetty URL.&#xA;Login Info login: userYOUR# Password: &amp;lt;Instructor Provided&amp;gt; After logging in, you should see a shell.&#xA;The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
     </item>
-    
     <item>
       <title>Microservices</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/</guid>
-      <description>A Brief Introduction to Microservices Microservices, also known as the microservice architecture, is a software development technique that structures an application as a collection of loosely coupled services. Microservice architectures enable the continuous delivery/deployment/scaling of complex applications.
-Why microservices? Agility. Deliver application updates faster. Isolate and fix bugs easier. Done right, a microservices architecture will you help to meet several important non-functional requirements for your software:
- scalability performance reliability resiliency extensibility availability  What is a Service Mesh?</description>
+      <description>A Brief Introduction to Microservices Microservices, also known as the microservice architecture, is a software development technique that structures an application as a collection of loosely coupled services. Microservice architectures enable the continuous delivery/deployment/scaling of complex applications.&#xA;Why microservices? Agility. Deliver application updates faster. Isolate and fix bugs easier. Done right, a microservices architecture will you help to meet several important non-functional requirements for your software:&#xA;scalability performance reliability resiliency extensibility availability What is a Service Mesh?</description>
     </item>
-    
     <item>
       <title>Observability - Feature Update</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/</guid>
-      <description>Digging into Observability Istio provides additional capabilities to analyze the service mesh and its performance. Let&amp;rsquo;s deploy a new version of the user profile service and analyze its effect on the service mesh.
-Feature Update The code has already been written for you on the &amp;lsquo;workshop-feature-update&amp;rsquo; branch of the repo.
-  Create a new build on this feature branch:  oc new-app -f ./openshift-configuration/userprofile-build.yaml \ -p APPLICATION_NAME=userprofile \ -p APPLICATION_CODE_URI=https://github.</description>
+      <description>Digging into Observability Istio provides additional capabilities to analyze the service mesh and its performance. Let&amp;rsquo;s deploy a new version of the user profile service and analyze its effect on the service mesh.&#xA;Feature Update The code has already been written for you on the &amp;lsquo;workshop-feature-update&amp;rsquo; branch of the repo.&#xA;Create a new build on this feature branch: oc new-app -f ./openshift-configuration/userprofile-build.yaml \ -p APPLICATION_NAME=userprofile \ -p APPLICATION_CODE_URI=https://github.com/RedHatGov/openshift-microservices.git \ -p APPLICATION_CODE_BRANCH=workshop-feature-update \ -p APP_VERSION_TAG=2.</description>
     </item>
-    
     <item>
       <title>Observability - Grafana</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/</guid>
-      <description>Service Mesh Metrics with Grafana Grafana is a monitoring tool that can be integrated with Istio for metric observation. Using Grafana, you can look at metrics associated with services in your mesh. Let&amp;rsquo;s use Grafana to get more information about the user profile service.
-Explore Grafana First, let&amp;rsquo;s explore the Grafana user interface.
-  Open the Grafana console. Retrieve the endpoint for Grafana:  GRAFANA_CONSOLE=$(oc get route grafana -n istio-system --template=&#39;https://{{.</description>
+      <description>Service Mesh Metrics with Grafana Grafana is a monitoring tool that can be integrated with Istio for metric observation. Using Grafana, you can look at metrics associated with services in your mesh. Let&amp;rsquo;s use Grafana to get more information about the user profile service.&#xA;Explore Grafana First, let&amp;rsquo;s explore the Grafana user interface.&#xA;Open the Grafana console. Retrieve the endpoint for Grafana: GRAFANA_CONSOLE=$(oc get route grafana -n istio-system --template=&amp;#39;https://{{.spec.host}}&amp;#39;) echo $GRAFANA_CONSOLE Click &#39;Allow selected permissions&#39; if prompted to authorized access.</description>
     </item>
-    
     <item>
       <title>Observability - Jaeger</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/</guid>
-      <description>Distributed Tracing with Jaeger Jaeger is a distributed tracing tool that lets you trace requests as they flow through your service mesh. This is incredibly useful for debugging performance issues in your microservices architecture.
-Explore Jaeger First, let&amp;rsquo;s explore the Jaeger user interface.
-  Open the Jaeger console. Retrieve the endpoint for Jaeger:  JAEGER_CONSOLE=$(oc get route jaeger -n istio-system --template=&#39;https://{{.spec.host}}&#39;) echo $JAEGER_CONSOLE  Click &#39;Allow selected permissions&#39; if prompted to authorized access.</description>
+      <description>Distributed Tracing with Jaeger Jaeger is a distributed tracing tool that lets you trace requests as they flow through your service mesh. This is incredibly useful for debugging performance issues in your microservices architecture.&#xA;Explore Jaeger First, let&amp;rsquo;s explore the Jaeger user interface.&#xA;Open the Jaeger console. Retrieve the endpoint for Jaeger: JAEGER_CONSOLE=$(oc get route jaeger -n istio-system --template=&amp;#39;https://{{.spec.host}}&amp;#39;) echo $JAEGER_CONSOLE Click &#39;Allow selected permissions&#39; if prompted to authorized access.</description>
     </item>
-    
     <item>
       <title>Observability - Kiali</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/</guid>
-      <description>Introducing Kiali for Observability All of your microservices are running in the service mesh. Now, you need a way to visualize the service mesh topology. That is, what&amp;rsquo;s running in your service mesh and how are they connected?
-Istio provides Kiali, an open source project that gives you a console view of your service mesh. You can inspect the health of your service mesh, and it has further integrations for metric querying and tracing that we will cover in later labs.</description>
+      <description>Introducing Kiali for Observability All of your microservices are running in the service mesh. Now, you need a way to visualize the service mesh topology. That is, what&amp;rsquo;s running in your service mesh and how are they connected?&#xA;Istio provides Kiali, an open source project that gives you a console view of your service mesh. You can inspect the health of your service mesh, and it has further integrations for metric querying and tracing that we will cover in later labs.</description>
     </item>
-    
     <item>
       <title>Prerequisites</title>
       <link>/workshops/source_to_image/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/prerequisites/</guid>
-      <description>Getting Started If you choose to work from your own command line, instead of the web terminal (Wetty) environment, that&amp;rsquo;s just fine! You&amp;rsquo;ll have to install a few of utilities first.
-Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.
-Install git Click here for instructions on how to install Git on your workstation.
-Install golang Click here for instructions on how to install Golang.</description>
+      <description>Getting Started If you choose to work from your own command line, instead of the web terminal (Wetty) environment, that&amp;rsquo;s just fine! You&amp;rsquo;ll have to install a few of utilities first.&#xA;Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.&#xA;Install git Click here for instructions on how to install Git on your workstation.&#xA;Install golang Click here for instructions on how to install Golang.</description>
     </item>
-    
     <item>
       <title>Prerequisites</title>
       <link>/workshops/strangling_the_monolith/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/prerequisites/</guid>
-      <description>If we provided you a laptop or cloud environment. We already set all this up for you — feel free to skip everything below!
- Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.
-Install git Click here for instructions on how to install Git on your workstation.
-Create GitHub account Click here for instructions on how to setup an account.</description>
+      <description>If we provided you a laptop or cloud environment. We already set all this up for you — feel free to skip everything below!&#xA;Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.&#xA;Install git Click here for instructions on how to install Git on your workstation.&#xA;Create GitHub account Click here for instructions on how to setup an account.</description>
     </item>
-    
     <item>
       <title>Prerequisites for JDV Development</title>
       <link>/workshops/jdv_dev/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/prerequisites/</guid>
-      <description>What you need  A free account on Red Hat Developers to download JBoss Data Virtualization and JBoss Developer Studio A Java Development Kit (JDK) 8 git available as a local command Node.js runtime, 6.x or higher Postman for testing An accessible PostgreSQL instance  Recommended: Download a pre-built VM, ISO or docker image from TurnKey Linux. The provided VM/ISO also provides an web interface for loading data. Step by step instructions are provided for a Turnkey linux instance    </description>
+      <description>What you need A free account on Red Hat Developers to download JBoss Data Virtualization and JBoss Developer Studio A Java Development Kit (JDK) 8 git available as a local command Node.js runtime, 6.x or higher Postman for testing An accessible PostgreSQL instance Recommended: Download a pre-built VM, ISO or docker image from TurnKey Linux. The provided VM/ISO also provides an web interface for loading data. Step by step instructions are provided for a Turnkey linux instance </description>
     </item>
-    
     <item>
       <title>Security - Auth Policy</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/</guid>
       <description>Authorizing and Authenticating Access via Policy In the previous labs we secured and verified the service-to-service communication. But what about user-to-service communication (aka origin authentication)? The service mesh can help with that too. To do this, we need to bring in an identity provider that will issue JSON Web Tokens (JWTs) to signed in users. JWTs are an open, industry standard (RFC 7519) way of sharing identity. The app-ui service will pass those JWTs along with it&amp;rsquo;s API requests.</description>
     </item>
-    
     <item>
       <title>Security - Auth Policy Prep</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.3_prep/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.3_prep/</guid>
-      <description>Single Sign-On Login, registration, and role-based authorization is handled via Red Hat SSO (aka Keycloak). SSO is included as part of OpenShift or any middleware product subscription you have from Red Hat - woot!
-Installation Because the service mesh will leverage SSO to authenticate users and generate JWT we need to install it. You will install it via Operator into your namespace.
-Customize the Resources Check out the .yaml files here and customize for this workshop cluster&amp;rsquo;s domain, and your user project.</description>
+      <description>Single Sign-On Login, registration, and role-based authorization is handled via Red Hat SSO (aka Keycloak). SSO is included as part of OpenShift or any middleware product subscription you have from Red Hat - woot!&#xA;Installation Because the service mesh will leverage SSO to authenticate users and generate JWT we need to install it. You will install it via Operator into your namespace.&#xA;Customize the Resources Check out the .yaml files here and customize for this workshop cluster&amp;rsquo;s domain, and your user project.</description>
     </item>
-    
     <item>
       <title>Security - mTLS</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/</guid>
-      <description>Mutual TLS One of the key features of the Service Mesh is its ability to bring additional security to your applications. It does this in a several different ways that will be explored in the next few labs. The first of which is a concept known as &amp;ldquo;Mutual TLS&amp;rdquo; or mTLS for short.
-Imagine a scenario where you are deploying a microservices application and are expecting a lot of PII to flow between the services.</description>
+      <description>Mutual TLS One of the key features of the Service Mesh is its ability to bring additional security to your applications. It does this in a several different ways that will be explored in the next few labs. The first of which is a concept known as &amp;ldquo;Mutual TLS&amp;rdquo; or mTLS for short.&#xA;Imagine a scenario where you are deploying a microservices application and are expecting a lot of PII to flow between the services.</description>
     </item>
-    
     <item>
       <title>Security - Securing Ingress and Egress</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/</guid>
-      <description>Securing Ingress and Egress In cases where strict security is required we need to configure specifics around securing ingress and egress traffic. Security around egress is often used to lock down and deny access to potentially harmful resources outside the network. Additionally, it is a good practice to prevent malicious activities from originating from the cluster.
-You are probably already familiar with basic ingress security concepts. Essentially, only exposing particular services to be accessible from outside the cluster and using basic TLS/SSL.</description>
+      <description>Securing Ingress and Egress In cases where strict security is required we need to configure specifics around securing ingress and egress traffic. Security around egress is often used to lock down and deny access to potentially harmful resources outside the network. Additionally, it is a good practice to prevent malicious activities from originating from the cluster.&#xA;You are probably already familiar with basic ingress security concepts. Essentially, only exposing particular services to be accessible from outside the cluster and using basic TLS/SSL.</description>
     </item>
-    
     <item>
       <title>Security - Verifying mTLS</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/</guid>
-      <description>Checking and Verification of mTLS OK, now that all our services are encrypting traffic Let&amp;rsquo;s take a look in Kiali to see our encryption setup.
-  Open up the dashboard to Kiali (if you don&#39;t already have it open) and navigate to the Graph view. In the first drop down select the &#34;Service graph&#34; and in the &#34;Display&#34; drop down make sure the &#34;Security&#34; check box is checked.  You should see something like this screenshot with little locks indicating that mTLS is working for service-to-service communication.</description>
+      <description>Checking and Verification of mTLS OK, now that all our services are encrypting traffic Let&amp;rsquo;s take a look in Kiali to see our encryption setup.&#xA;Open up the dashboard to Kiali (if you don&#39;t already have it open) and navigate to the Graph view. In the first drop down select the &#34;Service graph&#34; and in the &#34;Display&#34; drop down make sure the &#34;Security&#34; check box is checked. You should see something like this screenshot with little locks indicating that mTLS is working for service-to-service communication.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/setup/</guid>
-      <description>In order for you to &#39;write&#39; your first bit of Ansible, you will need an editor &amp;#8230;&amp;#8203; Ansible playbooks are written in YAML and you can use an text editor &#34;like vim&#34; or an editor like Visual Studio Code to get started. For this workshop, we will be utilizing a web-based IDE (integrated development environment) call Red Hat CodeReady Workspaces. Red Hat CodeReady Workspaces is a developer tool that makes cloud-native development practical for teams, using Kubernetes and containers to provide any member of the development or IT team with a consistent, preconfigured development environment.</description>
+      <description>In order for you to &amp;#39;write&amp;#39; your first bit of Ansible, you will need an editor …​ Ansible playbooks are written in YAML and you can use an text editor &amp;#34;like vim&amp;#34; or an editor like Visual Studio Code to get started. For this workshop, we will be utilizing a web-based IDE (integrated development environment) call Red Hat CodeReady Workspaces. Red Hat CodeReady Workspaces is a developer tool that makes cloud-native development practical for teams, using Kubernetes and containers to provide any member of the development or IT team with a consistent, preconfigured development environment.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/ansible_automation/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/ansible_tower_azure/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/setup/</guid>
-      <description>What you will learn: Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Wetty Use this URL to access the Wetty node, just change the workshopname and region (if applicable). Ask your instructor for the workshopname and region.</description>
+      <description>What you will learn: Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Use this URL to access the Wetty node, just change the workshopname and region (if applicable). Ask your instructor for the workshopname and region.&#xA;https://example-tower0.example.redhatgov.io:8888 login: azure-user Password: redhat!</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/ansible_tower_intro/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Ansible Tower Use this URL to access the Ansible Tower interface. Your instructor will provide the password, and the user ID is admin:</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Ansible Tower Use this URL to access the Ansible Tower interface. Your instructor will provide the password, and the user ID is admin:</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/containers_101/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.3_installing/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.3_installing/</guid>
-      <description>Setup You will conduct these labs in an OpenShift cluster. As in the previous terminal deployment exercise, you can access your cluster via console and CLI.
-OpenShift You will use the OpenShift &amp;lsquo;oc&amp;rsquo; CLI to execute commands for the majority of this lab.
-  Login using API endpoint and remember to add the &#39;--insecure-skip-tls-verify=true&#39; flag  $ oc login https://api.example.redhatgov.io:6443 --insecure-skip-tls-verify=true Authentication required for https://api.example.redhatgov.io:6443 (openshift) Username: userYOUR# Password: Login successful.</description>
+      <description>Setup You will conduct these labs in an OpenShift cluster. As in the previous terminal deployment exercise, you can access your cluster via console and CLI.&#xA;OpenShift You will use the OpenShift &amp;lsquo;oc&amp;rsquo; CLI to execute commands for the majority of this lab.&#xA;Login using API endpoint and remember to add the &#39;--insecure-skip-tls-verify=true&#39; flag $ oc login https://api.example.redhatgov.io:6443 --insecure-skip-tls-verify=true Authentication required for https://api.example.redhatgov.io:6443 (openshift) Username: userYOUR# Password: Login successful. The instructor will have preconfigured your projects for you.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/rhel_8/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/security_containers/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/security_openshift/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/setup/</guid>
-      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for the workshopname.
- https://&amp;lt;workshopname&amp;gt;.master.&amp;lt;student number&amp;gt;.redhatgov.io:8888   After logging in, you should see a shell.</description>
+      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for the workshopname.&#xA;https://&amp;lt;workshopname&amp;gt;.master.&amp;lt;student number&amp;gt;.redhatgov.io:8888 After logging in, you should see a shell.&#xA;Figure 1: wetty Important Be sure you can log in to your instances.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/selinux_policy/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/setup/</guid>
-      <description>What you will learn: Cockpit (Browser-based Admin Interface) This lab provides a quick tour of the browser based admin interface client &#39;Cockpit&#39;. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Cockpit Use this URL to access the Cockpit node, just change the workshop name (if applicable). Ask your instructor for the workshop name.</description>
+      <description>What you will learn: Cockpit (Browser-based Admin Interface) This lab provides a quick tour of the browser based admin interface client &amp;#39;Cockpit&amp;#39;. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Cockpit Use this URL to access the Cockpit node, just change the workshop name (if applicable). Ask your instructor for the workshop name.&#xA;https://node-0.example.redhatgov.io:9090/system/terminal The login screen looks like this:</description>
     </item>
-    
     <item>
       <title>The Setup</title>
       <link>/workshops/source_to_image/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/setup/</guid>
-      <description>Step 1 - Log in to the Web User Interface The workshop moderator will provide you with the URL, your username, and password.
-OpenShift WebUI Login        Step 2 - Create a Project for Your Wetty Terminal Create a new project by clicking the &amp;ldquo;New Project&amp;rdquo; button in the upper right of the WebUI.
-Create a Project        Step 3 - Name Your Project Name your project as follows.</description>
+      <description>Step 1 - Log in to the Web User Interface The workshop moderator will provide you with the URL, your username, and password.&#xA;OpenShift WebUI Login Step 2 - Create a Project for Your Wetty Terminal Create a new project by clicking the &amp;ldquo;New Project&amp;rdquo; button in the upper right of the WebUI.&#xA;Create a Project Step 3 - Name Your Project Name your project as follows.&#xA;wetty-userYOUR# Name the Project Step 4 - Add Wetty to the Project In the Search Catalog bar, enter the name of the template to search for, in this case wetty-persistant.</description>
     </item>
-    
     <item>
       <title>Traffic Control - Circuit Breaking</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/</guid>
-      <description>Circuit Breaking Your Services Fault Injection lets you see how the service mesh behaves when there are failures in network calls to a specific service. But how do you protect a service if it has overloaded or failing instances serving traffic? Ideally, you would like to identify an instance that is failing and prevent clients from connecting to it once it meets a certain threshold.
-In OpenShift, an instance is equivalent to a Kubernetes pod running the microservice.</description>
+      <description>Circuit Breaking Your Services Fault Injection lets you see how the service mesh behaves when there are failures in network calls to a specific service. But how do you protect a service if it has overloaded or failing instances serving traffic? Ideally, you would like to identify an instance that is failing and prevent clients from connecting to it once it meets a certain threshold.&#xA;In OpenShift, an instance is equivalent to a Kubernetes pod running the microservice.</description>
     </item>
-    
     <item>
       <title>Traffic Control - Fault Injection</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/</guid>
-      <description>Testing Resiliency with Fault Injection Your application is working great now with the new version of the user profile service. But the previous version caused performance issues, and future updates may cause issues in other areas of the application. How can you test how your application behaves when a failure occurs?
-You need a way to simulate failure in the service mesh. By doing so, you can test if your application functions correctly in a degraded state.</description>
+      <description>Testing Resiliency with Fault Injection Your application is working great now with the new version of the user profile service. But the previous version caused performance issues, and future updates may cause issues in other areas of the application. How can you test how your application behaves when a failure occurs?&#xA;You need a way to simulate failure in the service mesh. By doing so, you can test if your application functions correctly in a degraded state.</description>
     </item>
-    
     <item>
       <title>Traffic Control - Routing Traffic</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/</guid>
-      <description>Basics on Routing Traffic Through the Mesh One of Istio&amp;rsquo;s core capabilities is the ability to dynamically control how services communicate without modifying the application code itself. The general concept is called Traffic Management. It allows you to do things such as A/B test, canary rollouts, rollbacks, and more.
-The two core API objects for traffic management are the Virtual Service and the Destination Rule. The destination rule is for the owner of a microservice - what versions do I expose and what happens to traffic before it reaches my service?</description>
+      <description>Basics on Routing Traffic Through the Mesh One of Istio&amp;rsquo;s core capabilities is the ability to dynamically control how services communicate without modifying the application code itself. The general concept is called Traffic Management. It allows you to do things such as A/B test, canary rollouts, rollbacks, and more.&#xA;The two core API objects for traffic management are the Virtual Service and the Destination Rule. The destination rule is for the owner of a microservice - what versions do I expose and what happens to traffic before it reaches my service?</description>
     </item>
-    
     <item>
       <title>Traffic Control - Traffic Splitting</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/</guid>
-      <description>Splitting Traffic Amongst Service Versions It&amp;rsquo;s time to fix the performance issue of the application. Previously, you deployed a new version of the application and routed 100% of traffic to the new version. This time, you&amp;rsquo;ll use Istio traffic routing to do canary rollouts and split traffic.
-Feature Fix The code to fix the performance issue of the user profile service has already been written for you on the &amp;lsquo;workshop-feature-fix&amp;rsquo; branch.</description>
+      <description>Splitting Traffic Amongst Service Versions It&amp;rsquo;s time to fix the performance issue of the application. Previously, you deployed a new version of the application and routed 100% of traffic to the new version. This time, you&amp;rsquo;ll use Istio traffic routing to do canary rollouts and split traffic.&#xA;Feature Fix The code to fix the performance issue of the user profile service has already been written for you on the &amp;lsquo;workshop-feature-fix&amp;rsquo; branch.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/agile_integrations_ci/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser.
-  Chrome is the preferred browser for this workshop  </description>
+      <description>Prerequisites This workshop is done entirely through the browser.&#xA;Chrome is the preferred browser for this workshop </description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/agile_integrations_dev/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser.
-  Chrome is the preferred browser for this workshop  </description>
+      <description>Prerequisites This workshop is done entirely through the browser.&#xA;Chrome is the preferred browser for this workshop </description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/openshift_101_dcmetromap/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser, but you do need a free personal GitHub account.
- Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.
- Create GitHub Account Download Git Client (optional)   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser, but you do need a free personal GitHub account.&#xA;Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.&#xA;Create GitHub Account Download Git Client (optional) &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/openshift_4_101/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser, but you do need a free personal GitHub account.
- Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.
- Create GitHub Account   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.4); -webkit-animation-name: fadeIn; -webkit-animation-duration: 0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser, but you do need a free personal GitHub account.&#xA;Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.&#xA;Create GitHub Account &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/openshift_4_101_dynatrace/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser, but you do need a free personal GitHub account.
- Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.
- Create GitHub Account Download Git Client (optional)   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser, but you do need a free personal GitHub account.&#xA;Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.&#xA;Create GitHub Account Download Git Client (optional) &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/secure_software_factory/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser.
-  Chrome is the preferred browser for this workshop   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.4); -webkit-animation-name: fadeIn; -webkit-animation-duration: 0.4s; animation-name: fadeIn; animation-duration: 0.4s } .modal-content { position: fixed; bottom: 0; background-color: #fefefe; width: 100%; -webkit-animation-name: slideIn; -webkit-animation-duration: 0.4s; animation-name: slideIn; animation-duration: 0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser.&#xA;Chrome is the preferred browser for this workshop &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Welcome to OpenShift</title>
       <link>/workshops/agile_integrations_ci/openshift/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/openshift/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
     </item>
-    
     <item>
       <title>Welcome to OpenShift</title>
       <link>/workshops/agile_integrations_dev/openshift/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/openshift/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
     </item>
-    
     <item>
       <title>Workshop is Done</title>
       <link>/workshops/cloudforms41/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/wrapup/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the CloudForms environment. And hopefully, you have a deeper understanding of how CloudForms simplifies IT, providing unified management and operations in a hybrid environment.
-As your IT infrastructure progresses from traditional virtualization toward an Infrastructure-as-a-Service (IaaS) model, CloudForms evolves, protecting your investments and providing consistent user experience and functionality.
-Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore the web console.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the CloudForms environment. And hopefully, you have a deeper understanding of how CloudForms simplifies IT, providing unified management and operations in a hybrid environment.&#xA;As your IT infrastructure progresses from traditional virtualization toward an Infrastructure-as-a-Service (IaaS) model, CloudForms evolves, protecting your investments and providing consistent user experience and functionality.&#xA;Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore the web console.</description>
     </item>
-    
     <item>
       <title>Workshop is done!</title>
       <link>/workshops/jdv_dev/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/wrapup/</guid>
-      <description>Congratulations  You imported 3 different disparate datasources and exposed them as data services. You also combined them into a federated view and applied role based security. Congratulations!  Additional resources  JDV Documentation Teiid, upstream project for JDV odata, documentation for REST data services. JDV uses odata(v2) and odata(v4). V4 must be called with the context of /odata4 [Teiid Examples] (https://github.com/teiid/teiid-embedded-examples). Github with various source examples  </description>
+      <description>Congratulations You imported 3 different disparate datasources and exposed them as data services. You also combined them into a federated view and applied role based security. Congratulations! Additional resources JDV Documentation Teiid, upstream project for JDV odata, documentation for REST data services. JDV uses odata(v2) and odata(v4). V4 must be called with the context of /odata4 [Teiid Examples] (https://github.com/teiid/teiid-embedded-examples). Github with various source examples </description>
     </item>
-    
     <item>
       <title>Wrap Up</title>
       <link>/workshops/security_containers/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Container Security that you can apply in your daily role.
- What do you think? How can we help you understand Container Security better?
- Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your Container education.
- This Participant Guide will remain active for the next two weeks.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Container Security that you can apply in your daily role.&#xA;What do you think? How can we help you understand Container Security better?&#xA;Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your Container education.&#xA;This Participant Guide will remain active for the next two weeks.</description>
     </item>
-    
     <item>
       <title>Wrap Up</title>
       <link>/workshops/security_openshift/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about OpenShift Security that you can apply in your daily role.
- What do you think? How can we help you understand OpenShift Security better?
- Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your OpenShift education.
- This Participant Guide will remain active for the next two weeks.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about OpenShift Security that you can apply in your daily role.&#xA;What do you think? How can we help you understand OpenShift Security better?&#xA;Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your OpenShift education.&#xA;This Participant Guide will remain active for the next two weeks.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/ansible_automation/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/ansible_tower_azure/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/ansible_tower_intro/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/containers_101/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/wrapup/</guid>
-      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.
- What do you think? How can we better help you understand Linux container concepts?
- For more in depth overview and examples for working with containers and RHEL check out this link.
- Thank you for your time and participation!
-   </description>
+      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.&#xA;What do you think? How can we better help you understand Linux container concepts?&#xA;For more in depth overview and examples for working with containers and RHEL check out this link.&#xA;Thank you for your time and participation!</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/containers_the_hard_way/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/wrapup/</guid>
-      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.
- We explored Linux Namespaces and the unshare command in great depth. Obviously container enginers make heavy use of these namespaces. Their job is to orchestrate the namespaces, OverlayFS, image files, and active containers so you don&amp;#8217;t have to. Obviously, you wouldn&amp;#8217;t run containers this way in production, but there may be times that you&amp;#8217;d like to make use of namespaces.</description>
+      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.&#xA;We explored Linux Namespaces and the unshare command in great depth. Obviously container enginers make heavy use of these namespaces. Their job is to orchestrate the namespaces, OverlayFS, image files, and active containers so you don’t have to. Obviously, you wouldn’t run containers this way in production, but there may be times that you’d like to make use of namespaces.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/rhel_8/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve enjoyed learning about all the goodness that is RHEL 8!
- What do you think? How can we help you understand new RHEL features better?
- This Participant Guide will remain active for the next two weeks. Please take advantage of it by downloading RHEL8 and installing a test host or VM back at your organization.
- Thank you for your time and participation!</description>
+      <description>That wraps up what we have planned for today. We hope you’ve enjoyed learning about all the goodness that is RHEL 8!&#xA;What do you think? How can we help you understand new RHEL features better?&#xA;This Participant Guide will remain active for the next two weeks. Please take advantage of it by downloading RHEL8 and installing a test host or VM back at your organization.&#xA;Thank you for your time and participation!</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/selinux_policy/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about SELinux policies that you can apply in your daily role.
- What do you think? How can we help you understand SELinux better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your SELinux education.
- This Participant Guide will remain active for the next two weeks.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about SELinux policies that you can apply in your daily role.&#xA;What do you think? How can we help you understand SELinux better?&#xA;Before you leave, check out the Resources below; you will find useful links that will further your SELinux education.&#xA;This Participant Guide will remain available. Please take advantage of it by creating your own SELinux policy back at your organization.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/jr-sa/index.html b/jr-sa/index.html
index 0afcd5055..8c80c2e64 100644
--- a/jr-sa/index.html
+++ b/jr-sa/index.html
@@ -447,7 +447,7 @@ <h1 class="display-1 text-center">For more information, send your contact inform
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/sitemap.xml b/sitemap.xml
index 62a5a557e..66f7d4ef0 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,1293 +1,653 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
   xmlns:xhtml="http://www.w3.org/1999/xhtml">
-  
   <url>
     <loc>/events/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/jr-sa/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/readme/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_10/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_11/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_12/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/pki_workshop/unit_lessons/unit_9/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/readme/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/about/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_intro/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_ansible/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/conclusion/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab99-conclusion/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/contact/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/dynatrace_openshift/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_intro/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_intro/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.1/</loc>
-  </url>
-  
-  <url>
-    <loc>/workshops/selinux_policy/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/workshops/selinux_policy/exercise1.1/</loc>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.1/</loc>
-  </url>
-  
-  <url>
-    <loc>/workshops/ansible_automation/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise1.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/workshops/ansible_automation/exercise1.1/</loc>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.10/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.11/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.12/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.13/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.14/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.15/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.16/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.17/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.18/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.19/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.20/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/workshops/selinux_policy/exercise1.3/</loc>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/exercise1.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/workshops/selinux_policy/exercise1.4/</loc>
+  </url><url>
     <loc>/workshops/containers_101/exercise1.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise1.5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise1.5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/exercise1.9/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/exercise1.9/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/exercise1.9/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/exercise1.9/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise10/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise2.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise2.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise2.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise2.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise2.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise2.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise2.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise2.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise2.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise2.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/exercise2.4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/workshops/selinux_policy/exercise2.5/</loc>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/exercise3.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/exercise3.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise4/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise5/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise6/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/exercise7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise7/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/exercise9/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/fin/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/fin/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/fin/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/fin/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/fin/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/fin/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/intro/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/1_introduction/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/keyterms/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/lab1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/containerize_app/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/gochat_s2i/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/login_tour_oc/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/login_tour_wetty/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/lab3/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/dice/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/run_the_app/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/source_to_image/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/lab2/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab01/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab01/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab01/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab02/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab02/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab02/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab03/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab03/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab03/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab04/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab04/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab04/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab05/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab05/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab05/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab06/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab06/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab06/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab07/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab07/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/lab07/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/lab08/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab08/</loc>
-  </url>
-  
-  <url>
-    <loc>/workshops/secure_software_factory/lab09/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/workshops/secure_software_factory/lab09/</loc>
+  </url><url>
     <loc>/workshops/rhosp_101/2_login_to_horizon/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab1-welcome/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab1-welcome/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab1-welcome/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab01-intro/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab10/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab10-labels/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab11/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab11-cicd/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab12-bluegreen/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab12/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab13/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab14/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab15/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab16/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab17/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/lab18/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab2-byocontainer/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab2-byocontainer/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab2-byodocker/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/3_managing_networks/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab02-registry/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab2.1-byocontainer/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab2.2-byocontainer/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab3-s2i/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab3-s2i/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab3-installagent/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/4_managing_floating_ip_addresses/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab03-podman/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab3.1-s2i/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab4-devmanage/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab4-devmanage/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/5_managing_security_groups/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab04-isolation/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab5-s2i/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/6_managing_images/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab5-rollbacks/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab5-rollbacks/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab05-selinux/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab6-replicationrecovery/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/7_managing_instances/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab06-inspecting/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab6.1-replicationrecovery/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab6.2-replicationrecovery/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab7-devmanage/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab7-labels/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab7-labels/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/8_using_the_cli/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab07-signing/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab8-cicd/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab8-cicd/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/9_heat/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab8-rollbacks/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_container_intro/lab08-builds/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/lab9-bluegreen/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/lab9-bluegreen/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/10_storage/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/login_tour_wetty/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/login_tour_wetty/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_serverless/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/strangling_the_monolith/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
+    <loc>/</loc>
+  </url><url>
     <loc>/workshops/rhel_8/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhosp_101/</loc>
-  </url>
-  
-  <url>
-    <loc>/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab5.3_prep/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_intro/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab1.3_installing/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/source_to_image/setup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_101_dcmetromap/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_4_101_dynatrace/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/secure_software_factory/prerequisites/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_ci/openshift/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/agile_integrations_dev/openshift/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/cloudforms41/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/jdv_dev/wrapup/</loc>
-  </url>
-  
-  <url>
-    <loc>/workshops/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_containers/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/security_openshift/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/alpha/ansible_with_rhocp_edge/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_automation/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_azure/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/ansible_tower_intro/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_101/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/containers_the_hard_way/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/rhel_8/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/selinux_policy/wrapup/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>/workshops/openshift_service_mesh_v1.0/</loc>
   </url>
-  
-</urlset>
\ No newline at end of file
+</urlset>
diff --git a/workshops/agile_integrations_ci/index.html b/workshops/agile_integrations_ci/index.html
index f3b141684..19ec760a5 100644
--- a/workshops/agile_integrations_ci/index.html
+++ b/workshops/agile_integrations_ci/index.html
@@ -372,7 +372,7 @@ <h1 id="labs">Labs</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/index.xml b/workshops/agile_integrations_ci/index.xml
index 1a7a511ff..a1608ad07 100644
--- a/workshops/agile_integrations_ci/index.xml
+++ b/workshops/agile_integrations_ci/index.xml
@@ -4,112 +4,71 @@
     <title>Agile Integrations Workshop - Citizen Integrator on Red Hat | Public Sector</title>
     <link>/workshops/agile_integrations_ci/</link>
     <description>Recent content in Agile Integrations Workshop - Citizen Integrator on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/agile_integrations_ci/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/agile_integrations_ci/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Lab 01 - API Design</title>
       <link>/workshops/agile_integrations_ci/lab01/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab01/</guid>
-      <description>Lab 1 API Design Create an OpenAPI Specification using Apicurio Studio  Duration: 10 mins Audience: API Owner, Product Manager, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
+      <description>Lab 1 API Design Create an OpenAPI Specification using Apicurio Studio Duration: 10 mins Audience: API Owner, Product Manager, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
     </item>
-    
     <item>
       <title>Lab 02 - API Mocking</title>
       <link>/workshops/agile_integrations_ci/lab02/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab02/</guid>
-      <description>Lab 2 API Mocking Bring your APIs to life  Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers  
-&amp;lt;img src=&amp;rdquo;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
+      <description>Lab 2 API Mocking Bring your APIs to life Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers &amp;lt;img src=&amp;quot;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
     </item>
-    
     <item>
       <title>Lab 03 - Fuse Online</title>
       <link>/workshops/agile_integrations_ci/lab03/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab03/</guid>
-      <description>Lab 3 Fuse Online  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop and deploy the APIs. Here is how to create a simple API with Fuse Online.
-Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
+      <description>Lab 3 Fuse Online Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop and deploy the APIs. Here is how to create a simple API with Fuse Online.&#xA;Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
     </item>
-    
     <item>
       <title>Lab 04 - Managing API Endpoints</title>
       <link>/workshops/agile_integrations_ci/lab04/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab04/</guid>
-      <description>Lab 4 Managing API Endpoints Take control of your APIs  Duration: 15 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them, and for what purpose. You also need to begin to track usage of these different users to know who is or is not succeeding in their usage.</description>
+      <description>Lab 4 Managing API Endpoints Take control of your APIs Duration: 15 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them, and for what purpose. You also need to begin to track usage of these different users to know who is or is not succeeding in their usage.</description>
     </item>
-    
     <item>
       <title>Lab 05 - API Security</title>
       <link>/workshops/agile_integrations_ci/lab05/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab05/</guid>
-      <description>Lab 5 API Security Securing APIs with OpenID Connect and Red Hat Single Sign On  Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Once you have APIs in your organization and have applications being written, you also want to be sure in many cases that the various types of users of the APIs are correctly authenticated. In this lab you will discover how to set up the widely used OpenID connect pattern for Authentication.</description>
+      <description>Lab 5 API Security Securing APIs with OpenID Connect and Red Hat Single Sign On Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Once you have APIs in your organization and have applications being written, you also want to be sure in many cases that the various types of users of the APIs are correctly authenticated. In this lab you will discover how to set up the widely used OpenID connect pattern for Authentication.</description>
     </item>
-    
     <item>
       <title>Lab 06 - API Developer Portal</title>
       <link>/workshops/agile_integrations_ci/lab06/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab06/</guid>
-      <description>Lab 6 API Developer Portal Publishing APIs to Developer Portal  Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview The focal point of your developers experience is the API developer portal, and the level of effort you put into it will directly correlate to the level of success of your API program, and API developer engagement.
-Why Red Hat? Red Hat 3scale API Management Solution provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions, and help increase API adoption.</description>
+      <description>Lab 6 API Developer Portal Publishing APIs to Developer Portal Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview The focal point of your developers experience is the API developer portal, and the level of effort you put into it will directly correlate to the level of success of your API program, and API developer engagement.&#xA;Why Red Hat? Red Hat 3scale API Management Solution provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions, and help increase API adoption.</description>
     </item>
-    
     <item>
       <title>Lab 07 - Testing Your Application</title>
       <link>/workshops/agile_integrations_ci/lab07/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/lab07/</guid>
-      <description>Lab 7 Testing the International Inc. Locations webpage Testing your web application  Duration: 10 mins Audience: API Consumers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview This lab demonstrates the International Inc. Locations page using our newly authenticated locations API.
-Why Red Hat? Applications can be built from many technologies. In this case we use a simple web application, but a wide range of Red Hat and non-Red Hat technologies could be used.</description>
+      <description>Lab 7 Testing the International Inc. Locations webpage Testing your web application Duration: 10 mins Audience: API Consumers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview This lab demonstrates the International Inc. Locations page using our newly authenticated locations API.&#xA;Why Red Hat? Applications can be built from many technologies. In this case we use a simple web application, but a wide range of Red Hat and non-Red Hat technologies could be used.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/agile_integrations_ci/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser.
-  Chrome is the preferred browser for this workshop  </description>
+      <description>Prerequisites This workshop is done entirely through the browser.&#xA;Chrome is the preferred browser for this workshop </description>
     </item>
-    
     <item>
       <title>Welcome to OpenShift</title>
       <link>/workshops/agile_integrations_ci/openshift/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/openshift/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/agile_integrations_ci/lab01/index.html b/workshops/agile_integrations_ci/lab01/index.html
index e47ee9237..56f8032ce 100644
--- a/workshops/agile_integrations_ci/lab01/index.html
+++ b/workshops/agile_integrations_ci/lab01/index.html
@@ -324,7 +324,7 @@ <h3 id="create-an-openapi-specification-using-apicurio-studio">Create an OpenAPI
 <li>Duration: 10 mins</li>
 <li>Audience: API Owner, Product Manager, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-01.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-01.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -337,11 +337,11 @@ <h3 id="step-1-creating-apis-with-apicurio-studio">Step 1: Creating APIs with Ap
 </li>
 <li>
 <p>Log in using your designated user and password.</p>
-<p><br>&lt;img src=&rdquo;../images/design-01.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-01.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Create New API</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-03.png &ldquo;Create New API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-03.png &ldquo;Create New API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Create a brand new API by completing the following information:</p>
@@ -350,14 +350,14 @@ <h3 id="step-1-creating-apis-with-apicurio-studio">Step 1: Creating APIs with Ap
 <li>Name: <strong>Locations-UserX</strong> (Replace <em>X</em> with your user number)</li>
 <li>Description: <strong>Locations API</strong></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/design-04.png &ldquo;Create API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-04.png &ldquo;Create API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Create API</strong>.</p>
 </li>
 <li>
 <p>Finally, click on <strong>Edit API</strong> to start editing your newly created API.</p>
-<p><br>&lt;img src=&rdquo;../images/design-05.png &ldquo;Edit API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-05.png &ldquo;Edit API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-editing-apis">Step 2: Editing APIs</h3>
@@ -366,7 +366,7 @@ <h3 id="step-2-editing-apis">Step 2: Editing APIs</h3>
 <ol>
 <li>
 <p>Time to prepare our data definitions for the API. Click on the <strong>Add a datatype</strong> link under the <em>Data Types</em>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-15.png &ldquo;Add Datatype&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-15.png &ldquo;Add Datatype&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Fill in the <em>Name</em> field with the value <strong>location</strong>. Expand the <em>Enter the JSON Example (optional)</em> to paste the following example, then click <strong>Save</strong>:</p>
@@ -376,26 +376,26 @@ <h3 id="step-2-editing-apis">Step 2: Editing APIs</h3>
 </li>
 <li>
 <p>JSON Example:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"><span style="color:#f92672">{</span>
-    <span style="color:#e6db74">&#34;id&#34;</span>: 1,
-    <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc Corporate Office&#34;</span>,
-    <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
-        <span style="color:#e6db74">&#34;lat&#34;</span>: 51.5013673,
-        <span style="color:#e6db74">&#34;lng&#34;</span>: -0.1440787
-    <span style="color:#f92672">}</span>,
-    <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;headquarter&#34;</span>,
-    <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
-<span style="color:#f92672">}</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span><span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;id&#34;</span>: 1,
+</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc Corporate Office&#34;</span>,
+</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;lat&#34;</span>: 51.5013673,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;lng&#34;</span>: -0.1440787
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">}</span>,
+</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;headquarter&#34;</span>,
+</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">}</span>
+</span></span></code></pre></div></li>
 <li>
 <p>Choose to create a REST Resource with the Data Type: <strong>No Resource</strong></p>
 </li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/design-16.png &ldquo;JSON Example&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-16.png &ldquo;JSON Example&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Apicurio automatically tries to detect the data types from the provided example.</p>
-<p><br>&lt;img src=&rdquo;../images/design-17.png &ldquo;Definition Data Types&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-17.png &ldquo;Definition Data Types&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>Time to start creating some paths</em>.</p>
 </li>
 </ol>
@@ -405,14 +405,14 @@ <h4 id="3a-add-locations-path-with-get-method">3a: Add <code>/locations</code> p
 <ol>
 <li>
 <p>Click on the <strong>Add a path</strong> link under the <em>Paths</em> section. APIs need at least one path.</p>
-<p><br>&lt;img src=&rdquo;../images/design-06.png &ldquo;Add Path&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-06.png &ldquo;Add Path&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Fill in the new resource path with the following information:</p>
 <ul>
 <li>Path: <strong>/locations</strong></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/design-07.png &ldquo;Path&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-07.png &ldquo;Path&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click <strong>Add</strong>.</p>
@@ -420,37 +420,37 @@ <h4 id="3a-add-locations-path-with-get-method">3a: Add <code>/locations</code> p
 </li>
 <li>
 <p>Click <strong>Create Operation</strong> under the <em>GET</em> operation.</p>
-<p><br>&lt;img src=&rdquo;../images/design-08.png &ldquo;Create Operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-08.png &ldquo;Create Operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the green <strong>GET</strong> operation button to edit the operation information.</p>
-<p><br>&lt;img src=&rdquo;../images/design-09.png &ldquo;Get Operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-09.png &ldquo;Get Operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>As you can notice, Apicurio Editor guides you with warning for the elements missing in your design</em>.</p>
 </li>
 <li>
 <p>Click on the <strong>Add a response</strong> link under <em>Responses</em> to edit the response for this operation.</p>
-<p><br>&lt;img src=&rdquo;../images/design-58.png &ldquo;Add Response&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-58.png &ldquo;Add Response&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Leave the <strong>200</strong> option selected in the  <em>Response Status Code</em> combo box and click on <strong>Add</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-11.png &ldquo;Add Response Code&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-11.png &ldquo;Add Response Code&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down to the bottom of the page. Move your mouse over the <strong>200 OK</strong> response to enable the options. Click the <em>No response media types defined</em> drop-down. Now click on the <strong>Add Media Type</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-59.png &ldquo;Add Media Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-59.png &ldquo;Add Media Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Add</em> button to accept <strong>application/json</strong> as the Media Type.</p>
-<p><br>&lt;img src=&rdquo;../images/design-18.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-18.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Type</em> dropdown and select <strong>Array</strong> and <strong>location</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-18a.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-18a.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Add an example</strong> link to add a Response Example.</p>
 <p><em>This will be useful to mock your API in the next lab</em>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-19.png &ldquo;Add Example&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-19.png &ldquo;Add Example&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Fill in the information for your response example:</p>
@@ -460,49 +460,49 @@ <h4 id="3a-add-locations-path-with-get-method">3a: Add <code>/locations</code> p
 </li>
 <li>
 <p>Example:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"><span style="color:#f92672">[</span>
-    <span style="color:#f92672">{</span>
-        <span style="color:#e6db74">&#34;id&#34;</span>: 1,
-        <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc Corporate Office&#34;</span>,
-        <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
-            <span style="color:#e6db74">&#34;lat&#34;</span>: 51.5013673,
-            <span style="color:#e6db74">&#34;lng&#34;</span>: -0.1440787
-        <span style="color:#f92672">}</span>,
-        <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;headquarter&#34;</span>,
-        <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
-    <span style="color:#f92672">}</span>,
-    <span style="color:#f92672">{</span>
-        <span style="color:#e6db74">&#34;id&#34;</span>: 2,
-        <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc North America&#34;</span>,
-        <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
-            <span style="color:#e6db74">&#34;lat&#34;</span>: 40.6976701,
-            <span style="color:#e6db74">&#34;lng&#34;</span>: -74.259876
-        <span style="color:#f92672">}</span>,
-        <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;office&#34;</span>,
-        <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
-    <span style="color:#f92672">}</span>,
-    <span style="color:#f92672">{</span>
-        <span style="color:#e6db74">&#34;id&#34;</span>: 3,
-        <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc France&#34;</span>,
-        <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
-            <span style="color:#e6db74">&#34;lat&#34;</span>: 48.859,
-            <span style="color:#e6db74">&#34;lng&#34;</span>: 2.2069746
-        <span style="color:#f92672">}</span>,
-        <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;office&#34;</span>,
-        <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
-    <span style="color:#f92672">}</span>
-<span style="color:#f92672">]</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span><span style="color:#f92672">[</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;id&#34;</span>: 1,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc Corporate Office&#34;</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#e6db74">&#34;lat&#34;</span>: 51.5013673,
+</span></span><span style="display:flex;"><span>            <span style="color:#e6db74">&#34;lng&#34;</span>: -0.1440787
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">}</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;headquarter&#34;</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">}</span>,
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;id&#34;</span>: 2,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc North America&#34;</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#e6db74">&#34;lat&#34;</span>: 40.6976701,
+</span></span><span style="display:flex;"><span>            <span style="color:#e6db74">&#34;lng&#34;</span>: -74.259876
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">}</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;office&#34;</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">}</span>,
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;id&#34;</span>: 3,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;name&#34;</span>: <span style="color:#e6db74">&#34;International Inc France&#34;</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;location&#34;</span>: <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#e6db74">&#34;lat&#34;</span>: 48.859,
+</span></span><span style="display:flex;"><span>            <span style="color:#e6db74">&#34;lng&#34;</span>: 2.2069746
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">}</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;office&#34;</span>,
+</span></span><span style="display:flex;"><span>        <span style="color:#e6db74">&#34;status&#34;</span>: <span style="color:#e6db74">&#34;1&#34;</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">]</span>
+</span></span></code></pre></div></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/design-20.png &ldquo;Response Example&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-20.png &ldquo;Response Example&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the drop-down next to the <code>No description</code> message, and enter <code>Returns an array of location records</code> as the description.  Click the check-mark button to accept the description.</p>
-<p><br>&lt;img src=&rdquo;../images/design-54.png &ldquo;Enter description&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-54.png &ldquo;Enter description&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the green <strong>GET</strong> operation button to highlight the list of operations.</p>
-<p><br>&lt;img src=&rdquo;../images/design-31.png &ldquo;Get Operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-31.png &ldquo;Get Operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h4 id="3b-update-locations-path-with-post-method">3b: Update <code>/locations</code> path with POST method</h4>
@@ -510,35 +510,35 @@ <h4 id="3b-update-locations-path-with-post-method">3b: Update <code>/locations</
 <ol>
 <li>
 <p>Click on the <strong>Create Operation</strong> link under <em>POST</em> to create a new POST operation.</p>
-<p><br>&lt;img src=&rdquo;../images/design-32.png &ldquo;Create POST operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-32.png &ldquo;Create POST operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the orange <strong>POST</strong> button to edit the operation.</p>
-<p><br>&lt;img src=&rdquo;../images/design-33.png &ldquo;Edit POST operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-33.png &ldquo;Edit POST operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Add a response</strong> link.</p>
-<p><br>&lt;img src=&rdquo;../images/design-34.png &ldquo;Edit POST operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-34.png &ldquo;Edit POST operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Set the <strong>Response Status Code</strong> value to <code>201</code>.  Click Add.</p>
-<p><br>&lt;img src=&rdquo;../images/design-35.png &ldquo;Edit POST operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-35.png &ldquo;Edit POST operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the drop-down next to the <code>No description</code> message, and enter <code>Creates a new location record</code> as the description.  Click the check-mark button to accept the description.</p>
-<p><br>&lt;img src=&rdquo;../images/design-55.png &ldquo;Enter description&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-55.png &ldquo;Enter description&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down to the bottom of the page. Move your mouse over the <strong>201 Created</strong> response to enable the options. Click the <em>No response media types defined</em> drop-down. Now click on the <strong>Add Media Type</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-60.png &ldquo;Add Media Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-60.png &ldquo;Add Media Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Add</em> button to accept <strong>application/json</strong> as the Media Type.</p>
-<p><br>&lt;img src=&rdquo;../images/design-18.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-18.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Type</em> dropdown and select <strong>location</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-36.png &ldquo;Location&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-36.png &ldquo;Location&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h4 id="3c-add-locationsid-path-with-get-method">3c: Add <code>/locations/{id}</code> path with GET method</h4>
@@ -546,43 +546,43 @@ <h4 id="3c-add-locationsid-path-with-get-method">3c: Add <code>/locations/{id}</
 <ol>
 <li>
 <p>Now we need to create another path.  Click on the <code>+</code> symbol to add a new path, then enter <code>/locations/{id}</code> for the <strong>Path</strong> property.  Click <strong>Add</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-37.png &ldquo;Location&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-37.png &ldquo;Location&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll over the <code>id</code> <em>Path Parameter</em> value, then click the <strong>Create</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-37a.png &ldquo;Location&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-37a.png &ldquo;Location&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the drop-down arrow, then update the <code>id</code> Path Parameter by selecting <code>Integer</code> as the <strong>Type</strong> and <code>32-Bit Integer</code> as the sub-type.</p>
-<p><br>&lt;img src=&rdquo;../images/design-38.png &ldquo;Path Parameter&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-38.png &ldquo;Path Parameter&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <code>Create Operation</code> button underneath <strong>GET</strong>, then click the green <strong>GET</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-39.png &ldquo;Path Parameter&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-39.png &ldquo;Path Parameter&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <strong>Add a response</strong> link under <em>Responses</em> to edit the response for this operation.</p>
-<p><br>&lt;img src=&rdquo;../images/design-10.png &ldquo;Add Response&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-10.png &ldquo;Add Response&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Leave the <strong>200</strong> option selected in the  <em>Response Status Code</em> combo box and click on <strong>Add</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-11.png &ldquo;Add Response Code&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-11.png &ldquo;Add Response Code&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down to the bottom of the page. Move your mouse over the <strong>200 OK</strong> response to enable the options. Click the <em>No response media types defined</em> drop-down. Now click on the <strong>Add Media Type</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-12.png &ldquo;Add Media Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-12.png &ldquo;Add Media Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Add</em> button to accept <strong>application/json</strong> as the Media Type.</p>
-<p><br>&lt;img src=&rdquo;../images/design-18.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-18.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Type</em> dropdown and select <strong>location</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-40.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-40.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the drop-down next to the <code>No description</code> message, and enter <code>Returns a single location record</code> as the description.  Click the check-mark button to accept the description.</p>
-<p><br>&lt;img src=&rdquo;../images/design-56.png &ldquo;Enter description&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-56.png &ldquo;Enter description&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h4 id="3d-add-locationsphoneid-path-with-get-method">3d: Add <code>/locations/phone/{id}</code> path with GET method</h4>
@@ -590,61 +590,61 @@ <h4 id="3d-add-locationsphoneid-path-with-get-method">3d: Add <code>/locations/p
 <ol>
 <li>
 <p>Now we need to create another path.  Click on the <code>+</code> symbol to add a new path, then enter <code>/locations/phone/{id}</code> for the <strong>Path</strong> property.  Click <strong>Add</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-41.png &ldquo;Location&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-41.png &ldquo;Location&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <code>Create Operation</code> button underneath <strong>Get</strong>, then click the green <strong>Get</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-42.png &ldquo;Get operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-42.png &ldquo;Get operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down to the <code>id</code> path parameter to highlight the row, and click the <code>Create</code> button that appears.</p>
-<p><br>&lt;img src=&rdquo;../images/design-53.png &ldquo;Get operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-53.png &ldquo;Get operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the drop-down arrow next to <code>No Type</code>, then update the <code>id</code> Path Parameter by selecting <code>Integer</code> as the <strong>Type</strong> and <code>32-Bit Integer</code> as the sub-type.</p>
-<p><br>&lt;img src=&rdquo;../images/design-64.png &ldquo;Path Parameter&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-64.png &ldquo;Path Parameter&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <strong>Add a response</strong> link under <em>Responses</em> to edit the response for this operation.</p>
-<p><br>&lt;img src=&rdquo;../images/design-61.png &ldquo;Add Response&rdquo; width=&quot;900&rdquo; /&gt;<br><br>)</p>
+<p><br>&lt;img src=&quot;../images/design-61.png &ldquo;Add Response&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br>)</p>
 </li>
 <li>
 <p>Leave the <strong>200</strong> option selected in the  <em>Response Status Code</em> combo box and click on <strong>Add</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-11.png &ldquo;Add Response Code&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-11.png &ldquo;Add Response Code&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down to the bottom of the page. Move your mouse over the <strong>200 OK</strong> response to enable the options. Click the <em>No response media types defined</em> drop-down. Now click on the <strong>Add Media Type</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/design-62.png &ldquo;Add Media Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-62.png &ldquo;Add Media Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Add</em> button to accept <strong>application/json</strong> as the Media Type.</p>
-<p><br>&lt;img src=&rdquo;../images/design-18.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-18.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <em>Type</em> dropdown and select <strong>location</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-63.png &ldquo;Location Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-63.png &ldquo;Location Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the drop-down next to the <code>No description</code> message, and enter <code>Returns a location record</code> as the description.  Click the check-mark button to accept the description.</p>
-<p><br>&lt;img src=&rdquo;../images/design-57.png &ldquo;Enter description&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-57.png &ldquo;Enter description&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-4-download-the-api-definition">Step 4: Download the API definition</h3>
 <ol>
 <li>
 <p>Click the <strong>Locations-UserX</strong> link to return to the API admin page.</p>
-<p><br>&lt;img src=&rdquo;../images/design-22.png &ldquo;Locations API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-22.png &ldquo;Locations API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>To start using your new API definition, display the API menu from the kebab link. Click the <strong>Download (YAML)</strong> option from the menu.</p>
-<p><br>&lt;img src=&rdquo;../images/design-23.png &ldquo;Download API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-23.png &ldquo;Download API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>This will start the download of your API definition file. It could take a few seconds to start the download. <strong>Save</strong> it to your local disk drive.</p>
 </li>
 <li>
 <p>You can open the file with any text editor. Take a look at the source file. Everything is there.</p>
-<p><br>&lt;img src=&rdquo;../images/design-24.png &ldquo;API Definition Source&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-24.png &ldquo;API Definition Source&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations!</em> You have created your first API definition based on the OpenAPI Specification  using Red Hat&rsquo;s Apicurio. Don&rsquo;t lose track of the file, you will use this definition for your next lab.</p>
@@ -706,7 +706,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/lab02/index.html b/workshops/agile_integrations_ci/lab02/index.html
index b1ce5f77d..93d89e6f4 100644
--- a/workshops/agile_integrations_ci/lab02/index.html
+++ b/workshops/agile_integrations_ci/lab02/index.html
@@ -324,7 +324,7 @@ <h3 id="bring-your-apis-to-life">Bring your APIs to life</h3>
 <li>Duration: 20 mins</li>
 <li>Audience: Developers, Architects, Testers, Quality Engineers</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-02.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-02.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -337,36 +337,36 @@ <h3 id="step-1-create-a-microcks-job">Step 1: Create a Microcks Job</h3>
 </li>
 <li>
 <p>Log in into Microcks using your designated user and password.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-09.png &ldquo;Openshift Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-09.png &ldquo;Openshift Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You are now in the main Microcks page. Click the <strong>Importers</strong> button to access the Importers page.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-11.png &ldquo;Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-11.png &ldquo;Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Upload</strong> button to upload the <strong>Locations-UserX.yaml</strong> spec generated from Lab 1.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-12.png &ldquo;Upload Spec&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-12.png &ldquo;Upload Spec&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Upload</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-13.png &ldquo;Upload&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-13.png &ldquo;Upload&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>Congratulations! The spec is successfully imported</em></p>
 </li>
 <li>
 <p>Navigate to <strong>APIs | Services</strong> tab.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-14.png &ldquo;Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-14.png &ldquo;Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the link for your username. eg: <strong>Locations-User1</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-15.png &ldquo;Select services&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-15.png &ldquo;Select services&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the arrow to expand the <strong>Operation GET /locations</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-16.png &ldquo;Mock Service&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-16.png &ldquo;Mock Service&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You can check that the example we added to the definition in <a href="lab01.md">Lab 1</a> will be used to return the mock values. Copy and save the <strong>Mocks URL</strong>, we will use that endpoint to test the REST mock service.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-17.png &ldquo;Mock Operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-17.png &ldquo;Mock Operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-test-the-rest-mock-service">Step 2: Test the REST Mock Service</h3>
@@ -374,19 +374,19 @@ <h3 id="step-2-test-the-rest-mock-service">Step 2: Test the REST Mock Service</h
 <ol>
 <li>
 <p>Open a browser window and navigate to:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://onlinecurl.com/
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://onlinecurl.com/
+</span></span></code></pre></div></li>
 <li>
 <p>Enter the copied URL from <strong>Step 9</strong>. It should look similar to this:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">http://microcks.apps.ocp-ai.redhatgov.io/rest/Locations-User1/1.0.0/locations
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>http://microcks.apps.ocp-ai.redhatgov.io/rest/Locations-User1/1.0.0/locations
+</span></span></code></pre></div></li>
 <li>
 <p>Click the <strong>START YOUR CURL</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-18.png &ldquo;cURL Service&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-18.png &ldquo;cURL Service&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>The page will load the response information from the service. You will be able to see the <em>RESPONSE HEADERS</em> and the actual <em>RESPONSE_BODY</em>. This last part contains the examples we add during the design phase.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-19.png &ldquo;cURL Response&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-19.png &ldquo;cURL Response&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations!</em> You have successfully configure a Microcks Job to create a REST mock service to test your API.</p>
@@ -442,7 +442,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/lab03/index.html b/workshops/agile_integrations_ci/lab03/index.html
index c7388776c..148da87c5 100644
--- a/workshops/agile_integrations_ci/lab03/index.html
+++ b/workshops/agile_integrations_ci/lab03/index.html
@@ -323,7 +323,7 @@ <h2 id="fuse-online">Fuse Online</h2>
 <li>Duration: 20 mins</li>
 <li>Audience: Developers and Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-03.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-03.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>When it comes to quick API development, you need both the integration experts as well as application developers to easily develop and deploy the APIs. Here is how to create a simple API with Fuse Online.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -342,19 +342,19 @@ <h3 id="step-1-create-database-connection">Step 1: Create database connection</h
 </li>
 <li>
 <p>The first time that you hit the Fuse Online URL, you will be presented with an <em>Authorize Access</em> page.  Click the <strong>Allow selected permissions</strong> button to accept the defaults.</p>
-<p><br>&lt;img src=&rdquo;../images/design-54.png &ldquo;Accept permissions&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-54.png &ldquo;Accept permissions&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Connections &gt; Create Connection</strong></p>
-<p><br>&lt;img src=&rdquo;../images/00-create-connection.png &ldquo;Create Connection&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-create-connection.png &ldquo;Create Connection&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Database</strong></p>
-<p><br>&lt;img src=&rdquo;../images/01-select-database.png &ldquo;Select Database&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/01-select-database.png &ldquo;Select Database&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Enter below values for Database Configuration</p>
-<pre><code>Connection URL: jdbc:postgresql://postgresql.international.svc:5432/sampledb
+<pre tabindex="0"><code>Connection URL: jdbc:postgresql://postgresql.international.svc:5432/sampledb
 Username      : dbuser
 Password      : password
 Schema        : &lt;blank&gt;
@@ -364,7 +364,7 @@ <h3 id="step-1-create-database-connection">Step 1: Create database connection</h
 <ol>
 <li>
 <p>Click <strong>Validate</strong> and verify if the connection is successful. Click <strong>Next</strong> to proceed.</p>
-<p><br>&lt;img src=&rdquo;../images/02-click-validate.png &ldquo;Validate&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/02-click-validate.png &ldquo;Validate&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Add Connection details:</p>
@@ -379,7 +379,7 @@ <h3 id="step-1-create-database-connection">Step 1: Create database connection</h
 </li>
 <li>
 <p>Click <strong>Create</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/03-connection-details.png &ldquo;Add Connection Details&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/03-connection-details.png &ldquo;Add Connection Details&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -390,19 +390,19 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 <ol>
 <li>
 <p>Click on <strong>Integrations &gt; Create Integration</strong></p>
-<p><br>&lt;img src=&rdquo;../images/04-create-integration.png &ldquo;Create Integration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/04-create-integration.png &ldquo;Create Integration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Choose <strong>Webhook</strong></p>
-<p><br>&lt;img src=&rdquo;../images/05-choose-weebhook.png &ldquo;Choose webhook&quot;Integration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/05-choose-weebhook.png &ldquo;Choose webhook&quot;Integration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on Incoming webhook</p>
-<p><br>&lt;img src=&rdquo;../images/06-incoming-webhook.png &ldquo;Add incoming webhook&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/06-incoming-webhook.png &ldquo;Add incoming webhook&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>It navigates to the Webhook Token screen. Click <strong>Next</strong></p>
-<p><br>&lt;img src=&rdquo;../images/07-webhook-configuration.png &ldquo;Webhook Configuration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/07-webhook-configuration.png &ldquo;Webhook Configuration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Define the Output Data Type.</p>
@@ -420,27 +420,27 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 </li>
 <li>
 <p>Click Done</p>
-<pre><code>{
-  &quot;id&quot;: 1,
-  &quot;name&quot;: &quot;Kamarhati&quot;,
-  &quot;type&quot;: &quot;Regional Branch&quot;,
-  &quot;status&quot;: &quot;1&quot;,
-  &quot;location&quot;: {
-    &quot;lat&quot;: &quot;-28.32555&quot;,
-    &quot;lng&quot;: &quot;-5.91531&quot;
+<pre tabindex="0"><code>{
+  &#34;id&#34;: 1,
+  &#34;name&#34;: &#34;Kamarhati&#34;,
+  &#34;type&#34;: &#34;Regional Branch&#34;,
+  &#34;status&#34;: &#34;1&#34;,
+  &#34;location&#34;: {
+    &#34;lat&#34;: &#34;-28.32555&#34;,
+    &#34;lng&#34;: &#34;-5.91531&#34;
   }
 }
-</code></pre><p><br> <br> &lt;img src=&rdquo;../images/08-data-type.png &ldquo;Data Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+</code></pre><p><br> <br> &lt;img src=&quot;../images/08-data-type.png &ldquo;Data Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
 <li>
 <p>Click on LocationDB from the catalog and then select Invoke SQL</p>
-<p><br>&lt;img src=&rdquo;../images/09-invoke-sql.png &ldquo;Invoke SQL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/09-invoke-sql.png &ldquo;Invoke SQL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Enter the SQL statement and click <strong>Done</strong>.</p>
-<pre><code></code></pre></li>
+<pre tabindex="0"><code></code></pre></li>
 </ol>
 <p>INSERT INTO locations (id,name,lat,lng,location_type,status) VALUES (:#id,:#name,:#lat,:#lng,:#location_type,:#status )
 ```</p>
@@ -449,11 +449,11 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 <ol>
 <li>
 <p>Click on Add step and select Data mapper</p>
-<p><br>&lt;img src=&rdquo;../images/11-data-mapper.png &ldquo;Data Mapper&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/11-data-mapper.png &ldquo;Data Mapper&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Drag and drop the matching <strong>Source</strong> Data types to all their corresponding <strong>Targets</strong> as per the following screenshot. When finished, click <strong>Done</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/12-configure-mapper.png &ldquo;Configure Mapper&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/12-configure-mapper.png &ldquo;Configure Mapper&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click <strong>Publish</strong> on the next screen</p>
@@ -463,7 +463,7 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 </li>
 <li>
 <p>Again Click <strong>Publish</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/13-publish-integration.png &ldquo;Publish Integration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/13-publish-integration.png &ldquo;Publish Integration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations</em>. You successfully published the integration. (Wait for few minutes to for the integration to be built and published)</p>
@@ -472,7 +472,7 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <ol>
 <li>
 <p>Copy the External URL per the below screenshot</p>
-<p><br>&lt;img src=&rdquo;../images/14-copy-URL.png &ldquo;Copy URL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/14-copy-URL.png &ldquo;Copy URL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Open a browser window and navigate to: <a href="https://onlinecurl.com/">https://onlinecurl.com/</a></p>
@@ -516,7 +516,7 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <li>&ndash;data (-d): {&ldquo;id&rdquo;: 101, &ldquo;name&rdquo;: &ldquo;Kamarhati&rdquo;, &ldquo;type&rdquo;: &ldquo;Regional Branch&rdquo;, &ldquo;status&rdquo;: &ldquo;1&rdquo;, &ldquo;location&rdquo;: { &ldquo;lat&rdquo;: &ldquo;-28.32555&rdquo;, &ldquo;lng&rdquo;: &ldquo;-5.91531&rdquo; }}</li>
 <li>&ndash;request (-X): POST</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/15-online-curl.png &ldquo;Online URL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/15-online-curl.png &ldquo;Online URL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -525,7 +525,7 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <ul>
 <li>
 <p>If you get an SSL error, please see the next step.</p>
-<p><br>&lt;img src=&rdquo;../images/16-response-header.png &ldquo;Response Header&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/16-response-header.png &ldquo;Response Header&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -534,31 +534,31 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <ul>
 <li>
 <p>Please make sure to use the your URL you copied and pasted</p>
-<pre><code>curl -k \
---header &quot;Content-Type: application/json&quot; \
+<pre tabindex="0"><code>curl -k \
+--header &#34;Content-Type: application/json&#34; \
 --request POST \
---data '{&quot;id&quot;: 101, &quot;name&quot;: &quot;Kamarhati&quot;, &quot;type&quot;: &quot;Regional Branch&quot;, &quot;status&quot;: &quot;1&quot;, &quot;location&quot;: { &quot;lat&quot;: &quot;-28.32555&quot;, &quot;lng&quot;: &quot;-5.91531&quot; }}' \
+--data &#39;{&#34;id&#34;: 101, &#34;name&#34;: &#34;Kamarhati&#34;, &#34;type&#34;: &#34;Regional Branch&#34;, &#34;status&#34;: &#34;1&#34;, &#34;location&#34;: { &#34;lat&#34;: &#34;-28.32555&#34;, &#34;lng&#34;: &#34;-5.91531&#34; }}&#39; \
 https://i-addlocation-tools1.apps.ocp-ai.redhatgov.io/webhook/KcZ3E86SUJTqIUsA8iB7Yb5Sa1KLp9cchnRO5twYnr6UTruYd1
 </code></pre></li>
 </ul>
 <ol>
 <li>
 <p>Click on <strong>Activity &gt; Refresh</strong> and verify if the newly record is created.</p>
-<p><br>&lt;img src=&rdquo;../images/17-activity-refresh.png &ldquo;Activity Refresh&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/17-activity-refresh.png &ldquo;Activity Refresh&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p><em>(Optional)</em> Visit the application URL in the browser from the Location Service created in the previous lab and verify if the record can be fetched.</p>
 </li>
 </ol>
 <p><strong>RESPONSE</strong></p>
-<pre><code>  {
-    &quot;id&quot; : 101,
-    &quot;name&quot; : &quot;Kamarhati&quot;,
-    &quot;type&quot; : &quot;Regional Branch&quot;,
-    &quot;status&quot; : &quot;1&quot;,
-    &quot;location&quot; : {
-      &quot;lat&quot; : &quot;-28.32555&quot;,
-      &quot;lng&quot; : &quot;-5.91531&quot;
+<pre tabindex="0"><code>  {
+    &#34;id&#34; : 101,
+    &#34;name&#34; : &#34;Kamarhati&#34;,
+    &#34;type&#34; : &#34;Regional Branch&#34;,
+    &#34;status&#34; : &#34;1&#34;,
+    &#34;location&#34; : {
+      &#34;lat&#34; : &#34;-28.32555&#34;,
+      &#34;lng&#34; : &#34;-5.91531&#34;
     }
   }
 </code></pre><h2 id="summary">Summary</h2>
@@ -612,7 +612,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/lab04/index.html b/workshops/agile_integrations_ci/lab04/index.html
index 9e3f61d6d..c08a8ad49 100644
--- a/workshops/agile_integrations_ci/lab04/index.html
+++ b/workshops/agile_integrations_ci/lab04/index.html
@@ -324,7 +324,7 @@ <h3 id="take-control-of-your-apis">Take control of your APIs</h3>
 <li>Duration: 15 mins</li>
 <li>Audience: API Owners, Product Managers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-04.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-04.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>Once you have APIs deployed in your environment, it becomes critically important to manage who may use them, and for what purpose. You also need to begin to track usage of these different users to know who is or is not succeeding in their usage. For this reason, in this lab, you will be adding management capabilities to the API to give you control and visibility of it&rsquo;s usage.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -411,8 +411,8 @@ <h3 id="step-1-define-your-api-proxy">Step 1: Define your API Proxy</h3>
 </li>
 <li>
 <p>Type in the <em>Pattern</em> text box the following:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">/locations
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>/locations
+</span></span></code></pre></div></li>
 <li>
 <p>Select <strong>locations_all</strong> as Method from the combo box.</p>
 <p><br><img src="../images/07b-getall-rule.png" width="900" /><br><br></p>
@@ -424,7 +424,7 @@ <h3 id="step-2-define-your-api-policies">Step 2: Define your API Policies</h3>
 <ol>
 <li>
 <p>Scroll down and expand the <strong>POLICIES</strong> section to define the allowed methods on our exposed API.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-01.png &ldquo;Policies&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-01.png &ldquo;Policies&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>The default policy in the Policy Chain is APIcast. This is the main policy and most of the times you want to keep it</em>.</p>
 </li>
 <li>
@@ -434,34 +434,34 @@ <h3 id="step-2-define-your-api-policies">Step 2: Define your API Policies</h3>
 </li>
 <li>
 <p>Click in the <strong>CORS</strong> link to add the policy.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-03.png &ldquo;CORS&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-03.png &ldquo;CORS&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Put your mouse over the right side of the policy name to enable the reorder of the chain. Drag and drop the CORS policy to the top of the chain.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-04.png &ldquo;Chain Order&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-04.png &ldquo;Chain Order&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Now <strong>CORS</strong> policy will be executed before the <strong>APIcast</strong>. Click the <strong>CORS</strong> link to edit the policy.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-05.png &ldquo;Cors Configuration&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-05.png &ldquo;Cors Configuration&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the <em>Edit Policy</em> section, click the green <strong>+</strong> button to add the allowed headers.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-06.png &ldquo;Add Allow Headers&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-06.png &ldquo;Add Allow Headers&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Type <strong>Authorization</strong> in the <em>Allowed headers</em> field.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-07.png &ldquo;Add Authorization Header&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-07.png &ldquo;Add Authorization Header&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Tick the <strong>allow_credentials</strong> checkbox and fill in with a star (<strong>*</strong>) the <em>allow_origin</em> text box.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-08.png &ldquo;Allow Origin&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-08.png &ldquo;Allow Origin&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click twice the green <strong>+</strong> button under <em>ALLOW_METHODS</em> to enable two combo boxes for the CORS allowed methods.</p>
 </li>
 <li>
 <p>Select <strong>GET</strong> from the first box and <strong>OPTIONS</strong> from the second box.</p>
-<p><br>&lt;img src=&rdquo;../images/policies-09.png &ldquo;Allow Methods&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/policies-09.png &ldquo;Allow Methods&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Submit</strong> button to save the policy configuration.</p>
@@ -473,26 +473,26 @@ <h3 id="step-3-configure-the-upstream-endpoint">Step 3: Configure the Upstream E
 <p>Scroll back to the top of the page. Fill in the information for accessing your API:</p>
 <ul>
 <li>
-<p>Private Base URL: <strong><a href="http://location-service.international.svc">http://location-service.international.svc</a>:8080</strong></p>
+<p>Private Base URL: <strong><a href="http://location-service.international.svc:8080">http://location-service.international.svc:8080</a></strong></p>
 </li>
 <li>
-<p>Staging Public Base URL: <strong><a href="https://location-userX-api-staging.amp.apps.ocp-ai.redhatgov.io">https://location-userX-api-staging.amp.apps.ocp-ai.redhatgov.io</a>:443</strong></p>
+<p>Staging Public Base URL: <strong><a href="https://location-userX-api-staging.amp.apps.ocp-ai.redhatgov.io:443">https://location-userX-api-staging.amp.apps.ocp-ai.redhatgov.io:443</a></strong></p>
 </li>
 <li>
-<p>Production Public Base URL: <strong><a href="https://location-userX-api.amp.apps.ocp-ai.redhatgov.io">https://location-userX-api.amp.apps.ocp-ai.redhatgov.io</a>:443</strong></p>
+<p>Production Public Base URL: <strong><a href="https://location-userX-api.amp.apps.ocp-ai.redhatgov.io:443">https://location-userX-api.amp.apps.ocp-ai.redhatgov.io:443</a></strong></p>
 </li>
 </ul>
 <p><em>Remember to replace the X with your user number</em>.</p>
 <p><em>We are using the internal API service, as we are deploying our services inside the same OpenShift cluster</em>.</p>
-<p><br>&lt;img src=&rdquo;../images/07-baseurl-configuration.png)</p>
+<p><br>&lt;img src=&quot;../images/07-baseurl-configuration.png)</p>
 </li>
 <li>
 <p>Scroll down to the <strong>API Test GET request</strong>.</p>
 </li>
 <li>
 <p>Type in the textbox:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">/locations
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>/locations
+</span></span></code></pre></div></li>
 <li>
 <p>Click on the <strong>Update the Staging Environment</strong> to save the changes and check the connection between client, gateway and API.</p>
 <p><br><img src="../images/08-update-staging.png" width="900" /><br><br></p>
@@ -562,7 +562,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/lab05/index.html b/workshops/agile_integrations_ci/lab05/index.html
index 5e9f1c098..4a6e29e6e 100644
--- a/workshops/agile_integrations_ci/lab05/index.html
+++ b/workshops/agile_integrations_ci/lab05/index.html
@@ -324,7 +324,7 @@ <h3 id="securing-apis-with-openid-connect-and-red-hat-single-sign-on">Securing A
 <li>Duration: 20 mins</li>
 <li>Audience: API Owners, Product Managers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-05.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-05.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>Once you have APIs in your organization and have applications being written, you also want to be sure in many cases that the various types of users of the APIs are correctly authenticated. In this lab you will discover how to set up the widely used OpenID connect pattern for Authentication.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -334,58 +334,58 @@ <h3 id="step-1-get-red-hat-single-sign-on-service-account-credentials">Step 1: G
 <ol>
 <li>
 <p>Open a browser window and navigate to your SSO Console.  Please check with your instructor for the link.  It should be similar to the following.  Replace userX with your assigned user and OCP_URL.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">http://sso-sso.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>/auth/admin/<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>/console/
-</code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>http://sso-sso.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>/auth/admin/<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>/console/
+</span></span></code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
 </li>
 <li>
 <p>Log into Red Hat Single Sign On using your designated user and password. Click on <strong>Sign In</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-login-sso.png &ldquo;RH SSO Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-login-sso.png &ldquo;RH SSO Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Clients</strong> from the left menu.</p>
-<p><br>&lt;img src=&rdquo;../images/00-clients.png &ldquo;Clients&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-clients.png &ldquo;Clients&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>A 3scale-admin client and service account was already created for you</em>.</p>
 </li>
 <li>
 <p>Click on the <strong>3scale-admin</strong> link to view the details.</p>
-<p><br>&lt;img src=&rdquo;../images/00-3scale-admin.png &ldquo;3scale admin account&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-3scale-admin.png &ldquo;3scale admin account&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Credentials</strong> tab.</p>
-<p><br>&lt;img src=&rdquo;../images/00-sa-credentials.png &ldquo;Service Account Credentials&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-sa-credentials.png &ldquo;Service Account Credentials&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Take notice of the service account <strong>Secret</strong>. Copy and save it or write it down as you will use it to configure 3scale.</p>
-<p><br>&lt;img src=&rdquo;../images/00-sa-secret.png &ldquo;Service Account Secret&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-sa-secret.png &ldquo;Service Account Secret&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-add-user-to-realm">Step 2: Add User to Realm</h3>
 <ol>
 <li>
 <p>Click on the Users menu on the left side of the screen.</p>
-<p><br>&lt;img src=&rdquo;../images/00-users.png &ldquo;Users Menu&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-users.png &ldquo;Users Menu&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Add user</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/00-add-user.png &ldquo;Add User&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-add-user.png &ldquo;Add User&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Type <strong>apiuser</strong> as the Username.</p>
-<p><br>&lt;img src=&rdquo;../images/00-username.png &ldquo;User Details&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-username.png &ldquo;User Details&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the <strong>Save</strong> button.</p>
 </li>
 <li>
 <p>Click on the <strong>Credentials</strong> tab to reset the password. Type <strong>apipassword</strong> as the <em>New Password</em> and <em>Password Confirmation</em>. Turn OFF the <strong>Temporary</strong> to avoid the password reset at the next login.</p>
-<p><br>&lt;img src=&rdquo;../images/00-user-credentials.png &ldquo;User Credentials&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-user-credentials.png &ldquo;User Credentials&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Reset Password</strong>.</p>
 </li>
 <li>
 <p>Click on the <strong>Change password</strong> button in the pop-up dialog.</p>
-<p><br>&lt;img src=&rdquo;../images/00-change-password.png &ldquo;Change Password Dialog&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-change-password.png &ldquo;Change Password Dialog&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>Now you have a user to test your integration.</em></p>
 </li>
 </ol>
@@ -393,8 +393,8 @@ <h3 id="step-3-configure-3scale-integration">Step 3: Configure 3scale Integratio
 <ol>
 <li>
 <p>Open a browser window and navigate to:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://userX-admin.apps.ocp-ai.redhatgov.io/p/login
-</code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://userX-admin.apps.ocp-ai.redhatgov.io/p/login
+</span></span></code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
 </li>
 <li>
 <p>Accept the self-signed certificate if you haven&rsquo;t.</p>
@@ -436,36 +436,36 @@ <h3 id="step-3-configure-3scale-integration">Step 3: Configure 3scale Integratio
 </li>
 <li>
 <p>In the <strong>OpenID Connect Issuer</strong> field, type in your previously noted client credentials with the URL of your Red Hat Single Sing On instance:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">http://3scale-admin:CLIENT_SECRET@sso-sso.apps.ocp-ai.redhatgov.io/auth/realms/userX
-</code></pre></div><p><em>Remember to replace the X with user number</em></p>
-<p><br>&lt;img src=&rdquo;../images/06-openid-issuer.png &ldquo;OpenID Connect Issuer&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>http://3scale-admin:CLIENT_SECRET@sso-sso.apps.ocp-ai.redhatgov.io/auth/realms/userX
+</span></span></code></pre></div><p><em>Remember to replace the X with user number</em></p>
+<p><br>&lt;img src=&quot;../images/06-openid-issuer.png &ldquo;OpenID Connect Issuer&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down the page and click on the <strong>Update Staging Environment</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/08-back-integration.png &ldquo;Back Integration&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/08-back-integration.png &ldquo;Back Integration&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>After the reload, scroll down again and click the <strong>Back to Integration &amp; Configuration</strong> link.</p>
-<p><br>&lt;img src=&rdquo;../images/07-update-environment.png &ldquo;Update Environment&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/07-update-environment.png &ldquo;Update Environment&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Promote to Production by clicking the <strong>Promote to Production</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/08a-promote-production.png &ldquo;Update Environment&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/08a-promote-production.png &ldquo;Update Environment&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-4-create-a-test-app">Step 4: Create a Test App</h3>
 <ol>
 <li>
 <p>Go to the <em>Developers</em> tab and click on <strong>Developers</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/09-developers.png &ldquo;Developers&rdquo;)</p>
+<p><br>&lt;img src=&quot;../images/09-developers.png &ldquo;Developers&rdquo;)</p>
 </li>
 <li>
 <p>Click on the <strong>Applications</strong> link.</p>
-<p><br>&lt;img src=&rdquo;../images/10-applications.png &ldquo;Applications&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/10-applications.png &ldquo;Applications&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Create Application</strong> link.</p>
-<p><br>&lt;img src=&rdquo;../images/11-create-application.png &ldquo;Create Application&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/11-create-application.png &ldquo;Create Application&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Basic</strong> plan from the combo box. Type the following information:</p>
@@ -473,11 +473,11 @@ <h3 id="step-4-create-a-test-app">Step 4: Create a Test App</h3>
 <li>Name: <strong>Secure App</strong></li>
 <li>Description: <strong>OpenID Connect Secured Application</strong></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/12-application-details.png &ldquo;Application Details&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/12-application-details.png &ldquo;Application Details&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Finally, scroll down the page and click on the <strong>Create Application</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/13-create-app.png &ldquo;Create App&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/13-create-app.png &ldquo;Create App&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Update redirect link to your locations application link.</p>
@@ -486,7 +486,7 @@ <h3 id="step-4-create-a-test-app">Step 4: Create a Test App</h3>
 <ul>
 <li>Please update userX and OCP_URL http://www-[userX].apps.[OCP_URL]/</li>
 <li>And note the <em>API Credentials</em>. Write them down as you will need the <strong>Client ID</strong> and the <strong>Client Secret</strong> to test your integration.
-<br>&lt;img src=&rdquo;../images/14-app-credentials.png &ldquo;App Credentials&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></li>
+<br>&lt;img src=&quot;../images/14-app-credentials.png &ldquo;App Credentials&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></li>
 </ul>
 <p><em>Congratulations!</em> You have now an application to test your OpenID Connect Integration.</p>
 <h2 id="steps-beyond">Steps Beyond</h2>
@@ -539,7 +539,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/lab06/index.html b/workshops/agile_integrations_ci/lab06/index.html
index 11067ce93..7e6ded03d 100644
--- a/workshops/agile_integrations_ci/lab06/index.html
+++ b/workshops/agile_integrations_ci/lab06/index.html
@@ -324,7 +324,7 @@ <h3 id="publishing-apis-to-developer-portal">Publishing APIs to Developer Portal
 <li>Duration: 20 mins</li>
 <li>Audience: API Owners, Product Managers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-05.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-05.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>The focal point of your developers experience is the API developer portal, and the level of effort you put into it will directly correlate to the level of success of your API program, and API developer engagement.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -414,8 +414,8 @@ <h3 id="step-3-login-to-developer-portal">Step 3: Login to Developer Portal</h3>
 </li>
 <li>
 <p>Open a new <em>Incognito/Private</em> browser window to test the Developer Portal login. Navigate to the following.  Make sure your user and Openshift environment is correct.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"> http://<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span> http://<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>
+</span></span></code></pre></div></li>
 <li>
 <p>Type your portal code to finish the login.</p>
 <p><br><img src="../images/16e-ingress-code.png" width="900" /><br><br></p>
@@ -426,7 +426,7 @@ <h3 id="step-3-login-to-developer-portal">Step 3: Login to Developer Portal</h3>
 </li>
 <li>
 <p>You will land in the developers homepage, where you will be able to check your developers settings and retrieve your newly created <strong>Client ID</strong> and <strong>Client Secret</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/16g-user-credentials.png &ldquo;Application Credentials&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/16g-user-credentials.png &ldquo;Application Credentials&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations!</em> You have successfully customized your Developer Portal and completed a Sign Up process.</p>
@@ -496,7 +496,7 @@ <h3 id="links">Links</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/lab07/index.html b/workshops/agile_integrations_ci/lab07/index.html
index 93027b8d6..fc6ecd68c 100644
--- a/workshops/agile_integrations_ci/lab07/index.html
+++ b/workshops/agile_integrations_ci/lab07/index.html
@@ -320,7 +320,7 @@ <h3 id="testing-your-web-application">Testing your web application</h3>
 <li>Duration: 10 mins</li>
 <li>Audience: API Consumers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-05.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-05.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h3 id="overview">Overview</h3>
 <p>This lab demonstrates the International Inc. Locations page using our newly authenticated locations API.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -334,7 +334,7 @@ <h3 id="step-1-update-openshift-deployment">Step 1: Update OpenShift Deployment<
 </li>
 <li>
 <p>Scroll down and click in the www link in the BUILDS section.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-10.png &ldquo;Scroll Down&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-10.png &ldquo;Scroll Down&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the build environment variables page, replace the <code>CLIENT_ID</code> from <code>CHANGE_ME</code> to the one generated from the previous lab.</p>
@@ -343,7 +343,7 @@ <h3 id="step-1-update-openshift-deployment">Step 1: Update OpenShift Deployment<
 <ul>
 <li>
 <p>Also, make note of the API_BACKEND_URL.  That is the 3Scale backend address of your API.  If the 3Scale Environment is configured with self-signed certificates, go ahead and bring up that link in a Browser and have your Browser accept the certificate for later on. 3Scale should give you an authentication error since it&rsquo;s not configured yet.  The important thing is to just accept the certificate.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-11.png &ldquo;Change Client ID&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-11.png &ldquo;Change Client ID&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -352,18 +352,18 @@ <h3 id="step-1-update-openshift-deployment">Step 1: Update OpenShift Deployment<
 </li>
 <li>
 <p>Click the Start Build button to trigger a new build using the new environment variables pointing to your service.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-12.png &ldquo;Start Build&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-12.png &ldquo;Start Build&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>A new build will be triggered. Expand the row by clicking the Builds Icon.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-13.png &ldquo;View Build&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-13.png &ldquo;View Build&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>The build process checks out the code from the git repo, runs a source-to-image container image build, and redeploys the container with the new image using a rolling upgrade strategy.</em></p>
 <ol>
 <li>
 <p>Wait for until the new Build to complete and the rolling upgrade to finish to test your new deployment.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-22.png &ldquo;Updated App&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-22.png &ldquo;Updated App&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-update-secured-service-with-red-hat-single-sign-on-application-callback">Step 2: Update Secured Service with Red Hat Single Sign On Application Callback</h3>
@@ -371,23 +371,23 @@ <h3 id="step-2-update-secured-service-with-red-hat-single-sign-on-application-ca
 <ol>
 <li>
 <p>Open a browser window and navigate to your SSO Console.  Please check with your instructor for the link.  It should be similar to the following.  Replace userX with your assigned user and OCP_URL.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">http://sso-sso.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>/auth/admin/<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>/console/
-</code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>http://sso-sso.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>/auth/admin/<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>/console/
+</span></span></code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
 </li>
 <li>
 <p>Log into Red Hat Single Sign On using your designated user and password. Click on <strong>Sign In</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-login-sso.png &ldquo;RH SSO Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-login-sso.png &ldquo;RH SSO Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Clients</strong> from the left menu.</p>
-<p><br>&lt;img src=&rdquo;../images/00-clients.png &ldquo;Clients&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-clients.png &ldquo;Clients&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>3scale, through it&rsquo;s <a href="https://github.com/3scale/zync/">zync</a> component, already synchronized the application information into the Red Hat SSO security realm</em>.</p>
 </li>
 <li>
 <p>Click on the <strong>CLIENT_ID</strong> link to view the details.</p>
 <p><em>Remember to select CLIENT_ID with the one you got in the <a href="../lab05/#step-4-create-a-test-app">API Security Lab</a>. It will easily identifiable as its and hexadecimal name</em>.</p>
 <p><em>If you do not find the CLIENT_ID, make sure you correctly executed the sync between 3scale and RHSSO in <a href="../lab05/#step-3-configure-3scale-integration">Step 3.12 Lab05</a></em></p>
-<p><br>&lt;img src=&rdquo;../images/consume-24.png &ldquo;Client Application&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-24.png &ldquo;Client Application&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down, type in and select the following options in the application configuration:</p>
@@ -422,7 +422,7 @@ <h3 id="step-2-update-secured-service-with-red-hat-single-sign-on-application-ca
 </tbody>
 </table>
 <p><em>Remember to replace the X with your user number.</em></p>
-<p><br>&lt;img src=&rdquo;../images/consume-25.png &ldquo;Client Configuration&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-25.png &ldquo;Client Configuration&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Finally, click <strong>Save</strong> button to persist the changes.</p>
@@ -440,11 +440,11 @@ <h3 id="step-3-opening-international-inc-web-page">Step 3: Opening International
 <ol>
 <li>
 <p>You should now see what the development team created for International Inc. Click <strong>LOCATIONS</strong> to check the locations page.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-13.png &ldquo;Webpage&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-13.png &ldquo;Webpage&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You can notice now the <strong>Sign In</strong> button in the page.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-222.png &ldquo;Sign-In&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-222.png &ldquo;Sign-In&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-4-test-the-single-sign-on-integration">Step 4: Test the Single Sign On Integration</h3>
@@ -454,22 +454,22 @@ <h3 id="step-4-test-the-single-sign-on-integration">Step 4: Test the Single Sign
 </li>
 <li>
 <p>You are being redirected to Red Hat Single Sign On <strong>Login Page</strong>. Login using the user credentials you created in the API Security Lab.  Please check with your instructor if you need credentials.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-23.png &ldquo;Login Realm&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-23.png &ldquo;Login Realm&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You will be redirected again to the <strong>LOCATIONS</strong> page where now you will be able to see the map with the International Inc Offices.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-14.png &ldquo;Locations Page&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-14.png &ldquo;Locations Page&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-5-troubleshooting-the-locations-page">Step 5: Troubleshooting the Locations Page</h3>
 <ol>
 <li>
 <p>In most cases, the Locations web page will <strong>NOT</strong> show the locations because of a self-signed certificate issue in your web-browser.  See the below example with missing locations:</p>
-<p><br>&lt;img src=&rdquo;../images/00-missing-locations.png &ldquo;Missing Locations&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-missing-locations.png &ldquo;Missing Locations&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>To resolve this issue in Chrome, navigate to <em>View &gt; Developer &gt; Developer Tools</em> menu.  A Developer Tools console should appear.</p>
-<p><br>&lt;img src=&rdquo;../images/00-developer-console.png &ldquo;Developer Console&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-developer-console.png &ldquo;Developer Console&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the developer console, a red error should appear indicating a cert issue. Click on the link and accept the certificate.</p>
@@ -479,7 +479,7 @@ <h3 id="step-5-troubleshooting-the-locations-page">Step 5: Troubleshooting the L
 <ol>
 <li>
 <p>Refresh the page, and the locations should appear.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-14.png &ldquo;Locations Page&rdquo;&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-14.png &ldquo;Locations Page&rdquo;&quot; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>If you get an &ldquo;Authentication Parameter is Missing&rdquo; Error.  It&rsquo;s most likely your backend api is not working</p>
@@ -545,7 +545,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/openshift/index.html b/workshops/agile_integrations_ci/openshift/index.html
index a9c0c094f..25712da5f 100644
--- a/workshops/agile_integrations_ci/openshift/index.html
+++ b/workshops/agile_integrations_ci/openshift/index.html
@@ -344,15 +344,15 @@ <h2 id="lets-login-to-the-web-console">Let&rsquo;s Login to the Web Console</h2>
 <p>Once logged in you should see your available projects - or a button to create a project if none exist already.</p>
 <h2 id="lets-try-the-oc-command-line-cli-tool">Let&rsquo;s try the &lsquo;oc&rsquo; command line (CLI) tool</h2>
 <p>Open a terminal and login using the same URI with following command:</p>
-<pre><code>$ oc login https://ocp-ai.redhatgov.io/ --insecure-skip-tls-verify=true
-Authentication required for https://ocp-naps.redhatgov.io/ &quot;master&quot; &quot;:8443&quot; &gt;}} (openshift)
+<pre tabindex="0"><code>$ oc login https://ocp-ai.redhatgov.io/ --insecure-skip-tls-verify=true
+Authentication required for https://ocp-naps.redhatgov.io/ &#34;master&#34; &#34;:8443&#34; &gt;}} (openshift)
  Username: user#
  Password:
 Login successful.
 </code></pre><p>Check to see what projects you have access to:</p>
-<pre><code>$ oc get projects
+<pre tabindex="0"><code>$ oc get projects
 </code></pre><p>Type the following command to show services, deployment configs, build configurations, and active deployments (this will come in handy later):</p>
-<pre><code>$ oc status
+<pre tabindex="0"><code>$ oc status
 </code></pre><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.</p>
 
@@ -394,7 +394,7 @@ <h2 id="lets-try-the-oc-command-line-cli-tool">Let&rsquo;s try the &lsquo;oc&rsq
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_ci/prerequisites/index.html b/workshops/agile_integrations_ci/prerequisites/index.html
index 34c7a60a7..6910fa728 100644
--- a/workshops/agile_integrations_ci/prerequisites/index.html
+++ b/workshops/agile_integrations_ci/prerequisites/index.html
@@ -356,7 +356,7 @@ <h1 id="prerequisites">Prerequisites</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/index.html b/workshops/agile_integrations_dev/index.html
index 37fc70eab..0e70b1882 100644
--- a/workshops/agile_integrations_dev/index.html
+++ b/workshops/agile_integrations_dev/index.html
@@ -378,7 +378,7 @@ <h1 id="labs">Labs</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/index.xml b/workshops/agile_integrations_dev/index.xml
index a11fd0f72..2f1a45d5d 100644
--- a/workshops/agile_integrations_dev/index.xml
+++ b/workshops/agile_integrations_dev/index.xml
@@ -4,122 +4,78 @@
     <title>Agile Integrations Workshop - Developer on Red Hat | Public Sector</title>
     <link>/workshops/agile_integrations_dev/</link>
     <description>Recent content in Agile Integrations Workshop - Developer on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/agile_integrations_dev/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/agile_integrations_dev/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Lab 01 - API Design</title>
       <link>/workshops/agile_integrations_dev/lab01/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab01/</guid>
-      <description>Lab 1 API Design Import an OpenAPI Specification using Apicurio Studio  Duration: 10 mins Audience: Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
+      <description>Lab 1 API Design Import an OpenAPI Specification using Apicurio Studio Duration: 10 mins Audience: Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-01.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</description>
     </item>
-    
     <item>
       <title>Lab 02 - API Mocking</title>
       <link>/workshops/agile_integrations_dev/lab02/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab02/</guid>
-      <description>Lab 2 API Mocking Bring your APIs to life  Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers  
-&amp;lt;img src=&amp;rdquo;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
+      <description>Lab 2 API Mocking Bring your APIs to life Duration: 20 mins Audience: Developers, Architects, Testers, Quality Engineers &amp;lt;img src=&amp;quot;../images/agenda-02.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</description>
     </item>
-    
     <item>
       <title>Lab 03 - Swagger to REST</title>
       <link>/workshops/agile_integrations_dev/lab03/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab03/</guid>
-      <description>Lab 3 Swagger to REST Contract-first API development with a database interface, implemented using Eclipse Che  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview In the context of defining API&amp;rsquo;s, it&amp;rsquo;s common for a Business Analyst (or Citizen Integrator) to first create an API specification or contract. By beginning the process with a clearly defined contract, a Developer can easily take the contract and auto-generate the underlying service to implement that API.</description>
+      <description>Lab 3 Swagger to REST Contract-first API development with a database interface, implemented using Eclipse Che Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview In the context of defining API&amp;rsquo;s, it&amp;rsquo;s common for a Business Analyst (or Citizen Integrator) to first create an API specification or contract. By beginning the process with a clearly defined contract, a Developer can easily take the contract and auto-generate the underlying service to implement that API.</description>
     </item>
-    
     <item>
       <title>Lab 04 - SOAP to REST (Optional)</title>
       <link>/workshops/agile_integrations_dev/lab04/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab04/</guid>
-      <description>Lab 4 SOAP to REST (Optional) Contract-first API development wrapping an existing SOAP service, implemented using Eclipse Che  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Another important use case in developing API&amp;rsquo;s is to take an existing legacy SOAP service and wrap it with a new RESTful endpoint. This SOAP to REST transformation is implemented in the API service layer (Fuse). This lab will walk you through taking an existing SOAP contract (WSDL), converting it to Java POJO&amp;rsquo;s and exposing it using Camel REST DSL.</description>
+      <description>Lab 4 SOAP to REST (Optional) Contract-first API development wrapping an existing SOAP service, implemented using Eclipse Che Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Another important use case in developing API&amp;rsquo;s is to take an existing legacy SOAP service and wrap it with a new RESTful endpoint. This SOAP to REST transformation is implemented in the API service layer (Fuse). This lab will walk you through taking an existing SOAP contract (WSDL), converting it to Java POJO&amp;rsquo;s and exposing it using Camel REST DSL.</description>
     </item>
-    
     <item>
       <title>Lab 05 - Fuse Online</title>
       <link>/workshops/agile_integrations_dev/lab05/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab05/</guid>
-      <description>Lab 5 Fuse Online  Duration: 20 mins Audience: Developers and Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop, deploy the APIs. Here is how to create a simple API with Fuse online.
-Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
+      <description>Lab 5 Fuse Online Duration: 20 mins Audience: Developers and Architects &amp;lt;img src=&amp;quot;../images/agenda-03.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview When it comes to quick API development, you need both the integration experts as well as application developers to easily develop, deploy the APIs. Here is how to create a simple API with Fuse online.&#xA;Why Red Hat? Red Hat Fuse integration solution empowers integration experts, application developers, and business users to engage in enterprise-wide collaboration and high-productivity self-service.</description>
     </item>
-    
     <item>
       <title>Lab 06 - Managed API Endpoints</title>
       <link>/workshops/agile_integrations_dev/lab06/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab06/</guid>
-      <description>Lab 6 Managed API Endpoints Take control of your APIs  Duration: 5 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them and for what purpose. You also need to begin to track usage of these different users to know who is/is not succeeding in their usage.</description>
+      <description>Lab 6 Managed API Endpoints Take control of your APIs Duration: 5 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview Once you have APIs deployed in your environment, it becomes critically important to manage who may use them and for what purpose. You also need to begin to track usage of these different users to know who is/is not succeeding in their usage. For this reason in this lab you will be adding management capabilities to the API to give you control and visibility of it&amp;rsquo;s usage.</description>
     </item>
-    
     <item>
       <title>Lab 07 - API Developer Portal</title>
       <link>/workshops/agile_integrations_dev/lab07/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab07/</guid>
-      <description>Lab 7 API Developer Portal Publishing APIs to Developer Portal  Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview The focal point of your developers’ experience is the API developer portal, and the level of effort you put into it will determine the level of decreased support costs and increased developer engagement.
-Why Red Hat? 3scale provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions and increase API adoption.</description>
+      <description>Lab 7 API Developer Portal Publishing APIs to Developer Portal Duration: 20 mins Audience: API Owners, Product Managers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-04.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview The focal point of your developers’ experience is the API developer portal, and the level of effort you put into it will determine the level of decreased support costs and increased developer engagement.&#xA;Why Red Hat? 3scale provides a built-in, state-of-the-art CMS portal, making it very easy to create your own branded hub with a custom domain to manage developer interactions and increase API adoption.</description>
     </item>
-    
     <item>
       <title>Lab 08 - API Consumption</title>
       <link>/workshops/agile_integrations_dev/lab08/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/lab08/</guid>
-      <description>Lab 8 API Consumption Connect Applications and APIs  Duration: 15 mins Audience: API Consumers, Developers, Architects  
-&amp;lt;img src=&amp;rdquo;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;quot;900&amp;rdquo; /&amp;gt;
-Overview APIs provide the building blocks for applications, but it is applications which deliver functionality to the end users. hence to see APIs in action it helps to see how applications can call APIs to provide new functionality. In this lab you&amp;rsquo;ll be able to create a simple web application which consumes the API you built earlier in the exercises.</description>
+      <description>Lab 8 API Consumption Connect Applications and APIs Duration: 15 mins Audience: API Consumers, Developers, Architects &amp;lt;img src=&amp;quot;../images/agenda-05.png &amp;ldquo;Login&amp;rdquo; width=&amp;ldquo;900&amp;rdquo; /&amp;gt;&#xA;Overview APIs provide the building blocks for applications, but it is applications which deliver functionality to the end users. hence to see APIs in action it helps to see how applications can call APIs to provide new functionality. In this lab you&amp;rsquo;ll be able to create a simple web application which consumes the API you built earlier in the exercises.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/agile_integrations_dev/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser.
-  Chrome is the preferred browser for this workshop  </description>
+      <description>Prerequisites This workshop is done entirely through the browser.&#xA;Chrome is the preferred browser for this workshop </description>
     </item>
-    
     <item>
       <title>Welcome to OpenShift</title>
       <link>/workshops/agile_integrations_dev/openshift/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/openshift/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/agile_integrations_dev/lab01/index.html b/workshops/agile_integrations_dev/lab01/index.html
index 5663e263b..1d6da6ef2 100644
--- a/workshops/agile_integrations_dev/lab01/index.html
+++ b/workshops/agile_integrations_dev/lab01/index.html
@@ -324,7 +324,7 @@ <h3 id="import-an-openapi-specification-using-apicurio-studio">Import an OpenAPI
 <li>Duration: 10 mins</li>
 <li>Audience: Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-01.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-01.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>As APIs become more widespread in the enterprise, consistent design and usage is critically important to improve reusability. The more reusable APIs are, the less friction there is for other internal or external teams to make progress. Having design standards and tools baked into the API development and maintenance process is a very powerful way to enable this consistency.</p>
 <p>As a developer, we need to be familiar with API Design even though it&rsquo;s not our core capability.  Therefore, in this lab we will review Red Hat&rsquo;s API Designer product, Apicurio, so that we&rsquo;re familiar with it&rsquo;s capabilities only.</p>
@@ -338,15 +338,15 @@ <h3 id="step-1-importing-apis-with-apicurio-studio">Step 1: Importing APIs with
 </li>
 <li>
 <p>Log in using your designated user and password.</p>
-<p><br>&lt;img src=&rdquo;../images/design-01.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-01.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>APIs</strong> in the left side navigation menu from the Dashboard page.</p>
-<p><br>&lt;img src=&rdquo;../images/design-02.png &ldquo;APIs&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-02.png &ldquo;APIs&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Import API</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-03.png &ldquo;Import API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-03.png &ldquo;Import API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Import the API created by your friendly Citizen Integrator:</p>
@@ -354,14 +354,14 @@ <h3 id="step-1-importing-apis-with-apicurio-studio">Step 1: Importing APIs with
 <li>Import Type: <strong>Import From URL</strong></li>
 <li>Url: <code>https://raw.githubusercontent.com/epe105/dayinthelife-integration/master/docs/labs/developer-track/resources/Locations.yaml</code></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/design-04.png &ldquo;Import API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-04.png &ldquo;Import API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Import API</strong>.</p>
 </li>
 <li>
 <p>Finally, click on <strong>Edit API</strong> to walkthrough your newly imported API.</p>
-<p><br>&lt;img src=&rdquo;../images/design-05.png &ldquo;Edit API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-05.png &ldquo;Edit API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-verifying-apis">Step 2: Verifying APIs</h3>
@@ -370,33 +370,33 @@ <h3 id="step-2-verifying-apis">Step 2: Verifying APIs</h3>
 <ol>
 <li>
 <p>Time to verify our data definitions for the API. Click on the <code>location/phone{id}</code> link under the <em>Paths</em>.</p>
-<p><br>&lt;img src=&rdquo;../images/design-15.png &ldquo;Add Definition&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-15.png &ldquo;Add Definition&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Notice that this API path has a single path parameter (<code>id</code> defined as an <code>int32</code>) and a single GET operation defined.  Click on the GET operation, then click the location drop-down which is part of the 200 OK response.</p>
-<p><br>&lt;img src=&rdquo;../images/design-16.png &ldquo;Definition Name&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-16.png &ldquo;Definition Name&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Notice that this API path has a single response defined (a <code>200 OK</code> response) and the type that is returned is a <code>location</code> object.</p>
-<p><br>&lt;img src=&rdquo;../images/design-17.png &ldquo;Definition Data Types&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-17.png &ldquo;Definition Data Types&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-3-verify-the-location-object">Step 3: Verify the location object</h3>
 <ol>
 <li>
 <p>Click on the <code>&lt;/&gt; location</code> object link under the <em>Data Types</em> section.  Notice that the object has a bunch of properties defined which make up the object.</p>
-<p><br>&lt;img src=&rdquo;../images/design-06.png &ldquo;Add Path&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-06.png &ldquo;Add Path&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the source link and notice that we have both YAML and JSON schemas generated by our object design:</p>
-<p><br>&lt;img src=&rdquo;../images/design-07.png &ldquo;Path&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-07.png &ldquo;Path&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-4-verify-the-locations-path">Step 4: Verify the /locations path</h3>
 <ol>
 <li>
 <p>Click the <strong>/locations</strong> path.  Then click on the source tab.  Notice that we have both a GET and POST request defined, together with a couple of example requests.  Using a POST method, we can insert a new record into our sample database with Fuse.</p>
-<p><br>&lt;img src=&rdquo;../images/design-23.png &ldquo;Locations API&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-23.png &ldquo;Locations API&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations!</em> You have imported your first API definition based on the OpenAPI Specification  using Red Hat&rsquo;s Apicurio.</p>
@@ -459,7 +459,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab02/index.html b/workshops/agile_integrations_dev/lab02/index.html
index aa98d116c..429ad3f06 100644
--- a/workshops/agile_integrations_dev/lab02/index.html
+++ b/workshops/agile_integrations_dev/lab02/index.html
@@ -324,7 +324,7 @@ <h3 id="bring-your-apis-to-life">Bring your APIs to life</h3>
 <li>Duration: 20 mins</li>
 <li>Audience: Developers, Architects, Testers, Quality Engineers</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-02.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-02.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>When building and working with APIs, you often need to simulate the responses of the system before it has been fully completed. This is what we explore in this workshop - mocking up API structures quickly so they can be subjected to testing without having to create all the final service code.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -339,11 +339,11 @@ <h3 id="prerequisite-setup-the-collaboration-environment-using-git-gogs">Prerequ
 </li>
 <li>
 <p>Log into Gogs using your designated user and password. Click on <strong>Sign In</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-01.png &ldquo;Sign In&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-01.png &ldquo;Sign In&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the main page, click in the <strong>+</strong> sign in the right top corner to display the <em>New</em> menu. Click the <strong>New Migration</strong> option.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-02.png &ldquo;New Migration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-02.png &ldquo;New Migration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Fill in the information of the repository migration with the following values:</p>
@@ -352,39 +352,39 @@ <h3 id="prerequisite-setup-the-collaboration-environment-using-git-gogs">Prerequ
 <li>Owner: <strong>UserX</strong></li>
 <li>Repository Name: <strong>locations-api</strong></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/mock-03.png &ldquo;New Migration Repository&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-03.png &ldquo;New Migration Repository&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Migrate Repository</strong> to fork the GitHub repo into Gogs.</p>
 </li>
 <li>
 <p>Switch to branch <code>dev-track-lab-02</code></p>
-<p><br>&lt;img src=&rdquo;../images/mock-04.png &ldquo;Upload File&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-04.png &ldquo;Upload File&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Open the <code>locations-api</code> folder and click on the filename link <strong>Locations-UserX.json</strong> to open and review the file.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-05.png &ldquo;Click File&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-05.png &ldquo;Click File&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>If everything is fine, click the <strong>Edit</strong> button to apply your personal user settings.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-06.png &ldquo;Edit file&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-06.png &ldquo;Edit file&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Replace <strong>UserX</strong> with your user number.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-07.png &ldquo;Rename file&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-07.png &ldquo;Rename file&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Commit the changes to gogs.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-08.png &ldquo;Commit file&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-08.png &ldquo;Commit file&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>RAW</strong> button to get the raw download version of the file.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-09.png &ldquo;Raw file&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-09.png &ldquo;Raw file&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Copy the browser tab URL. Store that URL address as you will use it in the next steps of the lab. The URL should look similar to the following:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"> http://gogs.apps.ocp-ai.redhatgov.io/userX/locations-api/raw/dev-track-lab-02/locations-api/Locations-UserX.json
-</code></pre></div><p><em>If you feel more comfortable, you can also copy and paste the RAW button link from the previous step.  Also, don&rsquo;t forget to update the X variable with your user number</em>.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span> http://gogs.apps.ocp-ai.redhatgov.io/userX/locations-api/raw/dev-track-lab-02/locations-api/Locations-UserX.json
+</span></span></code></pre></div><p><em>If you feel more comfortable, you can also copy and paste the RAW button link from the previous step.  Also, don&rsquo;t forget to update the X variable with your user number</em>.</p>
 </li>
 </ol>
 <h3 id="step-1-create-a-microcks-job">Step 1: Create a Microcks Job</h3>
@@ -394,15 +394,15 @@ <h3 id="step-1-create-a-microcks-job">Step 1: Create a Microcks Job</h3>
 </li>
 <li>
 <p>Log in into Microcks using your designated user and password.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-10.png &ldquo;Openshift Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-10.png &ldquo;Openshift Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You are now in the main Microcks page. Click the <strong>Importers</strong> button to access the Importers page.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-11.png &ldquo;Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-11.png &ldquo;Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click the <strong>Create</strong> button to create your first job.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-12.png &ldquo;Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-12.png &ldquo;Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the <code>Create a New Job</code> dialog, type in the following information replacing <strong>X</strong> with your user number. Click <strong>Next</strong>.</p>
@@ -414,44 +414,44 @@ <h3 id="step-1-create-a-microcks-job">Step 1: Create a Microcks Job</h3>
 </ul>
 </li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/mock-13.png &ldquo;Job Details&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-13.png &ldquo;Job Details&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click <strong>Next</strong> for the Authentication options.</p>
 </li>
 <li>
 <p>Review the details and click on <strong>Create</strong> to create the job.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-14.png &ldquo;Create Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-14.png &ldquo;Create Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>After your job is created, click on the <strong>Activate</strong> option.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-15.png &ldquo;Activate Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-15.png &ldquo;Activate Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Repeat the last step, but now select the <strong>Force Import</strong> option. This will start the synchronization job.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-16.png &ldquo;Start Job&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-16.png &ldquo;Start Job&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Refresh your window to get it to the latest state.</p>
 </li>
 <li>
 <p>You will see 3 labels next to your Job. Click the <strong>Services</strong> label.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-17.png &ldquo;Job Services&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-17.png &ldquo;Job Services&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the dialog you will see your service listed. Click on the <strong>Locations-UserX - 1.0.0.</strong> link.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-18.png &ldquo;Job Service&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-18.png &ldquo;Job Service&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click <strong>Close</strong> to dismiss the dialog.</p>
 </li>
 <li>
 <p>This is your new REST mock service based on the OpenAPI definition you just loaded to Microcks. Click on the arrow to expand the <strong>GET /locations</strong> operation.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-19.png &ldquo;Mock Service&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-19.png &ldquo;Mock Service&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You can check that the example we added to the definition in Lab 1 will be used to return the mock values. Scroll down, copy and save the <strong>Mocks URL</strong>, we will use that endpoint to test the REST mock service.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-20.png &ldquo;Mock Operation&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-20.png &ldquo;Mock Operation&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-test-the-rest-mock-service">Step 2: Test the REST Mock Service</h3>
@@ -459,19 +459,19 @@ <h3 id="step-2-test-the-rest-mock-service">Step 2: Test the REST Mock Service</h
 <ol>
 <li>
 <p>Open a browser window and navigate to:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://onlinecurl.com/
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://onlinecurl.com/
+</span></span></code></pre></div></li>
 <li>
 <p>Copy and paste the Mock URL from earlier step. <em>Remember to replace X with your user number</em>. It should look similar to the link below.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">http://microcks.apps.ocp-ai.redhatgov.io/rest/Locations-UserX/1.0.0/locations
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>http://microcks.apps.ocp-ai.redhatgov.io/rest/Locations-UserX/1.0.0/locations
+</span></span></code></pre></div></li>
 <li>
 <p>Click the <strong>START YOUR CURL</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-21.png &ldquo;cURL Service&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-21.png &ldquo;cURL Service&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>The page will load the response information from the service. You will be able to see the <em>RESPONSE HEADERS</em> and the actual <em>RESPONSE_BODY</em>. This last part contains the examples we add during the design phase.</p>
-<p><br>&lt;img src=&rdquo;../images/mock-22.png &ldquo;cURL Response&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/mock-22.png &ldquo;cURL Response&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations!</em> You have successfully configure a Microcks Job to create a REST mock service to test your API.</p>
@@ -531,7 +531,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab03/index.html b/workshops/agile_integrations_dev/lab03/index.html
index 75625d8b1..865599624 100644
--- a/workshops/agile_integrations_dev/lab03/index.html
+++ b/workshops/agile_integrations_dev/lab03/index.html
@@ -324,7 +324,7 @@ <h3 id="contract-first-api-development-with-a-database-interface-implemented-usi
 <li>Duration: 20 mins</li>
 <li>Audience: Developers and Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-03.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-03.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>In the context of defining API&rsquo;s, it&rsquo;s common for a Business Analyst (or Citizen Integrator) to first create an API specification or contract.  By beginning the process with a clearly defined contract, a Developer can easily take the contract and auto-generate the underlying service to implement that API.  This <em>separation of concern</em>, whereby a Citizen Integrator and Developer can independently collaborate and contribute to create an end-to-end API implementation, is a powerful method for defining API&rsquo;s.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -346,11 +346,11 @@ <h3 id="step-1-create-an-eclipse-che-environment-for-your-personal-use">Step 1:
 </li>
 <li>
 <p>Select &ldquo;day in the life workshop&rdquo; stack, increase the RAM to 4GB and then click <strong>Create</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-new-workspace.png &ldquo;New Workspace&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-new-workspace.png &ldquo;New Workspace&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Create</strong> to generate and open the workspace.</p>
-<p><br>&lt;img src=&rdquo;../images/00-open-workspace.png &ldquo;Open Workspace&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-open-workspace.png &ldquo;Open Workspace&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Open in IDE</strong></p>
@@ -366,18 +366,18 @@ <h3 id="step-2-create-your-own-personal-openshift-project-and-setup-a-sample-dat
 </li>
 <li>
 <p>Click on your unique namespace to enter your workspace e.g. <code>user39</code>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-create-ocp-project.png &ldquo;Create Project&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-create-ocp-project.png &ldquo;Create Project&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Catalog</strong> on the left menu, then navigate to the <strong>Databases</strong> menu and select <strong>Postgres</strong>.  From there, select the <strong>PostgreSQL</strong> (Ephemeral) template.</p>
-<p><br>&lt;img src=&rdquo;../images/00-select-postgres.png &ldquo;Select Postgres&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-select-postgres.png &ldquo;Select Postgres&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the pop-up window that appears, click the <strong>Next</strong> button to reach the <strong>Configuration</strong> page.</p>
 </li>
 <li>
 <p>Update <strong>PostgreSQL Connection Username</strong> to <code>dbuser</code> and <strong>PostgreSQL Connection Password</strong> to <code>password</code>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-postgres-credentials.png &ldquo;Postgres Credentials&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-postgres-credentials.png &ldquo;Postgres Credentials&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click <strong>Next</strong> and ensure <em>Do not Bind at this time</em> is selected.  Click <strong>Create</strong> to generate the service.</p>
@@ -390,7 +390,7 @@ <h3 id="step-3-import-the-skeleton-projects-from-git-and-convert-them-to-maven-p
 <ol>
 <li>
 <p>In Eclipse Che, click on Workspace &gt; Import Project from the main menu.  A pop-up will appear.</p>
-<p><br>&lt;img src=&rdquo;../images/00-import-project.png &ldquo;Import Project&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-import-project.png &ldquo;Import Project&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Enter your gogs repository.  It should be similar to <code>http://gogs.apps.ocp-ai.redhatgov.io/userX/dayintheliferepo</code>, making sure to update <code>userX</code> with your unique username.</p>
@@ -402,15 +402,15 @@ <h3 id="step-3-import-the-skeleton-projects-from-git-and-convert-them-to-maven-p
 <ol>
 <li>
 <p>When the &ldquo;Save&rdquo; pop-up appears, click the &ldquo;X&rdquo; to close the pop-up.</p>
-<p><br>&lt;img src=&rdquo;../images/00-close-save.png &ldquo;Close Save&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-close-save.png &ldquo;Close Save&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Open the newly created folder, and right-click on the <strong>location-soap2rest</strong> project and select <strong>Convert to Project</strong></p>
-<p><br>&lt;img src=&rdquo;../images/00-convert-project.png &ldquo;Convert Project&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-convert-project.png &ldquo;Convert Project&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Maven</strong> then click <strong>Save</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-select-maven.png &ldquo;Select Maven&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-select-maven.png &ldquo;Select Maven&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Convert the remaining projects to Maven, by repeating steps 4 &amp; 5 for the <strong>location-service</strong> and <strong>location-gateway</strong> projects.</p>
@@ -421,33 +421,33 @@ <h3 id="step-4-import-the-swagger-specification">Step 4: Import the Swagger spec
 <ol>
 <li>
 <p>Expand the <code>location-service</code> project and right-click on the <code>src</code> folder, selecting New &gt; Folder.  Give the folder the name <code>spec</code>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-create-spec.png &ldquo;Create Spec&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-create-spec.png &ldquo;Create Spec&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Right-click on your newly created spec folder and select New &gt; File.  Name the file <code>location.yaml</code>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-location-yaml.png &ldquo;location&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-location-yaml.png &ldquo;location&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Copy the contents of this <a href="https://raw.githubusercontent.com/epe105/dayinthelife-integration/master/docs/labs/developer-track/resources/Locations.yaml">file</a> to your newly created <code>location.yaml</code> file.  The file will auto-save so no need to click <strong>Save</strong>.</p>
 </li>
 <li>
 <p>Open the <code>pom.xml</code> file, and examine and update the plugin entry for <code>camel-restdsl-swagger-plugin</code> located at the bottom of the file.  Take a look at the location of the yaml file, make sure it maps to the one you created.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-xml" data-lang="xml">  <span style="color:#f92672">&lt;plugin&gt;</span>
-      <span style="color:#f92672">&lt;groupId&gt;</span>org.apache.camel<span style="color:#f92672">&lt;/groupId&gt;</span>
-      <span style="color:#f92672">&lt;artifactId&gt;</span>camel-restdsl-swagger-plugin<span style="color:#f92672">&lt;/artifactId&gt;</span>
-      <span style="color:#f92672">&lt;version&gt;</span>2.21.0<span style="color:#f92672">&lt;/version&gt;</span>
-      <span style="color:#f92672">&lt;configuration&gt;</span>
-        <span style="color:#f92672">&lt;specificationUri&gt;</span>${project.basedir}/src/spec/location.yaml<span style="color:#f92672">&lt;/specificationUri&gt;</span>
-        <span style="color:#f92672">&lt;className&gt;</span>CamelRoutes<span style="color:#f92672">&lt;/className&gt;</span>
-        <span style="color:#f92672">&lt;packageName&gt;</span>com.redhat<span style="color:#f92672">&lt;/packageName&gt;</span>
-        <span style="color:#f92672">&lt;outputDirectory&gt;</span>${project.basedir}/src/main/java<span style="color:#f92672">&lt;/outputDirectory&gt;</span>      
-      <span style="color:#f92672">&lt;/configuration&gt;</span>
-  <span style="color:#f92672">&lt;/plugin&gt;</span>
-</code></pre></div><p><br>&lt;img src=&rdquo;../images/00-terminal.png &ldquo;terminal&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span>  <span style="color:#f92672">&lt;plugin&gt;</span>
+</span></span><span style="display:flex;"><span>	  <span style="color:#f92672">&lt;groupId&gt;</span>org.apache.camel<span style="color:#f92672">&lt;/groupId&gt;</span>
+</span></span><span style="display:flex;"><span>	  <span style="color:#f92672">&lt;artifactId&gt;</span>camel-restdsl-swagger-plugin<span style="color:#f92672">&lt;/artifactId&gt;</span>
+</span></span><span style="display:flex;"><span>	  <span style="color:#f92672">&lt;version&gt;</span>2.21.0<span style="color:#f92672">&lt;/version&gt;</span>
+</span></span><span style="display:flex;"><span>	  <span style="color:#f92672">&lt;configuration&gt;</span>
+</span></span><span style="display:flex;"><span>	    <span style="color:#f92672">&lt;specificationUri&gt;</span>${project.basedir}/src/spec/location.yaml<span style="color:#f92672">&lt;/specificationUri&gt;</span>
+</span></span><span style="display:flex;"><span>	    <span style="color:#f92672">&lt;className&gt;</span>CamelRoutes<span style="color:#f92672">&lt;/className&gt;</span>
+</span></span><span style="display:flex;"><span>	    <span style="color:#f92672">&lt;packageName&gt;</span>com.redhat<span style="color:#f92672">&lt;/packageName&gt;</span>
+</span></span><span style="display:flex;"><span>	    <span style="color:#f92672">&lt;outputDirectory&gt;</span>${project.basedir}/src/main/java<span style="color:#f92672">&lt;/outputDirectory&gt;</span>      
+</span></span><span style="display:flex;"><span>	  <span style="color:#f92672">&lt;/configuration&gt;</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">&lt;/plugin&gt;</span>
+</span></span></code></pre></div><p><br>&lt;img src=&quot;../images/00-terminal.png &ldquo;terminal&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>After you&rsquo;ve updated the <code>pom.xml</code> file, we need to run a Maven command to generate the Camel RESTdsl from our specification.  To do this, first highlight the <code>location-service</code> project then click the <strong>Manage Commands</strong> button.</p>
-<p><br>&lt;img src=&rdquo;../images/00-select-mvn.png &ldquo;select&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-select-mvn.png &ldquo;select&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Double-click the <strong>Generate REST DSL from..</strong> script to open the command window.</p>
@@ -462,7 +462,7 @@ <h3 id="step-4-import-the-swagger-specification">Step 4: Import the Swagger spec
 </li>
 <li>
 <p>If the Maven script fails, it&rsquo;s probably because you forgot to first highlight the <code>location-service</code> project in the previous step.  Be sure to do this and re-run the command to fix the error.</p>
-<p><br>&lt;img src=&rdquo;../images/00-run-mvn.png &ldquo;run&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-run-mvn.png &ldquo;run&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -480,249 +480,248 @@ <h3 id="step-4-import-the-swagger-specification">Step 4: Import the Swagger spec
 </li>
 <li>
 <p>If the <code>CamelRoutes.java</code> hasn&rsquo;t appeared, please right-click on the <code>location-service</code> project and click <strong>Refresh</strong> to manually refresh the project tree.</p>
-<p><br>&lt;img src=&rdquo;../images/00-camel-routes.png &ldquo;camel&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java">    <span style="color:#f92672">package</span> com.redhat<span style="color:#f92672">;</span>
-
-    <span style="color:#f92672">import</span> javax.annotation.Generated<span style="color:#f92672">;</span>
-    <span style="color:#f92672">import</span> org.apache.camel.builder.RouteBuilder<span style="color:#f92672">;</span>
-    <span style="color:#f92672">import</span> org.apache.camel.model.rest.RestParamType<span style="color:#f92672">;</span>
-
-    <span style="color:#75715e">/**
-</span><span style="color:#75715e">     * Generated from Swagger specification by Camel REST DSL generator.
-</span><span style="color:#75715e">     */</span>
-    <span style="color:#a6e22e">@Generated</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;org.apache.camel.generator.swagger.PathGenerator&#34;</span><span style="color:#f92672">)</span>
-    <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">final</span> <span style="color:#66d9ef">class</span> <span style="color:#a6e22e">CamelRoutes</span> <span style="color:#66d9ef">extends</span> RouteBuilder <span style="color:#f92672">{</span>
-        <span style="color:#75715e">/**
-</span><span style="color:#75715e">         * Defines Apache Camel routes using REST DSL fluent API.
-</span><span style="color:#75715e">         */</span>
-        <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span><span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-            rest<span style="color:#f92672">()</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:rest1&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">post</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:rest2&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations/{id}&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">param</span><span style="color:#f92672">()</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">name</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;id&#34;</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>RestParamType<span style="color:#f92672">.</span><span style="color:#a6e22e">path</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">dataType</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;integer&#34;</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">required</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">endParam</span><span style="color:#f92672">()</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:rest3&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/location/phone/{id}&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">param</span><span style="color:#f92672">()</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">name</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;id&#34;</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>RestParamType<span style="color:#f92672">.</span><span style="color:#a6e22e">path</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">dataType</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;integer&#34;</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">required</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">endParam</span><span style="color:#f92672">()</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:rest4&#34;</span><span style="color:#f92672">);</span>
-        <span style="color:#f92672">}</span>
-    <span style="color:#f92672">}</span>
-</code></pre></div></li>
+<p><br>&lt;img src=&quot;../images/00-camel-routes.png &ldquo;camel&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>    <span style="color:#f92672">package</span> com.redhat;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">import</span> javax.annotation.Generated;
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">import</span> org.apache.camel.builder.RouteBuilder;
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">import</span> org.apache.camel.model.rest.RestParamType;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    <span style="color:#75715e">/**
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">     * Generated from Swagger specification by Camel REST DSL generator.
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">     */</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#a6e22e">@Generated</span>(<span style="color:#e6db74">&#34;org.apache.camel.generator.swagger.PathGenerator&#34;</span>)
+</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">final</span> <span style="color:#66d9ef">class</span> <span style="color:#a6e22e">CamelRoutes</span> <span style="color:#66d9ef">extends</span> RouteBuilder {
+</span></span><span style="display:flex;"><span>        <span style="color:#75715e">/**
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">         * Defines Apache Camel routes using REST DSL fluent API.
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">         */</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span>() {
+</span></span><span style="display:flex;"><span>            rest()
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/locations&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:rest1&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">post</span>(<span style="color:#e6db74">&#34;/locations&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:rest2&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/locations/{id}&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">param</span>()
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">name</span>(<span style="color:#e6db74">&#34;id&#34;</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">type</span>(RestParamType.<span style="color:#a6e22e">path</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">dataType</span>(<span style="color:#e6db74">&#34;integer&#34;</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">required</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">endParam</span>()
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:rest3&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/location/phone/{id}&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">param</span>()
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">name</span>(<span style="color:#e6db74">&#34;id&#34;</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">type</span>(RestParamType.<span style="color:#a6e22e">path</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">dataType</span>(<span style="color:#e6db74">&#34;integer&#34;</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">required</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">endParam</span>()
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:rest4&#34;</span>);
+</span></span><span style="display:flex;"><span>        }
+</span></span><span style="display:flex;"><span>    }
+</span></span></code></pre></div></li>
 </ul>
 <ol>
 <li>
 <p>Open the generated <code>CamelRoutes.java</code> file.  Replace the contents of the CamelRoutes.java with the contents below:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">package</span> com.redhat<span style="color:#f92672">;</span>
-
-<span style="color:#f92672">import</span> javax.annotation.Generated<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> org.apache.camel.builder.RouteBuilder<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> org.apache.camel.model.rest.RestParamType<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> com.redhat.processor.*<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> com.redhat.model.*<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> org.springframework.stereotype.Component<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> org.apache.camel.model.rest.RestBindingMode<span style="color:#f92672">;</span>
-
-    <span style="color:#75715e">/**
-</span><span style="color:#75715e">     * Generated from Swagger specification by Camel REST DSL generator.
-</span><span style="color:#75715e">     */</span>
-    <span style="color:#a6e22e">@Generated</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;org.apache.camel.generator.swagger.PathGenerator&#34;</span><span style="color:#f92672">)</span>
-    <span style="color:#a6e22e">@Component</span>
-    <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">final</span> <span style="color:#66d9ef">class</span> <span style="color:#a6e22e">CamelRoutes</span> <span style="color:#66d9ef">extends</span> RouteBuilder <span style="color:#f92672">{</span>
-        <span style="color:#75715e">/**
-</span><span style="color:#75715e">         * Defines Apache Camel routes using REST DSL fluent API.
-</span><span style="color:#75715e">         */</span>
-        <span style="color:#a6e22e">@Override</span>
-        <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span><span style="color:#f92672">()</span> <span style="color:#66d9ef">throws</span> Exception <span style="color:#f92672">{</span>
-
-            ContactInfoResultProcessor ciResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> ContactInfoResultProcessor<span style="color:#f92672">();</span>
-            LocationResultProcessor locationResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> LocationResultProcessor<span style="color:#f92672">();</span>
-
-            restConfiguration<span style="color:#f92672">()</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">component</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;servlet&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">port</span><span style="color:#f92672">(</span>8080<span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">bindingMode</span><span style="color:#f92672">(</span>RestBindingMode<span style="color:#f92672">.</span><span style="color:#a6e22e">json</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">contextPath</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">dataFormatProperty</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;prettyPrint&#34;</span><span style="color:#f92672">,</span> <span style="color:#e6db74">&#34;true&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">enableCORS</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">apiContextPath</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/api-doc&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;api.title&#34;</span><span style="color:#f92672">,</span> <span style="color:#e6db74">&#34;Location and Contact Info API&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;api.version&#34;</span><span style="color:#f92672">,</span> <span style="color:#e6db74">&#34;1.0.0&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">;</span>
-
-            rest<span style="color:#f92672">()</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getalllocations&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">post</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>Location<span style="color:#f92672">.</span><span style="color:#a6e22e">class</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:addlocation&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations/{id}&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">param</span><span style="color:#f92672">()</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">name</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;id&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>RestParamType<span style="color:#f92672">.</span><span style="color:#a6e22e">path</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">dataType</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;integer&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">required</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">endParam</span><span style="color:#f92672">()</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocation&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/location/phone/{id}&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">param</span><span style="color:#f92672">()</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">name</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;id&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>RestParamType<span style="color:#f92672">.</span><span style="color:#a6e22e">path</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">dataType</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;integer&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">required</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">endParam</span><span style="color:#f92672">()</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">outType</span><span style="color:#f92672">(</span>ContactInfo<span style="color:#f92672">.</span><span style="color:#a6e22e">class</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">;</span>
-
-            from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getalllocations&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:select * from locations?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>locationResultProcessor<span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">log</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body}&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">;</span>
-
-            from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocation&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:select * from locations where id=cast(:#id as int)?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>locationResultProcessor<span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">choice</span><span style="color:#f92672">()</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">when</span><span style="color:#f92672">(</span>simple<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body.size} &gt; 0&#34;</span><span style="color:#f92672">))</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">setBody</span><span style="color:#f92672">(</span>simple<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body[0]}&#34;</span><span style="color:#f92672">))</span>
-                    <span style="color:#f92672">.</span><span style="color:#a6e22e">otherwise</span><span style="color:#f92672">()</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">setHeader</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;HTTP_RESPONSE_CODE&#34;</span><span style="color:#f92672">,</span>constant<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;404&#34;</span><span style="color:#f92672">))</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">log</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body}&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">;</span>
-
-            from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:addlocation&#34;</span><span style="color:#f92672">)</span>
-                        <span style="color:#f92672">.</span><span style="color:#a6e22e">log</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;Creating new location&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:INSERT INTO locations (id,name,lat,lng,location_type,status) VALUES (:#${body.id},:#${body.name},:#${body.location.lat},:#${body.location.lng},:#${body.type},:#${body.status});?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">;</span>
-
-            from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:select * from location_detail where id=cast(:#id as int)?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>ciResultProcessor<span style="color:#f92672">)</span>
-        <span style="color:#f92672">;</span>                
-      <span style="color:#f92672">}</span>
-    <span style="color:#f92672">}</span>
-
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span><span style="color:#f92672">package</span> com.redhat;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> javax.annotation.Generated;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> org.apache.camel.builder.RouteBuilder;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> org.apache.camel.model.rest.RestParamType;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> com.redhat.processor.*;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> com.redhat.model.*;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> org.springframework.stereotype.Component;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> org.apache.camel.model.rest.RestBindingMode;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    <span style="color:#75715e">/**
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">     * Generated from Swagger specification by Camel REST DSL generator.
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">     */</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#a6e22e">@Generated</span>(<span style="color:#e6db74">&#34;org.apache.camel.generator.swagger.PathGenerator&#34;</span>)
+</span></span><span style="display:flex;"><span>    <span style="color:#a6e22e">@Component</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">final</span> <span style="color:#66d9ef">class</span> <span style="color:#a6e22e">CamelRoutes</span> <span style="color:#66d9ef">extends</span> RouteBuilder {
+</span></span><span style="display:flex;"><span>        <span style="color:#75715e">/**
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">         * Defines Apache Camel routes using REST DSL fluent API.
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">         */</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#a6e22e">@Override</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span>() <span style="color:#66d9ef">throws</span> Exception {
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            ContactInfoResultProcessor ciResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> ContactInfoResultProcessor();
+</span></span><span style="display:flex;"><span>            LocationResultProcessor locationResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> LocationResultProcessor();
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            restConfiguration()
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">component</span>(<span style="color:#e6db74">&#34;servlet&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">port</span>(8080)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">bindingMode</span>(RestBindingMode.<span style="color:#a6e22e">json</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">contextPath</span>(<span style="color:#e6db74">&#34;/&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">dataFormatProperty</span>(<span style="color:#e6db74">&#34;prettyPrint&#34;</span>, <span style="color:#e6db74">&#34;true&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">enableCORS</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">apiContextPath</span>(<span style="color:#e6db74">&#34;/api-doc&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;api.title&#34;</span>, <span style="color:#e6db74">&#34;Location and Contact Info API&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;api.version&#34;</span>, <span style="color:#e6db74">&#34;1.0.0&#34;</span>)
+</span></span><span style="display:flex;"><span>        ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            rest()
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/locations&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getalllocations&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">post</span>(<span style="color:#e6db74">&#34;/locations&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">type</span>(Location.<span style="color:#a6e22e">class</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:addlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/locations/{id}&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">param</span>()
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">name</span>(<span style="color:#e6db74">&#34;id&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">type</span>(RestParamType.<span style="color:#a6e22e">path</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">dataType</span>(<span style="color:#e6db74">&#34;integer&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">required</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">endParam</span>()
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/location/phone/{id}&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">param</span>()
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">name</span>(<span style="color:#e6db74">&#34;id&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">type</span>(RestParamType.<span style="color:#a6e22e">path</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">dataType</span>(<span style="color:#e6db74">&#34;integer&#34;</span>)
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">required</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">endParam</span>()
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">outType</span>(ContactInfo.<span style="color:#a6e22e">class</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span>)
+</span></span><span style="display:flex;"><span>        ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            from(<span style="color:#e6db74">&#34;direct:getalllocations&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:select * from locations?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">process</span>(locationResultProcessor)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">log</span>(<span style="color:#e6db74">&#34;${body}&#34;</span>)
+</span></span><span style="display:flex;"><span>        ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            from(<span style="color:#e6db74">&#34;direct:getlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:select * from locations where id=cast(:#id as int)?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">process</span>(locationResultProcessor)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">choice</span>()
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">when</span>(simple(<span style="color:#e6db74">&#34;${body.size} &gt; 0&#34;</span>))
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">setBody</span>(simple(<span style="color:#e6db74">&#34;${body[0]}&#34;</span>))
+</span></span><span style="display:flex;"><span>                    .<span style="color:#a6e22e">otherwise</span>()
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">setHeader</span>(<span style="color:#e6db74">&#34;HTTP_RESPONSE_CODE&#34;</span>,constant(<span style="color:#e6db74">&#34;404&#34;</span>))
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">log</span>(<span style="color:#e6db74">&#34;${body}&#34;</span>)
+</span></span><span style="display:flex;"><span>        ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            from(<span style="color:#e6db74">&#34;direct:addlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>                        .<span style="color:#a6e22e">log</span>(<span style="color:#e6db74">&#34;Creating new location&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:INSERT INTO locations (id,name,lat,lng,location_type,status) VALUES (:#${body.id},:#${body.name},:#${body.location.lat},:#${body.location.lng},:#${body.type},:#${body.status});?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>            ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>            from(<span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:select * from location_detail where id=cast(:#id as int)?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">process</span>(ciResultProcessor)
+</span></span><span style="display:flex;"><span>        ;                
+</span></span><span style="display:flex;"><span>      }
+</span></span><span style="display:flex;"><span>    }
+</span></span></code></pre></div></li>
 <li>
 <p>Next, notice instantiation of our newly created Result Processors&rsquo; with the include the necessary imports.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-<span style="color:#f92672">import</span> com.redhat.processor.*<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> com.redhat.model.*<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> org.springframework.stereotype.Component<span style="color:#f92672">;</span>
-<span style="color:#f92672">import</span> org.apache.camel.model.rest.RestBindingMode<span style="color:#f92672">;</span>
-<span style="color:#f92672">...</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> com.redhat.processor.*;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> com.redhat.model.*;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> org.springframework.stereotype.Component;
+</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> org.apache.camel.model.rest.RestBindingMode;
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div></li>
 <li>
 <p>As we&rsquo;re using SpringBoot, we also include the <code>@Component</code> declaration to the class definition statement (under the <code>@Generated</code>).</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java">  <span style="color:#f92672">...</span>
-    <span style="color:#75715e">/**
-</span><span style="color:#75715e">    * Generated from Swagger specification by Camel REST DSL generator.
-</span><span style="color:#75715e">    */</span>
-    <span style="color:#a6e22e">@Generated</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;org.apache.camel.generator.swagger.PathGenerator&#34;</span><span style="color:#f92672">)</span>
-    <span style="color:#a6e22e">@Component</span>
-    <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">class</span> <span style="color:#a6e22e">CamelRoutes</span> <span style="color:#66d9ef">extends</span> RouteBuilder <span style="color:#f92672">{</span>
-    <span style="color:#f92672">...</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>  ...
+</span></span><span style="display:flex;"><span>	<span style="color:#75715e">/**
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">	* Generated from Swagger specification by Camel REST DSL generator.
+</span></span></span><span style="display:flex;"><span><span style="color:#75715e">	*/</span>
+</span></span><span style="display:flex;"><span>	<span style="color:#a6e22e">@Generated</span>(<span style="color:#e6db74">&#34;org.apache.camel.generator.swagger.PathGenerator&#34;</span>)
+</span></span><span style="display:flex;"><span>	<span style="color:#a6e22e">@Component</span>
+</span></span><span style="display:flex;"><span>	<span style="color:#66d9ef">public</span> <span style="color:#66d9ef">class</span> <span style="color:#a6e22e">CamelRoutes</span> <span style="color:#66d9ef">extends</span> RouteBuilder {
+</span></span><span style="display:flex;"><span>	...
+</span></span></code></pre></div></li>
 <li>
 <p>Next notice the <code>@Override</code> statement for our <code>configure()</code> method, and include references to our result processors.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-<span style="color:#a6e22e">@Override</span>
-<span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span><span style="color:#f92672">()</span> <span style="color:#66d9ef">throws</span> Exception <span style="color:#f92672">{</span>		
-
-    ContactInfoResultProcessor ciResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> ContactInfoResultProcessor<span style="color:#f92672">();</span>
-    LocationResultProcessor locationResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> LocationResultProcessor<span style="color:#f92672">();</span>
-<span style="color:#f92672">...</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span><span style="color:#a6e22e">@Override</span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span>() <span style="color:#66d9ef">throws</span> Exception {		
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>	ContactInfoResultProcessor ciResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> ContactInfoResultProcessor();
+</span></span><span style="display:flex;"><span>	LocationResultProcessor locationResultProcessor <span style="color:#f92672">=</span> <span style="color:#66d9ef">new</span> LocationResultProcessor();
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div></li>
 <li>
 <p>In order to startup an HTTP server for our REST service, we instantiate the <code>restConfiguration</code> bean with the corresponding properties.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-    restConfiguration<span style="color:#f92672">()</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">component</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;servlet&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">port</span><span style="color:#f92672">(</span>8080<span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">bindingMode</span><span style="color:#f92672">(</span>RestBindingMode<span style="color:#f92672">.</span><span style="color:#a6e22e">json</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">contextPath</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">dataFormatProperty</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;prettyPrint&#34;</span><span style="color:#f92672">,</span> <span style="color:#e6db74">&#34;true&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">enableCORS</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">apiContextPath</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/api-doc&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;api.title&#34;</span><span style="color:#f92672">,</span> <span style="color:#e6db74">&#34;Location and Contact Info API&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;api.version&#34;</span><span style="color:#f92672">,</span> <span style="color:#e6db74">&#34;1.0.0&#34;</span><span style="color:#f92672">)</span>
-    <span style="color:#f92672">;</span>
-<span style="color:#f92672">...</span>
-</code></pre></div><p>If the IDE has any issues compiling the code and you receive errors, then navigate to <strong>Project &gt; Configure Classpath</strong> then click <strong>Done</strong>.  This will trigger the compiler to run in the background and should eliminate any errors.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>	restConfiguration()
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">component</span>(<span style="color:#e6db74">&#34;servlet&#34;</span>)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">port</span>(8080)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">bindingMode</span>(RestBindingMode.<span style="color:#a6e22e">json</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">contextPath</span>(<span style="color:#e6db74">&#34;/&#34;</span>)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">dataFormatProperty</span>(<span style="color:#e6db74">&#34;prettyPrint&#34;</span>, <span style="color:#e6db74">&#34;true&#34;</span>)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">enableCORS</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">apiContextPath</span>(<span style="color:#e6db74">&#34;/api-doc&#34;</span>)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;api.title&#34;</span>, <span style="color:#e6db74">&#34;Location and Contact Info API&#34;</span>)
+</span></span><span style="display:flex;"><span>    	.<span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;api.version&#34;</span>, <span style="color:#e6db74">&#34;1.0.0&#34;</span>)
+</span></span><span style="display:flex;"><span>    ;
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div><p>If the IDE has any issues compiling the code and you receive errors, then navigate to <strong>Project &gt; Configure Classpath</strong> then click <strong>Done</strong>.  This will trigger the compiler to run in the background and should eliminate any errors.</p>
 <p>Notice that we now have both ResultProcessor&rsquo;s instantiated, and we&rsquo;ve stood-up an Servlet HTTP listener for our RESTful endpoint, together with some basic self-documenting API docs that describe our new service.</p>
 </li>
 <li>
 <p>Next notice how we implement our Camel routes.  We create 4 routes, each matching their associated HTTP GET / POST endpoint.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-    from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getalllocations&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:select * from locations?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>locationResultProcessor<span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">log</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body}&#34;</span><span style="color:#f92672">)</span>
-     <span style="color:#f92672">;</span>
-
-    from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocation&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:select * from locations where id=cast(:#id as int)?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>locationResultProcessor<span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">choice</span><span style="color:#f92672">()</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">when</span><span style="color:#f92672">(</span>simple<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body.size} &gt; 0&#34;</span><span style="color:#f92672">))</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">setBody</span><span style="color:#f92672">(</span>simple<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body[0]}&#34;</span><span style="color:#f92672">))</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">otherwise</span><span style="color:#f92672">()</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">setHeader</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;HTTP_RESPONSE_CODE&#34;</span><span style="color:#f92672">,</span>constant<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;404&#34;</span><span style="color:#f92672">))</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">log</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${body}&#34;</span><span style="color:#f92672">)</span>
-     <span style="color:#f92672">;</span>
-
-    from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:addlocation&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">log</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;Creating new location&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:INSERT INTO locations (id,name,lat,lng,location_type,status) VALUES (:#${body.id},:#${body.name},:#${body.location.lat},:#${body.location.lng},:#${body.type},:#${body.status});?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-     <span style="color:#f92672">;</span>
-
-    from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;sql:select * from location_detail where id=cast(:#id as int)?dataSource=dataSource&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>ciResultProcessor<span style="color:#f92672">)</span>
-     <span style="color:#f92672">;</span>
-<span style="color:#f92672">...</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>    from(<span style="color:#e6db74">&#34;direct:getalllocations&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:select * from locations?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">process</span>(locationResultProcessor)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">log</span>(<span style="color:#e6db74">&#34;${body}&#34;</span>)
+</span></span><span style="display:flex;"><span>     ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    from(<span style="color:#e6db74">&#34;direct:getlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:select * from locations where id=cast(:#id as int)?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">process</span>(locationResultProcessor)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">choice</span>()
+</span></span><span style="display:flex;"><span>			.<span style="color:#a6e22e">when</span>(simple(<span style="color:#e6db74">&#34;${body.size} &gt; 0&#34;</span>))
+</span></span><span style="display:flex;"><span>				.<span style="color:#a6e22e">setBody</span>(simple(<span style="color:#e6db74">&#34;${body[0]}&#34;</span>))
+</span></span><span style="display:flex;"><span>			.<span style="color:#a6e22e">otherwise</span>()
+</span></span><span style="display:flex;"><span>				.<span style="color:#a6e22e">setHeader</span>(<span style="color:#e6db74">&#34;HTTP_RESPONSE_CODE&#34;</span>,constant(<span style="color:#e6db74">&#34;404&#34;</span>))
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">log</span>(<span style="color:#e6db74">&#34;${body}&#34;</span>)
+</span></span><span style="display:flex;"><span>     ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    from(<span style="color:#e6db74">&#34;direct:addlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>        		.<span style="color:#a6e22e">log</span>(<span style="color:#e6db74">&#34;Creating new location&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:INSERT INTO locations (id,name,lat,lng,location_type,status) VALUES (:#${body.id},:#${body.name},:#${body.location.lat},:#${body.location.lng},:#${body.type},:#${body.status});?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>     ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    from(<span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;sql:select * from location_detail where id=cast(:#id as int)?dataSource=dataSource&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">process</span>(ciResultProcessor)
+</span></span><span style="display:flex;"><span>     ;
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div></li>
 <li>
 <p>Lastly, notice the RESTdsl code to accommodate our new routes.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-   rest<span style="color:#f92672">()</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getalllocations&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">post</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>Location<span style="color:#f92672">.</span><span style="color:#a6e22e">class</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:addlocation&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/locations/{id}&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">param</span><span style="color:#f92672">()</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">name</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;id&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>RestParamType<span style="color:#f92672">.</span><span style="color:#a6e22e">path</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">dataType</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;integer&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">required</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">endParam</span><span style="color:#f92672">()</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocation&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/location/phone/{id}&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">param</span><span style="color:#f92672">()</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">name</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;id&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">type</span><span style="color:#f92672">(</span>RestParamType<span style="color:#f92672">.</span><span style="color:#a6e22e">path</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">dataType</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;integer&#34;</span><span style="color:#f92672">)</span>
-                <span style="color:#f92672">.</span><span style="color:#a6e22e">required</span><span style="color:#f92672">(</span><span style="color:#66d9ef">true</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">endParam</span><span style="color:#f92672">()</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">outType</span><span style="color:#f92672">(</span>ContactInfo<span style="color:#f92672">.</span><span style="color:#a6e22e">class</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span><span style="color:#f92672">)</span>
-    <span style="color:#f92672">;</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>   rest()
+</span></span><span style="display:flex;"><span>        .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/locations&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getalllocations&#34;</span>)
+</span></span><span style="display:flex;"><span>        .<span style="color:#a6e22e">post</span>(<span style="color:#e6db74">&#34;/locations&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">type</span>(Location.<span style="color:#a6e22e">class</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:addlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>        .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/locations/{id}&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">param</span>()
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">name</span>(<span style="color:#e6db74">&#34;id&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">type</span>(RestParamType.<span style="color:#a6e22e">path</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">dataType</span>(<span style="color:#e6db74">&#34;integer&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">required</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">endParam</span>()
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getlocation&#34;</span>)
+</span></span><span style="display:flex;"><span>        .<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/location/phone/{id}&#34;</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">param</span>()
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">name</span>(<span style="color:#e6db74">&#34;id&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">type</span>(RestParamType.<span style="color:#a6e22e">path</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">dataType</span>(<span style="color:#e6db74">&#34;integer&#34;</span>)
+</span></span><span style="display:flex;"><span>                .<span style="color:#a6e22e">required</span>(<span style="color:#66d9ef">true</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">endParam</span>()
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">outType</span>(ContactInfo.<span style="color:#a6e22e">class</span>)
+</span></span><span style="display:flex;"><span>            .<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getlocationdetail&#34;</span>)
+</span></span><span style="display:flex;"><span>    ;
+</span></span></code></pre></div></li>
 <li>
 <p>Before we test our newly created Camel Routes, we need to update <code>src/main/resources/application.properties</code> to point to our Postgres database.</p>
 </li>
@@ -733,29 +732,29 @@ <h3 id="step-4-import-the-swagger-specification">Step 4: Import the Swagger spec
 </li>
 <li>
 <p>Replace <code>OCPPROJECT</code> with the OpenShift project name you used in the previous step to host Postgres Database (this should be your unique username).</p>
-<p><br>&lt;img src=&rdquo;../images/00-update-properties.png &ldquo;Update Properties&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-update-properties.png &ldquo;Update Properties&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
 <li>
 <p>Now we are ready to test our new Camel route locally. To do this, navigate back to the <strong>Manage commands</strong> screen, double-click the <strong>run:spring-boot</strong> script and hit <strong>Run</strong>.  The script will run locally in Eclipse Che.</p>
-<p><br>&lt;img src=&rdquo;../images/00-run-locally.png &ldquo;Maven Deploy&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-run-locally.png &ldquo;Maven Deploy&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Once SpringBoot has started-up, right-click the dev-machine (under <strong>Machines</strong>) and select <strong>Servers</strong>.  Click the link corresponding to port 8080.  A new tab should open with a <strong>Page Can&rsquo;t be Found</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-open-servers.png &ldquo;Open Servers&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-open-servers.png &ldquo;Open Servers&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the route link above the location-service pod and append <code>/locations</code> to the URI.  As a result, you should receive a list of all locations</p>
-<p><br>&lt;img src=&rdquo;../images/00-location-list.png &ldquo;Location List&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-location-list.png &ldquo;Location List&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Now that we&rsquo;ve tested our API service implementation locally, we can deploy it to our running OpenShift environment.  First we need to login to OpenShift via the Terminal.  Navigate back to the OpenShift web UI and click the <strong>Copy Login Command</strong> link.</p>
-<p><br>&lt;img src=&rdquo;../images/00-login-ocp-cli.png &ldquo;OCP CLI Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-login-ocp-cli.png &ldquo;OCP CLI Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Navigate back to Eclipse Che, open the terminal, and paste the login command from your clipboard.  Once you&rsquo;ve logged-in, select the OpenShift project you used earlier using <code>oc project userX</code> (replacing userX with your username).</p>
-<p><br>&lt;img src=&rdquo;../images/00-login-terminal.png &ldquo;OCP Terminal Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-login-terminal.png &ldquo;OCP Terminal Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>To run the fabric8 Maven command to deploy our project, navigate back to the <strong>Manage commands</strong> screen, double-click the <strong>fabric8:deploy</strong> script.</p>
@@ -769,19 +768,19 @@ <h3 id="step-4-import-the-swagger-specification">Step 4: Import the Swagger spec
 <ol>
 <li>
 <p>If the deployment script completes successfully, navigate back to your OCPPROJECT web console and verify the pod is running in your UserX project.</p>
-<p><br>&lt;img src=&rdquo;../images/00-verify-location-service.png &ldquo;Location Service&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-verify-location-service.png &ldquo;Location Service&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the route link above the location-service pod and append <code>locations</code> to the URI.  Initially, you may receive a <code>404</code> error when opening the route URL, but once you append <code>locations</code> and refresh you should receive a list of all locations</p>
-<p><br>&lt;img src=&rdquo;../images/00-location-list.png &ldquo;Location List&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-location-list.png &ldquo;Location List&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You can also search for individual locations by adjusting the URI to <code>/locations/{id}</code> e.g. <code>/locations/100</code>.</p>
 </li>
 <li>
 <p>Lastly, via the Eclipse Che terminal, test the HTTP POST using curl.  You can use the following below. Remember to the Route Link you got previously and replace OCPPROJECT with your username.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">curl --header <span style="color:#e6db74">&#34;Content-Type: application/json&#34;</span> --request POST --data <span style="color:#e6db74">&#39;{&#34;id&#34;: 101,&#34;name&#34;: &#34;Kakadu&#34;,&#34;type&#34;: &#34;HQ&#34;,&#34;status&#34;: &#34;1&#34;,&#34;location&#34;: {&#34;lat&#34;: &#34;78.88436&#34;,&#34;lng&#34;: &#34;99.05295&#34;}}&#39;</span> http://location-service-OCPPROJECT.apps.ocp-ai.redhatgov.io/locations
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>curl --header <span style="color:#e6db74">&#34;Content-Type: application/json&#34;</span> --request POST --data <span style="color:#e6db74">&#39;{&#34;id&#34;: 101,&#34;name&#34;: &#34;Kakadu&#34;,&#34;type&#34;: &#34;HQ&#34;,&#34;status&#34;: &#34;1&#34;,&#34;location&#34;: {&#34;lat&#34;: &#34;78.88436&#34;,&#34;lng&#34;: &#34;99.05295&#34;}}&#39;</span> http://location-service-OCPPROJECT.apps.ocp-ai.redhatgov.io/locations
+</span></span></code></pre></div></li>
 <li>
 <p>If the HTTP POST is successful, you should be able to view it by repeating the HTTP GET /locations test.</p>
 </li>
@@ -828,7 +827,7 @@ <h2 id="summary">Summary</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab04/index.html b/workshops/agile_integrations_dev/lab04/index.html
index 4336d2895..cb106c5d3 100644
--- a/workshops/agile_integrations_dev/lab04/index.html
+++ b/workshops/agile_integrations_dev/lab04/index.html
@@ -324,7 +324,7 @@ <h3 id="contract-first-api-development-wrapping-an-existing-soap-service-impleme
 <li>Duration: 20 mins</li>
 <li>Audience: Developers and Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-03.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-03.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>Another important use case in developing API&rsquo;s is to take an existing legacy SOAP service and wrap it with a new RESTful endpoint.  This SOAP to REST transformation is implemented in the API service layer (Fuse).  This lab will walk you through taking an existing SOAP contract (WSDL), converting it to Java POJO&rsquo;s and exposing it using Camel REST DSL.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -334,35 +334,35 @@ <h3 id="step-1-import-the-sample-soap-project-into-your-openshift-project">Step
 <ol>
 <li>
 <p>Navigate back to your Eclipse Che workspace and open the terminal window.</p>
-<p><br>&lt;img src=&rdquo;../images/00-open-terminal.png &ldquo;Open Terminal&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-open-terminal.png &ldquo;Open Terminal&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Log into the Openshift console:</p>
-<p><br>&lt;img src=&rdquo;../images/00-openshift-loginpage.png &ldquo;Commend Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-openshift-loginpage.png &ldquo;Commend Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Obtain your user login command by clicking on your username on the top right hand corner and select <strong>Copy Login Command</strong></p>
-<p><br>&lt;img src=&rdquo;../images/00-commend-login.png &ldquo;Commend Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-commend-login.png &ldquo;Commend Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Paste the login command for Openshift via the Terminal window. Use the double check the {OPENSHIFT_APP_URL} matches the environment given to you by the instructor</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc login  <span style="color:#f92672">{</span>OPENSHIFT_APP_URL<span style="color:#f92672">}</span> --token<span style="color:#f92672">=</span>XXXXX
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc login  <span style="color:#f92672">{</span>OPENSHIFT_APP_URL<span style="color:#f92672">}</span> --token<span style="color:#f92672">=</span>XXXXX
+</span></span></code></pre></div></li>
 <li>
 <p>Build and deploy the SOAP application using source to image(S2i) template. Paste the commend to the terminal.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc new-app s2i-fuse71-spring-boot-camel -p GIT_REPO<span style="color:#f92672">=</span>https://github.com/epe105/dayinthelife-integration -p CONTEXT_DIR<span style="color:#f92672">=</span>/projects/location-soap -p APP_NAME<span style="color:#f92672">=</span>location-soap -p GIT_REF<span style="color:#f92672">=</span>master -n <span style="color:#f92672">[</span>OCPPROJECT<span style="color:#f92672">]</span>
-</code></pre></div><p><em>Remember to replace the <strong>[OCPPROJECT]</strong> with the OpenShift project(NameSpace) you used in last lab.  [OCPPROJECT] should be your username</em></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc new-app s2i-fuse71-spring-boot-camel -p GIT_REPO<span style="color:#f92672">=</span>https://github.com/epe105/dayinthelife-integration -p CONTEXT_DIR<span style="color:#f92672">=</span>/projects/location-soap -p APP_NAME<span style="color:#f92672">=</span>location-soap -p GIT_REF<span style="color:#f92672">=</span>master -n <span style="color:#f92672">[</span>OCPPROJECT<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p><em>Remember to replace the <strong>[OCPPROJECT]</strong> with the OpenShift project(NameSpace) you used in last lab.  [OCPPROJECT] should be your username</em></p>
 </li>
 <li>
 <p>Once the build and deploy is complete, navigate back to your Openshift web console and verify the project is running.</p>
-<p><br>&lt;img src=&rdquo;../images/00-verify-location-soap.png &ldquo;Verify Pod&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-verify-location-soap.png &ldquo;Verify Pod&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="step-2-modify-the-skeleton-location-soap2rest-project">Step 2: Modify the skeleton location-soap2rest project</h3>
 <ol>
 <li>
 <p>In the OpenShift console, click on the route associated with the <code>location-soap</code> deployment.  A pop-up will appear.  Append the <code>/ws/location?wsdl</code> path to the URI and verify the WSDL appears. Copy the link to the clipboard.</p>
-<p><br>&lt;img src=&rdquo;../images/00-verify-wsdl.png &ldquo;Verify WSDL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-verify-wsdl.png &ldquo;Verify WSDL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Return to your Eclipse Che workspace and open the <code>dayintelife-import/location-soap2rest</code> project.</p>
@@ -380,31 +380,31 @@ <h3 id="step-2-modify-the-skeleton-location-soap2rest-project">Step 2: Modify th
 </li>
 <li>
 <p><em>Be sure to replace userX with your username.</em></p>
-<p><br>&lt;img src=&rdquo;../images/00-uncomment-codegen.png &ldquo;Uncomment codegen plugin&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-uncomment-codegen.png &ldquo;Uncomment codegen plugin&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
 <li>
 <p>We now need to generate the POJO objects from the WSDL contract.  To do this, change to the <strong>Manage commands</strong> view and double-click the <code>run generate-sources</code> script.  Click <strong>Run</strong> to execute the script.</p>
-<p><br>&lt;img src=&rdquo;../images/00-generate-sources.png &ldquo;Generate Sources&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-generate-sources.png &ldquo;Generate Sources&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Once the script has completed, navigate back to the <strong>Workspace</strong> view and open the <code>src/main/java/com/redhat</code> folder.  Notice that there are a bunch of new POJO classes that were created by the Maven script.</p>
-<p><br>&lt;img src=&rdquo;../images/00-verify-pojos.png &ldquo;Verify Pojos&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-verify-pojos.png &ldquo;Verify Pojos&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Open up the <code>CamelRoutes.java</code> file.  Notice that the existing implementation is barebones. First of all, we need to enter the SOAP service address and WSDL location for our CXF client to call after the camelContext and before the @Override.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-
-<span style="color:#a6e22e">@Autowired</span>
-<span style="color:#66d9ef">private</span> CamelContext camelContext<span style="color:#f92672">;</span>
-
-<span style="color:#66d9ef">private</span> <span style="color:#66d9ef">static</span> <span style="color:#66d9ef">final</span> String SERVICE_ADDRESS <span style="color:#f92672">=</span> <span style="color:#e6db74">&#34;http://localhost:8080/ws/location&#34;</span><span style="color:#f92672">;</span>
-<span style="color:#66d9ef">private</span> <span style="color:#66d9ef">static</span> <span style="color:#66d9ef">final</span> String WSDL_URL <span style="color:#f92672">=</span> <span style="color:#e6db74">&#34;http://localhost:8080/ws/location?wsdl&#34;</span><span style="color:#f92672">;</span>
-
-<span style="color:#a6e22e">@Override</span>
-<span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span><span style="color:#f92672">()</span> <span style="color:#66d9ef">throws</span> Exception <span style="color:#f92672">{</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#a6e22e">@Autowired</span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">private</span> CamelContext camelContext;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">private</span> <span style="color:#66d9ef">static</span> <span style="color:#66d9ef">final</span> String SERVICE_ADDRESS <span style="color:#f92672">=</span> <span style="color:#e6db74">&#34;http://localhost:8080/ws/location&#34;</span>;
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">private</span> <span style="color:#66d9ef">static</span> <span style="color:#66d9ef">final</span> String WSDL_URL <span style="color:#f92672">=</span> <span style="color:#e6db74">&#34;http://localhost:8080/ws/location?wsdl&#34;</span>;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#a6e22e">@Override</span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">configure</span>() <span style="color:#66d9ef">throws</span> Exception {
+</span></span></code></pre></div></li>
 </ol>
 <p>&hellip;<br>
 ```</p>
@@ -420,39 +420,38 @@ <h3 id="step-2-modify-the-skeleton-location-soap2rest-project">Step 2: Modify th
 </li>
 <li>
 <p>Check with your instructor if you are not sure.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-java" data-lang="java"><span style="color:#f92672">...</span>
-
-    rest<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/location&#34;</span><span style="color:#f92672">).</span><span style="color:#a6e22e">description</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;Location information&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">produces</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;application/json&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;/contact/{id}&#34;</span><span style="color:#f92672">).</span><span style="color:#a6e22e">description</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;Location Contact Info&#34;</span><span style="color:#f92672">)</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">responseMessage</span><span style="color:#f92672">().</span><span style="color:#a6e22e">code</span><span style="color:#f92672">(</span>200<span style="color:#f92672">).</span><span style="color:#a6e22e">message</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;Data successfully returned&#34;</span><span style="color:#f92672">).</span><span style="color:#a6e22e">endResponseMessage</span><span style="color:#f92672">()</span>
-            <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getalllocationphone&#34;</span><span style="color:#f92672">)</span>
-
-    <span style="color:#f92672">;</span>
-
-    from<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;direct:getalllocationphone&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">setBody</span><span style="color:#f92672">().</span><span style="color:#a6e22e">simple</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;${headers.id}&#34;</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">unmarshal</span><span style="color:#f92672">().</span><span style="color:#a6e22e">json</span><span style="color:#f92672">(</span>JsonLibrary<span style="color:#f92672">.</span><span style="color:#a6e22e">Jackson</span><span style="color:#f92672">)</span>
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">to</span><span style="color:#f92672">(</span><span style="color:#e6db74">&#34;cxf://http://location-soap-{YOUR_NAME_SPACE}.{OPENSHIFT_APP_URL}/ws/location?serviceClass=com.redhat.LocationDetailServicePortType&amp;defaultOperationName=contact&#34;</span><span style="color:#f92672">)</span>
-
-        <span style="color:#f92672">.</span><span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>
-                <span style="color:#66d9ef">new</span> Processor<span style="color:#f92672">(){</span>
-
-                    <span style="color:#a6e22e">@Override</span>
-                    <span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">process</span><span style="color:#f92672">(</span>Exchange exchange<span style="color:#f92672">)</span> <span style="color:#66d9ef">throws</span> Exception <span style="color:#f92672">{</span>
-                        <span style="color:#75715e">//LocationDetail locationDetail = new LocationDetail();
-</span><span style="color:#75715e"></span>                        <span style="color:#75715e">//locationDetail.setId(Integer.valueOf((String)exchange.getIn().getHeader(&#34;id&#34;)));
-</span><span style="color:#75715e"></span>
-                        MessageContentsList list <span style="color:#f92672">=</span> <span style="color:#f92672">(</span>MessageContentsList<span style="color:#f92672">)</span>exchange<span style="color:#f92672">.</span><span style="color:#a6e22e">getIn</span><span style="color:#f92672">().</span><span style="color:#a6e22e">getBody</span><span style="color:#f92672">();</span>
-
-                        exchange<span style="color:#f92672">.</span><span style="color:#a6e22e">getOut</span><span style="color:#f92672">().</span><span style="color:#a6e22e">setBody</span><span style="color:#f92672">((</span>ContactInfo<span style="color:#f92672">)</span>list<span style="color:#f92672">.</span><span style="color:#a6e22e">get</span><span style="color:#f92672">(</span>0<span style="color:#f92672">));</span>
-                    <span style="color:#f92672">}</span>
-                <span style="color:#f92672">}</span>
-        <span style="color:#f92672">)</span>
-
-    <span style="color:#f92672">;</span>
-
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>	rest(<span style="color:#e6db74">&#34;/location&#34;</span>).<span style="color:#a6e22e">description</span>(<span style="color:#e6db74">&#34;Location information&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">produces</span>(<span style="color:#e6db74">&#34;application/json&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/contact/{id}&#34;</span>).<span style="color:#a6e22e">description</span>(<span style="color:#e6db74">&#34;Location Contact Info&#34;</span>)
+</span></span><span style="display:flex;"><span>			.<span style="color:#a6e22e">responseMessage</span>().<span style="color:#a6e22e">code</span>(200).<span style="color:#a6e22e">message</span>(<span style="color:#e6db74">&#34;Data successfully returned&#34;</span>).<span style="color:#a6e22e">endResponseMessage</span>()
+</span></span><span style="display:flex;"><span>			.<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;direct:getalllocationphone&#34;</span>)
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>	;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>	from(<span style="color:#e6db74">&#34;direct:getalllocationphone&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">setBody</span>().<span style="color:#a6e22e">simple</span>(<span style="color:#e6db74">&#34;${headers.id}&#34;</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">unmarshal</span>().<span style="color:#a6e22e">json</span>(JsonLibrary.<span style="color:#a6e22e">Jackson</span>)
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">to</span>(<span style="color:#e6db74">&#34;cxf://http://location-soap-{YOUR_NAME_SPACE}.{OPENSHIFT_APP_URL}/ws/location?serviceClass=com.redhat.LocationDetailServicePortType&amp;defaultOperationName=contact&#34;</span>)
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>		.<span style="color:#a6e22e">process</span>(
+</span></span><span style="display:flex;"><span>				<span style="color:#66d9ef">new</span> Processor(){
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>					<span style="color:#a6e22e">@Override</span>
+</span></span><span style="display:flex;"><span>					<span style="color:#66d9ef">public</span> <span style="color:#66d9ef">void</span> <span style="color:#a6e22e">process</span>(Exchange exchange) <span style="color:#66d9ef">throws</span> Exception {
+</span></span><span style="display:flex;"><span>						<span style="color:#75715e">//LocationDetail locationDetail = new LocationDetail();</span>
+</span></span><span style="display:flex;"><span>						<span style="color:#75715e">//locationDetail.setId(Integer.valueOf((String)exchange.getIn().getHeader(&#34;id&#34;)));</span>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>						MessageContentsList list <span style="color:#f92672">=</span> (MessageContentsList)exchange.<span style="color:#a6e22e">getIn</span>().<span style="color:#a6e22e">getBody</span>();
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>						exchange.<span style="color:#a6e22e">getOut</span>().<span style="color:#a6e22e">setBody</span>((ContactInfo)list.<span style="color:#a6e22e">get</span>(0));
+</span></span><span style="display:flex;"><span>					}
+</span></span><span style="display:flex;"><span>				}
+</span></span><span style="display:flex;"><span>		)
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>	;
+</span></span></code></pre></div></li>
 </ul>
 <ol>
 <li>Now that we have our API service implementation, we can try to test this locally.  Navigate back to the <strong>Manage commands</strong> view and execute the <code>run spring-boot</code> script.</li>
@@ -487,11 +486,11 @@ <h3 id="step-2-modify-the-skeleton-location-soap2rest-project">Step 2: Modify th
 </li>
 <li>
 <p>Open the <code>fabic8:deploy</code> script and hit the <strong>Run</strong> button to deploy it to OpenShift.</p>
-<p><br>&lt;img src=&rdquo;../images/00-mvn-f8-deploy.png&rdquo; &ldquo;Maven Fabric8 Deploy&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-mvn-f8-deploy.png&quot; &ldquo;Maven Fabric8 Deploy&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>If the deployment script completes successfully, navigate back to your OCPPROJECT web console and verify the pod is running</p>
-<p><br>&lt;img src=&rdquo;../images/00-verify-pod.png&rdquo; &ldquo;Location SOAP2REST&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-verify-pod.png&quot; &ldquo;Location SOAP2REST&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on the route link above the location-soap2rest pod and append <code>/location/contact/2</code> to the URI.  As a result, you should get a contact back.</p>
@@ -539,7 +538,7 @@ <h2 id="summary">Summary</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab05/index.html b/workshops/agile_integrations_dev/lab05/index.html
index 01476eeff..167d89dfc 100644
--- a/workshops/agile_integrations_dev/lab05/index.html
+++ b/workshops/agile_integrations_dev/lab05/index.html
@@ -323,7 +323,7 @@ <h2 id="fuse-online">Fuse Online</h2>
 <li>Duration: 20 mins</li>
 <li>Audience: Developers and Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-03.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-03.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>When it comes to quick API development, you need both the integration experts as well as application developers to easily develop, deploy the APIs. Here is how to create a simple API with Fuse online.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -342,19 +342,19 @@ <h3 id="step-1-create-database-connection">Step 1: Create database connection</h
 </li>
 <li>
 <p>The first time that you hit the Fuse Online URL, you will be presented with an <em>Authorize Access</em> page.  Click the <strong>Allow selected permissions</strong> button to accept the defaults.</p>
-<p><br>&lt;img src=&rdquo;../images/design-54.png &ldquo;Accept permissions&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/design-54.png &ldquo;Accept permissions&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on <strong>Connections &gt; Create Connection</strong></p>
-<p><br>&lt;img src=&rdquo;../images/00-create-connection.png &ldquo;Create Connection&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-create-connection.png &ldquo;Create Connection&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Database</strong></p>
-<p><br>&lt;img src=&rdquo;../images/01-select-database.png &ldquo;Select Database&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/01-select-database.png &ldquo;Select Database&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Enter below values for Database Configuration</p>
-<pre><code>Connection URL: jdbc:postgresql://postgresql.OCPPROJECT.svc:5432/sampledb
+<pre tabindex="0"><code>Connection URL: jdbc:postgresql://postgresql.OCPPROJECT.svc:5432/sampledb
 Username      : dbuser
 Password      : password
 Schema        : &lt;blank&gt;
@@ -364,7 +364,7 @@ <h3 id="step-1-create-database-connection">Step 1: Create database connection</h
 <ol>
 <li>
 <p>Click <strong>Validate</strong> and verify if the connection is successful. Click <strong>Next</strong> to proceed.</p>
-<p><br>&lt;img src=&rdquo;../images/02-click-validate.png &ldquo;Validate&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/02-click-validate.png &ldquo;Validate&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Add Connection details:</p>
@@ -379,7 +379,7 @@ <h3 id="step-1-create-database-connection">Step 1: Create database connection</h
 </li>
 <li>
 <p>Click <strong>Create</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/03-connection-details.png &ldquo;Add Connection Details&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/03-connection-details.png &ldquo;Add Connection Details&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -390,19 +390,19 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 <ol>
 <li>
 <p>Click on <strong>Integrations &gt; Create Integration</strong></p>
-<p><br>&lt;img src=&rdquo;../images/04-create-integration.png &ldquo;Create Integration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/04-create-integration.png &ldquo;Create Integration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Choose <strong>Webhook</strong></p>
-<p><br>&lt;img src=&rdquo;../images/05-choose-weebhook.png &ldquo;Choose webhook&quot;Integration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/05-choose-weebhook.png &ldquo;Choose webhook&quot;Integration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click on Incoming webhook</p>
-<p><br>&lt;img src=&rdquo;../images/06-incoming-webhook.png &ldquo;Add incoming webhook&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/06-incoming-webhook.png &ldquo;Add incoming webhook&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>It navigates to the Webhook Token screen. Click <strong>Next</strong></p>
-<p><br>&lt;img src=&rdquo;../images/07-webhook-configuration.png &ldquo;Webhook Configuration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/07-webhook-configuration.png &ldquo;Webhook Configuration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Define the Output Data Type.</p>
@@ -420,27 +420,27 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 </li>
 <li>
 <p>Click Done</p>
-<pre><code>{
-  &quot;id&quot;: 1,
-  &quot;name&quot;: &quot;Kamarhati&quot;,
-  &quot;type&quot;: &quot;Regional Branch&quot;,
-  &quot;status&quot;: &quot;1&quot;,
-  &quot;location&quot;: {
-    &quot;lat&quot;: &quot;-28.32555&quot;,
-    &quot;lng&quot;: &quot;-5.91531&quot;
+<pre tabindex="0"><code>{
+  &#34;id&#34;: 1,
+  &#34;name&#34;: &#34;Kamarhati&#34;,
+  &#34;type&#34;: &#34;Regional Branch&#34;,
+  &#34;status&#34;: &#34;1&#34;,
+  &#34;location&#34;: {
+    &#34;lat&#34;: &#34;-28.32555&#34;,
+    &#34;lng&#34;: &#34;-5.91531&#34;
   }
 }
-</code></pre><p><br> <br> &lt;img src=&rdquo;../images/08-data-type.png &ldquo;Data Type&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+</code></pre><p><br> <br> &lt;img src=&quot;../images/08-data-type.png &ldquo;Data Type&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
 <li>
 <p>Click on LocationDB from the catalog and then select Invoke SQL</p>
-<p><br>&lt;img src=&rdquo;../images/09-invoke-sql.png &ldquo;Invoke SQL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/09-invoke-sql.png &ldquo;Invoke SQL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Enter the SQL statement and click <strong>Done</strong>.</p>
-<pre><code></code></pre></li>
+<pre tabindex="0"><code></code></pre></li>
 </ol>
 <p>INSERT INTO locations (id,name,lat,lng,location_type,status) VALUES (:#id,:#name,:#lat,:#lng,:#location_type,:#status )
 ```</p>
@@ -449,11 +449,11 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 <ol>
 <li>
 <p>Click on Add step and select Data mapper</p>
-<p><br>&lt;img src=&rdquo;../images/11-data-mapper.png &ldquo;Data Mapper&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/11-data-mapper.png &ldquo;Data Mapper&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Drag and drop the matching <strong>Source</strong> Data types to all their corresponding <strong>Targets</strong> as per the following screenshot. When finished, click <strong>Done</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/12-configure-mapper.png &ldquo;Configure Mapper&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/12-configure-mapper.png &ldquo;Configure Mapper&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Click <strong>Publish</strong> on the next screen</p>
@@ -463,7 +463,7 @@ <h3 id="step-2-create-webhook-integration">Step 2: Create webhook integration</h
 </li>
 <li>
 <p>Again Click <strong>Publish</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/13-publish-integration.png &ldquo;Publish Integration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/13-publish-integration.png &ldquo;Publish Integration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations</em>. You successfully published the integration. (Wait for few minutes to for the integration to be built and published)</p>
@@ -472,7 +472,7 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <ol>
 <li>
 <p>Copy the External URL per the below screenshot</p>
-<p><br>&lt;img src=&rdquo;../images/14-copy-URL.png &ldquo;Copy URL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/14-copy-URL.png &ldquo;Copy URL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Open a browser window and navigate to: <a href="https://onlinecurl.com/">https://onlinecurl.com/</a></p>
@@ -516,7 +516,7 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <li>&ndash;data (-d): {&ldquo;id&rdquo;: 101, &ldquo;name&rdquo;: &ldquo;Kamarhati&rdquo;, &ldquo;type&rdquo;: &ldquo;Regional Branch&rdquo;, &ldquo;status&rdquo;: &ldquo;1&rdquo;, &ldquo;location&rdquo;: { &ldquo;lat&rdquo;: &ldquo;-28.32555&rdquo;, &ldquo;lng&rdquo;: &ldquo;-5.91531&rdquo; }}</li>
 <li>&ndash;request (-X): POST</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/15-online-curl.png &ldquo;Online URL&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/15-online-curl.png &ldquo;Online URL&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -525,7 +525,7 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <ul>
 <li>
 <p>If you get an SSL error, please see the next step.</p>
-<p><br>&lt;img src=&rdquo;../images/16-response-header.png &ldquo;Response Header&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/16-response-header.png &ldquo;Response Header&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -534,31 +534,31 @@ <h3 id="step-3-create-a-post-request">Step 3: Create a POST request</h3>
 <ul>
 <li>
 <p>Please make sure to use the your URL you copied and pasted</p>
-<pre><code>curl -k \
---header &quot;Content-Type: application/json&quot; \
+<pre tabindex="0"><code>curl -k \
+--header &#34;Content-Type: application/json&#34; \
 --request POST \
---data '{&quot;id&quot;: 101, &quot;name&quot;: &quot;Kamarhati&quot;, &quot;type&quot;: &quot;Regional Branch&quot;, &quot;status&quot;: &quot;1&quot;, &quot;location&quot;: { &quot;lat&quot;: &quot;-28.32555&quot;, &quot;lng&quot;: &quot;-5.91531&quot; }}' \
+--data &#39;{&#34;id&#34;: 101, &#34;name&#34;: &#34;Kamarhati&#34;, &#34;type&#34;: &#34;Regional Branch&#34;, &#34;status&#34;: &#34;1&#34;, &#34;location&#34;: { &#34;lat&#34;: &#34;-28.32555&#34;, &#34;lng&#34;: &#34;-5.91531&#34; }}&#39; \
 https://i-addlocation-tools1.apps.ocp-ai.redhatgov.io/webhook/KcZ3E86SUJTqIUsA8iB7Yb5Sa1KLp9cchnRO5twYnr6UTruYd1
 </code></pre></li>
 </ul>
 <ol>
 <li>
 <p>Click on <strong>Activity &gt; Refresh</strong> and verify if the newly record is created.</p>
-<p><br>&lt;img src=&rdquo;../images/17-activity-refresh.png &ldquo;Activity Refresh&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/17-activity-refresh.png &ldquo;Activity Refresh&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p><em>(Optional)</em> Visit the application URL in the browser from the Location Service created in the previous lab and verify if the record can be fetched.</p>
 </li>
 </ol>
 <p><strong>RESPONSE</strong></p>
-<pre><code>  {
-    &quot;id&quot; : 101,
-    &quot;name&quot; : &quot;Kamarhati&quot;,
-    &quot;type&quot; : &quot;Regional Branch&quot;,
-    &quot;status&quot; : &quot;1&quot;,
-    &quot;location&quot; : {
-      &quot;lat&quot; : &quot;-28.32555&quot;,
-      &quot;lng&quot; : &quot;-5.91531&quot;
+<pre tabindex="0"><code>  {
+    &#34;id&#34; : 101,
+    &#34;name&#34; : &#34;Kamarhati&#34;,
+    &#34;type&#34; : &#34;Regional Branch&#34;,
+    &#34;status&#34; : &#34;1&#34;,
+    &#34;location&#34; : {
+      &#34;lat&#34; : &#34;-28.32555&#34;,
+      &#34;lng&#34; : &#34;-5.91531&#34;
     }
   }
 </code></pre><h2 id="summary">Summary</h2>
@@ -612,7 +612,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab06/index.html b/workshops/agile_integrations_dev/lab06/index.html
index 3a0fb5f8e..2e2e5050f 100644
--- a/workshops/agile_integrations_dev/lab06/index.html
+++ b/workshops/agile_integrations_dev/lab06/index.html
@@ -324,7 +324,7 @@ <h3 id="take-control-of-your-apis">Take control of your APIs</h3>
 <li>Duration: 5 mins</li>
 <li>Audience: API Owners, Product Managers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-04.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-04.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>Once you have APIs deployed in your environment, it becomes critically important to manage who may use them and for what purpose. You also need to begin to track usage of these different users to know who is/is not succeeding in their usage. For this reason in this lab you will be adding management capabilities to the API to give you control and visibility of it&rsquo;s usage.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -382,10 +382,10 @@ <h3 id="step-2-start-managing-your-apis">Step 2: Start managing your APIs</h3>
 <li>Replace USERX as your user id, such as user1, OPENSHIFT_URL, YOUR_API_TOKEN you copied earlier.</li>
 <li>If you are not sure, check with your instructor</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">curl -X POST http://threescale-automate-international.apps.<span style="color:#f92672">{</span>OPENSHIFT_URL<span style="color:#f92672">}</span>/threescale/automate/<span style="color:#f92672">{</span>YOUR_API_TOKEN<span style="color:#f92672">}</span>/<span style="color:#f92672">{</span>USERX<span style="color:#f92672">}</span>/apps.<span style="color:#f92672">{</span>OPENSHIFT_URL<span style="color:#f92672">}</span>
-</code></pre></div><p>For example:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">curl -X POST http://threescale-automate-international.apps.ocp-ai.redhatgov.io/threescale/automate/5077c20822f2e284aaa48d9b2115551cc9605cb9617eb2479815a4209fea20d9/user1/apps.ocp-ai.redhatgov.io
-</code></pre></div><p><strong>API automated, DONE!</strong> should be returned as the result.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>curl -X POST http://threescale-automate-international.apps.<span style="color:#f92672">{</span>OPENSHIFT_URL<span style="color:#f92672">}</span>/threescale/automate/<span style="color:#f92672">{</span>YOUR_API_TOKEN<span style="color:#f92672">}</span>/<span style="color:#f92672">{</span>USERX<span style="color:#f92672">}</span>/apps.<span style="color:#f92672">{</span>OPENSHIFT_URL<span style="color:#f92672">}</span>
+</span></span></code></pre></div><p>For example:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>curl -X POST http://threescale-automate-international.apps.ocp-ai.redhatgov.io/threescale/automate/5077c20822f2e284aaa48d9b2115551cc9605cb9617eb2479815a4209fea20d9/user1/apps.ocp-ai.redhatgov.io
+</span></span></code></pre></div><p><strong>API automated, DONE!</strong> should be returned as the result.</p>
 <p><strong>Save the Result as you will need it for the next lab</strong></p>
 <p>If the command was not Successful for you:</p>
 <ul>
@@ -450,7 +450,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab07/index.html b/workshops/agile_integrations_dev/lab07/index.html
index a00b94d20..b8da57700 100644
--- a/workshops/agile_integrations_dev/lab07/index.html
+++ b/workshops/agile_integrations_dev/lab07/index.html
@@ -324,7 +324,7 @@ <h3 id="publishing-apis-to-developer-portal">Publishing APIs to Developer Portal
 <li>Duration: 20 mins</li>
 <li>Audience: API Owners, Product Managers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-04.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-04.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h2 id="overview">Overview</h2>
 <p>The focal point of your developers’ experience is the API developer portal, and the level of effort you put into it will determine the level of decreased support costs and increased developer engagement.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -437,8 +437,8 @@ <h3 id="step-3-login-to-developer-portal">Step 3: Login to Developer Portal</h3>
 </li>
 <li>
 <p>Open a new <em>Incognito/Private</em> browser window to test the Developer Portal login. Navigate to the following.  Make sure your user and Openshift environment is correct.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"> http://<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>
-</code></pre></div></li>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span> http://<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>
+</span></span></code></pre></div></li>
 <li>
 <p>Type your portal code to finish the login.</p>
 <p><br><img src="../images/16e-ingress-code.png" width="900" /><br><br></p>
@@ -449,7 +449,7 @@ <h3 id="step-3-login-to-developer-portal">Step 3: Login to Developer Portal</h3>
 </li>
 <li>
 <p>You will land in the developers homepage, where you will be able to check your developers settings and retrieve your newly created <strong>Client ID</strong> and <strong>Client Secret</strong> for the <strong>Workshop App</strong> you created.</p>
-<p><br>&lt;img src=&rdquo;../images/16g-user-credentials.png&rdquo; &ldquo;Application Credentials&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/16g-user-credentials.png&quot; &ldquo;Application Credentials&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Copy down this credentials as it you will use them to authenticate yourself to the managed API</em> in the next lab.</p>
@@ -513,7 +513,7 @@ <h3 id="links">Links</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/lab08/index.html b/workshops/agile_integrations_dev/lab08/index.html
index d4039fd6b..5d03a0bb0 100644
--- a/workshops/agile_integrations_dev/lab08/index.html
+++ b/workshops/agile_integrations_dev/lab08/index.html
@@ -320,7 +320,7 @@ <h3 id="connect-applications-and-apis">Connect Applications and APIs</h3>
 <li>Duration: 15 mins</li>
 <li>Audience: API Consumers, Developers, Architects</li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/agenda-05.png &ldquo;Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/agenda-05.png &ldquo;Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <h3 id="overview">Overview</h3>
 <p>APIs provide the building blocks for applications, but it is applications which deliver functionality to the end users. hence to see APIs in action it helps to see how applications can call APIs to provide new functionality. In this lab you&rsquo;ll be able to create a simple web application which consumes the API you built earlier in the exercises.</p>
 <h3 id="why-red-hat">Why Red Hat?</h3>
@@ -334,7 +334,7 @@ <h3 id="update-openshift-deployment">Update OpenShift Deployment</h3>
 </li>
 <li>
 <p>Scroll down and click in the www link in the BUILDS section.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-10.png&rdquo; &ldquo;Scroll Down&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-10.png&quot; &ldquo;Scroll Down&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the build environment variables page, replace the <code>CLIENT_ID</code> from <code>CHANGE_ME</code> to the one generated from the previous lab.</p>
@@ -343,7 +343,7 @@ <h3 id="update-openshift-deployment">Update OpenShift Deployment</h3>
 <ul>
 <li>
 <p>Also, make note of the API_BACKEND_URL.  That is the 3Scale backend address of your API.  If the 3Scale Environment is configured with self-signed certificates, go ahead and bring up that link in a Browser and have your Browser accept the certificate for later on. 3Scale should give you an authentication error since it&rsquo;s not configured yet.  The important thing is to just accept the certificate.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-11.png&rdquo; &ldquo;Change Client ID&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-11.png&quot; &ldquo;Change Client ID&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ul>
 <ol>
@@ -352,18 +352,18 @@ <h3 id="update-openshift-deployment">Update OpenShift Deployment</h3>
 </li>
 <li>
 <p>Click the Start Build button to trigger a new build using the new environment variables pointing to your service.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-12.png &ldquo;Start Build&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-12.png &ldquo;Start Build&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>In the Overview Page, a new build will be triggered. Expand the row by clicking the Builds Icon.</p>
-<p><br>&lt;img src=&rdquo;../images/deploy-13.png &ldquo;View Build&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/deploy-13.png &ldquo;View Build&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>The build process checks out the code from the git repo, runs a source-to-image container image build, and redeploys the container with the new image using a rolling upgrade strategy.</em></p>
 <ol>
 <li>
 <p>Wait for until the new Build to complete and the rolling upgrade to finish to test your new deployment.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-22.png &ldquo;Updated App&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-22.png &ldquo;Updated App&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <h3 id="update-secured-service-with-red-hat-single-sign-on-application-callback">Update Secured Service with Red Hat Single Sign On Application Callback</h3>
@@ -371,22 +371,22 @@ <h3 id="update-secured-service-with-red-hat-single-sign-on-application-callback"
 <ol>
 <li>
 <p>Open a browser window and navigate to your SSO Console.  Please check with your instructor for the link.  It should be similar to the following.  Replace userX with your assigned user and OCP_URL.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">http://sso-sso.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>/auth/admin/<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>/console/
-</code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>http://sso-sso.apps.<span style="color:#f92672">[</span>OCP_URL<span style="color:#f92672">]</span>/auth/admin/<span style="color:#f92672">[</span>userX<span style="color:#f92672">]</span>/console/
+</span></span></code></pre></div><p><em>Remember to replace the X with your user number.</em></p>
 </li>
 <li>
 <p>Log into Red Hat Single Sign On using your designated user and password. Click on <strong>Sign In</strong>.</p>
-<p><br>&lt;img src=&rdquo;../images/00-login-sso.png &ldquo;RH SSO Login&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-login-sso.png &ldquo;RH SSO Login&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Select <strong>Clients</strong> from the left menu.</p>
-<p><br>&lt;img src=&rdquo;../images/00-clients.png &ldquo;Clients&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/00-clients.png &ldquo;Clients&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 <p><em>3scale, through it&rsquo;s <a href="https://github.com/3scale/zync/">zync</a> component, already synchronized the application information into the Red Hat SSO security realm</em>.</p>
 </li>
 <li>
 <p>Click on the <strong>CLIENT_ID</strong> link to view the details.</p>
 <p><em>Remember to select correct CLIENT_ID with the one you got in the <a href="../lab07">API Security Lab</a>. It will easily identifiable as its and hexadecimal name</em>.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-24.png &ldquo;Client Application&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-24.png &ldquo;Client Application&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Scroll down, type in and select the following options in the application configuration below.  Please make sure to use the Redirect URI for your user.</p>
@@ -421,7 +421,7 @@ <h3 id="update-secured-service-with-red-hat-single-sign-on-application-callback"
 </tbody>
 </table>
 <p><em>Remember to replace the X with your user number.</em></p>
-<p><br>&lt;img src=&rdquo;../images/consume-25.png &ldquo;Client Configuration&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-25.png &ldquo;Client Configuration&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>Finally, click <strong>Save</strong> button to persist the changes.</p>
@@ -448,11 +448,11 @@ <h3 id="test-the-single-sign-on-integration">Test the Single Sign On Integration
 <li>Username: <strong>userX</strong></li>
 <li>Password: <strong>password you received from instructor</strong></li>
 </ul>
-<p><br>&lt;img src=&rdquo;../images/consume-23.png &ldquo;Login Realm&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-23.png &ldquo;Login Realm&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 <li>
 <p>You will be redirected again to the <strong>LOCATIONS</strong> page where now you will be able to see the map with the International Inc Offices.</p>
-<p><br>&lt;img src=&rdquo;../images/consume-14.png &ldquo;Locations Page&rdquo; width=&quot;900&rdquo; /&gt;<br><br></p>
+<p><br>&lt;img src=&quot;../images/consume-14.png &ldquo;Locations Page&rdquo; width=&ldquo;900&rdquo; /&gt;<br><br></p>
 </li>
 </ol>
 <p><em>Congratulations!</em> You have successfully used the Keycloak Javascript Adapter to protect International Inc&rsquo;s Locations Service with Single Sign On.  If you have any issues, please see the next session.</p>
@@ -532,7 +532,7 @@ <h2 id="notes-and-further-reading">Notes and Further Reading</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/openshift/index.html b/workshops/agile_integrations_dev/openshift/index.html
index 2bb17b6fa..fe4d56ac2 100644
--- a/workshops/agile_integrations_dev/openshift/index.html
+++ b/workshops/agile_integrations_dev/openshift/index.html
@@ -344,15 +344,15 @@ <h2 id="lets-login-to-the-web-console">Let&rsquo;s Login to the Web Console</h2>
 <p>Once logged in you should see your available projects - or a button to create a project if none exist already.</p>
 <h2 id="lets-try-the-oc-command-line-cli-tool">Let&rsquo;s try the &lsquo;oc&rsquo; command line (CLI) tool</h2>
 <p>Open a terminal and login using the same URI with following command:</p>
-<pre><code>$ oc login https://ocp-ai.redhatgov.io/ --insecure-skip-tls-verify=true
-Authentication required for https://ocp-naps.redhatgov.io/ &quot;master&quot; &quot;:8443&quot; &gt;}} (openshift)
+<pre tabindex="0"><code>$ oc login https://ocp-ai.redhatgov.io/ --insecure-skip-tls-verify=true
+Authentication required for https://ocp-naps.redhatgov.io/ &#34;master&#34; &#34;:8443&#34; &gt;}} (openshift)
  Username: user#
  Password:
 Login successful.
 </code></pre><p>Check to see what projects you have access to:</p>
-<pre><code>$ oc get projects
+<pre tabindex="0"><code>$ oc get projects
 </code></pre><p>Type the following command to show services, deployment configs, build configurations, and active deployments (this will come in handy later):</p>
-<pre><code>$ oc status
+<pre tabindex="0"><code>$ oc status
 </code></pre><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.</p>
 
@@ -394,7 +394,7 @@ <h2 id="lets-try-the-oc-command-line-cli-tool">Let&rsquo;s try the &lsquo;oc&rsq
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/agile_integrations_dev/prerequisites/index.html b/workshops/agile_integrations_dev/prerequisites/index.html
index 6a302c248..b4306cbd9 100644
--- a/workshops/agile_integrations_dev/prerequisites/index.html
+++ b/workshops/agile_integrations_dev/prerequisites/index.html
@@ -356,7 +356,7 @@ <h1 id="prerequisites">Prerequisites</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/index.html
index b55d96a2f..a5f0978ae 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/index.html
@@ -329,19 +329,19 @@ <h3 id="_managing_remote_hosts">Managing remote hosts</h3>
 <p>First, in order to manage remote systems - we need to set up our dependencies:</p>
 </div>
 <div class="paragraph">
-<p>Define your inventory.  Inventories are crucial to Ansible, as they define remote machines on which you will run commands or your playbook(s).  Use the Code Ready Workspaces editor (Eclipse Che) to create a file called <code>hosts</code> by selecting [File] &#8594; [New File] &#8594; hosts (no .txt extention) file in /projects; then, click [Ok]</p>
+<p>Define your inventory.  Inventories are crucial to Ansible, as they define remote machines on which you will run commands or your playbook(s).  Use the Code Ready Workspaces editor (Eclipse Che) to create a file called <code>hosts</code> by selecting [File] → [New File] → hosts (no .txt extention) file in /projects; then, click [Ok]</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_hosts.gif" alt="ansible hosts" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_hosts.gif" alt="ansible hosts" height="500"/>
 </div>
-<div class="title">Figure 1: Creating the Ansible inventory file called "hosts"</div>
+<div class="title">Figure 1: Creating the Ansible inventory file called &#34;hosts&#34;</div>
 </div>
 <div class="exampleblock">
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -349,7 +349,7 @@ <h3 id="_managing_remote_hosts">Managing remote hosts</h3>
 The <strong>workshopname</strong>, in the example below, will be provided to you by your instructor.  The <strong>#</strong> should be replaced by your student number.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>For example, a recent workshop student used:
@@ -367,19 +367,19 @@ <h3 id="_managing_remote_hosts">Managing remote hosts</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>When complete, select "[File] &#8594; [Save]" to write out the content.</p>
+<p>When complete, select &#34;[File] → [Save]&#34; to write out the content.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_hosts_save.gif" alt="ansible hosts save" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_hosts_save.gif" alt="ansible hosts save" height="500"/>
 </div>
-<div class="title">Figure 2: Saving the Ansible inventory file called "hosts"</div>
+<div class="title">Figure 2: Saving the Ansible inventory file called &#34;hosts&#34;</div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_1_test_the_edge_host_response">Step 1: Test the edge host response</h3>
 <div class="paragraph">
-<p>Let&#8217;s start with something basic - pinging a host.  The <code>ping</code> module tests the responsiveness of our edge host from the Code Ready Workspaces Terminal.</p>
+<p>Let’s start with something basic - pinging a host.  The <code>ping</code> module tests the responsiveness of our edge host from the Code Ready Workspaces Terminal.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -390,18 +390,18 @@ <h3 id="_step_1_test_the_edge_host_response">Step 1: Test the edge host response
 <div class="sect2">
 <h3 id="_step_2_run_a_linux_command">Step 2: Run a Linux command</h3>
 <div class="paragraph">
-<p>Now let&#8217;s see how we can run a Linux command and format the output, using the <code>command</code> module.</p>
+<p>Now let’s see how we can run a Linux command and format the output, using the <code>command</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge --module-name command --args "uname -m" --one-line</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge --module-name command --args &#34;uname -m&#34; --one-line</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="paragraph">
-<p>Take a look at your edge node&#8217;s configuration.  The <code>setup</code> module displays Ansible facts (and a lot of them) about an endpoint.</p>
+<p>Take a look at your edge node’s configuration.  The <code>setup</code> module displays Ansible facts (and a lot of them) about an endpoint.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -412,7 +412,7 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -420,11 +420,11 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 Like many Linux commands, <strong>ansible</strong> allows for long-form and short-form command-line arguments.  For example:
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge --module-name command --args "uname -m" --one-line --become</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge --module-name command --args &#34;uname -m&#34; --one-line --become</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -432,7 +432,7 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge -m command -a "uname -m" -o -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge -m command -a &#34;uname -m&#34; -o -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -444,14 +444,14 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="sect2">
 <h3 id="_step_4_install_a_package_on_the_edge">Step 4:  Install a package on the edge.</h3>
 <div class="paragraph">
-<p>For this example, we will use the 'skopeo' package; which, provides a way inspect, copy, and sync (plus more) containers repositories.</p>
+<p>For this example, we will use the &#39;skopeo&#39; package; which, provides a way inspect, copy, and sync (plus more) containers repositories.</p>
 </div>
 <div class="paragraph">
-<p>Now, let&#8217;s install 'skopeo', using the Ansible <code>package</code> module.</p>
+<p>Now, let’s install &#39;skopeo&#39;, using the Ansible <code>package</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge -m package -a "name=skopeo state=present" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible edge -m package -a &#34;name=skopeo state=present&#34; -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -554,7 +554,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -814,7 +814,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -926,7 +926,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -936,7 +936,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1023,7 +1023,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/index.html
index 64296729a..2f8ce4ed7 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/index.html
@@ -347,7 +347,7 @@ <h3 id="_step_1_checking_a_playbook_playbook_for_correct_syntax">Step 1: Checkin
 <div class="ulist NOTE">
 <ul class="NOTE">
 <li>
-<p><strong>--syntax-check</strong> If you run into any issues with your playbook running properly (from the copy/pasting that we told you not to do), you could use this option to help find those issues like so&#8230;&#8203;</p>
+<p><strong>--syntax-check</strong> If you run into any issues with your playbook running properly (from the copy/pasting that we told you not to do), you could use this option to help find those issues like so…​</p>
 </li>
 </ul>
 </div>
@@ -361,17 +361,17 @@ <h3 id="_step_1_checking_a_playbook_playbook_for_correct_syntax">Step 1: Checkin
 </div>
 </div>
 <div class="paragraph">
-<p>Now, let&#8217;s look at the playbook by selecting it from the file list on the left.</p>
+<p>Now, let’s look at the playbook by selecting it from the file list on the left.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/pcp_setup_code_review.png" alt="pcp setup code review">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/pcp_setup_code_review.png" alt="pcp setup code review"/>
 </div>
 <div class="title"></div>
 </div>
-<hr>
+<hr/>
 <div class="paragraph">
-<p>Based on the above, let&#8217;s run the playbook</p>
+<p>Based on the above, let’s run the playbook</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -478,7 +478,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -738,7 +738,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -850,7 +850,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -860,7 +860,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -947,7 +947,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/index.html
index 2907608b3..f37fabaae 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/index.html
@@ -329,7 +329,7 @@ <h2 id="_objective">Objective</h2>
 <div class="ulist">
 <ul>
 <li>
-<p>Ansible modules and supporting parameters (example: '<strong>package</strong>' and '<strong>service</strong>' modules)</p>
+<p>Ansible modules and supporting parameters (example: &#39;<strong>package</strong>&#39; and &#39;<strong>service</strong>&#39; modules)</p>
 </li>
 <li>
 <p>How to use loops to make your ansible more efficient and smaller</p>
@@ -359,13 +359,13 @@ <h3 id="_create_a_directory_file">Create a directory &amp; file</h3>
 <p>Create a directory called <strong>install_podman</strong> in your projects directory and create a file call init-edge.yml:</p>
 </div>
 <div class="paragraph">
-<p>[<strong>File</strong>] &#8594; [<strong>New Folder</strong>] &#8594; Enter "<strong>install_podman</strong>" &#8594; Select [<strong>Ok</strong>] &#8594; right click on the "<strong>install_podman</strong>" folder &#8594; select [<strong>New File</strong>] &#8594; Enter "<strong>init-edge.yml</strong>"</p>
+<p>[<strong>File</strong>] → [<strong>New Folder</strong>] → Enter &#34;<strong>install_podman</strong>&#34; → Select [<strong>Ok</strong>] → right click on the &#34;<strong>install_podman</strong>&#34; folder → select [<strong>New File</strong>] → Enter &#34;<strong>init-edge.yml</strong>&#34;</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/install_podman.gif" alt="install podman" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/install_podman.gif" alt="install podman" height="500"/>
 </div>
-<div class="title">Create "init-edge.yml" file in the /projects/install_podman/ directory</div>
+<div class="title">Create &#34;init-edge.yml&#34; file in the /projects/install_podman/ directory</div>
 </div>
 </div>
 </div>
@@ -374,7 +374,7 @@ <h3 id="_create_a_directory_file">Create a directory &amp; file</h3>
 <h2 id="_section_2_defining_your_play">Section 2: Defining Your play</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you are editing <code>init-edge.yml</code>, let&#8217;s begin by defining the play. Then, we&#8217;ll take some time to understand what each line accomplishes.</p>
+<p>Now that you are editing <code>init-edge.yml</code>, let’s begin by defining the play. Then, we’ll take some time to understand what each line accomplishes.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -406,10 +406,10 @@ <h2 id="_section_2_defining_your_play">Section 2: Defining Your play</h2>
 <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding tasks to your play</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that we&#8217;ve defined your play, let&#8217;s add some tasks to get some things done.  Align (vertically) the <strong>t</strong> in <code>task</code> with the <strong>b</strong> <code>become</code>. <br></p>
+<p>Now that we’ve defined your play, let’s add some tasks to get some things done.  Align (vertically) the <strong>t</strong> in <code>task</code> with the <strong>b</strong> <code>become</code>. <br/></p>
 </div>
 <div class="paragraph">
-<p>Yes, it does actually matter.  In fact, you should make sure all of your playbook statements are aligned, as shown here.<br></p>
+<p>Yes, it does actually matter.  In fact, you should make sure all of your playbook statements are aligned, as shown here.<br/></p>
 </div>
 <div class="paragraph">
 <p>If you want to see the entire playbook for reference, skip to the bottom of this exercise.</p>
@@ -419,7 +419,7 @@ <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding tasks to your pl
 <pre class="highlight"><code class="language-bash" data-lang="bash">  tasks:
   - name: Install podman &amp; cockpit
     package:
-      name: "{{ item }}"
+      name: &#34;{{ item }}&#34;
       state: latest
     loop:
       - podman
@@ -449,7 +449,7 @@ <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding tasks to your pl
 <div class="content">
 <pre class="highlight"><code class="language-text" data-lang="text">  - name: Enable Podman API &amp; cockpit
     service:
-      name: "{{ item }}"
+      name: &#34;{{ item }}&#34;
       state: started
       enabled: yes
     loop:
@@ -472,13 +472,13 @@ <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding tasks to your pl
 <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve completed writing your playbook, it would be a shame not to keep it for later use by selecting [<strong>File</strong>] &#8594; [<strong>Save</strong>]</p>
+<p>Now that you’ve completed writing your playbook, it would be a shame not to keep it for later use by selecting [<strong>File</strong>] → [<strong>Save</strong>]</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/install_podman_save.gif" alt="install podman save" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/install_podman_save.gif" alt="install podman save" height="500"/>
 </div>
-<div class="title">Figure 2: Save "init-edge.yml" file in the /projects/install_podman/ directory</div>
+<div class="title">Figure 2: Save &#34;init-edge.yml&#34; file in the /projects/install_podman/ directory</div>
 </div>
 <div class="paragraph">
 <p>And that should do it.  You should now have a fully written playbook called <code>init-edge.yml</code>.
@@ -486,7 +486,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -496,7 +496,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
 like this.  Take note of the spacing and alignment.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -507,7 +507,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
   tasks:
   - name: Install podman &amp; cockpit
     package:
-      name: "{{ item }}"
+      name: &#34;{{ item }}&#34;
       state: latest
     loop:
       - podman
@@ -515,7 +515,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
       - cockpit-podman
   - name: Enable Podman API &amp; cockpit
     service:
-      name: "{{ item }}"
+      name: &#34;{{ item }}&#34;
       state: started
       enabled: yes
     loop:
@@ -542,7 +542,7 @@ <h2 id="_running_the_ansible_playbook">Running the Ansible playbook</h2>
 <pre>ansible-playbook init-edge.yml</pre>
 </div>
 </div>
-<hr>
+<hr/>
 <div class="paragraph">
 <style>
 
@@ -643,7 +643,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -903,7 +903,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1015,7 +1015,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1025,7 +1025,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1111,7 +1111,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/index.html
index 3d768a38d..a44dbb363 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/index.html
@@ -321,12 +321,12 @@ <h1>Exercise 2.0 - Build a CI/CD pipeline and container in Red Hat OpenShift</h1
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>As part of the Applied Ansible workshop, you will deploy <em>(copy/transfer)</em> a container built on top of Red Hat OpenShift to an edge node running only Red Hat Enterprise Linux utilizing Ansible Automation.  Prior to that step, we need to actually "create" a container on Red Hat OpenShift.</p>
+<p>As part of the Applied Ansible workshop, you will deploy <em>(copy/transfer)</em> a container built on top of Red Hat OpenShift to an edge node running only Red Hat Enterprise Linux utilizing Ansible Automation.  Prior to that step, we need to actually &#34;create&#34; a container on Red Hat OpenShift.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2>
+<h2 id="_lets_login_to_the_web_console">Let’s Login to the Web Console</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>In your browser &amp; in a new tab, connect to the Red Hat OpenShift console</p>
@@ -338,7 +338,7 @@ <h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_login.png" alt="rhocp login" height="400">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_login.png" alt="rhocp login" height="400"/>
 </div>
 <div class="title"></div>
 </div>
@@ -347,7 +347,7 @@ <h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_edge_namespace.gif" alt="rhocp edge namespace" height="200">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_edge_namespace.gif" alt="rhocp edge namespace" height="200"/>
 </div>
 <div class="title"></div>
 </div>
@@ -356,7 +356,7 @@ <h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_git.png" alt="s2i git" height="200">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_git.png" alt="s2i git" height="200"/>
 </div>
 <div class="title"></div>
 </div>
@@ -367,8 +367,8 @@ <h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2
 <h3 id="_build_a_oci_aka_docker_container_from_only_source_code_via_source_to_image_s2i">Build a OCI (aka docker) container from only source code via source-to-image (s2i).</h3>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -389,11 +389,11 @@ <h3 id="_build_a_oci_aka_docker_container_from_only_source_code_via_source_to_im
 <div class="sect2">
 <h3 id="_select_language_php">Select language (PHP)</h3>
 <div class="paragraph">
-<p><em>and of course, yes &#8230;&#8203; we could have used many other languages &#8230;&#8203;</em></p>
+<p><em>and of course, yes …​ we could have used many other languages …​</em></p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_php.png" alt="s2i php" height="100">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_php.png" alt="s2i php" height="100"/>
 </div>
 <div class="title"></div>
 </div>
@@ -408,8 +408,8 @@ <h3 id="_resources">Resources</h3>
 <h3 id="_resources_2">Resources</h3>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -434,9 +434,9 @@ <h3 id="_pipelines">Pipelines</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipeline.png" alt="s2i pipeline" height="100">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipeline.png" alt="s2i pipeline" height="100"/>
 </div>
-<div class="title">Select > Show pipeline visualization</div>
+<div class="title">Select &gt; Show pipeline visualization</div>
 </div>
 </div>
 <div class="sect2">
@@ -446,10 +446,10 @@ <h3 id="_advanced_options">Advanced options</h3>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_lastly_select">Lastly, select &#8230;&#8203;</h3>
+<h3 id="_lastly_select">Lastly, select …​</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_create.png" alt="s2i create" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_create.png" alt="s2i create" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -553,7 +553,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -813,7 +813,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -925,7 +925,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -935,7 +935,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1022,7 +1022,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/index.html
index 7793bb4d0..cfba9507f 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/index.html
@@ -324,13 +324,13 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>View the created pipeline and review the container that Ansible orchestrate deploying to the edge node.</p>
 </div>
 <div class="sect2">
-<h3 id="_lets_review_the_container_build">Let&#8217;s review the container build</h3>
+<h3 id="_lets_review_the_container_build">Let’s review the container build</h3>
 <div class="paragraph">
 <p>Select <strong>Pipelines</strong> in the left menu:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipelines.png" alt="s2i pipelines" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipelines.png" alt="s2i pipelines" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -340,7 +340,7 @@ <h3 id="_lets_review_the_container_build">Let&#8217;s review the container build
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_pipeline.gif" alt="s2i view pipeline" height="350">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_pipeline.gif" alt="s2i view pipeline" height="350"/>
 </div>
 <div class="title"></div>
 </div>
@@ -352,19 +352,19 @@ <h3 id="_wait_until_pipeline_details_are_green">Wait until pipeline details are
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_pipeline_green.png" alt="s2i view pipeline green" height="150">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_pipeline_green.png" alt="s2i view pipeline green" height="150"/>
 </div>
 <div class="title"></div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_view_built_container_images">View built container images &#8230;&#8203;</h3>
+<h3 id="_view_built_container_images">View built container images …​</h3>
 <div class="paragraph">
 <p>Select <strong>Topology</strong> in the left menu</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology.png" alt="s2i view topology" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology.png" alt="s2i view topology" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -373,19 +373,19 @@ <h3 id="_view_built_container_images">View built container images &#8230;&#8203;
 <h3 id="_review_running_container">Review running container</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology_url.png" alt="s2i view topology url" height="150">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology_url.png" alt="s2i view topology url" height="150"/>
 </div>
 <div class="title"></div>
 </div>
 <div class="paragraph">
-<p><strong><em>IMPORTANT</em></strong>: If your deployment does not say "edge" and begins with s2i; then, you missed a step in exercise 2.0 (Resources) where you declared the name.  Please go back and repeat exercise 2.0.</p>
+<p><strong><em>IMPORTANT</em></strong>: If your deployment does not say &#34;edge&#34; and begins with s2i; then, you missed a step in exercise 2.0 (Resources) where you declared the name.  Please go back and repeat exercise 2.0.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_ensure_that_you_see_the_running_container_return_the_output_release_1">Ensure that you see the running container return the output <strong>"Release 1"</strong></h3>
+<h3 id="_ensure_that_you_see_the_running_container_return_the_output_release_1">Ensure that you see the running container return the output <strong>&#34;Release 1&#34;</strong></h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_edge_release.gif" alt="s2i view edge release" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_edge_release.gif" alt="s2i view edge release" height="500"/>
 </div>
 <div class="title">Review running container</div>
 </div>
@@ -489,7 +489,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -749,7 +749,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -861,7 +861,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -871,7 +871,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -958,7 +958,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/index.html
index e9003802d..4828bb284 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/index.html
@@ -327,7 +327,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>As part of the exercise, we have built a playbook for you; however, no all of the variables are assigned.  This allows us to distribute the playbook to multiple workshops and you the capability to understand how to run playbooks in Ansible tower and assign custom variables to those plays.  As part of the exercise, you will create a Template within Ansible tower to run the defined playbook, set the custom variables, and define a <strong>survey</strong> to prompt you to enter the sensitive credential via a prompt.</p>
 </div>
 <div class="paragraph">
-<p>Navigate in your browser to &#8230;&#8203;</p>
+<p>Navigate in your browser to …​</p>
 </div>
 <div class="paragraph">
 <p><code>
@@ -336,19 +336,19 @@ <h2 id="_exercise_description">Exercise Description</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_login.png" alt="tower login" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_login.png" alt="tower login" height="500"/>
 </div>
 <div class="title">Login with your credentials</div>
 </div>
-<hr>
+<hr/>
 <div class="sect2">
-<h3 id="_lets_explore_projects">Let&#8217;s explore &#8230;&#8203; Projects</h3>
+<h3 id="_lets_explore_projects">Let’s explore …​ Projects</h3>
 <div class="paragraph">
 <p>Select <strong>Project</strong></p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_projects_select.png" alt="tower projects select" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_projects_select.png" alt="tower projects select" height="50"/>
 </div>
 <div class="title">Projects tab - Left hand side of screen</div>
 </div>
@@ -360,20 +360,20 @@ <h3 id="_lets_explore_projects">Let&#8217;s explore &#8230;&#8203; Projects</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_projects_info.png" alt="tower projects info" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_projects_info.png" alt="tower projects info" height="500"/>
 </div>
 <div class="title"></div>
 </div>
-<hr>
+<hr/>
 </div>
 <div class="sect2">
-<h3 id="_lets_explore_inventories">Let&#8217;s explore &#8230;&#8203; Inventories</h3>
+<h3 id="_lets_explore_inventories">Let’s explore …​ Inventories</h3>
 <div class="paragraph">
 <p>Select <strong>Inventories</strong></p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_inv_select.png" alt="tower inv select" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_inv_select.png" alt="tower inv select" height="50"/>
 </div>
 <div class="title">Inventories tab - Left hand side of screen</div>
 </div>
@@ -385,23 +385,23 @@ <h3 id="_lets_explore_inventories">Let&#8217;s explore &#8230;&#8203; Inventorie
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_inv_select_host.png" alt="tower inv select host" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_inv_select_host.png" alt="tower inv select host" height="50"/>
 </div>
 <div class="title"></div>
 </div>
 <div class="paragraph">
 <p>If you select <strong>HOSTS</strong>, you will notice that you will continue to utilize the edge node from the prior sections.</p>
 </div>
-<hr>
+<hr/>
 </div>
 <div class="sect2">
-<h3 id="_lets_explore_credentials">Let&#8217;s explore &#8230;&#8203; Credentials</h3>
+<h3 id="_lets_explore_credentials">Let’s explore …​ Credentials</h3>
 <div class="paragraph">
 <p>Select <strong>Credentials</strong></p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_cred_select.png" alt="tower cred select" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_cred_select.png" alt="tower cred select" height="50"/>
 </div>
 <div class="title">Credentials tab - Left hand side of screen</div>
 </div>
@@ -413,14 +413,14 @@ <h3 id="_lets_explore_credentials">Let&#8217;s explore &#8230;&#8203; Credential
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_cred_ssh.png" alt="tower cred ssh" height="350">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_cred_ssh.png" alt="tower cred ssh" height="350"/>
 </div>
 <div class="title">Encrypted credential</div>
 </div>
 <div class="paragraph">
 <p><strong><em>Note</em></strong>: Different credential types exists for different types of nodes that you want to manage.</p>
 </div>
-<hr>
+<hr/>
 </div>
 <div class="sect2">
 <h3 id="_navigate_to_the_next_lab_to_bring_it_all_together">Navigate to the next lab to bring it all together</h3>
@@ -524,7 +524,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -784,7 +784,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -896,7 +896,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -906,7 +906,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -993,7 +993,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/index.html
index 3c335124e..de14bfe6f 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/index.html
@@ -321,13 +321,13 @@ <h1>Exercise 3.1 - Setup Ansible template to stage temporary access token on edg
 <h2 id="_exercise_3_1_setup_a_template_to_load_a_temporary_token_on_the_edge_node">Exercise 3.1 - Setup a template to load a temporary token on the edge node</h2>
 <div class="sectionbody">
 <div class="sect2">
-<h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templates">Let&#8217;s bring Projects, Inventories, and Crentials all together with &#8230;&#8203; Templates</h3>
+<h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templates">Let’s bring Projects, Inventories, and Crentials all together with …​ Templates</h3>
 <div class="paragraph">
 <p>Select <strong>Templates</strong></p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_select.png" alt="tower templates select" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_select.png" alt="tower templates select" height="50"/>
 </div>
 <div class="title">Templates tab - Left hand side of screen</div>
 </div>
@@ -336,14 +336,14 @@ <h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templat
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_plus.png" alt="tower templates plus" height="200">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_plus.png" alt="tower templates plus" height="200"/>
 </div>
 <div class="title">Add Job Template</div>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -399,7 +399,7 @@ <h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templat
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 100%;">
+<col style="width: 100%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -415,7 +415,7 @@ <h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templat
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_extravars.png" alt="tower templates extravars" height="200">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_extravars.png" alt="tower templates extravars" height="200"/>
 </div>
 <div class="title">Example - Extra Variables</div>
 </div>
@@ -424,7 +424,7 @@ <h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templat
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_save.png" alt="tower template save" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_save.png" alt="tower template save" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -434,26 +434,26 @@ <h3 id="_lets_bring_projects_inventories_and_crentials_all_together_with_templat
 <div class="paragraph">
 <p><strong><em>Note:</em></strong> You may need to reload or you may need to wait for your browser to refresh</p>
 </div>
-<hr>
+<hr/>
 <div class="paragraph">
 <p>Select <strong>Add Survey</strong></p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_add_survey.png" alt="tower template add survey" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_add_survey.png" alt="tower template add survey" height="50"/>
 </div>
 <div class="title"></div>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_survey.png" alt="tower template survey" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_survey.png" alt="tower template survey" height="500"/>
 </div>
 <div class="title"></div>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -598,7 +598,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -858,7 +858,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -970,7 +970,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -980,7 +980,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1067,7 +1067,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/index.html
index d144c2ffa..6d5af51d8 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/index.html
@@ -329,7 +329,7 @@ <h3 id="_in_a_new_tab_log_into_red_hat_openshift">In a new tab, log into Red Hat
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_login.png" alt="rhocp login" height="400">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_login.png" alt="rhocp login" height="400"/>
 </div>
 <div class="title"></div>
 </div>
@@ -341,14 +341,14 @@ <h3 id="_in_a_new_tab_log_into_red_hat_openshift">In a new tab, log into Red Hat
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_token.gif" alt="rhocp token" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_token.gif" alt="rhocp token" height="500"/>
 </div>
 <div class="title"></div>
 </div>
 <div class="paragraph">
 <p>Highlight and copy the API token, it will look like <strong>sha256~ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopq</strong></p>
 </div>
-<hr>
+<hr/>
 <div class="paragraph">
 <p>Return to the Ansible Tower interface tab or navigate to
 <code>
@@ -366,7 +366,7 @@ <h3 id="_in_a_new_tab_log_into_red_hat_openshift">In a new tab, log into Red Hat
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_podman_login_run.gif" alt="tower podman login run" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_podman_login_run.gif" alt="tower podman login run" height="500"/>
 </div>
 <div class="title"></div>
 </div>
@@ -470,7 +470,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -730,7 +730,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -842,7 +842,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -852,7 +852,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -939,7 +939,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/index.html
index aafb7d51e..44209ef60 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/index.html
@@ -327,7 +327,7 @@ <h3 id="_configure_new_template_to_field_containers_to_edge_node">Configure new
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_select.png" alt="tower templates select" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_select.png" alt="tower templates select" height="50"/>
 </div>
 <div class="title">Templates tab - Left hand side of screen</div>
 </div>
@@ -336,14 +336,14 @@ <h3 id="_configure_new_template_to_field_containers_to_edge_node">Configure new
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_plus.png" alt="tower templates plus" height="200">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_plus.png" alt="tower templates plus" height="200"/>
 </div>
 <div class="title">Add Job Template</div>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -399,7 +399,7 @@ <h3 id="_configure_new_template_to_field_containers_to_edge_node">Configure new
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 100%;">
+<col style="width: 100%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -418,7 +418,7 @@ <h3 id="_configure_new_template_to_field_containers_to_edge_node">Configure new
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_save.png" alt="tower template save" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_template_save.png" alt="tower template save" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -433,7 +433,7 @@ <h3 id="_configure_new_template_to_field_containers_to_edge_node">Configure new
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_rocket.png" alt="tower rocket" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_rocket.png" alt="tower rocket" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -442,7 +442,7 @@ <h3 id="_configure_new_template_to_field_containers_to_edge_node">Configure new
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_field.gif" alt="tower templates field" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower_templates_field.gif" alt="tower templates field" height="500"/>
 </div>
 <div class="title"></div>
 </div>
@@ -554,7 +554,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -814,7 +814,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -926,7 +926,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -936,7 +936,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1023,7 +1023,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/index.html b/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/index.html
index f617d2f9e..19482d308 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/index.html
@@ -317,12 +317,12 @@ <h1>Exercise 4.0 - Update to a new container on OpenShift and field to edge</h1>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that we can pull a container from OpenShift and move it to an edge node via Ansible Automation, let&#8217;s repeat the process with a new release using the artifacts that we created.</p>
+<p>Now that we can pull a container from OpenShift and move it to an edge node via Ansible Automation, let’s repeat the process with a new release using the artifacts that we created.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2>
+<h2 id="_lets_login_to_the_web_console">Let’s Login to the Web Console</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>In your browser &amp; in a new tab, connect to the Red Hat OpenShift console</p>
@@ -334,18 +334,18 @@ <h2 id="_lets_login_to_the_web_console">Let&#8217;s Login to the Web Console</h2
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_login.png" alt="rhocp login" height="400">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/rhocp_login.png" alt="rhocp login" height="400"/>
 </div>
 <div class="title"></div>
 </div>
 <div class="sect2">
-<h3 id="_lets_build_the_pipeline_with_a_new_release">Let&#8217;s build the pipeline with a new release</h3>
+<h3 id="_lets_build_the_pipeline_with_a_new_release">Let’s build the pipeline with a new release</h3>
 <div class="paragraph">
 <p>Select <strong>Pipelines</strong> in the left menu</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipelines.png" alt="s2i pipelines" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipelines.png" alt="s2i pipelines" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -354,17 +354,17 @@ <h3 id="_lets_build_the_pipeline_with_a_new_release">Let&#8217;s build the pipel
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipelines_start.png" alt="s2i pipelines start" height="400">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_pipelines_start.png" alt="s2i pipelines start" height="400"/>
 </div>
 <div class="title"></div>
 </div>
 <div class="paragraph">
-<p>Click <strong>Edit Pipeline</strong> and then change <strong>GIT_REVISION</strong> from "<strong>release1</strong>" to "<strong>release2</strong>" and hit <strong>[Start]</strong>:</p>
+<p>Click <strong>Edit Pipeline</strong> and then change <strong>GIT_REVISION</strong> from &#34;<strong>release1</strong>&#34; to &#34;<strong>release2</strong>&#34; and hit <strong>[Start]</strong>:</p>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -381,7 +381,7 @@ <h3 id="_lets_build_the_pipeline_with_a_new_release">Let&#8217;s build the pipel
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology.png" alt="s2i view topology" height="50">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology.png" alt="s2i view topology" height="50"/>
 </div>
 <div class="title"></div>
 </div>
@@ -390,7 +390,7 @@ <h3 id="_lets_build_the_pipeline_with_a_new_release">Let&#8217;s build the pipel
 <h3 id="_review_running_container">Review running container</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology_url.png" alt="s2i view topology url" height="150">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/s2i_view_topology_url.png" alt="s2i view topology url" height="150"/>
 </div>
 <div class="title"></div>
 </div>
@@ -505,7 +505,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -765,7 +765,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -877,7 +877,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -887,7 +887,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -970,7 +970,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/index.html b/workshops/alpha/ansible_with_rhocp_edge/index.html
index 77c4eb3fb..115a60043 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/index.html
@@ -299,7 +299,7 @@ <h3 id="_what_is_ansible">What is Ansible?</h3>
 <div class="sect2">
 <h3 id="_what_is_red_hat_ansible_automation_platform">What is Red Hat Ansible Automation Platform?</h3>
 <div class="paragraph">
-<p>Red Hat Ansible Automation Platform is a foundation for building and operating automation services at scale using Ansible &#8230;&#8203; providing enterprises a composable, collaborative, and trusted execution environment.</p>
+<p>Red Hat Ansible Automation Platform is a foundation for building and operating automation services at scale using Ansible …​ providing enterprises a composable, collaborative, and trusted execution environment.</p>
 </div>
 <div class="paragraph">
 <p>Ansible Automation Platform allows users to take three simple actions with their enterprise automation journey:</p>
@@ -341,11 +341,11 @@ <h3 id="_what_is_red_hat_ansible_automation_platform">What is Red Hat Ansible Au
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_automation_platform_what.png" alt="ansible automation platform what">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_automation_platform_what.png" alt="ansible automation platform what"/>
 </div>
 <div class="title"></div>
 </div>
-<hr>
+<hr/>
 </div>
 </div>
 </div>
@@ -371,7 +371,7 @@ <h2 id="_what_you_will_learn">What you will learn</h2>
 <p>How to write an Ansible automation blueprint (<em>aka a playbook</em>)</p>
 </li>
 <li>
-<p>How Ansible Automation works with Red Hat&#8217;s enterprise Kubernets Platform - OpenShift</p>
+<p>How Ansible Automation works with Red Hat’s enterprise Kubernets Platform - OpenShift</p>
 </li>
 <li>
 <p>How to build an OCI container on Red Hat OpenShift via Source-to-Image (S2I)</p>
@@ -384,7 +384,7 @@ <h2 id="_what_you_will_learn">What you will learn</h2>
 </li>
 </ul>
 </div>
-<hr>
+<hr/>
 <div class="sect2">
 <h3 id="_what_do_we_want_to_do">What do we want to do?</h3>
 <div class="paragraph">
@@ -392,11 +392,11 @@ <h3 id="_what_do_we_want_to_do">What do we want to do?</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_workshop_what.png" alt="ansible workshop what">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/ansible_workshop_what.png" alt="ansible workshop what"/>
 </div>
 <div class="title"></div>
 </div>
-<hr>
+<hr/>
 </div>
 <div class="sect2">
 <h3 id="_where_do_we_start">Where do we start?</h3>
@@ -404,7 +404,7 @@ <h3 id="_where_do_we_start">Where do we start?</h3>
 <p>The environment consists of a Red Hat OpenShift cluster running Ansible Automation and Code Ready Workspaces.</p>
 </div>
 <div class="paragraph">
-<p>As part of the lab, you will &#8230;&#8203;</p>
+<p>As part of the lab, you will …​</p>
 </div>
 <div class="ulist">
 <ul>
@@ -424,10 +424,10 @@ <h3 id="_where_do_we_start">Where do we start?</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower.002.png" alt="Tower">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/tower.002.png" alt="Tower"/>
 </div>
 </div>
-<hr>
+<hr/>
 </div>
 </div>
 </div>
@@ -440,7 +440,7 @@ <h2 id="_your_responsibilities">Your Responsibilities</h2>
 <div class="paragraph">
 <p>Participate. We are going to cut you loose with Ansible, in just a little while. Have questions. Have opinions.</p>
 </div>
-<hr>
+<hr/>
 </div>
 </div>
 <div class="sect1">
@@ -619,7 +619,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -879,7 +879,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -991,7 +991,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1001,7 +1001,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1054,7 +1054,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/index.xml b/workshops/alpha/ansible_with_rhocp_edge/index.xml
index 80a714915..418f66e8a 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/index.xml
+++ b/workshops/alpha/ansible_with_rhocp_edge/index.xml
@@ -4,135 +4,85 @@
     <title>Applied Ansible Automation - Containerized Edge Workshop on Red Hat | Public Sector</title>
     <link>/workshops/alpha/ansible_with_rhocp_edge/</link>
     <description>Recent content in Applied Ansible Automation - Containerized Edge Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/alpha/ansible_with_rhocp_edge/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/alpha/ansible_with_rhocp_edge/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Running Ad hoc commands</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise1.0/</guid>
       <description>Exercise Description For our first exercise, we are going to run some ad hoc commands to help you get a feel for how Red Hat Ansible Automation works. Ansible ad hoc commands enable you to perform repeatable tasks on local or remote nodes, without having to write a playbook. They are very useful when you simply need to do one or two tasks quickly and often, to many remote nodes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Running an Ansible playbook</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise1.1/</guid>
-      <description>Objective: Configure Edge node to run a Performance CoPilot agent As part of this exercise, you will be running a pre-existing Ansible playbook pre-loaded into your CodeReady Workspace.
- The playbook is written to showcase a series of basic Ansible concepts.
- Note: The following commands below need to be run from within the Ansible terminal
- Step 1: Checking a playbook playbook for correct syntax However, before you run the playbook, lets take a few moments to understand the options.</description>
+      <description>Objective: Configure Edge node to run a Performance CoPilot agent As part of this exercise, you will be running a pre-existing Ansible playbook pre-loaded into your CodeReady Workspace.&#xA;The playbook is written to showcase a series of basic Ansible concepts.&#xA;Note: The following commands below need to be run from within the Ansible terminal&#xA;Step 1: Checking a playbook playbook for correct syntax However, before you run the playbook, lets take a few moments to understand the options.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Writing a playbook to push podman to the edge</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise1.2/</guid>
-      <description>Objective This exercise showcases using Ansible to configure podman and the podman API on a standalone Red Hat Enterprise Linux edge server.
- As part of the execise, you will be exposed to the following elements:
-   Ansible modules and supporting parameters (example: &#39;package&#39; and &#39;service&#39; modules)
-  How to use loops to make your ansible more efficient and smaller
-     Section 1: Creating a directory structure and files for your own playbook For our playbook, we are only going to write one play with two tasks.</description>
+      <description>Objective This exercise showcases using Ansible to configure podman and the podman API on a standalone Red Hat Enterprise Linux edge server.&#xA;As part of the execise, you will be exposed to the following elements:&#xA;Ansible modules and supporting parameters (example: &amp;#39;package&amp;#39; and &amp;#39;service&amp;#39; modules)&#xA;How to use loops to make your ansible more efficient and smaller&#xA;Section 1: Creating a directory structure and files for your own playbook For our playbook, we are only going to write one play with two tasks.</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Build a CI/CD pipeline and container in Red Hat OpenShift</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise2.0/</guid>
-      <description>Exercise Description As part of the Applied Ansible workshop, you will deploy (copy/transfer) a container built on top of Red Hat OpenShift to an edge node running only Red Hat Enterprise Linux utilizing Ansible Automation. Prior to that step, we need to actually &#34;create&#34; a container on Red Hat OpenShift.
-   Let&amp;#8217;s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console</description>
+      <description>Exercise Description As part of the Applied Ansible workshop, you will deploy (copy/transfer) a container built on top of Red Hat OpenShift to an edge node running only Red Hat Enterprise Linux utilizing Ansible Automation. Prior to that step, we need to actually &amp;#34;create&amp;#34; a container on Red Hat OpenShift.&#xA;Let’s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Run CI/CD pipeline (powered by Tekton) in Red Hat OpenShift</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise2.1/</guid>
-      <description>Exercise Description View the created pipeline and review the container that Ansible orchestrate deploying to the edge node.
- Let&amp;#8217;s review the container build Select Pipelines in the left menu:
-    === Click on Pipeline Runs in the menu, and then edge-?????? (where ?????? is some alphanumeric sequence):
-     Wait until pipeline details are green. Feel gree to watch the progress by selecting the Logs tab</description>
+      <description>Exercise Description View the created pipeline and review the container that Ansible orchestrate deploying to the edge node.&#xA;Let’s review the container build Select Pipelines in the left menu:&#xA;=== Click on Pipeline Runs in the menu, and then edge-?????? (where ?????? is some alphanumeric sequence):&#xA;Wait until pipeline details are green. Feel gree to watch the progress by selecting the Logs tab&#xA;View built container images …​ Select Topology in the left menu</description>
     </item>
-    
     <item>
       <title>Exercise 3.0 - Configure Red Hat Enterprise Linux to run containers</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.0/</guid>
-      <description>Exercise Description As part of the exercise, we are going to run a login command on the edge node to set a temporary token. This token will allow the edge node to log into the Red Hat OpenShift registry and download containers.
- As part of the exercise, we have built a playbook for you; however, no all of the variables are assigned. This allows us to distribute the playbook to multiple workshops and you the capability to understand how to run playbooks in Ansible tower and assign custom variables to those plays.</description>
+      <description>Exercise Description As part of the exercise, we are going to run a login command on the edge node to set a temporary token. This token will allow the edge node to log into the Red Hat OpenShift registry and download containers.&#xA;As part of the exercise, we have built a playbook for you; however, no all of the variables are assigned. This allows us to distribute the playbook to multiple workshops and you the capability to understand how to run playbooks in Ansible tower and assign custom variables to those plays.</description>
     </item>
-    
     <item>
       <title>Exercise 3.1 - Setup Ansible template to stage temporary access token on edge node</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.1/</guid>
-      <description>Exercise 3.1 - Setup a template to load a temporary token on the edge node Let&amp;#8217;s bring Projects, Inventories, and Crentials all together with &amp;#8230;&amp;#8203; Templates Select Templates
-  Templates tab - Left hand side of screen  Select the + sign to add a new template; then select Job Template
-  Add Job Template      NAME
- Setup edge authentication to registry - user1</description>
+      <description>Exercise 3.1 - Setup a template to load a temporary token on the edge node Let’s bring Projects, Inventories, and Crentials all together with …​ Templates Select Templates&#xA;Templates tab - Left hand side of screen Select the + sign to add a new template; then select Job Template&#xA;Add Job Template NAME&#xA;Setup edge authentication to registry - user1&#xA;DESCRIPTION&#xA;Podman login&#xA;JOB TYPE&#xA;Run&#xA;INVENTORY&#xA;user1-inventory&#xA;PROJECT</description>
     </item>
-    
     <item>
       <title>Exercise 3.2 - Running an Ansible Automation template</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.2/</guid>
-      <description>Exercise 3.2 - Retrieve user token from OpenShift and launch login template In a new tab, log into Red Hat OpenShift  https://console-openshift-console.apps.example.redhatgov.io 
-    Navigate to the user1 menu in the upper right hand corner and select Copy login command.
- You will be prompted to login again. Once complete, select Display Token
-    Highlight and copy the API token, it will look like sha256~ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopq</description>
+      <description>Exercise 3.2 - Retrieve user token from OpenShift and launch login template In a new tab, log into Red Hat OpenShift https://console-openshift-console.apps.example.redhatgov.io Navigate to the user1 menu in the upper right hand corner and select Copy login command.&#xA;You will be prompted to login again. Once complete, select Display Token&#xA;Highlight and copy the API token, it will look like sha256~ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopq&#xA;Return to the Ansible Tower interface tab or navigate to https://ansible-tower-web-svc-tower.</description>
     </item>
-    
     <item>
       <title>Exercise 3.3 - Create new template to stage containers on edge node</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise3.3/</guid>
-      <description>Exercise 3.3 - Configure podman, systemd, and pull a container from OpenShift Configure new template to field containers to edge node Select Templates
-  Templates tab - Left hand side of screen  Select the + sign to add a new template; then select Job Template
-  Add Job Template      NAME
- Field container to edge node - user1
-   DESCRIPTION</description>
+      <description>Exercise 3.3 - Configure podman, systemd, and pull a container from OpenShift Configure new template to field containers to edge node Select Templates&#xA;Templates tab - Left hand side of screen Select the + sign to add a new template; then select Job Template&#xA;Add Job Template NAME&#xA;Field container to edge node - user1&#xA;DESCRIPTION&#xA;Update to latest container release in OpenShift&#xA;JOB TYPE&#xA;Run&#xA;INVENTORY&#xA;user1-inventory&#xA;PROJECT</description>
     </item>
-    
     <item>
       <title>Exercise 4.0 - Update to a new container on OpenShift and field to edge</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/exercise4.0/</guid>
-      <description>Exercise Description Now that we can pull a container from OpenShift and move it to an edge node via Ansible Automation, let&amp;#8217;s repeat the process with a new release using the artifacts that we created.
-   Let&amp;#8217;s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console
-  https://console-openshift-console.apps.example.redhatgov.io 
-    Let&amp;#8217;s build the pipeline with a new release Select Pipelines in the left menu</description>
+      <description>Exercise Description Now that we can pull a container from OpenShift and move it to an edge node via Ansible Automation, let’s repeat the process with a new release using the artifacts that we created.&#xA;Let’s Login to the Web Console In your browser &amp;amp; in a new tab, connect to the Red Hat OpenShift console&#xA;https://console-openshift-console.apps.example.redhatgov.io Let’s build the pipeline with a new release Select Pipelines in the left menu</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/setup/</guid>
-      <description>In order for you to &#39;write&#39; your first bit of Ansible, you will need an editor &amp;#8230;&amp;#8203; Ansible playbooks are written in YAML and you can use an text editor &#34;like vim&#34; or an editor like Visual Studio Code to get started. For this workshop, we will be utilizing a web-based IDE (integrated development environment) call Red Hat CodeReady Workspaces. Red Hat CodeReady Workspaces is a developer tool that makes cloud-native development practical for teams, using Kubernetes and containers to provide any member of the development or IT team with a consistent, preconfigured development environment.</description>
+      <description>In order for you to &amp;#39;write&amp;#39; your first bit of Ansible, you will need an editor …​ Ansible playbooks are written in YAML and you can use an text editor &amp;#34;like vim&amp;#34; or an editor like Visual Studio Code to get started. For this workshop, we will be utilizing a web-based IDE (integrated development environment) call Red Hat CodeReady Workspaces. Red Hat CodeReady Workspaces is a developer tool that makes cloud-native development practical for teams, using Kubernetes and containers to provide any member of the development or IT team with a consistent, preconfigured development environment.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/alpha/ansible_with_rhocp_edge/setup/index.html b/workshops/alpha/ansible_with_rhocp_edge/setup/index.html
index cef1d1d34..6f098eb7a 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/setup/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/setup/index.html
@@ -314,10 +314,10 @@ <h1>Setup</h1>
 </nav>
 
     <div class="sect1">
-<h2 id="_in_order_for_you_to_write_your_first_bit_of_ansible_you_will_need_an_editor">In order for you to <em>'write'</em> your first bit of Ansible, you will need an <strong>editor</strong> &#8230;&#8203;</h2>
+<h2 id="_in_order_for_you_to_write_your_first_bit_of_ansible_you_will_need_an_editor">In order for you to <em>&#39;write&#39;</em> your first bit of Ansible, you will need an <strong>editor</strong> …​</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Ansible playbooks are written in YAML and you can use an text editor "like vim" or an editor like Visual Studio Code to get started.  For this workshop, we will be utilizing a web-based IDE (integrated development environment) call Red Hat CodeReady Workspaces.  Red Hat CodeReady Workspaces is a developer tool that makes cloud-native development practical for teams, using Kubernetes and containers to provide any member of the development or IT team with a consistent, preconfigured development environment.</p>
+<p>Ansible playbooks are written in YAML and you can use an text editor &#34;like vim&#34; or an editor like Visual Studio Code to get started.  For this workshop, we will be utilizing a web-based IDE (integrated development environment) call Red Hat CodeReady Workspaces.  Red Hat CodeReady Workspaces is a developer tool that makes cloud-native development practical for teams, using Kubernetes and containers to provide any member of the development or IT team with a consistent, preconfigured development environment.</p>
 </div>
 </div>
 </div>
@@ -345,14 +345,14 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_login.png" alt="crw login" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_login.png" alt="crw login" height="500"/>
 </div>
 <div class="title">Code Ready Workspaces Login</div>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -367,7 +367,7 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 </table>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
@@ -375,11 +375,11 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 Please accept any self-signed certificates (if prompted).  If you get the following certificate error, follow the instructions on the page.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_login_cert.png" alt="crw login cert" height="275">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_login_cert.png" alt="crw login cert" height="275"/>
 </div>
 <div class="title">Code Ready Workspaces Login - Certificate Import</div>
 </div>
@@ -388,13 +388,13 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_landingpage.png" alt="crw landingpage" height="300">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_landingpage.png" alt="crw landingpage" height="300"/>
 </div>
 <div class="title">Red Hat CodeReady Workspaces default landing page</div>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_play.png" alt="crw play" height="300">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_play.png" alt="crw play" height="300"/>
 </div>
 <div class="title">Play Ansible Workspace by selecting che-ansible-demo-XXXX</div>
 </div>
@@ -403,21 +403,21 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_restartcancel.png" alt="crw restartcancel" height="125">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_restartcancel.png" alt="crw restartcancel" height="125"/>
 </div>
-<div class="title">If presented with the following menu, press "Cancel".  There is not need to restart the workspace and apply the new features for this workshop.</div>
+<div class="title">If presented with the following menu, press &#34;Cancel&#34;.  There is not need to restart the workspace and apply the new features for this workshop.</div>
 </div>
 <div class="paragraph">
-<p>After entering the workspace, we have configured you a custom "Task" to setup your SSH keys for the session.
-Go to "Terminal" &#8594; "Run Task" &#8594; select "Set ssh-key file permissions"</p>
+<p>After entering the workspace, we have configured you a custom &#34;Task&#34; to setup your SSH keys for the session.
+Go to &#34;Terminal&#34; → &#34;Run Task&#34; → select &#34;Set ssh-key file permissions&#34;</p>
 </div>
 <div class="paragraph">
 <p>After the permissions are set, launch an interactive terminal with preloaded Ansible utilities within your web IDE.
-Go to "Terminal" &#8594; "Open Terminal in specific container" &#8594; select "ansible"</p>
+Go to &#34;Terminal&#34; → &#34;Open Terminal in specific container&#34; → select &#34;ansible&#34;</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_launch_terminal.gif" alt="crw launch terminal" height="500">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_launch_terminal.gif" alt="crw launch terminal" height="500"/>
 </div>
 <div class="title">Launch Ansible terminal</div>
 </div>
@@ -426,7 +426,7 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_tour.png" alt="crw tour" height="600">
+<img src="/workshops/alpha/ansible_with_rhocp_edge/images/crw_tour.png" alt="crw tour" height="600"/>
 </div>
 <div class="title">Quick Tour</div>
 </div>
@@ -436,7 +436,7 @@ <h2 id="_accessing_red_hat_codeready_workspaces">Accessing Red Hat CodeReady Wor
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your environment.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your environment.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -538,7 +538,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -798,7 +798,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -910,7 +910,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -920,7 +920,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1002,7 +1002,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/alpha/ansible_with_rhocp_edge/wrapup/index.html b/workshops/alpha/ansible_with_rhocp_edge/wrapup/index.html
index 82831b2c8..f6e5a91c2 100644
--- a/workshops/alpha/ansible_with_rhocp_edge/wrapup/index.html
+++ b/workshops/alpha/ansible_with_rhocp_edge/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrapup</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something valuable
+<p>That wraps up what we have planned for today.  We hope you’ve learned something valuable
 about Ansible and Red Hat Ansible Tower that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
@@ -331,7 +331,7 @@ <h1>Wrapup</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_ansible/images/redhat.svg" alt="redhat">
+<img src="/workshops/ansible_ansible/images/redhat.svg" alt="redhat"/>
 </div>
 </div>
 
@@ -369,7 +369,7 @@ <h1>Wrapup</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_ansible/index.html b/workshops/ansible_ansible/index.html
index b287ffd25..2fb14de54 100644
--- a/workshops/ansible_ansible/index.html
+++ b/workshops/ansible_ansible/index.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
 
-    <title>ansible_ansible | Red Hat | Public Sector</title>
+    <title>Ansible_ansible | Red Hat | Public Sector</title>
 
     
     
@@ -279,7 +279,7 @@
 
 
 <div class="jumbotron jumbotron-page text-center">
-  <h1>ansible_ansible</h1>
+  <h1>Ansible_ansible</h1>
 </div>
 
 <div class="container">
@@ -290,7 +290,7 @@ <h1>ansible_ansible</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_ansible/index.xml b/workshops/ansible_ansible/index.xml
index 8fb3a7974..232fc4a6d 100644
--- a/workshops/ansible_ansible/index.xml
+++ b/workshops/ansible_ansible/index.xml
@@ -1,36 +1,25 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
-    <title>ansible_ansible on Red Hat | Public Sector</title>
+    <title>Ansible_ansible on Red Hat | Public Sector</title>
     <link>/workshops/ansible_ansible/</link>
-    <description>Recent content in ansible_ansible on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <description>Recent content in Ansible_ansible on Red Hat | Public Sector</description>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/ansible_ansible/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/ansible_ansible/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Wrapup</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/ansible_automation/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/ansible_automation/exercise1.0/index.html b/workshops/ansible_automation/exercise1.0/index.html
index 5428eb13c..aab8bda3e 100644
--- a/workshops/ansible_automation/exercise1.0/index.html
+++ b/workshops/ansible_automation/exercise1.0/index.html
@@ -329,13 +329,13 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_quick_example">Quick example:</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Let&#8217;s deploy an application on your local node that can assist you with the workshop.  Using ad hoc commands, we will download a configuration file from a remote git server (gitOps), set up a system service, and start the service.</p>
+<p>Let’s deploy an application on your local node that can assist you with the workshop.  Using ad hoc commands, we will download a configuration file from a remote git server (gitOps), set up a system service, and start the service.</p>
 </div>
 <div class="exampleblock">
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -343,7 +343,7 @@ <h2 id="_quick_example">Quick example:</h2>
 The service will be a Visual Studio Code container, defined in a Kubernetes POD YAML, launched via podman by systemd.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -357,21 +357,21 @@ <h2 id="_quick_example">Quick example:</h2>
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-We have configured 'sudo' for you; however, Ansible can use lots of other methods to become (-b) the superuser.
+We have configured &#39;sudo&#39; for you; however, Ansible can use lots of other methods to become (-b) the superuser.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost --module-name uri --args "url=https://raw.githubusercontent.com/RedHatGov/redhatgov.workshops/master/ansible_tower_aws/files/code-server.service return_content=yes dest=/etc/systemd/system" --become</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost --module-name uri --args &#34;url=https://raw.githubusercontent.com/RedHatGov/redhatgov.workshops/master/ansible_tower_aws/files/code-server.service return_content=yes dest=/etc/systemd/system&#34; --become</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -379,7 +379,7 @@ <h2 id="_quick_example">Quick example:</h2>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost --module-name service --args "name=code-server state=started enabled=yes" --become</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost --module-name service --args &#34;name=code-server state=started enabled=yes&#34; --become</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -418,7 +418,7 @@ <h3 id="_managing_remote_hosts">Managing remote hosts</h3>
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -426,7 +426,7 @@ <h3 id="_managing_remote_hosts">Managing remote hosts</h3>
 The <strong>workshopname</strong>, in the example below, will be provided to you by your instructor.  The <strong>#</strong> should be replaced by your student number.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>For example, a recent workshop student used:
@@ -453,7 +453,7 @@ <h3 id="_managing_remote_hosts">Managing remote hosts</h3>
 <div class="sect2">
 <h3 id="_step_1_test_webhost_response">Step 1: Test webhost response</h3>
 <div class="paragraph">
-<p>Let&#8217;s start with something basic - pinging a host.  The <code>ping</code> module tests the responsiveness of our web host.</p>
+<p>Let’s start with something basic - pinging a host.  The <code>ping</code> module tests the responsiveness of our web host.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -464,18 +464,18 @@ <h3 id="_step_1_test_webhost_response">Step 1: Test webhost response</h3>
 <div class="sect2">
 <h3 id="_step_2_run_a_linux_command">Step 2: Run a Linux command</h3>
 <div class="paragraph">
-<p>Now let&#8217;s see how we can run a Linux command and format the output, using the <code>command</code> module.</p>
+<p>Now let’s see how we can run a Linux command and format the output, using the <code>command</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web --module-name command --args "uptime" --one-line</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web --module-name command --args &#34;uptime&#34; --one-line</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="paragraph">
-<p>Take a look at your web node&#8217;s configuration.  The <code>setup</code> module displays Ansible facts (and a lot of them) about an endpoint.</p>
+<p>Take a look at your web node’s configuration.  The <code>setup</code> module displays Ansible facts (and a lot of them) about an endpoint.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -486,7 +486,7 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -494,11 +494,11 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 Like many Linux commands, <strong>ansible</strong> allows for long-form and short-form command-line arguments.  For example:
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web --module-name command --args "uptime" --one-line --become</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web --module-name command --args &#34;uptime&#34; --one-line --become</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -506,7 +506,7 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m command -a "uptime" -o -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m command -a &#34;uptime&#34; -o -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -518,19 +518,19 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="sect2">
 <h3 id="_step_4_install_node_js">Step 4: Install Node.js</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s install Node.js, using the <code>dnf</code> module.</p>
+<p>Now, let’s install Node.js, using the <code>dnf</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m dnf -a "name=nodejs state=present" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m dnf -a &#34;name=nodejs state=present&#34; -b</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_5_lets_copy_a_file_to_the_managed_node">Step 5: Let&#8217;s copy a file to the managed node.</h3>
+<h3 id="_step_5_lets_copy_a_file_to_the_managed_node">Step 5: Let’s copy a file to the managed node.</h3>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m copy -a "src=hello.js dest=hello.js"</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m copy -a &#34;src=hello.js dest=hello.js&#34;</code></pre>
 </div>
 </div>
 </div>
@@ -538,7 +538,7 @@ <h3 id="_step_5_lets_copy_a_file_to_the_managed_node">Step 5: Let&#8217;s copy a
 <h3 id="_step_6_copy_configuration_file_to_priviledged_location">Step 6: Copy configuration file to priviledged location</h3>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m copy -a "src=hello.service dest=/etc/systemd/system/hello.service" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m copy -a &#34;src=hello.service dest=/etc/systemd/system/hello.service&#34; -b</code></pre>
 </div>
 </div>
 </div>
@@ -549,9 +549,9 @@ <h3 id="_step_6_deploy_an_application">Step 6: Deploy an application</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a "name=hello state=started enabled=yes" -b
-ansible web -m firewalld -a "port=8080/tcp permanent=yes state=enabled" -b
-ansible web -m systemd -a "name=firewalld state=reloaded" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a &#34;name=hello state=started enabled=yes&#34; -b
+ansible web -m firewalld -a &#34;port=8080/tcp permanent=yes state=enabled&#34; -b
+ansible web -m systemd -a &#34;name=firewalld state=reloaded&#34; -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -559,8 +559,8 @@ <h3 id="_step_6_deploy_an_application">Step 6: Deploy an application</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m uri -a "url=http://localhost:8080 return_content=yes"
-ansible localhost -m uri -a "url=node-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8080 return_content=yes"</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m uri -a &#34;url=http://localhost:8080 return_content=yes&#34;
+ansible localhost -m uri -a &#34;url=node-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8080 return_content=yes&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -575,11 +575,11 @@ <h3 id="_step_6_deploy_an_application">Step 6: Deploy an application</h3>
 <div class="sect2">
 <h3 id="_step_7_cleanup">Step 7: Cleanup</h3>
 <div class="paragraph">
-<p>Finally, let&#8217;s clean up after ourselves.  First, stop the node service, using the following command.</p>
+<p>Finally, let’s clean up after ourselves.  First, stop the node service, using the following command.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a "name=hello state=stopped enabled=no" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a &#34;name=hello state=stopped enabled=no&#34; -b</code></pre>
 </div>
 </div>
 </div>
@@ -590,19 +590,19 @@ <h3 id="_step_8_remove_package">Step 8: Remove package</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m dnf -a "name=nodejs state=absent" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m dnf -a &#34;name=nodejs state=absent&#34; -b</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_9_clean_files">Step 9: Clean files</h3>
 <div class="paragraph">
-<p>Last, let&#8217;s remove the web content and service definition:</p>
+<p>Last, let’s remove the web content and service definition:</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m file -a "path=/home/ec2-user/hello.js state=absent"
-ansible web -m file -a "path=/etc/systemd/system/hello.service state=absent" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m file -a &#34;path=/home/ec2-user/hello.js state=absent&#34;
+ansible web -m file -a &#34;path=/etc/systemd/system/hello.service state=absent&#34; -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -705,7 +705,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -965,7 +965,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1077,7 +1077,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1087,7 +1087,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1174,7 +1174,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise1.1/index.html b/workshops/ansible_automation/exercise1.1/index.html
index 634301dad..ac82524d5 100644
--- a/workshops/ansible_automation/exercise1.1/index.html
+++ b/workshops/ansible_automation/exercise1.1/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.1 - Writing Your First Playbook</h1>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve gotten a sense of how Red Hat Ansible Tower works, we are going to write our first Ansible playbook.  The playbook is where you can take some of those ad hoc commands you just ran and put them into a repeatable set of <strong>plays</strong> and <strong>tasks</strong>.</p>
+<p>Now that you’ve gotten a sense of how Red Hat Ansible Tower works, we are going to write our first Ansible playbook.  The playbook is where you can take some of those ad hoc commands you just ran and put them into a repeatable set of <strong>plays</strong> and <strong>tasks</strong>.</p>
 </div>
 <div class="paragraph">
 <p>A playbook can have multiple plays and a play can have one or multiple tasks.  The goal of a <strong>play</strong> is to map a group of hosts.  The goal of a <strong>task</strong> is to implement modules against those hosts.</p>
@@ -332,15 +332,15 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_running_a_pre_existing_playbook_from_scm">Section 1: Running a pre-existing playbook from SCM</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Let&#8217;s clone a source code repository locally to get the sample playbook.</p>
+<p>Let’s clone a source code repository locally to get the sample playbook.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m git -a "repo=https://github.com/RedHatGov/workshop.artifacts.git dest=artifacts"</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m git -a &#34;repo=https://github.com/RedHatGov/workshop.artifacts.git dest=artifacts&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p>Now, let&#8217;s run a playbook.  This playbook will open firewall ports on the remote node.</p>
+<p>Now, let’s run a playbook.  This playbook will open firewall ports on the remote node.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -390,7 +390,7 @@ <h3 id="_step_2_open_the_apache_install">Step 2: Open the apache install</h3>
 <h2 id="_section_2_defining_your_play">Section 2: Defining Your play</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you are editing <code>install_apache.yml</code>, let&#8217;s begin by defining the play. Then, we&#8217;ll take some time to understand what each line accomplishes.</p>
+<p>Now that you are editing <code>install_apache.yml</code>, let’s begin by defining the play. Then, we’ll take some time to understand what each line accomplishes.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -422,10 +422,10 @@ <h2 id="_section_2_defining_your_play">Section 2: Defining Your play</h2>
 <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding tasks to your play</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that we&#8217;ve defined your play, let&#8217;s add some tasks to get some things done.  Align (vertically) the <strong>t</strong> in <code>task</code> with the <strong>b</strong> <code>become</code>. <br></p>
+<p>Now that we’ve defined your play, let’s add some tasks to get some things done.  Align (vertically) the <strong>t</strong> in <code>task</code> with the <strong>b</strong> <code>become</code>. <br/></p>
 </div>
 <div class="paragraph">
-<p>Yes, it does actually matter.  In fact, you should make sure all of your playbook statements are aligned, as shown here.<br></p>
+<p>Yes, it does actually matter.  In fact, you should make sure all of your playbook statements are aligned, as shown here.<br/></p>
 </div>
 <div class="paragraph">
 <p>If you want to see the entire playbook for reference, skip to the bottom of this exercise.</p>
@@ -492,7 +492,7 @@ <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding tasks to your pl
 <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve completed writing your playbook, it would be a shame not to keep it for later use.</p>
+<p>Now that you’ve completed writing your playbook, it would be a shame not to keep it for later use.</p>
 </div>
 <div class="paragraph">
 <p>Use the <code>write/quit</code> method in <code>vi</code> or <code>vim</code> to save your playbook, i.e. <code>Esc :wq!</code></p>
@@ -503,7 +503,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -513,7 +513,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your playbook</h2>
 like this.  Take note of the spacing and alignment.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -634,7 +634,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -894,7 +894,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1006,7 +1006,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1016,7 +1016,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1102,7 +1102,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise1.2/index.html b/workshops/ansible_automation/exercise1.2/index.html
index 97e7f3f85..77e80a73f 100644
--- a/workshops/ansible_automation/exercise1.2/index.html
+++ b/workshops/ansible_automation/exercise1.2/index.html
@@ -341,7 +341,7 @@ <h3 id="_step_1_check_your_playbook">Step 1: Check your playbook</h3>
 <div class="ulist NOTE">
 <ul class="NOTE">
 <li>
-<p><strong>--syntax-check</strong> If you run into any issues with your playbook running properly (from the copy/pasting that we told you not to do), you could use this option to help find those issues like so&#8230;&#8203;</p>
+<p><strong>--syntax-check</strong> If you run into any issues with your playbook running properly (from the copy/pasting that we told you not to do), you could use this option to help find those issues like so…​</p>
 </li>
 </ul>
 </div>
@@ -350,7 +350,7 @@ <h3 id="_step_1_check_your_playbook">Step 1: Check your playbook</h3>
 <pre class="highlight"><code class="language-bash" data-lang="bash">ansible-playbook install_apache.yml --syntax-check</code></pre>
 </div>
 </div>
-<hr>
+<hr/>
 <div class="paragraph">
 <p>Now, run your playbook:</p>
 </div>
@@ -367,13 +367,13 @@ <h3 id="_step_1_check_your_playbook">Step 1: Check your playbook</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/stdout_1.png" alt="stdout 1" height="328">
+<img src="/workshops/ansible_automation/images/stdout_1.png" alt="stdout 1" height="328"/>
 </div>
 <div class="title">Figure 1: apache_basic playbook stdout</div>
 </div>
 <div class="paragraph">
 <p>Notice that the play and each task is named, so that you can understand the action being performed and the node it is being performed upon.
-You also may notice a task in there that you didn&#8217;t write;  &lt;cough&gt; <code>setup</code> &lt;/cough&gt;.  This is because the <code>setup</code> module
+You also may notice a task in there that you didn’t write;  &lt;cough&gt; <code>setup</code> &lt;/cough&gt;.  This is because the <code>setup</code> module
 runs by default.  To turn if off, you can specify <a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html#turning-off-facts">gather_facts: false</a> in your play definition like this:</p>
 </div>
 <div class="listingblock">
@@ -389,10 +389,10 @@ <h3 id="_step_1_check_your_playbook">Step 1: Check your playbook</h3>
 <div class="sect2">
 <h3 id="_step_2_remove_apache">Step 2: Remove Apache</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s experiment a little.
-We would like you to reverse what you&#8217;ve done (i.e. stop and uninstall apache on your web nodes).
-So, edit your playbook and then when you&#8217;re finished, rerun it - as described in <strong>Step 1</strong>.
-For this exercise we aren&#8217;t going to show you line by line, but we will give you a few hints.</p>
+<p>Now, let’s experiment a little.
+We would like you to reverse what you’ve done (i.e. stop and uninstall apache on your web nodes).
+So, edit your playbook and then when you’re finished, rerun it - as described in <strong>Step 1</strong>.
+For this exercise we aren’t going to show you line by line, but we will give you a few hints.</p>
 </div>
 <div class="ulist NOTE">
 <ul class="NOTE">
@@ -404,7 +404,7 @@ <h3 id="_step_2_remove_apache">Step 2: Remove Apache</h3>
 <p>If <code>started</code> makes sure a service is started, then what option ensures it is stopped?</p>
 </li>
 <li>
-<p>If <code>present</code> makes sure a package is installed, then what option ensures it is removed?  Er&#8230;&#8203; starts with an <strong>ab</strong>, ends with a <strong>sent</strong></p>
+<p>If <code>present</code> makes sure a package is installed, then what option ensures it is removed?  Er…​ starts with an <strong>ab</strong>, ends with a <strong>sent</strong></p>
 </li>
 </ul>
 </div>
@@ -521,7 +521,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -781,7 +781,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -893,7 +893,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -903,7 +903,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -990,7 +990,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise1.3/index.html b/workshops/ansible_automation/exercise1.3/index.html
index c7b837398..ff8731f38 100644
--- a/workshops/ansible_automation/exercise1.3/index.html
+++ b/workshops/ansible_automation/exercise1.3/index.html
@@ -341,9 +341,9 @@ <h2 id="_exercise_description">Exercise Description</h2>
 If so, you may need to restart a service, for those changes to take effect.  We do that with a handler.</p>
 </div>
 <div class="paragraph">
-<p>For a full understanding of variables, loops, and handlers; check out our Ansible documentation on these subjects.<br>
-<a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html">Ansible Variables</a><br>
-<a href="http://docs.ansible.com/ansible/latest/playbooks_loops.html">Ansible Loops</a><br>
+<p>For a full understanding of variables, loops, and handlers; check out our Ansible documentation on these subjects.<br/>
+<a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html">Ansible Variables</a><br/>
+<a href="http://docs.ansible.com/ansible/latest/playbooks_loops.html">Ansible Loops</a><br/>
 <a href="http://docs.ansible.com/ansible/latest/playbooks_intro.html#handlers-running-operations-on-change">Ansible Handlers</a></p>
 </div>
 </div>
@@ -360,7 +360,7 @@ <h2 id="_section_1_running_the_playbook">Section 1: Running the playbook</h2>
 <div class="sect2">
 <h3 id="_step_1_create_a_new_project_and_playbook">Step 1: Create a new project and playbook</h3>
 <div class="paragraph">
-<p>Navigate to the '~' directory create a new project and playbook.</p>
+<p>Navigate to the &#39;~&#39; directory create a new project and playbook.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -401,46 +401,46 @@ <h3 id="_step_3_add_a_task">Step 3: Add a task</h3>
 <pre class="highlight"><code class="language-bash" data-lang="bash">  tasks:
     - name: install httpd packages
       package:
-        name: "{{ item }}"
+        name: &#34;{{ item }}&#34;
         state: present
-      with_items: "{{ httpd_packages }}"
+      with_items: &#34;{{ httpd_packages }}&#34;
       notify: restart apache service</code></pre>
 </div>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>Explanation of the <strong>install httpd packages</strong> task actions.<br></p>
+<p>Explanation of the <strong>install httpd packages</strong> task actions.<br/></p>
 </div>
 <div class="ulist">
 <ul>
 <li>
-<p><code>vars:</code> You&#8217;ve told Ansible the next thing it sees will be a variable name<br></p>
+<p><code>vars:</code> You’ve told Ansible the next thing it sees will be a variable name<br/></p>
 </li>
 <li>
 <p><code>httpd_packages</code> You are defining a list-type variable called httpd_packages.  What follows
-is a list of those packages<br></p>
+is a list of those packages<br/></p>
 </li>
 <li>
-<p><code>{{ item }}</code> You are telling Ansible that this will expand into a list item like <code>httpd</code> and <code>python3-mod_wsgi</code>.<br></p>
+<p><code>{{ item }}</code> You are telling Ansible that this will expand into a list item like <code>httpd</code> and <code>python3-mod_wsgi</code>.<br/></p>
 </li>
 <li>
-<p><code>with_items: "{{ httpd_packages }}</code> This is your loop, which is instructing Ansible to perform this task on
+<p><code>with_items: &#34;{{ httpd_packages }}</code> This is your loop, which is instructing Ansible to perform this task on
 every <code>item</code> in <code>httpd_packages</code></p>
 </li>
 <li>
-<p><code>notify: restart apache service</code> This statement is a <code>handler</code>, so we&#8217;ll come back to it in Section 3.</p>
+<p><code>notify: restart apache service</code> This statement is a <code>handler</code>, so we’ll come back to it in Section 3.</p>
 </li>
 </ul>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -449,7 +449,7 @@ <h3 id="_step_3_add_a_task">Step 3: Add a task</h3>
 <h2 id="_section_2_deploying_files_and_starting_a_service">Section 2: Deploying files and starting a service</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>When you need to do pretty much anything with files and directories, use one of the <a href="http://docs.ansible.com/ansible/latest/list_of_files_modules.html">Ansible Files</a> modules.  In this case, we&#8217;ll leverage the <code>file</code> and <code>template</code> modules.</p>
+<p>When you need to do pretty much anything with files and directories, use one of the <a href="http://docs.ansible.com/ansible/latest/list_of_files_modules.html">Ansible Files</a> modules.  In this case, we’ll leverage the <code>file</code> and <code>template</code> modules.</p>
 </div>
 <div class="paragraph">
 <p>After that, you will define a task to start the apache service.</p>
@@ -500,7 +500,7 @@ <h3 id="_step_2_add_file_and_service_tasks">Step 2: Add file and service tasks</
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -518,7 +518,7 @@ <h3 id="_step_2_add_file_and_service_tasks">Step 2: Add file and service tasks</
 module family and we encourage you to check out all of the other <a href="http://docs.ansible.com/ansible/latest/list_of_files_modules.html">file-management modules here</a>.</p>
 </li>
 <li>
-<p><strong>jinja-who?</strong> - Not to be confused with 2013&#8217;s blockbuster "Ninja II - Shadow of a Tear", <a href="http://docs.ansible.com/ansible/latest/playbooks_templating.html">jinja2</a> is
+<p><strong>jinja-who?</strong> - Not to be confused with 2013’s blockbuster &#34;Ninja II - Shadow of a Tear&#34;, <a href="http://docs.ansible.com/ansible/latest/playbooks_templating.html">jinja2</a> is
 used in Ansible to transform data inside a template expression, i.e. filters.</p>
 </li>
 <li>
@@ -528,7 +528,7 @@ <h3 id="_step_2_add_file_and_service_tasks">Step 2: Add file and service tasks</
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -556,7 +556,7 @@ <h3 id="_step_1_define_a_handler">Step 1: Define a handler</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -572,33 +572,33 @@ <h3 id="_step_1_define_a_handler">Step 1: Define a handler</h3>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_calling_the_handlers">Step 2: Calling the handlers</h3>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>You can&#8217;t have a former if you don&#8217;t mention the latter.</p>
+<p>You can’t have a former if you don’t mention the latter.</p>
 </div>
 <div class="ulist">
 <ul>
 <li>
-<p><code>notify: restart apache service</code> &#8230;&#8203;and here is your latter. Finally!  The <code>notify</code> statement is the invocation of a handler by
-name.  Quite the reveal, we know.   You already noticed that you&#8217;ve added a <code>notify</code> statement to the <code>copy httpd.conf</code>
+<p><code>notify: restart apache service</code> …​and here is your latter. Finally!  The <code>notify</code> statement is the invocation of a handler by
+name.  Quite the reveal, we know.   You already noticed that you’ve added a <code>notify</code> statement to the <code>copy httpd.conf</code>
 task, now you know why.</p>
 </li>
 </ul>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -607,7 +607,7 @@ <h3 id="_step_2_calling_the_handlers">Step 2: Calling the handlers</h3>
 <h2 id="_section_4_review">Section 4: Review</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Your new, improved playbook is done! But don&#8217;t run it just yet, we&#8217;ll do that in our next exercise.  For now, let&#8217;s take a second look to make sure everything
+<p>Your new, improved playbook is done! But don’t run it just yet, we’ll do that in our next exercise.  For now, let’s take a second look to make sure everything
 looks the way you intended.  If not, now is the time to fix it up. The figure below shows line counts and spacing.</p>
 </div>
 <div class="listingblock">
@@ -626,9 +626,9 @@ <h2 id="_section_4_review">Section 4: Review</h2>
   tasks:
     - name: httpd packages are present
       package:
-        name: "{{ item }}"
+        name: &#34;{{ item }}&#34;
         state: present
-      with_items: "{{ httpd_packages }}"
+      with_items: &#34;{{ httpd_packages }}&#34;
       notify: restart apache service
 
     - name: site-enabled directory is present
@@ -761,7 +761,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1021,7 +1021,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1133,7 +1133,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1143,7 +1143,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1229,7 +1229,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise1.4/index.html b/workshops/ansible_automation/exercise1.4/index.html
index 2f47591bd..e2399d9da 100644
--- a/workshops/ansible_automation/exercise1.4/index.html
+++ b/workshops/ansible_automation/exercise1.4/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.4 - Running the apache-basic-playbook</h1>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Congratulations!  You just wrote a playbook that incorporates some key Ansible concepts that you use in
-most, if not all, of your future playbooks.  Before you get too excited though, we should probably make sure it actually runs. So, let&#8217;s do that now.</p>
+most, if not all, of your future playbooks.  Before you get too excited though, we should probably make sure it actually runs. So, let’s do that now.</p>
 </div>
 </div>
 </div>
@@ -347,11 +347,11 @@ <h2 id="_section_2_review">Section 2: Review</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>If successful, you should see standard output that looks very similar to the following.  If not, just let us
-know.  We&#8217;ll help get things fixed up.</p>
+know.  We’ll help get things fixed up.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/stdout_2.png" alt="stdout 2">
+<img src="/workshops/ansible_automation/images/stdout_2.png" alt="stdout 2"/>
 </div>
 <div class="title">Figure 1: apache-basic-playbook stdout</div>
 </div>
@@ -455,7 +455,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -715,7 +715,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -827,7 +827,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -837,7 +837,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -923,7 +923,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise1.5/index.html b/workshops/ansible_automation/exercise1.5/index.html
index 781d4d6c7..54d432cab 100644
--- a/workshops/ansible_automation/exercise1.5/index.html
+++ b/workshops/ansible_automation/exercise1.5/index.html
@@ -321,24 +321,24 @@ <h1>Exercise 1.5 - Roles: Making your playbooks reusable</h1>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>While it is possible to write a playbook in one file, as we&#8217;ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.</p>
+<p>While it is possible to write a playbook in one file, as we’ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.</p>
 </div>
 <div class="paragraph">
-<p>The "role" feature in Ansible is the way we do this.  When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure.  <em>"Wha??  You mean that seemingly useless <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html">best practice</a> you mentioned in exercise 1.2?"</em>   Yep, that one.</p>
+<p>The &#34;role&#34; feature in Ansible is the way we do this.  When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure.  <em>&#34;Wha??  You mean that seemingly useless <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html">best practice</a> you mentioned in exercise 1.2?&#34;</em>   Yep, that one.</p>
 </div>
 <div class="paragraph">
-<p>For this exercise, you are going to take the playbook you just wrote and refactor it into a role.  In addition, you&#8217;ll learn to use Ansible Galaxy.</p>
+<p>For this exercise, you are going to take the playbook you just wrote and refactor it into a role.  In addition, you’ll learn to use Ansible Galaxy.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s begin with understanding how your apache-basic-playbook will break down into a role.</p>
+<p>Let’s begin with understanding how your apache-basic-playbook will break down into a role.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/roledir_1.png" alt="apache-basic-playbook role directory structure">
+<img src="/workshops/ansible_automation/images/roledir_1.png" alt="apache-basic-playbook role directory structure"/>
 </div>
 </div>
 <div class="paragraph">
-<p>Fortunately, you don&#8217;t have to create all of these directories and files by hand.  That&#8217;s where Ansible Galaxy comes in.</p>
+<p>Fortunately, you don’t have to create all of these directories and files by hand.  That’s where Ansible Galaxy comes in.</p>
 </div>
 </div>
 </div>
@@ -346,7 +346,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_using_ansible_galaxy_to_initialize_a_new_role">Section 1: Using Ansible Galaxy to initialize a new role</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Ansible Galaxy is a free site for finding, downloading, and sharing roles.  It&#8217;s also pretty handy for creating them, which is what we are about to do here.</p>
+<p>Ansible Galaxy is a free site for finding, downloading, and sharing roles.  It’s also pretty handy for creating them, which is what we are about to do here.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1navigate_to_your_project">Step 1:Navigate to your project</h3>
@@ -382,7 +382,7 @@ <h3 id="_step_3_initialize_new_role">Step 3: Initialize new role</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Take a look around the structure you just created.  It should look a lot like Figure 1 above.  However, we need to complete one more step before moving onto Section 2.  It is Ansible best practice to clean out role directories and files you won&#8217;t be using.  For this role, we won&#8217;t be using anything from <code>files</code>, <code>tests</code>.</p>
+<p>Take a look around the structure you just created.  It should look a lot like Figure 1 above.  However, we need to complete one more step before moving onto Section 2.  It is Ansible best practice to clean out role directories and files you won’t be using.  For this role, we won’t be using anything from <code>files</code>, <code>tests</code>.</p>
 </div>
 </div>
 <div class="sect2">
@@ -477,13 +477,13 @@ <h3 id="_step_4_add_variables">Step 4: Add variables</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>Hey, wait just a minute&#8230;&#8203;did you just have us put variables in two separate places?  Yes&#8230;&#8203;yes we did.  Variables can live in quite a few places.  Just to name a few:<br></p>
+<p>Hey, wait just a minute…​did you just have us put variables in two separate places?  Yes…​yes we did.  Variables can live in quite a few places.  Just to name a few:<br/></p>
 </div>
 <div class="ulist">
 <ul>
@@ -509,11 +509,11 @@ <h3 id="_step_4_add_variables">Step 4: Add variables</h3>
 </div>
 <div class="paragraph">
 <p>Bottom line, you need to read up on <a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable">variable precedence</a> to understand both where to define variables and which locations take precedence.  In this exercise, we are using role defaults to define a couple of variables and these are the most malleable.  After that, we defined some variables in <code>/vars</code>
-which have a higher precedence than defaults and can&#8217;t be overridden as a default variable.</p>
+which have a higher precedence than defaults and can’t be overridden as a default variable.</p>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -556,9 +556,9 @@ <h3 id="_step_6_add_role_tasks">Step 6: Add role tasks</h3>
 <div class="content">
 <pre>- name: install httpd packages
   package:
-    name: "{{ item }}"
+    name: &#34;{{ item }}&#34;
     state: present
-  with_items: "{{ httpd_packages }}"
+  with_items: &#34;{{ httpd_packages }}&#34;
   notify: restart apache service
 
 - name: create site-enabled directory
@@ -588,7 +588,7 @@ <h3 id="_step_6_add_role_tasks">Step 6: Add role tasks</h3>
 <div class="sect2">
 <h3 id="_step_7_download_templates">Step 7: Download templates</h3>
 <div class="paragraph">
-<p>Download a couple of templates into <code>roles/apache-simple/templates/</code>.  And then, let&#8217;s clean up the templates from exercise 2.1, by removing the old templates directory.</p>
+<p>Download a couple of templates into <code>roles/apache-simple/templates/</code>.  And then, let’s clean up the templates from exercise 2.1, by removing the old templates directory.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -606,8 +606,8 @@ <h3 id="_step_7_download_templates">Step 7: Download templates</h3>
 <h2 id="_section_3_running_your_new_role_based_playbook">Section 3: Running your new role-based playbook</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve successfully separated your original playbook into a role,
-let&#8217;s run it and see how it works.</p>
+<p>Now that you’ve successfully separated your original playbook into a role,
+let’s run it and see how it works.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1_run_the_playbook">Step 1: Run the playbook</h3>
@@ -625,7 +625,7 @@ <h3 id="_step_2_verify_your_output">Step 2: Verify your output</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/stdout_3.png" alt="ansible-basic-playbook role-based stdout">
+<img src="/workshops/ansible_automation/images/stdout_3.png" alt="ansible-basic-playbook role-based stdout"/>
 </div>
 </div>
 </div>
@@ -737,7 +737,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -997,7 +997,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1109,7 +1109,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1119,7 +1119,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1205,7 +1205,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise2.0/index.html b/workshops/ansible_automation/exercise2.0/index.html
index d566671a7..6e42f13a3 100644
--- a/workshops/ansible_automation/exercise2.0/index.html
+++ b/workshops/ansible_automation/exercise2.0/index.html
@@ -388,15 +388,15 @@ <h3 id="_step_6_identify_variables">Step 6: Identify variables</h3>
 [database]
 
 [all:vars]
-admin_password=<strong>'ansibleWS'</strong>
+admin_password=<strong>&#39;ansibleWS&#39;</strong>
 
-pg_host=''
-pg_port=''
+pg_host=&#39;&#39;
+pg_port=&#39;&#39;
 
-pg_database='awx'
-pg_username='awx'
-pg_password=<strong>'ansibleWS'</strong>
-pg_sslmode='prefer'  # set to 'verify-full' for client-side enforced SSL
+pg_database=&#39;awx&#39;
+pg_username=&#39;awx&#39;
+pg_password=<strong>&#39;ansibleWS&#39;</strong>
+pg_sslmode=&#39;prefer&#39;  # set to &#39;verify-full&#39; for client-side enforced SSL
 
 # Isolated Tower nodes automatically generate an RSA key for authentication;
 # To disable this behavior, set this value to false
@@ -431,7 +431,7 @@ <h3 id="_step_7_run_setup">Step 7: Run setup</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -439,7 +439,7 @@ <h3 id="_step_7_run_setup">Step 7: Run setup</h3>
 Step 7 will take approx. 10-15 minutes to complete.  This may be a good time to take a break.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -456,11 +456,11 @@ <h3 id="_step_8_confirm_results">Step 8: Confirm results</h3>
 <div class="sect2">
 <h3 id="_ensuring_installation_success">Ensuring Installation Success</h3>
 <div class="paragraph">
-<p>You know you were successful if you are able to browse to your Ansible Tower&#8217;s url (<em>control node&#8217;s IP address</em>) and get something like this</p>
+<p>You know you were successful if you are able to browse to your Ansible Tower’s url (<em>control node’s IP address</em>) and get something like this</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen">
+<img src="/workshops/ansible_automation/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen"/>
 </div>
 <div class="title">Figure 2: Ansible Tower Login Screen</div>
 </div>
@@ -564,7 +564,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -824,7 +824,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -936,7 +936,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -946,7 +946,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1033,7 +1033,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise2.1/index.html b/workshops/ansible_automation/exercise2.1/index.html
index ca7f49cea..a7b0f73fa 100644
--- a/workshops/ansible_automation/exercise2.1/index.html
+++ b/workshops/ansible_automation/exercise2.1/index.html
@@ -355,7 +355,7 @@ <h3 id="_step_1_log_in">Step 1: Log in</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen">
+<img src="/workshops/ansible_automation/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen"/>
 </div>
 <div class="title">Figure 3: Ansible Tower Login Screen</div>
 </div>
@@ -364,7 +364,7 @@ <h3 id="_step_1_log_in">Step 1: Log in</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_lic_prompt.png" alt="at lic prompt">
+<img src="/workshops/ansible_automation/images/at_lic_prompt.png" alt="at lic prompt"/>
 </div>
 <div class="title">Figure 4: Uploading a License</div>
 </div>
@@ -378,19 +378,19 @@ <h3 id="_step_2_request_workshop_license">Step 2: Request workshop license</h3>
 <div class="sect2">
 <h3 id="_step_3_upload_ansible_tower_workshop_license">Step 3: Upload Ansible Tower workshop license</h3>
 <div class="paragraph">
-<p>Back in the Ansible Tower UI, choose BROWSE <span class="image"><img src="/workshops/ansible_automation/images/at_browse.png" alt="LicB" width="45" height="25"></span> and upload your recently downloaded license file into Ansible Tower.</p>
+<p>Back in the Ansible Tower UI, choose BROWSE <span class="image"><img src="/workshops/ansible_automation/images/at_browse.png" alt="LicB" width="45" height="25"/></span> and upload your recently downloaded license file into Ansible Tower.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_4_accept_license_agreement">Step 4: Accept license agreement</h3>
 <div class="paragraph">
-<p>Select "<em>I agree to the End User License Agreement</em>".</p>
+<p>Select &#34;<em>I agree to the End User License Agreement</em>&#34;.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_5_submit">Step 5: Submit</h3>
 <div class="paragraph">
-<p>Select SUBMIT <span class="image"><img src="/workshops/ansible_automation/images/at_submit.png" alt="Sub" width="35" height="25"></span></p>
+<p>Select SUBMIT <span class="image"><img src="/workshops/ansible_automation/images/at_submit.png" alt="Sub" width="35" height="25"/></span></p>
 </div>
 </div>
 </div>
@@ -408,13 +408,13 @@ <h2 id="_section_2_creating_a_credential">Section 2: Creating a credential</h2>
 <div class="sect2">
 <h3 id="_step_1_select_credentials">Step 1: Select Credentials</h3>
 <div class="paragraph">
-<p>Select CREDENTIALS, from the left-side menu bar.   <span class="image"><img src="/workshops/ansible_automation/images/at_credentials.png" alt="Cred" width="100" height="35"></span></p>
+<p>Select CREDENTIALS, from the left-side menu bar.   <span class="image"><img src="/workshops/ansible_automation/images/at_credentials.png" alt="Cred" width="100" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_select_add">Step 2: Select Add</h3>
 <div class="paragraph">
-<p>Select ADD   <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Select ADD   <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -429,8 +429,8 @@ <h3 id="_step_3_complete_the_ansible_tower_credentials_form">Step 3: Complete th
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -465,7 +465,7 @@ <h3 id="_step_3_complete_the_ansible_tower_credentials_form">Step 3: Complete th
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_cred_detail.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/at_cred_detail.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 5: Adding a Credential</div>
 </div>
@@ -473,7 +473,7 @@ <h3 id="_step_3_complete_the_ansible_tower_credentials_form">Step 3: Complete th
 <div class="sect2">
 <h3 id="_step_4_save">Step 4: Save</h3>
 <div class="paragraph">
-<p>Select SAVE  <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span><br></p>
+<p>Select SAVE  <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span><br/></p>
 </div>
 </div>
 </div>
@@ -490,13 +490,13 @@ <h2 id="_section_3_creating_a_project">Section 3: Creating a Project</h2>
 <div class="sect2">
 <h3 id="_step_1_open_a_new_project">Step 1: Open a new project</h3>
 <div class="paragraph">
-<p>Select PROJECTS <span class="image"><img src="/workshops/ansible_automation/images/at_projects.png" alt="projects" width="125" height="35"></span>.</p>
+<p>Select PROJECTS <span class="image"><img src="/workshops/ansible_automation/images/at_projects.png" alt="projects" width="125" height="35"/></span>.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_add_the_project">Step 2: Add the project</h3>
 <div class="paragraph">
-<p>Select ADD   <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Select ADD   <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -506,8 +506,8 @@ <h3 id="_step_3_complete_the_project_form">Step 3: Complete the Project form</h3
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -554,7 +554,7 @@ <h3 id="_step_3_complete_the_project_form">Step 3: Complete the Project form</h3
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_project_detail.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/at_project_detail.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 6: Defining a Project</div>
 </div>
@@ -562,7 +562,7 @@ <h3 id="_step_3_complete_the_project_form">Step 3: Complete the Project form</h3
 <div class="sect2">
 <h3 id="_step_4_save_2">Step 4: Save</h3>
 <div class="paragraph">
-<p>Select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 </div>
@@ -583,13 +583,13 @@ <h2 id="_section_4_creating_an_inventory">Section 4: Creating an Inventory</h2>
 <div class="sect2">
 <h3 id="_step_1_navigate_to_inventories_main_link">Step 1: Navigate to Inventories main link</h3>
 <div class="paragraph">
-<p>Select INVENTORIES    <span class="image"><img src="/workshops/ansible_automation/images/at_inv_icon.png" alt="Inv" width="100" height="30"></span></p>
+<p>Select INVENTORIES    <span class="image"><img src="/workshops/ansible_automation/images/at_inv_icon.png" alt="Inv" width="100" height="30"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_add_a_new_inventory">Step 2: Add a new inventory</h3>
 <div class="paragraph">
-<p>Select ADD <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span>, and then select Inventory.</p>
+<p>Select ADD <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span>, and then select Inventory.</p>
 </div>
 </div>
 <div class="sect2">
@@ -599,8 +599,8 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -619,7 +619,7 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_inv_create.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/at_inv_create.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 7: Create an Inventory</div>
 </div>
@@ -627,7 +627,7 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 <div class="sect2">
 <h3 id="_step_4_save_3">Step 4: Save</h3>
 <div class="paragraph">
-<p>Select SAVE  <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select SAVE  <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -648,7 +648,7 @@ <h3 id="_step_6_import_an_existing_inventory">Step 6: Import an existing invento
 </div>
 <div class="listingblock">
 <div class="content">
-<pre>sudo tower-manage inventory_import --source=/home/ec2-user/hosts --inventory-name="Ansible Workshop Inventory"</pre>
+<pre>sudo tower-manage inventory_import --source=/home/ec2-user/hosts --inventory-name=&#34;Ansible Workshop Inventory&#34;</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -656,19 +656,19 @@ <h3 id="_step_6_import_an_existing_inventory">Step 6: Import an existing invento
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_tm_stdout.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/at_tm_stdout.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 8: Importing an inventory with tower-manage</div>
 </div>
 <div class="paragraph">
-<p>Feel free to browse your inventory in Ansible Tower, by selecting <strong>Hosts</strong>. <span class="image"><img src="/workshops/ansible_automation/images/at_inv_hosts.png" alt="hosts" width="200" height="50"></span></p>
+<p>Feel free to browse your inventory in Ansible Tower, by selecting <strong>Hosts</strong>. <span class="image"><img src="/workshops/ansible_automation/images/at_inv_hosts.png" alt="hosts" width="200" height="50"/></span></p>
 </div>
 <div class="paragraph">
 <p>You should now notice that the inventory has been populated with each each of hosts and corresponding inventory.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_inv_group.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/at_inv_group.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 9: Inventory with Groups</div>
 </div>
@@ -778,7 +778,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1038,7 +1038,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1150,7 +1150,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1160,7 +1160,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1247,7 +1247,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise2.2/index.html b/workshops/ansible_automation/exercise2.2/index.html
index b10aa33c3..fb76ba00e 100644
--- a/workshops/ansible_automation/exercise2.2/index.html
+++ b/workshops/ansible_automation/exercise2.2/index.html
@@ -324,7 +324,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>This exercise will walk you through the steps required to create a job template and run it.  A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.</p>
 </div>
 <div class="paragraph">
-<p>Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.  Templates also drive uniformity, by running templates exactly the same way every time. And, because we&#8217;re using templates, production responsibilities can be delegated to less experienced production personnel.</p>
+<p>Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.  Templates also drive uniformity, by running templates exactly the same way every time. And, because we’re using templates, production responsibilities can be delegated to less experienced production personnel.</p>
 </div>
 </div>
 </div>
@@ -334,13 +334,13 @@ <h2 id="_section1_creating_a_job_template">Section1: Creating a job template</h2
 <div class="sect2">
 <h3 id="_step_1_navigate_to_the_templates_tab">Step 1: Navigate to the Templates tab</h3>
 <div class="paragraph">
-<p>Select TEMPLATES <span class="image"><img src="/workshops/ansible_automation/images/at_templates.png" alt="temp" width="120" height="35"></span></p>
+<p>Select TEMPLATES <span class="image"><img src="/workshops/ansible_automation/images/at_templates.png" alt="temp" width="120" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_create_a_new_template">Step 2: Create a new template</h3>
 <div class="paragraph">
-<p>Click <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span> and select JOB TEMPLATE <span class="image"><img src="/workshops/ansible_automation/images/at_jobtemplate.png" alt="jobT" width="150" height="100"></span></p>
+<p>Click <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span> and select JOB TEMPLATE <span class="image"><img src="/workshops/ansible_automation/images/at_jobtemplate.png" alt="jobT" width="150" height="100"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -350,8 +350,8 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -404,7 +404,7 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_jt_detail.png" alt="at jt detail" width="900">
+<img src="/workshops/ansible_automation/images/at_jt_detail.png" alt="at jt detail" width="900"/>
 </div>
 <div class="title">Figure 11: Job Template Form</div>
 </div>
@@ -412,7 +412,7 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 <div class="sect2">
 <h3 id="_step_4_save">Step 4: Save</h3>
 <div class="paragraph">
-<p>Click SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save"></span> and then select ADD SURVEY <span class="image"><img src="/workshops/ansible_automation/images/at_addsurvey.png" alt="Add Survey"></span></p>
+<p>Click SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save"/></span> and then select ADD SURVEY <span class="image"><img src="/workshops/ansible_automation/images/at_addsurvey.png" alt="Add Survey"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -425,8 +425,8 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -451,13 +451,13 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">DEFAULT ANSWER</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Be creative, keep it clean, we&#8217;re all professionals here</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Be creative, keep it clean, we’re all professionals here</p></td>
 </tr>
 </tbody>
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_survey_detail.png" alt="at survey detail" width="500">
+<img src="/workshops/ansible_automation/images/at_survey_detail.png" alt="at survey detail" width="500"/>
 </div>
 <div class="title">Figure 12: Survey Form</div>
 </div>
@@ -471,13 +471,13 @@ <h3 id="_step_6_add_the_survey_input">Step 6: Add the survey input</h3>
 <div class="sect2">
 <h3 id="_step_7_save">Step 7: Save</h3>
 <div class="paragraph">
-<p>Select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_8_save_at_the_main_page">Step 8: Save at the main page</h3>
 <div class="paragraph">
-<p>Back on the main Job Template page, select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span> again.</p>
+<p>Back on the main Job Template page, select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span> again.</p>
 </div>
 </div>
 </div>
@@ -486,7 +486,7 @@ <h3 id="_step_8_save_at_the_main_page">Step 8: Save at the main page</h3>
 <h2 id="_section_2_running_a_job_template">Section 2: Running a job template</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve sucessfully created your Job Template, you are ready to launch it.
+<p>Now that you’ve sucessfully created your Job Template, you are ready to launch it.
 You will be redirected to a job screen, which refreshes in realtime
 and displays the status of the job.</p>
 </div>
@@ -497,21 +497,21 @@ <h3 id="_step_1_select_the_template_tab">Step 1: Select the Template tab</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-Alternatively, if you haven&#8217;t navigated away from the job templates creation page, you can scroll down to see all existing job templates
+Alternatively, if you haven’t navigated away from the job templates creation page, you can scroll down to see all existing job templates
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_access_apache_basic_job_template">Step 2: Access Apache Basic Job Template</h3>
 <div class="paragraph">
-<p>Click the rocketship icon <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"></span> for the <strong>Apache Basic Job Template</strong></p>
+<p>Click the rocketship icon <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span> for the <strong>Apache Basic Job Template</strong></p>
 </div>
 </div>
 <div class="sect2">
@@ -521,7 +521,7 @@ <h3 id="_step_3_enter_test_message">Step 3: Enter test message</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_survey_prompt.png" alt="at survey prompt" width="800">
+<img src="/workshops/ansible_automation/images/at_survey_prompt.png" alt="at survey prompt" width="800"/>
 </div>
 <div class="title">Figure 13: Survey Prompt</div>
 </div>
@@ -529,7 +529,7 @@ <h3 id="_step_3_enter_test_message">Step 3: Enter test message</h3>
 <div class="sect2">
 <h3 id="_step_4_launch_the_job">Step 4: Launch the job</h3>
 <div class="paragraph">
-<p>Select LAUNCH <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"></span></p>
+<p>Select LAUNCH <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -538,11 +538,11 @@ <h3 id="_step_5_view_job_summary">Step 5: View job summary</h3>
 <p>Sit back, watch the magic happen</p>
 </div>
 <div class="paragraph">
-<p>One of the first things you will notice is the RESULTS section.  This section provides job details, such as who launched it, what playbook it&#8217;s running, what the status is, i.e. Pending, Running, or Complete.</p>
+<p>One of the first things you will notice is the RESULTS section.  This section provides job details, such as who launched it, what playbook it’s running, what the status is, i.e. Pending, Running, or Complete.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_job_status.png" alt="at job status">
+<img src="/workshops/ansible_automation/images/at_job_status.png" alt="at job status"/>
 </div>
 <div class="title">Figure 14: Job Summary</div>
 </div>
@@ -551,7 +551,7 @@ <h3 id="_step_5_view_job_summary">Step 5: View job summary</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_job_stdout.png" alt="at job stdout" width="900">
+<img src="/workshops/ansible_automation/images/at_job_stdout.png" alt="at job stdout" width="900"/>
 </div>
 <div class="title">Figure 16: Job Standard Output</div>
 </div>
@@ -571,7 +571,7 @@ <h3 id="_step_6_view_the_new_website">Step 6: View the new website</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_web_tm.png" alt="at web tm">
+<img src="/workshops/ansible_automation/images/at_web_tm.png" alt="at web tm"/>
 </div>
 <div class="title">Figure 17: New Website with Personalized Test Message</div>
 </div>
@@ -582,8 +582,8 @@ <h3 id="_step_6_view_the_new_website">Step 6: View the new website</h3>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point in the workshop, you&#8217;ve experienced the core functionality of Ansible Tower.  But wait&#8230;&#8203; there&#8217;s more!
-You&#8217;ve just begun to explore the possibilities of Ansible Core and Tower.  Take a look at the resources page in this guide, to explore some more features.</p>
+<p>At this point in the workshop, you’ve experienced the core functionality of Ansible Tower.  But wait…​ there’s more!
+You’ve just begun to explore the possibilities of Ansible Core and Tower.  Take a look at the resources page in this guide, to explore some more features.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -685,7 +685,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -945,7 +945,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1057,7 +1057,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1067,7 +1067,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1153,7 +1153,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/exercise3.0/index.html b/workshops/ansible_automation/exercise3.0/index.html
index 7fdde94df..d37e17692 100644
--- a/workshops/ansible_automation/exercise3.0/index.html
+++ b/workshops/ansible_automation/exercise3.0/index.html
@@ -326,7 +326,7 @@ <h3 id="_step_1_generate_a_security_profile_using_openscap">Step 1: Generate a s
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m package -a "name=scap-security-guide state=present" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m package -a &#34;name=scap-security-guide state=present&#34; -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -334,7 +334,7 @@ <h3 id="_step_1_generate_a_security_profile_using_openscap">Step 1: Generate a s
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m file -a "path=/var/lib/awx/projects/openscap-ospp state=directory mode=0755 owner=awx group=awx" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m file -a &#34;path=/var/lib/awx/projects/openscap-ospp state=directory mode=0755 owner=awx group=awx&#34; -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -351,13 +351,13 @@ <h3 id="_step_1_generate_a_security_profile_using_openscap">Step 1: Generate a s
 <div class="sect2">
 <h3 id="_step_2_select_projects">Step 2: Select Projects</h3>
 <div class="paragraph">
-<p>Click the Projects tab, in the Ansible Tower UI. <span class="image"><img src="/workshops/ansible_automation/images/at_projects_icon.png" alt="PROJECTS"></span></p>
+<p>Click the Projects tab, in the Ansible Tower UI. <span class="image"><img src="/workshops/ansible_automation/images/at_projects_icon.png" alt="PROJECTS"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_click_add">Step 3: Click Add</h3>
 <div class="paragraph">
-<p>Next, Select    <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Next, Select    <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -367,8 +367,8 @@ <h3 id="_step_4_complete_the_project_form">Step 4: Complete the Project form</h3
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -399,7 +399,7 @@ <h3 id="_step_4_complete_the_project_form">Step 4: Complete the Project form</h3
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/section3.0-ospp_project.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/section3.0-ospp_project.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 1: Defining a Project</div>
 </div>
@@ -407,7 +407,7 @@ <h3 id="_step_4_complete_the_project_form">Step 4: Complete the Project form</h3
 <div class="sect2">
 <h3 id="_step_5_save">Step 5: Save</h3>
 <div class="paragraph">
-<p>Select   SAVE   <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select   SAVE   <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -419,7 +419,7 @@ <h3 id="_step_6_select_template_tab">Step 6: Select Template tab</h3>
 <div class="sect2">
 <h3 id="_step_7_add_the_job_template">Step 7: Add the job template</h3>
 <div class="paragraph">
-<p>Click ADD <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span>, and select <code>JOB TEMPLATE</code></p>
+<p>Click ADD <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span>, and select <code>JOB TEMPLATE</code></p>
 </div>
 </div>
 <div class="sect2">
@@ -429,8 +429,8 @@ <h3 id="_step_8_complete_the_job_template_form">Step 8: Complete the job Templat
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -479,7 +479,7 @@ <h3 id="_step_8_complete_the_job_template_form">Step 8: Complete the job Templat
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/section3.0-ospp_template.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_automation/images/section3.0-ospp_template.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 2: Defining a Job</div>
 </div>
@@ -487,10 +487,10 @@ <h3 id="_step_8_complete_the_job_template_form">Step 8: Complete the job Templat
 <div class="sect2">
 <h3 id="_step_9_save_the_template_and_run_it">Step 9: Save the template and run it</h3>
 <div class="paragraph">
-<p>Click SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save"></span>, to store your new template, and we are ready to run it.</p>
+<p>Click SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save"/></span>, to store your new template, and we are ready to run it.</p>
 </div>
 <div class="paragraph">
-<p>Click  the rocketship icon <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"></span> next to the <code>RHEL8 OSPP Job Template</code> entry, to launch the job.</p>
+<p>Click  the rocketship icon <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span> next to the <code>RHEL8 OSPP Job Template</code> entry, to launch the job.</p>
 </div>
 <div class="paragraph">
 <p>View what the job looks like as it is executing, as well as what the SCAP results look like, when uploaded to your second node, in the panel, below.</p>
@@ -503,18 +503,18 @@ <h3 id="_step_9_save_the_template_and_run_it">Step 9: Save the template and run
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse6152164e7541085af0104573b505679b" class="collapsed">
+      <a data-toggle="collapse" href="#collapse3c6d32c746eb1a9d445c53f098f0d983" class="collapsed">
       
         Job Status
       </a>
     </h4>
   </div>
   
-  <div id="collapse6152164e7541085af0104573b505679b" class="panel-collapse collapse ">
+  <div id="collapse3c6d32c746eb1a9d445c53f098f0d983" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
-<p><span class="image"><img src="/workshops/ansible_automation/images/section3.0-ospp_job_status.png" alt="Job Status" width="1024"></span></p>
+<p><span class="image"><img src="/workshops/ansible_automation/images/section3.0-ospp_job_status.png" alt="Job Status" width="1024"/></span></p>
 </div>
 
     </div>
@@ -625,7 +625,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -885,7 +885,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -997,7 +997,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1007,7 +1007,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1090,7 +1090,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/index.html b/workshops/ansible_automation/index.html
index a1d0bba5e..acea151b9 100644
--- a/workshops/ansible_automation/index.html
+++ b/workshops/ansible_automation/index.html
@@ -535,7 +535,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -795,7 +795,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -907,7 +907,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -917,7 +917,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -970,7 +970,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/index.xml b/workshops/ansible_automation/index.xml
index b7f7897ad..01bf26c57 100644
--- a/workshops/ansible_automation/index.xml
+++ b/workshops/ansible_automation/index.xml
@@ -4,131 +4,85 @@
     <title>Ansible Automation Workshop on Red Hat | Public Sector</title>
     <link>/workshops/ansible_automation/</link>
     <description>Recent content in Ansible Automation Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/ansible_automation/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/ansible_automation/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Running Ad hoc commands</title>
       <link>/workshops/ansible_automation/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.0/</guid>
       <description>Exercise Description For our first exercise, we are going to run some ad hoc commands to help you get a feel for how Red Hat Ansible Automation works. Ansible ad hoc commands enable you to perform repeatable tasks on local or remote nodes, without having to write a playbook. They are very useful when you simply need to do one or two tasks quickly and often, to many remote nodes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Writing Your First Playbook</title>
       <link>/workshops/ansible_automation/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.1/</guid>
-      <description>Exercise Description Now that you&amp;#8217;ve gotten a sense of how Red Hat Ansible Tower works, we are going to write our first Ansible playbook. The playbook is where you can take some of those ad hoc commands you just ran and put them into a repeatable set of plays and tasks.
- A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
+      <description>Exercise Description Now that you’ve gotten a sense of how Red Hat Ansible Tower works, we are going to write our first Ansible playbook. The playbook is where you can take some of those ad hoc commands you just ran and put them into a repeatable set of plays and tasks.&#xA;A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Running Your Playbook</title>
       <link>/workshops/ansible_automation/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.2/</guid>
-      <description>Section 1: Running the playbook We are now going to run your brand-new playbook, on your two web nodes. To do this, you are going to use the ansible-playbook command.
- Step 1: Check your playbook However, before you run the playbook, lets take a few moments to understand the options.
-   install_apache.yml This is the name of the playbook that we are running.
-  -v Altough not used here, this increases verbosity.</description>
+      <description>Section 1: Running the playbook We are now going to run your brand-new playbook, on your two web nodes. To do this, you are going to use the ansible-playbook command.&#xA;Step 1: Check your playbook However, before you run the playbook, lets take a few moments to understand the options.&#xA;install_apache.yml This is the name of the playbook that we are running.&#xA;-v Altough not used here, this increases verbosity.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Using Variables, Loops, and Handlers</title>
       <link>/workshops/ansible_automation/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.3/</guid>
-      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.
- Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
+      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.&#xA;Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Running the apache-basic-playbook</title>
       <link>/workshops/ansible_automation/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.4/</guid>
-      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let&amp;#8217;s do that now.
-   Section 1: Running your new apache playbook Step 1: Run your playbook Run your playbook, using the following command.
- cd ~/apache-basic-playbook ansible-playbook site.yml      Section 2: Review If successful, you should see standard output that looks very similar to the following.</description>
+      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let’s do that now.&#xA;Section 1: Running your new apache playbook Step 1: Run your playbook Run your playbook, using the following command.&#xA;cd ~/apache-basic-playbook ansible-playbook site.yml Section 2: Review If successful, you should see standard output that looks very similar to the following.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Roles: Making your playbooks reusable</title>
       <link>/workshops/ansible_automation/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise1.5/</guid>
-      <description>Exercise Description While it is possible to write a playbook in one file, as we&amp;#8217;ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.
- The &#34;role&#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
+      <description>Exercise Description While it is possible to write a playbook in one file, as we’ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.&#xA;The &amp;#34;role&amp;#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &amp;#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Installing Ansible Tower</title>
       <link>/workshops/ansible_automation/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise2.0/</guid>
-      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node.
- Step 1: Change directories Change directories to /tmp
- cd /tmp    Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package
- curl -O https://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-3.7.3-1.tar.gz    Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-3.7.3-1.tar.gz    Step 4: Change directories Change directories into the Ansible Tower setup package</description>
+      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node.&#xA;Step 1: Change directories Change directories to /tmp&#xA;cd /tmp Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package&#xA;curl -O https://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-3.7.3-1.tar.gz Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-3.7.3-1.tar.gz Step 4: Change directories Change directories into the Ansible Tower setup package&#xA;cd /tmp/ansible-tower-setup-*/ Step 5: Open inventory file Using an editor of your choice, open the inventory file</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Configuring Ansible Tower</title>
       <link>/workshops/ansible_automation/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise2.1/</guid>
-      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.
- There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.
-   Credentials
-  Projects
-  Inventory
-  Job Template
-     Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password ansibleWS.</description>
+      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.&#xA;There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.&#xA;Credentials&#xA;Projects&#xA;Inventory&#xA;Job Template&#xA;Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password ansibleWS.</description>
     </item>
-    
     <item>
       <title>Exercise 2.2 - Creating and Running a Job Template</title>
       <link>/workshops/ansible_automation/exercise2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise2.2/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.
- Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.&#xA;Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
     </item>
-    
     <item>
       <title>Exercise 3.0 - Using Ansible to Implement Security</title>
       <link>/workshops/ansible_automation/exercise3.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/exercise3.0/</guid>
-      <description>Exercise Description In this exercise, we are going to use Red Hat Ansible Tower to run a Operating System Protection Profile (OSPP) for RHEL 8.x for our environment
- Step 1: Generate a security profile using OpenSCAP. In your Web Console Terminal window (if you closed it, see the SETUP step, in your workbook), install OpenScap on the Tower node:
- ansible localhost -m package -a &#34;name=scap-security-guide state=present&#34; -b   Next, setup a local projects directory to stage a remediation playbook</description>
+      <description>Exercise Description In this exercise, we are going to use Red Hat Ansible Tower to run a Operating System Protection Profile (OSPP) for RHEL 8.x for our environment&#xA;Step 1: Generate a security profile using OpenSCAP. In your Web Console Terminal window (if you closed it, see the SETUP step, in your workbook), install OpenScap on the Tower node:&#xA;ansible localhost -m package -a &amp;#34;name=scap-security-guide state=present&amp;#34; -b Next, setup a local projects directory to stage a remediation playbook</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/ansible_automation/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/ansible_automation/setup/index.html b/workshops/ansible_automation/setup/index.html
index d3a5295a6..029faeee2 100644
--- a/workshops/ansible_automation/setup/index.html
+++ b/workshops/ansible_automation/setup/index.html
@@ -317,7 +317,7 @@ <h1>Setup</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/tower.002.png" alt="Tower">
+<img src="/workshops/ansible_automation/images/tower.002.png" alt="Tower"/>
 </div>
 </div>
 </div>
@@ -346,7 +346,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/cockpit_login.png" alt="cockpit login" height="500">
+<img src="/workshops/ansible_automation/images/cockpit_login.png" alt="cockpit login" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Login</div>
 </div>
@@ -355,21 +355,21 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/cockpit_terminal.png" alt="cockpit terminal" height="500">
+<img src="/workshops/ansible_automation/images/cockpit_terminal.png" alt="cockpit terminal" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Terminal Tab</div>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-Be sure you can log in to your instances.  If you can&#8217;t log in start shouting, loudly, and waving your hands!
+Be sure you can log in to your instances.  If you can’t log in start shouting, loudly, and waving your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -377,7 +377,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -479,7 +479,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -739,7 +739,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -851,7 +851,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -861,7 +861,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -943,7 +943,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_automation/wrapup/index.html b/workshops/ansible_automation/wrapup/index.html
index 7fec12019..f381b78fb 100644
--- a/workshops/ansible_automation/wrapup/index.html
+++ b/workshops/ansible_automation/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrapup</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something valuable
+<p>That wraps up what we have planned for today.  We hope you’ve learned something valuable
 about Ansible and Red Hat Ansible Tower that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
@@ -331,7 +331,7 @@ <h1>Wrapup</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_ansible/images/redhat.svg" alt="redhat">
+<img src="/workshops/ansible_ansible/images/redhat.svg" alt="redhat"/>
 </div>
 </div>
 
@@ -369,7 +369,7 @@ <h1>Wrapup</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise1.0/index.html b/workshops/ansible_tower_azure/exercise1.0/index.html
index ab4a4642f..2f6ff7a2a 100644
--- a/workshops/ansible_tower_azure/exercise1.0/index.html
+++ b/workshops/ansible_tower_azure/exercise1.0/index.html
@@ -332,7 +332,7 @@ <h3 id="_set_up_dependencies">Set Up Dependencies:</h3>
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -340,10 +340,10 @@ <h3 id="_set_up_dependencies">Set Up Dependencies:</h3>
 The <strong>workshopname</strong>, in the example below, will be provided to you by your instructor.  The <strong>#</strong> should be replaced by your student number.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
-<p>For example, a recent workshop&#8217;s first student used:
+<p>For example, a recent workshop’s first student used:
 <strong><span class=prefix>example</span>-tower<span class=userid>0</span>.<span class=region>example</span>.<span class=domain>redhatgov.io</span></strong></p>
 </div>
 </div>
@@ -359,7 +359,7 @@ <h3 id="_set_up_dependencies">Set Up Dependencies:</h3>
 <div class="sect2">
 <h3 id="_step_1_test_webhost_response">Step 1: Test webhost response</h3>
 <div class="paragraph">
-<p>Let&#8217;s start with something basic - pinging a host.  The <code>ping</code> module tests the responsiveness of our web host.</p>
+<p>Let’s start with something basic - pinging a host.  The <code>ping</code> module tests the responsiveness of our web host.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -370,18 +370,18 @@ <h3 id="_step_1_test_webhost_response">Step 1: Test webhost response</h3>
 <div class="sect2">
 <h3 id="_step_2_run_a_linux_command">Step 2: Run a Linux command</h3>
 <div class="paragraph">
-<p>Now let&#8217;s see how we can run a Linux command and format the output, using the <code>command</code> module.</p>
+<p>Now let’s see how we can run a Linux command and format the output, using the <code>command</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m command -a "uptime" -o</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m command -a &#34;uptime&#34; -o</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="paragraph">
-<p>Take a look at your web node&#8217;s configuration.  The <code>setup</code> module displays Ansible facts (and a lot of them) about an endpoint.</p>
+<p>Take a look at your web node’s configuration.  The <code>setup</code> module displays Ansible facts (and a lot of them) about an endpoint.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -392,12 +392,12 @@ <h3 id="_step_3_review_the_setup_module">Step 3: Review the setup module</h3>
 <div class="sect2">
 <h3 id="_step_4_install_maven_and_git">Step 4: Install Maven and Git</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s install Maven &amp; Git using the <code>package</code> module.</p>
+<p>Now, let’s install Maven &amp; Git using the <code>package</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m package -a "name=rh-maven35 state=present" -b
-ansible web -m package -a "name=git state=present" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m package -a &#34;name=rh-maven35 state=present&#34; -b
+ansible web -m package -a &#34;name=git state=present&#34; -b</code></pre>
 </div>
 </div>
 </div>
@@ -408,32 +408,32 @@ <h3 id="_step_5install_a_group_of_packages">Step 5:Install a group of packages</
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m package -a "name=@jboss-eap7 state=present" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m package -a &#34;name=@jboss-eap7 state=present&#34; -b</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_6_start_jboss_eap">Step 6: Start JBoss EAP</h3>
 <div class="paragraph">
-<p>JBoss EAP is installed now, so let&#8217;s start it up using the <code>service</code> module.</p>
+<p>JBoss EAP is installed now, so let’s start it up using the <code>service</code> module.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a "name=eap7-standalone state=started" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a &#34;name=eap7-standalone state=started&#34; -b</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_7_deploy_an_application">Step 7: Deploy an application</h3>
 <div class="paragraph">
-<p>Next, let&#8217;s deploy an application.</p>
+<p>Next, let’s deploy an application.</p>
 </div>
 <div class="paragraph">
-<p>For simplicity sake, we will use an existing quickstart. To get started, we will checkout some code &#8230;&#8203;</p>
+<p>For simplicity sake, we will use an existing quickstart. To get started, we will checkout some code …​</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m git -a "repo=https://github.com/jboss-developer/jboss-eap-quickstarts.git dest=/tmp/checkout"</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m git -a &#34;repo=https://github.com/jboss-developer/jboss-eap-quickstarts.git dest=/tmp/checkout&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -441,7 +441,7 @@ <h3 id="_step_7_deploy_an_application">Step 7: Deploy an application</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m shell -a "scl enable rh-maven35 'mvn clean install wildfly:deploy -Dmaven.test.skip=true' chdir=/tmp/checkout/helloworld" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m shell -a &#34;scl enable rh-maven35 &#39;mvn clean install wildfly:deploy -Dmaven.test.skip=true&#39; chdir=/tmp/checkout/helloworld&#34; -b</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -449,7 +449,7 @@ <h3 id="_step_7_deploy_an_application">Step 7: Deploy an application</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m uri -a "url=http://localhost:8080/helloworld/ return_content=yes"</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m uri -a &#34;url=http://localhost:8080/helloworld/ return_content=yes&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -464,11 +464,11 @@ <h3 id="_step_7_deploy_an_application">Step 7: Deploy an application</h3>
 <div class="sect2">
 <h3 id="_step_8_cleanup">Step 8: Cleanup</h3>
 <div class="paragraph">
-<p>Finally, let&#8217;s clean up after ourselves.  First, stop the Red Hat JBoss EAP service, using the following command.</p>
+<p>Finally, let’s clean up after ourselves.  First, stop the Red Hat JBoss EAP service, using the following command.</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a "name=eap7-standalone state=stopped" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m service -a &#34;name=eap7-standalone state=stopped&#34; -b</code></pre>
 </div>
 </div>
 </div>
@@ -479,17 +479,17 @@ <h3 id="_step_9_remove_packages">Step 9: Remove packages</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m package -a "name=@jboss-eap7 state=absent" -b
-ansible web -m package -a "name=eap7-* state=absent" -b
-ansible web -m package -a "name=rh-maven35 state=absent" -b
-ansible web -m package -a "name=git state=absent" -b</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible web -m package -a &#34;name=@jboss-eap7 state=absent&#34; -b
+ansible web -m package -a &#34;name=eap7-* state=absent&#34; -b
+ansible web -m package -a &#34;name=rh-maven35 state=absent&#34; -b
+ansible web -m package -a &#34;name=git state=absent&#34; -b</code></pre>
 </div>
 </div>
 <div class="exampleblock">
 <div class="content">
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -497,7 +497,7 @@ <h3 id="_step_9_remove_packages">Step 9: Remove packages</h3>
 Like many Linux commands, <code>ansible</code> allows for long-form options as well as short-form.  For example:
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -709,7 +709,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -771,7 +771,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise1.1/index.html b/workshops/ansible_tower_azure/exercise1.1/index.html
index 509d8bf75..9e6271335 100644
--- a/workshops/ansible_tower_azure/exercise1.1/index.html
+++ b/workshops/ansible_tower_azure/exercise1.1/index.html
@@ -320,7 +320,7 @@ <h1>Exercise 1.1 - Writing Your First playbook</h1>
     <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve gotten a sense of how ansible works, we are going to write our first
+<p>Now that you’ve gotten a sense of how ansible works, we are going to write our first
 ansible <strong>playbook</strong>.  The playbook is where you can take some of those ad-hoc commands you just ran
 and put them into a repeatable set of <strong>plays</strong> and <strong>tasks</strong>.</p>
 </div>
@@ -363,7 +363,7 @@ <h3 id="_step_2_use_vi_or_vim_to_open_a_file_called_install_apache_yml">Step 2:
 <h2 id="_section_2_defining_your_play">Section 2: Defining Your Play</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you are editing <code>install_apache.yml</code>, let&#8217;s begin by defining the play and then understanding what each line accomplishes</p>
+<p>Now that you are editing <code>install_apache.yml</code>, let’s begin by defining the play and then understanding what each line accomplishes</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -395,8 +395,8 @@ <h2 id="_section_2_defining_your_play">Section 2: Defining Your Play</h2>
 <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding Tasks to Your Play</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that we&#8217;ve defined your play, let&#8217;s add some tasks to get some things done.  Align (vertically) the <strong>t</strong> in <code>task</code> with the <strong>b</strong> <code>become</code>. <br>
-Yes, it does actually matter.  In fact, you should make sure all of your playbook statements are aligned in the way shown here.<br>
+<p>Now that we’ve defined your play, let’s add some tasks to get some things done.  Align (vertically) the <strong>t</strong> in <code>task</code> with the <strong>b</strong> <code>become</code>. <br/>
+Yes, it does actually matter.  In fact, you should make sure all of your playbook statements are aligned in the way shown here.<br/>
 If you want to see the entire playbook for reference, skip to the bottom of this exercise.</p>
 </div>
 <div class="listingblock">
@@ -461,7 +461,7 @@ <h2 id="_section_3_adding_tasks_to_your_play">Section 3: Adding Tasks to Your Pl
 <h2 id="_section_4_saving_your_playbook">Section 4: Saving your Playbook</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve completed writing your playbook, it would be a shame not to keep it.</p>
+<p>Now that you’ve completed writing your playbook, it would be a shame not to keep it.</p>
 </div>
 <div class="paragraph">
 <p>Use the <code>write/quit</code> method in <code>vi</code> or <code>vim</code> to save your playbook, i.e. <code>Esc :wq!</code></p>
@@ -472,7 +472,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your Playbook</h2>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -482,7 +482,7 @@ <h2 id="_section_4_saving_your_playbook">Section 4: Saving your Playbook</h2>
 like this.  Take note of the spacing and alignment.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -695,7 +695,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -756,7 +756,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise1.2/index.html b/workshops/ansible_tower_azure/exercise1.2/index.html
index 2296a0433..c8d5e5ca7 100644
--- a/workshops/ansible_tower_azure/exercise1.2/index.html
+++ b/workshops/ansible_tower_azure/exercise1.2/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.2 - Running Your Playbook</h1>
 <h2 id="_section_1_running_the_playbook">Section 1: Running the Playbook</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>We are now going to run your brand spankin' new playbook on your two web nodes.  To do this,
+<p>We are now going to run your brand spankin&#39; new playbook on your two web nodes.  To do this,
  you are going to use the <code>ansible-playbook</code> command.</p>
 </div>
 <div class="sect2">
@@ -353,7 +353,7 @@ <h3 id="_step_1_run_your_playbook">Step 1: Run your playbook</h3>
 <div class="ulist NOTE">
 <ul class="NOTE">
 <li>
-<p><strong>--syntax-check</strong> If you run into any issues with your playbook running properly; you know, from that copy/pasting that you didn&#8217;t do because we said "<em>don&#8217;t do that</em>"; you could use this option to help find those issues like so&#8230;&#8203;</p>
+<p><strong>--syntax-check</strong> If you run into any issues with your playbook running properly; you know, from that copy/pasting that you didn’t do because we said &#34;<em>don’t do that</em>&#34;; you could use this option to help find those issues like so…​</p>
 </li>
 </ul>
 </div>
@@ -362,7 +362,7 @@ <h3 id="_step_1_run_your_playbook">Step 1: Run your playbook</h3>
 <pre class="highlight"><code class="language-bash" data-lang="bash">ansible-playbook -i ../hosts install_apache.yml --syntax-check --private-key=~/.ssh/<span class="prefix">example</span>-tower</code></pre>
 </div>
 </div>
-<hr>
+<hr/>
 <div class="paragraph">
 <p>Now, run your playbook as specified in <strong>Step 1</strong></p>
 </div>
@@ -371,13 +371,13 @@ <h3 id="_step_1_run_your_playbook">Step 1: Run your playbook</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/stdout_1.png" alt="stdout 1" height="328">
+<img src="/workshops/ansible_tower_azure/images/stdout_1.png" alt="stdout 1" height="328"/>
 </div>
 <div class="title">Figure 1: apache_basic playbook stdout</div>
 </div>
 <div class="paragraph">
 <p>Notice that the play and each task is named, so that you can understand the action being performed and the node it is being performed upon.
-You also may notice a task in there that you didn&#8217;t write;  &lt;cough&gt; <code>setup</code> &lt;cough&gt;.  This is because the <code>setup</code> module
+You also may notice a task in there that you didn’t write;  &lt;cough&gt; <code>setup</code> &lt;cough&gt;.  This is because the <code>setup</code> module
 runs by default.  To turn if off, you can specify <a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html#turning-off-facts">gather_facts: false</a> in your play definition like this:</p>
 </div>
 <div class="listingblock">
@@ -393,10 +393,10 @@ <h3 id="_step_1_run_your_playbook">Step 1: Run your playbook</h3>
 <div class="sect2">
 <h3 id="_step_2_remove_apache">Step 2: Remove Apache</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s experiment a little.
-We would like you to reverse what you&#8217;ve done (i.e. stop and uninstall apache on your web nodes).
-So, edit your playbook and then when you&#8217;re finished, rerun it - as described in <strong>Step 1</strong>.
-For this exercise we aren&#8217;t going to show you line by line, but we will give you a few hints.</p>
+<p>Now, let’s experiment a little.
+We would like you to reverse what you’ve done (i.e. stop and uninstall apache on your web nodes).
+So, edit your playbook and then when you’re finished, rerun it - as described in <strong>Step 1</strong>.
+For this exercise we aren’t going to show you line by line, but we will give you a few hints.</p>
 </div>
 <div class="ulist NOTE">
 <ul class="NOTE">
@@ -408,7 +408,7 @@ <h3 id="_step_2_remove_apache">Step 2: Remove Apache</h3>
 <p>If <code>started</code> makes sure a service is started, then what option ensures it is stopped?</p>
 </li>
 <li>
-<p>If <code>present</code> makes sure a package is installed, then what option ensures it is removed?  Er&#8230;&#8203; starts with an <strong>ab</strong>, ends with a <strong>sent</strong></p>
+<p>If <code>present</code> makes sure a package is installed, then what option ensures it is removed?  Er…​ starts with an <strong>ab</strong>, ends with a <strong>sent</strong></p>
 </li>
 </ul>
 </div>
@@ -617,7 +617,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -679,7 +679,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise1.3/index.html b/workshops/ansible_tower_azure/exercise1.3/index.html
index 0c8e91313..6a875f729 100644
--- a/workshops/ansible_tower_azure/exercise1.3/index.html
+++ b/workshops/ansible_tower_azure/exercise1.3/index.html
@@ -341,9 +341,9 @@ <h2 id="_exercise_description">Exercise Description</h2>
 If so, you may need to restart a service, for those changes to take effect.  We do that with a handler.</p>
 </div>
 <div class="paragraph">
-<p>For a full understanding of variables, loops, and handlers; check out our Ansible documentation on these subjects.<br>
-<a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html">Ansible Variables</a><br>
-<a href="http://docs.ansible.com/ansible/latest/playbooks_loops.html">Ansible Loops</a><br>
+<p>For a full understanding of variables, loops, and handlers; check out our Ansible documentation on these subjects.<br/>
+<a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html">Ansible Variables</a><br/>
+<a href="http://docs.ansible.com/ansible/latest/playbooks_loops.html">Ansible Loops</a><br/>
 <a href="http://docs.ansible.com/ansible/latest/playbooks_intro.html#handlers-running-operations-on-change">Ansible Handlers</a></p>
 </div>
 </div>
@@ -355,7 +355,7 @@ <h2 id="_section_1_running_the_playbook">Section 1: Running the Playbook</h2>
 <p>To begin, we are going to create a new playbook, but it should look very familiar to the one you created in exercise 1.2</p>
 </div>
 <div class="paragraph">
-<p>We are now going to run you&#8217;re brand spankin' new playbook on your web node.  To do this, you are going to use the <code>ansible-playbook</code> command.</p>
+<p>We are now going to run you’re brand spankin&#39; new playbook on your web node.  To do this, you are going to use the <code>ansible-playbook</code> command.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1create_a_new_project_and_playbook">Step 1:Create a new project and playbook</h3>
@@ -401,46 +401,46 @@ <h3 id="_step_3_add_a_task">Step 3: Add a task</h3>
 <pre class="highlight"><code class="language-bash" data-lang="bash">  tasks:
     - name: install httpd packages
       package:
-        name: "{{ item }}"
+        name: &#34;{{ item }}&#34;
         state: present
-      with_items: "{{ httpd_packages }}"
+      with_items: &#34;{{ httpd_packages }}&#34;
       notify: restart apache service</code></pre>
 </div>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>Explanation of the <strong>install httpd packages</strong> task actions.<br></p>
+<p>Explanation of the <strong>install httpd packages</strong> task actions.<br/></p>
 </div>
 <div class="ulist">
 <ul>
 <li>
-<p><code>vars:</code> You&#8217;ve told Ansible the next thing it sees will be a variable name<br></p>
+<p><code>vars:</code> You’ve told Ansible the next thing it sees will be a variable name<br/></p>
 </li>
 <li>
 <p><code>httpd_packages</code> You are defining a list-type variable called httpd_packages.  What follows
-is a list of those packages<br></p>
+is a list of those packages<br/></p>
 </li>
 <li>
-<p><code>{{ item }}</code> You are telling Ansible that this will expand into a list item like <code>httpd</code> and <code>mod_wsgi</code>.<br></p>
+<p><code>{{ item }}</code> You are telling Ansible that this will expand into a list item like <code>httpd</code> and <code>mod_wsgi</code>.<br/></p>
 </li>
 <li>
-<p><code>with_items: "{{ httpd_packages }}</code> This is your loop which is instructing Ansible to perform this task on
+<p><code>with_items: &#34;{{ httpd_packages }}</code> This is your loop which is instructing Ansible to perform this task on
 every <code>item</code> in <code>httpd_packages</code></p>
 </li>
 <li>
-<p><code>notify: restart apache service</code> This statement is a <code>handler</code>, so we&#8217;ll come back to it in Section 3.</p>
+<p><code>notify: restart apache service</code> This statement is a <code>handler</code>, so we’ll come back to it in Section 3.</p>
 </li>
 </ul>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -449,7 +449,7 @@ <h3 id="_step_3_add_a_task">Step 3: Add a task</h3>
 <h2 id="_section_2_deploying_files_and_starting_a_service">Section 2: Deploying files and starting a service</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>When you need to do pretty much anything with files and directories, use one of the <a href="http://docs.ansible.com/ansible/latest/list_of_files_modules.html">Ansible Files</a> modules.  In this case, we&#8217;ll leverage the <code>file</code> and <code>template</code> modules.</p>
+<p>When you need to do pretty much anything with files and directories, use one of the <a href="http://docs.ansible.com/ansible/latest/list_of_files_modules.html">Ansible Files</a> modules.  In this case, we’ll leverage the <code>file</code> and <code>template</code> modules.</p>
 </div>
 <div class="paragraph">
 <p>After that, you will define a task to start the start the apache service.</p>
@@ -500,7 +500,7 @@ <h3 id="_step_2_add_file_and_service_tasks">Step 2: Add file and service tasks</
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -518,7 +518,7 @@ <h3 id="_step_2_add_file_and_service_tasks">Step 2: Add file and service tasks</
 module family and we encourage you to check out all of the other <a href="http://docs.ansible.com/ansible/latest/list_of_files_modules.html">file-management modules here</a>.</p>
 </li>
 <li>
-<p><strong>jinja-who?</strong> - Not to be confused with 2013&#8217;s blockbuster "Ninja II - Shadow of a Tear", <a href="http://docs.ansible.com/ansible/latest/playbooks_templating.html">jinja2</a> is
+<p><strong>jinja-who?</strong> - Not to be confused with 2013’s blockbuster &#34;Ninja II - Shadow of a Tear&#34;, <a href="http://docs.ansible.com/ansible/latest/playbooks_templating.html">jinja2</a> is
 used in Ansible to transform data inside a template expression, i.e. filters.</p>
 </li>
 <li>
@@ -528,7 +528,7 @@ <h3 id="_step_2_add_file_and_service_tasks">Step 2: Add file and service tasks</
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -556,7 +556,7 @@ <h3 id="_step_1_define_a_handler">Step 1: Define a handler</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -572,28 +572,28 @@ <h3 id="_step_1_define_a_handler">Step 1: Define a handler</h3>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_calling_the_handlers">Step 2: Calling the handlers</h3>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-You can&#8217;t have a former if you don&#8217;t mention the latter
+You can’t have a former if you don’t mention the latter
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="ulist">
 <ul>
 <li>
-<p><code>notify: restart apache service</code> &#8230;&#8203;and here is your latter. Finally!  The <code>notify</code> statement is the invocation of a handler by
-name.  Quite the reveal, we know.   You already noticed that you&#8217;ve added a <code>notify</code> statement to the <code>copy httpd.conf</code>
+<p><code>notify: restart apache service</code> …​and here is your latter. Finally!  The <code>notify</code> statement is the invocation of a handler by
+name.  Quite the reveal, we know.   You already noticed that you’ve added a <code>notify</code> statement to the <code>copy httpd.conf</code>
 task, now you know why.
 ===</p>
 </li>
@@ -606,7 +606,7 @@ <h3 id="_step_2_calling_the_handlers">Step 2: Calling the handlers</h3>
 <h2 id="_section_4_review">Section 4: Review</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Your new, improved playbook is done! But don&#8217;t run it just yet, we&#8217;ll do that in our next exercise.  For now, let&#8217;s take a second look to make sure everything
+<p>Your new, improved playbook is done! But don’t run it just yet, we’ll do that in our next exercise.  For now, let’s take a second look to make sure everything
 looks the way you intended.  If not, now is the time to fix it up. The figure below shows line counts and spacing.</p>
 </div>
 <div class="listingblock">
@@ -625,9 +625,9 @@ <h2 id="_section_4_review">Section 4: Review</h2>
   tasks:
     - name: httpd packages are present
       package:
-        name: "{{ item }}"
+        name: &#34;{{ item }}&#34;
         state: present
-      with_items: "{{ httpd_packages }}"
+      with_items: &#34;{{ httpd_packages }}&#34;
       notify: restart apache service
 
     - name: site-enabled directory is present
@@ -852,7 +852,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -913,7 +913,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise1.4/index.html b/workshops/ansible_tower_azure/exercise1.4/index.html
index 42df4614d..72f423184 100644
--- a/workshops/ansible_tower_azure/exercise1.4/index.html
+++ b/workshops/ansible_tower_azure/exercise1.4/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.4 - Running the apache-basic-playbook</h1>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Congratulations!  You just wrote a playbook that incorporates some key Ansible concepts that you use in
-most, if not all, of your future playbooks.  Before you get too excited though, we should probably make sure it actually runs. So, let&#8217;s do that now.</p>
+most, if not all, of your future playbooks.  Before you get too excited though, we should probably make sure it actually runs. So, let’s do that now.</p>
 </div>
 </div>
 </div>
@@ -340,7 +340,7 @@ <h3 id="_step_1_create_a_host_file">Step 1: Create a host file</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -348,7 +348,7 @@ <h3 id="_step_1_create_a_host_file">Step 1: Create a host file</h3>
 Since you already did the work of creating a host file in Lession 1.0, feel free to re-use it.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -369,11 +369,11 @@ <h2 id="_section_2_review">Section 2: Review</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>If successful, you should see standard output that looks very similar to the following.  If not, just let us
-know.  We&#8217;ll help get things fixed up.</p>
+know.  We’ll help get things fixed up.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/stdout_2.png" alt="stdout 2">
+<img src="/workshops/ansible_tower_azure/images/stdout_2.png" alt="stdout 2"/>
 </div>
 <div class="title">Figure 1: apache-basic-playbook stdout</div>
 </div>
@@ -569,7 +569,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -630,7 +630,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise1.5/index.html b/workshops/ansible_tower_azure/exercise1.5/index.html
index 835e3cde7..abaf56caf 100644
--- a/workshops/ansible_tower_azure/exercise1.5/index.html
+++ b/workshops/ansible_tower_azure/exercise1.5/index.html
@@ -321,24 +321,24 @@ <h1>Exercise 1.5 - Roles: Making your playbooks reusable</h1>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>While it is possible to write a playbook in one file as we&#8217;ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.</p>
+<p>While it is possible to write a playbook in one file as we’ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.</p>
 </div>
 <div class="paragraph">
-<p>The "role" feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure.  <em>"Wha??  You mean that seemingly useless <a href="http://docs.ansible.com/ansible/playbooks_best_practices.html">best practice</a> you mentioned in exercise 1.2?".</em>  Yep, that one.</p>
+<p>The &#34;role&#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure.  <em>&#34;Wha??  You mean that seemingly useless <a href="http://docs.ansible.com/ansible/playbooks_best_practices.html">best practice</a> you mentioned in exercise 1.2?&#34;.</em>  Yep, that one.</p>
 </div>
 <div class="paragraph">
-<p>For this exercise, you are going to take the playbook you just wrote and refactor it into a role.  In addition, you&#8217;ll learn to use Ansible Galaxy.</p>
+<p>For this exercise, you are going to take the playbook you just wrote and refactor it into a role.  In addition, you’ll learn to use Ansible Galaxy.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s begin with seeing how your apache-basic-playbook will break down into a role.</p>
+<p>Let’s begin with seeing how your apache-basic-playbook will break down into a role.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/roledir_1.png" alt="apache-basic-playbook role directory structure">
+<img src="/workshops/ansible_tower_azure/images/roledir_1.png" alt="apache-basic-playbook role directory structure"/>
 </div>
 </div>
 <div class="paragraph">
-<p>Fortunately, you don&#8217;t have to create all of these directories and files by hand.  That&#8217;s where Ansible Galaxy comes in.</p>
+<p>Fortunately, you don’t have to create all of these directories and files by hand.  That’s where Ansible Galaxy comes in.</p>
 </div>
 </div>
 </div>
@@ -346,7 +346,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_using_ansible_galaxy_to_initialize_a_new_role">Section 1: Using Ansible Galaxy to initialize a new role</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Ansible Galaxy is a free site for finding, downloading, and sharing roles.  It&#8217;s also pretty handy for creating them which is what we are about to do here.</p>
+<p>Ansible Galaxy is a free site for finding, downloading, and sharing roles.  It’s also pretty handy for creating them which is what we are about to do here.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1_navigate_to_your_project">Step 1: Navigate to your project</h3>
@@ -382,7 +382,7 @@ <h3 id="_step_3_initialize_new_role">Step 3: Initialize new role</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Take a look around the structure you just created.  It should look a lot like Figure 1 above.  However, we need to complete one more step before moving onto section 2.  It is Ansible best practice to clean out role directories and files you won&#8217;t be using.  For this role, we won&#8217;t be using anything from <code>files</code>, <code>tests</code>.</p>
+<p>Take a look around the structure you just created.  It should look a lot like Figure 1 above.  However, we need to complete one more step before moving onto section 2.  It is Ansible best practice to clean out role directories and files you won’t be using.  For this role, we won’t be using anything from <code>files</code>, <code>tests</code>.</p>
 </div>
 </div>
 <div class="sect2">
@@ -465,16 +465,16 @@ <h3 id="_step_4_add_variables">Step 4: Add variables</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>Hey, wait a minute&#8230;&#8203;did you just have us put variables in two separate places?<br></p>
+<p>Hey, wait a minute…​did you just have us put variables in two separate places?<br/></p>
 </div>
 <div class="paragraph">
-<p>Yes&#8230;&#8203;yes we did.  Variables can live in quite a few places.  Just to name a few:<br></p>
+<p>Yes…​yes we did.  Variables can live in quite a few places.  Just to name a few:<br/></p>
 </div>
 <div class="ulist">
 <ul>
@@ -497,11 +497,11 @@ <h3 id="_step_4_add_variables">Step 4: Add variables</h3>
 </div>
 <div class="paragraph">
 <p>Bottom line, you need to read up on <a href="http://docs.ansible.com/ansible/latest/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable">variable precedence</a> to understand both where to define variables and which locations take precedence.  In this exercise, we are using role defaults to define a couple of variables and these are the most malleable.  After that, we defined some variables in <code>/vars</code>
-which have a higher precedence than defaults and can&#8217;t be overridden as a default variable.</p>
+which have a higher precedence than defaults and can’t be overridden as a default variable.</p>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -532,9 +532,9 @@ <h3 id="_step_6_add_role_tasks">Step 6: Add role tasks</h3>
 # tasks file for apache-simple
 - name: install httpd packages
   package:
-    name: "{{ item }}"
+    name: &#34;{{ item }}&#34;
     state: present
-  with_items: "{{ httpd_packages }}"
+  with_items: &#34;{{ httpd_packages }}&#34;
   notify: restart apache service
 
 - name: create site-enabled directory
@@ -564,7 +564,7 @@ <h3 id="_step_6_add_role_tasks">Step 6: Add role tasks</h3>
 <div class="sect2">
 <h3 id="_step_7_download_templates">Step 7: Download templates</h3>
 <div class="paragraph">
-<p>Download a couple of templates into <code>roles/apache-simple/templates/</code>.  And right after that, let&#8217;s clean up from exercise 2.1 by removing the old templates directory.</p>
+<p>Download a couple of templates into <code>roles/apache-simple/templates/</code>.  And right after that, let’s clean up from exercise 2.1 by removing the old templates directory.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -582,8 +582,8 @@ <h3 id="_step_7_download_templates">Step 7: Download templates</h3>
 <h2 id="_section_3_running_your_new_role_based_playbook">Section 3: Running your new role-based playbook</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve successfully separated your original playbook into a role,
-let&#8217;s run it and see how it works.</p>
+<p>Now that you’ve successfully separated your original playbook into a role,
+let’s run it and see how it works.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1_run_the_playbook">Step 1: Run the playbook</h3>
@@ -604,7 +604,7 @@ <h3 id="_step_2_verify_your_output">Step 2: Verify your output</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/stdout_3.png" alt="ansible-basic-playbook role-based stdout">
+<img src="/workshops/ansible_tower_azure/images/stdout_3.png" alt="ansible-basic-playbook role-based stdout"/>
 </div>
 </div>
 </div>
@@ -808,7 +808,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -869,7 +869,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise2.0/index.html b/workshops/ansible_tower_azure/exercise2.0/index.html
index a3431f7df..c12fcb976 100644
--- a/workshops/ansible_tower_azure/exercise2.0/index.html
+++ b/workshops/ansible_tower_azure/exercise2.0/index.html
@@ -393,19 +393,19 @@ <h3 id="_step_6_identify_variables">Step 6: Identify variables</h3>
 [database]
 
 [all:vars]
-admin_password=<strong>'ansibleWS'</strong>
+admin_password=<strong>&#39;ansibleWS&#39;</strong>
 
-pg_host=''
-pg_port=''
+pg_host=&#39;&#39;
+pg_port=&#39;&#39;
 
-pg_database='awx'
-pg_username='awx'
-pg_password=<strong>'ansibleWS'</strong>
+pg_database=&#39;awx&#39;
+pg_username=&#39;awx&#39;
+pg_password=<strong>&#39;ansibleWS&#39;</strong>
 
 rabbitmq_port=5672
 rabbitmq_vhost=tower
 rabbitmq_username=tower
-rabbitmq_password=<strong>'ansibleWS'</strong>
+rabbitmq_password=<strong>&#39;ansibleWS&#39;</strong>
 rabbitmq_cookie=cookiemonster
 
 # Needs to be true for fqdns and ip addresses
@@ -425,7 +425,7 @@ <h3 id="_step_7_run_setup">Step 7: Run setup</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -433,7 +433,7 @@ <h3 id="_step_7_run_setup">Step 7: Run setup</h3>
 Step 7 will take approx. 10-15 minutes to complete.  This may be a good time to take a break.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -451,11 +451,11 @@ <h3 id="_step_8_confirm_results">Step 8: Confirm results</h3>
 <div class="sect2">
 <h3 id="_ensuring_installation_success">Ensuring Installation Success</h3>
 <div class="paragraph">
-<p>You know you were successful if you are able to browse to your Ansible Tower&#8217;s url (<em>control node&#8217;s IP address</em>) and get something like this</p>
+<p>You know you were successful if you are able to browse to your Ansible Tower’s url (<em>control node’s IP address</em>) and get something like this</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen">
+<img src="/workshops/ansible_tower_azure/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen"/>
 </div>
 <div class="title">Figure 2: Ansible Tower Login Screen</div>
 </div>
@@ -651,7 +651,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -713,7 +713,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise2.1/index.html b/workshops/ansible_tower_azure/exercise2.1/index.html
index db6bb77fe..139906026 100644
--- a/workshops/ansible_tower_azure/exercise2.1/index.html
+++ b/workshops/ansible_tower_azure/exercise2.1/index.html
@@ -325,7 +325,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -334,7 +334,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 However, we are only going to focus on a few of the key concepts required for this workshop today.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="ulist">
 <ul>
@@ -362,7 +362,7 @@ <h2 id="_section_1_logging_into_ansible_tower_and_installing_the_license_key">Se
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen">
+<img src="/workshops/ansible_tower_azure/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen"/>
 </div>
 <div class="title">Figure 3: Ansible Tower Login Screen</div>
 </div>
@@ -371,7 +371,7 @@ <h2 id="_section_1_logging_into_ansible_tower_and_installing_the_license_key">Se
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_lic_prompt.png" alt="at lic prompt">
+<img src="/workshops/ansible_tower_azure/images/at_lic_prompt.png" alt="at lic prompt"/>
 </div>
 <div class="title">Figure 4: Uploading a License</div>
 </div>
@@ -384,19 +384,19 @@ <h3 id="_step_2_request_workshop_license">Step 2: Request workshop license</h3>
 <div class="sect2">
 <h3 id="_step_3_upload_ansible_tower_workshop_license">Step 3: Upload Ansible Tower workshop license</h3>
 <div class="paragraph">
-<p>Back in the Ansible Tower UI, choose BROWSE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_browse.png" alt="LicB" width="35" height="25"></span> and upload your recently downloaded license file into Ansible Tower.</p>
+<p>Back in the Ansible Tower UI, choose BROWSE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_browse.png" alt="LicB" width="35" height="25"/></span> and upload your recently downloaded license file into Ansible Tower.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_4_accept_license_agreement">Step 4: Accept license agreement</h3>
 <div class="paragraph">
-<p>Select "<em>I agree to the End User License Agreement</em>".</p>
+<p>Select &#34;<em>I agree to the End User License Agreement</em>&#34;.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_5_submit">Step 5: Submit</h3>
 <div class="paragraph">
-<p>Click on SUBMIT <span class="image"><img src="/workshops/ansible_tower_azure/images/at_submit.png" alt="Sub" width="35" height="25"></span></p>
+<p>Click on SUBMIT <span class="image"><img src="/workshops/ansible_tower_azure/images/at_submit.png" alt="Sub" width="35" height="25"/></span></p>
 </div>
 </div>
 </div>
@@ -414,19 +414,19 @@ <h2 id="_section_2_creating_a_credential">Section 2: Creating a Credential</h2>
 <div class="sect2">
 <h3 id="_step_1_select_settings">Step 1: Select Settings</h3>
 <div class="paragraph">
-<p>Select Ansible Tower Settings (gear icon).     <span class="image"><img src="/workshops/ansible_tower_azure/images/at_gear.png" alt="Gear" width="20" height="20"></span></p>
+<p>Select Ansible Tower Settings (gear icon).     <span class="image"><img src="/workshops/ansible_tower_azure/images/at_gear.png" alt="Gear" width="20" height="20"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_select_credentials">Step 2: Select Credentials</h3>
 <div class="paragraph">
-<p>Select CREDENTIALS <span class="image"><img src="/workshops/ansible_tower_azure/images/at_credentials.png" alt="Cred" width="100" height="35"></span></p>
+<p>Select CREDENTIALS <span class="image"><img src="/workshops/ansible_tower_azure/images/at_credentials.png" alt="Cred" width="100" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_select_add">Step 3: Select Add</h3>
 <div class="paragraph">
-<p>Select ADD <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Select ADD <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -441,8 +441,8 @@ <h3 id="_step_4_complete_the_ansible_tower_credentials_form">Step 4: Complete th
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -477,7 +477,7 @@ <h3 id="_step_4_complete_the_ansible_tower_credentials_form">Step 4: Complete th
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_cred_detail.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/at_cred_detail.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 5: Adding a Credential</div>
 </div>
@@ -485,7 +485,7 @@ <h3 id="_step_4_complete_the_ansible_tower_credentials_form">Step 4: Complete th
 <div class="sect2">
 <h3 id="_step_5_save">Step 5: Save</h3>
 <div class="paragraph">
-<p>Select   SAVE  <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"></span><br></p>
+<p>Select   SAVE  <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"/></span><br/></p>
 </div>
 </div>
 </div>
@@ -502,13 +502,13 @@ <h2 id="_section_3_creating_a_project">Section 3: Creating a Project</h2>
 <div class="sect2">
 <h3 id="_step_1_open_a_new_project">Step 1: Open a new project</h3>
 <div class="paragraph">
-<p>Click on PROJECTS <span class="image"><img src="/workshops/ansible_tower_azure/images/at_projects_icon.png" alt="Proj" width="100" height="35"></span></p>
+<p>Click on PROJECTS <span class="image"><img src="/workshops/ansible_tower_azure/images/at_projects_icon.png" alt="Proj" width="100" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_add_the_project">Step 2: Add the project</h3>
 <div class="paragraph">
-<p>Select  ADD   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Select  ADD   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -518,8 +518,8 @@ <h3 id="_step_3_complete_the_project_form">Step 3: Complete the Project form</h3
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -566,7 +566,7 @@ <h3 id="_step_3_complete_the_project_form">Step 3: Complete the Project form</h3
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_project_detail.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/at_project_detail.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 6: Defining a Project</div>
 </div>
@@ -574,7 +574,7 @@ <h3 id="_step_3_complete_the_project_form">Step 3: Complete the Project form</h3
 <div class="sect2">
 <h3 id="_step_4_save">Step 4: Save</h3>
 <div class="paragraph">
-<p>Select  SAVE   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select  SAVE   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 </div>
@@ -595,13 +595,13 @@ <h2 id="_section_4_creating_an_inventory">Section 4: Creating an Inventory</h2>
 <div class="sect2">
 <h3 id="_step_1_navigate_to_inventories_main_link">Step 1: Navigate to Inventories main link</h3>
 <div class="paragraph">
-<p>Click on INVENTORIES <span class="image"><img src="/workshops/ansible_tower_azure/images/at_inv_icon.png" alt="Inv" width="100" height="35"></span></p>
+<p>Click on INVENTORIES <span class="image"><img src="/workshops/ansible_tower_azure/images/at_inv_icon.png" alt="Inv" width="100" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_add_a_new_inventory">Step 2: Add a new inventory</h3>
 <div class="paragraph">
-<p>Select  ADD   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Select  ADD   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -611,8 +611,8 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -631,7 +631,7 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_inv_create.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/at_inv_create.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 7: Create an Inventory</div>
 </div>
@@ -639,7 +639,7 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 <div class="sect2">
 <h3 id="_step_4_save_2">Step 4: Save</h3>
 <div class="paragraph">
-<p>Select  SAVE   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select  SAVE   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -660,7 +660,7 @@ <h3 id="_step_6_import_an_existing_inventory">Step 6: Import an existing invento
 </div>
 <div class="listingblock">
 <div class="content">
-<pre>sudo tower-manage inventory_import --source=/home/azure-user/hosts --inventory-name="Ansible Workshop Inventory"</pre>
+<pre>sudo tower-manage inventory_import --source=/home/azure-user/hosts --inventory-name=&#34;Ansible Workshop Inventory&#34;</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -668,18 +668,18 @@ <h3 id="_step_6_import_an_existing_inventory">Step 6: Import an existing invento
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_tm_stdout.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/at_tm_stdout.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 8: Importing an inventory with tower-manage</div>
 </div>
 <div class="paragraph">
 <p>Feel free to browse your inventory in Ansible Tower, by selecting <strong>Hosts</strong>.
-<span class="image"><img src="/workshops/ansible_tower_azure/images/at_inv_hosts.png" alt="hosts" width="200" height="50"></span>
+<span class="image"><img src="/workshops/ansible_tower_azure/images/at_inv_hosts.png" alt="hosts" width="200" height="50"/></span>
 You should now notice that the inventory has been populated with each each of hosts and corresponding inventory.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_inv_group.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/at_inv_group.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 9: Inventory with Groups</div>
 </div>
@@ -881,7 +881,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -943,7 +943,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise2.2/index.html b/workshops/ansible_tower_azure/exercise2.2/index.html
index 9d786c8c8..fcb9b517e 100644
--- a/workshops/ansible_tower_azure/exercise2.2/index.html
+++ b/workshops/ansible_tower_azure/exercise2.2/index.html
@@ -327,7 +327,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.  Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</p>
 </div>
 <div class="paragraph">
-<p>Templates also drive uniformity, by running templates exactly the same way every time. And, because we&#8217;re using templates, production responsibilities can be delegated to less experienced production personnel.</p>
+<p>Templates also drive uniformity, by running templates exactly the same way every time. And, because we’re using templates, production responsibilities can be delegated to less experienced production personnel.</p>
 </div>
 </div>
 </div>
@@ -337,13 +337,13 @@ <h2 id="_creating_a_job_template">Creating a Job Template</h2>
 <div class="sect2">
 <h3 id="_step_1_navigate_to_the_templates_tab">Step 1: Navigate to the Templates tab</h3>
 <div class="paragraph">
-<p>Select TEMPLATES <span class="image"><img src="/workshops/ansible_tower_azure/images/at_templates.png" alt="temp" width="120" height="35"></span></p>
+<p>Select TEMPLATES <span class="image"><img src="/workshops/ansible_tower_azure/images/at_templates.png" alt="temp" width="120" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_create_a_new_template">Step 2: Create a new template</h3>
 <div class="paragraph">
-<p>Click <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span>, and select JOB TEMPLATE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_jobtemplate.png" alt="jobT" width="150" height="100"></span></p>
+<p>Click <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span>, and select JOB TEMPLATE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_jobtemplate.png" alt="jobT" width="150" height="100"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -353,8 +353,8 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -403,7 +403,7 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_jt_detail.png" alt="at jt detail" width="1024">
+<img src="/workshops/ansible_tower_azure/images/at_jt_detail.png" alt="at jt detail" width="1024"/>
 </div>
 <div class="title">Figure 11: Job Template Form</div>
 </div>
@@ -411,7 +411,7 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 <div class="sect2">
 <h3 id="_step_4_save">Step 4: Save</h3>
 <div class="paragraph">
-<p>Click SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save"></span> and then select ADD SURVEY <span class="image"><img src="/workshops/ansible_tower_azure/images/at_addsurvey.png" alt="Add Survey"></span></p>
+<p>Click SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save"/></span> and then select ADD SURVEY <span class="image"><img src="/workshops/ansible_tower_azure/images/at_addsurvey.png" alt="Add Survey"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -424,8 +424,8 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -450,13 +450,13 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">DEFAULT ANSWER</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Be creative, keep it clean, we&#8217;re all professionals here</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Be creative, keep it clean, we’re all professionals here</p></td>
 </tr>
 </tbody>
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_survey_detail.png" alt="at survey detail" width="500">
+<img src="/workshops/ansible_tower_azure/images/at_survey_detail.png" alt="at survey detail" width="500"/>
 </div>
 <div class="title">Figure 12: Survey Form</div>
 </div>
@@ -464,19 +464,19 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 <div class="sect2">
 <h3 id="_step_6_add_the_survey_input">Step 6: Add the survey input</h3>
 <div class="paragraph">
-<p>Select ADD <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Select ADD <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_7_save">Step 7: Save</h3>
 <div class="paragraph">
-<p>Select SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_8_save_at_the_main_page">Step 8: Save at the main page</h3>
 <div class="paragraph">
-<p>Back on the main Job Template page, select SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"></span> again.</p>
+<p>Back on the main Job Template page, select SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"/></span> again.</p>
 </div>
 </div>
 </div>
@@ -485,7 +485,7 @@ <h3 id="_step_8_save_at_the_main_page">Step 8: Save at the main page</h3>
 <h2 id="_section_2_running_a_job_template">Section 2: Running a job template</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve successfully creating your Job Template, you are ready to launch it.
+<p>Now that you’ve successfully creating your Job Template, you are ready to launch it.
 You will be redirected to a job screen, which refreshes in real-time
 and displays the status of the job.</p>
 </div>
@@ -496,21 +496,21 @@ <h3 id="_step_1_select_the_template_tab">Step 1: Select the Template tab</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-Alternatively, if you haven&#8217;t navigated away from the job templates creation page, you can scroll down to see all existing job templates
+Alternatively, if you haven’t navigated away from the job templates creation page, you can scroll down to see all existing job templates
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_access_apache_basic_job_template">Step 2: Access Apache Basic Job Template</h3>
 <div class="paragraph">
-<p>Click on the rocketship icon <span class="image"><img src="/workshops/ansible_tower_azure/images/at_launch_icon.png" alt="Add" width="35" height="25"></span> for the <strong>Apache Basic Job Template</strong></p>
+<p>Click on the rocketship icon <span class="image"><img src="/workshops/ansible_tower_azure/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span> for the <strong>Apache Basic Job Template</strong></p>
 </div>
 </div>
 <div class="sect2">
@@ -520,7 +520,7 @@ <h3 id="_step_3_enter_test_message">Step 3: Enter test message</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_survey_prompt.png" alt="at survey prompt">
+<img src="/workshops/ansible_tower_azure/images/at_survey_prompt.png" alt="at survey prompt"/>
 </div>
 <div class="title">Figure 13: Survey Prompt</div>
 </div>
@@ -528,7 +528,7 @@ <h3 id="_step_3_enter_test_message">Step 3: Enter test message</h3>
 <div class="sect2">
 <h3 id="_step_4">Step 4:</h3>
 <div class="paragraph">
-<p>Select LAUNCH <span class="image"><img src="/workshops/ansible_tower_azure/images/at_survey_launch.png" alt="SurveyL" width="35" height="25"></span></p>
+<p>Select LAUNCH <span class="image"><img src="/workshops/ansible_tower_azure/images/at_survey_launch.png" alt="SurveyL" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -538,11 +538,11 @@ <h3 id="_step_5_launch_the_job">Step 5: Launch the job</h3>
 </div>
 <div class="paragraph">
 <p>One of the first things you will notice is the summary section.  This gives you details about
-your job such as who launched it, what playbook it&#8217;s running, what the status is, i.e. pending, running, or complete.</p>
+your job such as who launched it, what playbook it’s running, what the status is, i.e. pending, running, or complete.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_job_status.png" alt="at job status">
+<img src="/workshops/ansible_tower_azure/images/at_job_status.png" alt="at job status"/>
 </div>
 <div class="title">Figure 14: Job Summary</div>
 </div>
@@ -551,7 +551,7 @@ <h3 id="_step_5_launch_the_job">Step 5: Launch the job</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_job_tasklist.png" alt="at job tasklist" width="800">
+<img src="/workshops/ansible_tower_azure/images/at_job_tasklist.png" alt="at job tasklist" width="800"/>
 </div>
 <div class="title">Figure 15: Play and Task Details</div>
 </div>
@@ -560,7 +560,7 @@ <h3 id="_step_5_launch_the_job">Step 5: Launch the job</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_job_stdout.png" alt="at job stdout" width="700">
+<img src="/workshops/ansible_tower_azure/images/at_job_stdout.png" alt="at job stdout" width="700"/>
 </div>
 <div class="title">Figure 16: Job Standard Output</div>
 </div>
@@ -580,7 +580,7 @@ <h3 id="_step_6_view_the_new_website">Step 6: View the new website</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/at_web_tm.png" alt="at web tm">
+<img src="/workshops/ansible_tower_azure/images/at_web_tm.png" alt="at web tm"/>
 </div>
 <div class="title">Figure 17: New Website with Personalized Test Message</div>
 </div>
@@ -591,8 +591,8 @@ <h3 id="_step_6_view_the_new_website">Step 6: View the new website</h3>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point in the workshop, you&#8217;ve experienced the core functionality of Ansible Tower.  But wait&#8230;&#8203;there&#8217;s more!
-You&#8217;ve just begun to explore the possibilities of Ansible Core and Tower.  Take a look at the resources page in this guide, to explore some more features.</p>
+<p>At this point in the workshop, you’ve experienced the core functionality of Ansible Tower.  But wait…​there’s more!
+You’ve just begun to explore the possibilities of Ansible Core and Tower.  Take a look at the resources page in this guide, to explore some more features.</p>
 </div>
 <div class="paragraph">
 <script type="text/javascript">
@@ -786,7 +786,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -847,7 +847,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/exercise3.0/index.html b/workshops/ansible_tower_azure/exercise3.0/index.html
index 760f7d500..672efc86d 100644
--- a/workshops/ansible_tower_azure/exercise3.0/index.html
+++ b/workshops/ansible_tower_azure/exercise3.0/index.html
@@ -354,7 +354,7 @@ <h3 id="_step_1_download_role_to_ansible_roles_directory">Step 1: Download role
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">- downloading role '800-53', owned by rhtps
+<pre class="highlight"><code class="language-bash" data-lang="bash">- downloading role &#39;800-53&#39;, owned by rhtps
 - downloading role from https://github.com/rhtps/ansible-role-800-53/archive/v1.1.1.tar.gz
 - extracting rhtps.800-53 to /etc/ansible/roles/rhtps.800-53
 - rhtps.800-53 (v1.1.1) was installed successfully</code></pre>
@@ -364,13 +364,13 @@ <h3 id="_step_1_download_role_to_ansible_roles_directory">Step 1: Download role
 <div class="sect2">
 <h3 id="_step_2_select_projects">Step 2: Select Projects</h3>
 <div class="paragraph">
-<p>First, in Ansible Tower, click on <span class="image"><img src="/workshops/ansible_tower_azure/images/at_projects_icon.png" alt="PROJECTS"></span></p>
+<p>First, in Ansible Tower, click on <span class="image"><img src="/workshops/ansible_tower_azure/images/at_projects_icon.png" alt="PROJECTS"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_click_uploaded">Step 3: Click uploaded</h3>
 <div class="paragraph">
-<p>Next, Select ADD    <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span></p>
+<p>Next, Select ADD    <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -380,8 +380,8 @@ <h3 id="_step_4_complete_the_project_form">Step 4: Complete the Project form</h3
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -428,7 +428,7 @@ <h3 id="_step_4_complete_the_project_form">Step 4: Complete the Project form</h3
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/section3.0-create-project.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/section3.0-create-project.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 1: Defining a Project</div>
 </div>
@@ -436,7 +436,7 @@ <h3 id="_step_4_complete_the_project_form">Step 4: Complete the Project form</h3
 <div class="sect2">
 <h3 id="_step_5_save">Step 5: Save</h3>
 <div class="paragraph">
-<p>Select  SAVE   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select  SAVE   <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -448,7 +448,7 @@ <h3 id="_step_6_select_template_tab">Step 6: Select Template tab</h3>
 <div class="sect2">
 <h3 id="_step_7_add_the_job_template">Step 7: Add the job template</h3>
 <div class="paragraph">
-<p>Click ADD <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"></span>, and select <code>JOB TEMPLATE</code></p>
+<p>Click ADD <span class="image"><img src="/workshops/ansible_tower_azure/images/at_add.png" alt="Add" width="35" height="25"/></span>, and select <code>JOB TEMPLATE</code></p>
 </div>
 </div>
 <div class="sect2">
@@ -458,8 +458,8 @@ <h3 id="_step_8_complete_the_job_template_form">Step 8: Complete the job Templat
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -508,7 +508,7 @@ <h3 id="_step_8_complete_the_job_template_form">Step 8: Complete the job Templat
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/section3.0-create-job-template.png" alt="Cred_Detail" width="900">
+<img src="/workshops/ansible_tower_azure/images/section3.0-create-job-template.png" alt="Cred_Detail" width="900"/>
 </div>
 <div class="title">Figure 2: Defining a Job</div>
 </div>
@@ -516,10 +516,10 @@ <h3 id="_step_8_complete_the_job_template_form">Step 8: Complete the job Templat
 <div class="sect2">
 <h3 id="_step_9_save_the_template_and_run_it">Step 9: Save the template and run it</h3>
 <div class="paragraph">
-<p>Click SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save"></span>, to store your new template, and we are ready to run it.</p>
+<p>Click SAVE <span class="image"><img src="/workshops/ansible_tower_azure/images/at_save.png" alt="Save"/></span>, to store your new template, and we are ready to run it.</p>
 </div>
 <div class="paragraph">
-<p>Click on the rocket ship icon <span class="image"><img src="/workshops/ansible_tower_azure/images/at_launch_icon.png" alt="Add" width="35" height="25"></span> next to the <code>NIST 800-53 and DISA STIG Job Template</code> entry, to launch the job.</p>
+<p>Click on the rocket ship icon <span class="image"><img src="/workshops/ansible_tower_azure/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span> next to the <code>NIST 800-53 and DISA STIG Job Template</code> entry, to launch the job.</p>
 </div>
 <div class="paragraph">
 <p>You can see what the job looks like, as it is executing, and what the SCAP results look like, when uploaded to your second node, in the panel, below.</p>
@@ -532,18 +532,18 @@ <h3 id="_step_9_save_the_template_and_run_it">Step 9: Save the template and run
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse9511e66bef88e72c21ef7c111cf148b1" class="collapsed">
+      <a data-toggle="collapse" href="#collapsecd80690c22a07901af5c62bc24552154" class="collapsed">
       
         Job Status
       </a>
     </h4>
   </div>
   
-  <div id="collapse9511e66bef88e72c21ef7c111cf148b1" class="panel-collapse collapse ">
+  <div id="collapsecd80690c22a07901af5c62bc24552154" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
-<p><span class="image"><img src="/workshops/ansible_tower/images/at_800-53_job_status.png" alt="Job Status" width="1024"></span></p>
+<p><span class="image"><img src="/workshops/ansible_tower/images/at_800-53_job_status.png" alt="Job Status" width="1024"/></span></p>
 </div>
 
     </div>
@@ -555,18 +555,18 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse1d8e8c2cd216a4eeec9f5071b0b77207" class="collapsed">
+      <a data-toggle="collapse" href="#collapse41e0f3eee06611e55e125f763e861570" class="collapsed">
       
         Results
       </a>
     </h4>
   </div>
   
-  <div id="collapse1d8e8c2cd216a4eeec9f5071b0b77207" class="panel-collapse collapse ">
+  <div id="collapse41e0f3eee06611e55e125f763e861570" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
-<p><span class="image"><img src="/workshops/ansible_tower/images/at_scap_report.png" alt="SCAP Report" width="1024"></span></p>
+<p><span class="image"><img src="/workshops/ansible_tower/images/at_scap_report.png" alt="SCAP Report" width="1024"/></span></p>
 </div>
 
     </div>
@@ -592,7 +592,7 @@ <h3 id="_step_10_observe_the_scanning_process_and_view_reports">Step 10: Observe
 </div>
 </div>
 <div class="paragraph">
-<p>Click on the link called <code>scan-xccdf-report-&#8230;&#8203;</code> to refiew the SCAP report that was generated.  Note the failures in the report; look at the machines, if you want, via your Wetty ssh session, to see what the problems might be.</p>
+<p>Click on the link called <code>scan-xccdf-report-…​</code> to refiew the SCAP report that was generated.  Note the failures in the report; look at the machines, if you want, via your Wetty ssh session, to see what the problems might be.</p>
 </div>
 <div class="paragraph">
 <script type="text/javascript">
@@ -786,7 +786,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -848,7 +848,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/index.html b/workshops/ansible_tower_azure/index.html
index e19de4870..823262a85 100644
--- a/workshops/ansible_tower_azure/index.html
+++ b/workshops/ansible_tower_azure/index.html
@@ -633,7 +633,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -661,7 +661,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/index.xml b/workshops/ansible_tower_azure/index.xml
index a514cfe55..45f4a7ef3 100644
--- a/workshops/ansible_tower_azure/index.xml
+++ b/workshops/ansible_tower_azure/index.xml
@@ -4,138 +4,92 @@
     <title>Ansible Tower Workshop on Azure on Red Hat | Public Sector</title>
     <link>/workshops/ansible_tower_azure/</link>
     <description>Recent content in Ansible Tower Workshop on Azure on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/ansible_tower_azure/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/ansible_tower_azure/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Running Ad-hoc commands</title>
       <link>/workshops/ansible_tower_azure/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.0/</guid>
       <description>Section 1: Ad hoc commands For our first exercise, we are going to run some ad hoc commands to help you get a feel for how Red Hat Ansible Tower works. Ansible ad hoc commands enable you to perform repeatable tasks on remote nodes, without having to write a playbook. They are very useful when you simply need to do one or two tasks quickly and often, to many remote nodes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Writing Your First playbook</title>
       <link>/workshops/ansible_tower_azure/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.1/</guid>
-      <description>Now that you&amp;#8217;ve gotten a sense of how ansible works, we are going to write our first ansible playbook. The playbook is where you can take some of those ad-hoc commands you just ran and put them into a repeatable set of plays and tasks.
- A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
+      <description>Now that you’ve gotten a sense of how ansible works, we are going to write our first ansible playbook. The playbook is where you can take some of those ad-hoc commands you just ran and put them into a repeatable set of plays and tasks.&#xA;A playbook can have multiple plays and a play can have one or multiple tasks. The goal of a play is to map a group of hosts.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Running Your Playbook</title>
       <link>/workshops/ansible_tower_azure/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.2/</guid>
-      <description>Section 1: Running the Playbook We are now going to run your brand spankin&#39; new playbook on your two web nodes. To do this, you are going to use the ansible-playbook command.
- Step 1: Run your playbook From your playbook directory ( ~/apache_basic ), run your playbook.
- ansible-playbook -i ../hosts install_apache.yml --private-key=~/.ssh/example-tower   However, before you run that command, lets take a few moments to understand the options.</description>
+      <description>Section 1: Running the Playbook We are now going to run your brand spankin&amp;#39; new playbook on your two web nodes. To do this, you are going to use the ansible-playbook command.&#xA;Step 1: Run your playbook From your playbook directory ( ~/apache_basic ), run your playbook.&#xA;ansible-playbook -i ../hosts install_apache.yml --private-key=~/.ssh/example-tower However, before you run that command, lets take a few moments to understand the options.&#xA;--private-key This option ask for the private ssh key to connect to the remote machine.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Using Variables, Loops, and Handlers</title>
       <link>/workshops/ansible_tower_azure/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.3/</guid>
-      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.
- Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
+      <description>Exercise Description In previous exercises, we showed you the basics of the Ansible core. In the next few exercises, we are going to teach some more advanced Ansible skills that will add flexibility and power to your playbooks.&#xA;Ansible exists to make tasks simple and repeatable. We also know that not all systems are exactly alike and often require some slight customization to the way an Ansible playbook is run.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Running the apache-basic-playbook</title>
       <link>/workshops/ansible_tower_azure/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.4/</guid>
-      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let&amp;#8217;s do that now.
-   Section 1 - Running your new apache playbook Step 1: Create a host file Make sure you are in the right directory and create a host file.</description>
+      <description>Congratulations! You just wrote a playbook that incorporates some key Ansible concepts that you use in most, if not all, of your future playbooks. Before you get too excited though, we should probably make sure it actually runs. So, let’s do that now.&#xA;Section 1 - Running your new apache playbook Step 1: Create a host file Make sure you are in the right directory and create a host file.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Roles: Making your playbooks reusable</title>
       <link>/workshops/ansible_tower_azure/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise1.5/</guid>
-      <description>Exercise Description While it is possible to write a playbook in one file as we&amp;#8217;ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.
- The &#34;role&#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
+      <description>Exercise Description While it is possible to write a playbook in one file as we’ve done throughout this workshop, eventually you’ll want to reuse files and start to organize things.&#xA;The &amp;#34;role&amp;#34; feature in Ansible is the way we do this. When you create a role, you deconstruct your playbook into parts and those parts sit in a directory structure. &amp;#34;Wha?? You mean that seemingly useless best practice you mentioned in exercise 1.</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Installing Ansible Tower</title>
       <link>/workshops/ansible_tower_azure/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise2.0/</guid>
-      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node
-   Installing Ansible Tower Step 1: Change directories Change directories to /tmp
- cd /tmp    Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package
- curl -O http://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-latest.tar.gz    Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-latest.tar.gz    Step 4: Change directories Change directories into the Ansible Tower package</description>
+      <description>Exercise Description In this exercise, we are going to get Ansible Tower installed on your control node&#xA;Installing Ansible Tower Step 1: Change directories Change directories to /tmp&#xA;cd /tmp Step 2: Download Red Hat Ansible Tower Download the latest Ansible Tower package&#xA;curl -O http://releases.ansible.com/ansible-tower/setup/ansible-tower-setup-latest.tar.gz Step 3: Untar and unzip the package file tar xvfz /tmp/ansible-tower-setup-latest.tar.gz Step 4: Change directories Change directories into the Ansible Tower package&#xA;cd /tmp/ansible-tower-setup-*/ Step 5: Open inventory file Using an editor of your choice, open the inventory file</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Configuring Ansible Tower</title>
       <link>/workshops/ansible_tower_azure/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise2.1/</guid>
-      <description>Exercise Description In this exercise, we are going to configure Tower so that we can run a playbook.
-     There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on a few of the key concepts required for this workshop today.       Credentials
-  Projects
-  Inventory</description>
+      <description>Exercise Description In this exercise, we are going to configure Tower so that we can run a playbook.&#xA;There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on a few of the key concepts required for this workshop today. Credentials&#xA;Projects&#xA;Inventory&#xA;Job Template&#xA;Section 1: Logging into Ansible Tower and installing the license key To log in, use the username admin and the password ansibleWS.</description>
     </item>
-    
     <item>
       <title>Exercise 2.2 - Creating and Running a Job Template</title>
       <link>/workshops/ansible_tower_azure/exercise2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise2.2/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it.
- A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package. Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it.&#xA;A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package. Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
     </item>
-    
     <item>
       <title>Exercise 3.0 - Using Ansible to Implement Security</title>
       <link>/workshops/ansible_tower_azure/exercise3.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/exercise3.0/</guid>
-      <description>In this exercise, we are going to use Ansible Tower to run DISA STIG and NIST 800-53 evaluations of our environment. Note that the NIST 800-53 role also includes the execution of DISA STIG evaluation against targeted hosts.
-   DISA STIG controls https://galaxy.ansible.com/MindPointGroup/RHEL7-STIG/
-  NIST 800-53 controls https://galaxy.ansible.com/rhtps/800-53/
-     Adding the DISA STIG and NIST 800-53 role to your Tower node Step 1: Download role to Ansible roles directory In your wetty window (if you closed it, see the SETUP step, in your workbook), type the following:</description>
+      <description>In this exercise, we are going to use Ansible Tower to run DISA STIG and NIST 800-53 evaluations of our environment. Note that the NIST 800-53 role also includes the execution of DISA STIG evaluation against targeted hosts.&#xA;DISA STIG controls https://galaxy.ansible.com/MindPointGroup/RHEL7-STIG/&#xA;NIST 800-53 controls https://galaxy.ansible.com/rhtps/800-53/&#xA;Adding the DISA STIG and NIST 800-53 role to your Tower node Step 1: Download role to Ansible roles directory In your wetty window (if you closed it, see the SETUP step, in your workbook), type the following:</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/ansible_tower_azure/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/setup/</guid>
-      <description>What you will learn: Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Wetty Use this URL to access the Wetty node, just change the workshopname and region (if applicable). Ask your instructor for the workshopname and region.</description>
+      <description>What you will learn: Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Use this URL to access the Wetty node, just change the workshopname and region (if applicable). Ask your instructor for the workshopname and region.&#xA;https://example-tower0.example.redhatgov.io:8888 login: azure-user Password: redhat!</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/ansible_tower_azure/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/ansible_tower_azure/setup/index.html b/workshops/ansible_tower_azure/setup/index.html
index 494477ef9..742565c2d 100644
--- a/workshops/ansible_tower_azure/setup/index.html
+++ b/workshops/ansible_tower_azure/setup/index.html
@@ -317,7 +317,7 @@ <h1>Setup</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/tower.002.png" alt="Tower">
+<img src="/workshops/ansible_tower_azure/images/tower.002.png" alt="Tower"/>
 </div>
 </div>
 </div>
@@ -352,21 +352,21 @@ <h2 id="_accessing_wetty">Accessing Wetty</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/wetty.png" alt="wetty" width="1024">
+<img src="/workshops/ansible_tower_azure/images/wetty.png" alt="wetty" width="1024"/>
 </div>
 <div class="title">Figure 1: wetty</div>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-Be sure you can log in to your instances.  If you can&#8217;t log in start shouting, loudly, and waving your hands!
+Be sure you can log in to your instances.  If you can’t log in start shouting, loudly, and waving your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -374,7 +374,7 @@ <h2 id="_accessing_wetty">Accessing Wetty</h2>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <script type="text/javascript">
@@ -568,7 +568,7 @@ <h3>Workshop Details</h3>
 <td align=right><b>Domain: </b></td>
 <td><span class="domain"></span></td>
 <td rowspan=3>
-<img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" onload=loadVariables()>
+<img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" onload=loadVariables()>
 </td>
 </tr>
 <tr>
@@ -625,7 +625,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_azure/wrapup/index.html b/workshops/ansible_tower_azure/wrapup/index.html
index e9566f8ef..aab9186ef 100644
--- a/workshops/ansible_tower_azure/wrapup/index.html
+++ b/workshops/ansible_tower_azure/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrapup</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something valuable
+<p>That wraps up what we have planned for today.  We hope you’ve learned something valuable
 about Ansible and Red Hat Ansible Tower that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
@@ -331,7 +331,7 @@ <h1>Wrapup</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_azure/images/redhat.svg" alt="redhat">
+<img src="/workshops/ansible_tower_azure/images/redhat.svg" alt="redhat"/>
 </div>
 </div>
 
@@ -369,7 +369,7 @@ <h1>Wrapup</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_intro/exercise1.0/index.html b/workshops/ansible_tower_intro/exercise1.0/index.html
index 4b038be60..0bb03c8d4 100644
--- a/workshops/ansible_tower_intro/exercise1.0/index.html
+++ b/workshops/ansible_tower_intro/exercise1.0/index.html
@@ -355,7 +355,7 @@ <h3 id="_step_1_log_in">Step 1: Log in</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen">
+<img src="/workshops/ansible_tower_intro/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen"/>
 </div>
 <div class="title">Figure 3: Ansible Tower Login Screen</div>
 </div>
@@ -374,14 +374,14 @@ <h2 id="_section_2_review_credentials">Section 2: Review credentials</h2>
 <div class="sect2">
 <h3 id="_step_1_view_available_credentials">Step 1: View Available Credentials</h3>
 <div class="paragraph">
-<p>Select CREDENTIALS, from the left-side menu bar.   <span class="image"><img src="/workshops/ansible_tower_intro/images/at_credentials.png" alt="Cred" width="100" height="35"></span></p>
+<p>Select CREDENTIALS, from the left-side menu bar.   <span class="image"><img src="/workshops/ansible_tower_intro/images/at_credentials.png" alt="Cred" width="100" height="35"/></span></p>
 </div>
 <div class="paragraph">
 <p>You will see a lit of credentials, like the following:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_cred_list.png" alt="at cred list">
+<img src="/workshops/ansible_tower_intro/images/at_cred_list.png" alt="at cred list"/>
 </div>
 <div class="title">Figure 4: Ansible Tower Credentials</div>
 </div>
@@ -389,11 +389,11 @@ <h3 id="_step_1_view_available_credentials">Step 1: View Available Credentials</
 <div class="sect2">
 <h3 id="_step_2_view_credential_attributes">Step 2: View credential attributes</h3>
 <div class="paragraph">
-<p>Click the pencil icon <span class="image"><img src="/workshops/ansible_tower_intro/images/at_pencil_icon.png" alt="Cred" width="50" height="50"></span> to access the details of the <code>Workshop Credential</code> credential. Redundant, aren&#8217;t we?</p>
+<p>Click the pencil icon <span class="image"><img src="/workshops/ansible_tower_intro/images/at_pencil_icon.png" alt="Cred" width="50" height="50"/></span> to access the details of the <code>Workshop Credential</code> credential. Redundant, aren’t we?</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_cred_detail.png" alt="Cred_Detail" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_cred_detail.png" alt="Cred_Detail" width="700"/>
 </div>
 <div class="title">Figure 5: Reviewing a Credential</div>
 </div>
@@ -405,12 +405,12 @@ <h3 id="_step_3_cancel">Step 3: Cancel</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_cred_detail2.png" alt="Cred_Detail" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_cred_detail2.png" alt="Cred_Detail" width="700"/>
 </div>
 <div class="title">Figure 6: Reviewing a Credential, continued</div>
 </div>
 <div class="paragraph">
-<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_cancel.png" alt="Cancel" width="105" height="58"></span> to exit.</p>
+<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_cancel.png" alt="Cancel" width="105" height="58"/></span> to exit.</p>
 </div>
 </div>
 </div>
@@ -424,7 +424,7 @@ <h2 id="_section_3_reviewing_a_project">Section 3: Reviewing a Project</h2>
 <div class="sect2">
 <h3 id="_step_1_open_a_project">Step 1: Open a project</h3>
 <div class="paragraph">
-<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_projects.png" alt="Projects" width="125" height="35"></span> from the left-side menu.</p>
+<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_projects.png" alt="Projects" width="125" height="35"/></span> from the left-side menu.</p>
 </div>
 </div>
 <div class="sect2">
@@ -434,7 +434,7 @@ <h3 id="_step_2_review_the_list_of_projects">Step 2: Review the list of projects
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_project_list.png" alt="Project_List" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_project_list.png" alt="Project_List" width="700"/>
 </div>
 <div class="title">Figure 7: Project List</div>
 </div>
@@ -446,7 +446,7 @@ <h3 id="_step_3_view_the_project_form">Step 3: View the Project Form</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_project_detail.png" alt="Project_Detail" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_project_detail.png" alt="Project_Detail" width="700"/>
 </div>
 <div class="title">Figure 8: Reviewing a Project</div>
 </div>
@@ -454,7 +454,7 @@ <h3 id="_step_3_view_the_project_form">Step 3: View the Project Form</h3>
 <div class="sect2">
 <h3 id="_step_4_cancel">Step 4: Cancel</h3>
 <div class="paragraph">
-<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_cancel.png" alt="Cancel" width="105" height="58"></span> to exit.</p>
+<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_cancel.png" alt="Cancel" width="105" height="58"/></span> to exit.</p>
 </div>
 </div>
 </div>
@@ -474,14 +474,14 @@ <h2 id="_section_4_reviewing_an_inventory">Section 4: Reviewing an Inventory</h2
 <div class="sect2">
 <h3 id="_step_1_navigate_to_inventories_main_link">Step 1: Navigate to Inventories main link</h3>
 <div class="paragraph">
-<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_inv_icon.png" alt="Inventories" width="149" height="32"></span> from the left-side menu.</p>
+<p>Select <span class="image"><img src="/workshops/ansible_tower_intro/images/at_inv_icon.png" alt="Inventories" width="149" height="32"/></span> from the left-side menu.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_review_the_inventory_list">Step 2: Review the inventory list</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_inventory_list.png" alt="Inventory_List" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_inventory_list.png" alt="Inventory_List" width="700"/>
 </div>
 <div class="title">Figure 9: Inventory List</div>
 </div>
@@ -493,25 +493,25 @@ <h3 id="_step_3_complete_the_inventory_form">Step 3: Complete the Inventory form
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_inv_detail.png" alt="Inventory_Details" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_inv_detail.png" alt="Inventory_Details" width="700"/>
 </div>
 <div class="title">Figure 10: Inventory Details</div>
 </div>
 <div class="paragraph">
-<p>You can click on <span class="image"><img src="/workshops/ansible_tower_intro/images/at_hosts_icon.png" alt="Hosts" width="108" height="50"></span> to see the list of hosts:</p>
+<p>You can click on <span class="image"><img src="/workshops/ansible_tower_intro/images/at_hosts_icon.png" alt="Hosts" width="108" height="50"/></span> to see the list of hosts:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_inventory_hosts.png" alt="Inventory_Details" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_inventory_hosts.png" alt="Inventory_Details" width="700"/>
 </div>
 <div class="title">Figure 11: Inventory Hosts</div>
 </div>
 <div class="paragraph">
-<p>You can click on <span class="image"><img src="/workshops/ansible_tower_intro/images/at_groups_icon.png" alt="Groups" width="108" height="50"></span> to see the list of groups:</p>
+<p>You can click on <span class="image"><img src="/workshops/ansible_tower_intro/images/at_groups_icon.png" alt="Groups" width="108" height="50"/></span> to see the list of groups:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_tower_intro/images/at_inventory_groups.png" alt="Inventory_Details" width="700">
+<img src="/workshops/ansible_tower_intro/images/at_inventory_groups.png" alt="Inventory_Details" width="700"/>
 </div>
 <div class="title">Figure 12: Inventory Groups</div>
 </div>
@@ -621,7 +621,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -881,7 +881,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -993,7 +993,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1003,7 +1003,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1090,7 +1090,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_intro/exercise1.1/index.html b/workshops/ansible_tower_intro/exercise1.1/index.html
index 843378905..cbb1c48da 100644
--- a/workshops/ansible_tower_intro/exercise1.1/index.html
+++ b/workshops/ansible_tower_intro/exercise1.1/index.html
@@ -324,7 +324,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>This exercise will walk you through the steps required to create a job template and run it.  A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.</p>
 </div>
 <div class="paragraph">
-<p>Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.  Templates also drive uniformity, by running templates exactly the same way every time. And, because we&#8217;re using templates, production responsibilities can be delegated to less experienced production personnel.</p>
+<p>Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.  Templates also drive uniformity, by running templates exactly the same way every time. And, because we’re using templates, production responsibilities can be delegated to less experienced production personnel.</p>
 </div>
 </div>
 </div>
@@ -334,13 +334,13 @@ <h2 id="_section1_creating_a_job_template">Section1: Creating a job template</h2
 <div class="sect2">
 <h3 id="_step_1_navigate_to_the_templates_tab">Step 1: Navigate to the Templates tab</h3>
 <div class="paragraph">
-<p>Select TEMPLATES <span class="image"><img src="/workshops/ansible_automation/images/at_templates.png" alt="temp" width="120" height="35"></span></p>
+<p>Select TEMPLATES <span class="image"><img src="/workshops/ansible_automation/images/at_templates.png" alt="temp" width="120" height="35"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_create_a_new_template">Step 2: Create a new template</h3>
 <div class="paragraph">
-<p>Click <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"></span> and select JOB TEMPLATE <span class="image"><img src="/workshops/ansible_automation/images/at_jobtemplate.png" alt="jobT" width="150" height="100"></span></p>
+<p>Click <span class="image"><img src="/workshops/ansible_automation/images/at_add.png" alt="Add" width="35" height="25"/></span> and select JOB TEMPLATE <span class="image"><img src="/workshops/ansible_automation/images/at_jobtemplate.png" alt="jobT" width="150" height="100"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -350,8 +350,8 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -404,7 +404,7 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_jt_detail.png" alt="at jt detail" width="700">
+<img src="/workshops/ansible_automation/images/at_jt_detail.png" alt="at jt detail" width="700"/>
 </div>
 <div class="title">Figure 11: Job Template Form</div>
 </div>
@@ -412,7 +412,7 @@ <h3 id="_step_3_complete_the_job_template_form">Step 3: Complete the job Templat
 <div class="sect2">
 <h3 id="_step_4_save">Step 4: Save</h3>
 <div class="paragraph">
-<p>Click SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save"></span> and then select ADD SURVEY <span class="image"><img src="/workshops/ansible_automation/images/at_addsurvey.png" alt="Add Survey"></span></p>
+<p>Click SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save"/></span> and then select ADD SURVEY <span class="image"><img src="/workshops/ansible_automation/images/at_addsurvey.png" alt="Add Survey"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -425,8 +425,8 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -451,13 +451,13 @@ <h3 id="_step_5_complete_survey">Step 5: Complete survey</h3>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">DEFAULT ANSWER</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Be creative, keep it clean, we&#8217;re all professionals here</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Be creative, keep it clean, we’re all professionals here</p></td>
 </tr>
 </tbody>
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_survey_detail.png" alt="at survey detail" width="500">
+<img src="/workshops/ansible_automation/images/at_survey_detail.png" alt="at survey detail" width="500"/>
 </div>
 <div class="title">Figure 12: Survey Form</div>
 </div>
@@ -471,13 +471,13 @@ <h3 id="_step_6_add_the_survey_input">Step 6: Add the survey input</h3>
 <div class="sect2">
 <h3 id="_step_7_save">Step 7: Save</h3>
 <div class="paragraph">
-<p>Select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span></p>
+<p>Select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_8_save_at_the_main_page">Step 8: Save at the main page</h3>
 <div class="paragraph">
-<p>Back on the main Job Template page, select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"></span> again.</p>
+<p>Back on the main Job Template page, select SAVE <span class="image"><img src="/workshops/ansible_automation/images/at_save.png" alt="Save" width="35" height="25"/></span> again.</p>
 </div>
 </div>
 </div>
@@ -486,7 +486,7 @@ <h3 id="_step_8_save_at_the_main_page">Step 8: Save at the main page</h3>
 <h2 id="_section_2_running_a_job_template">Section 2: Running a job template</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve sucessfully created your Job Template, you are ready to launch it.
+<p>Now that you’ve sucessfully created your Job Template, you are ready to launch it.
 You will be redirected to a job screen, which refreshes in realtime
 and displays the status of the job.</p>
 </div>
@@ -497,21 +497,21 @@ <h3 id="_step_1_select_the_template_tab">Step 1: Select the Template tab</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-Alternatively, if you haven&#8217;t navigated away from the job templates creation page, you can scroll down to see all existing job templates
+Alternatively, if you haven’t navigated away from the job templates creation page, you can scroll down to see all existing job templates
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_access_apache_basic_job_template">Step 2: Access Apache Basic Job Template</h3>
 <div class="paragraph">
-<p>Click the rocketship icon <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"></span> for the <strong>Apache Basic Job Template</strong></p>
+<p>Click the rocketship icon <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span> for the <strong>Apache Basic Job Template</strong></p>
 </div>
 </div>
 <div class="sect2">
@@ -521,7 +521,7 @@ <h3 id="_step_3_enter_test_message">Step 3: Enter test message</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_survey_prompt.png" alt="at survey prompt" width="800">
+<img src="/workshops/ansible_automation/images/at_survey_prompt.png" alt="at survey prompt" width="800"/>
 </div>
 <div class="title">Figure 13: Survey Prompt</div>
 </div>
@@ -529,7 +529,7 @@ <h3 id="_step_3_enter_test_message">Step 3: Enter test message</h3>
 <div class="sect2">
 <h3 id="_step_4_launch_the_job">Step 4: Launch the job</h3>
 <div class="paragraph">
-<p>Select LAUNCH <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"></span></p>
+<p>Select LAUNCH <span class="image"><img src="/workshops/ansible_automation/images/at_launch_icon.png" alt="Add" width="35" height="25"/></span></p>
 </div>
 </div>
 <div class="sect2">
@@ -538,11 +538,11 @@ <h3 id="_step_5_view_job_summary">Step 5: View job summary</h3>
 <p>Sit back, watch the magic happen</p>
 </div>
 <div class="paragraph">
-<p>One of the first things you will notice is the RESULTS section.  This section provides job details, such as who launched it, what playbook it&#8217;s running, what the status is, i.e. Pending, Running, or Complete.</p>
+<p>One of the first things you will notice is the RESULTS section.  This section provides job details, such as who launched it, what playbook it’s running, what the status is, i.e. Pending, Running, or Complete.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_job_status.png" alt="at job status">
+<img src="/workshops/ansible_automation/images/at_job_status.png" alt="at job status"/>
 </div>
 <div class="title">Figure 14: Job Summary</div>
 </div>
@@ -551,7 +551,7 @@ <h3 id="_step_5_view_job_summary">Step 5: View job summary</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_job_stdout.png" alt="at job stdout" width="700">
+<img src="/workshops/ansible_automation/images/at_job_stdout.png" alt="at job stdout" width="700"/>
 </div>
 <div class="title">Figure 15: Job Standard Output</div>
 </div>
@@ -571,7 +571,7 @@ <h3 id="_step_6_view_the_new_website">Step 6: View the new website</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/at_web_tm.png" alt="at web tm" width="700">
+<img src="/workshops/ansible_automation/images/at_web_tm.png" alt="at web tm" width="700"/>
 </div>
 <div class="title">Figure 16: New Website with Personalized Test Message</div>
 </div>
@@ -582,8 +582,8 @@ <h3 id="_step_6_view_the_new_website">Step 6: View the new website</h3>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point in the workshop, you&#8217;ve experienced the core functionality of Ansible Tower.  But wait&#8230;&#8203; there&#8217;s more!
-You&#8217;ve just begun to explore the possibilities of Ansible Core and Tower.  Take a look at the resources page in this guide, to explore some more features.</p>
+<p>At this point in the workshop, you’ve experienced the core functionality of Ansible Tower.  But wait…​ there’s more!
+You’ve just begun to explore the possibilities of Ansible Core and Tower.  Take a look at the resources page in this guide, to explore some more features.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -685,7 +685,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -945,7 +945,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1057,7 +1057,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1067,7 +1067,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1153,7 +1153,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_intro/index.html b/workshops/ansible_tower_intro/index.html
index 51bcfe421..4ce116b45 100644
--- a/workshops/ansible_tower_intro/index.html
+++ b/workshops/ansible_tower_intro/index.html
@@ -496,7 +496,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -756,7 +756,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -868,7 +868,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -878,7 +878,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -931,7 +931,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_intro/index.xml b/workshops/ansible_tower_intro/index.xml
index 1be46e024..a7b703496 100644
--- a/workshops/ansible_tower_intro/index.xml
+++ b/workshops/ansible_tower_intro/index.xml
@@ -4,57 +4,36 @@
     <title>Ansible Tower - an Introduction on Red Hat | Public Sector</title>
     <link>/workshops/ansible_tower_intro/</link>
     <description>Recent content in Ansible Tower - an Introduction on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/ansible_tower_intro/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/ansible_tower_intro/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Configuring Ansible Tower</title>
       <link>/workshops/ansible_tower_intro/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/exercise1.0/</guid>
-      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.
- There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.
-   Credentials
-  Projects
-  Inventory
-  Job Template
-     Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password provided by your instructor.</description>
+      <description>Exercise Description In this exercise, we are going to configure Red Hat Ansible Tower, so that we can run a playbook.&#xA;There are a number of constructs in the Ansible Tower UI that enable multi-tenancy, notifications, scheduling, etc. However, we are only going to focus on the key concepts required for this workshop today.&#xA;Credentials&#xA;Projects&#xA;Inventory&#xA;Job Template&#xA;Section 1: Logging into Ansible Tower and installing the license key Step 1: Log in To log in, use the username admin and and the password provided by your instructor.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Creating and Running a Job Template</title>
       <link>/workshops/ansible_tower_intro/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/exercise1.1/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.
- Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to create a job template and run it. A job template is a definition and set of parameters for running an Ansible job. In other words, a template combines an Ansible project playbook and the settings required to launch it, into one package.&#xA;Templates save setup time, for jobs that are launched repetitively. Once the template is set, it can be edited for future jobs, with different settings.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/ansible_tower_intro/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Ansible Tower Use this URL to access the Ansible Tower interface. Your instructor will provide the password, and the user ID is admin:</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Ansible Tower Use this URL to access the Ansible Tower interface. Your instructor will provide the password, and the user ID is admin:</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/ansible_tower_intro/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.
- What do you think? How can we help you understand Ansible Tower better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Ansible and Red Hat Ansible Tower that you can apply in your daily role.&#xA;What do you think? How can we help you understand Ansible Tower better?&#xA;Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your Ansible education.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/ansible_tower_intro/setup/index.html b/workshops/ansible_tower_intro/setup/index.html
index b74a9ab5b..7d2335a52 100644
--- a/workshops/ansible_tower_intro/setup/index.html
+++ b/workshops/ansible_tower_intro/setup/index.html
@@ -317,7 +317,7 @@ <h1>Setup</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/tower.002.png" alt="Tower">
+<img src="/workshops/ansible_automation/images/tower.002.png" alt="Tower"/>
 </div>
 </div>
 </div>
@@ -344,11 +344,11 @@ <h2 id="_accessing_ansible_tower">Accessing Ansible Tower</h2>
 <div class="sect2">
 <h3 id="_ensuring_workshop_success">Ensuring Workshop Success</h3>
 <div class="paragraph">
-<p>You know you were successful if you are able to browse to your Ansible Tower&#8217;s url and get something like this:</p>
+<p>You know you were successful if you are able to browse to your Ansible Tower’s url and get something like this:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_automation/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen">
+<img src="/workshops/ansible_automation/images/ansible-lab-figure01-logon-screen.png" alt="ansible lab figure01 logon screen"/>
 </div>
 <div class="title">Figure 2: Ansible Tower Login Screen</div>
 </div>
@@ -452,7 +452,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -712,7 +712,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -824,7 +824,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -834,7 +834,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -917,7 +917,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/ansible_tower_intro/wrapup/index.html b/workshops/ansible_tower_intro/wrapup/index.html
index 1d9f469d8..d204f62c8 100644
--- a/workshops/ansible_tower_intro/wrapup/index.html
+++ b/workshops/ansible_tower_intro/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrapup</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something valuable
+<p>That wraps up what we have planned for today.  We hope you’ve learned something valuable
 about Ansible and Red Hat Ansible Tower that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
@@ -331,7 +331,7 @@ <h1>Wrapup</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/ansible_ansible/images/redhat.svg" alt="redhat">
+<img src="/workshops/ansible_ansible/images/redhat.svg" alt="redhat"/>
 </div>
 </div>
 
@@ -369,7 +369,7 @@ <h1>Wrapup</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.0/index.html b/workshops/cloudforms41/exercise1.0/index.html
index 333a112a3..c026df3e1 100644
--- a/workshops/cloudforms41/exercise1.0/index.html
+++ b/workshops/cloudforms41/exercise1.0/index.html
@@ -406,7 +406,7 @@ <h3 id="step-5-experiment-with-widgets">Step 5: Experiment with widgets</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.1/index.html b/workshops/cloudforms41/exercise1.1/index.html
index 423928fb5..4a4c21e8d 100644
--- a/workshops/cloudforms41/exercise1.1/index.html
+++ b/workshops/cloudforms41/exercise1.1/index.html
@@ -433,7 +433,7 @@ <h3 id="step-3-view-provider-details">Step 3: View provider details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.10/index.html b/workshops/cloudforms41/exercise1.10/index.html
index ff7d9dd17..718a4267b 100644
--- a/workshops/cloudforms41/exercise1.10/index.html
+++ b/workshops/cloudforms41/exercise1.10/index.html
@@ -380,7 +380,7 @@ <h3 id="step-4-explore-the-details-and-selected-resources-tabs">Step 4. Explore
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.11/index.html b/workshops/cloudforms41/exercise1.11/index.html
index 10f61eb7e..6d4e616f3 100644
--- a/workshops/cloudforms41/exercise1.11/index.html
+++ b/workshops/cloudforms41/exercise1.11/index.html
@@ -397,7 +397,7 @@ <h3 id="step-5-observe-that-the-computed-rate-assignments-are-configured-for-the
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.12/index.html b/workshops/cloudforms41/exercise1.12/index.html
index 1f4ffb71c..467afdad0 100644
--- a/workshops/cloudforms41/exercise1.12/index.html
+++ b/workshops/cloudforms41/exercise1.12/index.html
@@ -381,7 +381,7 @@ <h3 id="step-2-select-the-report-tab-and-review-the-detailed-report">Step 2. Sel
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.13/index.html b/workshops/cloudforms41/exercise1.13/index.html
index a960bcde8..4fced58bc 100644
--- a/workshops/cloudforms41/exercise1.13/index.html
+++ b/workshops/cloudforms41/exercise1.13/index.html
@@ -379,7 +379,7 @@ <h2 id="section-2--review-information">Section 2:  Review Information</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.14/index.html b/workshops/cloudforms41/exercise1.14/index.html
index 2fd071bba..f92cfb0bb 100644
--- a/workshops/cloudforms41/exercise1.14/index.html
+++ b/workshops/cloudforms41/exercise1.14/index.html
@@ -448,7 +448,7 @@ <h3 id="step-4-assign-your-alert-profile">Step 4. Assign your alert profile:</h3
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.15/index.html b/workshops/cloudforms41/exercise1.15/index.html
index 2327092cb..70cefd774 100644
--- a/workshops/cloudforms41/exercise1.15/index.html
+++ b/workshops/cloudforms41/exercise1.15/index.html
@@ -375,7 +375,7 @@ <h3 id="step-2-explore-the-filtering-features-by-activating-and-deactivating-eac
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.16/index.html b/workshops/cloudforms41/exercise1.16/index.html
index f94e750e6..8b1f9a100 100644
--- a/workshops/cloudforms41/exercise1.16/index.html
+++ b/workshops/cloudforms41/exercise1.16/index.html
@@ -386,7 +386,7 @@ <h3 id="step-5-explore-the-filtering-features-by-activating-and-deactivating-any
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.17/index.html b/workshops/cloudforms41/exercise1.17/index.html
index c3509bffd..0b4901ed5 100644
--- a/workshops/cloudforms41/exercise1.17/index.html
+++ b/workshops/cloudforms41/exercise1.17/index.html
@@ -381,19 +381,19 @@ <h3 id="step-2-try-using-the-up-and-down-arrows-to-switch-the-priority-of-a-doma
 <div class="panel panel-default">
   <div class="panel-heading">
     <h4 class="panel-title">
-<pre><code>  &lt;a data-toggle=&quot;collapse&quot; href=&quot;#collapsec7415b44347a4a2e6907ac4a3984a364&quot; class=&quot;collapsed&quot;&gt;
+<pre><code>  &lt;a data-toggle=&quot;collapse&quot; href=&quot;#collapse864223a9d4840c9012882a2f671063f2&quot; class=&quot;collapsed&quot;&gt;
   
     Importing/Exporting Domains
   &lt;/a&gt;
 &lt;/h4&gt;
 </code></pre>
   </div>
-  <div id="collapsec7415b44347a4a2e6907ac4a3984a364" class="panel-collapse collapse ">
+  <div id="collapse864223a9d4840c9012882a2f671063f2" class="panel-collapse collapse ">
 <pre><code>&lt;div class=&quot;panel-body&quot;&gt;
    &lt;p&gt;We can export domains using rake from the command line and import them either using rake or from the WebUI.  Using rake enables us to specify more import and export options.  A typical rake import line is as follows:&lt;/p&gt;
 </code></pre>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">bin/rake evm:automate:import YAML_FILE<span style="color:#f92672">=</span>bit63.yaml IMPORT_AS<span style="color:#f92672">=</span>Bit63 SYSTEM<span style="color:#f92672">=</span>false ENABLED<span style="color:#f92672">=</span>true DOMAIN<span style="color:#f92672">=</span>Export PREVIEW<span style="color:#f92672">=</span>false
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>bin/rake evm:automate:import YAML_FILE<span style="color:#f92672">=</span>bit63.yaml IMPORT_AS<span style="color:#f92672">=</span>Bit63 SYSTEM<span style="color:#f92672">=</span>false ENABLED<span style="color:#f92672">=</span>true DOMAIN<span style="color:#f92672">=</span>Export PREVIEW<span style="color:#f92672">=</span>false
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -426,21 +426,21 @@ <h4 class="panel-title">
 <div class="panel panel-default">
   <div class="panel-heading">
     <h4 class="panel-title">
-<pre><code>  &lt;a data-toggle=&quot;collapse&quot; href=&quot;#collapsef36e230838639eac66c1886ce90ef582&quot; class=&quot;collapsed&quot;&gt;
+<pre><code>  &lt;a data-toggle=&quot;collapse&quot; href=&quot;#collapse196a17def2f35f432d8a1e048b4ee865&quot; class=&quot;collapsed&quot;&gt;
   
     Importing Old Format Exports
   &lt;/a&gt;
 &lt;/h4&gt;
 </code></pre>
   </div>
-  <div id="collapsef36e230838639eac66c1886ce90ef582" class="panel-collapse collapse ">
+  <div id="collapse196a17def2f35f432d8a1e048b4ee865" class="panel-collapse collapse ">
 <pre><code>&lt;div class=&quot;panel-body&quot;&gt;
    &lt;p&gt;Domains were a new feature of the Automate Datastore in CloudForms 3.1.  All factory-supplied and user-created automation code was contained in a common structure prior to the CloudForms 3.1 release.  This made updates difficult when any user-added code was introduced.  User-supplied modifications needed to be exported and reimported/merged whenever an automation update was released.&lt;/p&gt;
 </code></pre>
 <p>To import a Datastore backup from a CloudForms 3.0 and prior format Datastore, we must convert it to the new Datastore format first, like so:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cd /var/www/miq/vmdb
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">bin/rake evm:automate:convert FILE<span style="color:#f92672">=</span>database.xml DOMAIN<span style="color:#f92672">=</span>SAMPLE ZIP_FILE<span style="color:#f92672">=</span>/tmp/sample_converted.zip
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cd /var/www/miq/vmdb
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>bin/rake evm:automate:convert FILE<span style="color:#f92672">=</span>database.xml DOMAIN<span style="color:#f92672">=</span>SAMPLE ZIP_FILE<span style="color:#f92672">=</span>/tmp/sample_converted.zip
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -536,32 +536,32 @@ <h2 id="section-6-instances">Section 6. Instances</h2>
 <h2 id="section-7-methods">Section 7. Methods</h2>
 <p>A <em>method</em> is a self-contained block of Ruby code that gets executed when we run any automation operation.  A typical method looks like this:</p>
 <!-- TODO configure ruby highlighting for the block of text below.  Specifying ruby results in very poor color contrast (light colors on light grey background) and significant reformatting of code -->
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-ruby" data-lang="ruby"><span style="color:#75715e">#</span>
-<span style="color:#75715e"># Description: This method checks to see if the VM has been powered off or suspended.</span>
-<span style="color:#75715e">#</span>
-
-<span style="color:#75715e"># Get vm from root object</span>
-vm <span style="color:#f92672">=</span> $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;vm&#39;</span><span style="color:#f92672">]</span>
-
-<span style="color:#66d9ef">if</span> vm
-  power_state <span style="color:#f92672">=</span> vm<span style="color:#f92672">.</span>attributes<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;power_state&#39;</span><span style="color:#f92672">]</span>
-  ems <span style="color:#f92672">=</span> vm<span style="color:#f92672">.</span>ext_management_system
-  $evm<span style="color:#f92672">.</span>log(<span style="color:#e6db74">&#39;info&#39;</span>, <span style="color:#e6db74">&#34;VM:&lt;</span><span style="color:#e6db74">#{</span>vm<span style="color:#f92672">.</span>name<span style="color:#e6db74">}</span><span style="color:#e6db74">&gt; on provider:&lt;</span><span style="color:#e6db74">#{</span>ems<span style="color:#f92672">.</span>try(<span style="color:#e6db74">:name</span>)<span style="color:#e6db74">}</span><span style="color:#e6db74"> has Power \
-</span><span style="color:#e6db74">           State:&lt;</span><span style="color:#e6db74">#{</span>power_state<span style="color:#e6db74">}</span><span style="color:#e6db74">&gt;&#34;</span>)
-
-  <span style="color:#75715e"># If VM is powered off or suspended exit</span>
-  <span style="color:#66d9ef">if</span> <span style="color:#e6db74">%w(off suspended)</span><span style="color:#f92672">.</span>include?(power_state)
-    <span style="color:#75715e"># Bump State</span>
-    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_result&#39;</span><span style="color:#f92672">]</span>         <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;ok&#39;</span>
-  <span style="color:#66d9ef">elsif</span> power_state <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;never&#34;</span>
-    <span style="color:#75715e"># If never then this VM is a template so exit the retirement state machine</span>
-    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_result&#39;</span><span style="color:#f92672">]</span>         <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;error&#39;</span>
-  <span style="color:#66d9ef">else</span>
-    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_result&#39;</span><span style="color:#f92672">]</span>         <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;retry&#39;</span>
-    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_retry_interval&#39;</span><span style="color:#f92672">]</span> <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;60.seconds&#39;</span>
-  <span style="color:#66d9ef">end</span>
-<span style="color:#66d9ef">end</span>
-</code></pre></div><p>Methods can have one of three <em>location</em> values: <em>inline</em>, <em>built-in</em>, or <em>URI</em>.  In practice most of the methods that we create are inline methods, which means they run as a separate Ruby process outside of Rails.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-ruby" data-lang="ruby"><span style="display:flex;"><span><span style="color:#75715e">#</span>
+</span></span><span style="display:flex;"><span><span style="color:#75715e"># Description: This method checks to see if the VM has been powered off or suspended.</span>
+</span></span><span style="display:flex;"><span><span style="color:#75715e">#</span>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#75715e"># Get vm from root object</span>
+</span></span><span style="display:flex;"><span>vm <span style="color:#f92672">=</span> $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;vm&#39;</span><span style="color:#f92672">]</span>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">if</span> vm
+</span></span><span style="display:flex;"><span>  power_state <span style="color:#f92672">=</span> vm<span style="color:#f92672">.</span>attributes<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;power_state&#39;</span><span style="color:#f92672">]</span>
+</span></span><span style="display:flex;"><span>  ems <span style="color:#f92672">=</span> vm<span style="color:#f92672">.</span>ext_management_system
+</span></span><span style="display:flex;"><span>  $evm<span style="color:#f92672">.</span>log(<span style="color:#e6db74">&#39;info&#39;</span>, <span style="color:#e6db74">&#34;VM:&lt;</span><span style="color:#e6db74">#{</span>vm<span style="color:#f92672">.</span>name<span style="color:#e6db74">}</span><span style="color:#e6db74">&gt; on provider:&lt;</span><span style="color:#e6db74">#{</span>ems<span style="color:#f92672">.</span>try(<span style="color:#e6db74">:name</span>)<span style="color:#e6db74">}</span><span style="color:#e6db74"> has Power \
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">           State:&lt;</span><span style="color:#e6db74">#{</span>power_state<span style="color:#e6db74">}</span><span style="color:#e6db74">&gt;&#34;</span>)
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>  <span style="color:#75715e"># If VM is powered off or suspended exit</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#66d9ef">if</span> <span style="color:#e6db74">%w(off suspended)</span><span style="color:#f92672">.</span>include?(power_state)
+</span></span><span style="display:flex;"><span>    <span style="color:#75715e"># Bump State</span>
+</span></span><span style="display:flex;"><span>    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_result&#39;</span><span style="color:#f92672">]</span>         <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;ok&#39;</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#66d9ef">elsif</span> power_state <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;never&#34;</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#75715e"># If never then this VM is a template so exit the retirement state machine</span>
+</span></span><span style="display:flex;"><span>    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_result&#39;</span><span style="color:#f92672">]</span>         <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;error&#39;</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#66d9ef">else</span>
+</span></span><span style="display:flex;"><span>    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_result&#39;</span><span style="color:#f92672">]</span>         <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;retry&#39;</span>
+</span></span><span style="display:flex;"><span>    $evm<span style="color:#f92672">.</span>root<span style="color:#f92672">[</span><span style="color:#e6db74">&#39;ae_retry_interval&#39;</span><span style="color:#f92672">]</span> <span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;60.seconds&#39;</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#66d9ef">end</span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">end</span>
+</span></span></code></pre></div><p>Methods can have one of three <em>location</em> values: <em>inline</em>, <em>built-in</em>, or <em>URI</em>.  In practice most of the methods that we create are inline methods, which means they run as a separate Ruby process outside of Rails.</p>
 <h2 id="summary">Summary</h2>
 <p>In this lab exercise we’ve learned about the fundamental objects or organizational units that we work with in the Automate Datastore: domains, namespaces, classes, instances, and methods.</p>
 <p>We are now ready to use this information to write our first automation script!</p>
@@ -604,7 +604,7 @@ <h2 id="summary">Summary</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.18/index.html b/workshops/cloudforms41/exercise1.18/index.html
index c3021aadf..2fbe84ffa 100644
--- a/workshops/cloudforms41/exercise1.18/index.html
+++ b/workshops/cloudforms41/exercise1.18/index.html
@@ -372,9 +372,9 @@ <h3 id="step-3-click-the-checkmark-in-the-lefthand-column-to-save-the-field-entr
 <em>Save schema field</em></p>
 <h1 id="hello-world">Hello, World!</h1>
 <h3 id="step-4-our-first-automate-method-is-very-simple-well-write-an-entry-to-the-automationlog-file-using-this-two-line-script">Step 4. Our first Automate method is very simple; we’ll write an entry to the <em>automation.log</em> file using this two-line script:</h3>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$evm.log<span style="color:#f92672">(</span>:info, <span style="color:#e6db74">&#34;Hello, World!&#34;</span><span style="color:#f92672">)</span>
-exit MIQ_OK
-</code></pre></div><h2 id="section-5-adding-a-new-instance">Section 5. Adding a New Instance</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$evm.log<span style="color:#f92672">(</span>:info, <span style="color:#e6db74">&#34;Hello, World!&#34;</span><span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>exit MIQ_OK
+</span></span></code></pre></div><h2 id="section-5-adding-a-new-instance">Section 5. Adding a New Instance</h2>
 <h3 id="step-1-first-we-need-to-create-an-instance-from-our-class--in-the-instances-tab-of-the-new-methods-class-select-configuration--add-a-new-instance">Step 1. First we need to create an instance from our class.  In the Instances tab of the new <em>Methods</em> class, select <strong>Configuration</strong> → <strong>Add a New Instance</strong>.</h3>
 <p><img title="CloudForms Top Window Navigation VM Providers" src="../images/cfme-nav-automate-add-new-instance.png" width="1000"/><br/>
 <em>Adding a new instance to our class</em></p>
@@ -407,14 +407,14 @@ <h3 id="step-1-well-run-our-new-instance-using-the-simulation-functionality-of-a
 </div>
 </p>
 <p>Alternatively, <em>ssh</em> into the CloudForms appliance as root and enter:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">tail -f /var/www/miq/vmdb/log/automation.log
-</code></pre></div><p>In the simulation, we actually run an instance called Call_Instance in the <em>/System/Request/</em> namespace of the <em>ManageIQ</em> domain, and this in turn calls our <em>HelloWorld</em> instance using the namespace, class, and instance attribute/value pairs that we pass to it.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>tail -f /var/www/miq/vmdb/log/automation.log
+</span></span></code></pre></div><p>In the simulation, we actually run an instance called Call_Instance in the <em>/System/Request/</em> namespace of the <em>ManageIQ</em> domain, and this in turn calls our <em>HelloWorld</em> instance using the namespace, class, and instance attribute/value pairs that we pass to it.</p>
 <h3 id="step-2-from-the-automate--simulation-menu-complete-the-details">Step 2. From the <strong>Automate</strong> → <strong>Simulation</strong> menu, complete the details.</h3>
 <p><img title="CloudForms Top Window Navigation VM Providers" src="../images/cfme-nav-automate-simulation-helloworld.png" /><br/>
 <em>Completing the Simulation details</em></p>
 <h3 id="step-3-click-submit">Step 3. Click <strong>Submit</strong>.</h3>
 <p>If all went well, we should see our “Hello, World!” message appear in the <em>automation.log</em> file:</p>
-<pre><code>Invoking [inline] method [/ACME/General/Methods/hello_world] with inputs [{}]
+<pre tabindex="0"><code>Invoking [inline] method [/ACME/General/Methods/hello_world] with inputs [{}]
 &lt;AEMethod [/ACME/General/Methods/hello_world]&gt; Starting
 &lt;AEMethod hello_world&gt; Hello, World!
 &lt;AEMethod [/ACME/General/Methods/hello_world]&gt; Ending
@@ -426,7 +426,7 @@ <h3 id="step-3-click-submit">Step 3. Click <strong>Submit</strong>.</h3>
 <h2 id="section-8-exit-status-codes">Section 8: Exit Status Codes</h2>
 <p>In our example we used an exit status code of MIQ_OK.  Although with simple methods such as this we don’t strictly need to specify an exit code, it’s good practice to do so.  When we build more advanced multi-method classes and state machines, an exit code can signal an error condition to the Automation Engine so that action can be taken.</p>
 <p>There are four exit codes that we can use:</p>
-<pre><code>MIQ_OK (0)
+<pre tabindex="0"><code>MIQ_OK (0)
   Continues normal processing. This is logged to automation.log as:
   Method exited with rc=MIQ_OK
 MIQ_WARN(4)
@@ -487,7 +487,7 @@ <h1 id="summary">Summary</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.19/index.html b/workshops/cloudforms41/exercise1.19/index.html
index 0124ffa69..933eec024 100644
--- a/workshops/cloudforms41/exercise1.19/index.html
+++ b/workshops/cloudforms41/exercise1.19/index.html
@@ -354,24 +354,24 @@ <h2 id="section-1-enable-ansible-role">Section 1: Enable Ansible Role</h2>
 the Server Role for Embedded Ansible to On to enable the role.</p>
 <h2 id="section-2-configuration">Section 2: Configuration</h2>
 <h3 id="step-1-select-configuration">Step 1. Select Configuration</h3>
-<p><img src="../images/configure.png" width="300" /></p>
+<img src="../images/configure.png" width="300" />
 <h3 id="step-2-click-embedded-ansible---on">Step 2. Click Embedded Ansible -&gt; On</h3>
 <div class="alert alert-success">
 <p><span class="pficon pficon-ok"></span></p>
 <p>This should already be done for you.</p>
 </div>
-<p><img src="../images/configure2.png" width="1000" /></p>
-<p><img src="../images/configure3.png" width="650" /></p>
+<img src="../images/configure2.png" width="1000" />
+<img src="../images/configure3.png" width="650" />
 <h3 id="step-3-click-automate---ansible">Step 3. Click Automate -&gt; Ansible</h3>
 <p>You will now see Ansible Playbooks.  These playbooks are samples from <a href="https://github.com/jeromemarc/workflow-demo">GitHub</a></p>
-<p><img src="../images/ansible-playbooks.png" width="1000" /></p>
+<img src="../images/ansible-playbooks.png" width="1000" />
 <h2 id="section-3-playbook">Section 3: Playbook</h2>
 <h3 id="step-1-explore-the-first-playbook">Step 1. Explore the first Playbook</h3>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ManageIQ/create_user.yml
-</code></pre></div><p>From here we can see properties such as when it was uploaded and where the playbook came from.
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ManageIQ/create_user.yml
+</span></span></code></pre></div><p>From here we can see properties such as when it was uploaded and where the playbook came from.
 <img src="../images/ansible-playbooks2.png" width="1000" /></p>
 <p>If you click on &ldquo;Repository&rdquo; you can see even more detail about the Playbook.</p>
-<p><img src="../images/ansible-playbooks3.png" width="1000" /></p>
+<img src="../images/ansible-playbooks3.png" width="1000" />
 <p>Ansible is built into CloudForms so there is nothing to install.</p>
 <table>
 <thead>
@@ -397,15 +397,15 @@ <h3 id="step-1-explore-the-first-playbook">Step 1. Explore the first Playbook</h
 </table>
 <h3 id="step-2-add-credentials">Step 2. Add Credentials</h3>
 <p>Red Hat CloudForms can store credentials used by playbooks. Credentials saved in CloudForms are matched and executed with a playbook when run.</p>
-<p><img src="../images/ansible-creds.png" width="1000" /></p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Automate / Ansible / Credentials
-</code></pre></div><h3 id="step-3-explore-adding-a-new-credential">Step 3. Explore adding a new credential</h3>
+<img src="../images/ansible-creds.png" width="1000" />
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Automate / Ansible / Credentials
+</span></span></code></pre></div><h3 id="step-3-explore-adding-a-new-credential">Step 3. Explore adding a new credential</h3>
 <p>From here you would add a credential adding the Name and Type and actual credential.</p>
-<p><img src="../images/ansible-creds2.png" width="650" /></p>
+<img src="../images/ansible-creds2.png" width="650" />
 <h3 id="step-4-explore-your-new-ansible-service">Step 4. Explore your new Ansible Service</h3>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Services / My Services / Create CloudForms User
-</code></pre></div><p><img src="../images/ansible-create.png" width="1000" /></p>
-<p><img src="../images/ansible-create2.png" width="1000" /></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Services / My Services / Create CloudForms User
+</span></span></code></pre></div><img src="../images/ansible-create.png" width="1000" />
+<img src="../images/ansible-create2.png" width="1000" />
 <p>Now this Ansible Playbook can be offered up as a Service item with CloudForms controlling the access and lifecycle of the automation action.</p>
 <h1 id="summary">Summary</h1>
 <p>In this exercise we’ve seen how simple it is to add and use Ansible Playbooks. Ansible with it&rsquo;s 1300+ modules makes the sky the limit when it comes to automation actions you can perform or offer up as a service in CloudForms.</p>
@@ -448,7 +448,7 @@ <h1 id="summary">Summary</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.2/index.html b/workshops/cloudforms41/exercise1.2/index.html
index 86ed65ffc..c545d5343 100644
--- a/workshops/cloudforms41/exercise1.2/index.html
+++ b/workshops/cloudforms41/exercise1.2/index.html
@@ -488,7 +488,7 @@ <h3 id="step-2-check-the-box-next-to-any-host-but-do-not-select-the-host">Step 2
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.20/index.html b/workshops/cloudforms41/exercise1.20/index.html
index 2c749e5d0..2066133a6 100644
--- a/workshops/cloudforms41/exercise1.20/index.html
+++ b/workshops/cloudforms41/exercise1.20/index.html
@@ -352,8 +352,8 @@ <h2 id="exercise-description">Exercise Description</h2>
 </tbody>
 </table>
 <h2 id="section-1-explore-ansible-tower">Section 1: Explore Ansible Tower</h2>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Automate / Ansible Tower / Explore
-</code></pre></div><p><img src="../images/tower.png" width="1000" /></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Automate / Ansible Tower / Explore
+</span></span></code></pre></div><img src="../images/tower.png" width="1000" />
 <p>Red Hat CloudForms automatically updates its inventory from Ansible Tower. This includes system groups (known as Inventories in Ansible Tower), basic information about individual systems, and available Ansible Tower job templates to be executed from the service catalog or Automate.</p>
 <h2 id="section-2-explore-adding-an-ansible-tower-provider">Section 2: Explore adding an Ansible Tower Provider</h2>
 <table>
@@ -398,23 +398,23 @@ <h2 id="inventories">Inventories</h2>
 <p>Select your Ansible Tower provider to expand and list the inventory groups on that Ansible
 Tower system. The inventory groups can be expanded to view the systems contained within
 each group, as well as configuration details for these systems.</p>
-<p><img src="../images/inventory.png" width="1000" /></p>
+<img src="../images/inventory.png" width="1000" />
 <h2 id="playbookstemplates">Playbooks/Templates</h2>
 <p>You must first create the job template in Ansible Tower. The job templates are automatically discovered by Red Hat CloudForms when refreshing your Ansible Tower provider’s inventory.</p>
-<p><img src="../images/templates.png" width="1000" /></p>
+<img src="../images/templates.png" width="1000" />
 <p>You can execute an Ansible Tower playbook from Red Hat CloudForms by creating a service catalog item from an Ansible Tower job template.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Services / Catalog / Catalog Items
-</code></pre></div><p><img src="../images/tower1.png" width="1000" /></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Services / Catalog / Catalog Items
+</span></span></code></pre></div><img src="../images/tower1.png" width="1000" />
 <p>Now you can look at adding another Ansible Tower Playbook to the service catalog. When you check display in catalog your new service will show up in the self service catalog as a item a user can order.</p>
-<p><img src="../images/tower2.png" width="1000" /></p>
+<img src="../images/tower2.png" width="1000" />
 <h2 id="self-service-portal">Self Service Portal</h2>
 <p>To see the services that are in the service catalog, change the url to <a href="https://cf.db.redhatgov.io/self_service">https://cf.db.redhatgov.io/self_service</a>. By adding self_service to the end of the URL you will be directed to the user portal where you can order services from the service catalog.</p>
-<p><img src="../images/service.png" width="1000" /></p>
+<img src="../images/service.png" width="1000" />
 <p>Here we can see the Ansible Playbook for creating a new CloudForms user we viewed previously.</p>
-<p><img src="../images/service2.png" width="1000" /></p>
+<img src="../images/service2.png" width="1000" />
 <p>You can click on the playbook and see that there is basic info to fill out for the playbook and then you click order just like you are shopping on Amazon! Ansible Tower in the background will kickoff the playbook.</p>
-<p><img src="../images/service3.png" width="1000" /></p>
-<p><img src="../images/service4.png" width="1000" /></p>
+<img src="../images/service3.png" width="1000" />
+<img src="../images/service4.png" width="1000" />
 <h2 id="summary">Summary</h2>
 <p>In this exercise you got a overview of the integration with Ansible Tower and how you can take any playbook and offer it up as a service item in CloudForms.</p>
 
@@ -456,7 +456,7 @@ <h2 id="summary">Summary</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.3/index.html b/workshops/cloudforms41/exercise1.3/index.html
index 4195f4404..79aca5875 100644
--- a/workshops/cloudforms41/exercise1.3/index.html
+++ b/workshops/cloudforms41/exercise1.3/index.html
@@ -424,7 +424,7 @@ <h3 id="step-3-examine-the-on-screen-report-detailing-cpu-memory-disk-io-and-net
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.4/index.html b/workshops/cloudforms41/exercise1.4/index.html
index 4e9300862..2bf217bac 100644
--- a/workshops/cloudforms41/exercise1.4/index.html
+++ b/workshops/cloudforms41/exercise1.4/index.html
@@ -384,7 +384,7 @@ <h3 id="step-3-select-any-of-the-reports-and-observe-that-the-report-configurati
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.5/index.html b/workshops/cloudforms41/exercise1.5/index.html
index 97fd9c885..2c1ce6280 100644
--- a/workshops/cloudforms41/exercise1.5/index.html
+++ b/workshops/cloudforms41/exercise1.5/index.html
@@ -405,7 +405,7 @@ <h3 id="step-7-on-the-resulting-screen-observe-that-your-provision-request-appea
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.6/index.html b/workshops/cloudforms41/exercise1.6/index.html
index ac338e0ef..c997f022d 100644
--- a/workshops/cloudforms41/exercise1.6/index.html
+++ b/workshops/cloudforms41/exercise1.6/index.html
@@ -400,7 +400,7 @@ <h3 id="step-7-select-the-openstack-cloud-provider-and-click-the-relationships-t
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.7/index.html b/workshops/cloudforms41/exercise1.7/index.html
index c287fcf4b..5e791a14d 100644
--- a/workshops/cloudforms41/exercise1.7/index.html
+++ b/workshops/cloudforms41/exercise1.7/index.html
@@ -408,7 +408,7 @@ <h3 id="step-3-click-these-relationships-to-review-how-this-instance-relates-to-
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.8/index.html b/workshops/cloudforms41/exercise1.8/index.html
index 7a54ea67d..b613b3ee9 100644
--- a/workshops/cloudforms41/exercise1.8/index.html
+++ b/workshops/cloudforms41/exercise1.8/index.html
@@ -420,7 +420,7 @@ <h3 id="step-5-explore-the-data-provided">Step 5. Explore the data provided.</h3
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/exercise1.9/index.html b/workshops/cloudforms41/exercise1.9/index.html
index ea73879c2..171ba3e3b 100644
--- a/workshops/cloudforms41/exercise1.9/index.html
+++ b/workshops/cloudforms41/exercise1.9/index.html
@@ -394,7 +394,7 @@ <h3 id="step-3-click-the-request-you-just-made">Step 3. Click the request you ju
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/index.html b/workshops/cloudforms41/index.html
index 16a6d6d9b..150b6c15e 100644
--- a/workshops/cloudforms41/index.html
+++ b/workshops/cloudforms41/index.html
@@ -430,7 +430,7 @@ <h2 id="exercises">Exercises</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/index.xml b/workshops/cloudforms41/index.xml
index 0e302c282..6b506c471 100644
--- a/workshops/cloudforms41/index.xml
+++ b/workshops/cloudforms41/index.xml
@@ -4,266 +4,169 @@
     <title>CloudForms Workshops on Red Hat | Public Sector</title>
     <link>/workshops/cloudforms41/</link>
     <description>Recent content in CloudForms Workshops on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/cloudforms41/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/cloudforms41/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>CloudForms Workshop Prerequisites</title>
       <link>/workshops/cloudforms41/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/prerequisites/</guid>
-      <description>If we have provided a laptop or cloud environment to you for this workshop, the following steps are already set up for you. Please jump to Exercise 1.0
- Install git We will use a few git commands directly in some of the advanced labs, please make sure git is installed on your system. You can download the latest version here.
-Create GitHub account Create a FREE GitHub account by going to this link and following their step-by-step instructions.</description>
+      <description>If we have provided a laptop or cloud environment to you for this workshop, the following steps are already set up for you. Please jump to Exercise 1.0&#xA;Install git We will use a few git commands directly in some of the advanced labs, please make sure git is installed on your system. You can download the latest version here.&#xA;Create GitHub account Create a FREE GitHub account by going to this link and following their step-by-step instructions.</description>
     </item>
-    
     <item>
       <title>Exercise 1.0 - A Guided Tour of CloudForms</title>
       <link>/workshops/cloudforms41/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.0/</guid>
-      <description>Exercise 1.0: How to Access CloudForms Exercise Description This exercise provides a quick tour of the console to help you get familiar with the user interface, along with some key terminology we will use in subsequent workshop content. If you are already familiar with the basics of CloudForms you can skip this exercise — after making sure you can login.
-Key Terms Before sinking our teeth into Cloud Forms, it is important to understand some terminology.</description>
+      <description>Exercise 1.0: How to Access CloudForms Exercise Description This exercise provides a quick tour of the console to help you get familiar with the user interface, along with some key terminology we will use in subsequent workshop content. If you are already familiar with the basics of CloudForms you can skip this exercise — after making sure you can login.&#xA;Key Terms Before sinking our teeth into Cloud Forms, it is important to understand some terminology.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Explore Your First Infrastructure Provider</title>
       <link>/workshops/cloudforms41/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.1/</guid>
-      <description>Exercise 1.1: Working with Infrastructure Providers Exercise Description Learn to view, search and manage infrastructure providers, in Red Hat CloudForms.
-In Red Hat CloudForms, an infrastructure provider is a virtual infrastructure environment that you can add to a Red Hat CloudForms appliance, to manage and interact with the resources, in that environment.
-In other words, a infrastructure provider is a management platform for managing virtual machines from a single type of hypervisor.</description>
+      <description>Exercise 1.1: Working with Infrastructure Providers Exercise Description Learn to view, search and manage infrastructure providers, in Red Hat CloudForms.&#xA;In Red Hat CloudForms, an infrastructure provider is a virtual infrastructure environment that you can add to a Red Hat CloudForms appliance, to manage and interact with the resources, in that environment.&#xA;In other words, a infrastructure provider is a management platform for managing virtual machines from a single type of hypervisor.</description>
     </item>
-    
     <item>
       <title>Exercise 1.10 - Explore Catalog Configuration</title>
       <link>/workshops/cloudforms41/exercise1.10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.10/</guid>
-      <description>Log in to CloudForms using the admin account (if not done already).
- Exercise 1.10 - Explore Catalog Configuration Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs.  Services Catalog
-Step 2. Select the Catalog Items accordion.  Services Catalog Items
-Step 3. Select All Catalog Items → VMware Operations → Deploy Ticket Monster on VMware  Services Catalog Ticket Monster
-Step 4. Explore the Details and Selected Resources tabs.</description>
+      <description>Log in to CloudForms using the admin account (if not done already).&#xA;Exercise 1.10 - Explore Catalog Configuration Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs. Services Catalog&#xA;Step 2. Select the Catalog Items accordion. Services Catalog Items&#xA;Step 3. Select All Catalog Items → VMware Operations → Deploy Ticket Monster on VMware Services Catalog Ticket Monster&#xA;Step 4. Explore the Details and Selected Resources tabs. In a live environment, this tab displays details about the item the user is ordering.</description>
     </item>
-    
     <item>
       <title>Exercise 1.11 - Explore Chargeback</title>
       <link>/workshops/cloudforms41/exercise1.11/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.11/</guid>
-      <description>Exercise 1.11 - Explore Chargeback Exercise Description In Red Hat CloudForms, the chargeback feature of CloudForms Management Engine (CFME) enables you to calculate monetary virtual machine charges, based on owner or company tag. In this exercise you will learn how to review chargebacks, and explore related reports, rates and assignments.
-Section 1: Explore Chargebacks CloudForms Management Engine provides a default set of rates for calculating chargeback costs, but you can create your own set of computing and storage costs, as well.</description>
+      <description>Exercise 1.11 - Explore Chargeback Exercise Description In Red Hat CloudForms, the chargeback feature of CloudForms Management Engine (CFME) enables you to calculate monetary virtual machine charges, based on owner or company tag. In this exercise you will learn how to review chargebacks, and explore related reports, rates and assignments.&#xA;Section 1: Explore Chargebacks CloudForms Management Engine provides a default set of rates for calculating chargeback costs, but you can create your own set of computing and storage costs, as well.</description>
     </item>
-    
     <item>
       <title>Exercise 1.12 - Explore Utilization</title>
       <link>/workshops/cloudforms41/exercise1.12/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.12/</guid>
-      <description>Exercise 1.12 - Explore Utilization Exercise Description CloudForms Management Engine server can collect and analyze capacity and utilization data from your virtual infrastructure. In this exercise, you will learn how to view utilization metrics.
-Section 1: Explore Utilization Step 1. Select Optimize → Utilization.  Utilization
-Step 2. Select Region 10 → Cloud/Infrastructure Providers → RHV-M.  Region 10 RHV-M Utilization
-Step 3. On the Summary tab, review the daily utilization chart.</description>
+      <description>Exercise 1.12 - Explore Utilization Exercise Description CloudForms Management Engine server can collect and analyze capacity and utilization data from your virtual infrastructure. In this exercise, you will learn how to view utilization metrics.&#xA;Section 1: Explore Utilization Step 1. Select Optimize → Utilization. Utilization&#xA;Step 2. Select Region 10 → Cloud/Infrastructure Providers → RHV-M. Region 10 RHV-M Utilization&#xA;Step 3. On the Summary tab, review the daily utilization chart. Step 4.</description>
     </item>
-    
     <item>
       <title>Exercise 1.13 - Explore Planning</title>
       <link>/workshops/cloudforms41/exercise1.13/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.13/</guid>
-      <description>Exercise 1.13 - Explore Planning Exercise Description In this exercise you will learn how to plan and optimize a deployment.
-Section 1: Explore Planning Step 1. Select Optimize → Planning.  Optimize Planning
-Step 2. Under Reference VM Selection, select All VMs.  Reference VM Selection
-Step 3. Choose the CFME027 VM. Step 4. Under VM Options, set the Source to Usage. Step 5. Under Target Options/Limits, set Show to Hosts.</description>
+      <description>Exercise 1.13 - Explore Planning Exercise Description In this exercise you will learn how to plan and optimize a deployment.&#xA;Section 1: Explore Planning Step 1. Select Optimize → Planning. Optimize Planning&#xA;Step 2. Under Reference VM Selection, select All VMs. Reference VM Selection&#xA;Step 3. Choose the CFME027 VM. Step 4. Under VM Options, set the Source to Usage. Step 5. Under Target Options/Limits, set Show to Hosts. Step 6.</description>
     </item>
-    
     <item>
       <title>Exercise 1.14 - Examine Policies</title>
       <link>/workshops/cloudforms41/exercise1.14/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.14/</guid>
-      <description>Exercise 1.14 - Examine Policies Exercise Description Policy profiles are groups of policies that you can apply to entities within CloudForms. Two common types of policies are Compliance policies, which check for a specific state in a host or VM, and Control policies, which control a host or VM, depending on certain criteria.
-In this exercise, you will learn how to work with policies, events, conditions, actions, alerts, and profiles.</description>
+      <description>Exercise 1.14 - Examine Policies Exercise Description Policy profiles are groups of policies that you can apply to entities within CloudForms. Two common types of policies are Compliance policies, which check for a specific state in a host or VM, and Control policies, which control a host or VM, depending on certain criteria.&#xA;In this exercise, you will learn how to work with policies, events, conditions, actions, alerts, and profiles.</description>
     </item>
-    
     <item>
       <title>Exercise 1.15 - Explore Network Topology</title>
       <link>/workshops/cloudforms41/exercise1.15/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.15/</guid>
       <description>Exercise 1.15 - Explore Network Topology Exercise Description When working in complex provider environments, with many objects, Red Hat CloudForms topology feature can be extremely useful, to quickly view and categorize information. The topology view enables you to view a container provider’s objects, plus their details, such as the properties, status, and relationships to other provider objects. In this exercise, you will learn how to explore the topology of a network.</description>
     </item>
-    
     <item>
       <title>Exercise 1.16 - Explore Containers</title>
       <link>/workshops/cloudforms41/exercise1.16/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.16/</guid>
-      <description>Exercise 1.16 - Explore Containers Exercise Description In this exercise we will take a general overview of containers and how you will work with them in Red Hat CloudForms.
-First, it is important to know the definition of a container: A container is an application sandbox that wraps your software in a complete filesystem, containing everything it needs to run.
- Traditional OS vs. Containers
-Exploring Containers Step 1. Go to Compute → Containers.</description>
+      <description>Exercise 1.16 - Explore Containers Exercise Description In this exercise we will take a general overview of containers and how you will work with them in Red Hat CloudForms.&#xA;First, it is important to know the definition of a container: A container is an application sandbox that wraps your software in a complete filesystem, containing everything it needs to run.&#xA;Traditional OS vs. Containers&#xA;Exploring Containers Step 1. Go to Compute → Containers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.17 - Introduction to the Automate Datastore</title>
       <link>/workshops/cloudforms41/exercise1.17/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.17/</guid>
-      <description>Exercise 1.17 - Introduction to the Automate Datastore Exercise Description In this exercise, you will learn about scripting actions, used to control automation datastore functions.
-When we use the Automate capability of CloudForms, we write scripts in the Ruby language and use objects that the CloudForms Automation Engine makes available to us. The Automate model is arranged to provide an object oriented hierarchy to control automation functions. The model uses the following organizational units arranged in a hierarchy:</description>
+      <description>Exercise 1.17 - Introduction to the Automate Datastore Exercise Description In this exercise, you will learn about scripting actions, used to control automation datastore functions.&#xA;When we use the Automate capability of CloudForms, we write scripts in the Ruby language and use objects that the CloudForms Automation Engine makes available to us. The Automate model is arranged to provide an object oriented hierarchy to control automation functions. The model uses the following organizational units arranged in a hierarchy:</description>
     </item>
-    
     <item>
       <title>Exercise 1.18 - “Hello, World!” Automation Script</title>
       <link>/workshops/cloudforms41/exercise1.18/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.18/</guid>
-      <description>Exercise 1.18 - “Hello, World!” Automation Script Exercise Description Let’s jump right in and start writing our first automation script. In time-honored fashion we’ll write “Hello, World!” to the Automate Engine logfile.
-Before we do anything, we need to ensure that the Automation Engine server role is selected on our CloudForms appliance. We do this from the Configure → Configuration menu, selecting the CloudForms server in the Settings accordion.
-  The Automation Engine server role is now enabled by default in CloudForms 4.</description>
+      <description>Exercise 1.18 - “Hello, World!” Automation Script Exercise Description Let’s jump right in and start writing our first automation script. In time-honored fashion we’ll write “Hello, World!” to the Automate Engine logfile.&#xA;Before we do anything, we need to ensure that the Automation Engine server role is selected on our CloudForms appliance. We do this from the Configure → Configuration menu, selecting the CloudForms server in the Settings accordion.&#xA;The Automation Engine server role is now enabled by default in CloudForms 4.</description>
     </item>
-    
     <item>
       <title>Exercise 1.19 - Ansible Inside</title>
       <link>/workshops/cloudforms41/exercise1.19/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.19/</guid>
-      <description>Exercise 1.19 - Ansible Inside Exercise Description Red Hat Ansible integration delivers out-of-the-box support for backing service, alert and policy actions using Ansible playbooks. Sync your existing playbook repositories with CloudForms, add credentials to access providers, and create service catalog items for actions ranging from creating and retiring VMs, updating security software, or adding additional disks when space runs low.
-Ansible integrates with Red Hat CloudForms to provide automation solutions, using playbooks, for Service, Policy and Alert actions.</description>
+      <description>Exercise 1.19 - Ansible Inside Exercise Description Red Hat Ansible integration delivers out-of-the-box support for backing service, alert and policy actions using Ansible playbooks. Sync your existing playbook repositories with CloudForms, add credentials to access providers, and create service catalog items for actions ranging from creating and retiring VMs, updating security software, or adding additional disks when space runs low.&#xA;Ansible integrates with Red Hat CloudForms to provide automation solutions, using playbooks, for Service, Policy and Alert actions.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Discovering Virtualization Host Systems</title>
       <link>/workshops/cloudforms41/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.2/</guid>
-      <description>Exercise 1.2 - Discovering Virtualization Host Systems Exercise Description In this exercise, you will learn how to view, search and manage host systems.
-In Red Hat CloudForms, hosts are hypervisors running on physical hardware providing virtual machines and infrastructure.
-The CloudForms Management Engine automatically adds hosts from discovered providers. However, you can also discover hosts directly if not using a provider. Discovering hosts is only supported for standalone VMware vSphere servers.</description>
+      <description>Exercise 1.2 - Discovering Virtualization Host Systems Exercise Description In this exercise, you will learn how to view, search and manage host systems.&#xA;In Red Hat CloudForms, hosts are hypervisors running on physical hardware providing virtual machines and infrastructure.&#xA;The CloudForms Management Engine automatically adds hosts from discovered providers. However, you can also discover hosts directly if not using a provider. Discovering hosts is only supported for standalone VMware vSphere servers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.20 - Ansible Tower</title>
       <link>/workshops/cloudforms41/exercise1.20/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.20/</guid>
-      <description>Ansible Tower Exercise Description Ansible Tower is a management tool integrated with Red Hat CloudForms, designed to help automate infrastructure operations. Red Hat CloudForms allows you to execute Ansible Tower jobs using service catalogs and Automate. No custom configuration or Ruby scripting is needed in Red Hat CloudForms, as configuration is done in Ansible Tower using playbooks.
-You can use the large library of existing Ansible playbooks as Red Hat CloudForms state machines to automate tasks such as backups, package updates, and maintenance in your Red Hat CloudForms environment.</description>
+      <description>Ansible Tower Exercise Description Ansible Tower is a management tool integrated with Red Hat CloudForms, designed to help automate infrastructure operations. Red Hat CloudForms allows you to execute Ansible Tower jobs using service catalogs and Automate. No custom configuration or Ruby scripting is needed in Red Hat CloudForms, as configuration is done in Ansible Tower using playbooks.&#xA;You can use the large library of existing Ansible playbooks as Red Hat CloudForms state machines to automate tasks such as backups, package updates, and maintenance in your Red Hat CloudForms environment.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Discovering VM Systems</title>
       <link>/workshops/cloudforms41/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.3/</guid>
-      <description>Exercise 1.3 - Discovering VM Systems Exercise Description In Red Hat CloudForms, infrastructure VMs are operating systems running under a hypervisor. This exercise will enable you to view and manage infrastructure VMs.
-Section 1: Explore Infrastructure VMs Step 1: Select Compute → Infrastructure → Virtual Machines.  Infrastructure VMs
-Step 2: View the list of your private datacenter’s infrastructure virtual machines. Section 2: Explore the Virtual Thumbnail for Infrastructure VMs The web interface uses virtual thumbnails to represent providers.</description>
+      <description>Exercise 1.3 - Discovering VM Systems Exercise Description In Red Hat CloudForms, infrastructure VMs are operating systems running under a hypervisor. This exercise will enable you to view and manage infrastructure VMs.&#xA;Section 1: Explore Infrastructure VMs Step 1: Select Compute → Infrastructure → Virtual Machines. Infrastructure VMs&#xA;Step 2: View the list of your private datacenter’s infrastructure virtual machines. Section 2: Explore the Virtual Thumbnail for Infrastructure VMs The web interface uses virtual thumbnails to represent providers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Explore Reports</title>
       <link>/workshops/cloudforms41/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.4/</guid>
-      <description>Exercise 1.4 - Explore Reports Exercise Description In this exercise, you will learn how to view, search and customize reports.
-In Red Hat CloudForms, reports have been constructed to help you view the most commonly requested and significant data. With appropriate access credentials, you can also create reports. CloudForms Management Engine provides a large group of default reports, organized into categories. Each category has a set of subfolders.
-Section 1: Explore Reports Step 1: Select Cloud Intel → Reports.</description>
+      <description>Exercise 1.4 - Explore Reports Exercise Description In this exercise, you will learn how to view, search and customize reports.&#xA;In Red Hat CloudForms, reports have been constructed to help you view the most commonly requested and significant data. With appropriate access credentials, you can also create reports. CloudForms Management Engine provides a large group of default reports, organized into categories. Each category has a set of subfolders.&#xA;Section 1: Explore Reports Step 1: Select Cloud Intel → Reports.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Examine Infrastructure Provisioning</title>
       <link>/workshops/cloudforms41/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.5/</guid>
-      <description>Exercise 1.5: Examine Infrastructure Provisioning Exercise Description Learn to provision infrastructures, using Red Hat CloudForms. CloudForms enables provisioning and management across physical, virtual, and private cloud platforms.
-Red Hat CloudForms Infrastructure Provisioning process (Summary) In Red Hat CloudForms, when a virtual machine or cloud instance is provisioned, it goes through multiple phases. First, the request must be made. The request includes ownership information, tags, virtual hardware requirements, the operating system, and any customization of the request.</description>
+      <description>Exercise 1.5: Examine Infrastructure Provisioning Exercise Description Learn to provision infrastructures, using Red Hat CloudForms. CloudForms enables provisioning and management across physical, virtual, and private cloud platforms.&#xA;Red Hat CloudForms Infrastructure Provisioning process (Summary) In Red Hat CloudForms, when a virtual machine or cloud instance is provisioned, it goes through multiple phases. First, the request must be made. The request includes ownership information, tags, virtual hardware requirements, the operating system, and any customization of the request.</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - Explore Cloud Providers</title>
       <link>/workshops/cloudforms41/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.6/</guid>
-      <description>Exercise 1.6 - Explore Cloud Providers Exercise Description This exercise will explain how to view cloud providers and related details.
-In Red Hat CloudForms, a cloud provider is a computing platform that manages instances and enables the creation of multi-tenant infrastructure services, independently from underlying hypervisors.
-Section 1: Explore Cloud Providers Step 1: Select Compute → Clouds → Providers.  Cloud Providers
-A list of your private and public cloud providers, such as OpenStack and Amazon EC2, displays.</description>
+      <description>Exercise 1.6 - Explore Cloud Providers Exercise Description This exercise will explain how to view cloud providers and related details.&#xA;In Red Hat CloudForms, a cloud provider is a computing platform that manages instances and enables the creation of multi-tenant infrastructure services, independently from underlying hypervisors.&#xA;Section 1: Explore Cloud Providers Step 1: Select Compute → Clouds → Providers. Cloud Providers&#xA;A list of your private and public cloud providers, such as OpenStack and Amazon EC2, displays.</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - Explore Cloud Instances</title>
       <link>/workshops/cloudforms41/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.7/</guid>
-      <description>#Exercise 1.7 - Explore Cloud Instances
-Exercise Description In Red Hat CloudForms, a cloud instance is a virtual machine running under cloud infrastructure. In this exercise, you will learn how to search for cloud instances and review the details related to the cloud instance.
-Section 1: Explore Cloud Instances &amp;gt; Select Compute → Clouds → Instances.  Cloud Instances
-A list of your public and private cloud instances displays.
-Section 2: Explore the Virtual Thumbnail for Cloud Instances The web interface uses virtual thumbnails to represent providers.</description>
+      <description>#Exercise 1.7 - Explore Cloud Instances&#xA;Exercise Description In Red Hat CloudForms, a cloud instance is a virtual machine running under cloud infrastructure. In this exercise, you will learn how to search for cloud instances and review the details related to the cloud instance.&#xA;Section 1: Explore Cloud Instances &amp;gt; Select Compute → Clouds → Instances. Cloud Instances&#xA;A list of your public and private cloud instances displays.&#xA;Section 2: Explore the Virtual Thumbnail for Cloud Instances The web interface uses virtual thumbnails to represent providers.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - Explore Group and User Access Controls</title>
       <link>/workshops/cloudforms41/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.8/</guid>
-      <description>Exercise 1.8 - Explore Group and User Access Controls Exercise Description This exercise is designed to provide an understanding of Red Hat CloudForms group controls and access controls.
-Section 1: Explore Access Control Step 1. Go to Administrator (in the top right corner of the screen) → Configuration and select the Access Control accordion.  Configuration Dashboard
- Access Control
-Step 2. Add a role by modifying a copy of an existing role: Step 3.</description>
+      <description>Exercise 1.8 - Explore Group and User Access Controls Exercise Description This exercise is designed to provide an understanding of Red Hat CloudForms group controls and access controls.&#xA;Section 1: Explore Access Control Step 1. Go to Administrator (in the top right corner of the screen) → Configuration and select the Access Control accordion. Configuration Dashboard&#xA;Access Control&#xA;Step 2. Add a role by modifying a copy of an existing role: Step 3.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - Introduction to Catalogs</title>
       <link>/workshops/cloudforms41/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/exercise1.9/</guid>
-      <description>The following steps are initially run as a non-admin customer account.
- Exercise 1.9 - Introduction to Catalogs Exercise Description This exercise enables you to explore and verify the catalog configuration.
-Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs.  Services Catalog
-Step 2. On the right, select the Deploy Ticket Monster on VMware catalog item.  Ticket Monster
-Step 3. Click Order to order the service.</description>
+      <description>The following steps are initially run as a non-admin customer account.&#xA;Exercise 1.9 - Introduction to Catalogs Exercise Description This exercise enables you to explore and verify the catalog configuration.&#xA;Section 1: Explore Catalog Configuration Step 1. Select Services → Catalogs. Services Catalog&#xA;Step 2. On the right, select the Deploy Ticket Monster on VMware catalog item. Ticket Monster&#xA;Step 3. Click Order to order the service. Step 4. Enter values for DBName and App Server Name and click Submit.</description>
     </item>
-    
     <item>
       <title>Workshop is Done</title>
       <link>/workshops/cloudforms41/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/wrapup/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the CloudForms environment. And hopefully, you have a deeper understanding of how CloudForms simplifies IT, providing unified management and operations in a hybrid environment.
-As your IT infrastructure progresses from traditional virtualization toward an Infrastructure-as-a-Service (IaaS) model, CloudForms evolves, protecting your investments and providing consistent user experience and functionality.
-Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore the web console.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the CloudForms environment. And hopefully, you have a deeper understanding of how CloudForms simplifies IT, providing unified management and operations in a hybrid environment.&#xA;As your IT infrastructure progresses from traditional virtualization toward an Infrastructure-as-a-Service (IaaS) model, CloudForms evolves, protecting your investments and providing consistent user experience and functionality.&#xA;Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore the web console.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/cloudforms41/prerequisites/index.html b/workshops/cloudforms41/prerequisites/index.html
index 383a7ce05..7aefb5a37 100644
--- a/workshops/cloudforms41/prerequisites/index.html
+++ b/workshops/cloudforms41/prerequisites/index.html
@@ -364,7 +364,7 @@ <h1 id="create-github-account">Create GitHub account</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/cloudforms41/wrapup/index.html b/workshops/cloudforms41/wrapup/index.html
index 45e267932..edb7c35fd 100644
--- a/workshops/cloudforms41/wrapup/index.html
+++ b/workshops/cloudforms41/wrapup/index.html
@@ -355,7 +355,7 @@ <h1 id="get-even-deeper">Get even deeper</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/exercise1.0/index.html b/workshops/containers_101/exercise1.0/index.html
index 263e30351..4cc3c4f98 100644
--- a/workshops/containers_101/exercise1.0/index.html
+++ b/workshops/containers_101/exercise1.0/index.html
@@ -351,7 +351,7 @@ <h3 id="_set_up_dependencies">Set up dependencies</h3>
 <h2 id="_install_buildah_skopeo_and_podman">Install Buildah, Skopeo, and Podman</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The Docker tooling requires a daemon (service) to operate. There are alternative command-line interface (CLI) tools, which provide focused separation of the Docker command&#8217;s features and extends their capabilities.  The following three commands will be used throughout this workshop.</p>
+<p>The Docker tooling requires a daemon (service) to operate. There are alternative command-line interface (CLI) tools, which provide focused separation of the Docker command’s features and extends their capabilities.  The following three commands will be used throughout this workshop.</p>
 </div>
 <div class="ulist">
 <ul>
@@ -471,7 +471,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -731,7 +731,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -843,7 +843,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -853,7 +853,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -939,7 +939,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/exercise1.1/index.html b/workshops/containers_101/exercise1.1/index.html
index d735d6f21..a416b427d 100644
--- a/workshops/containers_101/exercise1.1/index.html
+++ b/workshops/containers_101/exercise1.1/index.html
@@ -363,7 +363,7 @@ <h3 id="_step_1_use_the_following_command_to_pull_a_rhel_image_from_the_red_hat_
 <div class="sect2">
 <h3 id="_step_2_try_the_skopeo_command">Step 2. Try the Skopeo command</h3>
 <div class="paragraph">
-<p>Skopeo provides the ability to inspect containers stored in a registry. The Inspect feature displays details of the selected container. The 'skopeo inspect' command&#8217;s ability to list all the tags associated with a selected container is a benefit over the docker tool.</p>
+<p>Skopeo provides the ability to inspect containers stored in a registry. The Inspect feature displays details of the selected container. The &#39;skopeo inspect&#39; command’s ability to list all the tags associated with a selected container is a benefit over the docker tool.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -432,8 +432,8 @@ <h2 id="_section_2_inspecting_the_container_tools_environment">Section 2: Inspec
   GraphRoot: /var/lib/containers/storage
   GraphStatus:
     Backing Filesystem: xfs
-    Native Overlay Diff: "true"
-    Supports d_type: "true"
+    Native Overlay Diff: &#34;true&#34;
+    Supports d_type: &#34;true&#34;
   ImageStore:
     number: 0
   RunRoot: /var/run/containers/storage</pre>
@@ -539,7 +539,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -799,7 +799,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -911,7 +911,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -921,7 +921,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1007,7 +1007,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/exercise1.2/index.html b/workshops/containers_101/exercise1.2/index.html
index 42982ecdf..c0fcfd381 100644
--- a/workshops/containers_101/exercise1.2/index.html
+++ b/workshops/containers_101/exercise1.2/index.html
@@ -327,7 +327,7 @@ <h2 id="_exercise_1_2_working_with_container_images">Exercise 1.2 - Working with
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>In this exercise, you&#8217;ll learn the fundamentals of container images, including how to run them and how to see what is  inside of a container. Container storage volumes will be discussed, showing how to mount external file systems, with useful functions and data. We will also discuss container metadata and explain what types of information you can get from them.</p>
+<p>In this exercise, you’ll learn the fundamentals of container images, including how to run them and how to see what is  inside of a container. Container storage volumes will be discussed, showing how to mount external file systems, with useful functions and data. We will also discuss container metadata and explain what types of information you can get from them.</p>
 </div>
 </div>
 </div>
@@ -335,7 +335,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_container_images">Section 1: Container Images</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>What you can do with container images, using 'podman run'</p>
+<p>What you can do with container images, using &#39;podman run&#39;</p>
 </div>
 <div class="paragraph">
 <p>When you execute the <code>podman run</code> command, a new container is created, from a container image.  That container consists of the image contents, plus any features based on additional selected options.</p>
@@ -357,7 +357,7 @@ <h2 id="_section_1_container_images">Section 1: Container Images</h2>
 </ul>
 </div>
 <div class="paragraph">
-<p>Additionally you can also&#8230;&#8203;</p>
+<p>Additionally you can also…​</p>
 </div>
 <div class="ulist">
 <ul>
@@ -394,7 +394,7 @@ <h3 id="_step_1_launch_a_container_and_explore_inside_interactively">Step 1. Lau
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -409,7 +409,7 @@ <h3 id="_step_1_launch_a_container_and_explore_inside_interactively">Step 1. Lau
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -447,7 +447,7 @@ <h2 id="_section_2_container_storage_volumes">Section 2: Container Storage Volum
 <p>In this section, we will mount a system volume to a container and use commands that are not present in the container.</p>
 </div>
 <div class="paragraph">
-<p>Note: The following command will fail as the "ip" command is not present in the base rhel7 container image.</p>
+<p>Note: The following command will fail as the &#34;ip&#34; command is not present in the base rhel7 container image.</p>
 </div>
 <div class="sect2">
 <h3 id="_volume_mounts">Volume Mounts</h3>
@@ -455,14 +455,14 @@ <h3 id="_volume_mounts">Volume Mounts</h3>
 <p>Container images are very minimal installs of their referenced operating system, so commonly-used commands may not be present.</p>
 </div>
 <div class="listingblock">
-<div class="title">nonexistent command "lshw"</div>
+<div class="title">nonexistent command &#34;lshw&#34;</div>
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">podman run --rm -it ubi8/python-39 /usr/sbin/lshw</code></pre>
 </div>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>container create failed: container_linux.go:348: starting container process caused "exec: \"/usr/sbin/lshw\": stat /usr/sbin/lshw: no such file or directory"
+<pre>container create failed: container_linux.go:348: starting container process caused &#34;exec: \&#34;/usr/sbin/lshw\&#34;: stat /usr/sbin/lshw: no such file or directory&#34;
 : internal libpod error</pre>
 </div>
 </div>
@@ -503,7 +503,7 @@ <h3 id="_volume_mounts_continued">Volume Mounts (continued)</h3>
 <div class="listingblock">
 <div class="title">search the container host</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">journalctl | grep "Testing logging"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">journalctl | grep &#34;Testing logging&#34;</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -526,7 +526,7 @@ <h3 id="_persistent_container_data">Persistent Container Data</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">podman run -d -p 8080:8000 --name="python_web" \
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">podman run -d -p 8080:8000 --name=&#34;python_web&#34; \
        -w /opt \
        -v /opt/rhel_data:/var/www/html ubi8/python-39 \
        -- python -m http.server -d /var/www/html</code></pre>
@@ -571,7 +571,7 @@ <h3 id="_step_3_run_the_following_url_command_to_show_there_are_no_files_via_the
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"&gt;&lt;html&gt;
+<pre>&lt;!DOCTYPE html PUBLIC &#34;-//W3C//DTD HTML 3.2 Final//EN&#34;&gt;&lt;html&gt;
 &lt;title&gt;Directory listing for /&lt;/title&gt;
 &lt;body&gt;
 &lt;h2&gt;Directory listing for /&lt;/h2&gt;
@@ -624,22 +624,22 @@ <h3 id="_step_6_then_use_curl_to_view_the_files_from_the_python_webserver_that_i
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"&gt;&lt;html&gt;
+<pre>&lt;!DOCTYPE html PUBLIC &#34;-//W3C//DTD HTML 3.2 Final//EN&#34;&gt;&lt;html&gt;
 &lt;title&gt;Directory listing for /&lt;/title&gt;
 &lt;body&gt;
 &lt;h2&gt;Directory listing for /&lt;/h2&gt;
 &lt;hr&gt;
 &lt;ul&gt;
-&lt;li&gt;&lt;a href="file1"&gt;file1&lt;/a&gt;
-&lt;li&gt;&lt;a href="file10"&gt;file10&lt;/a&gt;
-&lt;li&gt;&lt;a href="file2"&gt;file2&lt;/a&gt;
-&lt;li&gt;&lt;a href="file3"&gt;file3&lt;/a&gt;
-&lt;li&gt;&lt;a href="file4"&gt;file4&lt;/a&gt;
-&lt;li&gt;&lt;a href="file5"&gt;file5&lt;/a&gt;
-&lt;li&gt;&lt;a href="file6"&gt;file6&lt;/a&gt;
-&lt;li&gt;&lt;a href="file7"&gt;file7&lt;/a&gt;
-&lt;li&gt;&lt;a href="file8"&gt;file8&lt;/a&gt;
-&lt;li&gt;&lt;a href="file9"&gt;file9&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file1&#34;&gt;file1&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file10&#34;&gt;file10&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file2&#34;&gt;file2&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file3&#34;&gt;file3&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file4&#34;&gt;file4&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file5&#34;&gt;file5&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file6&#34;&gt;file6&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file7&#34;&gt;file7&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file8&#34;&gt;file8&lt;/a&gt;
+&lt;li&gt;&lt;a href=&#34;file9&#34;&gt;file9&lt;/a&gt;
 &lt;/ul&gt;
 &lt;hr&gt;
 &lt;/body&gt;
@@ -663,28 +663,28 @@ <h2 id="_section_3_container_metadata">Section 3: Container metadata</h2>
 <div class="literalblock">
 <div class="content">
 <pre>[{
-    "ID": "fcd06aee95338748ab86faddd696c2cda212e7797b1e44428434da4a0d0b2b45",
-    "Created": "2018-05-23T17:21:40.315773016Z",
-    "Path": "python",
-    "Args": [
-      "-m",
-      "http.server",
-      "-d",
-      "/var/www/html"
+    &#34;ID&#34;: &#34;fcd06aee95338748ab86faddd696c2cda212e7797b1e44428434da4a0d0b2b45&#34;,
+    &#34;Created&#34;: &#34;2018-05-23T17:21:40.315773016Z&#34;,
+    &#34;Path&#34;: &#34;python&#34;,
+    &#34;Args&#34;: [
+      &#34;-m&#34;,
+      &#34;http.server&#34;,
+      &#34;-d&#34;,
+      &#34;/var/www/html&#34;
     ],
 ...
-    "Name": "python_web",
-    "RestartCount": 0,
-    "Driver": "overlay",
-    "MountLabel": "system_u:object_r:svirt_sandbox_file_t:s0:c744,c884",
-    "ProcessLabel": "system_u:system_r:svirt_lxc_net_t:s0:c744,c884",
+    &#34;Name&#34;: &#34;python_web&#34;,
+    &#34;RestartCount&#34;: 0,
+    &#34;Driver&#34;: &#34;overlay&#34;,
+    &#34;MountLabel&#34;: &#34;system_u:object_r:svirt_sandbox_file_t:s0:c744,c884&#34;,
+    &#34;ProcessLabel&#34;: &#34;system_u:system_r:svirt_lxc_net_t:s0:c744,c884&#34;,
 ...</pre>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_scripting_pro_tips">Scripting Pro Tips</h3>
 <div class="paragraph">
-<p>You can use a dot notation to parse the metadata returned by 'podman inspect' and use it in your scripting, to quickly access properties you need, as shown in the following example.</p>
+<p>You can use a dot notation to parse the metadata returned by &#39;podman inspect&#39; and use it in your scripting, to quickly access properties you need, as shown in the following example.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -852,7 +852,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1112,7 +1112,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1224,7 +1224,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1234,7 +1234,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1321,7 +1321,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/exercise1.3/index.html b/workshops/containers_101/exercise1.3/index.html
index 74966228d..7a1f8fd69 100644
--- a/workshops/containers_101/exercise1.3/index.html
+++ b/workshops/containers_101/exercise1.3/index.html
@@ -376,13 +376,13 @@ <h3 id="_step_2_review_the_container_contents">Step 2. Review the container cont
 RUN yum install -y postgresql-server
 USER postgres
 RUN /bin/initdb -D /var/lib/pgsql/data
-RUN /usr/bin/pg_ctl start -D /var/lib/pgsql/data -s -o "-p 5432" -w -t 300 &amp;&amp;\
-                /bin/psql --command "CREATE USER docker WITH SUPERUSER PASSWORD 'docker';" &amp;&amp;\
+RUN /usr/bin/pg_ctl start -D /var/lib/pgsql/data -s -o &#34;-p 5432&#34; -w -t 300 &amp;&amp;\
+                /bin/psql --command &#34;CREATE USER docker WITH SUPERUSER PASSWORD &#39;docker&#39;;&#34; &amp;&amp;\
                 /bin/createdb -O docker docker
-RUN echo "host all  all    0.0.0.0/0  md5" &gt;&gt; /var/lib/pgsql/data/pg_hba.conf
-RUN echo "listen_addresses='*'" &gt;&gt; /var/lib/pgsql/data/postgresql.conf
+RUN echo &#34;host all  all    0.0.0.0/0  md5&#34; &gt;&gt; /var/lib/pgsql/data/pg_hba.conf
+RUN echo &#34;listen_addresses=&#39;*&#39;&#34; &gt;&gt; /var/lib/pgsql/data/postgresql.conf
 EXPOSE 5432
-CMD ["/bin/postgres", "-D", "/var/lib/pgsql/data", "-c", "config_file=/var/lib/pgsql/data/postgresql.conf"]</pre>
+CMD [&#34;/bin/postgres&#34;, &#34;-D&#34;, &#34;/var/lib/pgsql/data&#34;, &#34;-c&#34;, &#34;config_file=/var/lib/pgsql/data/postgresql.conf&#34;]</pre>
 </div>
 </div>
 </div>
@@ -438,7 +438,7 @@ <h3 id="_step_5_examine_the_container_contents">Step 5. Examine the container co
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_6_lets_do_a_quick_check_to_see_what_databases_are_available">Step 6. Let&#8217;s do a quick check to see what databases are available:</h3>
+<h3 id="_step_6_lets_do_a_quick_check_to_see_what_databases_are_available">Step 6. Let’s do a quick check to see what databases are available:</h3>
 <div class="listingblock">
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">\l</code></pre>
@@ -568,7 +568,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -828,7 +828,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -940,7 +940,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -950,7 +950,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1037,7 +1037,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/exercise1.4/index.html b/workshops/containers_101/exercise1.4/index.html
index 9d5869e9c..825a852b0 100644
--- a/workshops/containers_101/exercise1.4/index.html
+++ b/workshops/containers_101/exercise1.4/index.html
@@ -347,7 +347,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>tightly control where your images are being stored</p>
 </li>
 <li>
-<p>fully own your image&#8217;s distribution pipeline</p>
+<p>fully own your image’s distribution pipeline</p>
 </li>
 <li>
 <p>integrate image storage and distribution tightly into your in-house development workflow</p>
@@ -368,7 +368,7 @@ <h3 id="_step_1_launch_a_docker_registry_image">Step 1. Launch a Docker registry
 <div class="sect2">
 <h3 id="_step_2_view_images_in_the_local_image_database">Step 2. View images in the local image database.</h3>
 <div class="paragraph">
-<p>Before we upload anything, let&#8217;s take a look to see what images we have in the local image database:</p>
+<p>Before we upload anything, let’s take a look to see what images we have in the local image database:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -390,7 +390,7 @@ <h3 id="_step_3_push_the_container_to_the_local_registry">Step 3. Push the conta
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
@@ -398,7 +398,7 @@ <h3 id="_step_3_push_the_container_to_the_local_registry">Step 3. Push the conta
 Choose only one of the following two commands (<code>buildah push</code> or <code>skopeo copy</code>).  Both accomplish the same purpose.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -410,7 +410,7 @@ <h3 id="_step_3_push_the_container_to_the_local_registry">Step 3. Push the conta
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -418,7 +418,7 @@ <h3 id="_step_3_push_the_container_to_the_local_registry">Step 3. Push the conta
 This image ID will vary, and you should use the value from the output produced on your workshop instance:
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -429,7 +429,7 @@ <h3 id="_step_3_push_the_container_to_the_local_registry">Step 3. Push the conta
 <div class="sect2">
 <h3 id="_step_4_verify_the_image_location_in_the_registry">Step 4. Verify the image location in the registry.</h3>
 <div class="paragraph">
-<p>Next, let&#8217;s search the registry to make sure that our image made it, and is available:</p>
+<p>Next, let’s search the registry to make sure that our image made it, and is available:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -542,7 +542,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -802,7 +802,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -914,7 +914,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -924,7 +924,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1011,7 +1011,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/index.html b/workshops/containers_101/index.html
index 34dcbe928..38b9dcf8e 100644
--- a/workshops/containers_101/index.html
+++ b/workshops/containers_101/index.html
@@ -296,7 +296,7 @@ <h2 id="_workshop_description">Workshop Description</h2>
 <h2 id="_who_should_attend">Who should attend</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Today&#8217;s container workshop is meant for anyone who has any exposure to Linux containers, whether you have used it or not.</p>
+<p>Today’s container workshop is meant for anyone who has any exposure to Linux containers, whether you have used it or not.</p>
 </div>
 </div>
 </div>
@@ -495,7 +495,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -755,7 +755,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -867,7 +867,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -877,7 +877,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -930,7 +930,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/index.xml b/workshops/containers_101/index.xml
index 7ab34113a..d7aa2d693 100644
--- a/workshops/containers_101/index.xml
+++ b/workshops/containers_101/index.xml
@@ -4,85 +4,57 @@
     <title>Containers 101 Workshop on Red Hat | Public Sector</title>
     <link>/workshops/containers_101/</link>
     <description>Recent content in Containers 101 Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/containers_101/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/containers_101/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Install buildah, skopeo, and podman</title>
       <link>/workshops/containers_101/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.0/</guid>
-      <description>Exercise 1.0: Installing Buildah, Skopeo and Podman Set up dependencies Elevate privileges
- In order to do any of the steps in the Containers 101 Workshop, you will need root privileges. There are two methods of doing this; the method you choose is up to you. Either method will work, but in a production environment, Method 2 is much more secure and auditable.
- Method 1: The first, and easiest, method is to start a root session, with sudo -i:</description>
+      <description>Exercise 1.0: Installing Buildah, Skopeo and Podman Set up dependencies Elevate privileges&#xA;In order to do any of the steps in the Containers 101 Workshop, you will need root privileges. There are two methods of doing this; the method you choose is up to you. Either method will work, but in a production environment, Method 2 is much more secure and auditable.&#xA;Method 1: The first, and easiest, method is to start a root session, with sudo -i:</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Pulling and Running Container Images</title>
       <link>/workshops/containers_101/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.1/</guid>
-      <description>Exercise 1.1 - Pulling Container Images   Section 1: Pull RHEL Images Step 1. Use the following command to pull a RHEL image from the Red Hat repository: podman pull command podman pull registry.access.redhat.com/ubi8   Images are accessed using the container registry URL (registry.access.redhat.com). If the container registry URL is not specified in the pull command, it could result in the retrieval of an image that originates from an untrusted registry.</description>
+      <description>Exercise 1.1 - Pulling Container Images Section 1: Pull RHEL Images Step 1. Use the following command to pull a RHEL image from the Red Hat repository: podman pull command podman pull registry.access.redhat.com/ubi8 Images are accessed using the container registry URL (registry.access.redhat.com). If the container registry URL is not specified in the pull command, it could result in the retrieval of an image that originates from an untrusted registry.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Working with Container Images</title>
       <link>/workshops/containers_101/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.2/</guid>
-      <description>Exercise 1.2 - Working with Container Images   Exercise Description In this exercise, you&amp;#8217;ll learn the fundamentals of container images, including how to run them and how to see what is inside of a container. Container storage volumes will be discussed, showing how to mount external file systems, with useful functions and data. We will also discuss container metadata and explain what types of information you can get from them.</description>
+      <description>Exercise 1.2 - Working with Container Images Exercise Description In this exercise, you’ll learn the fundamentals of container images, including how to run them and how to see what is inside of a container. Container storage volumes will be discussed, showing how to mount external file systems, with useful functions and data. We will also discuss container metadata and explain what types of information you can get from them.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Working with the Dockerfile</title>
       <link>/workshops/containers_101/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.3/</guid>
-      <description>Exercise 1.3 - Working with the Dockerfile   Exercise Description This exercise will enable you to use a Dockerfile to build a container. Once you understand how images and containers can be created from the command line, you can try building containers in a more permanent way.
- Building container images from Dockerfile files is, by far, the preferred way to create docker-formatted containers, as compared to modifying running containers and committing them to images.</description>
+      <description>Exercise 1.3 - Working with the Dockerfile Exercise Description This exercise will enable you to use a Dockerfile to build a container. Once you understand how images and containers can be created from the command line, you can try building containers in a more permanent way.&#xA;Building container images from Dockerfile files is, by far, the preferred way to create docker-formatted containers, as compared to modifying running containers and committing them to images.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Working with a Container Registry</title>
       <link>/workshops/containers_101/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/exercise1.4/</guid>
-      <description>Exercise 1.4 - Working with a Container Registry   Exercise Description In this exercise, you will learn container registry basics, what the registry offers and how to use it.
- What is container registry?
- A basic container registry is a stateless, highly scalable server side application that stores and distributes container images. The docker registry is an open-source project offered under the permissive Apache license.
- Why use container registries?</description>
+      <description>Exercise 1.4 - Working with a Container Registry Exercise Description In this exercise, you will learn container registry basics, what the registry offers and how to use it.&#xA;What is container registry?&#xA;A basic container registry is a stateless, highly scalable server side application that stores and distributes container images. The docker registry is an open-source project offered under the permissive Apache license.&#xA;Why use container registries?&#xA;You should use a private container registry if you want to:</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/containers_101/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/containers_101/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/wrapup/</guid>
-      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.
- What do you think? How can we better help you understand Linux container concepts?
- For more in depth overview and examples for working with containers and RHEL check out this link.
- Thank you for your time and participation!
-   </description>
+      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.&#xA;What do you think? How can we better help you understand Linux container concepts?&#xA;For more in depth overview and examples for working with containers and RHEL check out this link.&#xA;Thank you for your time and participation!</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/containers_101/setup/index.html b/workshops/containers_101/setup/index.html
index f7ec7ce3b..46dd3e555 100644
--- a/workshops/containers_101/setup/index.html
+++ b/workshops/containers_101/setup/index.html
@@ -337,8 +337,8 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -357,7 +357,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_101/images/cockpit_login.png" alt="cockpit login" height="500">
+<img src="/workshops/containers_101/images/cockpit_login.png" alt="cockpit login" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Login</div>
 </div>
@@ -366,21 +366,21 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_101/images/cockpit_terminal.png" alt="cockpit terminal" height="500">
+<img src="/workshops/containers_101/images/cockpit_terminal.png" alt="cockpit terminal" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Terminal Tab</div>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-Be sure you can log in to your instances.  If you can&#8217;t log in start shouting, loudly, and waving your hands!
+Be sure you can log in to your instances.  If you can’t log in start shouting, loudly, and waving your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -388,7 +388,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -490,7 +490,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -750,7 +750,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -862,7 +862,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -872,7 +872,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -954,7 +954,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_101/wrapup/index.html b/workshops/containers_101/wrapup/index.html
index db94bb7ab..8b54842d6 100644
--- a/workshops/containers_101/wrapup/index.html
+++ b/workshops/containers_101/wrapup/index.html
@@ -365,7 +365,7 @@ <h2 id="_wrap_up_and_qa">Wrap Up and Q&amp;A</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise1/index.html b/workshops/containers_the_hard_way/exercise1/index.html
index eb8e7c712..8f4354b21 100644
--- a/workshops/containers_the_hard_way/exercise1/index.html
+++ b/workshops/containers_the_hard_way/exercise1/index.html
@@ -366,7 +366,7 @@ <h2 id="_exercise_1_2_the_mount_namespace">Exercise 1.2: The Mount Namespace</h2
 <p>The Mount Namespace is the part of the Kernel that stores the mount table. When our sandboxed environment runs in a new Mount Namespace, it can mount filesystems not present on the host.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s explore this. First, we are going to create a new mount namespace and start a Bash shell inside that namespace.</p>
+<p>Let’s explore this. First, we are going to create a new mount namespace and start a Bash shell inside that namespace.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -387,7 +387,7 @@ <h2 id="_exercise_1_2_the_mount_namespace">Exercise 1.2: The Mount Namespace</h2
 </ul>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s mount something in our workspace.</p>
+<p>Now let’s mount something in our workspace.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -404,7 +404,7 @@ <h2 id="_exercise_1_2_the_mount_namespace">Exercise 1.2: The Mount Namespace</h2
 <p>If you switch to another terminal, one that is in the native namespaces, running the <code>mount</code> command will show nothing mounted to <code>/mnt</code>.</p>
 </div>
 <div class="paragraph">
-<p>On the terminal that is in the new mount namespace, let&#8217;s create a file.</p>
+<p>On the terminal that is in the new mount namespace, let’s create a file.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -523,7 +523,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -783,7 +783,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -895,7 +895,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -905,7 +905,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -991,7 +991,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise2/index.html b/workshops/containers_the_hard_way/exercise2/index.html
index abb35beb8..56971d16b 100644
--- a/workshops/containers_the_hard_way/exercise2/index.html
+++ b/workshops/containers_the_hard_way/exercise2/index.html
@@ -324,7 +324,7 @@ <h2 id="_exercise_2_1_the_pid_basics">Exercise 2.1 - The PID Basics</h2>
 <p>Before we start playing with PID namespaces, it is good to have some background on how PIDs in Linux work.</p>
 </div>
 <div class="paragraph">
-<p>Every process that runs on a Linux system gets a Process ID (PID). This exists as a 32-bit integer. Numbering starts at 1 and increments until there are none left. PIDs can be reused once the process terminates. If you run out of PIDs, you&#8217;ll have a bad time.</p>
+<p>Every process that runs on a Linux system gets a Process ID (PID). This exists as a 32-bit integer. Numbering starts at 1 and increments until there are none left. PIDs can be reused once the process terminates. If you run out of PIDs, you’ll have a bad time.</p>
 </div>
 <div class="paragraph">
 <p>Processes are structured in a Tree Structure. Every process has a parent except the first process. Typically the init system (SystemD) will be PID 1 and has no parent.
@@ -372,7 +372,7 @@ <h2 id="_exercise_2_1_the_pid_basics">Exercise 2.1 - The PID Basics</h2>
 <p>If you have any questions here, ask your instructor as being able to understand the process tree is fairly important.</p>
 </div>
 <div class="paragraph">
-<p>Now&#8230;&#8203; Let&#8217;s play with some PIDs.</p>
+<p>Now…​ Let’s play with some PIDs.</p>
 </div>
 </div>
 </div>
@@ -380,10 +380,10 @@ <h2 id="_exercise_2_1_the_pid_basics">Exercise 2.1 - The PID Basics</h2>
 <h2 id="_exercise_2_2_pid_and_ipc_namespaces">Exercise 2.2 - PID and IPC Namespaces</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The PID namespace allows a process and its children to run in a new process tree that maps back to the host process tree. The new PID namespace starts with PID 1 which will map to a much higher PID in the host&#8217;s native PID namespace. The Inter-Process Communication (IPC) Namespace limits the processes ability to share memory.</p>
+<p>The PID namespace allows a process and its children to run in a new process tree that maps back to the host process tree. The new PID namespace starts with PID 1 which will map to a much higher PID in the host’s native PID namespace. The Inter-Process Communication (IPC) Namespace limits the processes ability to share memory.</p>
 </div>
 <div class="paragraph">
-<p>First, let&#8217;s take note of our current PID.</p>
+<p>First, let’s take note of our current PID.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -396,7 +396,7 @@ <h2 id="_exercise_2_2_pid_and_ipc_namespaces">Exercise 2.2 - PID and IPC Namespa
 </div>
 </div>
 <div class="paragraph">
-<p>Ok, so our current Bash shell has a PID of 7128. Let&#8217;s make a new PID namespace.</p>
+<p>Ok, so our current Bash shell has a PID of 7128. Let’s make a new PID namespace.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -404,17 +404,17 @@ <h2 id="_exercise_2_2_pid_and_ipc_namespaces">Exercise 2.2 - PID and IPC Namespa
 </div>
 </div>
 <div class="paragraph">
-<p>That&#8217;s a lof more flags this time.
-- <code>m</code> creates a new mount namespace (you&#8217;ll see why)
+<p>That’s a lof more flags this time.
+- <code>m</code> creates a new mount namespace (you’ll see why)
 - <code>i</code> creates a new IPC namespace
 - <code>p</code> creates a new PID namespace
 - <code>f</code> tells unshare to fork after creating the new namespaces and before starting Bash</p>
 </div>
 <div class="paragraph">
-<p>It is very important that we fork anytime we create a new PID namespace. The reason is because a new PID table is created, but the current process is still in the old namespace. If we run a Bash shell, it will not be able to look up its own PID. If that sounds bad, its because it is! Don&#8217;t believe me? Try running that unshare command without the f option. Use the exit command to leave the broken Bash shell when you are done.</p>
+<p>It is very important that we fork anytime we create a new PID namespace. The reason is because a new PID table is created, but the current process is still in the old namespace. If we run a Bash shell, it will not be able to look up its own PID. If that sounds bad, its because it is! Don’t believe me? Try running that unshare command without the f option. Use the exit command to leave the broken Bash shell when you are done.</p>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s inspect the current PID.</p>
+<p>Now let’s inspect the current PID.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -444,7 +444,7 @@ <h2 id="_exercise_2_2_pid_and_ipc_namespaces">Exercise 2.2 - PID and IPC Namespa
 </div>
 </div>
 <div class="paragraph">
-<p>Wait a minute&#8230;&#8203; Why is ps reporting that systemd is PID 1? It looks like ps is referencing the native PID namespace. Indeed it is!
+<p>Wait a minute…​ Why is ps reporting that systemd is PID 1? It looks like ps is referencing the native PID namespace. Indeed it is!
 The Linux Kernel uses the /proc pseudo filesystem to report raw data on processes. Since we created a new PID namespace, we need to mount a new /proc that matches this new namespace.</p>
 </div>
 <div class="listingblock">
@@ -469,7 +469,7 @@ <h2 id="_exercise_2_2_pid_and_ipc_namespaces">Exercise 2.2 - PID and IPC Namespa
 </div>
 </div>
 <div class="paragraph">
-<p>Now that&#8217;s more like it!</p>
+<p>Now that’s more like it!</p>
 </div>
 <div class="paragraph">
 <p>On the terminal that is in the new namespaces, type <code>exit</code> to return to the native namespaces.</p>
@@ -574,7 +574,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -834,7 +834,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -946,7 +946,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -956,7 +956,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1042,7 +1042,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise3/index.html b/workshops/containers_the_hard_way/exercise3/index.html
index 261d3fd80..d5f837c24 100644
--- a/workshops/containers_the_hard_way/exercise3/index.html
+++ b/workshops/containers_the_hard_way/exercise3/index.html
@@ -324,7 +324,7 @@ <h2 id="_exercise_3_1_network_stack_background">Exercise 3.1 - Network Stack Bac
 <p>The networking namespace in the Kernel is actually responsible for a surprisingly large number of things. It keeps tabs on all the network interfaces and their state, routing tables (Did you know there is more than one? By default, there are 4.), firewall rules, etc. All of these things are explored using the <code>ip</code> command. This command allows root to view and modify the networking stack.</p>
 </div>
 <div class="paragraph">
-<p>The hostname of the machine is stored in a few places. First, the Kernel tracks the machine&#8217;s hostname. Next, the <code>/etc/hostname</code> file stores the statically defined hostname. Finally, a hostname can be derived from DHCP and DNS. What is important to note is that the <code>hostnamectl</code> command will change the hostname value in the Kernel and the value in <code>/etc/hostname</code>. Because our sandbox is using the same filesystem as our host, this is not desireable. Instead of using <code>hostnamectl</code> to manipulate the hostname, we will only use the <code>hostname</code> command as it only changes the Kernel&#8217;s value.</p>
+<p>The hostname of the machine is stored in a few places. First, the Kernel tracks the machine’s hostname. Next, the <code>/etc/hostname</code> file stores the statically defined hostname. Finally, a hostname can be derived from DHCP and DNS. What is important to note is that the <code>hostnamectl</code> command will change the hostname value in the Kernel and the value in <code>/etc/hostname</code>. Because our sandbox is using the same filesystem as our host, this is not desireable. Instead of using <code>hostnamectl</code> to manipulate the hostname, we will only use the <code>hostname</code> command as it only changes the Kernel’s value.</p>
 </div>
 </div>
 </div>
@@ -332,10 +332,10 @@ <h2 id="_exercise_3_1_network_stack_background">Exercise 3.1 - Network Stack Bac
 <h2 id="_exercise_3_2_network_and_uts_namespaces">Exercise 3.2 - Network and UTS Namespaces</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The Network Namespace allows a new network stack to exist in the sandbox. This means our sandboxed environment can have its own network interfaces, routing tables, DNS lookup servers, IP addresses, subnets&#8230;&#8203; you name it! The Unix Time Sharing (UTS) Namespace exists solely for storing the system&#8217;s hostname. Seriously. A whole namespace to store one string. This namespace has a long history and has changed quite a bit along the way. It exists the way it is for historical reasons.</p>
+<p>The Network Namespace allows a new network stack to exist in the sandbox. This means our sandboxed environment can have its own network interfaces, routing tables, DNS lookup servers, IP addresses, subnets…​ you name it! The Unix Time Sharing (UTS) Namespace exists solely for storing the system’s hostname. Seriously. A whole namespace to store one string. This namespace has a long history and has changed quite a bit along the way. It exists the way it is for historical reasons.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s create a sandbox with a new Network and UTS Namespace.</p>
+<p>Let’s create a sandbox with a new Network and UTS Namespace.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -367,10 +367,10 @@ <h2 id="_exercise_3_2_network_and_uts_namespaces">Exercise 3.2 - Network and UTS
 </div>
 </div>
 <div class="paragraph">
-<p>Just the loopback. Good news, our network namespace worked! Bad news, we can&#8217;t reach the internet. Keep this issue in mind, we will revisit it later.</p>
+<p>Just the loopback. Good news, our network namespace worked! Bad news, we can’t reach the internet. Keep this issue in mind, we will revisit it later.</p>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s change our hostname.</p>
+<p>Now let’s change our hostname.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -502,7 +502,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -762,7 +762,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -874,7 +874,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -884,7 +884,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -970,7 +970,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise4/index.html b/workshops/containers_the_hard_way/exercise4/index.html
index 2240cd7ac..df1650de2 100644
--- a/workshops/containers_the_hard_way/exercise4/index.html
+++ b/workshops/containers_the_hard_way/exercise4/index.html
@@ -332,7 +332,7 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 <p>The User Namespaces allow our sandboxed environment to have its own set of user and group IDs that will map to very high, unique, user and group IDs back on the host system. They also allow the root user in the sandbox to be mapped to another user on the host.</p>
 </div>
 <div class="paragraph">
-<p>Because we are now invoking the User Namespace, we no longer need to work as root. Let&#8217;s switch to a non-priviledged user.</p>
+<p>Because we are now invoking the User Namespace, we no longer need to work as root. Let’s switch to a non-priviledged user.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -340,7 +340,7 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s unshare some namespaces!</p>
+<p>Now let’s unshare some namespaces!</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -354,10 +354,10 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>Wait&#8230;&#8203; We are root again? I thought we just left root!</p>
+<p>Wait…​ We are root again? I thought we just left root!</p>
 </div>
 <div class="paragraph">
-<p>Well&#8230;&#8203; yes and no. Inside of our sandbox, we are the root user, but we have instructed unshare to map the root user to our actual UID outside the sandbox. That is what the <code>r</code> option does. The <code>U</code> option creates the new User Namespace.</p>
+<p>Well…​ yes and no. Inside of our sandbox, we are the root user, but we have instructed unshare to map the root user to our actual UID outside the sandbox. That is what the <code>r</code> option does. The <code>U</code> option creates the new User Namespace.</p>
 </div>
 <div class="paragraph">
 <p>To inspect how UIDs are being mapped, we can query the Kernel state.</p>
@@ -376,7 +376,7 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 <p>This tells us that root (UID 0) is mapped to rhel (UID 1001) and a span of 1 UID is available for mapping. It is possible to allocate additional UIDs to the sandbox, but that is outside the scope of this workshop.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s look at the UID mapping in the host&#8217;s native namespace. Switch to a terminal that is not in your sandbox.</p>
+<p>Let’s look at the UID mapping in the host’s native namespace. Switch to a terminal that is not in your sandbox.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -392,7 +392,7 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 <p>This says that root (UID 0) is mapped to root (UID 0) and a span of 4294967295 UIDs are available. That number may seem odd until you realize it is the maximum value for a 32-bit unsigned integer.</p>
 </div>
 <div class="paragraph">
-<p>So&#8230;&#8203; let&#8217;s test the limts of our root powers. If we were root, we could do some pretty destructive things&#8230;&#8203; Like delete Bash! Go back to the terminal that is in your sandbox.</p>
+<p>So…​ let’s test the limts of our root powers. If we were root, we could do some pretty destructive things…​ Like delete Bash! Go back to the terminal that is in your sandbox.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -401,14 +401,14 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>rm: cannot remove '/bin/bash': Permission denied</pre>
+<pre>rm: cannot remove &#39;/bin/bash&#39;: Permission denied</pre>
 </div>
 </div>
 <div class="paragraph">
 <p>However, since we are not root outside of the sandbox, we cannot remove files owned by the real root outside of the sandbox.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s do another test.</p>
+<p>Let’s do another test.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -422,7 +422,7 @@ <h2 id="_exercise_4_2_user_namespace">Exercise 4.2 - User Namespace</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>Makes sense. We are root so the files we create are owned by root. But lets leave our sandbox and check that same file in the host&#8217;s native namespace. Run the following commands on a terminal that is not in your sandbox.</p>
+<p>Makes sense. We are root so the files we create are owned by root. But lets leave our sandbox and check that same file in the host’s native namespace. Run the following commands on a terminal that is not in your sandbox.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -537,7 +537,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -797,7 +797,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -909,7 +909,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -919,7 +919,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1005,7 +1005,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise5/index.html b/workshops/containers_the_hard_way/exercise5/index.html
index b081413e4..7ba115502 100644
--- a/workshops/containers_the_hard_way/exercise5/index.html
+++ b/workshops/containers_the_hard_way/exercise5/index.html
@@ -318,7 +318,7 @@ <h1>Exercise 5 - All Together Now</h1>
 </nav>
 
     <div class="paragraph">
-<p>Let&#8217;s put all of our new namespace skills to use! Again, we will be working as the rhel user.</p>
+<p>Let’s put all of our new namespace skills to use! Again, we will be working as the rhel user.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -343,7 +343,7 @@ <h1>Exercise 5 - All Together Now</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_the_hard_way/images/cgroups_namespaces.jpeg" alt="cgroups namespaces" width="500">
+<img src="/workshops/containers_the_hard_way/images/cgroups_namespaces.jpeg" alt="cgroups namespaces" width="500"/>
 </div>
 </div>
 <div class="paragraph">
@@ -446,7 +446,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -706,7 +706,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -818,7 +818,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -828,7 +828,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -912,7 +912,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise6/index.html b/workshops/containers_the_hard_way/exercise6/index.html
index e477c6b71..c879cebfe 100644
--- a/workshops/containers_the_hard_way/exercise6/index.html
+++ b/workshops/containers_the_hard_way/exercise6/index.html
@@ -321,13 +321,13 @@ <h1>Exercise 6 - Changing the Filesystem</h1>
 <h2 id="_exercise_6_1_some_background">Exercise 6.1 - Some Background</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>All of that is well and good. However, containers are great because they allow us to package and distribute software. All we&#8217;ve done is isolate some Linux processes. Where&#8217;s the beef?</p>
+<p>All of that is well and good. However, containers are great because they allow us to package and distribute software. All we’ve done is isolate some Linux processes. Where’s the beef?</p>
 </div>
 <div class="paragraph">
 <p>Containers get their root filesystem from a container image file. This is typically pulled from a registry. This file is, essentially, a TAR archive with the root filesystem contents and some metadata. Those contents are then made available to the running container through use of an Overlay Filesystem. The Overlay Filesystem mechanism allows the container to use the files provided by the image and make ephemeral changes to those files.</p>
 </div>
 <div class="paragraph">
-<p>This is how Overlay Filesystems work. There are four directories: LOWER, UPPER, WORK, and MOUNT. The LOWER directory contains the filesystem&#8217;s initial state. This is the contents of the container image and can be read only. The UPPER directory is where runtime changes will be stored and must be read/write. The WORK directory is where runtime changes are staged and must be read/write. Finally, the MOUNT directory is simply a directory where the OverlayFS is mounted and presented as a single filesystem. This is the directory we will chroot our container into.</p>
+<p>This is how Overlay Filesystems work. There are four directories: LOWER, UPPER, WORK, and MOUNT. The LOWER directory contains the filesystem’s initial state. This is the contents of the container image and can be read only. The UPPER directory is where runtime changes will be stored and must be read/write. The WORK directory is where runtime changes are staged and must be read/write. Finally, the MOUNT directory is simply a directory where the OverlayFS is mounted and presented as a single filesystem. This is the directory we will chroot our container into.</p>
 </div>
 <div class="paragraph">
 <p>Strictly speaking, there are other backend storage methods that can be used with containers. However, OverlayFS has become quite popular lately and it is the one used by podman.</p>
@@ -370,7 +370,7 @@ <h2 id="_exercise_6_2_fetch_dependencies">Exercise 6.2 - Fetch Dependencies</h2>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_exercise_6_3_whats_in_an_image">Exercise 6.3 - What&#8217;s in an Image</h2>
+<h2 id="_exercise_6_3_whats_in_an_image">Exercise 6.3 - What’s in an Image</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>If you have worked with containers before, you will have a general notion of image files. However, you have probably never seen one. They usually get stashed away in <code>/var/lib/containers</code> or <code>/var/lib/docker</code> and you interact with them only through the orchestration of your container engine. Today we will change all that.
@@ -397,11 +397,11 @@ <h2 id="_exercise_6_3_whats_in_an_image">Exercise 6.3 - What&#8217;s in an Image
 <p>Here we have a few files:
 - <strong>version</strong> contains the OCI file format spec information for this image
 - <strong>manifest.json</strong> contains information regarding the contents of the image
-- <strong>f085&#8230;&#8203;</strong> contains the image metadata. We know that because it is small in file size.
-- <strong>d318&#8230;&#8203;</strong> contains the image layer. This image contains only one layer, but some will contain more than one. These layers get stacked to create the base filesystem. We know this is a layer because its file size is quite large.</p>
+- <strong>f085…​</strong> contains the image metadata. We know that because it is small in file size.
+- <strong>d318…​</strong> contains the image layer. This image contains only one layer, but some will contain more than one. These layers get stacked to create the base filesystem. We know this is a layer because its file size is quite large.</p>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s extract the contents of the layer.</p>
+<p>Now let’s extract the contents of the layer.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -438,7 +438,7 @@ <h2 id="_exercise_6_3_whats_in_an_image">Exercise 6.3 - What&#8217;s in an Image
 </div>
 </div>
 <div class="paragraph">
-<p>What we have just extracted is a Fedora 31 system&#8217;s root filesystem!</p>
+<p>What we have just extracted is a Fedora 31 system’s root filesystem!</p>
 </div>
 </div>
 </div>
@@ -446,7 +446,7 @@ <h2 id="_exercise_6_3_whats_in_an_image">Exercise 6.3 - What&#8217;s in an Image
 <h2 id="_exercise_6_4_create_an_overlay_filesystem">Exercise 6.4 - Create an Overlay Filesystem</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now let&#8217;s use the LOWER directory we just populated to create an OverlayFS.</p>
+<p>Now let’s use the LOWER directory we just populated to create an OverlayFS.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -465,7 +465,7 @@ <h2 id="_exercise_6_4_create_an_overlay_filesystem">Exercise 6.4 - Create an Ove
 </div>
 </div>
 <div class="paragraph">
-<p>Now you can explore the ROOTFS directory. You&#8217;ll notice it is a replica of the LOWER dir. As you make changes to ROOTFS, those changes will appear in UPPER.</p>
+<p>Now you can explore the ROOTFS directory. You’ll notice it is a replica of the LOWER dir. As you make changes to ROOTFS, those changes will appear in UPPER.</p>
 </div>
 </div>
 </div>
@@ -473,7 +473,7 @@ <h2 id="_exercise_6_4_create_an_overlay_filesystem">Exercise 6.4 - Create an Ove
 <h2 id="_exercise_6_4_create_a_fedora_container">Exercise 6.4 - Create a Fedora Container</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Let&#8217;s add a chroot to our namespace skills to create a container.</p>
+<p>Let’s add a chroot to our namespace skills to create a container.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -489,7 +489,7 @@ <h2 id="_exercise_6_4_create_a_fedora_container">Exercise 6.4 - Create a Fedora
 </div>
 </div>
 <div class="paragraph">
-<p>And there we have it. A bona fide Fedora container! Feel free to poke around the container a bit. Because the Fedora image is very barebones, you won&#8217;t be able to do much. Type exit when you are done.</p>
+<p>And there we have it. A bona fide Fedora container! Feel free to poke around the container a bit. Because the Fedora image is very barebones, you won’t be able to do much. Type exit when you are done.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -591,7 +591,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -851,7 +851,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -963,7 +963,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -973,7 +973,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1059,7 +1059,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/exercise7/index.html b/workshops/containers_the_hard_way/exercise7/index.html
index 2690ea178..e45d5d572 100644
--- a/workshops/containers_the_hard_way/exercise7/index.html
+++ b/workshops/containers_the_hard_way/exercise7/index.html
@@ -339,23 +339,23 @@ <h2 id="_exercise_7_1_some_background">Exercise 7.1 - Some Background</h2>
 <h2 id="_exercise_7_2_container_network_devices">Exercise 7.2 - Container Network Devices</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>As we have already seen, when a container intiates a new Network Namespace, it wil have no network devices available to it. In order to get network connectivity to the container, we need to add devices to the container&#8217;s network namespace from the host.
-Traditionally, when we run containers as the root user, we will create a virtual adpater and attach it to the container&#8217;s network namespace as <code>eth0</code>. The virtual adapter then joins a bridge that is shared with the host&#8217;s physical network interface. The bridge will have its own subnet that is unique from the host&#8217;s physical network and the bridge will handle routing traffic from the internal subnet to the network.</p>
+<p>As we have already seen, when a container intiates a new Network Namespace, it wil have no network devices available to it. In order to get network connectivity to the container, we need to add devices to the container’s network namespace from the host.
+Traditionally, when we run containers as the root user, we will create a virtual adpater and attach it to the container’s network namespace as <code>eth0</code>. The virtual adapter then joins a bridge that is shared with the host’s physical network interface. The bridge will have its own subnet that is unique from the host’s physical network and the bridge will handle routing traffic from the internal subnet to the network.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_the_hard_way/images/networking_traditional.png" alt="networking traditional" width="500">
+<img src="/workshops/containers_the_hard_way/images/networking_traditional.png" alt="networking traditional" width="500"/>
 </div>
 </div>
 <div class="paragraph">
 <p>This model uses all Kernel native networking primitives. This is great for efficiency and speed. However, none of these devices can be created by a non-root user.</p>
 </div>
 <div class="paragraph">
-<p>When we create a container as a non-root user, we have to do something slightly different. We use an application called slirp4netns. This application creates a tap inside the container&#8217;s network namespace and attaches to it. The application then handles traffic routing much the same way the bridge would, except in user space.</p>
+<p>When we create a container as a non-root user, we have to do something slightly different. We use an application called slirp4netns. This application creates a tap inside the container’s network namespace and attaches to it. The application then handles traffic routing much the same way the bridge would, except in user space.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_the_hard_way/images/networking_rootless.png" alt="networking rootless" width="500">
+<img src="/workshops/containers_the_hard_way/images/networking_rootless.png" alt="networking rootless" width="500"/>
 </div>
 </div>
 </div>
@@ -368,7 +368,7 @@ <h2 id="_exercise_7_3_before_we_begin">Exercise 7.3 - Before We Begin</h2>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sysctl -w "net.ipv4.ping_group_range=0 2000000"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sysctl -w &#34;net.ipv4.ping_group_range=0 2000000&#34;</code></pre>
 </div>
 </div>
 </div>
@@ -377,7 +377,7 @@ <h2 id="_exercise_7_3_before_we_begin">Exercise 7.3 - Before We Begin</h2>
 <h2 id="_exercise_7_4_create_a_sandbox">Exercise 7.4 - Create A Sandbox</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Let&#8217;s create a sandbox and launch a Bash shell into that sandbox.</p>
+<p>Let’s create a sandbox and launch a Bash shell into that sandbox.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -441,7 +441,7 @@ <h2 id="_exercise_7_5_create_a_tap_in_the_sandbox">Exercise 7.5 - Create a Tap i
 </div>
 </div>
 <div class="paragraph">
-<p>Look at that! It created and configured our tap0 netork adapter for us! That&#8217;s nice.</p>
+<p>Look at that! It created and configured our tap0 netork adapter for us! That’s nice.</p>
 </div>
 <div class="paragraph">
 <p>From here you can test out the network interface. For example, try pinging 8.8.8.8.</p>
@@ -546,7 +546,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -806,7 +806,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -918,7 +918,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -928,7 +928,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1014,7 +1014,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/index.html b/workshops/containers_the_hard_way/index.html
index 365991105..fece36a03 100644
--- a/workshops/containers_the_hard_way/index.html
+++ b/workshops/containers_the_hard_way/index.html
@@ -296,7 +296,7 @@ <h2 id="_workshop_description">Workshop Description</h2>
 <h2 id="_who_should_attend">Who should attend</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Today&#8217;s container workshop is meant for anyone who has any exposure to Linux containers, and assumes that you have run a container or two. If you have had no exposure to containers, that&#8217;s fine too, just don&#8217;t be shy about asking questions.</p>
+<p>Today’s container workshop is meant for anyone who has any exposure to Linux containers, and assumes that you have run a container or two. If you have had no exposure to containers, that’s fine too, just don’t be shy about asking questions.</p>
 </div>
 </div>
 </div>
@@ -510,7 +510,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -770,7 +770,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -882,7 +882,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -892,7 +892,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -945,7 +945,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/index.xml b/workshops/containers_the_hard_way/index.xml
index 0aaa59a61..8734f7bde 100644
--- a/workshops/containers_the_hard_way/index.xml
+++ b/workshops/containers_the_hard_way/index.xml
@@ -4,99 +4,71 @@
     <title>Linux Containers the Hard Way on Red Hat | Public Sector</title>
     <link>/workshops/containers_the_hard_way/</link>
     <description>Recent content in Linux Containers the Hard Way on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/containers_the_hard_way/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/containers_the_hard_way/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1 - The Mount Namespace</title>
       <link>/workshops/containers_the_hard_way/exercise1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise1/</guid>
-      <description>Exercise 1.1: Unsharing is Caring New Linux Namespaces are typically spawned by using either the clone or unshare system calls. These exist as C functions but wrappers exist in many other languages. For our purposes today, we will be using the unshare command which is ostensibly a Bash wrapper to the unshare system call.
- unshare --help   Usage: unshare [options] [&amp;lt;program&amp;gt; [&amp;lt;argument&amp;gt;...]] Run a program with some namespaces unshared from the parent.</description>
+      <description>Exercise 1.1: Unsharing is Caring New Linux Namespaces are typically spawned by using either the clone or unshare system calls. These exist as C functions but wrappers exist in many other languages. For our purposes today, we will be using the unshare command which is ostensibly a Bash wrapper to the unshare system call.&#xA;unshare --help Usage: unshare [options] [&amp;lt;program&amp;gt; [&amp;lt;argument&amp;gt;...]] Run a program with some namespaces unshared from the parent.</description>
     </item>
-    
     <item>
       <title>Exercise 2 - PID and IPC Namespaces</title>
       <link>/workshops/containers_the_hard_way/exercise2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise2/</guid>
-      <description>Exercise 2.1 - The PID Basics Before we start playing with PID namespaces, it is good to have some background on how PIDs in Linux work.
- Every process that runs on a Linux system gets a Process ID (PID). This exists as a 32-bit integer. Numbering starts at 1 and increments until there are none left. PIDs can be reused once the process terminates. If you run out of PIDs, you&amp;#8217;ll have a bad time.</description>
+      <description>Exercise 2.1 - The PID Basics Before we start playing with PID namespaces, it is good to have some background on how PIDs in Linux work.&#xA;Every process that runs on a Linux system gets a Process ID (PID). This exists as a 32-bit integer. Numbering starts at 1 and increments until there are none left. PIDs can be reused once the process terminates. If you run out of PIDs, you’ll have a bad time.</description>
     </item>
-    
     <item>
       <title>Exercise 3 - Network and UTS Namespaces</title>
       <link>/workshops/containers_the_hard_way/exercise3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise3/</guid>
       <description>Exercise 3.1 - Network Stack Background The networking namespace in the Kernel is actually responsible for a surprisingly large number of things. It keeps tabs on all the network interfaces and their state, routing tables (Did you know there is more than one? By default, there are 4.), firewall rules, etc. All of these things are explored using the ip command. This command allows root to view and modify the networking stack.</description>
     </item>
-    
     <item>
       <title>Exercise 4 - User Namespace</title>
       <link>/workshops/containers_the_hard_way/exercise4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise4/</guid>
       <description>Exercise 4.1 - History Lesson The User Namespace is easily the newest namespce in the Linux Kernel. It was introduced to allow non-root users to run containers without a heavy root daemon. Typically, a non-priviledged user cannot spawn new namespaces. However, if a new User Namespace is created, then that same user can now spawn any type of namespace. Since this feature was introduced in the Kernel, you have seen newer container images come out that do not rely on daemons because they are no longer necessary.</description>
     </item>
-    
     <item>
       <title>Exercise 5 - All Together Now</title>
       <link>/workshops/containers_the_hard_way/exercise5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise5/</guid>
-      <description>Let&amp;#8217;s put all of our new namespace skills to use! Again, we will be working as the rhel user.
- su - rhel # if neccessary unshare -mipfnuUr /bin/bash mount -t proc none /proc mount -t tmpfs none /tmp mount -t sysfs none /sys   With the call to unshare, we used all of the flags that we have used in the previous exercises. We also mounted three new filesystems after creating our sandbox.</description>
+      <description>Let’s put all of our new namespace skills to use! Again, we will be working as the rhel user.&#xA;su - rhel # if neccessary unshare -mipfnuUr /bin/bash mount -t proc none /proc mount -t tmpfs none /tmp mount -t sysfs none /sys With the call to unshare, we used all of the flags that we have used in the previous exercises. We also mounted three new filesystems after creating our sandbox.</description>
     </item>
-    
     <item>
       <title>Exercise 6 - Changing the Filesystem</title>
       <link>/workshops/containers_the_hard_way/exercise6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise6/</guid>
-      <description>Exercise 6.1 - Some Background All of that is well and good. However, containers are great because they allow us to package and distribute software. All we&amp;#8217;ve done is isolate some Linux processes. Where&amp;#8217;s the beef?
- Containers get their root filesystem from a container image file. This is typically pulled from a registry. This file is, essentially, a TAR archive with the root filesystem contents and some metadata. Those contents are then made available to the running container through use of an Overlay Filesystem.</description>
+      <description>Exercise 6.1 - Some Background All of that is well and good. However, containers are great because they allow us to package and distribute software. All we’ve done is isolate some Linux processes. Where’s the beef?&#xA;Containers get their root filesystem from a container image file. This is typically pulled from a registry. This file is, essentially, a TAR archive with the root filesystem contents and some metadata. Those contents are then made available to the running container through use of an Overlay Filesystem.</description>
     </item>
-    
     <item>
       <title>Exercise 7 - Container Networking</title>
       <link>/workshops/containers_the_hard_way/exercise7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/exercise7/</guid>
-      <description>Exercise 7.1 - Some Background The Linux Kernel provides many useful primitives that can be used to construct very intricate network configurations. They are very flexible and powerful. Of particular interest today are Virtual Ethernet Adapaters, Bridges, and Taps.
- A Virtual Ethernet Adapater operates in the Kernel exactly the way a physical NIC would. The only difference is that instead of receiving data from a physical device, a virtual adapter recieves data from another network adapter in the stack.</description>
+      <description>Exercise 7.1 - Some Background The Linux Kernel provides many useful primitives that can be used to construct very intricate network configurations. They are very flexible and powerful. Of particular interest today are Virtual Ethernet Adapaters, Bridges, and Taps.&#xA;A Virtual Ethernet Adapater operates in the Kernel exactly the way a physical NIC would. The only difference is that instead of receiving data from a physical device, a virtual adapter recieves data from another network adapter in the stack.</description>
     </item>
-    
     <item>
       <title>Introduction</title>
       <link>/workshops/containers_the_hard_way/intro/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/intro/</guid>
-      <description>What is a container? It is a simple question without a simple answer. Search the internet for this question and you&amp;#8217;ll find an endless stream of blog posts explaining how containers differ from virtual machines. That&amp;#8217;s great, but that doesn&amp;#8217;t answer my question. What is a container? Does anybody really understand what is happening on their server what they podman run?
-   By the end of this workshop, you will feel confident answering this question and explaining it to your peers.</description>
+      <description>What is a container? It is a simple question without a simple answer. Search the internet for this question and you’ll find an endless stream of blog posts explaining how containers differ from virtual machines. That’s great, but that doesn’t answer my question. What is a container? Does anybody really understand what is happening on their server what they podman run?&#xA;By the end of this workshop, you will feel confident answering this question and explaining it to your peers.</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/containers_the_hard_way/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/wrapup/</guid>
-      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.
- We explored Linux Namespaces and the unshare command in great depth. Obviously container enginers make heavy use of these namespaces. Their job is to orchestrate the namespaces, OverlayFS, image files, and active containers so you don&amp;#8217;t have to. Obviously, you wouldn&amp;#8217;t run containers this way in production, but there may be times that you&amp;#8217;d like to make use of namespaces.</description>
+      <description>Wrap Up and Q&amp;amp;A That wraps up what we have planned for today.&#xA;We explored Linux Namespaces and the unshare command in great depth. Obviously container enginers make heavy use of these namespaces. Their job is to orchestrate the namespaces, OverlayFS, image files, and active containers so you don’t have to. Obviously, you wouldn’t run containers this way in production, but there may be times that you’d like to make use of namespaces.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/containers_the_hard_way/intro/index.html b/workshops/containers_the_hard_way/intro/index.html
index 90fdbfd13..54ae56cd6 100644
--- a/workshops/containers_the_hard_way/intro/index.html
+++ b/workshops/containers_the_hard_way/intro/index.html
@@ -317,11 +317,11 @@ <h1>Introduction</h1>
 <h2 id="_what_is_a_container">What is a container?</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>It is a simple question without a simple answer. Search the internet for this question and you&#8217;ll find an endless stream of blog posts explaining how containers differ from virtual machines. That&#8217;s great, but that doesn&#8217;t answer my question. What is a container? Does anybody really understand what is happening on their server what they <code>podman run</code>?</p>
+<p>It is a simple question without a simple answer. Search the internet for this question and you’ll find an endless stream of blog posts explaining how containers differ from virtual machines. That’s great, but that doesn’t answer my question. What is a container? Does anybody really understand what is happening on their server what they <code>podman run</code>?</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_the_hard_way/images/afraid_to_ask_andy.jpg" alt="afraid to ask andy" width="500">
+<img src="/workshops/containers_the_hard_way/images/afraid_to_ask_andy.jpg" alt="afraid to ask andy" width="500"/>
 </div>
 </div>
 <div class="paragraph">
@@ -330,7 +330,7 @@ <h2 id="_what_is_a_container">What is a container?</h2>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_so_really_what_is_it">So really&#8230;&#8203; What is it?</h2>
+<h2 id="_so_really_what_is_it">So really…​ What is it?</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>A container is a sandboxed runtime environment that exists on a Linux system. The sandbox is constructed using utilities that exist in the Linux Kernel. Applications running in this sandbox share a Kernel with their host, but certain parts of the Kernel that store machine state are abstracted through namespaces. Namespaces allow the isolated environment to have a different state than the host even though they are sharing a Kernel.</p>
@@ -346,34 +346,34 @@ <h2 id="_so_really_what_is_it">So really&#8230;&#8203; What is it?</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/containers_the_hard_way/images/container_stack.png" alt="container stack" width="500">
+<img src="/workshops/containers_the_hard_way/images/container_stack.png" alt="container stack" width="500"/>
 </div>
 </div>
 <div class="paragraph">
 <p>In Figure 2 above, the sandboxed container environment can be seen as the blue box. The orange boxes are the Kernel Namespaces and they are as follows:</p>
 </div>
 <div class="paragraph">
-<p><strong>cgroups</strong><br>
-cgroups allow limits to be placed on a process and its children. Primarily, these are used for limiting CPU and RAM usage. We won&#8217;t dive deep into cgroups as they are technically optional for containers. However, you will be using them in production.</p>
+<p><strong>cgroups</strong><br/>
+cgroups allow limits to be placed on a process and its children. Primarily, these are used for limiting CPU and RAM usage. We won’t dive deep into cgroups as they are technically optional for containers. However, you will be using them in production.</p>
 </div>
 <div class="paragraph">
-<p><strong>PID and IPC Namespaces</strong><br>
-The PID namespace allows a process and its children to run in a new process tree that maps back to the host process tree. The new PID namespace starts with PID 1 which will map to a much higher PID in the host&#8217;s native PID namespace. The Inter-Process Communication (IPC) Namespace limits the processes ability to share memory.</p>
+<p><strong>PID and IPC Namespaces</strong><br/>
+The PID namespace allows a process and its children to run in a new process tree that maps back to the host process tree. The new PID namespace starts with PID 1 which will map to a much higher PID in the host’s native PID namespace. The Inter-Process Communication (IPC) Namespace limits the processes ability to share memory.</p>
 </div>
 <div class="paragraph">
-<p><strong>Network and UTS Namespaces</strong><br>
-The Network Namespace allows a new network stack to exist in the sandbox. This means our sandboxed environment can have its own network interfaces, routing tables, DNS lookup servers, IP addresses, subnets&#8230;&#8203; you name it! The Unix Time Sharing (UTS) Namespace exists solely for storing the system&#8217;s hostname. Seriously. A whole namespace to store one string. This namespace has a long history and has changed quite a bit along the way. It exists the way it is for historical reasons.</p>
+<p><strong>Network and UTS Namespaces</strong><br/>
+The Network Namespace allows a new network stack to exist in the sandbox. This means our sandboxed environment can have its own network interfaces, routing tables, DNS lookup servers, IP addresses, subnets…​ you name it! The Unix Time Sharing (UTS) Namespace exists solely for storing the system’s hostname. Seriously. A whole namespace to store one string. This namespace has a long history and has changed quite a bit along the way. It exists the way it is for historical reasons.</p>
 </div>
 <div class="paragraph">
-<p><strong>Mount Namespace</strong><br>
-The Mount Namespace is the part of the Kernel that stores the mount table. When our sandboxed environment runs in a new Mount Namespace, it can mount filesystems not present on the host. This is very important, as you&#8217;ll see.</p>
+<p><strong>Mount Namespace</strong><br/>
+The Mount Namespace is the part of the Kernel that stores the mount table. When our sandboxed environment runs in a new Mount Namespace, it can mount filesystems not present on the host. This is very important, as you’ll see.</p>
 </div>
 <div class="paragraph">
-<p><strong>User Namespace</strong><br>
+<p><strong>User Namespace</strong><br/>
 The User Namespaces allow our sandboxed environment to have its own set of user and group IDs that will map to very high, unique, user and group IDs back on the host system. They also allow the root user in the sandbox to be mapped to another user on the host.</p>
 </div>
 <div class="paragraph">
-<p><strong>seccomp</strong><br>
+<p><strong>seccomp</strong><br/>
 The seccomp utility, while not actually a namespace, acts as a filter for Kernel calls. This allows us to drop Kernel capabilities in our sandboxed environment. For example, we could drop the <code>CAP_NET_RAW</code> kernel capability and processes in our sandbox will not be able to ping. Utilizing seccomp is also not strictly vital to containers and will not be discussed in further detail in this workshop.</p>
 </div>
 <div class="paragraph">
@@ -385,17 +385,17 @@ <h2 id="_so_really_what_is_it">So really&#8230;&#8203; What is it?</h2>
 <h2 id="_setup_for_containers_the_hard_way">Setup for Containers the Hard Way</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>To work through this workshop, you will need access to a RHEL 8 machine. Don&#8217;t worry, though, we have one prepared for you.</p>
+<p>To work through this workshop, you will need access to a RHEL 8 machine. Don’t worry, though, we have one prepared for you.</p>
 </div>
 <div class="paragraph">
 <p><strong>Note:</strong> Your instructor may have different directions for connecting the workshop environment.</p>
 </div>
 <div class="paragraph">
-<p>In this lab, we will use the RHEL 8 Lab Environments on: [lab.redhat.com][1]. This site has a handful of great RHEL 8 scenarios. We won&#8217;t be running through and of them today, but check them out sometime.
+<p>In this lab, we will use the RHEL 8 Lab Environments on: [lab.redhat.com][1]. This site has a handful of great RHEL 8 scenarios. We won’t be running through and of them today, but check them out sometime.
 Navigate to the RHEL 8 labs, and start the <code>Deploying Containers Using Podman</code> scenario by clicked <code>Start Scenario</code> and then <code>Start Scenario</code> again.</p>
 </div>
 <div class="paragraph">
-<p>This will open a screen with lab instructions on the left and terminals on the right. You can minimize the provided directions, we won&#8217;t be using them today.
+<p>This will open a screen with lab instructions on the left and terminals on the right. You can minimize the provided directions, we won’t be using them today.
 On the right, note that you have access to two terminals. You can open another tab with the + button.</p>
 </div>
 </div>
@@ -408,7 +408,7 @@ <h2 id="_conventions_used_in_this_workshop">Conventions Used in this Workshop</h
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">echo "hello, world!"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">echo &#34;hello, world!&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -530,7 +530,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -790,7 +790,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -902,7 +902,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -912,7 +912,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -994,7 +994,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/containers_the_hard_way/wrapup/index.html b/workshops/containers_the_hard_way/wrapup/index.html
index c4795cece..ea12a6c18 100644
--- a/workshops/containers_the_hard_way/wrapup/index.html
+++ b/workshops/containers_the_hard_way/wrapup/index.html
@@ -320,13 +320,13 @@ <h2 id="_wrap_up_and_qa">Wrap Up and Q&amp;A</h2>
 <p>That wraps up what we have planned for today.</p>
 </div>
 <div class="paragraph">
-<p>We explored Linux Namespaces and the unshare command in great depth. Obviously container enginers make heavy use of these namespaces. Their job is to orchestrate the namespaces, OverlayFS, image files, and active containers so you don&#8217;t have to. Obviously, you wouldn&#8217;t run containers this way in production, but there may be times that you&#8217;d like to make use of namespaces. For example, did you know that Ansible Tower uses namespaces to create isolated environments for running Ansible code? By segragating untrusted code with namespaces, you can maintain a higher degree of security. Chromium uses namespaces for isolating JavaScript code downloaded from the web. Pretty cool, huh?</p>
+<p>We explored Linux Namespaces and the unshare command in great depth. Obviously container enginers make heavy use of these namespaces. Their job is to orchestrate the namespaces, OverlayFS, image files, and active containers so you don’t have to. Obviously, you wouldn’t run containers this way in production, but there may be times that you’d like to make use of namespaces. For example, did you know that Ansible Tower uses namespaces to create isolated environments for running Ansible code? By segragating untrusted code with namespaces, you can maintain a higher degree of security. Chromium uses namespaces for isolating JavaScript code downloaded from the web. Pretty cool, huh?</p>
 </div>
 <div class="paragraph">
 <p>Then we explored Overlay Filesystems and Container Networking basics. These are the extra bits that make containers work.</p>
 </div>
 <div class="paragraph">
-<p>All container engines, be it podman, docker, rkt, etc&#8230;&#8203; They all use the same Linux components. Now that the Registry API and Image File Format have been standardized, the underlying container engine can be changed with little affect to the runtime environment. Open source and open standards have provided a vast amount of flexibility.</p>
+<p>All container engines, be it podman, docker, rkt, etc…​ They all use the same Linux components. Now that the Registry API and Image File Format have been standardized, the underlying container engine can be changed with little affect to the runtime environment. Open source and open standards have provided a vast amount of flexibility.</p>
 </div>
 <div class="paragraph">
 <p>Thank you for your time and participation!</p>
@@ -368,7 +368,7 @@ <h2 id="_wrap_up_and_qa">Wrap Up and Q&amp;A</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/dynatrace_openshift/index.html b/workshops/dynatrace_openshift/index.html
index 810db1442..8b9385592 100644
--- a/workshops/dynatrace_openshift/index.html
+++ b/workshops/dynatrace_openshift/index.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
 
-    <title>dynatrace_openshift | Red Hat | Public Sector</title>
+    <title>Dynatrace_openshift | Red Hat | Public Sector</title>
 
     
     
@@ -279,7 +279,7 @@
 
 
 <div class="jumbotron jumbotron-page text-center">
-  <h1>dynatrace_openshift</h1>
+  <h1>Dynatrace_openshift</h1>
 </div>
 
 <div class="container">
@@ -290,7 +290,7 @@ <h1>dynatrace_openshift</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/dynatrace_openshift/index.xml b/workshops/dynatrace_openshift/index.xml
index 7f0cb6a46..b30843b42 100644
--- a/workshops/dynatrace_openshift/index.xml
+++ b/workshops/dynatrace_openshift/index.xml
@@ -1,157 +1,109 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
-    <title>dynatrace_openshift on Red Hat | Public Sector</title>
+    <title>Dynatrace_openshift on Red Hat | Public Sector</title>
     <link>/workshops/dynatrace_openshift/</link>
-    <description>Recent content in dynatrace_openshift on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <description>Recent content in Dynatrace_openshift on Red Hat | Public Sector</description>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/dynatrace_openshift/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/dynatrace_openshift/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_4_101_dynatrace/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.
- OpenShift Architecture OpenShift Developer&amp;rsquo;s Site   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.&#xA;OpenShift Architecture OpenShift Developer&amp;rsquo;s Site &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Welcome</title>
       <link>/workshops/openshift_4_101_dynatrace/lab1-welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab1-welcome/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
     </item>
-    
     <item>
       <title>Lab 10 - Labels (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab10-labels/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab10-labels/</guid>
-      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.
-For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.
-Labels on a pod In a previous lab we added our web app using a S2I template.</description>
+      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.&#xA;For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.&#xA;Labels on a pod In a previous lab we added our web app using a S2I template.</description>
     </item>
-    
     <item>
       <title>Lab 11 - Webhooks and Rollbacks (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab11-cicd/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab11-cicd/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 12 - Blue | Green Deployment (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab12-bluegreen/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab12-bluegreen/</guid>
       <description>Blue/Green deployments When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments. It addresses the desire to minimize downtime during the release of a new version of an application to production. Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified. Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.</description>
     </item>
-    
     <item>
       <title>Lab 2 - BYO Container</title>
       <link>/workshops/openshift_4_101_dynatrace/lab2-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab2-byocontainer/</guid>
-      <description>Bring your own docker It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image. And we will dig into the details to show how all that works.
-Let&amp;rsquo;s point OpenShift to an existing built container image CLI Steps      Verify you&#39;re still in the project we created at the end of the last lab by going to the terminal and typing the following:  $ oc projects  You should see something *similar* in the last line of the output:  $ Using project &amp;#34;demo-0&amp;#34; on server &amp;#34;https://172.</description>
+      <description>Bring your own docker It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image. And we will dig into the details to show how all that works.&#xA;Let&amp;rsquo;s point OpenShift to an existing built container image CLI Steps Verify you&#39;re still in the project we created at the end of the last lab by going to the terminal and typing the following: $ oc projects You should see something *similar* in the last line of the output: $ Using project &amp;#34;demo-0&amp;#34; on server &amp;#34;https://172.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Install Dynatrace Agent</title>
       <link>/workshops/openshift_4_101_dynatrace/lab3-installagent/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab3-installagent/</guid>
-      <description>Deploy the Dynatrace OneAgent Operator on OpenShift 4.4+  Prerequisites: 1) If no existing account, sign-up for a trial with Dynatrace at https://www.dynatrace.com/trial/  Dynatrace API Token from Settings &amp;gt; Integration &amp;gt; Dynatrace API &amp;gt; Generate Token Activate the following settings:
- Access problem and event feed, metrics, and topology Read log content Write configuration    Dynatrace PaaS token PaaS (used to download OneAgent and ActiveGate installers) from Settings &amp;gt; Integration &amp;gt; Platform as a Service &amp;gt; Generate Token</description>
+      <description>Deploy the Dynatrace OneAgent Operator on OpenShift 4.4+ Prerequisites: 1) If no existing account, sign-up for a trial with Dynatrace at https://www.dynatrace.com/trial/ Dynatrace API Token from Settings &amp;gt; Integration &amp;gt; Dynatrace API &amp;gt; Generate Token Activate the following settings:&#xA;Access problem and event feed, metrics, and topology Read log content Write configuration Dynatrace PaaS token PaaS (used to download OneAgent and ActiveGate installers) from Settings &amp;gt; Integration &amp;gt; Platform as a Service &amp;gt; Generate Token</description>
     </item>
-    
     <item>
       <title>Lab 4 - Configuring Dynatrace ActiveGate (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/</guid>
-      <description>Connect your OpenShift clusters to Dynatrace with an ActiveGate to take advantage of the dedicated OpenShift overview page Connecting your OpenShift clusters to Dynatrace to take advantage of the dedicated OpenShift overview page requires that you run an ActiveGate in your environment (version 1.163+).
-See https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/monitoring/monitor-openshift-clusters-with-dynatrace/
-oc project dynatrace oc apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml serviceaccount/dynatrace-monitoring created clusterrole.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created clusterrolebinding.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created oc config view --minify -o jsonpath=&amp;#39;{.clusters[0].cluster.server}&amp;#39; https://api.ocp4.local:6443  Get the Bearer token for the OpenShift cluster using the following command: Copy the secret returned by the following command:</description>
+      <description>Connect your OpenShift clusters to Dynatrace with an ActiveGate to take advantage of the dedicated OpenShift overview page Connecting your OpenShift clusters to Dynatrace to take advantage of the dedicated OpenShift overview page requires that you run an ActiveGate in your environment (version 1.163+).&#xA;See https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/monitoring/monitor-openshift-clusters-with-dynatrace/&#xA;oc project dynatrace oc apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml serviceaccount/dynatrace-monitoring created clusterrole.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created clusterrolebinding.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created oc config view --minify -o jsonpath=&amp;#39;{.clusters[0].cluster.server}&amp;#39; https://api.ocp4.local:6443 Get the Bearer token for the OpenShift cluster using the following command: Copy the secret returned by the following command:</description>
     </item>
-    
     <item>
       <title>Lab 5 - Deploying an App with S2I</title>
       <link>/workshops/openshift_4_101_dynatrace/lab5-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab5-s2i/</guid>
-      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.
-Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
+      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.&#xA;Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Deploying a 3 Tier App</title>
       <link>/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/</guid>
-      <description>Deploying a 3 Tier App This builds on the work done in the labs so far to deploy a 3 Tier App. The reason for this lab are to highlight the capabilities of OpenShift to handle more complex application stacks and to show how Dynatrace automatically captures new applications and interactions between them.
- Instructions are located in a Red Hat blog post at:  https://developers.redhat.com/articles/deploy-a-NodeJS-app-OpenShift   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Deploying a 3 Tier App This builds on the work done in the labs so far to deploy a 3 Tier App. The reason for this lab are to highlight the capabilities of OpenShift to handle more complex application stacks and to show how Dynatrace automatically captures new applications and interactions between them.&#xA;Instructions are located in a Red Hat blog post at: https://developers.redhat.com/articles/deploy-a-NodeJS-app-OpenShift &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Developing and Managing Your Application</title>
       <link>/workshops/openshift_4_101_dynatrace/lab7-devmanage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab7-devmanage/</guid>
-      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.
-Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
+      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.&#xA;Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 8 - Webhooks and Rollbacks (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab8-rollbacks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab8-rollbacks/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 9 - Replication and Recovery (Optional)</title>
       <link>/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/</guid>
-      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.
-Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
+      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.&#xA;Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/openshift_4_101_dynatrace/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser, but you do need a free personal GitHub account.
- Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.
- Create GitHub Account Download Git Client (optional)   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser, but you do need a free personal GitHub account.&#xA;Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.&#xA;Create GitHub Account Download Git Client (optional) &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/index.html b/workshops/index.html
index e68185531..2f245dadc 100644
--- a/workshops/index.html
+++ b/workshops/index.html
@@ -307,7 +307,7 @@ <h1>Workshops</h1>
         </li>
       
         <li>
-          ansible_ansible
+          Ansible_ansible
         </li>
       
         <li>
@@ -335,7 +335,7 @@ <h1>Workshops</h1>
         </li>
       
         <li>
-          dynatrace_openshift
+          Dynatrace_openshift
         </li>
       
         <li>
@@ -400,7 +400,7 @@ <h1>Workshops</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/index.xml b/workshops/index.xml
index 701518166..49ab5557a 100644
--- a/workshops/index.xml
+++ b/workshops/index.xml
@@ -4,312 +4,197 @@
     <title>Workshops on Red Hat | Public Sector</title>
     <link>/workshops/</link>
     <description>Recent content in Workshops on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Agile Integrations Workshop - Citizen Integrator</title>
       <link>/workshops/agile_integrations_ci/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_ci/</guid>
-      <description>Description The Agile Integration Workshop teaches the development, testing, and deployment of cloud-native and connected solutions. You will walk through an API Development and Agile Integration process leveraging OpenShift, Apicurio, Microcks, Fuse, and 3scale for a sample application.
-Who should attend  Developers API Owners API Consumers Architects Technical leads  What you will learn  Exploring OpenAPI contracts Create contract-first APIs Convert existing SOAP APIs to REST API Management API Security  Introduction Red Hat&amp;rsquo;s integration solutions give you the power to connect everything in your enterprise—from apps and APIs to data and devices—to provide greater value to your customers.</description>
+      <description>Description The Agile Integration Workshop teaches the development, testing, and deployment of cloud-native and connected solutions. You will walk through an API Development and Agile Integration process leveraging OpenShift, Apicurio, Microcks, Fuse, and 3scale for a sample application.&#xA;Who should attend Developers API Owners API Consumers Architects Technical leads What you will learn Exploring OpenAPI contracts Create contract-first APIs Convert existing SOAP APIs to REST API Management API Security Introduction Red Hat&amp;rsquo;s integration solutions give you the power to connect everything in your enterprise—from apps and APIs to data and devices—to provide greater value to your customers.</description>
     </item>
-    
     <item>
       <title>Agile Integrations Workshop - Developer</title>
       <link>/workshops/agile_integrations_dev/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/agile_integrations_dev/</guid>
-      <description>Description The Agile Integration Workshop teaches the development, testing, and deployment of cloud-native and connected solutions. You will walk through an API Development and Agile Integration process leveraging OpenShift, Apicurio, Microcks, Fuse, and 3scale for a sample application.
-Who should attend  Developers API Owners API Consumers Architects Technical leads  What you will learn  Exploring OpenAPI contracts Create contract-first APIs Convert existing SOAP APIs to REST API Management API Security  Introduction Red Hat&amp;rsquo;s integration solutions give you the power to connect everything in your enterprise—from apps and APIs to data and devices—to provide greater value to your customers.</description>
+      <description>Description The Agile Integration Workshop teaches the development, testing, and deployment of cloud-native and connected solutions. You will walk through an API Development and Agile Integration process leveraging OpenShift, Apicurio, Microcks, Fuse, and 3scale for a sample application.&#xA;Who should attend Developers API Owners API Consumers Architects Technical leads What you will learn Exploring OpenAPI contracts Create contract-first APIs Convert existing SOAP APIs to REST API Management API Security Introduction Red Hat&amp;rsquo;s integration solutions give you the power to connect everything in your enterprise—from apps and APIs to data and devices—to provide greater value to your customers.</description>
     </item>
-    
     <item>
       <title>Ansible Automation Workshop</title>
       <link>/workshops/ansible_automation/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_automation/</guid>
-      <description>Workshop Description Ansible Tower will enable you to create playbooks, while building in security. Automation features will save time, empower junior staff, offload senior staff and automate your most tedious tasks!
-   Who should attend   Architects
-  Developers
-  Technical Leads
-  Operations Engineers
-     What you will learn   How to run ad hoc commands
-  How to write a playbook</description>
+      <description>Workshop Description Ansible Tower will enable you to create playbooks, while building in security. Automation features will save time, empower junior staff, offload senior staff and automate your most tedious tasks!&#xA;Who should attend Architects&#xA;Developers&#xA;Technical Leads&#xA;Operations Engineers&#xA;What you will learn How to run ad hoc commands&#xA;How to write a playbook&#xA;How to install and configure Red Hat Ansible Tower&#xA;How to use templates to save time</description>
     </item>
-    
     <item>
       <title>Ansible Tower - an Introduction</title>
       <link>/workshops/ansible_tower_intro/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_intro/</guid>
-      <description>Workshop Description This workshop will introduce you to the possibilities of automation using Ansible Tower.
- Ansible Tower will enable you to create playbooks, while building in security. Automation features will save time, empower junior staff, offload senior staff and automate your most tedious tasks!
-   Who should attend   Architects
-  Developers
-  Technical Leads
-  Operations Engineers
-     What you will learn   How to run ad hoc commands</description>
+      <description>Workshop Description This workshop will introduce you to the possibilities of automation using Ansible Tower.&#xA;Ansible Tower will enable you to create playbooks, while building in security. Automation features will save time, empower junior staff, offload senior staff and automate your most tedious tasks!&#xA;Who should attend Architects&#xA;Developers&#xA;Technical Leads&#xA;Operations Engineers&#xA;What you will learn How to run ad hoc commands&#xA;How to write a playbook&#xA;How to install and configure Red Hat Ansible Tower</description>
     </item>
-    
     <item>
       <title>Ansible Tower Workshop on Azure</title>
       <link>/workshops/ansible_tower_azure/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_tower_azure/</guid>
-      <description>Workshop Description Learn to build Red Hat Ansible Tower playbooks to build in security, empower junior staff and offload senior staff, by automating your most tedious tasks!
-   Who should attend   Architects
-  Developers
-  Technical Leads
-  Operations Engineers
-     What you will learn   How to run ad hoc commands
-  How to write a playbook</description>
+      <description>Workshop Description Learn to build Red Hat Ansible Tower playbooks to build in security, empower junior staff and offload senior staff, by automating your most tedious tasks!&#xA;Who should attend Architects&#xA;Developers&#xA;Technical Leads&#xA;Operations Engineers&#xA;What you will learn How to run ad hoc commands&#xA;How to write a playbook&#xA;How to install and configure Red Hat Ansible Tower on Azure&#xA;How to use templates to save time</description>
     </item>
-    
     <item>
-      <title>ansible_ansible</title>
+      <title>Ansible_ansible</title>
       <link>/workshops/ansible_ansible/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/ansible_ansible/</guid>
       <description></description>
     </item>
-    
     <item>
       <title>Applied Ansible Automation - Containerized Edge Workshop</title>
       <link>/workshops/alpha/ansible_with_rhocp_edge/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/alpha/ansible_with_rhocp_edge/</guid>
-      <description>Workshop Description Learn the fundamentals of the Ansible Automation platform by utilizing it in an applied fashion. As part of the workshop, you will introduced to general concepts of Ansible, pick up some principles of running Ansible adhoc commands and generating playbooks, work with the Ansible Automation platform (running on Red Hat OpenShift); while, deploying a working containerized edge solution.
- What is Ansible? Ansible is a simple open source universal automation languague (written in YAML) utilized by IT systems teams to automate IT services (provision, configure, manage, and deploy).</description>
+      <description>Workshop Description Learn the fundamentals of the Ansible Automation platform by utilizing it in an applied fashion. As part of the workshop, you will introduced to general concepts of Ansible, pick up some principles of running Ansible adhoc commands and generating playbooks, work with the Ansible Automation platform (running on Red Hat OpenShift); while, deploying a working containerized edge solution.&#xA;What is Ansible? Ansible is a simple open source universal automation languague (written in YAML) utilized by IT systems teams to automate IT services (provision, configure, manage, and deploy).</description>
     </item>
-    
     <item>
       <title>CloudForms Workshops</title>
       <link>/workshops/cloudforms41/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/cloudforms41/</guid>
-      <description>CloudForms Workshop Workshop Description Manage the hybrid environment, on-premise and commercial cloud providers to include: Quota management, auditing, Continuous discovery and tracking.
-Who should attend  Architects Developers Technical Leads Operations Engineers  What you will learn  Resource usage, optimization, and capacity planning. Cloud and container fundamentals. Configuration auditing, change tracking, and drift analysis. Continuous discovery, monitoring, and tracking.  Exercise Overview  Learn the basics of a CloudForms environment.</description>
+      <description>CloudForms Workshop Workshop Description Manage the hybrid environment, on-premise and commercial cloud providers to include: Quota management, auditing, Continuous discovery and tracking.&#xA;Who should attend Architects Developers Technical Leads Operations Engineers What you will learn Resource usage, optimization, and capacity planning. Cloud and container fundamentals. Configuration auditing, change tracking, and drift analysis. Continuous discovery, monitoring, and tracking. Exercise Overview Learn the basics of a CloudForms environment. Understand resource quota enforcement, cost allocation, and chargeback.</description>
     </item>
-    
     <item>
       <title>Container Security - A Practical Introduction</title>
       <link>/workshops/security_container_intro/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/</guid>
-      <description>A PRACTICAL INTRODUCTION TO CONTAINER SECURITY Red Hat Summit 2020 Bob Kozdemba (bkozdemb@redhat.com) Dan Walsh (dwalsh@redhat.com)
-    Abstract Linux containers provide convenient application packaging and run-time isolation in multi-tenant environments. However, the security implications of running containerized applications is often taken for granted. For example, today it is very easy to pull container images from the internet and run them in the enterprise without examining their content and authenticity.</description>
+      <description>A PRACTICAL INTRODUCTION TO CONTAINER SECURITY Red Hat Summit 2020 Bob Kozdemba (bkozdemb@redhat.com) Dan Walsh (dwalsh@redhat.com)&#xA;Abstract Linux containers provide convenient application packaging and run-time isolation in multi-tenant environments. However, the security implications of running containerized applications is often taken for granted. For example, today it is very easy to pull container images from the internet and run them in the enterprise without examining their content and authenticity. In this lab, you’ll complete a series of hands on exercises aimed at understanding the concepts, challenges and best practices associated with deploying containers in a secure fashion.</description>
     </item>
-    
     <item>
       <title>Container Security Workshop</title>
       <link>/workshops/security_containers/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/</guid>
-      <description>Description Learn how to scan, secure and leverage properties in the Linux kernel like seccomp, namespaces, ccgroups to secure your docker containers.
-   Who should attend   People familiar with containers that have had Containers 101
-  Architects
-  Developers
-  Technical leads
-  Operations Engineers
-     What you will learn   Cockpit
-  CGroups
-  Namespaces</description>
+      <description>Description Learn how to scan, secure and leverage properties in the Linux kernel like seccomp, namespaces, ccgroups to secure your docker containers.&#xA;Who should attend People familiar with containers that have had Containers 101&#xA;Architects&#xA;Developers&#xA;Technical leads&#xA;Operations Engineers&#xA;What you will learn Cockpit&#xA;CGroups&#xA;Namespaces&#xA;Seccomp&#xA;SELinux&#xA;Overview Today is meant for anyone who has any exposure to containers, whether you have used them or not. We are going to start with a short overview (yes, slideware) and then we’ll get into the lab as soon as possible.</description>
     </item>
-    
     <item>
       <title>Containers 101 Workshop</title>
       <link>/workshops/containers_101/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_101/</guid>
-      <description>Workshop Description This workshop will introduce you to Linux containers and provide you with foundational container hands-on training.
-   Who should attend Today&amp;#8217;s container workshop is meant for anyone who has any exposure to Linux containers, whether you have used it or not.
-   What you will learn   How to install docker, buildah, podman, and skopeo
-  How to run an existing container image</description>
+      <description>Workshop Description This workshop will introduce you to Linux containers and provide you with foundational container hands-on training.&#xA;Who should attend Today’s container workshop is meant for anyone who has any exposure to Linux containers, whether you have used it or not.&#xA;What you will learn How to install docker, buildah, podman, and skopeo&#xA;How to run an existing container image&#xA;How to build a new container from a base container image</description>
     </item>
-    
     <item>
       <title>DevSecOps Workshop - Secure Software Factory</title>
       <link>/workshops/secure_software_factory/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/</guid>
-      <description>Description In this workshop, you&amp;rsquo;ll be building a Secure Software Factory for a Java based website leveraging several containerized tools such as Gogs, Nexus, Jenkins, Sonarqube, and Che hosted on the OpenShift Container Platform
-Who Should Attend  Anyone who has had OpenShift 101 Architects Developers Technical leads Operations Engineers  What you will learn  A tiny bit of Jenkins Automating the development process Trusted Software Supply Chain  Agenda  Introductions and Agenda Familiarization with the Environment Setting the Context  Labs   Verify Prerequisites     Login Tour - Wetty     Lab 01 - Welcome to OpenShift     Lab 02 - Trusted Software Supply Chain     Lab 03 - CI/CD Project and Pods     Lab 04 - Jenkins and OpenShift     Lab 05 - Creating Your Pipeline     Lab 06 - Build App Stage     Lab 07 - Test Stage     Lab 08 - Static Application Security Testing     Lab 09 - Archive App     Lab 10 - Create Image Builder     Lab 11 - Build Image     Lab 12 - Create and Deploy to Dev     Lab 13 - Promote and Deploy to Stage     Lab 14 - Run Pipeline     Lab 15 - Trigger the Software Supply Chain     Lab 16 - Create Quay Account     Lab 17 - Clair Vulnerability Scan     Lab 18 - OpenSCAP DISA STIG Scan     Fin    .</description>
+      <description>Description In this workshop, you&amp;rsquo;ll be building a Secure Software Factory for a Java based website leveraging several containerized tools such as Gogs, Nexus, Jenkins, Sonarqube, and Che hosted on the OpenShift Container Platform&#xA;Who Should Attend Anyone who has had OpenShift 101 Architects Developers Technical leads Operations Engineers What you will learn A tiny bit of Jenkins Automating the development process Trusted Software Supply Chain Agenda Introductions and Agenda Familiarization with the Environment Setting the Context Labs Verify Prerequisites Login Tour - Wetty Lab 01 - Welcome to OpenShift Lab 02 - Trusted Software Supply Chain Lab 03 - CI/CD Project and Pods Lab 04 - Jenkins and OpenShift Lab 05 - Creating Your Pipeline Lab 06 - Build App Stage Lab 07 - Test Stage Lab 08 - Static Application Security Testing Lab 09 - Archive App Lab 10 - Create Image Builder Lab 11 - Build Image Lab 12 - Create and Deploy to Dev Lab 13 - Promote and Deploy to Stage Lab 14 - Run Pipeline Lab 15 - Trigger the Software Supply Chain Lab 16 - Create Quay Account Lab 17 - Clair Vulnerability Scan Lab 18 - OpenSCAP DISA STIG Scan Fin &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
-      <title>dynatrace_openshift</title>
+      <title>Dynatrace_openshift</title>
       <link>/workshops/dynatrace_openshift/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/dynatrace_openshift/</guid>
       <description></description>
     </item>
-    
     <item>
       <title>JBoss Data Virtualization Development</title>
       <link>/workshops/jdv_dev/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/</guid>
-      <description>Who should attend  Developers People who are comfortable using the command line People with knowledge of SQL People who can work with Virtual Machines or Docker People who understand REST services and JSON  What you will create  Brand new JBoss Data Virtualization install JBoss Developer Studio development environment Consume, compose and create REST data services from several data sources Apply role based security and column masking to the create REST data services An AngularJS based web application to consume and view the REST data services  Your end product You will walk away from this workshop with a basic end to end JBoss Data Virtualization environment.</description>
+      <description>Who should attend Developers People who are comfortable using the command line People with knowledge of SQL People who can work with Virtual Machines or Docker People who understand REST services and JSON What you will create Brand new JBoss Data Virtualization install JBoss Developer Studio development environment Consume, compose and create REST data services from several data sources Apply role based security and column masking to the create REST data services An AngularJS based web application to consume and view the REST data services Your end product You will walk away from this workshop with a basic end to end JBoss Data Virtualization environment.</description>
     </item>
-    
     <item>
       <title>Linux Containers the Hard Way</title>
       <link>/workshops/containers_the_hard_way/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/containers_the_hard_way/</guid>
-      <description>Workshop Description This workshop will deep dive into the Linux internals that enable containers to work. Containers will be demystified so developers and admins will have a better grasp at what their favorite container engine is doing at runtime.
-   Who should attend Today&amp;#8217;s container workshop is meant for anyone who has any exposure to Linux containers, and assumes that you have run a container or two. If you have had no exposure to containers, that&amp;#8217;s fine too, just don&amp;#8217;t be shy about asking questions.</description>
+      <description>Workshop Description This workshop will deep dive into the Linux internals that enable containers to work. Containers will be demystified so developers and admins will have a better grasp at what their favorite container engine is doing at runtime.&#xA;Who should attend Today’s container workshop is meant for anyone who has any exposure to Linux containers, and assumes that you have run a container or two. If you have had no exposure to containers, that’s fine too, just don’t be shy about asking questions.</description>
     </item>
-    
     <item>
       <title>Microservices Workshop - Strangling the Monolith</title>
       <link>/workshops/strangling_the_monolith/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/</guid>
-      <description>Microservices Workshop - Strangling the Monolith Description Large organizations have a tremendous amount of resources invested in existing monolithic applications, in the workshop you will learn a sane way to capture the benefits of containers and orchestration without having to execute a complete rewrite.
-Who should attend  Anyone who has had Containers 101 Architects Developers Technical leads -Operations Engineers  What you will learn Tour of Openshift Strangling your Monolith Microservice Integration Patterns</description>
+      <description>Microservices Workshop - Strangling the Monolith Description Large organizations have a tremendous amount of resources invested in existing monolithic applications, in the workshop you will learn a sane way to capture the benefits of containers and orchestration without having to execute a complete rewrite.&#xA;Who should attend Anyone who has had Containers 101 Architects Developers Technical leads -Operations Engineers What you will learn Tour of Openshift Strangling your Monolith Microservice Integration Patterns</description>
     </item>
-    
     <item>
       <title>OpenShift 101 - DC Metro Map Workshop</title>
       <link>/workshops/openshift_101_dcmetromap/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/</guid>
-      <description>OpenShift 101 - DC Metro Map Workshop Description This workshop will have you deploying and creating native docker images for a Node.js based website and learning to leverage the power of OpenShift to build, deploy, scale, and automate.
-Who should attend  Anyone who has had any exposure to Containers Architects Developers Technical leads Operations Engineers  What you will learn  S21 Rollback Replication and Recovery Using Labels CI/CD pipeline Blue/Green Deployment  Introduction Welcome to the workshop!</description>
+      <description>OpenShift 101 - DC Metro Map Workshop Description This workshop will have you deploying and creating native docker images for a Node.js based website and learning to leverage the power of OpenShift to build, deploy, scale, and automate.&#xA;Who should attend Anyone who has had any exposure to Containers Architects Developers Technical leads Operations Engineers What you will learn S21 Rollback Replication and Recovery Using Labels CI/CD pipeline Blue/Green Deployment Introduction Welcome to the workshop!</description>
     </item>
-    
     <item>
       <title>OpenShift 4 101</title>
       <link>/workshops/openshift_4_101/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/</guid>
-      <description>OpenShift 4 101 Description This workshop will have you deploying and creating native docker images for a Node.js based website and learning to leverage the power of OpenShift 4 to build, deploy, scale, and automate.
-Who should attend  Anyone who has had any exposure to Containers Architects Developers Technical leads Operations Engineers  What you will learn  S2I Rollback Replication and Recovery Using Labels CI/CD pipeline Blue/Green Deployment  Introduction Welcome to the workshop!</description>
+      <description>OpenShift 4 101 Description This workshop will have you deploying and creating native docker images for a Node.js based website and learning to leverage the power of OpenShift 4 to build, deploy, scale, and automate.&#xA;Who should attend Anyone who has had any exposure to Containers Architects Developers Technical leads Operations Engineers What you will learn S2I Rollback Replication and Recovery Using Labels CI/CD pipeline Blue/Green Deployment Introduction Welcome to the workshop!</description>
     </item>
-    
     <item>
       <title>OpenShift 4 101 w/Dynatrace</title>
       <link>/workshops/openshift_4_101_dynatrace/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101_dynatrace/</guid>
-      <description>OpenShift 4 101 w/Dynatrace Description This workshop will have you deploying and creating native docker images for a Node.js based website and learning to leverage the power of OpenShift 4 to build, deploy, scale, and automate. Additionaly, you will learn how to monitor the applications through the deployment of a Dynatrace OneAgent Operator.
-Who should attend  Anyone who has had any exposure to Containers Architects Developers Technical leads Operations Engineers  What you will learn  Enabling Dynatrace OneAgent Operator and integration with Dynatrace ActiveGate (optional) S2I Rollback Replication and Recovery Using Labels CI/CD pipeline Blue/Green Deployment  Introduction Welcome to the workshop!</description>
+      <description>OpenShift 4 101 w/Dynatrace Description This workshop will have you deploying and creating native docker images for a Node.js based website and learning to leverage the power of OpenShift 4 to build, deploy, scale, and automate. Additionaly, you will learn how to monitor the applications through the deployment of a Dynatrace OneAgent Operator.&#xA;Who should attend Anyone who has had any exposure to Containers Architects Developers Technical leads Operations Engineers What you will learn Enabling Dynatrace OneAgent Operator and integration with Dynatrace ActiveGate (optional) S2I Rollback Replication and Recovery Using Labels CI/CD pipeline Blue/Green Deployment Introduction Welcome to the workshop!</description>
     </item>
-    
     <item>
       <title>OpenShift Security Workshop</title>
       <link>/workshops/security_openshift/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/</guid>
-      <description>Description Learn about secrets and how to Secure your microservices and containers by using and extending Linux scanning features, SCC, Seccomp and the security API.
-   Who should attend   Anyone who has had any exposure to Containers
-  Architects
-  Developers
-  Technical leads
-  Operations Engineers
-     What you will learn   SELinux
-  Openshift deployment</description>
+      <description>Description Learn about secrets and how to Secure your microservices and containers by using and extending Linux scanning features, SCC, Seccomp and the security API.&#xA;Who should attend Anyone who has had any exposure to Containers&#xA;Architects&#xA;Developers&#xA;Technical leads&#xA;Operations Engineers&#xA;What you will learn SELinux&#xA;Openshift deployment&#xA;SCC&#xA;Seccomp&#xA;Security API&#xA;Overview Today is meant for anyone who has any exposure to Containers, whether you have used them or not.</description>
     </item>
-    
     <item>
       <title>OpenShift Serverless</title>
       <link>/workshops/openshift_serverless/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_serverless/</guid>
       <description>OpenShift Serverless Description Serverless computing allows developers to optimize their application usage by executing and billing on application resource consumption. Traditionally, this execution model was offered by cloud providers in a non-portable manner. Today, the serverless paradigm is offered on OpenShift - leveraging the innovation happening in the open source Knative project. This brings a key capability for developers to build portable cloud native applications in hybrid and multi-cloud environments.</description>
     </item>
-    
     <item>
       <title>OpenShift Service Mesh</title>
       <link>/workshops/openshift_service_mesh/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh/</guid>
-      <description>OpenShift Service Mesh Description As modern applications move toward microservices based architectures the importance of a platform to back both development and operational work grows. Development teams struggle with building, debugging, and connecting services properly. And application operations teams face increasing challenges with hybrid deployments, scaling bottlenecks, recovering from failure, and gathering metrics. Red Hat’s OpenShift Service Mesh lets you connect, secure, control, and observe your microservice based applications.
-Who should attend The workshop is ideal for developers, architects, and technical leads interested in learning more about the latest technologies for microservices based applications.</description>
+      <description>OpenShift Service Mesh Description As modern applications move toward microservices based architectures the importance of a platform to back both development and operational work grows. Development teams struggle with building, debugging, and connecting services properly. And application operations teams face increasing challenges with hybrid deployments, scaling bottlenecks, recovering from failure, and gathering metrics. Red Hat’s OpenShift Service Mesh lets you connect, secure, control, and observe your microservice based applications.&#xA;Who should attend The workshop is ideal for developers, architects, and technical leads interested in learning more about the latest technologies for microservices based applications.</description>
     </item>
-    
     <item>
       <title>Red Hat Enterprise Linux 8</title>
       <link>/workshops/rhel_8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/</guid>
-      <description>Workshop Description This workshop will cover the features, specifications and improvements that comprise the release of Red Hat Enterprise Linux Version 8 (RHEL 8). RHEL 8 brings many improvements over previous releases, including:
-   Application streams, which enables the use of bleeding edge interpreters, compilers and libraries, while maintaining full backwards compatibility and stability of the system
-  The web console has been completely overhauled, and significant new features have been added</description>
+      <description>Workshop Description This workshop will cover the features, specifications and improvements that comprise the release of Red Hat Enterprise Linux Version 8 (RHEL 8). RHEL 8 brings many improvements over previous releases, including:&#xA;Application streams, which enables the use of bleeding edge interpreters, compilers and libraries, while maintaining full backwards compatibility and stability of the system&#xA;The web console has been completely overhauled, and significant new features have been added</description>
     </item>
-    
     <item>
       <title>Red Hat OpenStack Platform 101</title>
       <link>/workshops/rhosp_101/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/</guid>
-      <description>Red Hat OpenStack Platform 101 Description During this workshop, you get your first taste of using and operating a Red Hat OpenStack Platform cloud. After the workshop, you will have hands on experience working with software defined networking, software defined storage, managing security groups and using heat to define application stacks.
-Who should attend  System Administrators Architects Technical leads Operations Engineers  What you will learn  Working in the OpenStack Dashboard and CLI Managing Neutron Networks and Floating IPs Managing Security Groups, Images and Instances Using Heat for Orchestration Using Software defined block and object Storage  Introduction This workshop on Red Hat OpenStack Platform is designed as an introduction for those who are intending to implement a cloud computing environment using OpenStack.</description>
+      <description>Red Hat OpenStack Platform 101 Description During this workshop, you get your first taste of using and operating a Red Hat OpenStack Platform cloud. After the workshop, you will have hands on experience working with software defined networking, software defined storage, managing security groups and using heat to define application stacks.&#xA;Who should attend System Administrators Architects Technical leads Operations Engineers What you will learn Working in the OpenStack Dashboard and CLI Managing Neutron Networks and Floating IPs Managing Security Groups, Images and Instances Using Heat for Orchestration Using Software defined block and object Storage Introduction This workshop on Red Hat OpenStack Platform is designed as an introduction for those who are intending to implement a cloud computing environment using OpenStack.</description>
     </item>
-    
     <item>
       <title>SELinux Policy Workshop</title>
       <link>/workshops/selinux_policy/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/</guid>
-      <description>Workshop Description Writing your own SELinux policies doesn&amp;#8217;t have to be a terrifying prospect! This workshop will walk you through the process of creating a custom policy for a source-compiled application, using the advanced tooling present in Red Hat Enterprise Linux.
-   Who should attend   Architects
-  Developers
-  Technical Leads
-  Operations Engineers
-     What you will learn   Where to find SELinux reference information</description>
+      <description>Workshop Description Writing your own SELinux policies doesn’t have to be a terrifying prospect! This workshop will walk you through the process of creating a custom policy for a source-compiled application, using the advanced tooling present in Red Hat Enterprise Linux.&#xA;Who should attend Architects&#xA;Developers&#xA;Technical Leads&#xA;Operations Engineers&#xA;What you will learn Where to find SELinux reference information&#xA;How to create a new policy framework&#xA;How to analyze AVC messages generated by SELinux</description>
     </item>
-    
     <item>
       <title>Source to Image</title>
       <link>/workshops/source_to_image/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/</guid>
-      <description>Source-to-Image - Accelerating Application Development Description Containers have transformed the IT space by leaps and bounds. Source-to-image allows developers to take advantage of containers and truly focus on their code. S2I also allows infrastructure managers to standardize both the development and deployment environments. This starts you on a path towards a high-speed, high-efficiency DevOps organization
-Who Should Attend  Anyone who has had Containers 101 Architects Developers Technical leads Operations Engineers  What you will learn  A tiny bit of Golang How to install S2I tooling How to use S2I to deploy apps with cutom frameworks  Agenda  Arrivals Introductions and Agenda Familiarization with the Environment Setting the Context Build a Container Image Create a Custom S2I Builder Create an OCP Template  Labs   Prerequisites     The Setup     Lab - Run the App     Lab - Containerize the App     Lab - Source-to-Image     Lab - Gochat S2I     Lab - Roll Dice     Conclusion    .</description>
+      <description>Source-to-Image - Accelerating Application Development Description Containers have transformed the IT space by leaps and bounds. Source-to-image allows developers to take advantage of containers and truly focus on their code. S2I also allows infrastructure managers to standardize both the development and deployment environments. This starts you on a path towards a high-speed, high-efficiency DevOps organization&#xA;Who Should Attend Anyone who has had Containers 101 Architects Developers Technical leads Operations Engineers What you will learn A tiny bit of Golang How to install S2I tooling How to use S2I to deploy apps with cutom frameworks Agenda Arrivals Introductions and Agenda Familiarization with the Environment Setting the Context Build a Container Image Create a Custom S2I Builder Create an OCP Template Labs Prerequisites The Setup Lab - Run the App Lab - Containerize the App Lab - Source-to-Image Lab - Gochat S2I Lab - Roll Dice Conclusion &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>zOpenShift Service Mesh</title>
       <link>/workshops/openshift_service_mesh_v1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/</guid>
-      <description>OpenShift Service Mesh Description As modern applications move toward microservices based architectures the importance of a platform to back both development and operational work grows. Development teams struggle with building, debugging, and connecting services properly. And application operations teams face increasing challenges with hybrid deployments, scaling bottlenecks, recovering from failure, and gathering metrics. Red Hat’s OpenShift Service Mesh lets you connect, secure, control, and observe your microservice based applications.
-Who should attend The workshop is ideal for developers, architects, and technical leads interested in learning more about the latest technologies for microservices based applications.</description>
+      <description>OpenShift Service Mesh Description As modern applications move toward microservices based architectures the importance of a platform to back both development and operational work grows. Development teams struggle with building, debugging, and connecting services properly. And application operations teams face increasing challenges with hybrid deployments, scaling bottlenecks, recovering from failure, and gathering metrics. Red Hat’s OpenShift Service Mesh lets you connect, secure, control, and observe your microservice based applications.&#xA;Who should attend The workshop is ideal for developers, architects, and technical leads interested in learning more about the latest technologies for microservices based applications.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/jdv_dev/exercise1/index.html b/workshops/jdv_dev/exercise1/index.html
index 456257127..dc9dfe51c 100644
--- a/workshops/jdv_dev/exercise1/index.html
+++ b/workshops/jdv_dev/exercise1/index.html
@@ -348,7 +348,7 @@ <h1 id="install-jboss-data-virtualization-jdv-a-namelink3a">Install JBoss Data V
 <ul>
 <li>In the location where you downloaded the installer, run the following command</li>
 </ul>
-<pre><code>java -jar jboss-dv-6.3.0-1-installer.jar
+<pre tabindex="0"><code>java -jar jboss-dv-6.3.0-1-installer.jar
 </code></pre><ul>
 <li>Follow the default prompts with the following exceptions below</li>
 </ul>
@@ -373,12 +373,12 @@ <h2 id="run-jdv-a-namelink4a">Run JDV <a name="link4"></a></h2>
 <ul>
 <li>In <code>$JBOSS_HOME/bin</code> directory run the following</li>
 </ul>
-<pre><code>./standalone.sh
+<pre tabindex="0"><code>./standalone.sh
 </code></pre><img src="../images/1-jdv-run.png" width="640px">
 <div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>If you are connecting to this server from machines other than <code>localhost</code>.  You need to allow outside connections like this</p>
-<pre><code>./standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0
+<pre tabindex="0"><code>./standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0
 </code></pre></div>
 <ul>
 <li>Verify your installation by going to http://localhost:9990/console and logging in as <code>admin/Password1!</code></li>
@@ -391,7 +391,7 @@ <h1 id="install-jboss-developer-studio-jbds-a-namelink5a">Install JBoss Develope
 <ul>
 <li>In the location where you downloaded the installer, run the following command</li>
 </ul>
-<pre><code>java -jar devstudio-11.0.0.GA-installer-standalone.jar
+<pre tabindex="0"><code>java -jar devstudio-11.0.0.GA-installer-standalone.jar
 </code></pre><ul>
 <li>
 <p>Follow the default prompts with the following exceptions</p>
@@ -410,7 +410,7 @@ <h2 id="run-jbds-a-namelink6a">Run JBDS <a name="link6"></a></h2>
 <p>Launch JBDS with the following command in the <code>$STUDIO_HOME</code> directory</p>
 </li>
 </ul>
-<pre><code>./devstudio
+<pre tabindex="0"><code>./devstudio
 </code></pre><ul>
 <li>On startup select ok add the datavirt server install you specified during installation</li>
 </ul>
@@ -418,17 +418,17 @@ <h2 id="run-jbds-a-namelink6a">Run JBDS <a name="link6"></a></h2>
 <div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>For Linux and/or Mac users running via the command prompt, if you see the following errors:</p>
-<pre><code>(Red Hat JBoss Developer Studio:23670): Gtk-WARNING **: Negative content width -5 (allocation 1, extents 3x3) while allocating gadget (node toolbar, owner GtkToolbar)
+<pre tabindex="0"><code>(Red Hat JBoss Developer Studio:23670): Gtk-WARNING **: Negative content width -5 (allocation 1, extents 3x3) while allocating gadget (node toolbar, owner GtkToolbar)
 </code></pre><p>You need a tweak to the launcher to force usage of GTK2 instead of GTK3.<br>
 Either create a wrapper script like this</p>
-<pre><code>#!/bin/bash
+<pre tabindex="0"><code>#!/bin/bash
 export SWT_GTK3=0
 
 $STUDIO_HOME/./devstudio
 </code></pre><p>or edit
 <code>$STUDIO_HOME/studio/devstudio.ini</code>
 and add</p>
-<pre><code>--launcher.GTK_version
+<pre tabindex="0"><code>--launcher.GTK_version
 2
 </code></pre><p>at the very beginning of the file</p>
 </div>
@@ -517,7 +517,7 @@ <h2 id="configure-the-server-settings-a-namelink8a">Configure the server setting
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise10/index.html b/workshops/jdv_dev/exercise10/index.html
index 81396237a..13bbb5453 100644
--- a/workshops/jdv_dev/exercise10/index.html
+++ b/workshops/jdv_dev/exercise10/index.html
@@ -379,7 +379,7 @@ <h1 id="change-users-to-view-maskingfiltering">Change users to view masking/filt
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise2/index.html b/workshops/jdv_dev/exercise2/index.html
index fd61a390c..0963e2a07 100644
--- a/workshops/jdv_dev/exercise2/index.html
+++ b/workshops/jdv_dev/exercise2/index.html
@@ -326,11 +326,11 @@ <h1 id="get-the-course-repositories">Get the course repositories</h1>
 <p>Pull down the JDV project</p>
 </li>
 </ul>
-<pre><code>git clone https://github.com/mechevarria/jdv-demo
+<pre tabindex="0"><code>git clone https://github.com/mechevarria/jdv-demo
 </code></pre><ul>
 <li>Next pull down the AngularJS client</li>
 </ul>
-<pre><code>https://github.com/mechevarria/jdv-demo-client
+<pre tabindex="0"><code>https://github.com/mechevarria/jdv-demo-client
 </code></pre><h1 id="add-the-workshop-data-to-postgresql">Add the workshop data to PostgreSQL</h1>
 <ul>
 <li>The script that needs to be run is</li>
@@ -401,7 +401,7 @@ <h1 id="get-the-course-repositories">Get the course repositories</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise3/index.html b/workshops/jdv_dev/exercise3/index.html
index c2ae3de5a..2b53c3ff4 100644
--- a/workshops/jdv_dev/exercise3/index.html
+++ b/workshops/jdv_dev/exercise3/index.html
@@ -321,11 +321,11 @@ <h1 id="prepare-the-angularjs-client">Prepare the AngularJS client</h1>
 <ul>
 <li>In the <code>jdv-demo-client</code> folder run the following command</li>
 </ul>
-<pre><code>npm install
+<pre tabindex="0"><code>npm install
 </code></pre><ul>
 <li>Afterwards run</li>
 </ul>
-<pre><code>npm run dev
+<pre tabindex="0"><code>npm run dev
 </code></pre><ul>
 <li>To start a node webserver that will host the AngularJS application.</li>
 </ul>
@@ -379,7 +379,7 @@ <h1 id="prepare-postman">Prepare Postman</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise4/index.html b/workshops/jdv_dev/exercise4/index.html
index 14cf372ce..3f2d454d7 100644
--- a/workshops/jdv_dev/exercise4/index.html
+++ b/workshops/jdv_dev/exercise4/index.html
@@ -407,7 +407,7 @@ <h1 id="test-vdb">Test VDB</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise5/index.html b/workshops/jdv_dev/exercise5/index.html
index e8e1f18c1..0d0e5406b 100644
--- a/workshops/jdv_dev/exercise5/index.html
+++ b/workshops/jdv_dev/exercise5/index.html
@@ -459,7 +459,7 @@ <h1 id="test-with-postman">Test with Postman</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise6/index.html b/workshops/jdv_dev/exercise6/index.html
index 43fdeaff6..e40a37a49 100644
--- a/workshops/jdv_dev/exercise6/index.html
+++ b/workshops/jdv_dev/exercise6/index.html
@@ -456,7 +456,7 @@ <h1 id="test-with-postman">Test with Postman</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise7/index.html b/workshops/jdv_dev/exercise7/index.html
index 9e0c90307..104337823 100644
--- a/workshops/jdv_dev/exercise7/index.html
+++ b/workshops/jdv_dev/exercise7/index.html
@@ -470,7 +470,7 @@ <h1 id="test-with-postman">Test with Postman</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise8/index.html b/workshops/jdv_dev/exercise8/index.html
index 1dcfb02a7..61f93021d 100644
--- a/workshops/jdv_dev/exercise8/index.html
+++ b/workshops/jdv_dev/exercise8/index.html
@@ -357,9 +357,9 @@ <h1 id="create-the-combined-view">Create the combined view</h1>
 <ul>
 <li>In the <strong>Transformation Editor</strong>, copy the following where clause to the end of the transformation SQL to join the added tables on the &lsquo;id&rsquo; field</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-sql" data-lang="sql">	<span style="color:#66d9ef">WHERE</span>
-		(ExcelView.Sheet1.id <span style="color:#f92672">=</span> PostgresView.order_details.id) <span style="color:#66d9ef">AND</span> (PostgresView.order_details.id <span style="color:#f92672">=</span> RestView.users.id)
-</code></pre></div><ul>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sql" data-lang="sql"><span style="display:flex;"><span>	<span style="color:#66d9ef">WHERE</span>
+</span></span><span style="display:flex;"><span>		(ExcelView.Sheet1.id <span style="color:#f92672">=</span> PostgresView.order_details.id) <span style="color:#66d9ef">AND</span> (PostgresView.order_details.id <span style="color:#f92672">=</span> RestView.users.id)
+</span></span></code></pre></div><ul>
 <li>Now click the <strong>Save and Validate</strong> button to check our work</li>
 </ul>
 <img src="../images/8-validate.png" width="800px">
@@ -425,7 +425,7 @@ <h1 id="test-with-postman">Test with Postman</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/exercise9/index.html b/workshops/jdv_dev/exercise9/index.html
index 39366810a..5d47aea53 100644
--- a/workshops/jdv_dev/exercise9/index.html
+++ b/workshops/jdv_dev/exercise9/index.html
@@ -325,7 +325,7 @@ <h1 id="create-the-additional-user">Create the additional user</h1>
 <ul>
 <li>In <code>$JBOSS_HOME/bin</code> directory run the following script with the answers to the prompts below</li>
 </ul>
-<pre><code>./add-user.sh
+<pre tabindex="0"><code>./add-user.sh
 </code></pre><div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>For windows users, the script will be <strong>add-user.bat</strong></p>
@@ -434,7 +434,7 @@ <h1 id="test-with-postman">Test with Postman</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/index.html b/workshops/jdv_dev/index.html
index 32a550de5..34004b9fd 100644
--- a/workshops/jdv_dev/index.html
+++ b/workshops/jdv_dev/index.html
@@ -386,7 +386,7 @@ <h1 id="lab-exercises">Lab Exercises</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/index.xml b/workshops/jdv_dev/index.xml
index a8afa9f53..a07a6b113 100644
--- a/workshops/jdv_dev/index.xml
+++ b/workshops/jdv_dev/index.xml
@@ -4,156 +4,92 @@
     <title>JBoss Data Virtualization Development on Red Hat | Public Sector</title>
     <link>/workshops/jdv_dev/</link>
     <description>Recent content in JBoss Data Virtualization Development on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/jdv_dev/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/jdv_dev/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1 - Install JDV and JBDS</title>
       <link>/workshops/jdv_dev/exercise1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise1/</guid>
-      <description>Table of Contents  Download JDV Download JBDS Install JDV  Run JDV   Install JBDS  Run JBDS Install teiid designer Configure server settings    Download JBoss Data Virtualization   jboss-dv-6.3.0-1-installer.jar  Download JBoss Developer Studio   devstudio-11.0.0.GA-installer-standalone.jar  Install JBoss Data Virtualization (JDV)   In the location where you downloaded the installer, run the following command  java -jar jboss-dv-6.3.0-1-installer.jar  Follow the default prompts with the following exceptions below</description>
+      <description>Table of Contents Download JDV Download JBDS Install JDV Run JDV Install JBDS Run JBDS Install teiid designer Configure server settings Download JBoss Data Virtualization jboss-dv-6.3.0-1-installer.jar Download JBoss Developer Studio devstudio-11.0.0.GA-installer-standalone.jar Install JBoss Data Virtualization (JDV) In the location where you downloaded the installer, run the following command java -jar jboss-dv-6.3.0-1-installer.jar Follow the default prompts with the following exceptions below Take note of the directory you use to install JDV, it will be helpful when installing JBoss Developer studio.</description>
     </item>
-    
     <item>
       <title>Exercise 10 - View data in AngularJS client</title>
       <link>/workshops/jdv_dev/exercise10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise10/</guid>
-      <description>View the data services   Go back to the Angualar client at http://localhost:8181
-  View each of the data services we created by navigating the lefthand pane, including the combined data service for all 3 sources
-  Change users to view masking/filtering   In the upper right, click the user icon and change the user to maskUser
-  Go to the Federated page or click reload if already on the page.</description>
+      <description>View the data services Go back to the Angualar client at http://localhost:8181&#xA;View each of the data services we created by navigating the lefthand pane, including the combined data service for all 3 sources&#xA;Change users to view masking/filtering In the upper right, click the user icon and change the user to maskUser&#xA;Go to the Federated page or click reload if already on the page.&#xA;You will see only rows with Visibility public and email is masked as anon@email.</description>
     </item>
-    
     <item>
       <title>Exercise 2 - Prepare the datasources</title>
       <link>/workshops/jdv_dev/exercise2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise2/</guid>
-      <description>Get the course repositories   There are two repositories, one that contains a sample JDV project with helper data/scripts and another which is the AngularJS frontend.
-  Pull down the JDV project
-  git clone https://github.com/mechevarria/jdv-demo  Next pull down the AngularJS client  https://github.com/mechevarria/jdv-demo-client Add the workshop data to PostgreSQL  The script that needs to be run is  jdv-demo/assets/postgres/create_insert.sql
- If you are running the instance from TurnKey Linux, you can load the data via a browser.</description>
+      <description>Get the course repositories There are two repositories, one that contains a sample JDV project with helper data/scripts and another which is the AngularJS frontend.&#xA;Pull down the JDV project&#xA;git clone https://github.com/mechevarria/jdv-demo Next pull down the AngularJS client https://github.com/mechevarria/jdv-demo-client Add the workshop data to PostgreSQL The script that needs to be run is jdv-demo/assets/postgres/create_insert.sql&#xA;If you are running the instance from TurnKey Linux, you can load the data via a browser.</description>
     </item>
-    
     <item>
       <title>Exercise 3 - Prepare Postman and AngularJS client</title>
       <link>/workshops/jdv_dev/exercise3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise3/</guid>
-      <description>Prepare the AngularJS client  In the jdv-demo-client folder run the following command  npm install  Afterwards run  npm run dev  To start a node webserver that will host the AngularJS application.  * To check go to http://localhost:8181 in your browser. You will get an error when checking the pages. That is ok since we are going to be building the data services for the web application.</description>
+      <description>Prepare the AngularJS client In the jdv-demo-client folder run the following command npm install Afterwards run npm run dev To start a node webserver that will host the AngularJS application. * To check go to http://localhost:8181 in your browser. You will get an error when checking the pages. That is ok since we are going to be building the data services for the web application. Prepare Postman Import the REST tests into Postman by going to file import Select jdv-demo/assets/demo-jdv.</description>
     </item>
-    
     <item>
       <title>Exercise 4 - Create new teiid project</title>
       <link>/workshops/jdv_dev/exercise4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise4/</guid>
-      <description>Create a new JDV project   In JBDS, do window  perspective  open perspective  other  teiid designer
-  file  new  teiid model project
-  Name the project jdv-demo and its ok to leave the default location.
-  Do change the default folders to sources, views and federated
-  
-teiid is the the upstream community project for JBoss Data Virtualization</description>
+      <description>Create a new JDV project In JBDS, do window perspective open perspective other teiid designer&#xA;file new teiid model project&#xA;Name the project jdv-demo and its ok to leave the default location.&#xA;Do change the default folders to sources, views and federated&#xA;teiid is the the upstream community project for JBoss Data Virtualization&#xA;Create a VDB file New Teiid VDB&#xA;name the vdb demo-jdv&#xA;Deploy a VDB Double click the new vdb and then click the Deploy</description>
     </item>
-    
     <item>
       <title>Exercise 5 - Import PostgreSQL data</title>
       <link>/workshops/jdv_dev/exercise5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise5/</guid>
-      <description>Import JDBC datasource  file  import  teiid designer  JDBC Database &amp;raquo; source model    Under Connection Profile, select new
-  Select PostgreSQL as the Connection Profile Type, Next
-  In the next window, click the New Driver Definition icon
-  Under the Jar List tab, select Add JAR/Zip and then select jdv-demo/assets/postgres/postgresql-42.1.4.jar, then ok
-  In the New JDBC Connection Profile window make sure to use the IP address of your PostgreSQL instance and put the credentails for the postgres user and check Save Password.</description>
+      <description>Import JDBC datasource file import teiid designer JDBC Database &amp;raquo; source model Under Connection Profile, select new&#xA;Select PostgreSQL as the Connection Profile Type, Next&#xA;In the next window, click the New Driver Definition icon&#xA;Under the Jar List tab, select Add JAR/Zip and then select jdv-demo/assets/postgres/postgresql-42.1.4.jar, then ok&#xA;In the New JDBC Connection Profile window make sure to use the IP address of your PostgreSQL instance and put the credentails for the postgres user and check Save Password.</description>
     </item>
-    
     <item>
       <title>Exercise 6 - Import REST data</title>
       <link>/workshops/jdv_dev/exercise6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise6/</guid>
-      <description>Import REST source   file  import  Web Service Source &amp;raquo; Source and View Model (REST)
-  Click New Connection Profile, then next
-  Connection URL https://jsonplaceholder.typicode.com/users
-  Response type JSON
-  Make sure Test Connection returns Ping Succeeded!, then Finish
-    Click Next
-  Set the following values like the screenshot below
-    Next and put JNDI as java:/RestDS, then Next</description>
+      <description>Import REST source file import Web Service Source &amp;raquo; Source and View Model (REST)&#xA;Click New Connection Profile, then next&#xA;Connection URL https://jsonplaceholder.typicode.com/users&#xA;Response type JSON&#xA;Make sure Test Connection returns Ping Succeeded!, then Finish&#xA;Click Next&#xA;Set the following values like the screenshot below&#xA;Next and put JNDI as java:/RestDS, then Next&#xA;In the Import from REST Web Service Source, expand the first response element then right click on the second response element and select Set as Root path</description>
     </item>
-    
     <item>
       <title>Exercise 7 - Import Excel data</title>
       <link>/workshops/jdv_dev/exercise7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise7/</guid>
-      <description>Verify Settings   You need to first verify that the Excel extensions were imported correctly into the designer
-  window  show view  other 
-  Teiid Designer  Model Extension Registry
-   In the Model Extension Registry tab at the bottom, verify in the Namespace Prefix you see the value excel and a checkbox in the imported column. If not, close the designer, re-open, click the start button to mark the server as started, and check again.</description>
+      <description>Verify Settings You need to first verify that the Excel extensions were imported correctly into the designer&#xA;window show view other Teiid Designer Model Extension Registry&#xA;In the Model Extension Registry tab at the bottom, verify in the Namespace Prefix you see the value excel and a checkbox in the imported column. If not, close the designer, re-open, click the start button to mark the server as started, and check again.</description>
     </item>
-    
     <item>
       <title>Exercise 8 - Federate Data</title>
       <link>/workshops/jdv_dev/exercise8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise8/</guid>
-      <description>Create the combined view file -&amp;gt; new -&amp;gt; teiid metadata model
-  Location demo-jdv/federated
-  Model Name FedView
-  Model Type View Model
-  Do not select any options under model builder and click Finish
-  Right-click on the FedView Package diagram and select new -&amp;gt; child -&amp;gt; table
-  Select Option 1: Build with new table wizard
-  Name combined
-   Under the PK tab, check the include box then put id_pk in the name field.</description>
+      <description>Create the combined view file -&amp;gt; new -&amp;gt; teiid metadata model&#xA;Location demo-jdv/federated&#xA;Model Name FedView&#xA;Model Type View Model&#xA;Do not select any options under model builder and click Finish&#xA;Right-click on the FedView Package diagram and select new -&amp;gt; child -&amp;gt; table&#xA;Select Option 1: Build with new table wizard&#xA;Name combined&#xA;Under the PK tab, check the include box then put id_pk in the name field. Click ok.</description>
     </item>
-    
     <item>
       <title>Exercise 9 - Secure Data Services</title>
       <link>/workshops/jdv_dev/exercise9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/exercise9/</guid>
-      <description>Overview  To secure the services we created in our VDB, we need to create an additional user on the server.  Create the additional user  In $JBOSS_HOME/bin directory run the following script with the answers to the prompts below  ./add-user.sh 
-For windows users, the script will be add-user.bat
-   Type: b) Application User
-  Username: maskUser
-  Password: Password1! (same as the one used during installation</description>
+      <description>Overview To secure the services we created in our VDB, we need to create an additional user on the server. Create the additional user In $JBOSS_HOME/bin directory run the following script with the answers to the prompts below ./add-user.sh For windows users, the script will be add-user.bat&#xA;Type: b) Application User&#xA;Username: maskUser&#xA;Password: Password1! (same as the one used during installation&#xA;groups: odata,mask&#xA;Remoting: no&#xA;Back in JBDS open the demo-jdv.</description>
     </item>
-    
     <item>
       <title>Prerequisites for JDV Development</title>
       <link>/workshops/jdv_dev/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/prerequisites/</guid>
-      <description>What you need  A free account on Red Hat Developers to download JBoss Data Virtualization and JBoss Developer Studio A Java Development Kit (JDK) 8 git available as a local command Node.js runtime, 6.x or higher Postman for testing An accessible PostgreSQL instance  Recommended: Download a pre-built VM, ISO or docker image from TurnKey Linux. The provided VM/ISO also provides an web interface for loading data. Step by step instructions are provided for a Turnkey linux instance    </description>
+      <description>What you need A free account on Red Hat Developers to download JBoss Data Virtualization and JBoss Developer Studio A Java Development Kit (JDK) 8 git available as a local command Node.js runtime, 6.x or higher Postman for testing An accessible PostgreSQL instance Recommended: Download a pre-built VM, ISO or docker image from TurnKey Linux. The provided VM/ISO also provides an web interface for loading data. Step by step instructions are provided for a Turnkey linux instance </description>
     </item>
-    
     <item>
       <title>Workshop is done!</title>
       <link>/workshops/jdv_dev/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/jdv_dev/wrapup/</guid>
-      <description>Congratulations  You imported 3 different disparate datasources and exposed them as data services. You also combined them into a federated view and applied role based security. Congratulations!  Additional resources  JDV Documentation Teiid, upstream project for JDV odata, documentation for REST data services. JDV uses odata(v2) and odata(v4). V4 must be called with the context of /odata4 [Teiid Examples] (https://github.com/teiid/teiid-embedded-examples). Github with various source examples  </description>
+      <description>Congratulations You imported 3 different disparate datasources and exposed them as data services. You also combined them into a federated view and applied role based security. Congratulations! Additional resources JDV Documentation Teiid, upstream project for JDV odata, documentation for REST data services. JDV uses odata(v2) and odata(v4). V4 must be called with the context of /odata4 [Teiid Examples] (https://github.com/teiid/teiid-embedded-examples). Github with various source examples </description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/jdv_dev/prerequisites/index.html b/workshops/jdv_dev/prerequisites/index.html
index ea2d8b32e..c39877123 100644
--- a/workshops/jdv_dev/prerequisites/index.html
+++ b/workshops/jdv_dev/prerequisites/index.html
@@ -361,7 +361,7 @@ <h1 id="what-you-need">What you need</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/jdv_dev/wrapup/index.html b/workshops/jdv_dev/wrapup/index.html
index 9879b0837..ced807e82 100644
--- a/workshops/jdv_dev/wrapup/index.html
+++ b/workshops/jdv_dev/wrapup/index.html
@@ -359,7 +359,7 @@ <h1 id="additional-resources">Additional resources</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/fin/index.html b/workshops/openshift_101_dcmetromap/fin/index.html
index 6abc04944..ed87b5f85 100644
--- a/workshops/openshift_101_dcmetromap/fin/index.html
+++ b/workshops/openshift_101_dcmetromap/fin/index.html
@@ -421,7 +421,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -681,7 +681,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -793,7 +793,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -803,7 +803,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -882,7 +882,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/index.html b/workshops/openshift_101_dcmetromap/index.html
index 98db67681..c0395b860 100644
--- a/workshops/openshift_101_dcmetromap/index.html
+++ b/workshops/openshift_101_dcmetromap/index.html
@@ -488,7 +488,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -748,7 +748,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -860,7 +860,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -870,7 +870,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -920,7 +920,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/index.xml b/workshops/openshift_101_dcmetromap/index.xml
index c98804b52..d922c9769 100644
--- a/workshops/openshift_101_dcmetromap/index.xml
+++ b/workshops/openshift_101_dcmetromap/index.xml
@@ -4,135 +4,92 @@
     <title>OpenShift 101 - DC Metro Map Workshop on Red Hat | Public Sector</title>
     <link>/workshops/openshift_101_dcmetromap/</link>
     <description>Recent content in OpenShift 101 - DC Metro Map Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/openshift_101_dcmetromap/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/openshift_101_dcmetromap/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_101_dcmetromap/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.
-Get even deeper While you&amp;rsquo;re here, we can help you install the Container Development Kit (CDK) on your laptop.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.&#xA;Get even deeper While you&amp;rsquo;re here, we can help you install the Container Development Kit (CDK) on your laptop.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Welcome</title>
       <link>/workshops/openshift_101_dcmetromap/lab1-welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab1-welcome/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift simply ensure you can login and create the project.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with.</description>
     </item>
-    
     <item>
       <title>Lab 2 - BYO Docker</title>
       <link>/workshops/openshift_101_dcmetromap/lab2-byodocker/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab2-byodocker/</guid>
       <description>Bring your own docker It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing docker assets. In this quick lab we will deploy an application using an exisiting docker image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image. And we will dig into the details to show how all that works.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Deploying an App with S2I</title>
       <link>/workshops/openshift_101_dcmetromap/lab3-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab3-s2i/</guid>
-      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.
-Let&amp;rsquo;s build a node.js web server using S2I We can do this either via the command line or the web console.</description>
+      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.&#xA;Let&amp;rsquo;s build a node.js web server using S2I We can do this either via the command line or the web console.</description>
     </item>
-    
     <item>
       <title>Lab 4 - Developing and Managing Your Application</title>
       <link>/workshops/openshift_101_dcmetromap/lab4-devmanage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab4-devmanage/</guid>
-      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.
-Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
+      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.&#xA;Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Webhooks and Rollbacks</title>
       <link>/workshops/openshift_101_dcmetromap/lab5-rollbacks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab5-rollbacks/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Replication and Recovery</title>
       <link>/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/</guid>
-      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.
-Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
+      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something out of your control. But we can plan for that failure, and planning for it let&amp;rsquo;s us minimize the impact. OpenShift supports this via what we call replication and recovery.&#xA;Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Labels</title>
       <link>/workshops/openshift_101_dcmetromap/lab7-labels/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab7-labels/</guid>
-      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.
-For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.
-Labels on a pod In a previous lab we added our web app using a S2I template.</description>
+      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.&#xA;For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.&#xA;Labels on a pod In a previous lab we added our web app using a S2I template.</description>
     </item>
-    
     <item>
       <title>Lab 8 - CI / CD Pipeline</title>
       <link>/workshops/openshift_101_dcmetromap/lab8-cicd/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab8-cicd/</guid>
-      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.
-In this lab we walk through creating a simple example of a CI/CD pipeline utlizing Jenkins, all running on top of OpenShift!</description>
+      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.&#xA;In this lab we walk through creating a simple example of a CI/CD pipeline utlizing Jenkins, all running on top of OpenShift!</description>
     </item>
-    
     <item>
       <title>Lab 9 - Blue | Green Deployment</title>
       <link>/workshops/openshift_101_dcmetromap/lab9-bluegreen/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/lab9-bluegreen/</guid>
       <description>Blue/Green deployments When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments. It addresses the desire to minimize downtime during the release of a new version of an application to production. Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified. Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.</description>
     </item>
-    
     <item>
       <title>Login Tour - Butterfly</title>
       <link>/workshops/openshift_101_dcmetromap/login_tour_wetty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/login_tour_wetty/</guid>
-      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.
-Let&amp;rsquo;s Login to the Web Console  Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.
- https://master.example.redhatgov.io:8443  Login Webpage
-Once logged in you should see your available projects - or a button to create a project if none exist already.
-So this is what an empty project looks like First let&amp;rsquo;s create a new project to do our workshop work in.</description>
+      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.&#xA;Let&amp;rsquo;s Login to the Web Console Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.&#xA;https://master.example.redhatgov.io:8443 Login Webpage&#xA;Once logged in you should see your available projects - or a button to create a project if none exist already.&#xA;So this is what an empty project looks like First let&amp;rsquo;s create a new project to do our workshop work in.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/openshift_101_dcmetromap/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_101_dcmetromap/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser, but you do need a free personal GitHub account.
- Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.
- Create GitHub Account Download Git Client (optional)   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser, but you do need a free personal GitHub account.&#xA;Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.&#xA;Create GitHub Account Download Git Client (optional) &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/openshift_101_dcmetromap/lab1-welcome/index.html b/workshops/openshift_101_dcmetromap/lab1-welcome/index.html
index d1b0246a4..289c4b7de 100644
--- a/workshops/openshift_101_dcmetromap/lab1-welcome/index.html
+++ b/workshops/openshift_101_dcmetromap/lab1-welcome/index.html
@@ -340,27 +340,27 @@ <h2 id="lets-try-the-command-line-cli">Let&rsquo;s try the command line (CLI)</h
 <blockquote>
 <p><i class="fa fa-terminal"></i> Open a terminal and login using the same URI with following command:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc login https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 --insecure-skip-tls-verify<span style="color:#f92672">=</span>true
-Authentication required <span style="color:#66d9ef">for</span> https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 <span style="color:#f92672">(</span>openshift<span style="color:#f92672">)</span>
- Username: user<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc login https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 --insecure-skip-tls-verify<span style="color:#f92672">=</span>true
+</span></span><span style="display:flex;"><span>Authentication required <span style="color:#66d9ef">for</span> https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 <span style="color:#f92672">(</span>openshift<span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span> Username: user<span class="userid">YOUR#</span>
  Password:
-Login successful.
-</code></pre></div><blockquote>
+</span></span><span style="display:flex;"><span>Login successful.
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Check to see what projects you have access to:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get projects
-</code></pre></div><h2 id="it-looks-empty-via-the-command-line-too">It looks empty via the command line too</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get projects
+</span></span></code></pre></div><h2 id="it-looks-empty-via-the-command-line-too">It looks empty via the command line too</h2>
 <p>You just created a project using the web console, let&rsquo;s tell the terminal command line tool to use it.</p>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Type the following command to use the demo project:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project demo-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project demo-<span class="userid">YOUR#</span>
 
-</code></pre></div><blockquote>
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Type the following command to show services, deployment configs, build configurations, and active deployments (this will come in handy later):</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.</p>
 <style>
 
@@ -461,7 +461,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -721,7 +721,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -833,7 +833,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -843,7 +843,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -926,7 +926,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab2-byodocker/index.html b/workshops/openshift_101_dcmetromap/lab2-byodocker/index.html
index 36b87c998..eb5e0d4ae 100644
--- a/workshops/openshift_101_dcmetromap/lab2-byodocker/index.html
+++ b/workshops/openshift_101_dcmetromap/lab2-byodocker/index.html
@@ -415,21 +415,21 @@ <h2 id="we-can-browse-our-project-details-with-the-command-line">We can browse o
 <blockquote>
 <p><i class="fa fa-terminal"></i> Try typing the following to see what is available to &lsquo;get&rsquo;:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get all
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get all
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Now let&rsquo;s look at what our image stream has in it:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get is
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe is/nexus
-</code></pre></div><div class="alert alert-info">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get is
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe is/nexus
+</span></span></code></pre></div><div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</p>
 </div>
 <blockquote>
 <p><i class="fa fa-terminal"></i> The app is running in a pod, let&rsquo;s look at that:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe pods
-</code></pre></div><h2 id="we-can-see-those-details-using-the-web-console-too">We can see those details using the web console too</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe pods
+</span></span></code></pre></div><h2 id="we-can-see-those-details-using-the-web-console-too">We can see those details using the web console too</h2>
 <p>Let&rsquo;s look at the image stream.</p>
 <blockquote>
 Click on "Builds -> Images"
@@ -451,21 +451,21 @@ <h2 id="does-this-nexus-do-anything">Does this nexus do anything?</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse2d05e6e12ae7b557da7cc05b7e29f211" class="collapsed">
+      <a data-toggle="collapse" href="#collapse07ae853123d924ba40d5c02b63c9c2f0" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse2d05e6e12ae7b557da7cc05b7e29f211" class="panel-collapse collapse ">
+  <div id="collapse07ae853123d924ba40d5c02b63c9c2f0" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> In the command line type this:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc expose service nexus
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc expose service nexus
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -533,8 +533,8 @@ <h2 id="lets-clean-this-up">Let&rsquo;s clean this up</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Let&rsquo;s clean up all this to get ready for the next lab:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc delete all --all
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc delete all --all
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>In this lab you&rsquo;ve deployed an example docker image, pulled from docker hub, into a pod running in OpenShift.  You exposed a route for clients to access that service via thier web browsers.  And you learned how to get and describe resources using the command line and the web console.  Hopefully, this basic lab also helped to get you familiar with using the CLI and navigating within the web console.</p>
 <style>
 
@@ -635,7 +635,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -895,7 +895,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1007,7 +1007,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1017,7 +1017,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1100,7 +1100,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab3-s2i/index.html b/workshops/openshift_101_dcmetromap/lab3-s2i/index.html
index 435b001c0..aeb3a4d07 100644
--- a/workshops/openshift_101_dcmetromap/lab3-s2i/index.html
+++ b/workshops/openshift_101_dcmetromap/lab3-s2i/index.html
@@ -328,22 +328,22 @@ <h2 id="lets-build-a-nodejs-web-server-using-s2i">Let&rsquo;s build a node.js we
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse88a61c2eca565ba955bd496fd443ec7d" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4333dffe0a305c1c4542ce9c69abd48a" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse88a61c2eca565ba955bd496fd443ec7d" class="panel-collapse collapse ">
+  <div id="collapse4333dffe0a305c1c4542ce9c69abd48a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
-$ oc expose service dc-metro-map
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc expose service dc-metro-map
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -423,25 +423,25 @@ <h2 id="check-out-the-build-details">Check out the build details</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse70c0688f8dd01883e3bcef2da1a96cae" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7c672af06b6df64420bceddff9219c42" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse70c0688f8dd01883e3bcef2da1a96cae" class="panel-collapse collapse ">
+  <div id="collapse7c672af06b6df64420bceddff9219c42" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get builds
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get builds
+</span></span></code></pre></div><blockquote>
 Note the name of your build from the above command output and use it to see the logs with:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs builds/<span style="color:#f92672">[</span>BUILD_NAME<span style="color:#f92672">]</span>
-</code></pre></div><p>The console will print out the full log for your build.  Note, you could pipe this to more or less for easier viewing in the CLI.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs builds/<span style="color:#f92672">[</span>BUILD_NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p>The console will print out the full log for your build.  Note, you could pipe this to more or less for easier viewing in the CLI.</p>
 
     </div>
   </div>
@@ -493,21 +493,21 @@ <h2 id="see-the-app-in-action">See the app in action</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsea50884c4b9d7fb95a491491eccfbe0ef" class="collapsed">
+      <a data-toggle="collapse" href="#collapse5063e6c3ec761dc3140668a72392b1ab" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsea50884c4b9d7fb95a491491eccfbe0ef" class="panel-collapse collapse ">
+  <div id="collapse5063e6c3ec761dc3140668a72392b1ab" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get routes
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get routes
+</span></span></code></pre></div><blockquote>
 Copy the HOST/PORT and paste into your favorite web browser:
 </blockquote>
 
@@ -651,7 +651,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -911,7 +911,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1023,7 +1023,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1033,7 +1033,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1116,7 +1116,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab4-devmanage/index.html b/workshops/openshift_101_dcmetromap/lab4-devmanage/index.html
index a9e8c46b8..bf9462f46 100644
--- a/workshops/openshift_101_dcmetromap/lab4-devmanage/index.html
+++ b/workshops/openshift_101_dcmetromap/lab4-devmanage/index.html
@@ -328,9 +328,9 @@ <h2 id="setup">Setup</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
-$ oc expose service dc-metro-map
-</code></pre></div><h2 id="see-the-app-in-action-and-inspect-some-details">See the app in action and inspect some details</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc expose service dc-metro-map
+</span></span></code></pre></div><h2 id="see-the-app-in-action-and-inspect-some-details">See the app in action and inspect some details</h2>
 <p>There is no more ambiguity or confusion about where the app came from.  OpenShift provides traceability for your running deployment back to the docker image and the registry it came from, as well as (for images built by OpenShift) back to the exact source code branch and commit.  Let&rsquo;s take a look at that.</p>
 <div class="panel-group">
   
@@ -339,21 +339,21 @@ <h2 id="setup">Setup</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsebcbff7eabb65b3b5222764f8b27a8cc7" class="collapsed">
+      <a data-toggle="collapse" href="#collapsedf4d6fb4f5af885550af9525c043155c" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsebcbff7eabb65b3b5222764f8b27a8cc7" class="panel-collapse collapse ">
+  <div id="collapsedf4d6fb4f5af885550af9525c043155c" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status
-</code></pre></div><p>This is going to show the status of your current project.  In this case it will show the dc-metro-map service (svc) with a nested deployment config (dc) along with some more info that you can ignore for now.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status
+</span></span></code></pre></div><p>This is going to show the status of your current project.  In this case it will show the dc-metro-map service (svc) with a nested deployment config (dc) along with some more info that you can ignore for now.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i>  A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration <br/>
 </blockquote>
@@ -361,8 +361,8 @@ <h4 class="panel-title">
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following to find out more about our dc:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe dc/dc-metro-map
-</code></pre></div><p>Notice under the template section it lists the containers it wants to deploy along with the path to the container image.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe dc/dc-metro-map
+</span></span></code></pre></div><p>Notice under the template section it lists the containers it wants to deploy along with the path to the container image.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> There are a few other ways you could get to this information.  If you are feeling adventurous, you might want to describe the replication controller (oc describe rc -l app=dc-metro-map), the image stream (oc describe is -l app=dc-metro-map) or the running pod itself (oc describe pod -l app=dc-metro-map).
 </blockquote>
@@ -370,8 +370,8 @@ <h4 class="panel-title">
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following to find out more about our bc:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map
-</code></pre></div><p>Notice the information about the configuration of how this app gets built.  In particular look at the github URL, the webhooks you can use to automatically trigger a new build, the docker image where the build runs inside of, and the builds that have been completed.  New let&rsquo;s look at one of those builds.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map
+</span></span></code></pre></div><p>Notice the information about the configuration of how this app gets built.  In particular look at the github URL, the webhooks you can use to automatically trigger a new build, the docker image where the build runs inside of, and the builds that have been completed.  New let&rsquo;s look at one of those builds.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following:
 </blockquote>
@@ -448,26 +448,26 @@ <h2 id="pod-logs">Pod logs</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsed17251e50d717941c20e8c2d893fe34e" class="collapsed">
+      <a data-toggle="collapse" href="#collapseb8c8014515ee60c7623e0becfd66ac4a" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsed17251e50d717941c20e8c2d893fe34e" class="panel-collapse collapse ">
+  <div id="collapseb8c8014515ee60c7623e0becfd66ac4a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>This is going to show basic details for all pods in this project (including the builders).  Let&rsquo;s look at the log for the pod running our application.  Look for the POD NAME that that is &ldquo;Running&rdquo; you will use it below.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>This is going to show basic details for all pods in this project (including the builders).  Let&rsquo;s look at the log for the pod running our application.  Look for the POD NAME that that is &ldquo;Running&rdquo; you will use it below.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following (replacing the POD ID with your pod's ID):
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span>
-</code></pre></div><p>You will see in the output details of your app starting up and any status messages it has reported since it started.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p>You will see in the output details of your app starting up and any status messages it has reported since it started.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> You can see more details about the pod itself with 'oc describe pod/<POD NAME>'
 </blockquote>
@@ -526,23 +526,23 @@ <h2 id="how-about-we-set-some-environment-variables">How about we set some envir
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse583014961abb1e09bd92be8395403c48" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef29b0634000f9ff8c48e2bb4bebdac15" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse583014961abb1e09bd92be8395403c48" class="panel-collapse collapse ">
+  <div id="collapsef29b0634000f9ff8c48e2bb4bebdac15" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p>Let&rsquo;s have a little fun.  The app has some easter eggs that get triggered when certain env vars are set to &lsquo;true&rsquo;.</p>
+       <p>Let&rsquo;s have a little fun.  The app has some easter eggs that get triggered when certain env vars are set to &rsquo;true'.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc set env dc/dc-metro-map -e BEERME<span style="color:#f92672">=</span>true
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods -w
-</code></pre></div><p>Due to the deployment config strategy being set to &ldquo;Rolling&rdquo; and the &ldquo;ConfigChange&rdquo; trigger being set, OpenShift auto deployed a new pod as soon as you updated with the env variable.  If you were quick enough you saw this happening with the get pods command</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc set env dc/dc-metro-map -e BEERME<span style="color:#f92672">=</span>true
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>Due to the deployment config strategy being set to &ldquo;Rolling&rdquo; and the &ldquo;ConfigChange&rdquo; trigger being set, OpenShift auto deployed a new pod as soon as you updated with the env variable.  If you were quick enough you saw this happening with the get pods command</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Type Ctrl+C to stop watching the pods
 </blockquote>
@@ -612,27 +612,27 @@ <h2 id="getting-into-a-pod">Getting into a pod</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse368bf25641b001e43ef9c9ed76343bf9" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4cce3b2a133bc5daca49351b8dd9f0ac" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse368bf25641b001e43ef9c9ed76343bf9" class="panel-collapse collapse ">
+  <div id="collapse4cce3b2a133bc5daca49351b8dd9f0ac" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>Find the pod name for your Running pod</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc exec -it <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span> /bin/bash
-</code></pre></div><p>You are now interactively attached to the container in your pod.  Let&rsquo;s look for the environment variables we set:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ env | grep BEER
-</code></pre></div><p>That should return the <strong>BEERME=true</strong> matching the value that we set in the deployment config.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ exit
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>Find the pod name for your Running pod</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc exec -it <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span> /bin/bash
+</span></span></code></pre></div><p>You are now interactively attached to the container in your pod.  Let&rsquo;s look for the environment variables we set:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ env | grep BEER
+</span></span></code></pre></div><p>That should return the <strong>BEERME=true</strong> matching the value that we set in the deployment config.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ exit
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -680,8 +680,8 @@ <h2 id="good-work-lets-clean-this-up">Good work, let&rsquo;s clean this up</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Let&rsquo;s clean up all this to get ready for the next lab:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc delete all -l app<span style="color:#f92672">=</span>dc-metro-map
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>dc-metro-map
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>In this lab you&rsquo;ve seen how to trace running software back to its roots, how to see details on the pods running your software, how to update deployment configurations, how to inspect logs files, how to set environment variables consistently across your environment, and how to interactively attach to running containers.  All these things should come in handy for any developer working in an OpenShift platform.</p>
 <p>To dig deeper in to details behind the steps you performed in this lab, check out the OpenShift <a href="https://docs.openshift.com/container-platform/3.4/dev_guide/index.html">developer&rsquo;s guide</a>.</p>
 <style>
@@ -783,7 +783,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1043,7 +1043,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1155,7 +1155,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1165,7 +1165,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1248,7 +1248,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab5-rollbacks/index.html b/workshops/openshift_101_dcmetromap/lab5-rollbacks/index.html
index 7ab51a748..869dd7eb2 100644
--- a/workshops/openshift_101_dcmetromap/lab5-rollbacks/index.html
+++ b/workshops/openshift_101_dcmetromap/lab5-rollbacks/index.html
@@ -383,21 +383,21 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsecf86d5888595f2da86917e08cfd39104" class="collapsed">
+      <a data-toggle="collapse" href="#collapsed2d458f0694309d3adc049eec202e8cb" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsecf86d5888595f2da86917e08cfd39104" class="panel-collapse collapse ">
+  <div id="collapsed2d458f0694309d3adc049eec202e8cb" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map | grep -i webhook
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map | grep -i webhook
+</span></span></code></pre></div><blockquote>
 Copy the Generic webhook to the clipboard
 </blockquote>
 
@@ -517,22 +517,22 @@ <h2 id="rollbacks">Rollbacks</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse96dd2ce8e5d882724e769537e24333b1" class="collapsed">
+      <a data-toggle="collapse" href="#collapsed1029e8b270cb348e172bd84da87a05e" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse96dd2ce8e5d882724e769537e24333b1" class="panel-collapse collapse ">
+  <div id="collapsed1029e8b270cb348e172bd84da87a05e" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc rollback dc-metro-map-1
-$ oc get pods -w
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc rollback dc-metro-map-1
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -693,7 +693,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -953,7 +953,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1065,7 +1065,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1075,7 +1075,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1158,7 +1158,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/index.html b/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/index.html
index 75dd94d34..7d059f9a6 100644
--- a/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/index.html
+++ b/workshops/openshift_101_dcmetromap/lab6-replicationrecovery/index.html
@@ -328,25 +328,25 @@ <h2 id="replication">Replication</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsec6b7a5ea3409de97f4b66837c750626e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse8f774a7febf11de023d340ae4cde4234" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsec6b7a5ea3409de97f4b66837c750626e" class="panel-collapse collapse ">
+  <div id="collapse8f774a7febf11de023d340ae4cde4234" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and try the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc scale --replicas<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span> dc/dc-metro-map
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc scale --replicas<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span> dc/dc-metro-map
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Check out the new pods:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>Notice that you now have 4 unique pods availble to inspect.  If you want go ahead and inspect them, using &lsquo;oc describe pod/<POD NAME>&rsquo;, you can see that each have their own IP address and logs.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>Notice that you now have 4 unique pods availble to inspect.  If you want go ahead and inspect them, using &lsquo;oc describe pod/<POD NAME>&rsquo;, you can see that each have their own IP address and logs.</p>
 
     </div>
   </div>
@@ -399,28 +399,28 @@ <h2 id="recovery">Recovery</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsea592e5619c37674d2250899f90f0ed87" class="collapsed">
+      <a data-toggle="collapse" href="#collapse17be8bd3c9f4ec2fd214f2c2173fe94f" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsea592e5619c37674d2250899f90f0ed87" class="panel-collapse collapse ">
+  <div id="collapse17be8bd3c9f4ec2fd214f2c2173fe94f" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Choose a random pod and delete it:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc delete pod/PODNAME
-$ oc get pods -w
-</code></pre></div><p>If you&rsquo;re fast enough you&rsquo;ll see the pod you deleted go &ldquo;Terminating&rdquo; and you&rsquo;ll also see a new pod immediately get created and transition from &ldquo;Pending&rdquo; to &ldquo;Running&rdquo;.  If you weren&rsquo;t fast enough you can see that your old pod is gone and a new pod is in the list with an age of only a few seconds.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc delete pod/PODNAME
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>If you&rsquo;re fast enough you&rsquo;ll see the pod you deleted go &ldquo;Terminating&rdquo; and you&rsquo;ll also see a new pod immediately get created and transition from &ldquo;Pending&rdquo; to &ldquo;Running&rdquo;.  If you weren&rsquo;t fast enough you can see that your old pod is gone and a new pod is in the list with an age of only a few seconds.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i>  You can see the more details about your replication controller with:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe rc
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe rc
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -477,38 +477,38 @@ <h2 id="application-health">Application Health</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse308612c980500fa293cad5ede5225ec4" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4259ced397e22ccb9804c7e6630687bb" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse308612c980500fa293cad5ede5225ec4" class="panel-collapse collapse ">
+  <div id="collapse4259ced397e22ccb9804c7e6630687bb" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Choose a running pod and shell into it:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc exec PODNAME -it /bin/bash
-</code></pre></div><p>You are now executing a bash shell running in the container of the pod.  Let&rsquo;s kill our webapp and see what happens.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc exec PODNAME -it /bin/bash
+</span></span></code></pre></div><p>You are now executing a bash shell running in the container of the pod.  Let&rsquo;s kill our webapp and see what happens.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> If we had multiple containers in the pod we could use "-c CONTAINER_NAME" to select the right one
 </blockquote>
 <blockquote>
 <i class="fa fa-terminal"></i> Choose a running pod and shell into its container:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ pkill -9 node
-</code></pre></div><p>This will kick you out off the container with an error like &ldquo;Error executing command in container&rdquo;</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ pkill -9 node
+</span></span></code></pre></div><p>This will kick you out off the container with an error like &ldquo;Error executing command in container&rdquo;</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Do it again - shell in and execute the same command to kill node
 </blockquote>
 <blockquote>
 <i class="fa fa-terminal"></i> Watch for the container restart
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods -w
-</code></pre></div><p>If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state.  This ensures the system doesn&rsquo;t waste resources trying to restart containers that are continuously crashing.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state.  This ensures the system doesn&rsquo;t waste resources trying to restart containers that are continuously crashing.</p>
 
     </div>
   </div>
@@ -663,7 +663,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -923,7 +923,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1035,7 +1035,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1045,7 +1045,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1128,7 +1128,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab7-labels/index.html b/workshops/openshift_101_dcmetromap/lab7-labels/index.html
index 6ea21aa22..430d9ceeb 100644
--- a/workshops/openshift_101_dcmetromap/lab7-labels/index.html
+++ b/workshops/openshift_101_dcmetromap/lab7-labels/index.html
@@ -329,35 +329,35 @@ <h2 id="labels-on-a-pod">Labels on a pod</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsedb169deb1b9a5b8e5b76369cac2464b9" class="collapsed">
+      <a data-toggle="collapse" href="#collapse84a9ab480470b043feb3ece11712285a" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsedb169deb1b9a5b8e5b76369cac2464b9" class="panel-collapse collapse ">
+  <div id="collapse84a9ab480470b043feb3ece11712285a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and try the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc describe pod/&lt;POD NAME&gt; | more
-</code></pre></div><p>You can see the Labels automatically added contain the app, deployment, and deploymentconfig.  Let&rsquo;s add a new label to this pod.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc describe pod/&lt;POD NAME&gt; | more
+</span></span></code></pre></div><p>You can see the Labels automatically added contain the app, deployment, and deploymentconfig.  Let&rsquo;s add a new label to this pod.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Add a label
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc label pod/&lt;POD NAME&gt; testdate<span style="color:#f92672">=</span>4.30.2018 testedby<span style="color:#f92672">=</span>mylastname
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc label pod/&lt;POD NAME&gt; testdate<span style="color:#f92672">=</span>4.30.2018 testedby<span style="color:#f92672">=</span>mylastname
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Look at the labels
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe pod/&lt;POD NAME&gt; | more
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe pod/&lt;POD NAME&gt; | more
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-info-circle"></i> Here's a handy way to search through all objects and look at all the labels:<br/>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe all | grep -i <span style="color:#e6db74">&#34;labels:&#34;</span>
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe all | grep -i <span style="color:#e6db74">&#34;labels:&#34;</span>
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -519,7 +519,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -779,7 +779,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -891,7 +891,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -901,7 +901,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -984,7 +984,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab8-cicd/index.html b/workshops/openshift_101_dcmetromap/lab8-cicd/index.html
index a06497940..6fe8c6019 100644
--- a/workshops/openshift_101_dcmetromap/lab8-cicd/index.html
+++ b/workshops/openshift_101_dcmetromap/lab8-cicd/index.html
@@ -391,11 +391,11 @@ <h4 class="panel-title">
 
 </div>
 
-<h2 id="use-the-cicd-hahahugoshortcode-s2-hbhb-project">Use the cicd-<span class="userid">YOUR#</span>
+<h2 id="use-the-cicd-hahahugoshortcode153s2hbhb-project">Use the cicd-<span class="userid">YOUR#</span>
  project</h2>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project cicd-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project cicd-<span class="userid">YOUR#</span>
 
-</code></pre></div><h2 id="instantiate-a-jenkins-server-in-your-project">Instantiate a Jenkins server in your project</h2>
+</span></span></code></pre></div><h2 id="instantiate-a-jenkins-server-in-your-project">Instantiate a Jenkins server in your project</h2>
 <div class="panel-group">
   
 
@@ -404,18 +404,18 @@ <h2 id="use-the-cicd-hahahugoshortcode-s2-hbhb-project">Use the cicd-<span class
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse83cd1f4c7a73bdeb8cf3b4baa1647193" class="collapsed">
+      <a data-toggle="collapse" href="#collapse76e03c948b589f5bc8ff4b5a0d0147c7" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse83cd1f4c7a73bdeb8cf3b4baa1647193" class="panel-collapse collapse ">
+  <div id="collapse76e03c948b589f5bc8ff4b5a0d0147c7" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app jenkins-ephemeral
-</code></pre></div>
+       <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app jenkins-ephemeral
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -471,8 +471,8 @@ <h2 id="create-a-sample-application-configuration">Create a sample application c
 <blockquote>
 <p>Use the &ldquo;oc create&rdquo; command to create a template resource by filename for a simple nodejs application:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/application-template.json
-</code></pre></div><h2 id="modify-the-sample-application-configuration-to-use-the-nodejs-red-hat-universal-base-image-ubihttpswwwredhatcomenblogintroducing-red-hat-universal-base-image">Modify the sample application configuration to use the Node.js <a href="https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image">Red Hat Universal Base Image (UBI)</a></h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/application-template.json
+</span></span></code></pre></div><h2 id="modify-the-sample-application-configuration-to-use-the-nodejs-red-hat-universal-base-image-ubihttpswwwredhatcomenblogintroducing-red-hat-universal-base-image">Modify the sample application configuration to use the Node.js <a href="https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image">Red Hat Universal Base Image (UBI)</a></h2>
 <blockquote>
 <p>The template used above references a DEPRECATED: A Centos7 based NodeJS v0.10 image for use with OpenShift v3.</p>
 </blockquote>
@@ -484,21 +484,21 @@ <h2 id="create-a-sample-application-configuration">Create a sample application c
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsecc944a0ec241266bfb41ca8efcb109a4" class="collapsed">
+      <a data-toggle="collapse" href="#collapse3e0ec758ba39dfc4b4c7ca5b091e0254" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsecc944a0ec241266bfb41ca8efcb109a4" class="panel-collapse collapse ">
+  <div id="collapse3e0ec758ba39dfc4b4c7ca5b091e0254" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 Find and replace "nodejs-010-centos7" with "nodejs-10"
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc edit template nodejs-helloworld-sample
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc edit template nodejs-helloworld-sample
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -551,8 +551,8 @@ <h2 id="create-a-sample-application-from-template">Create a sample application f
 <blockquote>
 <p>Use the &ldquo;oc process&rdquo; command to create a simple nodejs application from the template file:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc process nodejs-helloworld-sample -p NAMESPACE<span style="color:#f92672">=</span>registry.access.redhat.com/ubi7 | oc create -f -
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc process nodejs-helloworld-sample -p NAMESPACE<span style="color:#f92672">=</span>registry.access.redhat.com/ubi7 | oc create -f -
+</span></span></code></pre></div><blockquote>
 <p>Click on &ldquo;Overview&rdquo; within the OpenShift console to display the sample application configuration</p>
 </blockquote>
 <p><img src="../images/ocp-lab-cicd-app-create.png" width="900"><br/></p>
@@ -565,25 +565,25 @@ <h2 id="confirm-you-can-access-jenkins">Confirm you can access Jenkins</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsef8a6bfa7fdc06b8fe6eb9300cdc3406a" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec22e63d28bedcbbc7728c13e24b50818" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsef8a6bfa7fdc06b8fe6eb9300cdc3406a" class="panel-collapse collapse ">
+  <div id="collapsec22e63d28bedcbbc7728c13e24b50818" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Get the route to the Jenkins server. Your HOST/PORT values will differ
 from the example below.
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get route
-NAME       HOST/PORT                            PATH      SERVICES   PORT      TERMINATION     WILDCARD
-frontend   frontend-cicd.192.168.42.27.xip.io             frontend   &lt;all&gt;     edge            None
-jenkins    jenkins-cicd.192.168.42.27.xip.io              jenkins    &lt;all&gt;     edge/Redirect   None
-</code></pre></div><p>Use Jenkins HOST/PORT to access through web browser</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get route
+</span></span><span style="display:flex;"><span>NAME       HOST/PORT                            PATH      SERVICES   PORT      TERMINATION     WILDCARD
+</span></span><span style="display:flex;"><span>frontend   frontend-cicd.192.168.42.27.xip.io             frontend   &lt;all&gt;     edge            None
+</span></span><span style="display:flex;"><span>jenkins    jenkins-cicd.192.168.42.27.xip.io              jenkins    &lt;all&gt;     edge/Redirect   None
+</span></span></code></pre></div><p>Use Jenkins HOST/PORT to access through web browser</p>
 
     </div>
   </div>
@@ -651,82 +651,82 @@ <h2 id="create-a-jenkins-pipeline-using-openshift">Create a Jenkins pipeline usi
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse62e31951cf15246dd9f09978a47f52cb" class="collapsed">
+      <a data-toggle="collapse" href="#collapse44de831e3f83ea27c4d5d31d577cef78" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse62e31951cf15246dd9f09978a47f52cb" class="panel-collapse collapse ">
+  <div id="collapse44de831e3f83ea27c4d5d31d577cef78" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <p>Copy and paste the following into bash.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc create -f - <span style="color:#e6db74">&lt;&lt;EOF
-</span><span style="color:#e6db74">kind: &#34;BuildConfig&#34;
-</span><span style="color:#e6db74">apiVersion: &#34;v1&#34;
-</span><span style="color:#e6db74">metadata:
-</span><span style="color:#e6db74">  name: &#34;pipeline&#34;
-</span><span style="color:#e6db74">spec:
-</span><span style="color:#e6db74">  strategy:
-</span><span style="color:#e6db74">    jenkinsPipelineStrategy:
-</span><span style="color:#e6db74">      jenkinsfile: |-
-</span><span style="color:#e6db74">        pipeline {
-</span><span style="color:#e6db74">          agent any
-</span><span style="color:#e6db74">          stages {
-</span><span style="color:#e6db74">            stage(&#39;buildFrontEnd&#39;) {
-</span><span style="color:#e6db74">              steps {
-</span><span style="color:#e6db74">                script {
-</span><span style="color:#e6db74">                  openshift.withCluster() {
-</span><span style="color:#e6db74">                    openshift.withProject() {
-</span><span style="color:#e6db74">                      openshift.selector(&#34;bc&#34;, &#34;frontend&#34;).startBuild(&#34;--wait=true&#34;, &#34;--follow&#34;)
-</span><span style="color:#e6db74">                    }
-</span><span style="color:#e6db74">                  }
-</span><span style="color:#e6db74">                }
-</span><span style="color:#e6db74">              }
-</span><span style="color:#e6db74">            }
-</span><span style="color:#e6db74">            stage(&#39;deployFrontEnd&#39;) {
-</span><span style="color:#e6db74">              steps {
-</span><span style="color:#e6db74">                script {
-</span><span style="color:#e6db74">                  openshift.withCluster() {
-</span><span style="color:#e6db74">                    openshift.withProject() {
-</span><span style="color:#e6db74">                      openshift.selector(&#34;dc&#34;, &#34;frontend&#34;).rollout().latest()
-</span><span style="color:#e6db74">                    }
-</span><span style="color:#e6db74">                  }
-</span><span style="color:#e6db74">                }
-</span><span style="color:#e6db74">              }
-</span><span style="color:#e6db74">            }
-</span><span style="color:#e6db74">            stage(&#39;promoteToProd&#39;) {
-</span><span style="color:#e6db74">              steps {
-</span><span style="color:#e6db74">                script {
-</span><span style="color:#e6db74">                  timeout(time: 15, unit: &#39;MINUTES&#39;) {
-</span><span style="color:#e6db74">                    input message: &#34;Promote to PROD?&#34;, ok: &#34;Promote&#34;
-</span><span style="color:#e6db74">                  }
-</span><span style="color:#e6db74">                  openshift.withCluster() {
-</span><span style="color:#e6db74">                    openshift.withProject() {
-</span><span style="color:#e6db74">                      openshift.tag(&#34;origin-nodejs-sample:latest&#34;, &#34;origin-nodejs-sample:prod&#34;)
-</span><span style="color:#e6db74">                    }
-</span><span style="color:#e6db74">                  }
-</span><span style="color:#e6db74">                }
-</span><span style="color:#e6db74">              }
-</span><span style="color:#e6db74">            }
-</span><span style="color:#e6db74">            stage(&#39;scaleUp&#39;) {
-</span><span style="color:#e6db74">              steps {
-</span><span style="color:#e6db74">                script {
-</span><span style="color:#e6db74">                  openshift.withCluster() {
-</span><span style="color:#e6db74">                    openshift.withProject() {
-</span><span style="color:#e6db74">                      openshift.selector(&#34;dc&#34;, &#34;frontend-prod&#34;).scale(&#34;--replicas=2&#34;)
-</span><span style="color:#e6db74">                    }
-</span><span style="color:#e6db74">                  }
-</span><span style="color:#e6db74">                }
-</span><span style="color:#e6db74">              }
-</span><span style="color:#e6db74">            }
-</span><span style="color:#e6db74">          }
-</span><span style="color:#e6db74">        }
-</span><span style="color:#e6db74">EOF</span>
-</code></pre></div><p>Expected output:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">buildconfig <span style="color:#e6db74">&#34;pipeline&#34;</span> created
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc create -f - <span style="color:#e6db74">&lt;&lt;EOF
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">kind: &#34;BuildConfig&#34;
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">apiVersion: &#34;v1&#34;
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">metadata:
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">  name: &#34;pipeline&#34;
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">spec:
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">  strategy:
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    jenkinsPipelineStrategy:
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">      jenkinsfile: |-
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">        pipeline {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">          agent any
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">          stages {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            stage(&#39;buildFrontEnd&#39;) {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              steps {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                script {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  openshift.withCluster() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    openshift.withProject() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                      openshift.selector(&#34;bc&#34;, &#34;frontend&#34;).startBuild(&#34;--wait=true&#34;, &#34;--follow&#34;)
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            stage(&#39;deployFrontEnd&#39;) {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              steps {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                script {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  openshift.withCluster() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    openshift.withProject() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                      openshift.selector(&#34;dc&#34;, &#34;frontend&#34;).rollout().latest()
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            stage(&#39;promoteToProd&#39;) {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              steps {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                script {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  timeout(time: 15, unit: &#39;MINUTES&#39;) {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    input message: &#34;Promote to PROD?&#34;, ok: &#34;Promote&#34;
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  openshift.withCluster() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    openshift.withProject() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                      openshift.tag(&#34;origin-nodejs-sample:latest&#34;, &#34;origin-nodejs-sample:prod&#34;)
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            stage(&#39;scaleUp&#39;) {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              steps {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                script {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  openshift.withCluster() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    openshift.withProject() {
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                      openshift.selector(&#34;dc&#34;, &#34;frontend-prod&#34;).scale(&#34;--replicas=2&#34;)
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                    }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                  }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">                }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">              }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">            }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">          }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">        }
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">EOF</span>
+</span></span></code></pre></div><p>Expected output:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>buildconfig <span style="color:#e6db74">&#34;pipeline&#34;</span> created
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -737,80 +737,80 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse49be2700e9c194abf08a0c21d8ec8b70" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef3f741393868e526d81914e65d61fdc9" class="collapsed">
       
         Web Console Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse49be2700e9c194abf08a0c21d8ec8b70" class="panel-collapse collapse ">
+  <div id="collapsef3f741393868e526d81914e65d61fdc9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <p>Use the following OpenShift build configuration to create the pipeline.</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">kind: <span style="color:#e6db74">&#34;BuildConfig&#34;</span>
-apiVersion: <span style="color:#e6db74">&#34;v1&#34;</span>
-metadata:
-  name: <span style="color:#e6db74">&#34;pipeline&#34;</span>
-spec:
-  strategy:
-    jenkinsPipelineStrategy:
-      jenkinsfile: |-
-        pipeline <span style="color:#f92672">{</span>
-          agent any
-          stages <span style="color:#f92672">{</span>
-            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;buildFrontEnd&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
-              steps <span style="color:#f92672">{</span>
-                script <span style="color:#f92672">{</span>
-                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                      openshift.selector<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;bc&#34;</span>, <span style="color:#e6db74">&#34;frontend&#34;</span><span style="color:#f92672">)</span>.startBuild<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;--wait=true&#34;</span>, <span style="color:#e6db74">&#34;--follow&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">}</span>
-                  <span style="color:#f92672">}</span>
-                <span style="color:#f92672">}</span>
-              <span style="color:#f92672">}</span>
-            <span style="color:#f92672">}</span>
-            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;deployFrontEnd&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
-              steps <span style="color:#f92672">{</span>
-                script <span style="color:#f92672">{</span>
-                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                      openshift.selector<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;dc&#34;</span>, <span style="color:#e6db74">&#34;frontend&#34;</span><span style="color:#f92672">)</span>.rollout<span style="color:#f92672">()</span>.latest<span style="color:#f92672">()</span>
-                    <span style="color:#f92672">}</span>
-                  <span style="color:#f92672">}</span>
-                <span style="color:#f92672">}</span>
-              <span style="color:#f92672">}</span>
-            <span style="color:#f92672">}</span>
-            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;promoteToProd&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
-              steps <span style="color:#f92672">{</span>
-                script <span style="color:#f92672">{</span>
-                  timeout<span style="color:#f92672">(</span>time: 15, unit: <span style="color:#e6db74">&#39;MINUTES&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
-                    input message: <span style="color:#e6db74">&#34;Promote to PROD?&#34;</span>, ok: <span style="color:#e6db74">&#34;Promote&#34;</span>
-                  <span style="color:#f92672">}</span>
-                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                      openshift.tag<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;origin-nodejs-sample:latest&#34;</span>, <span style="color:#e6db74">&#34;origin-nodejs-sample:prod&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">}</span>
-                  <span style="color:#f92672">}</span>
-                <span style="color:#f92672">}</span>
-              <span style="color:#f92672">}</span>
-            <span style="color:#f92672">}</span>
-            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;scaleUp&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
-              steps <span style="color:#f92672">{</span>
-                script <span style="color:#f92672">{</span>
-                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
-                      openshift.selector<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;dc&#34;</span>, <span style="color:#e6db74">&#34;frontend-prod&#34;</span><span style="color:#f92672">)</span>.scale<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;--replicas=2&#34;</span><span style="color:#f92672">)</span>
-                    <span style="color:#f92672">}</span>
-                  <span style="color:#f92672">}</span>
-                <span style="color:#f92672">}</span>
-              <span style="color:#f92672">}</span>
-            <span style="color:#f92672">}</span>
-          <span style="color:#f92672">}</span>
-        <span style="color:#f92672">}</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>kind: <span style="color:#e6db74">&#34;BuildConfig&#34;</span>
+</span></span><span style="display:flex;"><span>apiVersion: <span style="color:#e6db74">&#34;v1&#34;</span>
+</span></span><span style="display:flex;"><span>metadata:
+</span></span><span style="display:flex;"><span>  name: <span style="color:#e6db74">&#34;pipeline&#34;</span>
+</span></span><span style="display:flex;"><span>spec:
+</span></span><span style="display:flex;"><span>  strategy:
+</span></span><span style="display:flex;"><span>    jenkinsPipelineStrategy:
+</span></span><span style="display:flex;"><span>      jenkinsfile: |-
+</span></span><span style="display:flex;"><span>        pipeline <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>          agent any
+</span></span><span style="display:flex;"><span>          stages <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;buildFrontEnd&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>              steps <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                script <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                      openshift.selector<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;bc&#34;</span>, <span style="color:#e6db74">&#34;frontend&#34;</span><span style="color:#f92672">)</span>.startBuild<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;--wait=true&#34;</span>, <span style="color:#e6db74">&#34;--follow&#34;</span><span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>                    <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                  <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>              <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;deployFrontEnd&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>              steps <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                script <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                      openshift.selector<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;dc&#34;</span>, <span style="color:#e6db74">&#34;frontend&#34;</span><span style="color:#f92672">)</span>.rollout<span style="color:#f92672">()</span>.latest<span style="color:#f92672">()</span>
+</span></span><span style="display:flex;"><span>                    <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                  <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>              <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;promoteToProd&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>              steps <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                script <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                  timeout<span style="color:#f92672">(</span>time: 15, unit: <span style="color:#e6db74">&#39;MINUTES&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                    input message: <span style="color:#e6db74">&#34;Promote to PROD?&#34;</span>, ok: <span style="color:#e6db74">&#34;Promote&#34;</span>
+</span></span><span style="display:flex;"><span>                  <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                      openshift.tag<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;origin-nodejs-sample:latest&#34;</span>, <span style="color:#e6db74">&#34;origin-nodejs-sample:prod&#34;</span><span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>                    <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                  <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>              <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            stage<span style="color:#f92672">(</span><span style="color:#e6db74">&#39;scaleUp&#39;</span><span style="color:#f92672">)</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>              steps <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                script <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                  openshift.withCluster<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                    openshift.withProject<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
+</span></span><span style="display:flex;"><span>                      openshift.selector<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;dc&#34;</span>, <span style="color:#e6db74">&#34;frontend-prod&#34;</span><span style="color:#f92672">)</span>.scale<span style="color:#f92672">(</span><span style="color:#e6db74">&#34;--replicas=2&#34;</span><span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>                    <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                  <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>                <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>              <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">}</span>
+</span></span></code></pre></div><blockquote>
 <p>Choose <em>Add to project</em> -&gt; <em>Import YAML</em></p>
 </blockquote>
 <img src="../images/ocp-lab-cicd-import-yaml.png" width="900">
@@ -866,24 +866,24 @@ <h2 id="confirm-both-the-test-and-production-services-are-available">Confirm bot
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse21fe62d737f2e9b621aa9cfb14b5eb54" class="collapsed">
+      <a data-toggle="collapse" href="#collapse29f1baee9aa379382c0431043f997135" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse21fe62d737f2e9b621aa9cfb14b5eb54" class="panel-collapse collapse ">
+  <div id="collapse29f1baee9aa379382c0431043f997135" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <p>Use the <code>oc get routes</code> command to get the HOST/PORT (URLs) needed to access the frontend and frontend-prod services. Your HOST/PORT values will differ
 from the example below.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get routes
-
-NAME            HOST/PORT                            PATH      SERVICES        PORT      TERMINATION     WILDCARD
-frontend        frontend-cicd-XX.apps.eadgbe.net                  frontend        &lt;all&gt;     edge            None
-frontend-prod   frontend-prod-cicd-XX.apps.eadgbe.net             frontend-prod   web       edge            None
-</code></pre></div><p>Use a web browser to visit the HOST/PORT (URLs) for the frontend and frontend-prod services. Don&rsquo;t forget the <code>https://</code> prefix.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get routes
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>NAME            HOST/PORT                            PATH      SERVICES        PORT      TERMINATION     WILDCARD
+</span></span><span style="display:flex;"><span>frontend        frontend-cicd-XX.apps.eadgbe.net                  frontend        &lt;all&gt;     edge            None
+</span></span><span style="display:flex;"><span>frontend-prod   frontend-prod-cicd-XX.apps.eadgbe.net             frontend-prod   web       edge            None
+</span></span></code></pre></div><p>Use a web browser to visit the HOST/PORT (URLs) for the frontend and frontend-prod services. Don&rsquo;t forget the <code>https://</code> prefix.</p>
 
     </div>
   </div>
@@ -935,19 +935,19 @@ <h2 id="edit-the-pipeline">Edit the pipeline.</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse3b4d51191166f4b234ea762204841fbb" class="collapsed">
+      <a data-toggle="collapse" href="#collapseb9d3c3630956842315d73544da431eaf" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse3b4d51191166f4b234ea762204841fbb" class="panel-collapse collapse ">
+  <div id="collapseb9d3c3630956842315d73544da431eaf" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <p>If you are comfortable using the <strong>vi</strong> editor:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc edit bc/pipeline
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc edit bc/pipeline
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -1084,7 +1084,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1344,7 +1344,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1456,7 +1456,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1466,7 +1466,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1549,7 +1549,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/lab9-bluegreen/index.html b/workshops/openshift_101_dcmetromap/lab9-bluegreen/index.html
index 9a837656c..c3babb1cd 100644
--- a/workshops/openshift_101_dcmetromap/lab9-bluegreen/index.html
+++ b/workshops/openshift_101_dcmetromap/lab9-bluegreen/index.html
@@ -321,21 +321,21 @@ <h1 id="bluegreen-deployments">Blue/Green deployments</h1>
 <p>When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments.  It addresses the desire to minimize downtime during the release of a new version of an application to production.  Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified.  Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.  In this lab, we will walk through a simple Blue/Green workflow with an simple web application on OpenShift.</p>
 <h2 id="before-starting">Before starting</h2>
 <p>Before we get started with the Blue/Green deployment lab, lets clean up some of the projects from the previous lab.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc delete all -l app<span style="color:#f92672">=</span>jenkins-ephemeral
-$ oc delete all -l app<span style="color:#f92672">=</span>nodejs-helloworld-sample
-$ oc delete project cicd-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>jenkins-ephemeral
+</span></span><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>nodejs-helloworld-sample
+</span></span><span style="display:flex;"><span>$ oc delete project cicd-<span class="userid">YOUR#</span>
 
-</code></pre></div><h2 id="lets-deploy-an-application">Lets deploy an application</h2>
+</span></span></code></pre></div><h2 id="lets-deploy-an-application">Lets deploy an application</h2>
 <p>To demonstrate Blue/Green deployments, we&rsquo;ll use a simple application that renders a colored box as an example. Using your GitHub account, please fork the following <a href="https://github.com/RedHatGov/openshift-workshops">https://github.com/RedHatGov/openshift-workshops</a> <a href="https://github.com/RedHatGov/openshift-workshops">project</a>.</p>
 <p>You should be comfortable deploying an app at this point, but here are the steps anyway:</p>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project bluegreen-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project bluegreen-<span class="userid">YOUR#</span>
 
-$ oc new-app --name<span style="color:#f92672">=</span>green <span style="color:#f92672">[</span>your-project-repo-url<span style="color:#f92672">]</span> --context-dir<span style="color:#f92672">=</span>dc-metro-map
-$ oc expose service green
-</code></pre></div><p>Note that we exposed this application using a route named &ldquo;green&rdquo;. Wait for the application to become available, then navigate to your application and validate it deployed correctly.</p>
+</span></span><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>green <span style="color:#f92672">[</span>your-project-repo-url<span style="color:#f92672">]</span> --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc expose service green
+</span></span></code></pre></div><p>Note that we exposed this application using a route named &ldquo;green&rdquo;. Wait for the application to become available, then navigate to your application and validate it deployed correctly.</p>
 <h2 id="release-a-new-version-of-our-app-and-test-it-in-the-same-environment">Release a new version of our app and test it in the same environment</h2>
 <p>What we&rsquo;ll do next is create a new version of the application called &ldquo;blue&rdquo;. The quickest way to make a change to the code is directly in the GitHub web interface. In GitHub, edit the dc-metro-map/views/dcmetro.jade file in your repo.</p>
 <p><img src="../images/ocp-lab-bluegreen-editgithub.png" width="900"><br/></p>
@@ -344,8 +344,8 @@ <h2 id="release-a-new-version-of-our-app-and-test-it-in-the-same-environment">Re
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app --name<span style="color:#f92672">=</span>blue <span style="color:#f92672">[</span>your-project-repo-url<span style="color:#f92672">]</span> --context-dir<span style="color:#f92672">=</span>dc-metro-map
-</code></pre></div><p>Wait for the &ldquo;blue&rdquo; application to become avialable before proceeding.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>blue <span style="color:#f92672">[</span>your-project-repo-url<span style="color:#f92672">]</span> --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span></code></pre></div><p>Wait for the &ldquo;blue&rdquo; application to become avialable before proceeding.</p>
 <h2 id="switch-from-green-to-blue">Switch from Green to Blue</h2>
 <p>Now that we are satisfied with our change we can do the Green/Blue switch.  With OpenShift services and routes, this is super simple.  Follow the steps below to make the switch:</p>
 <div class="panel-group">
@@ -355,21 +355,21 @@ <h2 id="switch-from-green-to-blue">Switch from Green to Blue</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse670f4cba23d6c52ea622100cb206b642" class="collapsed">
+      <a data-toggle="collapse" href="#collapse70c013b3de9bf8431047b56238a0f42e" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse670f4cba23d6c52ea622100cb206b642" class="panel-collapse collapse ">
+  <div id="collapse70c013b3de9bf8431047b56238a0f42e" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc edit route green
-</code></pre></div><p>This will bring up the Route configuration yaml. Edit the element spec: to: name and change it&rsquo;s value from &ldquo;green&rdquo; to &ldquo;blue&rdquo;.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc edit route green
+</span></span></code></pre></div><p>This will bring up the Route configuration yaml. Edit the element spec: to: name and change it&rsquo;s value from &ldquo;green&rdquo; to &ldquo;blue&rdquo;.</p>
 
     </div>
   </div>
@@ -518,7 +518,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -778,7 +778,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -890,7 +890,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -900,7 +900,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -983,7 +983,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/login_tour_wetty/index.html b/workshops/openshift_101_dcmetromap/login_tour_wetty/index.html
index 88a2d7e5d..4411a8020 100644
--- a/workshops/openshift_101_dcmetromap/login_tour_wetty/index.html
+++ b/workshops/openshift_101_dcmetromap/login_tour_wetty/index.html
@@ -323,8 +323,8 @@ <h2 id="lets-login-to-the-web-console">Let&rsquo;s Login to the Web Console</h2>
 <blockquote>
 <p>Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443
-</code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443
+</span></span></code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
 <em>Login Webpage</em></p>
 <p>Once logged in you should see your available projects - or a button to create a project if none exist already.</p>
 <h2 id="so-this-is-what-an-empty-project-looks-like">So this is what an empty project looks like</h2>
@@ -492,7 +492,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -752,7 +752,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -864,7 +864,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -874,7 +874,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -957,7 +957,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_101_dcmetromap/prerequisites/index.html b/workshops/openshift_101_dcmetromap/prerequisites/index.html
index 79b7c86db..eff04f0e8 100644
--- a/workshops/openshift_101_dcmetromap/prerequisites/index.html
+++ b/workshops/openshift_101_dcmetromap/prerequisites/index.html
@@ -423,7 +423,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -683,7 +683,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -795,7 +795,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -805,7 +805,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -884,7 +884,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/fin/index.html b/workshops/openshift_4_101/fin/index.html
index 0c653fed3..849e3658b 100644
--- a/workshops/openshift_4_101/fin/index.html
+++ b/workshops/openshift_4_101/fin/index.html
@@ -418,7 +418,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -678,7 +678,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -790,7 +790,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -800,7 +800,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -879,7 +879,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/index.html b/workshops/openshift_4_101/index.html
index 8c6600553..73f877f8d 100644
--- a/workshops/openshift_4_101/index.html
+++ b/workshops/openshift_4_101/index.html
@@ -518,7 +518,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -778,7 +778,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -890,7 +890,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -900,7 +900,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -950,7 +950,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/index.xml b/workshops/openshift_4_101/index.xml
index f61c1c6ff..a742f3706 100644
--- a/workshops/openshift_4_101/index.xml
+++ b/workshops/openshift_4_101/index.xml
@@ -4,189 +4,127 @@
     <title>OpenShift 4 101 on Red Hat | Public Sector</title>
     <link>/workshops/openshift_4_101/</link>
     <description>Recent content in OpenShift 4 101 on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/openshift_4_101/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/openshift_4_101/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_4_101/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.
- OpenShift Architecture OpenShift Developer&amp;rsquo;s Site   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenShift environment. And hopefully, you have a deeper understanding of how containers and container orchestration works. Please feel free to continue to &amp;ldquo;kick the tires&amp;rdquo; in the demo environment we&amp;rsquo;ve setup and explore both the web console and the oc command line client.&#xA;OpenShift Architecture OpenShift Developer&amp;rsquo;s Site &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Key Terms</title>
       <link>/workshops/openshift_4_101/keyterms/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/keyterms/</guid>
-      <description>Key Terms We will be using the following terms throughout the workshop labs; so, here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way; but, these are the basics to get you started.
- Container - Your software wrapped in a complete filesystem containing everything it needs to run Image - We are talking about docker images; read-only and used to create containers Image Stream - An image stream comprises one or more OCI images identified by tags.</description>
+      <description>Key Terms We will be using the following terms throughout the workshop labs; so, here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way; but, these are the basics to get you started.&#xA;Container - Your software wrapped in a complete filesystem containing everything it needs to run Image - We are talking about docker images; read-only and used to create containers Image Stream - An image stream comprises one or more OCI images identified by tags.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Welcome</title>
       <link>/workshops/openshift_4_101/lab1-welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab1-welcome/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the OpenShift console to help you get familiar with the user interface. If you are already familiar with the basics of OpenShift, this will be easy in that we are simply ensuring you can login and create a project.
-Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.
-Let&amp;rsquo;s Login to the Web Console  Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the OpenShift console to help you get familiar with the user interface. If you are already familiar with the basics of OpenShift, this will be easy in that we are simply ensuring you can login and create a project.&#xA;Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.&#xA;Let&amp;rsquo;s Login to the Web Console Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</description>
     </item>
-    
     <item>
       <title>Lab 2 - BYO Container</title>
       <link>/workshops/openshift_4_101/lab2-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab2-byocontainer/</guid>
-      <description>Bring your own OCI image It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image.
-Let&amp;rsquo;s point OpenShift to an existing built container image Choose either to complete the steps via CLI or Web Console.</description>
+      <description>Bring your own OCI image It&amp;rsquo;s easy to get started with OpenShift whether you&amp;rsquo;re using our app templates or bringing your existing assets. In this quick lab we will deploy an application using an exisiting container image. OpenShift will create an image stream for the image as well as deploy and manage containers based on that image.&#xA;Let&amp;rsquo;s point OpenShift to an existing built container image Choose either to complete the steps via CLI or Web Console.</description>
     </item>
-    
     <item>
       <title>Lab 2.1 - Reviewing container details</title>
       <link>/workshops/openshift_4_101/lab2.1-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab2.1-byocontainer/</guid>
-      <description>Now that we have a running container, we can browse our project details with the command line https://console-openshift-console.apps.example.redhatgov.io/terminal
-  Try typing the following to see what is available to &amp;lsquo;get&amp;rsquo;:
- $ oc project demo-YOUR# $ oc get all   Now let&amp;rsquo;s look at what our image stream has in it:
- $ oc get is $ oc describe is/nexus 
-An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</description>
+      <description>Now that we have a running container, we can browse our project details with the command line https://console-openshift-console.apps.example.redhatgov.io/terminal&#xA;Try typing the following to see what is available to &amp;lsquo;get&amp;rsquo;:&#xA;$ oc project demo-YOUR# $ oc get all Now let&amp;rsquo;s look at what our image stream has in it:&#xA;$ oc get is $ oc describe is/nexus An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</description>
     </item>
-    
     <item>
       <title>Lab 2.2 - Clean-up &amp; Summary</title>
       <link>/workshops/openshift_4_101/lab2.2-byocontainer/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab2.2-byocontainer/</guid>
-      <description>Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal
-Let&amp;rsquo;s clean this up   Let&amp;rsquo;s clean up all this to get ready for the next lab:
- $ oc project demo-YOUR# $ oc delete all --selector app=nexus Summary In this lab, you&amp;rsquo;ve deployed an example container image into a pod running in OpenShift. You exposed a route for clients to access that service via their web browsers. And you learned how to get and describe resources using the command line and the web console.</description>
+      <description>Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal&#xA;Let&amp;rsquo;s clean this up Let&amp;rsquo;s clean up all this to get ready for the next lab:&#xA;$ oc project demo-YOUR# $ oc delete all --selector app=nexus Summary In this lab, you&amp;rsquo;ve deployed an example container image into a pod running in OpenShift. You exposed a route for clients to access that service via their web browsers. And you learned how to get and describe resources using the command line and the web console.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Deploying an App with S2I</title>
       <link>/workshops/openshift_4_101/lab3-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab3-s2i/</guid>
-      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.
-Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
+      <description>Source to Image (S2I) One of the useful components of OpenShift is its source-to-image capability. S2I is a framework that makes it easy to turn your source code into runnable images. The main advantage of using S2I for building reproducible docker images is the ease of use for developers. You&amp;rsquo;ll see just how simple it can be in this lab.&#xA;Let&amp;rsquo;s build a node.js web app, using S2I We can do this either via the command line or the web console.</description>
     </item>
-    
     <item>
       <title>Lab 3.1 - Check out the build details</title>
       <link>/workshops/openshift_4_101/lab3.1-s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab3.1-s2i/</guid>
-      <description>Check out the build details We can see the details of what the S2I builder did. This can be helpful to diagnose issues if builds are failing.
- TIP: For a node.js app, running &amp;ldquo;npm shrinkwrap&amp;rdquo; is a good practice to perform on your branch before releasing changes that you plan to build/deploy as an image with S2I
-CLI Steps    Terminal access  https://console-openshift-console.apps.example.redhatgov.io/terminal    Goto the terminal and type the following:  $ oc get builds  Note the name of your build from the above command output and use it to see the logs with:  $ oc logs builds/[BUILD_NAME] The console will print out the full log for your build.</description>
+      <description>Check out the build details We can see the details of what the S2I builder did. This can be helpful to diagnose issues if builds are failing.&#xA;TIP: For a node.js app, running &amp;ldquo;npm shrinkwrap&amp;rdquo; is a good practice to perform on your branch before releasing changes that you plan to build/deploy as an image with S2I&#xA;CLI Steps Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal Goto the terminal and type the following: $ oc get builds Note the name of your build from the above command output and use it to see the logs with: $ oc logs builds/[BUILD_NAME] The console will print out the full log for your build.</description>
     </item>
-    
     <item>
       <title>Lab 4 - Developing and Managing Your Application</title>
       <link>/workshops/openshift_4_101/lab4-devmanage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab4-devmanage/</guid>
-      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.
-Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
+      <description>Developing and managing an application in OpenShift In this lab we will explore some of the common activities undertaken by developers working in OpenShift. You will become familiar with how to use environment variables, secrets, build configurations, and more. Let&amp;rsquo;s look at some of the basic things a developer might care about for a deployed app.&#xA;Setup From the previous lab you should have the DC Metro Maps web app running in OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Webhooks and Rollbacks</title>
       <link>/workshops/openshift_4_101/lab5-rollbacks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab5-rollbacks/</guid>
-      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.
-A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
+      <description>Build Triggers, Webhooks and Rollbacks - Oh My! Once you have an app deployed in OpenShift you can take advantage of some continuous capabilities that help to enable DevOps and automate your management process. We will cover some of those in this lab: Build triggers, webhooks, and rollbacks.&#xA;A bit of configuration We are going to do some integration and coding with an external git repository. For this lab we are going to use github, if you don&amp;rsquo;t already have an account, you can create one here.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Application Replication</title>
       <link>/workshops/openshift_4_101/lab6-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab6-replicationrecovery/</guid>
-      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something completely out of your control. But, we can plan for such failures, thus minimizing their impact. OpenShift supports this via the replication and recovery functionality.
-Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state. Assuming you still have the dc-metro-map project running we can manually scale up our replicas to handle increased user load.</description>
+      <description>Things will go wrong, and that&amp;rsquo;s why we have replication and recovery Things will go wrong with your software, or your hardware, or from something completely out of your control. But, we can plan for such failures, thus minimizing their impact. OpenShift supports this via the replication and recovery functionality.&#xA;Replication Let&amp;rsquo;s walk through a simple example of how the replication controller can keep your deployment at a desired state. Assuming you still have the dc-metro-map project running we can manually scale up our replicas to handle increased user load.</description>
     </item>
-    
     <item>
       <title>Lab 6.1 - Application Recovery</title>
       <link>/workshops/openshift_4_101/lab6.1-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab6.1-replicationrecovery/</guid>
-      <description>Recovery Okay, now that we have a slightly more interesting replication state, we can test a service outages scenario. In this scenario, the dc-metro-map replication controller will ensure that other pods are created to replace those that become unhealthy. Let&amp;rsquo;s forcibly inflict an issue and see how OpenShift responds.
-CLI Steps    Terminal access  https://console-openshift-console.apps.example.redhatgov.io/terminal    Choose a random pod and delete it:  $ oc get pods $ oc delete pod/PODNAME $ oc get pods -w If you&amp;rsquo;re fast enough you&amp;rsquo;ll see the pod you deleted go &amp;ldquo;Terminating&amp;rdquo; and you&amp;rsquo;ll also see a new pod immediately get created and transition from &amp;ldquo;Pending&amp;rdquo; to &amp;ldquo;Running&amp;rdquo;.</description>
+      <description>Recovery Okay, now that we have a slightly more interesting replication state, we can test a service outages scenario. In this scenario, the dc-metro-map replication controller will ensure that other pods are created to replace those that become unhealthy. Let&amp;rsquo;s forcibly inflict an issue and see how OpenShift responds.&#xA;CLI Steps Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal Choose a random pod and delete it: $ oc get pods $ oc delete pod/PODNAME $ oc get pods -w If you&amp;rsquo;re fast enough you&amp;rsquo;ll see the pod you deleted go &amp;ldquo;Terminating&amp;rdquo; and you&amp;rsquo;ll also see a new pod immediately get created and transition from &amp;ldquo;Pending&amp;rdquo; to &amp;ldquo;Running&amp;rdquo;.</description>
     </item>
-    
     <item>
       <title>Lab 6.2 - Application Health</title>
       <link>/workshops/openshift_4_101/lab6.2-replicationrecovery/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab6.2-replicationrecovery/</guid>
-      <description>Application Health In addition to the health of your application&amp;rsquo;s pods, OpenShift will watch the containers inside those pods. Let&amp;rsquo;s forcibly inflict some issues and see how OpenShift responds.
-CLI Steps    Terminal access  https://console-openshift-console.apps.example.redhatgov.io/terminal    Choose a running pod and shell into it:  $ oc get pods $ oc exec PODNAME -it /bin/bash You are now executing a bash shell running in the container of the pod.</description>
+      <description>Application Health In addition to the health of your application&amp;rsquo;s pods, OpenShift will watch the containers inside those pods. Let&amp;rsquo;s forcibly inflict some issues and see how OpenShift responds.&#xA;CLI Steps Terminal access https://console-openshift-console.apps.example.redhatgov.io/terminal Choose a running pod and shell into it: $ oc get pods $ oc exec PODNAME -it /bin/bash You are now executing a bash shell running in the container of the pod. Let&amp;rsquo;s kill our webapp and see what happens.</description>
     </item>
-    
     <item>
       <title>Lab 7 - Labels</title>
       <link>/workshops/openshift_4_101/lab7-labels/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab7-labels/</guid>
-      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.
-For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.
-Labels on a pod In a previous lab we added our web app using a S2I template.</description>
+      <description>Labels This is a pretty simple lab, we are going to explore labels. You can use labels to organize, group, or select API objects.&#xA;For example, pods are &amp;ldquo;tagged&amp;rdquo; with labels, and then services use label selectors to identify the pods they proxy to. This makes it possible for services to reference groups of pods, even treating pods with potentially different docker containers as related entities.&#xA;Labels on a pod In a previous lab we added our web app using a S2I template.</description>
     </item>
-    
     <item>
       <title>Lab 8 - CI / CD Pipeline</title>
       <link>/workshops/openshift_4_101/lab8-cicd/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab8-cicd/</guid>
-      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.
-In this lab we walk through creating a simple example of a CI/CD [pipeline] utilizing Jenkins, all running on top of OpenShift!</description>
+      <description>CI/CD Defined In modern software projects many teams utilize the concept of Continuous Integration (CI) and Continuous Delivery (CD). By setting up a tool chain that continuously builds, tests, and stages software releases, a team can ensure that their product can be reliably released at any time. OpenShift can be an enabler in the creation and management of this tool chain.&#xA;In this lab we walk through creating a simple example of a CI/CD [pipeline] utilizing Jenkins, all running on top of OpenShift!</description>
     </item>
-    
     <item>
       <title>Lab 9 - Blue | Green Deployment</title>
       <link>/workshops/openshift_4_101/lab9-bluegreen/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/lab9-bluegreen/</guid>
       <description>Blue/Green deployments When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments. It addresses the desire to minimize downtime during the release of a new version of an application to production. Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified. Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/openshift_4_101/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_4_101/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser, but you do need a free personal GitHub account.
- Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.
- Create GitHub Account   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.4); -webkit-animation-name: fadeIn; -webkit-animation-duration: 0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser, but you do need a free personal GitHub account.&#xA;Create a Github account If you don&amp;rsquo;t have a person GitHub account please sign up here to create a free account.&#xA;Create GitHub Account &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/openshift_4_101/keyterms/index.html b/workshops/openshift_4_101/keyterms/index.html
index 53c7a6951..7100d7520 100644
--- a/workshops/openshift_4_101/keyterms/index.html
+++ b/workshops/openshift_4_101/keyterms/index.html
@@ -373,7 +373,7 @@ <h1 id="key-terms">Key Terms</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab1-welcome/index.html b/workshops/openshift_4_101/lab1-welcome/index.html
index 414784ae9..3a4b5eead 100644
--- a/workshops/openshift_4_101/lab1-welcome/index.html
+++ b/workshops/openshift_4_101/lab1-welcome/index.html
@@ -343,19 +343,19 @@ <h2 id="so-this-is-what-an-empty-project-looks-like">So this is what an empty pr
 </blockquote>
 <p>This is going to take you to the next logical step of adding something to the project, but we don&rsquo;t want to do that just yet.</p>
 <h2 id="lets-launch-a-terminal">Let&rsquo;s launch a terminal.</h2>
-<p>At the top of the screen, click the **[&gt;_]** button.</p>
-<p>&lt;img src=&rdquo;../images/ocp-redhat-terminal-launch.gif&quot;<br>
+<p>At the top of the screen, click the <strong>[&gt;_]</strong> button.</p>
+<p>&lt;img src=&quot;../images/ocp-redhat-terminal-launch.gif&quot;<br>
 <em><strong>Note:</strong></em> If the button does not exist, it may be necessary for the cluster administrator to load the <strong>&ldquo;Red Hat Terminal Operator&rdquo;</strong>.</p>
 <p><i class="fa fa-terminal"></i> Check to see what projects you have access to:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get projects
-oc get projects
-NAME          DISPLAY NAME   STATUS
-terminal-<span class="userid">YOUR#</span>                  Active
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get projects
+</span></span><span style="display:flex;"><span>oc get projects
+</span></span><span style="display:flex;"><span>NAME          DISPLAY NAME   STATUS
+</span></span><span style="display:flex;"><span>terminal-<span class="userid">YOUR#</span>                  Active
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Type the following command to show services, deployment configs, build configurations, and active deployments (this will come in handy later):</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.</p>
 <style>
 
@@ -456,7 +456,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -716,7 +716,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -828,7 +828,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -838,7 +838,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -921,7 +921,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab2-byocontainer/index.html b/workshops/openshift_4_101/lab2-byocontainer/index.html
index 0061ecc1a..d1908e497 100644
--- a/workshops/openshift_4_101/lab2-byocontainer/index.html
+++ b/workshops/openshift_4_101/lab2-byocontainer/index.html
@@ -404,20 +404,20 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsee66df6f6fb8775ef7bbc52f3b3e756eb" class="collapsed">
+      <a data-toggle="collapse" href="#collapsed42f04a8915f076d6bc8dd6aa25dee9b" class="collapsed">
       
         Web Console Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsee66df6f6fb8775ef7bbc52f3b3e756eb" class="panel-collapse collapse ">
+  <div id="collapsed42f04a8915f076d6bc8dd6aa25dee9b" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <p>Ensure that you are in &ldquo;Developer&rdquo; mode, by clicking on the menu, in the top left corner under the logo and selecting &ldquo;Developer&rdquo;
 <img src="../images/ocp-switch-developer.gif"><br><br></p>
 <hr>
-<p>Create a new project by selecting the &ldquo;Project:&rdquo; drop down and selecting &ldquo;Create project&quot;<br>
+<p>Create a new project by selecting the &ldquo;Project:&rdquo; drop down and selecting &ldquo;Create project&rdquo;<br>
 Note: When prompted, ensure to create the project with the name demo-<span class="userid">YOUR#</span>
 <img src="../images/ocp-addToProjectButton.gif"><br></p>
 <hr>
@@ -548,7 +548,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -808,7 +808,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -920,7 +920,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -930,7 +930,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1013,7 +1013,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab2.1-byocontainer/index.html b/workshops/openshift_4_101/lab2.1-byocontainer/index.html
index e3a09b6fb..5b9747d40 100644
--- a/workshops/openshift_4_101/lab2.1-byocontainer/index.html
+++ b/workshops/openshift_4_101/lab2.1-byocontainer/index.html
@@ -322,22 +322,22 @@ <h2 id="now-that-we-have-a-running-container-we-can-browse-our-project-details-w
 <blockquote>
 <p><i class="fa fa-terminal"></i> Try typing the following to see what is available to &lsquo;get&rsquo;:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project demo-<span class="userid">YOUR#</span>
-$ oc get all
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project demo-<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>$ oc get all
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Now let&rsquo;s look at what our image stream has in it:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get is
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe is/nexus
-</code></pre></div><div class="alert alert-info">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get is
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe is/nexus
+</span></span></code></pre></div><div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</p>
 </div>
 <blockquote>
 <p><i class="fa fa-terminal"></i> The app is running in a pod, let&rsquo;s look at that:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe pods
-</code></pre></div><h2 id="we-can-see-those-details-using-the-web-console-too">We can see those details using the web console too</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe pods
+</span></span></code></pre></div><h2 id="we-can-see-those-details-using-the-web-console-too">We can see those details using the web console too</h2>
 <p><code>https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span></code></p>
 <p>Let&rsquo;s look at the image stream.</p>
 <blockquote>
@@ -459,7 +459,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -719,7 +719,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -831,7 +831,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -841,7 +841,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -924,7 +924,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab2.2-byocontainer/index.html b/workshops/openshift_4_101/lab2.2-byocontainer/index.html
index 016cc3bae..8bd0ea5a7 100644
--- a/workshops/openshift_4_101/lab2.2-byocontainer/index.html
+++ b/workshops/openshift_4_101/lab2.2-byocontainer/index.html
@@ -323,9 +323,9 @@ <h2 id="lets-clean-this-up">Let&rsquo;s clean this up</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Let&rsquo;s clean up all this to get ready for the next lab:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project demo-<span class="userid">YOUR#</span>
-$ oc delete all --selector app<span style="color:#f92672">=</span>nexus
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project demo-<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>$ oc delete all --selector app<span style="color:#f92672">=</span>nexus
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>In this lab, you&rsquo;ve deployed an example container image into a pod running in OpenShift.  You exposed a route for clients to access that service via their web browsers.  And you learned how to get and describe resources using the command line and the web console.  Hopefully, this basic lab also helped to get you familiar with using the CLI and navigating within the web console.</p>
 <style>
 
@@ -426,7 +426,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -686,7 +686,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -798,7 +798,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -808,7 +808,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -891,7 +891,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab3-s2i/index.html b/workshops/openshift_4_101/lab3-s2i/index.html
index e70cc9b93..8abefe78c 100644
--- a/workshops/openshift_4_101/lab3-s2i/index.html
+++ b/workshops/openshift_4_101/lab3-s2i/index.html
@@ -522,7 +522,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -782,7 +782,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -894,7 +894,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -904,7 +904,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -987,7 +987,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab3.1-s2i/index.html b/workshops/openshift_4_101/lab3.1-s2i/index.html
index 28490ea2c..075a29442 100644
--- a/workshops/openshift_4_101/lab3.1-s2i/index.html
+++ b/workshops/openshift_4_101/lab3.1-s2i/index.html
@@ -327,14 +327,14 @@ <h2 id="check-out-the-build-details">Check out the build details</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsec3bce64928fbc9318486ae6a93aed175" class="collapsed">
+      <a data-toggle="collapse" href="#collapseef4738849cb0c34350961c8902f3eb1e" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsec3bce64928fbc9318486ae6a93aed175" class="panel-collapse collapse ">
+  <div id="collapseef4738849cb0c34350961c8902f3eb1e" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -344,12 +344,12 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get builds
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get builds
+</span></span></code></pre></div><blockquote>
 Note the name of your build from the above command output and use it to see the logs with:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs builds/<span style="color:#f92672">[</span>BUILD_NAME<span style="color:#f92672">]</span>
-</code></pre></div><p>The console will print out the full log for your build.  Note, you could pipe this to more or less for easier viewing in the CLI.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs builds/<span style="color:#f92672">[</span>BUILD_NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p>The console will print out the full log for your build.  Note, you could pipe this to more or less for easier viewing in the CLI.</p>
 
     </div>
   </div>
@@ -397,14 +397,14 @@ <h2 id="see-the-app-in-action">See the app in action</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse780b93216d2adcf10c9c13afe07e0b41" class="collapsed">
+      <a data-toggle="collapse" href="#collapse675287386c21cbb3052e784ec6f3181c" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse780b93216d2adcf10c9c13afe07e0b41" class="panel-collapse collapse ">
+  <div id="collapse675287386c21cbb3052e784ec6f3181c" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -414,8 +414,8 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following (ensure you are in the right project):
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get routes
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get routes
+</span></span></code></pre></div><blockquote>
 Copy the HOST/PORT and paste into your favorite web browser:
 </blockquote>
 
@@ -563,7 +563,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -823,7 +823,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -935,7 +935,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -945,7 +945,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1028,7 +1028,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab4-devmanage/index.html b/workshops/openshift_4_101/lab4-devmanage/index.html
index 46c4396eb..9f9f937b6 100644
--- a/workshops/openshift_4_101/lab4-devmanage/index.html
+++ b/workshops/openshift_4_101/lab4-devmanage/index.html
@@ -330,14 +330,14 @@ <h2 id="see-the-app-in-action-and-inspect-some-details">See the app in action an
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsefcbe379a7736b8cfa3f3938b680b1b38" class="collapsed">
+      <a data-toggle="collapse" href="#collapsed67a236c617d5a4ee84705c2223ac832" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsefcbe379a7736b8cfa3f3938b680b1b38" class="panel-collapse collapse ">
+  <div id="collapsed67a236c617d5a4ee84705c2223ac832" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -347,8 +347,8 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status
-</code></pre></div><p>This is going to show the status of your current project.  In this case it will show the dc-metro-map service (svc) with a nested deployment config(also called a &ldquo;DC&rdquo;) along with some more info that you can ignore for now.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status
+</span></span></code></pre></div><p>This is going to show the status of your current project.  In this case it will show the dc-metro-map service (svc) with a nested deployment config(also called a &ldquo;DC&rdquo;) along with some more info that you can ignore for now.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i>  A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration <br/>
 </blockquote>
@@ -356,8 +356,8 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following to find out more about our dc:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe deploymentconfig/dc-metro-map
-</code></pre></div><p>Notice under the template section it lists the containers it wants to deploy along with the path to the container image.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe deploymentconfig/dc-metro-map
+</span></span></code></pre></div><p>Notice under the template section it lists the containers it wants to deploy along with the path to the container image.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> There are a few other ways you could get to this information.  If you are feeling adventurous, you might also want to try to:
 </blockquote>
@@ -382,8 +382,8 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following to find out more about our bc:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map
-</code></pre></div><p>Notice the information about the configuration of how this app gets built.  In particular look at the github URL, the webhooks you can use to automatically trigger a new build, the docker image where the build runs inside of, and the builds that have been completed.  New let&rsquo;s look at one of those builds.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map
+</span></span></code></pre></div><p>Notice the information about the configuration of how this app gets built.  In particular look at the github URL, the webhooks you can use to automatically trigger a new build, the docker image where the build runs inside of, and the builds that have been completed.  New let&rsquo;s look at one of those builds.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following:
 </blockquote>
@@ -472,14 +472,14 @@ <h2 id="pod-logs">Pod logs</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsed4f0e0924d122802f1a9465337a19034" class="collapsed">
+      <a data-toggle="collapse" href="#collapse6f30583dc1df74dfc7b9599820f5187d" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsed4f0e0924d122802f1a9465337a19034" class="panel-collapse collapse ">
+  <div id="collapse6f30583dc1df74dfc7b9599820f5187d" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -489,13 +489,13 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>This is going to show basic details for all pods in this project (including the builders).  Let&rsquo;s look at the log for the pod running our application.  Look for the POD NAME that that is &ldquo;Running&rdquo; you will use it below.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>This is going to show basic details for all pods in this project (including the builders).  Let&rsquo;s look at the log for the pod running our application.  Look for the POD NAME that that is &ldquo;Running&rdquo; you will use it below.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following (replacing the POD ID with your pod's ID):
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span>
-</code></pre></div><p>You will see in the output details of your app starting up and any status messages it has reported since it started.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p>You will see in the output details of your app starting up and any status messages it has reported since it started.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> You can see more details about the pod itself with 'oc describe pod/<POD NAME>'
 </blockquote>
@@ -562,27 +562,27 @@ <h2 id="how-about-we-set-some-environment-variables">How about we set some envir
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsef3cb1768b1b1fc28317bd81fc3d0ca0e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse0d1455f46e82c952d1045de8f7ac1598" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsef3cb1768b1b1fc28317bd81fc3d0ca0e" class="panel-collapse collapse ">
+  <div id="collapse0d1455f46e82c952d1045de8f7ac1598" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
 <pre>
 https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/terminal
 </pre>
-<p>Let&rsquo;s have a little fun.  The app has some easter eggs that get triggered when certain environment variables are set to &lsquo;true&rsquo;.</p>
+<p>Let&rsquo;s have a little fun.  The app has some easter eggs that get triggered when certain environment variables are set to &rsquo;true'.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc set env deploymentconfig/dc-metro-map -e BEERME<span style="color:#f92672">=</span>true
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods -w
-</code></pre></div><p>Due to the deployment config strategy being set to &ldquo;Rolling&rdquo; and the &ldquo;ConfigChange&rdquo; trigger being set, OpenShift auto deployed a new pod as soon as you updated the environment variable.  If you were quick enough, you might have seen this happening, with the &ldquo;oc get pods -w&rdquo; command</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc set env deploymentconfig/dc-metro-map -e BEERME<span style="color:#f92672">=</span>true
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>Due to the deployment config strategy being set to &ldquo;Rolling&rdquo; and the &ldquo;ConfigChange&rdquo; trigger being set, OpenShift auto deployed a new pod as soon as you updated the environment variable.  If you were quick enough, you might have seen this happening, with the &ldquo;oc get pods -w&rdquo; command</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Type Ctrl+C to stop watching the pods
 </blockquote>
@@ -657,14 +657,14 @@ <h2 id="getting-into-a-pod">Getting into a pod</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse492c0dd064445b3f37e48423231a4fa3" class="collapsed">
+      <a data-toggle="collapse" href="#collapse9b5a4b05e8f2b77c357c9dc9e6e1ee0f" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse492c0dd064445b3f37e48423231a4fa3" class="panel-collapse collapse ">
+  <div id="collapse9b5a4b05e8f2b77c357c9dc9e6e1ee0f" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -674,14 +674,14 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>Find the pod name for your Running pod</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc exec -it <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span> -- /bin/bash
-</code></pre></div><p>You are now interactively attached to the container in your pod.  Let&rsquo;s look for the environment variables we set:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ env | grep BEER
-</code></pre></div><p>That should return the <strong>BEERME=true</strong> matching the value that we set in the deployment config.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ exit
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>Find the pod name for your Running pod</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc exec -it <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span> -- /bin/bash
+</span></span></code></pre></div><p>You are now interactively attached to the container in your pod.  Let&rsquo;s look for the environment variables we set:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ env | grep BEER
+</span></span></code></pre></div><p>That should return the <strong>BEERME=true</strong> matching the value that we set in the deployment config.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ exit
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -740,10 +740,10 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Let&rsquo;s clean up all this to get ready for the next lab:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project demo-<span class="userid">YOUR#</span>
-$ oc delete all -l app<span style="color:#f92672">=</span>dc-metro-map
-$ oc delete secrets dc-metro-map-generic-webhook-secret dc-metro-map-github-webhook-secret 2&gt;/dev/null
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project demo-<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc delete secrets dc-metro-map-generic-webhook-secret dc-metro-map-github-webhook-secret 2&gt;/dev/null
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>In this lab you&rsquo;ve seen how to trace running software back to its roots, how to see details on the pods running your software, how to update deployment configurations, how to inspect logs files, how to set environment variables consistently across your environment, and how to interactively attach to running containers.  All these things should come in handy for any developer working in an OpenShift platform.</p>
 <p>To dig deeper into the details behind the steps you performed in this lab, check out the OpenShift documentation<a href="https://docs.openshift.com/container-platform/latest/welcome/index.html">1</a>.</p>
 <style>
@@ -845,7 +845,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1105,7 +1105,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1217,7 +1217,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1227,7 +1227,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1310,7 +1310,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab5-rollbacks/index.html b/workshops/openshift_4_101/lab5-rollbacks/index.html
index ad9835749..7c94ec760 100644
--- a/workshops/openshift_4_101/lab5-rollbacks/index.html
+++ b/workshops/openshift_4_101/lab5-rollbacks/index.html
@@ -399,14 +399,14 @@ <h3 id="web-console-access">Web Console access</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse6dc6679b28b42f5b14b999d15a34142e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse3a0aa5144f11cd4b1052f37fb2e84426" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse6dc6679b28b42f5b14b999d15a34142e" class="panel-collapse collapse ">
+  <div id="collapse3a0aa5144f11cd4b1052f37fb2e84426" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -416,26 +416,26 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get bc/dc-metro-map -o yaml | grep github-webhook
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get bc/dc-metro-map -o yaml | grep github-webhook
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> ...which returns the name of the secret that we need to find:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">name: dc-metro-map-github-webhook-secret
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>name: dc-metro-map-github-webhook-secret
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Now that you have the name of the secret, you can get its value:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ curl -o jq -L https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64
-$ chmod <span style="color:#ae81ff">0755</span> jq
-$ SECRET<span style="color:#f92672">=</span><span style="color:#e6db74">`</span>oc get secrets dc-metro-map-github-webhook-secret -o json | ./jq <span style="color:#e6db74">&#34;.data.WebHookSecretKey&#34;</span> | base64 -di<span style="color:#e6db74">`</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ curl -o jq -L https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64
+</span></span><span style="display:flex;"><span>$ chmod <span style="color:#ae81ff">0755</span> jq
+</span></span><span style="display:flex;"><span>$ SECRET<span style="color:#f92672">=</span><span style="color:#e6db74">`</span>oc get secrets dc-metro-map-github-webhook-secret -o json | ./jq <span style="color:#e6db74">&#34;.data.WebHookSecretKey&#34;</span> | base64 -di<span style="color:#e6db74">`</span>
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Last, we can get the URL for the webhook, this way:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map | awk <span style="color:#e6db74">&#39;/github$/{print $2}&#39;</span> | sed <span style="color:#e6db74">&#34;s/&lt;secret&gt;/</span><span style="color:#e6db74">${</span>SECRET<span style="color:#e6db74">}</span><span style="color:#e6db74">/&#34;</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map | awk <span style="color:#e6db74">&#39;/github$/{print $2}&#39;</span> | sed <span style="color:#e6db74">&#34;s/&lt;secret&gt;/</span><span style="color:#e6db74">${</span>SECRET<span style="color:#e6db74">}</span><span style="color:#e6db74">/&#34;</span>
+</span></span></code></pre></div><blockquote>
 ... which results in the information that we need:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://api.alexocp43.redhatgov.io:6443/apis/build.openshift.io/v1/namespaces/cicd-1/buildconfigs/dc-metro-map/webhooks/1234abcd5678efgh/github
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://api.alexocp43.redhatgov.io:6443/apis/build.openshift.io/v1/namespaces/cicd-1/buildconfigs/dc-metro-map/webhooks/1234abcd5678efgh/github
+</span></span></code></pre></div><blockquote>
 Copy the "Webhook Generic" URL to the clipboard, so that we can use it in GitHub.
 </blockquote>
 
@@ -566,14 +566,14 @@ <h2 id="rollbacks">Rollbacks</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse47104cf1ebd75bfbed2671f3ffa677a1" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4c684719295e613e63e09b847d425fcb" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse47104cf1ebd75bfbed2671f3ffa677a1" class="panel-collapse collapse ">
+  <div id="collapse4c684719295e613e63e09b847d425fcb" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -583,9 +583,9 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc rollout undo dc/dc-metro-map
-$ oc get pods -w
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc rollout undo dc/dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -742,7 +742,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1002,7 +1002,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1114,7 +1114,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1124,7 +1124,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1207,7 +1207,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab6-replicationrecovery/index.html b/workshops/openshift_4_101/lab6-replicationrecovery/index.html
index 04e6bd4a2..0d28e451b 100644
--- a/workshops/openshift_4_101/lab6-replicationrecovery/index.html
+++ b/workshops/openshift_4_101/lab6-replicationrecovery/index.html
@@ -328,14 +328,14 @@ <h2 id="replication">Replication</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsebc06bd33feb3ef4624b901db9f232001" class="collapsed">
+      <a data-toggle="collapse" href="#collapse373358386344c873c9a9997b43a80ded" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsebc06bd33feb3ef4624b901db9f232001" class="panel-collapse collapse ">
+  <div id="collapse373358386344c873c9a9997b43a80ded" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -345,12 +345,12 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and try the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc scale --replicas<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span> dc/dc-metro-map
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc scale --replicas<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span> dc/dc-metro-map
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Check out the new pods:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>Notice that you now have 4 unique pods available to inspect.  If you want go ahead and inspect them, using &lsquo;oc describe pod/<b>POD NAME</b>&rsquo;. You can see that each has its own IP address and logs.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>Notice that you now have 4 unique pods available to inspect.  If you want go ahead and inspect them, using &lsquo;oc describe pod/<b>POD NAME</b>&rsquo;. You can see that each has its own IP address and logs.</p>
 
     </div>
   </div>
@@ -497,7 +497,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -757,7 +757,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -869,7 +869,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -879,7 +879,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -962,7 +962,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab6.1-replicationrecovery/index.html b/workshops/openshift_4_101/lab6.1-replicationrecovery/index.html
index ef53a11da..d85e8f6d7 100644
--- a/workshops/openshift_4_101/lab6.1-replicationrecovery/index.html
+++ b/workshops/openshift_4_101/lab6.1-replicationrecovery/index.html
@@ -326,14 +326,14 @@ <h2 id="recovery">Recovery</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsec7f897fcbbcbd02c9b82c610839af8b4" class="collapsed">
+      <a data-toggle="collapse" href="#collapse1d01816793a60d477f2642f3ca4916b2" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsec7f897fcbbcbd02c9b82c610839af8b4" class="panel-collapse collapse ">
+  <div id="collapse1d01816793a60d477f2642f3ca4916b2" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -343,15 +343,15 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Choose a random pod and delete it:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc delete pod/PODNAME
-$ oc get pods -w
-</code></pre></div><p>If you&rsquo;re fast enough you&rsquo;ll see the pod you deleted go &ldquo;Terminating&rdquo; and you&rsquo;ll also see a new pod immediately get created and transition from &ldquo;Pending&rdquo; to &ldquo;Running&rdquo;.  If you weren&rsquo;t fast enough you can see that your old pod is gone and a new pod is in the list with an age of only a few seconds.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc delete pod/PODNAME
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>If you&rsquo;re fast enough you&rsquo;ll see the pod you deleted go &ldquo;Terminating&rdquo; and you&rsquo;ll also see a new pod immediately get created and transition from &ldquo;Pending&rdquo; to &ldquo;Running&rdquo;.  If you weren&rsquo;t fast enough you can see that your old pod is gone and a new pod is in the list with an age of only a few seconds.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i>  You can see the more details about your deployment configuration with:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe dc/dc-metro-map
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe dc/dc-metro-map
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -500,7 +500,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -760,7 +760,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -872,7 +872,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -882,7 +882,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -965,7 +965,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab6.2-replicationrecovery/index.html b/workshops/openshift_4_101/lab6.2-replicationrecovery/index.html
index c8aa21986..5bc6ea687 100644
--- a/workshops/openshift_4_101/lab6.2-replicationrecovery/index.html
+++ b/workshops/openshift_4_101/lab6.2-replicationrecovery/index.html
@@ -326,14 +326,14 @@ <h2 id="application-health">Application Health</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseca2b4950ff749472ab9a02bce546ed4b" class="collapsed">
+      <a data-toggle="collapse" href="#collapse08d2c73c7ee40e9b87d7c390cf7b26b2" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapseca2b4950ff749472ab9a02bce546ed4b" class="panel-collapse collapse ">
+  <div id="collapse08d2c73c7ee40e9b87d7c390cf7b26b2" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -343,25 +343,25 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Choose a running pod and shell into it:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc exec PODNAME -it /bin/bash
-</code></pre></div><p>You are now executing a bash shell running in the container of the pod.  Let&rsquo;s kill our webapp and see what happens.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc exec PODNAME -it /bin/bash
+</span></span></code></pre></div><p>You are now executing a bash shell running in the container of the pod.  Let&rsquo;s kill our webapp and see what happens.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> If we had multiple containers in the pod we could use "-c CONTAINER_NAME" to select the right one
 </blockquote>
 <blockquote>
 <i class="fa fa-terminal"></i> Choose a running pod and shell into its container:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ pkill -9 node
-</code></pre></div><p>This will kick you out off the container with an error like &ldquo;Error executing command in container&rdquo;</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ pkill -9 node
+</span></span></code></pre></div><p>This will kick you out off the container with an error like &ldquo;Error executing command in container&rdquo;</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Do it again - shell in and execute the same command to kill node
 </blockquote>
 <blockquote>
 <i class="fa fa-terminal"></i> Watch for the container restart
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods -w
-</code></pre></div><p>If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state.  This ensures the system doesn&rsquo;t waste resources trying to restart containers that are continuously crashing.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state.  This ensures the system doesn&rsquo;t waste resources trying to restart containers that are continuously crashing.</p>
 
     </div>
   </div>
@@ -519,7 +519,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -779,7 +779,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -891,7 +891,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -901,7 +901,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -984,7 +984,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab7-labels/index.html b/workshops/openshift_4_101/lab7-labels/index.html
index b7ce40636..eb7418ff6 100644
--- a/workshops/openshift_4_101/lab7-labels/index.html
+++ b/workshops/openshift_4_101/lab7-labels/index.html
@@ -329,14 +329,14 @@ <h2 id="labels-on-a-pod">Labels on a pod</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse189d169142ea42ed209412295f9c3cdc" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7af261da51d42695c8a807d077e108da" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse189d169142ea42ed209412295f9c3cdc" class="panel-collapse collapse ">
+  <div id="collapse7af261da51d42695c8a807d077e108da" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -346,36 +346,36 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and try the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
-Namespace:    demo-1
-Priority:     <span style="color:#ae81ff">0</span>
-Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
-Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
-Labels:       app<span style="color:#f92672">=</span>dc-metro-map
-              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
-              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
-Annotations:  k8s.v1.cni.cncf.io/networks-status:
-                <span style="color:#f92672">[{</span>
-</code></pre></div><p>You can see the Labels automatically added contain the app, deployment, and deploymentconfig.  Let&rsquo;s add a new label to this pod.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
+</span></span><span style="display:flex;"><span>Namespace:    demo-1
+</span></span><span style="display:flex;"><span>Priority:     <span style="color:#ae81ff">0</span>
+</span></span><span style="display:flex;"><span>Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
+</span></span><span style="display:flex;"><span>Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
+</span></span><span style="display:flex;"><span>Labels:       app<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
+</span></span><span style="display:flex;"><span>Annotations:  k8s.v1.cni.cncf.io/networks-status:
+</span></span><span style="display:flex;"><span>                <span style="color:#f92672">[{</span>
+</span></span></code></pre></div><p>You can see the Labels automatically added contain the app, deployment, and deploymentconfig.  Let&rsquo;s add a new label to this pod.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Add a label
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc label pod/&lt;POD NAME&gt; testdate<span style="color:#f92672">=</span>4.14.2020 testedby<span style="color:#f92672">=</span>mylastname
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc label pod/&lt;POD NAME&gt; testdate<span style="color:#f92672">=</span>4.14.2020 testedby<span style="color:#f92672">=</span>mylastname
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Look at the labels
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
-Namespace:    demo-1
-Priority:     <span style="color:#ae81ff">0</span>
-Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
-Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
-Labels:       app<span style="color:#f92672">=</span>dc-metro-map
-              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
-              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
-              testdate<span style="color:#f92672">=</span>4.14.2020
-              testedby<span style="color:#f92672">=</span>mylastname
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
+</span></span><span style="display:flex;"><span>Namespace:    demo-1
+</span></span><span style="display:flex;"><span>Priority:     <span style="color:#ae81ff">0</span>
+</span></span><span style="display:flex;"><span>Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
+</span></span><span style="display:flex;"><span>Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
+</span></span><span style="display:flex;"><span>Labels:       app<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
+</span></span><span style="display:flex;"><span>              testdate<span style="color:#f92672">=</span>4.14.2020
+</span></span><span style="display:flex;"><span>              testedby<span style="color:#f92672">=</span>mylastname
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -528,7 +528,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -788,7 +788,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -900,7 +900,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -910,7 +910,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -993,7 +993,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab8-cicd/index.html b/workshops/openshift_4_101/lab8-cicd/index.html
index c0b6f6091..6116d16ef 100644
--- a/workshops/openshift_4_101/lab8-cicd/index.html
+++ b/workshops/openshift_4_101/lab8-cicd/index.html
@@ -401,23 +401,23 @@ <h2 id="instantiate-a-jenkins-server-in-your-project">Instantiate a Jenkins serv
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse891f675bf600bf47672563e1f8cd35dd" class="collapsed">
+      <a data-toggle="collapse" href="#collapse3b5a0becc58fdbb21a57ceb6e36ac208" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse891f675bf600bf47672563e1f8cd35dd" class="panel-collapse collapse ">
+  <div id="collapse3b5a0becc58fdbb21a57ceb6e36ac208" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
 <pre>
 https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/terminal
 </pre>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app jenkins-ephemeral --as-deployment-config<span style="color:#f92672">=</span>true
-$ oc logs -f dc/jenkins
-</code></pre></div><p>Wait for logs to return &ldquo;Success&rdquo;.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app jenkins-ephemeral --as-deployment-config<span style="color:#f92672">=</span>true
+</span></span><span style="display:flex;"><span>$ oc logs -f dc/jenkins
+</span></span></code></pre></div><p>Wait for logs to return &ldquo;Success&rdquo;.</p>
 <div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
   <p>NOTE: this may take some time</p>
@@ -489,10 +489,10 @@ <h3 id="web-console-access">Web Console access</h3>
 </div>
 
 <h2 id="create-a-sample-application-configuration">Create a sample application configuration</h2>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project cicd-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project cicd-<span class="userid">YOUR#</span>
 
-$ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/nodejs-sample-pipeline.yaml
-</code></pre></div><h2 id="confirm-you-can-access-jenkins">Confirm you can access Jenkins</h2>
+</span></span><span style="display:flex;"><span>$ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/nodejs-sample-pipeline.yaml
+</span></span></code></pre></div><h2 id="confirm-you-can-access-jenkins">Confirm you can access Jenkins</h2>
 <div class="panel-group">
   
 
@@ -501,14 +501,14 @@ <h2 id="create-a-sample-application-configuration">Create a sample application c
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse9a88ec51185044e5484cec9f2c8a469e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse27b42ff2f97af7c60be8ce4639d23446" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse9a88ec51185044e5484cec9f2c8a469e" class="panel-collapse collapse ">
+  <div id="collapse27b42ff2f97af7c60be8ce4639d23446" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -518,8 +518,8 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Get the route to the Jenkins server:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get route | grep jenkins | awk <span style="color:#e6db74">&#39;{ print $2 }&#39;</span>
-</code></pre></div><p>Copy the above URL, and paste it in your web browser, to access Jenkins.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get route | grep jenkins | awk <span style="color:#e6db74">&#39;{ print $2 }&#39;</span>
+</span></span></code></pre></div><p>Copy the above URL, and paste it in your web browser, to access Jenkins.</p>
 
     </div>
   </div>
@@ -579,14 +579,14 @@ <h2 id="start-the-pipeline">Start the pipeline</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsebcdc858b0e1e54917ea7e82d41e61cf9" class="collapsed">
+      <a data-toggle="collapse" href="#collapse41d40a2436af6961d1c04beede9c0622" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsebcdc858b0e1e54917ea7e82d41e61cf9" class="panel-collapse collapse ">
+  <div id="collapse41d40a2436af6961d1c04beede9c0622" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -594,8 +594,8 @@ <h3 id="terminal-access">Terminal access</h3>
 https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/terminal
 </pre>
 <p><i class="fa fa-terminal"></i> Launch the pipeline:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc start-build nodejs-sample-pipeline
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc start-build nodejs-sample-pipeline
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -754,7 +754,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1014,7 +1014,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1126,7 +1126,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1136,7 +1136,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1219,7 +1219,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/lab9-bluegreen/index.html b/workshops/openshift_4_101/lab9-bluegreen/index.html
index 4b83cff31..5bdd0dc87 100644
--- a/workshops/openshift_4_101/lab9-bluegreen/index.html
+++ b/workshops/openshift_4_101/lab9-bluegreen/index.html
@@ -325,20 +325,20 @@ <h3 id="terminal-access">Terminal access</h3>
 <pre>
 https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/terminal
 </pre>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project cicd-<span class="userid">YOUR#</span>
-$ oc delete all -l app<span style="color:#f92672">=</span>jenkins-ephemeral
-$ oc delete project cicd-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project cicd-<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>jenkins-ephemeral
+</span></span><span style="display:flex;"><span>$ oc delete project cicd-<span class="userid">YOUR#</span>
 
-</code></pre></div><h2 id="lets-deploy-an-application">Lets deploy an application</h2>
+</span></span></code></pre></div><h2 id="lets-deploy-an-application">Lets deploy an application</h2>
 <p>To demonstrate Blue/Green deployments, we&rsquo;ll use a simple application that renders a colored box as an example. Using your GitHub account, please fork the following <a href="https://github.com/RedHatGov/openshift-workshops">https://github.com/RedHatGov/openshift-workshops</a> project.</p>
 <p>You should be comfortable deploying an app at this point, but here are the steps anyway:</p>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project bluegreen-<span class="userid">YOUR#</span>
-$ oc new-app --name<span style="color:#f92672">=</span>green https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map --as-deployment-config<span style="color:#f92672">=</span>true
-$ oc expose service green
-</code></pre></div><p>Note that we exposed this application using a route named &ldquo;green&rdquo;. Wait for the application to become available, then navigate to your application and validate it deployed correctly.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project bluegreen-<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>green https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map --as-deployment-config<span style="color:#f92672">=</span>true
+</span></span><span style="display:flex;"><span>$ oc expose service green
+</span></span></code></pre></div><p>Note that we exposed this application using a route named &ldquo;green&rdquo;. Wait for the application to become available, then navigate to your application and validate it deployed correctly.</p>
 <h2 id="release-a-new-version-of-our-app-and-test-it-in-the-same-environment">Release a new version of our app and test it in the same environment</h2>
 <p>What we&rsquo;ll do next is create a new version of the application called &ldquo;blue&rdquo;. The quickest way to make a change to the code is directly in the GitHub web interface. In GitHub, edit the dc-metro-map/views/dcmetro.jade file in your repo.</p>
 <p><img src="../images/ocp-lab-bluegreen-editgithub.png" width="900"><br/></p>
@@ -347,8 +347,8 @@ <h2 id="release-a-new-version-of-our-app-and-test-it-in-the-same-environment">Re
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app --name<span style="color:#f92672">=</span>blue https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map --as-deployment-config<span style="color:#f92672">=</span>true
-</code></pre></div><p>Wait for the &ldquo;blue&rdquo; application to become avialable before proceeding.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>blue https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map --as-deployment-config<span style="color:#f92672">=</span>true
+</span></span></code></pre></div><p>Wait for the &ldquo;blue&rdquo; application to become avialable before proceeding.</p>
 <h2 id="switch-from-green-to-blue">Switch from Green to Blue</h2>
 <p>Now that we are satisfied with our change we can do the Green/Blue switch.  With OpenShift services and routes, this is super simple.  Follow the steps below to make the switch:</p>
 <div class="panel-group">
@@ -358,14 +358,14 @@ <h2 id="switch-from-green-to-blue">Switch from Green to Blue</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse1817c25d4a5e65c7eb7e60e5ef9e56db" class="collapsed">
+      <a data-toggle="collapse" href="#collapse11e03ab280126112a25858cef024e1b9" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse1817c25d4a5e65c7eb7e60e5ef9e56db" class="panel-collapse collapse ">
+  <div id="collapse11e03ab280126112a25858cef024e1b9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <h3 id="terminal-access">Terminal access</h3>
@@ -375,16 +375,16 @@ <h3 id="terminal-access">Terminal access</h3>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc edit route green
-</code></pre></div><p>This will bring up the Route configuration yaml. Edit the element &ldquo;spec:&rdquo;. On the &ldquo;to:&rdquo; &ldquo;name:&rdquo; line, change its value from &ldquo;green&rdquo; to &ldquo;blue&rdquo;:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">  port:
-    targetPort: 8080-tcp
-  to:
-    kind: Service
-    name: blue
-    weight: <span style="color:#ae81ff">100</span>
-  wildcardPolicy: None
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc edit route green
+</span></span></code></pre></div><p>This will bring up the Route configuration yaml. Edit the element &ldquo;spec:&rdquo;. On the &ldquo;to:&rdquo; &ldquo;name:&rdquo; line, change its value from &ldquo;green&rdquo; to &ldquo;blue&rdquo;:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>  port:
+</span></span><span style="display:flex;"><span>    targetPort: 8080-tcp
+</span></span><span style="display:flex;"><span>  to:
+</span></span><span style="display:flex;"><span>    kind: Service
+</span></span><span style="display:flex;"><span>    name: blue
+</span></span><span style="display:flex;"><span>    weight: <span style="color:#ae81ff">100</span>
+</span></span><span style="display:flex;"><span>  wildcardPolicy: None
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -533,7 +533,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -793,7 +793,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -905,7 +905,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -915,7 +915,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -998,7 +998,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101/prerequisites/index.html b/workshops/openshift_4_101/prerequisites/index.html
index 582970e6e..3142ae6f2 100644
--- a/workshops/openshift_4_101/prerequisites/index.html
+++ b/workshops/openshift_4_101/prerequisites/index.html
@@ -422,7 +422,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -682,7 +682,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -794,7 +794,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -804,7 +804,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -883,7 +883,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/fin/index.html b/workshops/openshift_4_101_dynatrace/fin/index.html
index 1142b941c..badff7878 100644
--- a/workshops/openshift_4_101_dynatrace/fin/index.html
+++ b/workshops/openshift_4_101_dynatrace/fin/index.html
@@ -418,7 +418,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -678,7 +678,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -790,7 +790,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -800,7 +800,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -879,7 +879,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/index.html b/workshops/openshift_4_101_dynatrace/index.html
index c6fbe5a90..a255fec54 100644
--- a/workshops/openshift_4_101_dynatrace/index.html
+++ b/workshops/openshift_4_101_dynatrace/index.html
@@ -502,7 +502,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -762,7 +762,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -874,7 +874,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -884,7 +884,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -934,7 +934,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/index.xml b/workshops/openshift_4_101_dynatrace/index.xml
index 74e8a309c..8b3729aaf 100644
--- a/workshops/openshift_4_101_dynatrace/index.xml
+++ b/workshops/openshift_4_101_dynatrace/index.xml
@@ -4,11 +4,8 @@
     <title>OpenShift 4 101 w/Dynatrace on Red Hat | Public Sector</title>
     <link>/workshops/openshift_4_101_dynatrace/</link>
     <description>Recent content in OpenShift 4 101 w/Dynatrace on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/openshift_4_101_dynatrace/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/openshift_4_101_dynatrace/index.xml" rel="self" type="application/rss+xml" />
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/openshift_4_101_dynatrace/lab1-welcome/index.html b/workshops/openshift_4_101_dynatrace/lab1-welcome/index.html
index 65a9062fc..73ae2c769 100644
--- a/workshops/openshift_4_101_dynatrace/lab1-welcome/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab1-welcome/index.html
@@ -342,8 +342,8 @@ <h2 id="lets-login-to-the-web-console">Let&rsquo;s Login to the Web Console</h2>
 <blockquote>
 <p>Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>
-</code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>
+</span></span></code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
 <em>Login Webpage</em></p>
 <p>Once you are logged in you should see the overview page for your cluster:</p>
 <p><img src="../images/ocp-admin-default.png" width="600"><br/>
@@ -401,29 +401,29 @@ <h2 id="using-the-command-line-cli">Using the command line (CLI)</h2>
 <blockquote>
  Use your existing Butterfly terminal login following command:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc login
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc login
+</span></span></code></pre></div><blockquote>
  Using the same username/password combination as before, finish authenticating to the CLI
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Authentication required <span style="color:#66d9ef">for</span> https://api.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443 <span style="color:#f92672">(</span>openshift<span style="color:#f92672">)</span>
- Username: kubeadmin
- Password:
-Login successful.
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Authentication required <span style="color:#66d9ef">for</span> https://api.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443 <span style="color:#f92672">(</span>openshift<span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span> Username: kubeadmin
+</span></span><span style="display:flex;"><span> Password:
+</span></span><span style="display:flex;"><span>Login successful.
+</span></span></code></pre></div><blockquote>
  Check to see what projects you have access to:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get projects
-</code></pre></div><h3 id="you-will-see-58-projects-including-the-terminal-0-project">You will see ~58 projects including the &ldquo;terminal-0&rdquo; project.</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get projects
+</span></span></code></pre></div><h3 id="you-will-see-58-projects-including-the-terminal-0-project">You will see ~58 projects including the &ldquo;terminal-0&rdquo; project.</h3>
 <h2 id="use-the-cli-to-create-a-new-project">Use the CLI to create a new project</h2>
 <blockquote>
  Use the CLI to create and use a new project by typing the following command to create and use the project "demo-0"
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project demo-0
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project demo-0
+</span></span></code></pre></div><blockquote>
  Type the following command to show services, deployment configs, build configurations, and active deployments (this will come in handy later):
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.</p>
 <style>
 
@@ -524,7 +524,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -784,7 +784,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -896,7 +896,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -906,7 +906,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -989,7 +989,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab10-labels/index.html b/workshops/openshift_4_101_dynatrace/lab10-labels/index.html
index 4fc65890d..5030d6495 100644
--- a/workshops/openshift_4_101_dynatrace/lab10-labels/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab10-labels/index.html
@@ -329,49 +329,49 @@ <h2 id="labels-on-a-pod">Labels on a pod</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsec56ab609e8fbff8859d94a5500e9fd12" class="collapsed">
+      <a data-toggle="collapse" href="#collapse89a0ea0f0ad8826134f11b9ffbfb9fc9" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsec56ab609e8fbff8859d94a5500e9fd12" class="panel-collapse collapse ">
+  <div id="collapse89a0ea0f0ad8826134f11b9ffbfb9fc9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and try the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
-Namespace:    demo-1
-Priority:     <span style="color:#ae81ff">0</span>
-Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
-Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
-Labels:       app<span style="color:#f92672">=</span>dc-metro-map
-              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
-              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
-Annotations:  k8s.v1.cni.cncf.io/networks-status:
-                <span style="color:#f92672">[{</span>
-</code></pre></div><p>You can see the Labels automatically added contain the app, deployment, and deploymentconfig.  Let&rsquo;s add a new label to this pod.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
+</span></span><span style="display:flex;"><span>Namespace:    demo-1
+</span></span><span style="display:flex;"><span>Priority:     <span style="color:#ae81ff">0</span>
+</span></span><span style="display:flex;"><span>Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
+</span></span><span style="display:flex;"><span>Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
+</span></span><span style="display:flex;"><span>Labels:       app<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
+</span></span><span style="display:flex;"><span>Annotations:  k8s.v1.cni.cncf.io/networks-status:
+</span></span><span style="display:flex;"><span>                <span style="color:#f92672">[{</span>
+</span></span></code></pre></div><p>You can see the Labels automatically added contain the app, deployment, and deploymentconfig.  Let&rsquo;s add a new label to this pod.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Add a label
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc label pod/&lt;POD NAME&gt; testdate<span style="color:#f92672">=</span>4.14.2020 testedby<span style="color:#f92672">=</span>mylastname
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc label pod/&lt;POD NAME&gt; testdate<span style="color:#f92672">=</span>4.14.2020 testedby<span style="color:#f92672">=</span>mylastname
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Look at the labels
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
-Namespace:    demo-1
-Priority:     <span style="color:#ae81ff">0</span>
-Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
-Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
-Labels:       app<span style="color:#f92672">=</span>dc-metro-map
-              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
-              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
-              testdate<span style="color:#f92672">=</span>4.14.2020
-              testedby<span style="color:#f92672">=</span>mylastname
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe pod/&lt;POD NAME&gt; | grep Labels: --context<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span>
+</span></span><span style="display:flex;"><span>Namespace:    demo-1
+</span></span><span style="display:flex;"><span>Priority:     <span style="color:#ae81ff">0</span>
+</span></span><span style="display:flex;"><span>Node:         ip-10-0-132-38.us-east-2.compute.internal/10.0.132.38
+</span></span><span style="display:flex;"><span>Start Time:   Tue, <span style="color:#ae81ff">14</span> Apr <span style="color:#ae81ff">2020</span> 17:41:58 +0000
+</span></span><span style="display:flex;"><span>Labels:       app<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              deploymentconfig<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>              pod-template-hash<span style="color:#f92672">=</span>7bc46bf89d
+</span></span><span style="display:flex;"><span>              testdate<span style="color:#f92672">=</span>4.14.2020
+</span></span><span style="display:flex;"><span>              testedby<span style="color:#f92672">=</span>mylastname
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -520,7 +520,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -780,7 +780,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -892,7 +892,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -902,7 +902,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -985,7 +985,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab11-cicd/index.html b/workshops/openshift_4_101_dynatrace/lab11-cicd/index.html
index 8613eb076..b916d5473 100644
--- a/workshops/openshift_4_101_dynatrace/lab11-cicd/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab11-cicd/index.html
@@ -394,38 +394,38 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseec010b36bb1a35639c66bd23f0a1847c" class="collapsed">
+      <a data-toggle="collapse" href="#collapse9dd6e7a1653d4687bd2cd90d216fb8e9" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapseec010b36bb1a35639c66bd23f0a1847c" class="panel-collapse collapse ">
+  <div id="collapse9dd6e7a1653d4687bd2cd90d216fb8e9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get bc/dc-metro-map -o yaml | grep generic-webhook
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get bc/dc-metro-map -o yaml | grep generic-webhook
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> ...which returns the name of the secret that we need to find:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">name: dc-metro-map-generic-webhook-secret
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>name: dc-metro-map-generic-webhook-secret
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Now that you have the name of the secret, you can get its value:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ SECRET<span style="color:#f92672">=</span><span style="color:#e6db74">`</span>oc get secrets dc-metro-map-generic-webhook-secret -o yaml | grep -i key | sed <span style="color:#e6db74">&#39;s/^.*: //&#39;</span> | base64 -d ; echo<span style="color:#e6db74">`</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ SECRET<span style="color:#f92672">=</span><span style="color:#e6db74">`</span>oc get secrets dc-metro-map-generic-webhook-secret -o yaml | grep -i key | sed <span style="color:#e6db74">&#39;s/^.*: //&#39;</span> | base64 -d ; echo<span style="color:#e6db74">`</span>
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Last, we can get the URL for the webhook, this way:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map | grep <span style="color:#e6db74">&#34;Webhook Generic&#34;</span> -A <span style="color:#ae81ff">1</span> | sed <span style="color:#e6db74">&#34;s/&lt;secret&gt;/</span><span style="color:#e6db74">${</span>SECRET<span style="color:#e6db74">}</span><span style="color:#e6db74">/&#34;</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map | grep <span style="color:#e6db74">&#34;Webhook Generic&#34;</span> -A <span style="color:#ae81ff">1</span> | sed <span style="color:#e6db74">&#34;s/&lt;secret&gt;/</span><span style="color:#e6db74">${</span>SECRET<span style="color:#e6db74">}</span><span style="color:#e6db74">/&#34;</span>
+</span></span></code></pre></div><blockquote>
 ... which results in the information that we need:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Webhook Generic:
-        URL:            https://api.alexocp43.redhatgov.io:6443/apis/build.openshift.io/v1/namespaces/cicd-1/buildconfigs/dc-metro-map/webhooks/1234abcd5678efgh/generic
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Webhook Generic:
+</span></span><span style="display:flex;"><span>        URL:            https://api.alexocp43.redhatgov.io:6443/apis/build.openshift.io/v1/namespaces/cicd-1/buildconfigs/dc-metro-map/webhooks/1234abcd5678efgh/generic
+</span></span></code></pre></div><blockquote>
 Copy the "Webhook Generic" URL to the clipboard, so that we can use it in GitHub.
 </blockquote>
 
@@ -545,22 +545,22 @@ <h2 id="rollbacks">Rollbacks</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseaa93cf48d4f1eea9e53cef2911d2b641" class="collapsed">
+      <a data-toggle="collapse" href="#collapse04ecaac60ed3b96410a23867d40d29d9" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapseaa93cf48d4f1eea9e53cef2911d2b641" class="panel-collapse collapse ">
+  <div id="collapse04ecaac60ed3b96410a23867d40d29d9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc rollout undo dc/dc-metro-map
-$ oc get pods -w
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc rollout undo dc/dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -713,7 +713,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -973,7 +973,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1085,7 +1085,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1095,7 +1095,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1178,7 +1178,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab12-bluegreen/index.html b/workshops/openshift_4_101_dynatrace/lab12-bluegreen/index.html
index f90be708b..e8ff94bf7 100644
--- a/workshops/openshift_4_101_dynatrace/lab12-bluegreen/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab12-bluegreen/index.html
@@ -321,19 +321,19 @@ <h1 id="bluegreen-deployments">Blue/Green deployments</h1>
 <p>When implementing continuous delivery for your software one very useful technique is called Blue/Green deployments.  It addresses the desire to minimize downtime during the release of a new version of an application to production.  Essentially, it involves running two production versions of your app side-by-side and then switching the routing from the last stable version to the new version once it is verified.  Using OpenShift, this can be very seamless because using containers we can easily and rapidly deploy a duplicate infrastructure to support alternate versions and modify routes as a service.  In this lab, we will walk through a simple Blue/Green workflow with an simple web application on OpenShift.</p>
 <h2 id="before-starting">Before starting</h2>
 <p>Before we get started with the Blue/Green deployment lab, lets clean up some of the projects from the previous lab.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc delete all -l app<span style="color:#f92672">=</span>jenkins-ephemeral
-$ oc delete project cicd-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>jenkins-ephemeral
+</span></span><span style="display:flex;"><span>$ oc delete project cicd-<span class="userid">YOUR#</span>
 
-</code></pre></div><h2 id="lets-deploy-an-application">Lets deploy an application</h2>
+</span></span></code></pre></div><h2 id="lets-deploy-an-application">Lets deploy an application</h2>
 <p>To demonstrate Blue/Green deployments, we&rsquo;ll use a simple application that renders a colored box as an example. Using your GitHub account, please fork the following <a href="https://github.com/RedHatGov/openshift-workshops">https://github.com/RedHatGov/openshift-workshops</a> project.</p>
 <p>You should be comfortable deploying an app at this point, but here are the steps anyway:</p>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project bluegreen-<span class="userid">YOUR#</span>
-$ oc new-app --name<span style="color:#f92672">=</span>green https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map
-$ oc expose service green
-</code></pre></div><p>Note that we exposed this application using a route named &ldquo;green&rdquo;. Wait for the application to become available, then navigate to your application and validate it deployed correctly.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project bluegreen-<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>green https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc expose service green
+</span></span></code></pre></div><p>Note that we exposed this application using a route named &ldquo;green&rdquo;. Wait for the application to become available, then navigate to your application and validate it deployed correctly.</p>
 <h2 id="release-a-new-version-of-our-app-and-test-it-in-the-same-environment">Release a new version of our app and test it in the same environment</h2>
 <p>What we&rsquo;ll do next is create a new version of the application called &ldquo;blue&rdquo;. The quickest way to make a change to the code is directly in the GitHub web interface. In GitHub, edit the dc-metro-map/views/dcmetro.jade file in your repo.</p>
 <p><img src="../images/ocp-lab-bluegreen-editgithub.png" width="900"><br/></p>
@@ -342,8 +342,8 @@ <h2 id="release-a-new-version-of-our-app-and-test-it-in-the-same-environment">Re
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app --name<span style="color:#f92672">=</span>blue https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map
-</code></pre></div><p>Wait for the &ldquo;blue&rdquo; application to become avialable before proceeding.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>blue https://github.com/your-github-uid-goes-here/openshift-workshops --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span></code></pre></div><p>Wait for the &ldquo;blue&rdquo; application to become avialable before proceeding.</p>
 <h2 id="switch-from-green-to-blue">Switch from Green to Blue</h2>
 <p>Now that we are satisfied with our change we can do the Green/Blue switch.  With OpenShift services and routes, this is super simple.  Follow the steps below to make the switch:</p>
 <div class="panel-group">
@@ -353,32 +353,32 @@ <h2 id="switch-from-green-to-blue">Switch from Green to Blue</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse94ccbdbc39cb4f9cdbb0a93d01ad76af" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef96163b4b0737e99578e5f014895edc8" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse94ccbdbc39cb4f9cdbb0a93d01ad76af" class="panel-collapse collapse ">
+  <div id="collapsef96163b4b0737e99578e5f014895edc8" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc edit route green
-</code></pre></div><p>This will bring up the Route configuration yaml. Edit the element &ldquo;spec:&rdquo;. On the &ldquo;to:&rdquo; &ldquo;name:&rdquo; line, change its value from &ldquo;green&rdquo; to &ldquo;blue&rdquo;:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">spec:
-  host: green-bluegreen-&lt;span class<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;userid&#34;</span>&gt;YOUR#&lt;/span&gt;
-.apps.alexocp43.redhatgov.io
-  port:
-    targetPort: 8080-tcp
-  to:
-    kind: Service
-    name: blue
-    weight: <span style="color:#ae81ff">100</span>
-  wildcardPolicy: None
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc edit route green
+</span></span></code></pre></div><p>This will bring up the Route configuration yaml. Edit the element &ldquo;spec:&rdquo;. On the &ldquo;to:&rdquo; &ldquo;name:&rdquo; line, change its value from &ldquo;green&rdquo; to &ldquo;blue&rdquo;:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>spec:
+</span></span><span style="display:flex;"><span>  host: green-bluegreen-&lt;span class<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;userid&#34;</span>&gt;YOUR#&lt;/span&gt;
+</span></span><span style="display:flex;"><span>.apps.alexocp43.redhatgov.io
+</span></span><span style="display:flex;"><span>  port:
+</span></span><span style="display:flex;"><span>    targetPort: 8080-tcp
+</span></span><span style="display:flex;"><span>  to:
+</span></span><span style="display:flex;"><span>    kind: Service
+</span></span><span style="display:flex;"><span>    name: blue
+</span></span><span style="display:flex;"><span>    weight: <span style="color:#ae81ff">100</span>
+</span></span><span style="display:flex;"><span>  wildcardPolicy: None
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -523,7 +523,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -783,7 +783,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -895,7 +895,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -905,7 +905,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -988,7 +988,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab2-byocontainer/index.html b/workshops/openshift_4_101_dynatrace/lab2-byocontainer/index.html
index 2c9deca8c..e9b4cfc83 100644
--- a/workshops/openshift_4_101_dynatrace/lab2-byocontainer/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab2-byocontainer/index.html
@@ -327,62 +327,62 @@ <h2 id="lets-point-openshift-to-an-existing-built-container-image">Let&rsquo;s p
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse64a8ba3fb6546c32d813ca28b49f8129" class="collapsed">
+      <a data-toggle="collapse" href="#collapse8c2d27d504b039b11a8bb51e889ead25" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse64a8ba3fb6546c32d813ca28b49f8129" class="panel-collapse collapse ">
+  <div id="collapse8c2d27d504b039b11a8bb51e889ead25" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Verify you're still in the project we created at the end of the last lab by going to the terminal and typing the following:  
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc projects
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc projects
+</span></span></code></pre></div><blockquote>
 You should see something *similar* in the last line of the output:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ Using project <span style="color:#e6db74">&#34;demo-0&#34;</span> on server <span style="color:#e6db74">&#34;https://172.30.0.1:443&#34;</span>.
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ Using project <span style="color:#e6db74">&#34;demo-0&#34;</span> on server <span style="color:#e6db74">&#34;https://172.30.0.1:443&#34;</span>.
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> If you don't, use the following command to use the correct project:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project demo-0
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project demo-0
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> In the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app sonatype/nexus:oss
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app sonatype/nexus:oss
+</span></span></code></pre></div><blockquote>
 The output should show something *similar* to below:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">--&gt; Found container image ae52f07 <span style="color:#f92672">(</span><span style="color:#ae81ff">4</span> months old<span style="color:#f92672">)</span> from Docker Hub <span style="color:#66d9ef">for</span> <span style="color:#e6db74">&#34;sonatype/nexus:oss&#34;</span>
-
-    Red Hat Universal Base Image <span style="color:#ae81ff">7</span>
-    ------------------------------
-    The Universal Base Image is designed and engineered to be the base layer <span style="color:#66d9ef">for</span> all of your 
-containerized applications, middleware and utilities. This base image is freely redistributable, 
-but Red Hat only supports Red Hat technologies through subscriptions <span style="color:#66d9ef">for</span> Red Hat products. 
-This image is maintained by Red Hat and updated regularly.
-
-    Tags: base rhel7
-
-    * An image stream tag will be created as <span style="color:#e6db74">&#34;nexus:oss&#34;</span> that will track this image
-
---&gt; Creating resources ...
-    imagestream.image.openshift.io <span style="color:#e6db74">&#34;nexus&#34;</span> created
-    deployment.apps <span style="color:#e6db74">&#34;nexus&#34;</span> created
-    service <span style="color:#e6db74">&#34;nexus&#34;</span> created
---&gt; Success
-    Application is not exposed. You can expose services to the outside world by executing one or 
-more of the commands below:
-     <span style="color:#e6db74">&#39;oc expose svc/nexus&#39;</span>
-    Run <span style="color:#e6db74">&#39;oc status&#39;</span> to view your app.  
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>--&gt; Found container image ae52f07 <span style="color:#f92672">(</span><span style="color:#ae81ff">4</span> months old<span style="color:#f92672">)</span> from Docker Hub <span style="color:#66d9ef">for</span> <span style="color:#e6db74">&#34;sonatype/nexus:oss&#34;</span>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    Red Hat Universal Base Image <span style="color:#ae81ff">7</span>
+</span></span><span style="display:flex;"><span>    ------------------------------
+</span></span><span style="display:flex;"><span>    The Universal Base Image is designed and engineered to be the base layer <span style="color:#66d9ef">for</span> all of your 
+</span></span><span style="display:flex;"><span>containerized applications, middleware and utilities. This base image is freely redistributable, 
+</span></span><span style="display:flex;"><span>but Red Hat only supports Red Hat technologies through subscriptions <span style="color:#66d9ef">for</span> Red Hat products. 
+</span></span><span style="display:flex;"><span>This image is maintained by Red Hat and updated regularly.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    Tags: base rhel7
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    * An image stream tag will be created as <span style="color:#e6db74">&#34;nexus:oss&#34;</span> that will track this image
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>--&gt; Creating resources ...
+</span></span><span style="display:flex;"><span>    imagestream.image.openshift.io <span style="color:#e6db74">&#34;nexus&#34;</span> created
+</span></span><span style="display:flex;"><span>    deployment.apps <span style="color:#e6db74">&#34;nexus&#34;</span> created
+</span></span><span style="display:flex;"><span>    service <span style="color:#e6db74">&#34;nexus&#34;</span> created
+</span></span><span style="display:flex;"><span>--&gt; Success
+</span></span><span style="display:flex;"><span>    Application is not exposed. You can expose services to the outside world by executing one or 
+</span></span><span style="display:flex;"><span>more of the commands below:
+</span></span><span style="display:flex;"><span>     <span style="color:#e6db74">&#39;oc expose svc/nexus&#39;</span>
+</span></span><span style="display:flex;"><span>    Run <span style="color:#e6db74">&#39;oc status&#39;</span> to view your app.  
+</span></span></code></pre></div><blockquote>
 Now, let's create a route, so that you can get to the app:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc expose svc/nexus
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc expose svc/nexus
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -449,23 +449,23 @@ <h2 id="we-can-browse-our-project-details-with-the-command-line">We can browse o
 <blockquote>
 <p><i class="fa fa-terminal"></i> Try typing the following to see what is available to &lsquo;get&rsquo;:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project demo-<span class="userid">YOUR#</span>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project demo-<span class="userid">YOUR#</span>
 
-$ oc get all
-</code></pre></div><blockquote>
+</span></span><span style="display:flex;"><span>$ oc get all
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Now let&rsquo;s look at what our image stream has in it:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get is
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe is/nexus
-</code></pre></div><div class="alert alert-info">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get is
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe is/nexus
+</span></span></code></pre></div><div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>An image stream can be used to automatically perform an action, such as updating a deployment, when a new image, in our case a new version of the nexus image, is created.</p>
 </div>
 <blockquote>
 <p><i class="fa fa-terminal"></i> The app is running in a pod, let&rsquo;s look at that:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe pods
-</code></pre></div><h2 id="we-can-see-those-details-using-the-web-console-too">We can see those details using the web console too</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe pods
+</span></span></code></pre></div><h2 id="we-can-see-those-details-using-the-web-console-too">We can see those details using the web console too</h2>
 <p>Let&rsquo;s look at the image stream.</p>
 <blockquote>
 Click on "Developer", in the top left corner, and change it to "Administrator"
@@ -488,15 +488,15 @@ <h2 id="test-out-the-nexus-webapp">Test out the nexus webapp</h2>
 <p><img src="../images/ocp-nexus-app.png" width="300"><br/></p>
 <p>Good work - this error is expected; since the nexus console is on /nexus</p>
 <p>Go to this URL:</p>
-<h2 id="hahahugoshortcode-s3-hbhb">http://nexus-demo-<span class="userid">0</span>.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/nexus/</h2>
+<h2 id="hahahugoshortcode182s3hbhb">http://nexus-demo-<span class="userid">0</span>.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/nexus/</h2>
 <p>&hellip; to get the Nexus console.  Of course, we have not provided persistent storage; so, any and all work will be lost.</p>
 <p><img src="../images/ocp-nexus-app2.png" width="600"><br/></p>
 <h2 id="lets-clean-this-up">Let&rsquo;s clean this up</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Let&rsquo;s clean up all this to get ready for the next lab:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc delete all --selector app<span style="color:#f92672">=</span>nexus
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc delete all --selector app<span style="color:#f92672">=</span>nexus
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>In this lab you&rsquo;ve deployed an example container image, pulled from Quay.io, into a pod running in OpenShift.  You exposed a route for clients to access that service via thier web browsers.  And you learned how to get and describe resources using the command line and the web console.  Hopefully, this basic lab also helped to get you familiar with using the CLI and navigating within the web console.</p>
 <style>
 
@@ -597,7 +597,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -857,7 +857,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -969,7 +969,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -979,7 +979,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1062,7 +1062,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab3-installagent/index.html b/workshops/openshift_4_101_dynatrace/lab3-installagent/index.html
index 535ff608f..83759d5cf 100644
--- a/workshops/openshift_4_101_dynatrace/lab3-installagent/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab3-installagent/index.html
@@ -348,56 +348,56 @@ <h1 id="deploy-the-dynatrace-oneagent-operator-on-openshift-44">Deploy the Dynat
 <blockquote>
 The first step is to define the new project where we'll deploy the Dynatrace OneAgent pods
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc new-project dynatrace
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc new-project dynatrace
+</span></span></code></pre></div><blockquote>
 Using the information you gathered in the pre-requisites referenced above, define the secret that will be used to provision the operator.  You may update this secret at any time to rotate the tokens.
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc -n dynatrace create secret generic oneagent <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>--from-literal<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;apiToken=&lt;API token&gt;&#34;</span> --from-literal<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;paasToken=&lt;PaaS token&gt;&#34;</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc -n dynatrace create secret generic oneagent <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>--from-literal<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;apiToken=&lt;API token&gt;&#34;</span> --from-literal<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;paasToken=&lt;PaaS token&gt;&#34;</span>
+</span></span></code></pre></div><blockquote>
 Optional: Check the latest release at 
 https://github.com/Dynatrace/dynatrace-oneagent-operator/branches/active
 </blockquote>
 <blockquote>
 Apply the latest configuration from Dynatrace:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc apply -f <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/latest/download/openshift.yaml
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc apply -f <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/latest/download/openshift.yaml
+</span></span></code></pre></div><blockquote>
 You should see an output *similar* to the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">customresourcedefinition.apiextensions.k8s.io/oneagentapms.dynatrace.com created
-customresourcedefinition.apiextensions.k8s.io/oneagents.dynatrace.com created
-serviceaccount/dynatrace-oneagent created
-serviceaccount/dynatrace-oneagent-operator created
-serviceaccount/dynatrace-oneagent-webhook created
-role.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
-role.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
-clusterrole.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
-clusterrole.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
-rolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
-rolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
-clusterrolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
-clusterrolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
-service/dynatrace-oneagent-webhook created
-deployment.apps/dynatrace-oneagent-operator created
-deployment.apps/dynatrace-oneagent-webhook created
-securitycontextconstraints.security.openshift.io/dynatrace-oneagent-privileged created
-mutatingwebhookconfiguration.admissionregistration.k8s.io/dynatrace-oneagent-webhook created
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>customresourcedefinition.apiextensions.k8s.io/oneagentapms.dynatrace.com created
+</span></span><span style="display:flex;"><span>customresourcedefinition.apiextensions.k8s.io/oneagents.dynatrace.com created
+</span></span><span style="display:flex;"><span>serviceaccount/dynatrace-oneagent created
+</span></span><span style="display:flex;"><span>serviceaccount/dynatrace-oneagent-operator created
+</span></span><span style="display:flex;"><span>serviceaccount/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>role.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
+</span></span><span style="display:flex;"><span>role.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>clusterrole.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
+</span></span><span style="display:flex;"><span>clusterrole.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>rolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
+</span></span><span style="display:flex;"><span>rolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>clusterrolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-operator created
+</span></span><span style="display:flex;"><span>clusterrolebinding.rbac.authorization.k8s.io/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>service/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>deployment.apps/dynatrace-oneagent-operator created
+</span></span><span style="display:flex;"><span>deployment.apps/dynatrace-oneagent-webhook created
+</span></span><span style="display:flex;"><span>securitycontextconstraints.security.openshift.io/dynatrace-oneagent-privileged created
+</span></span><span style="display:flex;"><span>mutatingwebhookconfiguration.admissionregistration.k8s.io/dynatrace-oneagent-webhook created
+</span></span></code></pre></div><blockquote>
 Create the default custom resource for the Dynatrace OneAgent:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">curl -o cr.yaml https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/master/deploy/cr.yaml
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>curl -o cr.yaml https://raw.githubusercontent.com/Dynatrace/dynatrace-oneagent-operator/master/deploy/cr.yaml
+</span></span></code></pre></div><blockquote>
 Update the custom resource (cr.yaml) with apiUrl and the name of secret we create above ("oneagent") as shown below
 <p>e.g.
 apiUrl: <a href="https://eye15053.live.dynatrace.com/api">https://eye15053.live.dynatrace.com/api</a>
 tokens: &ldquo;oneagent&rdquo;</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">vi cr.yaml
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>vi cr.yaml
+</span></span></code></pre></div><blockquote>
 </blockquote>
-<pre><code>apiVersion: dynatrace.com/v1alpha1
+<pre tabindex="0"><code>apiVersion: dynatrace.com/v1alpha1
 kind: OneAgent
 metadata:
   # a descriptive name for this object.
@@ -412,63 +412,63 @@ <h1 id="deploy-the-dynatrace-oneagent-operator-on-openshift-44">Deploy the Dynat
   skipCertCheck: false
   # name of secret holding `apiToken` and `paasToken`
   # if unset, name of custom resource is used
-  tokens: &quot;oneagent&quot;
+  tokens: &#34;oneagent&#34;
 </code></pre><blockquote>
 If you want Dynatrace to monitor OpenShift Service Mesh deployments, set
 </blockquote>
-<pre><code>enableIstio: true
+<pre tabindex="0"><code>enableIstio: true
 </code></pre><blockquote>
 Apply the modified custom resource (cr.yaml)
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc apply -f cr.yaml
-oneagent.dynatrace.com/oneagent configured
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc apply -f cr.yaml
+</span></span><span style="display:flex;"><span>oneagent.dynatrace.com/oneagent configured
+</span></span></code></pre></div><blockquote>
 Verify that the operator, webhook, and OneAgent pods have been created and are deploying
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc get pods
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc get pods
+</span></span></code></pre></div><blockquote>
 The outpout should look *similar* to the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">NAME                                           READY   STATUS    RESTARTS   AGE
-dynatrace-oneagent-operator-788fd7f5b4-6lt67   1/1     Running   <span style="color:#ae81ff">0</span>          4m21s
-dynatrace-oneagent-webhook-84747567df-lmltw    2/2     Running   <span style="color:#ae81ff">0</span>          4m21s
-oneagent-4j9xf                                 0/1     Running   <span style="color:#ae81ff">0</span>          102s
-oneagent-55p2k                                 0/1     Running   <span style="color:#ae81ff">0</span>          106s
-oneagent-b7qlb                                 0/1     Running   <span style="color:#ae81ff">0</span>          108s
-oneagent-jhk2f                                 0/1     Running   <span style="color:#ae81ff">0</span>          107s
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>NAME                                           READY   STATUS    RESTARTS   AGE
+</span></span><span style="display:flex;"><span>dynatrace-oneagent-operator-788fd7f5b4-6lt67   1/1     Running   <span style="color:#ae81ff">0</span>          4m21s
+</span></span><span style="display:flex;"><span>dynatrace-oneagent-webhook-84747567df-lmltw    2/2     Running   <span style="color:#ae81ff">0</span>          4m21s
+</span></span><span style="display:flex;"><span>oneagent-4j9xf                                 0/1     Running   <span style="color:#ae81ff">0</span>          102s
+</span></span><span style="display:flex;"><span>oneagent-55p2k                                 0/1     Running   <span style="color:#ae81ff">0</span>          106s
+</span></span><span style="display:flex;"><span>oneagent-b7qlb                                 0/1     Running   <span style="color:#ae81ff">0</span>          108s
+</span></span><span style="display:flex;"><span>oneagent-jhk2f                                 0/1     Running   <span style="color:#ae81ff">0</span>          107s
+</span></span></code></pre></div><blockquote>
 Check the deployment status of one of the pods:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc logs oneagent-jhk2f
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc logs oneagent-jhk2f
+</span></span></code></pre></div><blockquote>
 The output should look *similar* to the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">23:19:49 Started agent deployment as a container, PID 1352627.
-23:19:49 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://eye15053.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?Api-Token<span style="color:#f92672">=</span>***&amp;arch<span style="color:#f92672">=</span>x86&amp;flavor<span style="color:#f92672">=</span>default
-23:20:18 Download complete
-23:20:18 Downloaded version: 1.195.161.20200720-160625
-23:20:18 Verifying agent installer signature
-23:20:21 Verification successful
-23:20:21 Deploying to: /mnt/host_root
-23:20:21 Starting installer...
-23:20:22 Warning: Parameter APP_LOG_CONTENT_ACCESS is deprecated and will be removed in future release. Please use --set-app-log-content-access instead. For details, see https://www.dynatrace.com/support/help/shortlink/oneagentctl
-23:20:23 Checking root privileges...
-23:20:23 OK
-23:20:23 Installation started, version 1.195.161.20200720-160625, build date: 20.07.2020, PID 1352627.
-23:20:25 Detected platform: LINUX arch: X86
-23:20:25 Detected bitness: <span style="color:#ae81ff">64</span>
-23:20:25 Checking free space in /opt/dynatrace/oneagent
-23:20:27 Extracting...
-23:20:28 Unpacking. This may take a few minutes...
-23:20:52 Unpacking complete.
-23:20:52 Moving new binaries into lib folders...
-23:20:54 User <span style="color:#e6db74">&#39;dtuser&#39;</span> added successfully.
-23:20:57 Non-privileged mode is enabled.
-23:20:57 Applying agent configuration
-23:20:58 Storing SELinux policy sources in /opt/dynatrace/oneagent/agent.
-23:20:58 Installing SELinux Dynatrace module. This may take a <span style="color:#66d9ef">while</span>...
-23:21:35 dynatrace_oneagent module was successfully installed
-</code></pre></div><h2 id="verify-that-the-dynatrace-oneagent-operator-is-deployed-in-both-the-openshift-management-console-and-the-dynatrace-tenant">Verify that the Dynatrace OneAgent Operator is deployed in both the OpenShift Management Console and the Dynatrace tenant</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>23:19:49 Started agent deployment as a container, PID 1352627.
+</span></span><span style="display:flex;"><span>23:19:49 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://eye15053.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?Api-Token<span style="color:#f92672">=</span>***&amp;arch<span style="color:#f92672">=</span>x86&amp;flavor<span style="color:#f92672">=</span>default
+</span></span><span style="display:flex;"><span>23:20:18 Download complete
+</span></span><span style="display:flex;"><span>23:20:18 Downloaded version: 1.195.161.20200720-160625
+</span></span><span style="display:flex;"><span>23:20:18 Verifying agent installer signature
+</span></span><span style="display:flex;"><span>23:20:21 Verification successful
+</span></span><span style="display:flex;"><span>23:20:21 Deploying to: /mnt/host_root
+</span></span><span style="display:flex;"><span>23:20:21 Starting installer...
+</span></span><span style="display:flex;"><span>23:20:22 Warning: Parameter APP_LOG_CONTENT_ACCESS is deprecated and will be removed in future release. Please use --set-app-log-content-access instead. For details, see https://www.dynatrace.com/support/help/shortlink/oneagentctl
+</span></span><span style="display:flex;"><span>23:20:23 Checking root privileges...
+</span></span><span style="display:flex;"><span>23:20:23 OK
+</span></span><span style="display:flex;"><span>23:20:23 Installation started, version 1.195.161.20200720-160625, build date: 20.07.2020, PID 1352627.
+</span></span><span style="display:flex;"><span>23:20:25 Detected platform: LINUX arch: X86
+</span></span><span style="display:flex;"><span>23:20:25 Detected bitness: <span style="color:#ae81ff">64</span>
+</span></span><span style="display:flex;"><span>23:20:25 Checking free space in /opt/dynatrace/oneagent
+</span></span><span style="display:flex;"><span>23:20:27 Extracting...
+</span></span><span style="display:flex;"><span>23:20:28 Unpacking. This may take a few minutes...
+</span></span><span style="display:flex;"><span>23:20:52 Unpacking complete.
+</span></span><span style="display:flex;"><span>23:20:52 Moving new binaries into lib folders...
+</span></span><span style="display:flex;"><span>23:20:54 User <span style="color:#e6db74">&#39;dtuser&#39;</span> added successfully.
+</span></span><span style="display:flex;"><span>23:20:57 Non-privileged mode is enabled.
+</span></span><span style="display:flex;"><span>23:20:57 Applying agent configuration
+</span></span><span style="display:flex;"><span>23:20:58 Storing SELinux policy sources in /opt/dynatrace/oneagent/agent.
+</span></span><span style="display:flex;"><span>23:20:58 Installing SELinux Dynatrace module. This may take a <span style="color:#66d9ef">while</span>...
+</span></span><span style="display:flex;"><span>23:21:35 dynatrace_oneagent module was successfully installed
+</span></span></code></pre></div><h2 id="verify-that-the-dynatrace-oneagent-operator-is-deployed-in-both-the-openshift-management-console-and-the-dynatrace-tenant">Verify that the Dynatrace OneAgent Operator is deployed in both the OpenShift Management Console and the Dynatrace tenant</h2>
 <p>First verify the deployment via the OpenShift Management Conole</p>
 <blockquote>
 In the "Developer" interface, ensure that you are in the project "dynatrace" and choose topology to verify that you have three deployments: dynatrace-oneagent-operator, dynatrace-oneagent-webhook, and oneagent
@@ -578,7 +578,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -838,7 +838,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -950,7 +950,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -960,7 +960,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1043,7 +1043,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/index.html b/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/index.html
index 53a81383c..9afd4e6b6 100644
--- a/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab4-configdynatraceactivegate/index.html
@@ -321,29 +321,29 @@ <h1 id="connect-your-openshift-clusters-to-dynatrace-with-an-activegate-to-take-
 <p>Connecting your OpenShift clusters to Dynatrace to take advantage of the dedicated OpenShift overview page
 requires that you run an ActiveGate in your environment (version 1.163+).</p>
 <p>See <a href="https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/monitoring/monitor-openshift-clusters-with-dynatrace/">https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/monitoring/monitor-openshift-clusters-with-dynatrace/</a></p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc project dynatrace
-oc apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml
-
-serviceaccount/dynatrace-monitoring created
-clusterrole.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created
-clusterrolebinding.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc config view --minify -o jsonpath<span style="color:#f92672">=</span><span style="color:#e6db74">&#39;{.clusters[0].cluster.server}&#39;</span>
-
-https://api.ocp4.local:6443
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc project dynatrace
+</span></span><span style="display:flex;"><span>oc apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>serviceaccount/dynatrace-monitoring created
+</span></span><span style="display:flex;"><span>clusterrole.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created
+</span></span><span style="display:flex;"><span>clusterrolebinding.rbac.authorization.k8s.io/dynatrace-monitoring-cluster created
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc config view --minify -o jsonpath<span style="color:#f92672">=</span><span style="color:#e6db74">&#39;{.clusters[0].cluster.server}&#39;</span>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>https://api.ocp4.local:6443
+</span></span></code></pre></div><blockquote>
 Get the Bearer token for the OpenShift cluster using the following command:
 <p>Copy the secret returned by the following command:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">oc get secret <span style="color:#66d9ef">$(</span>oc get sa dynatrace-monitoring -o jsonpath<span style="color:#f92672">=</span><span style="color:#e6db74">&#39;{.secrets[1].name}&#39;</span> -n dynatrace<span style="color:#66d9ef">)</span> <span style="color:#ae81ff">\ </span>
--o yaml | grep token
-
-echo <span style="color:#e6db74">&#34;&lt;token&gt;&#34;</span> | base64 --decode
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>oc get secret <span style="color:#66d9ef">$(</span>oc get sa dynatrace-monitoring -o jsonpath<span style="color:#f92672">=</span><span style="color:#e6db74">&#39;{.secrets[1].name}&#39;</span> -n dynatrace<span style="color:#66d9ef">)</span> <span style="color:#ae81ff">\ </span>
+</span></span><span style="display:flex;"><span>-o yaml | grep token
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>echo <span style="color:#e6db74">&#34;&lt;token&gt;&#34;</span> | base64 --decode
+</span></span></code></pre></div><blockquote>
 The result of the command above is the Bearer token that you'll use to connect your OpenShift cluster to Dynatrace.
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"><span style="color:#75715e">#oc get secret $(oc get sa dynatrace-monitoring -o jsonpath=&#39;{.secrets[1].name}&#39; -n dynatrace) -o jsonpath=&#39;{.data.token}&#39; -n dynatrace | base64 --decode</span>
-<span style="color:#75715e">#oc get secret $(oc get sa dynatrace-monitoring -o jsonpath=&#39;{.secrets[1].name}&#39; -n dynatrace) -o yaml | grep token</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span><span style="color:#75715e">#oc get secret $(oc get sa dynatrace-monitoring -o jsonpath=&#39;{.secrets[1].name}&#39; -n dynatrace) -o jsonpath=&#39;{.data.token}&#39; -n dynatrace | base64 --decode</span>
+</span></span><span style="display:flex;"><span><span style="color:#75715e">#oc get secret $(oc get sa dynatrace-monitoring -o jsonpath=&#39;{.secrets[1].name}&#39; -n dynatrace) -o yaml | grep token</span>
+</span></span></code></pre></div><blockquote>
 Connect your OpenShift cluster to Dynatrace 
 You'll need the Bearer token and the Kubernetes API URL mentioned above to set up the connection to the Kubernetes API.
 <p>Go to Settings &gt; Cloud and virtualization &gt; Kubernetes.
@@ -455,7 +455,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -715,7 +715,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -827,7 +827,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -837,7 +837,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -920,7 +920,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab5-s2i/index.html b/workshops/openshift_4_101_dynatrace/lab5-s2i/index.html
index 2cec09a86..aa5b019d2 100644
--- a/workshops/openshift_4_101_dynatrace/lab5-s2i/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab5-s2i/index.html
@@ -328,23 +328,23 @@ <h2 id="lets-build-a-nodejs-web-app-using-s2i">Let&rsquo;s build a node.js web a
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsecdb555e0fe2c6fdd76dbcea20e7e3ab2" class="collapsed">
+      <a data-toggle="collapse" href="#collapseee3406b8c37aecd7def71a407e0cdb56" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsecdb555e0fe2c6fdd76dbcea20e7e3ab2" class="panel-collapse collapse ">
+  <div id="collapseee3406b8c37aecd7def71a407e0cdb56" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project metro-map
-$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
-$ oc expose service dc-metro-map
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project metro-map
+</span></span><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc expose service dc-metro-map
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -451,25 +451,25 @@ <h2 id="check-out-the-build-details">Check out the build details</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse70c0688f8dd01883e3bcef2da1a96cae" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7c672af06b6df64420bceddff9219c42" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse70c0688f8dd01883e3bcef2da1a96cae" class="panel-collapse collapse ">
+  <div id="collapse7c672af06b6df64420bceddff9219c42" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get builds
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get builds
+</span></span></code></pre></div><blockquote>
 Note the name of your build from the above command output and use it to see the logs with:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs builds/<span style="color:#f92672">[</span>BUILD_NAME<span style="color:#f92672">]</span>
-</code></pre></div><p>The console will print out the full log for your build.  Note, you could pipe this to more or less for easier viewing in the CLI.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs builds/<span style="color:#f92672">[</span>BUILD_NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p>The console will print out the full log for your build.  Note, you could pipe this to more or less for easier viewing in the CLI.</p>
 
     </div>
   </div>
@@ -513,21 +513,21 @@ <h2 id="see-the-app-in-action">See the app in action</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsea50884c4b9d7fb95a491491eccfbe0ef" class="collapsed">
+      <a data-toggle="collapse" href="#collapse5063e6c3ec761dc3140668a72392b1ab" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsea50884c4b9d7fb95a491491eccfbe0ef" class="panel-collapse collapse ">
+  <div id="collapse5063e6c3ec761dc3140668a72392b1ab" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get routes
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get routes
+</span></span></code></pre></div><blockquote>
 Copy the HOST/PORT and paste into your favorite web browser:
 </blockquote>
 
@@ -684,7 +684,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -944,7 +944,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1056,7 +1056,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1066,7 +1066,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1149,7 +1149,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/index.html b/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/index.html
index 3e6ae8134..ffda7c0f3 100644
--- a/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab6-deploy3tierapp/index.html
@@ -424,7 +424,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -684,7 +684,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -796,7 +796,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -806,7 +806,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -889,7 +889,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab7-devmanage/index.html b/workshops/openshift_4_101_dynatrace/lab7-devmanage/index.html
index a30077511..6395f215b 100644
--- a/workshops/openshift_4_101_dynatrace/lab7-devmanage/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab7-devmanage/index.html
@@ -328,9 +328,9 @@ <h2 id="setup">Setup</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Goto the terminal and type these commands:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
-$ oc expose service dc-metro-map
-</code></pre></div><h2 id="see-the-app-in-action-and-inspect-some-details">See the app in action and inspect some details</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-app --name<span style="color:#f92672">=</span>dc-metro-map https://github.com/RedHatGov/openshift-workshops.git --context-dir<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc expose service dc-metro-map
+</span></span></code></pre></div><h2 id="see-the-app-in-action-and-inspect-some-details">See the app in action and inspect some details</h2>
 <p>Unlike in previous versions of OpenShift, there is no more ambiguity or confusion about where the app came from.  OpenShift provides traceability for your running deployment, back to the container image, and the registry that it came from. Additionally, images built by OpenShift are traceable back to the exact <a href="https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-branches">branch</a> and <a href="https://help.github.com/en/github/getting-started-with-github/github-glossary#commit">commit</a>. Let&rsquo;s take a look at that!</p>
 <div class="panel-group">
   
@@ -339,21 +339,21 @@ <h2 id="setup">Setup</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse9f9e3738f6c102d8625f14983b23e3bd" class="collapsed">
+      <a data-toggle="collapse" href="#collapse857b81798b9fc859ecb0e5dd7e9c0c35" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse9f9e3738f6c102d8625f14983b23e3bd" class="panel-collapse collapse ">
+  <div id="collapse857b81798b9fc859ecb0e5dd7e9c0c35" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status
-</code></pre></div><p>This is going to show the status of your current project.  In this case it will show the dc-metro-map service (svc) with a nested deployment config(also called a &ldquo;DC&rdquo;) along with some more info that you can ignore for now.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status
+</span></span></code></pre></div><p>This is going to show the status of your current project.  In this case it will show the dc-metro-map service (svc) with a nested deployment config(also called a &ldquo;DC&rdquo;) along with some more info that you can ignore for now.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i>  A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration <br/>
 </blockquote>
@@ -361,8 +361,8 @@ <h4 class="panel-title">
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following to find out more about our dc:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe deploymentconfig/dc-metro-map
-</code></pre></div><p>Notice under the template section it lists the containers it wants to deploy along with the path to the container image.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe deploymentconfig/dc-metro-map
+</span></span></code></pre></div><p>Notice under the template section it lists the containers it wants to deploy along with the path to the container image.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> There are a few other ways you could get to this information.  If you are feeling adventurous, you might also want to try to:
 </blockquote>
@@ -387,8 +387,8 @@ <h4 class="panel-title">
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following to find out more about our bc:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map
-</code></pre></div><p>Notice the information about the configuration of how this app gets built.  In particular look at the github URL, the webhooks you can use to automatically trigger a new build, the docker image where the build runs inside of, and the builds that have been completed.  New let&rsquo;s look at one of those builds.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map
+</span></span></code></pre></div><p>Notice the information about the configuration of how this app gets built.  In particular look at the github URL, the webhooks you can use to automatically trigger a new build, the docker image where the build runs inside of, and the builds that have been completed.  New let&rsquo;s look at one of those builds.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Type the following:
 </blockquote>
@@ -473,26 +473,26 @@ <h2 id="pod-logs">Pod logs</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsed17251e50d717941c20e8c2d893fe34e" class="collapsed">
+      <a data-toggle="collapse" href="#collapseb8c8014515ee60c7623e0becfd66ac4a" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapsed17251e50d717941c20e8c2d893fe34e" class="panel-collapse collapse ">
+  <div id="collapseb8c8014515ee60c7623e0becfd66ac4a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>This is going to show basic details for all pods in this project (including the builders).  Let&rsquo;s look at the log for the pod running our application.  Look for the POD NAME that that is &ldquo;Running&rdquo; you will use it below.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>This is going to show basic details for all pods in this project (including the builders).  Let&rsquo;s look at the log for the pod running our application.  Look for the POD NAME that that is &ldquo;Running&rdquo; you will use it below.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following (replacing the POD ID with your pod's ID):
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span>
-</code></pre></div><p>You will see in the output details of your app starting up and any status messages it has reported since it started.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><p>You will see in the output details of your app starting up and any status messages it has reported since it started.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> You can see more details about the pod itself with 'oc describe pod/<POD NAME>'
 </blockquote>
@@ -555,23 +555,23 @@ <h2 id="how-about-we-set-some-environment-variables">How about we set some envir
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse9f1c2ac947846d09c016927809ec47b8" class="collapsed">
+      <a data-toggle="collapse" href="#collapseafd53982b347e3628cba208fb451b0b2" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse9f1c2ac947846d09c016927809ec47b8" class="panel-collapse collapse ">
+  <div id="collapseafd53982b347e3628cba208fb451b0b2" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p>Let&rsquo;s have a little fun.  The app has some easter eggs that get triggered when certain environment variables are set to &lsquo;true&rsquo;.</p>
+       <p>Let&rsquo;s have a little fun.  The app has some easter eggs that get triggered when certain environment variables are set to &rsquo;true'.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc set env deploymentconfig/dc-metro-map -e BEERME<span style="color:#f92672">=</span>true
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods -w
-</code></pre></div><p>Due to the deployment config strategy being set to &ldquo;Rolling&rdquo; and the &ldquo;ConfigChange&rdquo; trigger being set, OpenShift auto deployed a new pod as soon as you updated the environment variable.  If you were quick enough, you might have seen this happening, with the &ldquo;oc get pods -w&rdquo; command</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc set env deploymentconfig/dc-metro-map -e BEERME<span style="color:#f92672">=</span>true
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>Due to the deployment config strategy being set to &ldquo;Rolling&rdquo; and the &ldquo;ConfigChange&rdquo; trigger being set, OpenShift auto deployed a new pod as soon as you updated the environment variable.  If you were quick enough, you might have seen this happening, with the &ldquo;oc get pods -w&rdquo; command</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Type Ctrl+C to stop watching the pods
 </blockquote>
@@ -643,27 +643,27 @@ <h2 id="getting-into-a-pod">Getting into a pod</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse368bf25641b001e43ef9c9ed76343bf9" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4cce3b2a133bc5daca49351b8dd9f0ac" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse368bf25641b001e43ef9c9ed76343bf9" class="panel-collapse collapse ">
+  <div id="collapse4cce3b2a133bc5daca49351b8dd9f0ac" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>Find the pod name for your Running pod</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc exec -it <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span> /bin/bash
-</code></pre></div><p>You are now interactively attached to the container in your pod.  Let&rsquo;s look for the environment variables we set:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ env | grep BEER
-</code></pre></div><p>That should return the <strong>BEERME=true</strong> matching the value that we set in the deployment config.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ exit
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>Find the pod name for your Running pod</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc exec -it <span style="color:#f92672">[</span>POD NAME<span style="color:#f92672">]</span> /bin/bash
+</span></span></code></pre></div><p>You are now interactively attached to the container in your pod.  Let&rsquo;s look for the environment variables we set:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ env | grep BEER
+</span></span></code></pre></div><p>That should return the <strong>BEERME=true</strong> matching the value that we set in the deployment config.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ exit
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -714,9 +714,9 @@ <h2 id="good-work-lets-clean-this-up">Good work, let&rsquo;s clean this up</h2>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Let&rsquo;s clean up all this to get ready for the next lab:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc delete all -l app<span style="color:#f92672">=</span>dc-metro-map
-$ oc delete secrets dc-metro-map-generic-webhook-secret dc-metro-map-github-webhook-secret    
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc delete all -l app<span style="color:#f92672">=</span>dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc delete secrets dc-metro-map-generic-webhook-secret dc-metro-map-github-webhook-secret    
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>In this lab you&rsquo;ve seen how to trace running software back to its roots, how to see details on the pods running your software, how to update deployment configurations, how to inspect logs files, how to set environment variables consistently across your environment, and how to interactively attach to running containers.  All these things should come in handy for any developer working in an OpenShift platform.</p>
 <p>To dig deeper into the details behind the steps you performed in this lab, check out the OpenShift <a href="https://docs.openshift.com/container-platform/3.4/dev_guide/index.html">developer&rsquo;s guide</a>.</p>
 <style>
@@ -818,7 +818,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1078,7 +1078,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1190,7 +1190,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1200,7 +1200,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1283,7 +1283,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab8-rollbacks/index.html b/workshops/openshift_4_101_dynatrace/lab8-rollbacks/index.html
index 70eadf9d6..140c21f3a 100644
--- a/workshops/openshift_4_101_dynatrace/lab8-rollbacks/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab8-rollbacks/index.html
@@ -394,38 +394,38 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseec010b36bb1a35639c66bd23f0a1847c" class="collapsed">
+      <a data-toggle="collapse" href="#collapse9dd6e7a1653d4687bd2cd90d216fb8e9" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapseec010b36bb1a35639c66bd23f0a1847c" class="panel-collapse collapse ">
+  <div id="collapse9dd6e7a1653d4687bd2cd90d216fb8e9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get bc/dc-metro-map -o yaml | grep generic-webhook
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get bc/dc-metro-map -o yaml | grep generic-webhook
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> ...which returns the name of the secret that we need to find:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">name: dc-metro-map-generic-webhook-secret
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>name: dc-metro-map-generic-webhook-secret
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Now that you have the name of the secret, you can get its value:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ SECRET<span style="color:#f92672">=</span><span style="color:#e6db74">`</span>oc get secrets dc-metro-map-generic-webhook-secret -o yaml | grep -i key | sed <span style="color:#e6db74">&#39;s/^.*: //&#39;</span> | base64 -d ; echo<span style="color:#e6db74">`</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ SECRET<span style="color:#f92672">=</span><span style="color:#e6db74">`</span>oc get secrets dc-metro-map-generic-webhook-secret -o yaml | grep -i key | sed <span style="color:#e6db74">&#39;s/^.*: //&#39;</span> | base64 -d ; echo<span style="color:#e6db74">`</span>
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Last, we can get the URL for the webhook, this way:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe bc/dc-metro-map | grep <span style="color:#e6db74">&#34;Webhook Generic&#34;</span> -A <span style="color:#ae81ff">1</span> | sed <span style="color:#e6db74">&#34;s/&lt;secret&gt;/</span><span style="color:#e6db74">${</span>SECRET<span style="color:#e6db74">}</span><span style="color:#e6db74">/&#34;</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe bc/dc-metro-map | grep <span style="color:#e6db74">&#34;Webhook Generic&#34;</span> -A <span style="color:#ae81ff">1</span> | sed <span style="color:#e6db74">&#34;s/&lt;secret&gt;/</span><span style="color:#e6db74">${</span>SECRET<span style="color:#e6db74">}</span><span style="color:#e6db74">/&#34;</span>
+</span></span></code></pre></div><blockquote>
 ... which results in the information that we need:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">Webhook Generic:
-        URL:            https://api.alexocp43.redhatgov.io:6443/apis/build.openshift.io/v1/namespaces/cicd-1/buildconfigs/dc-metro-map/webhooks/1234abcd5678efgh/generic
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>Webhook Generic:
+</span></span><span style="display:flex;"><span>        URL:            https://api.alexocp43.redhatgov.io:6443/apis/build.openshift.io/v1/namespaces/cicd-1/buildconfigs/dc-metro-map/webhooks/1234abcd5678efgh/generic
+</span></span></code></pre></div><blockquote>
 Copy the "Webhook Generic" URL to the clipboard, so that we can use it in GitHub.
 </blockquote>
 
@@ -545,22 +545,22 @@ <h2 id="rollbacks">Rollbacks</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseaa93cf48d4f1eea9e53cef2911d2b641" class="collapsed">
+      <a data-toggle="collapse" href="#collapse04ecaac60ed3b96410a23867d40d29d9" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapseaa93cf48d4f1eea9e53cef2911d2b641" class="panel-collapse collapse ">
+  <div id="collapse04ecaac60ed3b96410a23867d40d29d9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and type the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc rollout undo dc/dc-metro-map
-$ oc get pods -w
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc rollout undo dc/dc-metro-map
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -713,7 +713,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -973,7 +973,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1085,7 +1085,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1095,7 +1095,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1178,7 +1178,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/index.html b/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/index.html
index f8d3f7dfc..bd6e2d97b 100644
--- a/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/index.html
+++ b/workshops/openshift_4_101_dynatrace/lab9-replicationrecovery/index.html
@@ -328,25 +328,25 @@ <h2 id="replication">Replication</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse996af14f4ed8b575f2c14568c77e6681" class="collapsed">
+      <a data-toggle="collapse" href="#collapse098510ee7a35794d5d9fe522d8601802" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse996af14f4ed8b575f2c14568c77e6681" class="panel-collapse collapse ">
+  <div id="collapse098510ee7a35794d5d9fe522d8601802" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Goto the terminal and try the following:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc scale --replicas<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span> dc/dc-metro-map
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc scale --replicas<span style="color:#f92672">=</span><span style="color:#ae81ff">4</span> dc/dc-metro-map
+</span></span></code></pre></div><blockquote>
 <i class="fa fa-terminal"></i> Check out the new pods:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><p>Notice that you now have 4 unique pods available to inspect.  If you want go ahead and inspect them, using &lsquo;oc describe pod/<b>POD NAME</b>&rsquo;. You can see that each has its own IP address and logs.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><p>Notice that you now have 4 unique pods available to inspect.  If you want go ahead and inspect them, using &lsquo;oc describe pod/<b>POD NAME</b>&rsquo;. You can see that each has its own IP address and logs.</p>
 
     </div>
   </div>
@@ -399,28 +399,28 @@ <h2 id="recovery">Recovery</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse361bd4628df4d5b05bf2ca805e7f73c8" class="collapsed">
+      <a data-toggle="collapse" href="#collapse795ec71b1119c359a3c0b98d33ff36ea" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse361bd4628df4d5b05bf2ca805e7f73c8" class="panel-collapse collapse ">
+  <div id="collapse795ec71b1119c359a3c0b98d33ff36ea" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Choose a random pod and delete it:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc delete pod/PODNAME
-$ oc get pods -w
-</code></pre></div><p>If you&rsquo;re fast enough you&rsquo;ll see the pod you deleted go &ldquo;Terminating&rdquo; and you&rsquo;ll also see a new pod immediately get created and transition from &ldquo;Pending&rdquo; to &ldquo;Running&rdquo;.  If you weren&rsquo;t fast enough you can see that your old pod is gone and a new pod is in the list with an age of only a few seconds.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc delete pod/PODNAME
+</span></span><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>If you&rsquo;re fast enough you&rsquo;ll see the pod you deleted go &ldquo;Terminating&rdquo; and you&rsquo;ll also see a new pod immediately get created and transition from &ldquo;Pending&rdquo; to &ldquo;Running&rdquo;.  If you weren&rsquo;t fast enough you can see that your old pod is gone and a new pod is in the list with an age of only a few seconds.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i>  You can see the more details about your deployment configuration with:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc describe dc/dc-metro-map
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc describe dc/dc-metro-map
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -477,38 +477,38 @@ <h2 id="application-health">Application Health</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse308612c980500fa293cad5ede5225ec4" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4259ced397e22ccb9804c7e6630687bb" class="collapsed">
       
         CLI Steps
       </a>
     </h4>
   </div>
   
-  <div id="collapse308612c980500fa293cad5ede5225ec4" class="panel-collapse collapse ">
+  <div id="collapse4259ced397e22ccb9804c7e6630687bb" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i> Choose a running pod and shell into it:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-$ oc exec PODNAME -it /bin/bash
-</code></pre></div><p>You are now executing a bash shell running in the container of the pod.  Let&rsquo;s kill our webapp and see what happens.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span><span style="display:flex;"><span>$ oc exec PODNAME -it /bin/bash
+</span></span></code></pre></div><p>You are now executing a bash shell running in the container of the pod.  Let&rsquo;s kill our webapp and see what happens.</p>
 <blockquote>
 <i class="fa fa-info-circle"></i> If we had multiple containers in the pod we could use "-c CONTAINER_NAME" to select the right one
 </blockquote>
 <blockquote>
 <i class="fa fa-terminal"></i> Choose a running pod and shell into its container:
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ pkill -9 node
-</code></pre></div><p>This will kick you out off the container with an error like &ldquo;Error executing command in container&rdquo;</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ pkill -9 node
+</span></span></code></pre></div><p>This will kick you out off the container with an error like &ldquo;Error executing command in container&rdquo;</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Do it again - shell in and execute the same command to kill node
 </blockquote>
 <blockquote>
 <i class="fa fa-terminal"></i> Watch for the container restart
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods -w
-</code></pre></div><p>If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state.  This ensures the system doesn&rsquo;t waste resources trying to restart containers that are continuously crashing.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods -w
+</span></span></code></pre></div><p>If a container dies multiple times quickly, OpenShift is going to put the pod in a CrashBackOff state.  This ensures the system doesn&rsquo;t waste resources trying to restart containers that are continuously crashing.</p>
 
     </div>
   </div>
@@ -663,7 +663,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -923,7 +923,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1035,7 +1035,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1045,7 +1045,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1128,7 +1128,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_4_101_dynatrace/prerequisites/index.html b/workshops/openshift_4_101_dynatrace/prerequisites/index.html
index 11e99a518..096efedb5 100644
--- a/workshops/openshift_4_101_dynatrace/prerequisites/index.html
+++ b/workshops/openshift_4_101_dynatrace/prerequisites/index.html
@@ -423,7 +423,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -683,7 +683,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -795,7 +795,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -805,7 +805,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -884,7 +884,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_serverless/index.html b/workshops/openshift_serverless/index.html
index 60834175f..7e8383775 100644
--- a/workshops/openshift_serverless/index.html
+++ b/workshops/openshift_serverless/index.html
@@ -313,7 +313,7 @@ <h2 id="labs">Labs</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_serverless/index.xml b/workshops/openshift_serverless/index.xml
index af14c7aa4..e8c4a1a59 100644
--- a/workshops/openshift_serverless/index.xml
+++ b/workshops/openshift_serverless/index.xml
@@ -4,11 +4,8 @@
     <title>OpenShift Serverless on Red Hat | Public Sector</title>
     <link>/workshops/openshift_serverless/</link>
     <description>Recent content in OpenShift Serverless on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/openshift_serverless/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/openshift_serverless/index.xml" rel="self" type="application/rss+xml" />
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/openshift_service_mesh/index.html b/workshops/openshift_service_mesh/index.html
index 597b99b51..80e1fa964 100644
--- a/workshops/openshift_service_mesh/index.html
+++ b/workshops/openshift_service_mesh/index.html
@@ -309,7 +309,7 @@ <h2 id="labs">Labs</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh/index.xml b/workshops/openshift_service_mesh/index.xml
index 6502af60a..640f0d8bf 100644
--- a/workshops/openshift_service_mesh/index.xml
+++ b/workshops/openshift_service_mesh/index.xml
@@ -4,11 +4,8 @@
     <title>OpenShift Service Mesh on Red Hat | Public Sector</title>
     <link>/workshops/openshift_service_mesh/</link>
     <description>Recent content in OpenShift Service Mesh on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/openshift_service_mesh/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/openshift_service_mesh/index.xml" rel="self" type="application/rss+xml" />
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/openshift_service_mesh_v1.0/fin/index.html b/workshops/openshift_service_mesh_v1.0/fin/index.html
index 67d7eaa99..8a97af60d 100644
--- a/workshops/openshift_service_mesh_v1.0/fin/index.html
+++ b/workshops/openshift_service_mesh_v1.0/fin/index.html
@@ -418,7 +418,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -678,7 +678,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -790,7 +790,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -800,7 +800,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -879,7 +879,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/index.html b/workshops/openshift_service_mesh_v1.0/index.html
index 1c2bf2d5d..9d46544ce 100644
--- a/workshops/openshift_service_mesh_v1.0/index.html
+++ b/workshops/openshift_service_mesh_v1.0/index.html
@@ -528,7 +528,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -788,7 +788,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -900,7 +900,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -910,7 +910,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -960,7 +960,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/index.xml b/workshops/openshift_service_mesh_v1.0/index.xml
index c81570033..94010f9b5 100644
--- a/workshops/openshift_service_mesh_v1.0/index.xml
+++ b/workshops/openshift_service_mesh_v1.0/index.xml
@@ -4,222 +4,148 @@
     <title>zOpenShift Service Mesh on Red Hat | Public Sector</title>
     <link>/workshops/openshift_service_mesh_v1.0/</link>
     <description>Recent content in zOpenShift Service Mesh on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/openshift_service_mesh_v1.0/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/openshift_service_mesh_v1.0/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Deploy Your Own Terminal</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/</guid>
-      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.
-Let&amp;rsquo;s Login to the Web Console  Use your browser to navigate to the below URI, and login with the username userYOUR#  and the password provided by your instructor:
- https://console-openshift-console.apps.example.redhatgov.io  Login Webpage
-Once logged in you should see your available projects - or a button to create a project if none exist already:</description>
+      <description>Accessing OpenShift OpenShift provides a web console that allows you to perform various tasks via a web browser.&#xA;Let&amp;rsquo;s Login to the Web Console Use your browser to navigate to the below URI, and login with the username userYOUR# and the password provided by your instructor:&#xA;https://console-openshift-console.apps.example.redhatgov.io Login Webpage&#xA;Once logged in you should see your available projects - or a button to create a project if none exist already:</description>
     </item>
-    
     <item>
       <title>Fin.</title>
       <link>/workshops/openshift_service_mesh_v1.0/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of why a service mesh is critical when developing and operating microservice applications. Istio is an emerging technology so keep checking the upstream announcements and blog for exciting news.
-Also, release notes are a great place to see changes that occurred between releases. You can find the OpenShift Service Mesh release notes here and the upstream Istio project release notes here.</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of why a service mesh is critical when developing and operating microservice applications. Istio is an emerging technology so keep checking the upstream announcements and blog for exciting news.&#xA;Also, release notes are a great place to see changes that occurred between releases. You can find the OpenShift Service Mesh release notes here and the upstream Istio project release notes here.</description>
     </item>
-    
     <item>
       <title>Intro to Service Mesh - Adding a New Service</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/</guid>
-      <description>Adding a New Service to the Mesh You need to deploy the new user profile application into the service mesh.
-Deploy Application The deployment file &amp;lsquo;userprofile-deploy-all.yaml&amp;rsquo; was created for you to deploy the application. The file creates the user profile service and an accompanying PostgreSQL database. Similar to the other source files, an annotation &amp;lsquo;sidecar.istio.io/inject&amp;rsquo; was added to tell Istio to inject a sidecar proxy and add this to the mesh.</description>
+      <description>Adding a New Service to the Mesh You need to deploy the new user profile application into the service mesh.&#xA;Deploy Application The deployment file &amp;lsquo;userprofile-deploy-all.yaml&amp;rsquo; was created for you to deploy the application. The file creates the user profile service and an accompanying PostgreSQL database. Similar to the other source files, an annotation &amp;lsquo;sidecar.istio.io/inject&amp;rsquo; was added to tell Istio to inject a sidecar proxy and add this to the mesh.</description>
     </item>
-    
     <item>
       <title>Intro to Service Mesh - Building a Microservice</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/</guid>
-      <description>Building a Microservice   In the browser, navigate to the &#39;Profile&#39; section in the header.   If you lost the URL, you can retrieve it via:
-`echo $GATEWAY_URL` You should see the following:
- Unknown Profile Page
-The UI shows an unknown user and that&amp;rsquo;s because there&amp;rsquo;s no profile service for your application. You are going to build a new microservice for user profiles and add this to your service mesh.</description>
+      <description>Building a Microservice In the browser, navigate to the &#39;Profile&#39; section in the header. If you lost the URL, you can retrieve it via:&#xA;`echo $GATEWAY_URL` You should see the following:&#xA;Unknown Profile Page&#xA;The UI shows an unknown user and that&amp;rsquo;s because there&amp;rsquo;s no profile service for your application. You are going to build a new microservice for user profiles and add this to your service mesh.&#xA;Application Code Your new application is written in Java, whereas the other backend components such as &amp;lsquo;app-ui&amp;rsquo; and &amp;lsquo;boards&amp;rsquo; are written in NodeJS.</description>
     </item>
-    
     <item>
       <title>Intro to Service Mesh - Deploying an App</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/</guid>
-      <description>Deploying an App into the Service Mesh It&amp;rsquo;s time to deploy your microservices application. The application you are working on is a paste board application in which users can post comments in shared boards. Here is a diagram of the architecture:
-
-App Architecture
-The microservices include single sign-on (SSO), user interface (UI), the boards application, and the context scraper. In this scenario, you are going to deploy these services and then add a new user profile service.</description>
+      <description>Deploying an App into the Service Mesh It&amp;rsquo;s time to deploy your microservices application. The application you are working on is a paste board application in which users can post comments in shared boards. Here is a diagram of the architecture:&#xA;App Architecture&#xA;The microservices include single sign-on (SSO), user interface (UI), the boards application, and the context scraper. In this scenario, you are going to deploy these services and then add a new user profile service.</description>
     </item>
-    
     <item>
       <title>Microservices</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/</guid>
-      <description>A Brief Introduction to Microservices Microservices, also known as the microservice architecture, is a software development technique that structures an application as a collection of loosely coupled services. Microservice architectures enable the continuous delivery/deployment/scaling of complex applications.
-Why microservices? Agility. Deliver application updates faster. Isolate and fix bugs easier. Done right, a microservices architecture will you help to meet several important non-functional requirements for your software:
- scalability performance reliability resiliency extensibility availability  What is a Service Mesh?</description>
+      <description>A Brief Introduction to Microservices Microservices, also known as the microservice architecture, is a software development technique that structures an application as a collection of loosely coupled services. Microservice architectures enable the continuous delivery/deployment/scaling of complex applications.&#xA;Why microservices? Agility. Deliver application updates faster. Isolate and fix bugs easier. Done right, a microservices architecture will you help to meet several important non-functional requirements for your software:&#xA;scalability performance reliability resiliency extensibility availability What is a Service Mesh?</description>
     </item>
-    
     <item>
       <title>Observability - Feature Update</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/</guid>
-      <description>Digging into Observability Istio provides additional capabilities to analyze the service mesh and its performance. Let&amp;rsquo;s deploy a new version of the user profile service and analyze its effect on the service mesh.
-Feature Update The code has already been written for you on the &amp;lsquo;workshop-feature-update&amp;rsquo; branch of the repo.
-  Create a new build on this feature branch:  oc new-app -f ./openshift-configuration/userprofile-build.yaml \ -p APPLICATION_NAME=userprofile \ -p APPLICATION_CODE_URI=https://github.</description>
+      <description>Digging into Observability Istio provides additional capabilities to analyze the service mesh and its performance. Let&amp;rsquo;s deploy a new version of the user profile service and analyze its effect on the service mesh.&#xA;Feature Update The code has already been written for you on the &amp;lsquo;workshop-feature-update&amp;rsquo; branch of the repo.&#xA;Create a new build on this feature branch: oc new-app -f ./openshift-configuration/userprofile-build.yaml \ -p APPLICATION_NAME=userprofile \ -p APPLICATION_CODE_URI=https://github.com/RedHatGov/openshift-microservices.git \ -p APPLICATION_CODE_BRANCH=workshop-feature-update \ -p APP_VERSION_TAG=2.</description>
     </item>
-    
     <item>
       <title>Observability - Grafana</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/</guid>
-      <description>Service Mesh Metrics with Grafana Grafana is a monitoring tool that can be integrated with Istio for metric observation. Using Grafana, you can look at metrics associated with services in your mesh. Let&amp;rsquo;s use Grafana to get more information about the user profile service.
-Explore Grafana First, let&amp;rsquo;s explore the Grafana user interface.
-  Open the Grafana console. Retrieve the endpoint for Grafana:  GRAFANA_CONSOLE=$(oc get route grafana -n istio-system --template=&#39;https://{{.</description>
+      <description>Service Mesh Metrics with Grafana Grafana is a monitoring tool that can be integrated with Istio for metric observation. Using Grafana, you can look at metrics associated with services in your mesh. Let&amp;rsquo;s use Grafana to get more information about the user profile service.&#xA;Explore Grafana First, let&amp;rsquo;s explore the Grafana user interface.&#xA;Open the Grafana console. Retrieve the endpoint for Grafana: GRAFANA_CONSOLE=$(oc get route grafana -n istio-system --template=&amp;#39;https://{{.spec.host}}&amp;#39;) echo $GRAFANA_CONSOLE Click &#39;Allow selected permissions&#39; if prompted to authorized access.</description>
     </item>
-    
     <item>
       <title>Observability - Jaeger</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/</guid>
-      <description>Distributed Tracing with Jaeger Jaeger is a distributed tracing tool that lets you trace requests as they flow through your service mesh. This is incredibly useful for debugging performance issues in your microservices architecture.
-Explore Jaeger First, let&amp;rsquo;s explore the Jaeger user interface.
-  Open the Jaeger console. Retrieve the endpoint for Jaeger:  JAEGER_CONSOLE=$(oc get route jaeger -n istio-system --template=&#39;https://{{.spec.host}}&#39;) echo $JAEGER_CONSOLE  Click &#39;Allow selected permissions&#39; if prompted to authorized access.</description>
+      <description>Distributed Tracing with Jaeger Jaeger is a distributed tracing tool that lets you trace requests as they flow through your service mesh. This is incredibly useful for debugging performance issues in your microservices architecture.&#xA;Explore Jaeger First, let&amp;rsquo;s explore the Jaeger user interface.&#xA;Open the Jaeger console. Retrieve the endpoint for Jaeger: JAEGER_CONSOLE=$(oc get route jaeger -n istio-system --template=&amp;#39;https://{{.spec.host}}&amp;#39;) echo $JAEGER_CONSOLE Click &#39;Allow selected permissions&#39; if prompted to authorized access.</description>
     </item>
-    
     <item>
       <title>Observability - Kiali</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/</guid>
-      <description>Introducing Kiali for Observability All of your microservices are running in the service mesh. Now, you need a way to visualize the service mesh topology. That is, what&amp;rsquo;s running in your service mesh and how are they connected?
-Istio provides Kiali, an open source project that gives you a console view of your service mesh. You can inspect the health of your service mesh, and it has further integrations for metric querying and tracing that we will cover in later labs.</description>
+      <description>Introducing Kiali for Observability All of your microservices are running in the service mesh. Now, you need a way to visualize the service mesh topology. That is, what&amp;rsquo;s running in your service mesh and how are they connected?&#xA;Istio provides Kiali, an open source project that gives you a console view of your service mesh. You can inspect the health of your service mesh, and it has further integrations for metric querying and tracing that we will cover in later labs.</description>
     </item>
-    
     <item>
       <title>Security - Auth Policy</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/</guid>
       <description>Authorizing and Authenticating Access via Policy In the previous labs we secured and verified the service-to-service communication. But what about user-to-service communication (aka origin authentication)? The service mesh can help with that too. To do this, we need to bring in an identity provider that will issue JSON Web Tokens (JWTs) to signed in users. JWTs are an open, industry standard (RFC 7519) way of sharing identity. The app-ui service will pass those JWTs along with it&amp;rsquo;s API requests.</description>
     </item>
-    
     <item>
       <title>Security - Auth Policy Prep</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.3_prep/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.3_prep/</guid>
-      <description>Single Sign-On Login, registration, and role-based authorization is handled via Red Hat SSO (aka Keycloak). SSO is included as part of OpenShift or any middleware product subscription you have from Red Hat - woot!
-Installation Because the service mesh will leverage SSO to authenticate users and generate JWT we need to install it. You will install it via Operator into your namespace.
-Customize the Resources Check out the .yaml files here and customize for this workshop cluster&amp;rsquo;s domain, and your user project.</description>
+      <description>Single Sign-On Login, registration, and role-based authorization is handled via Red Hat SSO (aka Keycloak). SSO is included as part of OpenShift or any middleware product subscription you have from Red Hat - woot!&#xA;Installation Because the service mesh will leverage SSO to authenticate users and generate JWT we need to install it. You will install it via Operator into your namespace.&#xA;Customize the Resources Check out the .yaml files here and customize for this workshop cluster&amp;rsquo;s domain, and your user project.</description>
     </item>
-    
     <item>
       <title>Security - mTLS</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/</guid>
-      <description>Mutual TLS One of the key features of the Service Mesh is its ability to bring additional security to your applications. It does this in a several different ways that will be explored in the next few labs. The first of which is a concept known as &amp;ldquo;Mutual TLS&amp;rdquo; or mTLS for short.
-Imagine a scenario where you are deploying a microservices application and are expecting a lot of PII to flow between the services.</description>
+      <description>Mutual TLS One of the key features of the Service Mesh is its ability to bring additional security to your applications. It does this in a several different ways that will be explored in the next few labs. The first of which is a concept known as &amp;ldquo;Mutual TLS&amp;rdquo; or mTLS for short.&#xA;Imagine a scenario where you are deploying a microservices application and are expecting a lot of PII to flow between the services.</description>
     </item>
-    
     <item>
       <title>Security - Securing Ingress and Egress</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/</guid>
-      <description>Securing Ingress and Egress In cases where strict security is required we need to configure specifics around securing ingress and egress traffic. Security around egress is often used to lock down and deny access to potentially harmful resources outside the network. Additionally, it is a good practice to prevent malicious activities from originating from the cluster.
-You are probably already familiar with basic ingress security concepts. Essentially, only exposing particular services to be accessible from outside the cluster and using basic TLS/SSL.</description>
+      <description>Securing Ingress and Egress In cases where strict security is required we need to configure specifics around securing ingress and egress traffic. Security around egress is often used to lock down and deny access to potentially harmful resources outside the network. Additionally, it is a good practice to prevent malicious activities from originating from the cluster.&#xA;You are probably already familiar with basic ingress security concepts. Essentially, only exposing particular services to be accessible from outside the cluster and using basic TLS/SSL.</description>
     </item>
-    
     <item>
       <title>Security - Verifying mTLS</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/</guid>
-      <description>Checking and Verification of mTLS OK, now that all our services are encrypting traffic Let&amp;rsquo;s take a look in Kiali to see our encryption setup.
-  Open up the dashboard to Kiali (if you don&#39;t already have it open) and navigate to the Graph view. In the first drop down select the &#34;Service graph&#34; and in the &#34;Display&#34; drop down make sure the &#34;Security&#34; check box is checked.  You should see something like this screenshot with little locks indicating that mTLS is working for service-to-service communication.</description>
+      <description>Checking and Verification of mTLS OK, now that all our services are encrypting traffic Let&amp;rsquo;s take a look in Kiali to see our encryption setup.&#xA;Open up the dashboard to Kiali (if you don&#39;t already have it open) and navigate to the Graph view. In the first drop down select the &#34;Service graph&#34; and in the &#34;Display&#34; drop down make sure the &#34;Security&#34; check box is checked. You should see something like this screenshot with little locks indicating that mTLS is working for service-to-service communication.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab1.3_installing/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab1.3_installing/</guid>
-      <description>Setup You will conduct these labs in an OpenShift cluster. As in the previous terminal deployment exercise, you can access your cluster via console and CLI.
-OpenShift You will use the OpenShift &amp;lsquo;oc&amp;rsquo; CLI to execute commands for the majority of this lab.
-  Login using API endpoint and remember to add the &#39;--insecure-skip-tls-verify=true&#39; flag  $ oc login https://api.example.redhatgov.io:6443 --insecure-skip-tls-verify=true Authentication required for https://api.example.redhatgov.io:6443 (openshift) Username: userYOUR# Password: Login successful.</description>
+      <description>Setup You will conduct these labs in an OpenShift cluster. As in the previous terminal deployment exercise, you can access your cluster via console and CLI.&#xA;OpenShift You will use the OpenShift &amp;lsquo;oc&amp;rsquo; CLI to execute commands for the majority of this lab.&#xA;Login using API endpoint and remember to add the &#39;--insecure-skip-tls-verify=true&#39; flag $ oc login https://api.example.redhatgov.io:6443 --insecure-skip-tls-verify=true Authentication required for https://api.example.redhatgov.io:6443 (openshift) Username: userYOUR# Password: Login successful. The instructor will have preconfigured your projects for you.</description>
     </item>
-    
     <item>
       <title>Traffic Control - Circuit Breaking</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/</guid>
-      <description>Circuit Breaking Your Services Fault Injection lets you see how the service mesh behaves when there are failures in network calls to a specific service. But how do you protect a service if it has overloaded or failing instances serving traffic? Ideally, you would like to identify an instance that is failing and prevent clients from connecting to it once it meets a certain threshold.
-In OpenShift, an instance is equivalent to a Kubernetes pod running the microservice.</description>
+      <description>Circuit Breaking Your Services Fault Injection lets you see how the service mesh behaves when there are failures in network calls to a specific service. But how do you protect a service if it has overloaded or failing instances serving traffic? Ideally, you would like to identify an instance that is failing and prevent clients from connecting to it once it meets a certain threshold.&#xA;In OpenShift, an instance is equivalent to a Kubernetes pod running the microservice.</description>
     </item>
-    
     <item>
       <title>Traffic Control - Fault Injection</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/</guid>
-      <description>Testing Resiliency with Fault Injection Your application is working great now with the new version of the user profile service. But the previous version caused performance issues, and future updates may cause issues in other areas of the application. How can you test how your application behaves when a failure occurs?
-You need a way to simulate failure in the service mesh. By doing so, you can test if your application functions correctly in a degraded state.</description>
+      <description>Testing Resiliency with Fault Injection Your application is working great now with the new version of the user profile service. But the previous version caused performance issues, and future updates may cause issues in other areas of the application. How can you test how your application behaves when a failure occurs?&#xA;You need a way to simulate failure in the service mesh. By doing so, you can test if your application functions correctly in a degraded state.</description>
     </item>
-    
     <item>
       <title>Traffic Control - Routing Traffic</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/</guid>
-      <description>Basics on Routing Traffic Through the Mesh One of Istio&amp;rsquo;s core capabilities is the ability to dynamically control how services communicate without modifying the application code itself. The general concept is called Traffic Management. It allows you to do things such as A/B test, canary rollouts, rollbacks, and more.
-The two core API objects for traffic management are the Virtual Service and the Destination Rule. The destination rule is for the owner of a microservice - what versions do I expose and what happens to traffic before it reaches my service?</description>
+      <description>Basics on Routing Traffic Through the Mesh One of Istio&amp;rsquo;s core capabilities is the ability to dynamically control how services communicate without modifying the application code itself. The general concept is called Traffic Management. It allows you to do things such as A/B test, canary rollouts, rollbacks, and more.&#xA;The two core API objects for traffic management are the Virtual Service and the Destination Rule. The destination rule is for the owner of a microservice - what versions do I expose and what happens to traffic before it reaches my service?</description>
     </item>
-    
     <item>
       <title>Traffic Control - Traffic Splitting</title>
       <link>/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/</guid>
-      <description>Splitting Traffic Amongst Service Versions It&amp;rsquo;s time to fix the performance issue of the application. Previously, you deployed a new version of the application and routed 100% of traffic to the new version. This time, you&amp;rsquo;ll use Istio traffic routing to do canary rollouts and split traffic.
-Feature Fix The code to fix the performance issue of the user profile service has already been written for you on the &amp;lsquo;workshop-feature-fix&amp;rsquo; branch.</description>
+      <description>Splitting Traffic Amongst Service Versions It&amp;rsquo;s time to fix the performance issue of the application. Previously, you deployed a new version of the application and routed 100% of traffic to the new version. This time, you&amp;rsquo;ll use Istio traffic routing to do canary rollouts and split traffic.&#xA;Feature Fix The code to fix the performance issue of the user profile service has already been written for you on the &amp;lsquo;workshop-feature-fix&amp;rsquo; branch.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/index.html b/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/index.html
index ef8227413..7c0b267af 100644
--- a/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab1.1_welcome/index.html
@@ -429,7 +429,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -689,7 +689,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -801,7 +801,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -811,7 +811,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -890,7 +890,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/index.html b/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/index.html
index b087f561c..caf7a9cf8 100644
--- a/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab1.2_terminal/index.html
@@ -324,8 +324,8 @@ <h2 id="lets-login-to-the-web-console">Let&rsquo;s Login to the Web Console</h2>
 <p>Use your browser to navigate to the below URI, and login with the username <code>user<span class="userid">YOUR#</span>
 </code> and the password provided by your instructor:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>
-</code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://console-openshift-console.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>
+</span></span></code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
 <em>Login Webpage</em></p>
 <p>Once logged in you should see your available projects - or a button to create a project if none exist already:</p>
 <p><img src="../images/ocp-admin-default.png" width="600"><br/>
@@ -478,7 +478,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -738,7 +738,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -850,7 +850,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -860,7 +860,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -943,7 +943,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab1.3_installing/index.html b/workshops/openshift_service_mesh_v1.0/lab1.3_installing/index.html
index 5fc01a637..dd458ecbc 100644
--- a/workshops/openshift_service_mesh_v1.0/lab1.3_installing/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab1.3_installing/index.html
@@ -324,7 +324,7 @@ <h2 id="openshift">OpenShift</h2>
 <blockquote>
 <i class="fa fa-terminal"></i> Login using API endpoint and remember to add the '--insecure-skip-tls-verify=true' flag
 </blockquote>
-<pre><code>$ oc login https://api.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443 --insecure-skip-tls-verify=true
+<pre tabindex="0"><code>$ oc login https://api.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443 --insecure-skip-tls-verify=true
 Authentication required for https://api.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443 (openshift)
  Username: user<span class="userid">YOUR#</span>
  Password:
@@ -334,22 +334,22 @@ <h2 id="openshift">OpenShift</h2>
 <blockquote>
 <i class="fa fa-terminal"></i> List your projects:
 </blockquote>
-<pre><code>oc projects
+<pre tabindex="0"><code>oc projects
 </code></pre><p>You should see two projects: your user project (e.g. &lsquo;userX&rsquo;) and &lsquo;istio-system&rsquo;.</p>
 <br>
 <blockquote>
 <i class="fa fa-terminal"></i> Switch to your user project.  For example:
 </blockquote>
-<pre><code>oc project user<span class="userid">YOUR#</span>
+<pre tabindex="0"><code>oc project user<span class="userid">YOUR#</span>
 
 </code></pre><br>
 <p>Let&rsquo;s take a look at the project.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> List the pods in the project:
 </blockquote>
-<pre><code>oc get pods
+<pre tabindex="0"><code>oc get pods
 </code></pre><p>Output (sample):</p>
-<pre><code>NAME                                       READY   STATUS    RESTARTS   AGE
+<pre tabindex="0"><code>NAME                                       READY   STATUS    RESTARTS   AGE
 istio-demogateway-user1-xxxxxxxxxx-xxxxx   1/1     Running   0          2m41s
 keycloak-operator-xxxxxxxxx-xxxxx          1/1     Running   0          15h
 </code></pre><p>The gateway is a load balancer dedicated to your project.  You will configure this load balancer in the next lab.  The keycloak operator will be used in the security labs.</p>
@@ -359,23 +359,23 @@ <h2 id="openshift">OpenShift</h2>
 <i class="fa fa-terminal"></i>
 Run this command:
 </blockquote>
-<pre><code>PROJECT_NAME=$(oc project -q)
+<pre tabindex="0"><code>PROJECT_NAME=$(oc project -q)
 </code></pre><br>
 <h2 id="application-code">Application Code</h2>
 <p>Next we need a local copy of our application code.</p>
 <blockquote>
 <i class="fa fa-terminal"></i> Clone the repository:
 </blockquote>
-<pre><code>git clone https://github.com/RedHatGov/openshift-microservices.git
+<pre tabindex="0"><code>git clone https://github.com/RedHatGov/openshift-microservices.git
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i> Checkout the workshop-stable branch:
 </blockquote>
-<pre><code>cd openshift-microservices &amp;&amp; git checkout workshop-stable
+<pre tabindex="0"><code>cd openshift-microservices &amp;&amp; git checkout workshop-stable
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Navigate to the workshop directory:
 </blockquote>
-<pre><code>cd deployment/workshop
+<pre tabindex="0"><code>cd deployment/workshop
 </code></pre><br>
 <h2 id="istio">Istio</h2>
 <p>Istio should have been installed in the cluster by the instructor.  Let&rsquo;s make sure Istio is running in the cluster.  You will only have view access to the Istio project.</p>
@@ -383,9 +383,9 @@ <h2 id="istio">Istio</h2>
 <i class="fa fa-terminal"></i>
 List all the Istio components:
 </blockquote>
-<pre><code>oc get pods -n istio-system
+<pre tabindex="0"><code>oc get pods -n istio-system
 </code></pre><p>Output:</p>
-<pre><code>NAME                                      READY   STATUS    RESTARTS   AGE
+<pre tabindex="0"><code>NAME                                      READY   STATUS    RESTARTS   AGE
 grafana-xxxxxxxxx-xxxxx                  2/2     Running   0          17m
 istio-citadel-xxxxxxxxx-xxxxx            1/1     Running   0          20m
 istio-egressgateway-xxxxxxxx-xxxxx       1/1     Running   0          17m
@@ -498,7 +498,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -758,7 +758,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -870,7 +870,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -880,7 +880,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -963,7 +963,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/index.html b/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/index.html
index 6982af1af..351e8bc78 100644
--- a/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab1.4_deploymsa/index.html
@@ -330,17 +330,17 @@ <h2 id="deploy-microservices">Deploy Microservices</h2>
 <i class="fa fa-terminal"></i>
 Verify the annotation in the 'app-ui' file:
 </blockquote>
-<pre><code>cat openshift-configuration/app-ui-fromsource.yaml | grep -B 1 sidecar.istio.io/inject
+<pre tabindex="0"><code>cat openshift-configuration/app-ui-fromsource.yaml | grep -B 1 sidecar.istio.io/inject
 </code></pre><p>Output:</p>
-<pre><code>	annotations:
-	  sidecar.istio.io/inject: &quot;true&quot;
+<pre tabindex="0"><code>	annotations:
+	  sidecar.istio.io/inject: &#34;true&#34;
 </code></pre><br>
 <p>Now let&rsquo;s deploy the microservices.</p>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Deploy the boards service:
 </blockquote>
-<pre><code>oc new-app -f ./openshift-configuration/boards-fromsource.yaml \
+<pre tabindex="0"><code>oc new-app -f ./openshift-configuration/boards-fromsource.yaml \
   -p APPLICATION_NAME=boards \
   -p NODEJS_VERSION_TAG=10 \
   -p GIT_URI=https://github.com/RedHatGov/openshift-microservices.git \
@@ -351,7 +351,7 @@ <h2 id="deploy-microservices">Deploy Microservices</h2>
 <i class="fa fa-terminal"></i>
 Deploy the context scraper service:
 </blockquote>
-<pre><code>oc new-app -f ./openshift-configuration/context-scraper-fromsource.yaml \
+<pre tabindex="0"><code>oc new-app -f ./openshift-configuration/context-scraper-fromsource.yaml \
   -p APPLICATION_NAME=context-scraper \
   -p NODEJS_VERSION_TAG=10 \
   -p GIT_BRANCH=workshop-stable \
@@ -360,7 +360,7 @@ <h2 id="deploy-microservices">Deploy Microservices</h2>
 <i class="fa fa-terminal"></i>
 Deploy the user interface:
 </blockquote>
-<pre><code>oc new-app -f ./openshift-configuration/app-ui-fromsource.yaml \
+<pre tabindex="0"><code>oc new-app -f ./openshift-configuration/app-ui-fromsource.yaml \
   -p APPLICATION_NAME=app-ui \
   -p NODEJS_VERSION_TAG=10 \
   -p GIT_BRANCH=workshop-stable \
@@ -370,10 +370,10 @@ <h2 id="deploy-microservices">Deploy Microservices</h2>
 <i class="fa fa-terminal"></i>
 Watch the microservices demo installation:
 </blockquote>
-<pre><code>oc get pods --watch
+<pre tabindex="0"><code>oc get pods --watch
 </code></pre><br>
 <p>Wait a couple minutes.  You should see the &lsquo;app-ui&rsquo;, &lsquo;boards&rsquo;, &lsquo;context-scraper&rsquo;, and &lsquo;sso&rsquo; pods running.  For example:</p>
-<pre><code>NAME                       READY   STATUS      RESTARTS   AGE
+<pre tabindex="0"><code>NAME                       READY   STATUS      RESTARTS   AGE
 app-ui-1-build             0/1     Completed   0          64m
 app-ui-1-xxxxx             2/2     Running     0          62m
 app-ui-1-deploy            0/1     Completed   0          62m
@@ -391,9 +391,9 @@ <h2 id="deploy-microservices">Deploy Microservices</h2>
 <i class="fa fa-terminal"></i>
 Print the containers in the 'app-ui' pod:
 </blockquote>
-<pre><code>oc get pods -l app=app-ui -o jsonpath='{.items[*].spec.containers[*].name}{&quot;\n&quot;}'
+<pre tabindex="0"><code>oc get pods -l app=app-ui -o jsonpath=&#39;{.items[*].spec.containers[*].name}{&#34;\n&#34;}&#39;
 </code></pre><p>Output:</p>
-<pre><code>app-ui istio-proxy
+<pre tabindex="0"><code>app-ui istio-proxy
 </code></pre><br>
 <h2 id="access-application">Access Application</h2>
 <p>The application is deployed!  But you need a way to access the application via the user interface.</p>
@@ -402,20 +402,20 @@ <h2 id="access-application">Access Application</h2>
 <i class="fa fa-terminal"></i>
 Create the gateway configuration and routing rules:
 </blockquote>
-<pre><code>oc process -f ./istio-configuration/ingress-gateway.yaml \
+<pre tabindex="0"><code>oc process -f ./istio-configuration/ingress-gateway.yaml \
   -p INGRESS_GATEWAY_NAME=demogateway-$PROJECT_NAME | oc create -f -
 </code></pre><p>To access the application, you need the endpoint of your load balancer.</p>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Retrieve the URL of the load balancer:
 </blockquote>
-<pre><code>GATEWAY_URL=$(oc get route istio-demogateway-$(oc project -q) --template='http://{{.spec.host}}')
+<pre tabindex="0"><code>GATEWAY_URL=$(oc get route istio-demogateway-$(oc project -q) --template=&#39;http://{{.spec.host}}&#39;)
 echo $GATEWAY_URL
 </code></pre><blockquote>
 <i class="fa fa-desktop"></i>
 Navigate to this URL in the browser:
 </blockquote>
-<pre><code>http://istio-demogateway-user<span class="userid">X</span>-user<span class="userid">X</span>.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443
+<pre tabindex="0"><code>http://istio-demogateway-user<span class="userid">X</span>-user<span class="userid">X</span>.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:6443
 </code></pre><br>
 <p>You should see the application user interface.  Try creating a new board and posting to the shared board.</p>
 <p>For example:</p>
@@ -528,7 +528,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -788,7 +788,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -900,7 +900,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -910,7 +910,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -993,7 +993,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/index.html b/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/index.html
index a7d3046d6..64e62a2ea 100644
--- a/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab2.1_userprofile/index.html
@@ -335,9 +335,9 @@ <h2 id="application-code">Application Code</h2>
 <i class="fa fa-desktop"></i>
 Navigate to the 'UserProfile' class in your browser:
 </blockquote>
-<pre><code>https://github.com/RedHatGov/openshift-microservices/blob/workshop-stable/code/userprofile/src/main/java/org/microservices/demo/json/UserProfile.java
+<pre tabindex="0"><code>https://github.com/RedHatGov/openshift-microservices/blob/workshop-stable/code/userprofile/src/main/java/org/microservices/demo/json/UserProfile.java
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
     }
     public UserProfile(String id, String firstname, String lastname, String aboutme) {
         this.id = id;
@@ -354,9 +354,9 @@ <h2 id="application-code">Application Code</h2>
 <i class="fa fa-terminal"></i>
 Navigate to the 'UserProfileService' interface in your browser:
 </blockquote>
-<pre><code>https://github.com/RedHatGov/openshift-microservices/blob/workshop-stable/code/userprofile/src/main/java/org/microservices/demo/service/UserProfileService.java
+<pre tabindex="0"><code>https://github.com/RedHatGov/openshift-microservices/blob/workshop-stable/code/userprofile/src/main/java/org/microservices/demo/service/UserProfileService.java
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
     /**
      * return a specific profile
      * @param id
@@ -373,9 +373,9 @@ <h2 id="build-application">Build Application</h2>
 <i class="fa fa-terminal"></i>
 Verify the base image used to build the application:
 </blockquote>
-<pre><code>cat ./openshift-configuration/userprofile-build.yaml | grep -A 4 sourceStrategy
+<pre tabindex="0"><code>cat ./openshift-configuration/userprofile-build.yaml | grep -A 4 sourceStrategy
 </code></pre><p>Output (snippet):</p>
-<pre><code>      sourceStrategy:
+<pre tabindex="0"><code>      sourceStrategy:
         from:
           kind: ImageStreamTag
           name: java:11
@@ -386,7 +386,7 @@ <h2 id="build-application">Build Application</h2>
 <i class="fa fa-terminal"></i>
 Create the build:
 </blockquote>
-<pre><code>oc new-app -f ./openshift-configuration/userprofile-build.yaml \
+<pre tabindex="0"><code>oc new-app -f ./openshift-configuration/userprofile-build.yaml \
   -p APPLICATION_NAME=userprofile \
   -p APPLICATION_CODE_URI=https://github.com/RedHatGov/openshift-microservices.git \
   -p APPLICATION_CODE_BRANCH=workshop-stable \
@@ -395,15 +395,15 @@ <h2 id="build-application">Build Application</h2>
 <i class="fa fa-terminal"></i>
 Start the build:
 </blockquote>
-<pre><code>oc start-build userprofile-1.0
+<pre tabindex="0"><code>oc start-build userprofile-1.0
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Follow the build:
 </blockquote>
-<pre><code>oc logs -f bc/userprofile-1.0
+<pre tabindex="0"><code>oc logs -f bc/userprofile-1.0
 </code></pre><p>The builder will compile the source code and use the base image to create your deployable image artifact.  You should eventually see a successful build.</p>
 <p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 [INFO] ------------------------------------------------------------------------
 [INFO] BUILD SUCCESS
 [INFO] ------------------------------------------------------------------------
@@ -417,9 +417,9 @@ <h2 id="build-application">Build Application</h2>
 <i class="fa fa-terminal"></i>
 Verify the image was created:
 </blockquote>
-<pre><code>oc get is userprofile
+<pre tabindex="0"><code>oc get is userprofile
 </code></pre><p>Output:</p>
-<pre><code>NAME          IMAGE REPOSITORY                                                                  TAGS     UPDATED
+<pre tabindex="0"><code>NAME          IMAGE REPOSITORY                                                                  TAGS     UPDATED
 userprofile   image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile   1.0   3 minutes ago
 </code></pre><style>
 
@@ -520,7 +520,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -780,7 +780,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -892,7 +892,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -902,7 +902,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -985,7 +985,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/index.html b/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/index.html
index bef3312f8..578bc50b1 100644
--- a/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab2.2_deployuserprofile/index.html
@@ -325,13 +325,13 @@ <h2 id="deploy-application">Deploy Application</h2>
 <i class="fa fa-terminal"></i>
 Verify the annotation in the 'userprofile' file:
 </blockquote>
-<pre><code>cat ./openshift-configuration/userprofile-deploy-all.yaml | grep -B 1 sidecar.istio.io/inject
+<pre tabindex="0"><code>cat ./openshift-configuration/userprofile-deploy-all.yaml | grep -B 1 sidecar.istio.io/inject
 </code></pre><p>Output:</p>
-<pre><code>    annotations:
-      sidecar.istio.io/inject: &quot;true&quot;
+<pre tabindex="0"><code>    annotations:
+      sidecar.istio.io/inject: &#34;true&#34;
   --
     annotations:
-      sidecar.istio.io/inject: &quot;true&quot;
+      sidecar.istio.io/inject: &#34;true&#34;
 </code></pre><p>The annotation appears twice for the userprofile and PostgreSQL services.</p>
 <br>
 <p>Before deploying the service, you need a reference to the local image you built in the previous lab.</p>
@@ -339,35 +339,35 @@ <h2 id="deploy-application">Deploy Application</h2>
 <i class="fa fa-terminal"></i>
 Run the following commands:
 </blockquote>
-<pre><code>USER_PROFILE_IMAGE_URI=$(oc get is userprofile --template='{{.status.dockerImageRepository}}')
+<pre tabindex="0"><code>USER_PROFILE_IMAGE_URI=$(oc get is userprofile --template=&#39;{{.status.dockerImageRepository}}&#39;)
 echo $USER_PROFILE_IMAGE_URI
 </code></pre><p>Output (sample):</p>
-<pre><code>image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile
+<pre tabindex="0"><code>image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Deploy the service using this image URI:
 </blockquote>
-<pre><code>sed &quot;s|%USER_PROFILE_IMAGE_URI%|$USER_PROFILE_IMAGE_URI|&quot; ./openshift-configuration/userprofile-deploy-all.yaml | oc create -f -
+<pre tabindex="0"><code>sed &#34;s|%USER_PROFILE_IMAGE_URI%|$USER_PROFILE_IMAGE_URI|&#34; ./openshift-configuration/userprofile-deploy-all.yaml | oc create -f -
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Watch the deployment of the user profile:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=userprofile --watch
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=userprofile --watch
 </code></pre><p>
 <i class="fa fa-info-circle"></i>
 The userprofile service may error and restart if the PostgreSQL pod is not running yet.
 </p>
 <p>Output:</p>
-<pre><code>userprofile-xxxxxxxxxx-xxxxx              2/2     Running		    0          2m55s
+<pre tabindex="0"><code>userprofile-xxxxxxxxxx-xxxxx              2/2     Running		    0          2m55s
 </code></pre><br>
 <p>Similar to the other microservices, the user profile service runs the application and the Istio proxy.</p>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Print the containers in the 'userprofile' pod:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=userprofile -o jsonpath='{.items[*].spec.containers[*].name}{&quot;\n&quot;}'
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=userprofile -o jsonpath=&#39;{.items[*].spec.containers[*].name}{&#34;\n&#34;}&#39;
 </code></pre><p>Output:</p>
-<pre><code>userprofile istio-proxy
+<pre tabindex="0"><code>userprofile istio-proxy
 </code></pre><br>
 <h2 id="access-application">Access Application</h2>
 <p>The user profile service is deployed!  Let&rsquo;s test this in the browser.</p>
@@ -480,7 +480,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -740,7 +740,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -852,7 +852,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -862,7 +862,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -945,7 +945,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/index.html b/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/index.html
index e0abb5053..84b7b3ac7 100644
--- a/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab2.3_kiali/index.html
@@ -326,21 +326,21 @@ <h2 id="explore-kiali">Explore Kiali</h2>
 <i class="fa fa-terminal"></i>
 Send load to the application user interface:
 </blockquote>
-<pre><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL; done
+<pre tabindex="0"><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL; done
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Send load to the user profile service:
 </blockquote>
-<pre><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Now let's open the Kiali console.  Retrieve the endpoint for Kiali:
 </blockquote>
-<pre><code>KIALI_CONSOLE=$(oc get route kiali -n istio-system --template='https://{{.spec.host}}')
+<pre tabindex="0"><code>KIALI_CONSOLE=$(oc get route kiali -n istio-system --template=&#39;https://{{.spec.host}}&#39;)
 echo $KIALI_CONSOLE
 </code></pre><p>Output:</p>
-<pre><code>https://kiali-istio-system.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/
+<pre tabindex="0"><code>https://kiali-istio-system.apps.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>/
 </code></pre><br>
 <blockquote>
 <i class="fa fa-desktop"></i>
@@ -495,7 +495,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -755,7 +755,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -867,7 +867,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -877,7 +877,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -960,7 +960,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/index.html b/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/index.html
index 79a72dbce..38aafda0c 100644
--- a/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab3.1_featureupdate/index.html
@@ -325,7 +325,7 @@ <h2 id="feature-update">Feature Update</h2>
 <i class="fa fa-terminal"></i>
 Create a new build on this feature branch:
 </blockquote>
-<pre><code>oc new-app -f ./openshift-configuration/userprofile-build.yaml \
+<pre tabindex="0"><code>oc new-app -f ./openshift-configuration/userprofile-build.yaml \
   -p APPLICATION_NAME=userprofile \
   -p APPLICATION_CODE_URI=https://github.com/RedHatGov/openshift-microservices.git \
   -p APPLICATION_CODE_BRANCH=workshop-feature-update \
@@ -336,15 +336,15 @@ <h2 id="feature-update">Feature Update</h2>
 <i class="fa fa-terminal"></i>
 Start the build:
 </blockquote>
-<pre><code>oc start-build userprofile-2.0
+<pre tabindex="0"><code>oc start-build userprofile-2.0
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Follow the build:
 </blockquote>
-<pre><code>oc logs -f bc/userprofile-2.0
+<pre tabindex="0"><code>oc logs -f bc/userprofile-2.0
 </code></pre><p>The builder will compile the source code and use the base image to create your deployable image artifact.  You should eventually see a successful build.</p>
 <p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 [INFO] [io.quarkus.deployment.pkg.steps.JarResultBuildStep] Building thin jar: /tmp/src/target/userprofile-1.0-SNAPSHOT-runner.jar
 [INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in 7988ms
 [INFO] ------------------------------------------------------------------------
@@ -359,9 +359,9 @@ <h2 id="feature-update">Feature Update</h2>
 <i class="fa fa-terminal"></i>
 Verify the image was created:
 </blockquote>
-<pre><code>oc describe is userprofile
+<pre tabindex="0"><code>oc describe is userprofile
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 2.0
   no spec tag
 
@@ -379,24 +379,24 @@ <h2 id="feature-update">Feature Update</h2>
 <i class="fa fa-terminal"></i>
 Grab a reference to the local image:
 </blockquote>
-<pre><code>USER_PROFILE_IMAGE_URI=$(oc get is userprofile --template='{{.status.dockerImageRepository}}')
+<pre tabindex="0"><code>USER_PROFILE_IMAGE_URI=$(oc get is userprofile --template=&#39;{{.status.dockerImageRepository}}&#39;)
 echo $USER_PROFILE_IMAGE_URI
 </code></pre><p>Output (sample):</p>
-<pre><code>image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile
+<pre tabindex="0"><code>image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile
 </code></pre><br>
 <p>The deployment file &lsquo;userprofile-deploy-v2.yaml&rsquo; was created for you to deploy the application.</p>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Deploy the service using the image URI:
 </blockquote>
-<pre><code>sed &quot;s|%USER_PROFILE_IMAGE_URI%|$USER_PROFILE_IMAGE_URI|&quot; ./openshift-configuration/userprofile-deploy-v2.yaml | oc create -f -
+<pre tabindex="0"><code>sed &#34;s|%USER_PROFILE_IMAGE_URI%|$USER_PROFILE_IMAGE_URI|&#34; ./openshift-configuration/userprofile-deploy-v2.yaml | oc create -f -
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Watch the deployment of the user profile:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=userprofile --watch
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=userprofile --watch
 </code></pre><p>Output:</p>
-<pre><code>userprofile-2-xxxxxxxxxx-xxxxx            2/2     Running        0          22s
+<pre tabindex="0"><code>userprofile-2-xxxxxxxxxx-xxxxx            2/2     Running        0          22s
 userprofile-xxxxxxxxxx-xxxxx              2/2     Running        0          2m55s
 </code></pre><br>
 <h2 id="access-application">Access Application</h2>
@@ -512,7 +512,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -772,7 +772,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -884,7 +884,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -894,7 +894,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -977,7 +977,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/index.html b/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/index.html
index fd4257182..139b983b1 100644
--- a/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab3.2_grafana/index.html
@@ -325,7 +325,7 @@ <h2 id="explore-grafana">Explore Grafana</h2>
 <i class="fa fa-terminal"></i>
 Open the Grafana console.  Retrieve the endpoint for Grafana:
 </blockquote>
-<pre><code>GRAFANA_CONSOLE=$(oc get route grafana -n istio-system --template='https://{{.spec.host}}')
+<pre tabindex="0"><code>GRAFANA_CONSOLE=$(oc get route grafana -n istio-system --template=&#39;https://{{.spec.host}}&#39;)
 echo $GRAFANA_CONSOLE
 </code></pre><p><i class="fa fa-info-circle"></i> Click 'Allow selected permissions' if prompted to authorized access.</p>
 <blockquote>
@@ -349,7 +349,7 @@ <h2 id="explore-grafana">Explore Grafana</h2>
 <i class="fa fa-terminal"></i>
 Send load to the application user interface:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL; done
 </code></pre><br>
 <p>While that is running, let&rsquo;s look at some dashboards.</p>
 <blockquote>
@@ -365,7 +365,7 @@ <h2 id="explore-grafana">Explore Grafana</h2>
 <i class="fa fa-terminal"></i>
 Send that terminal job to the background:
 </blockquote>
-<pre><code>^Z
+<pre tabindex="0"><code>^Z
 [1]+  Stopped                 curl -s -o /dev/null $GATEWAY_URL
 bg                                                     
 [1]+ curl -s -o /dev/null $GATEWAY_URL &amp;
@@ -373,7 +373,7 @@ <h2 id="explore-grafana">Explore Grafana</h2>
 <i class="fa fa-terminal"></i>
 Now, send load to the user profile service:
 </blockquote>
-<pre><code>GATEWAY_URL=$(oc get route istio-demogateway-$(oc project -q) --template='http://{{.spec.host}}')
+<pre tabindex="0"><code>GATEWAY_URL=$(oc get route istio-demogateway-$(oc project -q) --template=&#39;http://{{.spec.host}}&#39;)
 while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><p>The mesh dashboard should dynamically update.  It should look like this now:</p>
 <p><img src="../images/grafana-istio-mesh-updated.png" width="1024"><br/>
@@ -498,7 +498,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -758,7 +758,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -870,7 +870,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -880,7 +880,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -963,7 +963,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/index.html b/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/index.html
index 9ca19dabd..1821a89aa 100644
--- a/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab3.3_jaeger/index.html
@@ -325,7 +325,7 @@ <h2 id="explore-jaeger">Explore Jaeger</h2>
 <i class="fa fa-terminal"></i>
 Open the Jaeger console.  Retrieve the endpoint for Jaeger:
 </blockquote>
-<pre><code>JAEGER_CONSOLE=$(oc get route jaeger -n istio-system --template='https://{{.spec.host}}')
+<pre tabindex="0"><code>JAEGER_CONSOLE=$(oc get route jaeger -n istio-system --template=&#39;https://{{.spec.host}}&#39;)
 echo $JAEGER_CONSOLE
 </code></pre><p><i class="fa fa-info-circle"></i> Click 'Allow selected permissions' if prompted to authorized access.</p>
 <blockquote>
@@ -341,7 +341,7 @@ <h2 id="explore-jaeger">Explore Jaeger</h2>
 <i class="fa fa-terminal"></i>
 Send load to the application user interface:
 </blockquote>
-<pre><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL; done
+<pre tabindex="0"><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL; done
 </code></pre><br>
 Let's inspect the traces.  
 <blockquote>
@@ -382,12 +382,12 @@ <h2 id="explore-jaeger">Explore Jaeger</h2>
 <i class="fa fa-terminal"></i>
 Verify the app-ui pod IP:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=app-ui -o jsonpath='{.items[*].status.podIP}{&quot;\n&quot;}'
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=app-ui -o jsonpath=&#39;{.items[*].status.podIP}{&#34;\n&#34;}&#39;
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Verify the boards pod IP:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=boards -o jsonpath='{.items[*].status.podIP}{&quot;\n&quot;}'
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=boards -o jsonpath=&#39;{.items[*].status.podIP}{&#34;\n&#34;}&#39;
 </code></pre><p>The pod IPs should match to the process IPs in the spans you expanded.</p>
 <br>
 <h2 id="debug-user-profile">Debug User Profile</h2>
@@ -396,7 +396,7 @@ <h2 id="debug-user-profile">Debug User Profile</h2>
 <i class="fa fa-terminal"></i>
 Send load to the user profile service:
 </blockquote>
-<pre><code>for ((i=1;i&lt;=5;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>for ((i=1;i&lt;=5;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><p><i class="fa fa-info-circle"></i> Wait for this to complete as the profile service is slow.</p>
 <br>
 Inspect the traces.  
@@ -427,7 +427,7 @@ <h2 id="debug-user-profile">Debug User Profile</h2>
 <i class="fa fa-terminal"></i>
 Verify the userprofile-v1 pod IP:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=userprofile,version=1.0 -o jsonpath='{.items[*].status.podIP}{&quot;\n&quot;}'
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=userprofile,version=1.0 -o jsonpath=&#39;{.items[*].status.podIP}{&#34;\n&#34;}&#39;
 </code></pre><p>The pod IP should match to the process IP in the span you expanded.</p>
 <br>
 <blockquote>
@@ -443,7 +443,7 @@ <h2 id="debug-user-profile">Debug User Profile</h2>
 <i class="fa fa-terminal"></i>
 Verify the userprofile-v2 pod IP:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=userprofile,version=2.0 -o jsonpath='{.items[*].status.podIP}{&quot;\n&quot;}'
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=userprofile,version=2.0 -o jsonpath=&#39;{.items[*].status.podIP}{&#34;\n&#34;}&#39;
 </code></pre><p>The pod IP should match to the process IP in the span you expanded.</p>
 <br>
 <p>At this point, it is really clear that there is a performance issue directly in the version 2 source.  Although the example was simplistic, distributed tracing is incredibly helpful when you have a complicated network of service calls in your mesh.</p>
@@ -547,7 +547,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -807,7 +807,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -919,7 +919,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -929,7 +929,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1012,7 +1012,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/index.html b/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/index.html
index 17c86534c..070e97f06 100644
--- a/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab4.1_routingtraffic/index.html
@@ -327,9 +327,9 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 View the destination rules in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/destinationrules-all.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/destinationrules-all.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 apiVersion: networking.istio.io/v1alpha3
 kind: DestinationRule
 metadata:
@@ -355,9 +355,9 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 View the virtual services in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-services-all-v2.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-services-all-v2.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 ---
 apiVersion: networking.istio.io/v1alpha3
 kind: VirtualService
@@ -378,15 +378,15 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Let's deploy these routing rules:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/destinationrules-all.yaml 
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/destinationrules-all.yaml 
 oc apply -f ./istio-configuration/virtual-services-all-v2.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Verify the destination rules:
 </blockquote>
-<pre><code>oc get dr
+<pre tabindex="0"><code>oc get dr
 </code></pre><p>Output:</p>
-<pre><code>NAME                     HOST                     AGE
+<pre tabindex="0"><code>NAME                     HOST                     AGE
 app-ui                   app-ui                   24m
 boards                   boards                   24m
 boards-mongodb           boards-mongodb           24m
@@ -396,9 +396,9 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Verify the virtual services:
 </blockquote>
-<pre><code>oc get vs
+<pre tabindex="0"><code>oc get vs
 </code></pre><p>Output (sample):</p>
-<pre><code>NAME                     GATEWAYS                       HOSTS                      AGE
+<pre tabindex="0"><code>NAME                     GATEWAYS                       HOSTS                      AGE
 app-ui                                                  [app-ui]                   25m
 boards                                                  [boards]                   25m
 boards-mongodb                                          [boards-mongodb]           25m
@@ -420,7 +420,7 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Send load to the user profile service:
 </blockquote>
-<pre><code>for ((i=1;i&lt;=5;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>for ((i=1;i&lt;=5;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <blockquote>
 <i class="fa fa-desktop"></i>
@@ -444,9 +444,9 @@ <h2 id="change-traffic-routing">Change Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 View the modified virtual service in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-service-userprofile-v1.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-service-userprofile-v1.yaml
 </code></pre><p>Output:</p>
-<pre><code>apiVersion: networking.istio.io/v1alpha3
+<pre tabindex="0"><code>apiVersion: networking.istio.io/v1alpha3
 kind: VirtualService
 metadata:
   name: userprofile
@@ -463,14 +463,14 @@ <h2 id="change-traffic-routing">Change Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Deploy the change:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-v1.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-v1.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Verify the change:
 </blockquote>
-<pre><code>oc describe vs userprofile
+<pre tabindex="0"><code>oc describe vs userprofile
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 Spec:
   Hosts:
     userprofile
@@ -491,7 +491,7 @@ <h2 id="change-traffic-routing">Change Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Let's send 100 user profile requests to generate traffic
 </blockquote>
-<pre><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>for ((i=1;i&lt;=100;i++)); do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><blockquote>
 <i class="fa fa-desktop"></i>
 Now in Kiali, navigate to 'Graph' in the left navigation bar.
@@ -612,7 +612,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -872,7 +872,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -984,7 +984,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -994,7 +994,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1077,7 +1077,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/index.html b/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/index.html
index 6d0206900..863af2674 100644
--- a/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab4.2_trafficsplitting/index.html
@@ -325,7 +325,7 @@ <h2 id="feature-fix">Feature Fix</h2>
 <i class="fa fa-terminal"></i>
 Create a new build on this feature branch:
 </blockquote>
-<pre><code>oc new-app -f ./openshift-configuration/userprofile-build.yaml \
+<pre tabindex="0"><code>oc new-app -f ./openshift-configuration/userprofile-build.yaml \
   -p APPLICATION_NAME=userprofile \
   -p APPLICATION_CODE_URI=https://github.com/RedHatGov/openshift-microservices.git \
   -p APPLICATION_CODE_BRANCH=workshop-feature-fix \
@@ -335,15 +335,15 @@ <h2 id="feature-fix">Feature Fix</h2>
 <i class="fa fa-terminal"></i>
 Start the build:
 </blockquote>
-<pre><code>oc start-build userprofile-3.0
+<pre tabindex="0"><code>oc start-build userprofile-3.0
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Follow the build:
 </blockquote>
-<pre><code>oc logs -f bc/userprofile-3.0
+<pre tabindex="0"><code>oc logs -f bc/userprofile-3.0
 </code></pre><p>The builder will compile the source code and use the base image to create your deployable image artifact.  You should eventually see a successful build.</p>
 <p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 [INFO] [io.quarkus.deployment.pkg.steps.JarResultBuildStep] Building thin jar: /tmp/src/target/userprofile-1.0-SNAPSHOT-runner.jar
 [INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in 7988ms
 [INFO] ------------------------------------------------------------------------
@@ -357,9 +357,9 @@ <h2 id="feature-fix">Feature Fix</h2>
 <i class="fa fa-terminal"></i>
 Verify the image was created:
 </blockquote>
-<pre><code>oc describe is userprofile
+<pre tabindex="0"><code>oc describe is userprofile
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 
 3.0
   no spec tag
@@ -378,23 +378,23 @@ <h2 id="feature-fix">Feature Fix</h2>
 <i class="fa fa-terminal"></i>
 Grab a reference to the local image:
 </blockquote>
-<pre><code>USER_PROFILE_IMAGE_URI=$(oc get is userprofile --template='{{.status.dockerImageRepository}}')
+<pre tabindex="0"><code>USER_PROFILE_IMAGE_URI=$(oc get is userprofile --template=&#39;{{.status.dockerImageRepository}}&#39;)
 echo $USER_PROFILE_IMAGE_URI
 </code></pre><p>Output (sample):</p>
-<pre><code>image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile
+<pre tabindex="0"><code>image-registry.openshift-image-registry.svc:5000/microservices-demo/userprofile
 </code></pre><p>The deployment file &lsquo;userprofile-deploy-v3.yaml&rsquo; was created for you to deploy the application.</p>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Deploy the service using the image URI:
 </blockquote>
-<pre><code>sed &quot;s|%USER_PROFILE_IMAGE_URI%|$USER_PROFILE_IMAGE_URI|&quot; ./openshift-configuration/userprofile-deploy-v3.yaml | oc create -f -
+<pre tabindex="0"><code>sed &#34;s|%USER_PROFILE_IMAGE_URI%|$USER_PROFILE_IMAGE_URI|&#34; ./openshift-configuration/userprofile-deploy-v3.yaml | oc create -f -
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Watch the deployment of the user profile:
 </blockquote>
-<pre><code>oc get pods -l deploymentconfig=userprofile --watch
+<pre tabindex="0"><code>oc get pods -l deploymentconfig=userprofile --watch
 </code></pre><p>Output:</p>
-<pre><code>userprofile-3-xxxxxxxxxx-xxxxx              2/2     Running        0          53s
+<pre tabindex="0"><code>userprofile-3-xxxxxxxxxx-xxxxx              2/2     Running        0          53s
 userprofile-2-xxxxxxxxxx-xxxxx              2/2     Running        0          13m
 userprofile-xxxxxxxxxx-xxxxx                2/2     Running        0          22h
 </code></pre><br>
@@ -404,9 +404,9 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 View the virtual service in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-service-userprofile-90-10.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-service-userprofile-90-10.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 ---
   http:
   - route:
@@ -425,12 +425,12 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Deploy the routing rule:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-90-10.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-90-10.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 If you aren't already (from the Grafana lab) - send load continuously to the user profile service:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <p>Inspect the change in Kiali.</p>
 <blockquote>
@@ -456,9 +456,9 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 View the virtual service in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-service-userprofile-50-50.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-service-userprofile-50-50.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 ---
   http:
   - route:
@@ -477,12 +477,12 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Deploy the routing rule:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-50-50.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-50-50.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 If you aren't already - send load to the user profile service:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <p>Inspect the change again in Kiali.</p>
 <blockquote>
@@ -502,9 +502,9 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 View the virtual service in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-service-userprofile-v3.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-service-userprofile-v3.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
 ---
   http:
   - route:
@@ -517,12 +517,12 @@ <h2 id="traffic-routing">Traffic Routing</h2>
 <i class="fa fa-terminal"></i>
 Deploy the routing rule:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-v3.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-v3.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 If you aren't already - Send load to the user profile service:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <p>Inspect the change again in Kiali.</p>
 <blockquote>
@@ -655,7 +655,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -915,7 +915,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1027,7 +1027,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1037,7 +1037,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1120,7 +1120,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/index.html b/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/index.html
index 804f8c21a..84450de2d 100644
--- a/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab4.3_faultinjection/index.html
@@ -326,9 +326,9 @@ <h2 id="abort-faults">Abort Faults</h2>
 <i class="fa fa-terminal"></i>
 View the virtual service in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-service-userprofile-503.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-service-userprofile-503.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
   http:
   - fault:
       abort:
@@ -344,12 +344,12 @@ <h2 id="abort-faults">Abort Faults</h2>
 <i class="fa fa-terminal"></i>
 Deploy the routing rule:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-503.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-503.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 If you aren't already (from previous labs) - Send load to the user profile service:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <p>Inspect the change in Kiali.</p>
 <blockquote>
@@ -393,9 +393,9 @@ <h2 id="delay-faults">Delay Faults</h2>
 <i class="fa fa-terminal"></i>
 View the virtual service in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/virtual-service-userprofile-delay.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/virtual-service-userprofile-delay.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
   http:
   - fault:
       delay:
@@ -411,12 +411,12 @@ <h2 id="delay-faults">Delay Faults</h2>
 <i class="fa fa-terminal"></i>
 Deploy the routing rule:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-delay.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-delay.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 If you aren't already - Send load to the user profile service:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><br>
 <blockquote>
 <i class="fa fa-desktop"></i>
@@ -437,7 +437,7 @@ <h2 id="clean-up">Clean up</h2>
 <i class="fa fa-terminal"></i>
 Revert the changes you made before ending this lab.
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-v3.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-v3.yaml
 </code></pre><br>
 <h2 id="summary">Summary</h2>
 <p>Congratulations, you configured fault injection with Istio!</p>
@@ -547,7 +547,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -807,7 +807,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -919,7 +919,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -929,7 +929,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1012,7 +1012,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/index.html b/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/index.html
index 537069479..4862f9d29 100644
--- a/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab4.4_circuitbreaking/index.html
@@ -328,9 +328,9 @@ <h2 id="define-threshold-limits">Define Threshold Limits</h2>
 <i class="fa fa-terminal"></i>
 View the destination rule in your favorite editor or via bash:
 </blockquote>
-<pre><code>cat ./istio-configuration/destinationrule-circuitbreaking.yaml
+<pre tabindex="0"><code>cat ./istio-configuration/destinationrule-circuitbreaking.yaml
 </code></pre><p>Output (snippet):</p>
-<pre><code>...
+<pre tabindex="0"><code>...
   trafficPolicy:
     tls:
       mode: ISTIO_MUTUAL
@@ -349,24 +349,24 @@ <h2 id="define-threshold-limits">Define Threshold Limits</h2>
 <i class="fa fa-terminal"></i>
 Deploy this circuit breaking rule:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/destinationrule-circuitbreaking.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/destinationrule-circuitbreaking.yaml
 </code></pre><br>
 <h2 id="trip-the-circuit-breaker">Trip the Circuit Breaker</h2>
 <blockquote>
 <i class="fa fa-terminal"></i>
 First, route traffic evenly between v1 and v3 of the user profile service.
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/virtual-service-userprofile-50-50.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/virtual-service-userprofile-50-50.yaml
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Send load to the user profile service:
 </blockquote>
-<pre><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
+<pre tabindex="0"><code>while true; do curl -s -o /dev/null $GATEWAY_URL/profile; done
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 In another tab in terminal, kill the server running version 3 of the user profile service:
 </blockquote>
-<pre><code>USERPROFILE_POD=$(oc get pod -l deploymentconfig=userprofile,version=3.0 -o jsonpath='{.items[0].metadata.name}')
+<pre tabindex="0"><code>USERPROFILE_POD=$(oc get pod -l deploymentconfig=userprofile,version=3.0 -o jsonpath=&#39;{.items[0].metadata.name}&#39;)
 oc exec $USERPROFILE_POD -- kill 1
 </code></pre><br>
 <p>Inspect the change in Kiali.</p>
@@ -390,7 +390,7 @@ <h2 id="clean-up">Clean up</h2>
 <i class="fa fa-terminal"></i>
 Revert the changes you made before ending this lab.
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/destinationrules-all.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/destinationrules-all.yaml
 </code></pre><br>
 <h2 id="summary">Summary</h2>
 <p>Congratulations, you configured circuit breaking in Istio!</p>
@@ -498,7 +498,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -758,7 +758,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -870,7 +870,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -880,7 +880,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -963,7 +963,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/index.html b/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/index.html
index 071396e77..990f4534a 100644
--- a/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab5.1_intromtls/index.html
@@ -326,28 +326,28 @@ <h2 id="current-state-of-no-encryption">Current State of No Encryption</h2>
 <blockquote>
 <i class="fa fa-terminal"></i> let's launch a job using the CLI with to show that:
 </blockquote>
-<pre><code>oc run curl-boards-1 -i --restart=Never --image=appropriate/curl --timeout=10s -- boards:8080/shareditems
+<pre tabindex="0"><code>oc run curl-boards-1 -i --restart=Never --image=appropriate/curl --timeout=10s -- boards:8080/shareditems
 </code></pre><p>This job executes a direct HTTP curl request for the current shared boards list. It&rsquo;ll print out something similar to this:</p>
-<pre><code>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+<pre tabindex="0"><code>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed
   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0[
   {
-    &quot;_id&quot;: &quot;5e5d75b33396fe0043f63e5c&quot;,
-    &quot;owner&quot;: &quot;anonymous&quot;,
-    &quot;type&quot;: &quot;string&quot;,
-    &quot;raw&quot;: &quot;something goes here&quot;,
-    &quot;name&quot;: &quot;&quot;,
-    &quot;id&quot;: &quot;MNCkr3mK&quot;,
-    &quot;created_at&quot;: &quot;2020-03-02T21:08:03+00:00&quot;
+    &#34;_id&#34;: &#34;5e5d75b33396fe0043f63e5c&#34;,
+    &#34;owner&#34;: &#34;anonymous&#34;,
+    &#34;type&#34;: &#34;string&#34;,
+    &#34;raw&#34;: &#34;something goes here&#34;,
+    &#34;name&#34;: &#34;&#34;,
+    &#34;id&#34;: &#34;MNCkr3mK&#34;,
+    &#34;created_at&#34;: &#34;2020-03-02T21:08:03+00:00&#34;
   },
   {
-    &quot;_id&quot;: &quot;5e5d75b63396fe0043f63e5d&quot;,
-    &quot;owner&quot;: &quot;anonymous&quot;,
-    &quot;type&quot;: &quot;string&quot;,
-    &quot;raw&quot;: &quot;another item&quot;,
-    &quot;name&quot;: &quot;&quot;,
-    &quot;id&quot;: &quot;x5ORoJu8&quot;,
-    &quot;created_at&quot;: &quot;2020-03-02T21:08:06+00:00&quot;
+    &#34;_id&#34;: &#34;5e5d75b63396fe0043f63e5d&#34;,
+    &#34;owner&#34;: &#34;anonymous&#34;,
+    &#34;type&#34;: &#34;string&#34;,
+    &#34;raw&#34;: &#34;another item&#34;,
+    &#34;name&#34;: &#34;&#34;,
+    &#34;id&#34;: &#34;x5ORoJu8&#34;,
+    &#34;created_at&#34;: &#34;2020-03-02T21:08:06+00:00&#34;
   }
 100   423  100   423    0     0  23500      0 --:--:-- --:--:-- --:--:-- 23500
 ]
@@ -359,11 +359,11 @@ <h2 id="adding-mtls-to-our-existing-services">Adding mTLS to Our Existing Servic
 Service mesh allows setting policy at the individual service, namespace, and entire mesh levels (applied/enforced in that order)
 </p>
 <p>We already wrote the YAML config to do this. It looks like this:</p>
-<pre><code>apiVersion: authentication.istio.io/v1alpha1
+<pre tabindex="0"><code>apiVersion: authentication.istio.io/v1alpha1
 kind: Policy
 metadata:
-  name: &quot;default&quot;
-  namespace: &quot;microservices-demo&quot;
+  name: &#34;default&#34;
+  namespace: &#34;microservices-demo&#34;
 spec:
   peers:
   - mtls:
@@ -376,13 +376,13 @@ <h2 id="adding-mtls-to-our-existing-services">Adding mTLS to Our Existing Servic
 ```
 <br>
 <p>Now we also need to set DestinationRules for each service so that our sidecars know to use mTLS when communicating with each other. The YAML for that looks like this - note the use of a wildcard:</p>
-<pre><code>apiVersion: &quot;networking.istio.io/v1alpha3&quot;
-kind: &quot;DestinationRule&quot;
+<pre tabindex="0"><code>apiVersion: &#34;networking.istio.io/v1alpha3&#34;
+kind: &#34;DestinationRule&#34;
 metadata:
-  name: &quot;destinationrule-mtls-istio-mutual&quot;
-  namespace: &quot;microservices-demo&quot;
+  name: &#34;destinationrule-mtls-istio-mutual&#34;
+  namespace: &#34;microservices-demo&#34;
 spec:
-  host: &quot;*.microservices-demo.svc.cluster.local&quot;
+  host: &#34;*.microservices-demo.svc.cluster.local&#34;
   trafficPolicy:
     tls:
       mode: ISTIO_MUTUAL
@@ -508,7 +508,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -768,7 +768,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -880,7 +880,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -890,7 +890,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -973,7 +973,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/index.html b/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/index.html
index 9e2af6401..d981e7b8e 100644
--- a/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab5.2_verifymtls/index.html
@@ -341,9 +341,9 @@ <h1 id="checking-and-verification-of-mtls">Checking and Verification of mTLS</h1
 <i class="fa fa-terminal"></i>
 OK, let's try to run that same command again to snoop on traffic. Run the following:
 </blockquote>
-<pre><code>oc run curl-boards-2 -i --restart=Never --image=appropriate/curl --timeout=10s -- boards:8080/shareditems
+<pre tabindex="0"><code>oc run curl-boards-2 -i --restart=Never --image=appropriate/curl --timeout=10s -- boards:8080/shareditems
 </code></pre><p>You should get an output indicating that the job failed to pull data. This is because the traffic didn&rsquo;t come from a verifiable service known to the mesh and wasn&rsquo;t able to do a secure mTLS token handshake. Your output should look like this:</p>
-<pre><code>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+<pre tabindex="0"><code>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed
   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 curl: (56) Recv failure: Connection reset by peer
@@ -354,7 +354,7 @@ <h1 id="checking-and-verification-of-mtls">Checking and Verification of mTLS</h1
 <i class="fa fa-terminal"></i>
 Type the following in the CLI
 </blockquote>
-<pre><code>oc delete policy/default
+<pre tabindex="0"><code>oc delete policy/default
 oc delete dr --all
 </code></pre><h2 id="more-about-mtls-options">More About mTLS Options</h2>
 <p>mTLS in the service mesh isn&rsquo;t <em>just</em> an ON/OFF capability. We kept it basic for the lab, but you could have easily chosen specific services to enforce it on. PERMISSIVE mode is especially useful in a scenario where want to migrate your existing services’ traffic from plain text to mTLS. It allows a service to accept both plaintext traffic and mutual TLS traffic at the same time (without breaking live traffic).</p>
@@ -481,7 +481,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -741,7 +741,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -853,7 +853,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -863,7 +863,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -946,7 +946,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab5.3_prep/index.html b/workshops/openshift_service_mesh_v1.0/lab5.3_prep/index.html
index 6d6686a84..e5b4939a6 100644
--- a/workshops/openshift_service_mesh_v1.0/lab5.3_prep/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab5.3_prep/index.html
@@ -329,13 +329,13 @@ <h3 id="create-an-instance-of-sso--configuration">Create an Instance of SSO / Co
 <blockquote>
 <i class="fa fa-terminal"></i> We create a Keycloak instance using a Kubernetes resource:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/sso-keycloak.yaml
-</code></pre><pre><code>oc patch cm/keycloak-probes -p '{&quot;data&quot;:{&quot;liveness_probe.sh&quot;:&quot;#!/bin/bash\necho pass\n&quot;,&quot;readiness_probe.sh&quot;:&quot;#!/bin/bash\necho pass\n&quot;}}'
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/sso-keycloak.yaml
+</code></pre><pre tabindex="0"><code>oc patch cm/keycloak-probes -p &#39;{&#34;data&#34;:{&#34;liveness_probe.sh&#34;:&#34;#!/bin/bash\necho pass\n&#34;,&#34;readiness_probe.sh&#34;:&#34;#!/bin/bash\necho pass\n&#34;}}&#39;
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i> Watch the pods for keycloak-0 to become READY 1/1:
 </blockquote>
-<pre><code>oc get pods keycloak-0 -w
-</code></pre><pre><code>NAME                                       READY   STATUS      RESTARTS   AGE
+<pre tabindex="0"><code>oc get pods keycloak-0 -w
+</code></pre><pre tabindex="0"><code>NAME                                       READY   STATUS      RESTARTS   AGE
 keycloak-0                                 0/1     Pending       0          0s
 keycloak-0                                 0/1     Init:0/1      0          0s
 keycloak-0                                 0/1     Init:0/1      0          3s
@@ -346,15 +346,15 @@ <h3 id="create-an-instance-of-sso--configuration">Create an Instance of SSO / Co
 <blockquote>
 <i class="fa fa-terminal"></i> We configure via Kubernetes resources to create the realm + roles + clients & users as follows:
 </blockquote>
-<pre><code>sed &quot;s|http://istio-ingressgateway-istio-system.apps.cluster.domain.com|$GATEWAY_URL|&quot; ./istio-configuration/sso-realm.yaml | oc create -f -
-</code></pre><pre><code>oc apply -f ./istio-configuration/sso-user1.yaml
-</code></pre><pre><code>oc apply -f ./istio-configuration/sso-user2.yaml
+<pre tabindex="0"><code>sed &#34;s|http://istio-ingressgateway-istio-system.apps.cluster.domain.com|$GATEWAY_URL|&#34; ./istio-configuration/sso-realm.yaml | oc create -f -
+</code></pre><pre tabindex="0"><code>oc apply -f ./istio-configuration/sso-user1.yaml
+</code></pre><pre tabindex="0"><code>oc apply -f ./istio-configuration/sso-user2.yaml
 </code></pre><h3 id="login-to-the-sso-admin-console">Login to the SSO Admin Console</h3>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Open the SSO console.  Retrieve the endpoint:
 </blockquote>
-<pre><code>SSO_CONSOLE=$(oc get route keycloak --template='https://{{.spec.host}}')
+<pre tabindex="0"><code>SSO_CONSOLE=$(oc get route keycloak --template=&#39;https://{{.spec.host}}&#39;)
 echo $SSO_CONSOLE
 </code></pre><p>
 <i class="fa fa-info-circle"></i>
@@ -408,23 +408,23 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse3836b71e2e83af3c1da26fd3f75383ce" class="collapsed">
+      <a data-toggle="collapse" href="#collapse1bf4ec1265580338b7ab4d12d5a6e56b" class="collapsed">
       
         Or you can get the secret with the CLI (click to expand)
       </a>
     </h4>
   </div>
   
-  <div id="collapse3836b71e2e83af3c1da26fd3f75383ce" class="panel-collapse collapse ">
+  <div id="collapse1bf4ec1265580338b7ab4d12d5a6e56b" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <blockquote>
 <i class="fa fa-terminal"></i>
 Run the following to print the secret out:
 </blockquote>
-<pre><code>oc get secret/credential-workshop-keycloak -o yaml
+<pre tabindex="0"><code>oc get secret/credential-workshop-keycloak -o yaml
 </code></pre><p>You&rsquo;ll see something like:</p>
-<pre><code>apiVersion: v1
+<pre tabindex="0"><code>apiVersion: v1
 data:
   ADMIN_PASSWORD: SVZuM0pZQmNCeGl3bGc9PQ==
   ADMIN_USERNAME: YWRtaW4=
@@ -436,7 +436,7 @@ <h4 class="panel-title">
 <i class="fa fa-terminal"></i>
 Decode the characters by running (replace your copy):
 </blockquote>
-<pre><code>echo &lt;PASTE_YOUR_DATA_HERE&gt; | base64 -d
+<pre tabindex="0"><code>echo &lt;PASTE_YOUR_DATA_HERE&gt; | base64 -d
 </code></pre><blockquote>
 <i class="fa fa-terminal"></i>
 Copy the password decoded
@@ -518,8 +518,8 @@ <h2 id="tell-the-app-ui-to-use-this-sso-service">Tell the APP UI to use this SSO
 <i class="fa fa-terminal"></i>
 Type the following in the CLI:
 </blockquote>
-<pre><code>oc create route reencrypt keycloak-alt --service=keycloak 
-</code></pre><pre><code>SSO_SVC=$(oc get route keycloak-alt --template='{{.spec.host}}')
+<pre tabindex="0"><code>oc create route reencrypt keycloak-alt --service=keycloak 
+</code></pre><pre tabindex="0"><code>SSO_SVC=$(oc get route keycloak-alt --template=&#39;{{.spec.host}}&#39;)
 oc set env dc/app-ui FAKE_USER=false SSO_SVC_HOST=$SSO_SVC
 </code></pre><br/>
 <h2 id="access-info--api-documentation">Access Info / API documentation</h2>
@@ -633,7 +633,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -893,7 +893,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1005,7 +1005,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1015,7 +1015,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1098,7 +1098,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/index.html b/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/index.html
index 44898628a..a723e66b5 100644
--- a/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab5.4_authpolicy/index.html
@@ -325,10 +325,10 @@ <h2 id="authenticated-users-only">Authenticated Users Only</h2>
 <blockquote>
 <i class="fa fa-terminal"></i> Apply a new authentication policy and service entry with the following commands:
 </blockquote>
-<pre><code> sed &quot;s|keycloak-sso-shared.apps.cluster.domain.com|$SSO_SVC|&quot; ./istio-configuration/policy-boards-jwt.yaml | oc apply -f -
- sed &quot;s|keycloak-sso-shared.apps.cluster.domain.com|$SSO_SVC|&quot; ./istio-configuration/serviceentry-keycloak.yaml | oc apply -f -
+<pre tabindex="0"><code> sed &#34;s|keycloak-sso-shared.apps.cluster.domain.com|$SSO_SVC|&#34; ./istio-configuration/policy-boards-jwt.yaml | oc apply -f -
+ sed &#34;s|keycloak-sso-shared.apps.cluster.domain.com|$SSO_SVC|&#34; ./istio-configuration/serviceentry-keycloak.yaml | oc apply -f -
 </code></pre><p>The policy specifies the requirements for traffic to the boards service to have a JWT with specific properties. It looks like this:</p>
-<pre><code>apiVersion: authentication.istio.io/v1alpha1
+<pre tabindex="0"><code>apiVersion: authentication.istio.io/v1alpha1
 kind: Policy
 metadata:
   name: boards-jwt
@@ -337,8 +337,8 @@ <h2 id="authenticated-users-only">Authenticated Users Only</h2>
   - name: boards
   origins:
   - jwt:
-      issuer: &quot;https://keycloak-sso-shared.apps.leonardo.nub3s.io/auth/realms/microservices-demo&quot;
-      jwksUri: &quot;https://keycloak-sso-shared.apps.leonardo.nub3s.io/auth/realms/microservices-demo/protocol/openid-connect/certs&quot;
+      issuer: &#34;https://keycloak-sso-shared.apps.leonardo.nub3s.io/auth/realms/microservices-demo&#34;
+      jwksUri: &#34;https://keycloak-sso-shared.apps.leonardo.nub3s.io/auth/realms/microservices-demo/protocol/openid-connect/certs&#34;
       triggerRules:
       - excludedPaths:
         - exact: /health_check
@@ -380,9 +380,9 @@ <h2 id="only-the-cool-kids">Only The Cool Kids</h2>
 <blockquote>
 <i class="fa fa-terminal"></i> Apply an authorization policy with the following command:
 </blockquote>
-<pre><code>sed &quot;s|microservices-demo|$PROJECT_NAME|&quot; ./istio-configuration/authorization-boards-shared-lockdown.yaml | oc apply -f -
+<pre tabindex="0"><code>sed &#34;s|microservices-demo|$PROJECT_NAME|&#34; ./istio-configuration/authorization-boards-shared-lockdown.yaml | oc apply -f -
 </code></pre><p>That configuration looks like this:</p>
-<pre><code>apiVersion: security.istio.io/v1beta1
+<pre tabindex="0"><code>apiVersion: security.istio.io/v1beta1
 kind: AuthorizationPolicy
 metadata:
   name: boards-shared-lockdown
@@ -395,23 +395,23 @@ <h2 id="only-the-cool-kids">Only The Cool Kids</h2>
   rules:
   - from:
     - source:
-        requestPrincipals: [&quot;*&quot;]
+        requestPrincipals: [&#34;*&#34;]
     to:
     - operation:
-        methods: [&quot;POST&quot;]
-        paths: [&quot;*/shareditems&quot;]
+        methods: [&#34;POST&#34;]
+        paths: [&#34;*/shareditems&#34;]
     when:
     - key: request.auth.claims[realm_access_roles]
-      values: [&quot;cool-kids&quot;]
+      values: [&#34;cool-kids&#34;]
   - from:
     - source:
-        requestPrincipals: [&quot;*&quot;]
+        requestPrincipals: [&#34;*&#34;]
     to:
     - operation:
-        methods: [&quot;GET&quot;]
+        methods: [&#34;GET&#34;]
     when:
     - key: request.auth.claims[scope]
-      values: [&quot;openid&quot;]
+      values: [&#34;openid&#34;]
 </code></pre><p>An authorization policy includes a selector and a list of rules. The selector specifies the <strong>target</strong> that the policy applies to - in this case our boards microservice. While the rules specify <strong>who</strong> (from) is allowed to do <strong>what</strong> (to) under <strong>which</strong> (when) conditions - in this case any source can POST as long as they have the &ldquo;cool-kids&rdquo; role listed in their JWT payload.</p>
 <p>So, now that we&rsquo;ve applied it, let&rsquo;s try to access your boards service when you&rsquo;re not in the cool kids club.</p>
 <br>
@@ -436,10 +436,10 @@ <h2 id="only-the-cool-kids">Only The Cool Kids</h2>
 <blockquote>
 <i class="fa fa-terminal"></i> Now let's put things back to normal:
 </blockquote>
-<pre><code>oc delete authorizationpolicy/boards-shared-lockdown
-</code></pre><pre><code>oc delete policy/boards-jwt
-</code></pre><pre><code>oc delete serviceentry/keycloak-egress
-</code></pre><pre><code>SSO_SVC=$(oc get route keycloak-alt --template='{{.spec.host}}')
+<pre tabindex="0"><code>oc delete authorizationpolicy/boards-shared-lockdown
+</code></pre><pre tabindex="0"><code>oc delete policy/boards-jwt
+</code></pre><pre tabindex="0"><code>oc delete serviceentry/keycloak-egress
+</code></pre><pre tabindex="0"><code>SSO_SVC=$(oc get route keycloak-alt --template=&#39;{{.spec.host}}&#39;)
 oc set env dc/app-ui FAKE_USER=true SSO_SVC_HOST=$SSO_SVC
 </code></pre><h2 id="how-it-works">How it Works</h2>
 <p>Our app-ui microservice gets the JWT from the Keycloak SSO whenever a user logs in. If logged in, the JWT is always passed (in the request header) from the app-ui to any services it calls. All our services have Envoy sidecar proxies running and are seeing the traffic, including the JWT in app-ui request headers. So the configuration we applied is used to inform sidecar proxies to follow the policies we set. When we weren&rsquo;t logged in there was no JWT to pass along so our call requests failed. Only after we were logged in with as a valid user did we pass along a valid JWT. And each user&rsquo;s JWT was different, so the <em>when</em> conditions only matched for theterminator, allowing him able to POST to the shared board.</p>
@@ -564,7 +564,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -824,7 +824,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -936,7 +936,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -946,7 +946,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1029,7 +1029,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/index.html b/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/index.html
index d2cfe4084..9aa7abe04 100644
--- a/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/index.html
+++ b/workshops/openshift_service_mesh_v1.0/lab5.5_secureingressegress/index.html
@@ -325,7 +325,7 @@ <h1 id="securing-ingress-and-egress">Securing Ingress and Egress</h1>
 <h2 id="lock-down-egress">Lock Down Egress</h2>
 <p>In this example we are going to restrict access to external endpoints to only approved hosts. The service mesh has an egress router (a standalone Envoy) running by default and we just need to configure it.</p>
 <p>The <code>ServiceMeshControlPlane</code> custom resource we used to install Istio has a <code>global</code> config which allows control of the defaults for egress security. That looks like this:</p>
-<pre><code># Set the default behavior of the sidecar for handling outbound traffic from the application:
+<pre tabindex="0"><code># Set the default behavior of the sidecar for handling outbound traffic from the application:
 # ALLOW_ANY - outbound traffic to unknown destinations will be allowed, in case there are no
 #   services or ServiceEntries for the destination port
 # REGISTRY_ONLY - restrict outbound traffic to services defined in the service registry as well
@@ -337,15 +337,15 @@ <h2 id="lock-down-egress">Lock Down Egress</h2>
 <i class="fa fa-terminal"></i>
 Run this command and look for outboundTrafficPolicy
 </blockquote>
-<pre><code>oc describe cm/istio -n istio-system
+<pre tabindex="0"><code>oc describe cm/istio -n istio-system
 </code></pre><br>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Now let's verify it's working - Run this command to scrape some data:
 </blockquote>
-<pre><code>oc run curl-scraper-1 -i --restart=Never --image=appropriate/curl --timeout=30s -- -v context-scraper:8080/scrape/custom_search?term==skynet
+<pre tabindex="0"><code>oc run curl-scraper-1 -i --restart=Never --image=appropriate/curl --timeout=30s -- -v context-scraper:8080/scrape/custom_search?term==skynet
 </code></pre><p>We should get an output similar to the one below, with error of ECONNRESET:</p>
-<pre><code>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+<pre tabindex="0"><code>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed
   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 172.30.83.172...
 * TCP_NODELAY set
@@ -360,7 +360,7 @@ <h2 id="lock-down-egress">Lock Down Egress</h2>
 &lt; access-control-allow-origin: *
 &lt; content-type: application/json; charset=utf-8
 &lt; content-length: 682
-&lt; etag: W/&quot;2aa-5GVBTSjlqUqotSZU1yZmOHgTWC0&quot;
+&lt; etag: W/&#34;2aa-5GVBTSjlqUqotSZU1yZmOHgTWC0&#34;
 &lt; date: Thu, 07 May 2020 23:02:45 GMT
 &lt; x-envoy-upstream-service-time: 36
 &lt; server: istio-envoy
@@ -369,7 +369,7 @@ <h2 id="lock-down-egress">Lock Down Egress</h2>
 { [682 bytes data]
 100   682  100   682    0     0  16634      0 --:--:-- --:--:-- --:--:-- 16634
 * Connection #0 to host context-scraper left intact
-{&quot;oops&quot;:{&quot;name&quot;:&quot;RequestError&quot;,&quot;message&quot;:&quot;Error: read ECONNRESET&quot;,&quot;cause&quot;:{&quot;errno&quot;:&quot;ECONNRESET&quot;,&quot;code&quot;:&quot;ECONNRESET&quot;,&quot;syscall&quot;:&quot;read&quot;},&quot;error&quot;:{&quot;errno&quot;:&quot;ECONNRESET&quot;,&quot;code&quot;:&quot;ECONNRESET&quot;,&quot;syscall&quot;:&quot;read&quot;},&quot;options&quot;:{&quot;method&quot;:&quot;GET&quot;,&quot;uri&quot;:&quot;https://www.googleapis.com/customsearch/v1/siterestrict&quot;,&quot;qs&quot;:{&quot;key&quot;:&quot;AIzaSyDRdgirA2Pakl4PMi7t-8LFfnnjEFHnbY4&quot;,&quot;cx&quot;:&quot;005627457786250373845:lwanzyzfwji&quot;,&quot;q&quot;:&quot;=skynet&quot;},&quot;headers&quot;:{&quot;user-agent&quot;:&quot;curl/7.59.0&quot;,&quot;x-request-id&quot;:&quot;d78cf7b9-0010-9ecf-b520-f3d6a83376a0&quot;,&quot;x-b3-traceid&quot;:&quot;21b58b1725b20a81f914496d9a55455d&quot;,&quot;x-b3-spanid&quot;:&quot;f914496d9a55455d&quot;,&quot;x-b3-sampled&quot;:&quot;1&quot;},&quot;json&quot;:true,&quot;simple&quot;:true,&quot;resolveWithFullResponse&quot;:false,&quot;transform2xxOnly&quot;:false}}}
+{&#34;oops&#34;:{&#34;name&#34;:&#34;RequestError&#34;,&#34;message&#34;:&#34;Error: read ECONNRESET&#34;,&#34;cause&#34;:{&#34;errno&#34;:&#34;ECONNRESET&#34;,&#34;code&#34;:&#34;ECONNRESET&#34;,&#34;syscall&#34;:&#34;read&#34;},&#34;error&#34;:{&#34;errno&#34;:&#34;ECONNRESET&#34;,&#34;code&#34;:&#34;ECONNRESET&#34;,&#34;syscall&#34;:&#34;read&#34;},&#34;options&#34;:{&#34;method&#34;:&#34;GET&#34;,&#34;uri&#34;:&#34;https://www.googleapis.com/customsearch/v1/siterestrict&#34;,&#34;qs&#34;:{&#34;key&#34;:&#34;AIzaSyDRdgirA2Pakl4PMi7t-8LFfnnjEFHnbY4&#34;,&#34;cx&#34;:&#34;005627457786250373845:lwanzyzfwji&#34;,&#34;q&#34;:&#34;=skynet&#34;},&#34;headers&#34;:{&#34;user-agent&#34;:&#34;curl/7.59.0&#34;,&#34;x-request-id&#34;:&#34;d78cf7b9-0010-9ecf-b520-f3d6a83376a0&#34;,&#34;x-b3-traceid&#34;:&#34;21b58b1725b20a81f914496d9a55455d&#34;,&#34;x-b3-spanid&#34;:&#34;f914496d9a55455d&#34;,&#34;x-b3-sampled&#34;:&#34;1&#34;},&#34;json&#34;:true,&#34;simple&#34;:true,&#34;resolveWithFullResponse&#34;:false,&#34;transform2xxOnly&#34;:false}}}
 </code></pre><p>Which is curl (running in a pod in our project) trying to talk to the context-scraper microservice (in the mesh). You can see from the error details that the service is trying to get out to googleapis.com but fails.</p>
 <br>
 <blockquote>
@@ -381,7 +381,7 @@ <h2 id="lock-down-egress">Lock Down Egress</h2>
 <h2 id="allow-egress-to-approved-hosts">Allow Egress to Approved Hosts</h2>
 <p>Now we will be using an Istio API object of type <a href="https://istio.io/docs/concepts/traffic-management/#service-entries">ServiceEntry</a> to allow controlled egress. After you add this ServiceEntry, our microservices (via their Envoy sidecars) can send traffic to the specified external service as if it was a service in your mesh.</p>
 <p>Our ServiceEntry looks like this:</p>
-<pre><code>apiVersion: networking.istio.io/v1alpha3
+<pre tabindex="0"><code>apiVersion: networking.istio.io/v1alpha3
 kind: ServiceEntry
 metadata:
   name: context-scraper-egress
@@ -399,18 +399,18 @@ <h2 id="allow-egress-to-approved-hosts">Allow Egress to Approved Hosts</h2>
 <i class="fa fa-terminal"></i>
 Apply it with the following command:
 </blockquote>
-<pre><code>oc apply -f ./istio-configuration/serviceentry-googleapis.yaml
+<pre tabindex="0"><code>oc apply -f ./istio-configuration/serviceentry-googleapis.yaml
 </code></pre><br>
 <blockquote>
 <i class="fa fa-terminal"></i>
 Run a new curl job to try scrape some data again:
 </blockquote>
-<pre><code>oc run curl-scraper-2 -i --restart=Never --image=appropriate/curl --timeout=30s -- context-scraper:8080/scrape/custom_search?term==skynet
+<pre tabindex="0"><code>oc run curl-scraper-2 -i --restart=Never --image=appropriate/curl --timeout=30s -- context-scraper:8080/scrape/custom_search?term==skynet
 </code></pre><p>Now we should get an output similar to the one below - showing results:</p>
-<pre><code>custom_search?term==skynet
+<pre tabindex="0"><code>custom_search?term==skynet
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed
-  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0[{&quot;link&quot;:&quot;https://www.reddit.com/r/movies/comments/1jqo8m/in_the_terminator_franchise_what_does_skynet/&quot;,&quot;title&quot;:&quot;In the Terminator franchise, what does Skynet actually want? : movies&quot;,&quot;snippet&quot;:&quot;Skynet perceived this as an attack and came to the conclusion that all of \nhumanity would attempt to destroy it. To defend itself, Skynet launched nuclear \nmissiles ...&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/incremental_games/comments/akfdz3/skynet_in_alpha_v2_10min_feedback_welcome/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcSq88CbTfa-lnWG4n7Y3xEVP4mD4A66tKWsBRRKJi7uPmPhacMeeVuexYI&quot;,&quot;width&quot;:&quot;310&quot;,&quot;height&quot;:&quot;163&quot;}],&quot;title&quot;:&quot;Skynet. In Alpha v2 (~10min). Feedback welcome ...&quot;,&quot;snippet&quot;:&quot;r/incremental_games: This subreddit is for lovers of games that feature an \nincremental mechanism, such as unlocking progressively more powerful …&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/DeepBrainChain/comments/8rar5b/deepbrain_chain_launches_skynet_project/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&quot;,&quot;width&quot;:&quot;225&quot;,&quot;height&quot;:&quot;225&quot;}],&quot;title&quot;:&quot;DeepBrain Chain Launches ''Skynet Project''— Recruiting AI ...&quot;,&quot;snippet&quot;:&quot;To achieve that, DeepBrain Chain Foundation will activate the ''Skynet Project'' \non June 15th Beijing time and, recruit AI computing power from the globe.&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/OutOfTheLoop/comments/24obct/what_is_skynet_and_why_do_people_reference_it/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&quot;,&quot;width&quot;:&quot;225&quot;,&quot;height&quot;:&quot;225&quot;}],&quot;title&quot;:&quot;What is Skynet and why do people reference it often? : OutOfTheLoop&quot;,&quot;snippet&quot;:&quot;It is a reference to the movie Terminator. Skynet is the fictional computer entity \nwhich becomes self-aware and takes over all other computers it is linked to. Then\n, ...&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/linux/comments/2vyhr6/apparently_terminator_runs_linux_version/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQSpw8eEnexhK7SlaTQPtFUIqBZYb-Qt5Pa28s8fPAMI4uydC7nmbCc_bU&quot;,&quot;width&quot;:&quot;300&quot;,&quot;height&quot;:&quot;168&quot;}],&quot;title&quot;:&quot;Apparently Terminator runs Linux version 4.1.15-1.1381 ...&quot;,&quot;snippet&quot;:&quot;The real question is why skynet bothers making visuals displays for data. \nContinue this thread. level 1. ptrwis. 177 points · 5 years ago. It's systemd, \nevolved and ...&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/siacoin/comments/elqcyi/taek_teases_skynet_huge_news_in_the_pipeline/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcRcez9TMXJ9S-onsmNDs7ZxIJEdM8hhhneEJgjELCbomsACnBA2ywgnPvo&quot;,&quot;width&quot;:&quot;152&quot;,&quot;height&quot;:&quot;331&quot;}],&quot;title&quot;:&quot;Taek teases Skynet - huge news in the pipeline, game-changing ...&quot;,&quot;snippet&quot;:&quot;r/siacoin: Sia is a cryptocurrency engineered to provide industrial grade cloud \nstorage at consumer prices.&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/incremental_games/comments/98oj1p/skynet_in_alpha_5min_feedback_welcome/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcSq88CbTfa-lnWG4n7Y3xEVP4mD4A66tKWsBRRKJi7uPmPhacMeeVuexYI&quot;,&quot;width&quot;:&quot;310&quot;,&quot;height&quot;:&quot;163&quot;}],&quot;title&quot;:&quot;Skynet. In Alpha (~5min). Feedback welcome : incremental_games&quot;,&quot;snippet&quot;:&quot;r/incremental_games: This subreddit is for lovers of games that feature an \nincremental mechanism, such as unlocking progressively more powerful …&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/AskScienceFiction/comments/3msulj/terminator_why_doesnt_skynet_use_bio_weapons/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&quot;,&quot;width&quot;:&quot;225&quot;,&quot;height&quot;:&quot;225&quot;}],&quot;title&quot;:&quot;[Terminator] why doesn't skynet use bio weapons? : AskScienceFiction&quot;,&quot;snippet&quot;:&quot;When skynet came online initially it calculated that humanities greatest threat \nwas itself and so it launched our best weapons against Americas most well ...&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/AskScienceFiction/comments/9yp425/terminator_why_does_skynet_only_send_robots_back/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&quot;,&quot;width&quot;:&quot;225&quot;,&quot;height&quot;:&quot;225&quot;}],&quot;title&quot;:&quot;[Terminator] Why does Skynet only send robots back within one life ...&quot;,&quot;snippet&quot;:&quot;Skynet's existence exists as a mobius strip in time, centered around Judgement \nDay. Judgement Day is inevitable, and nothing can stop it from taking place.&quot;},{&quot;link&quot;:&quot;https://www.reddit.com/r/AskScienceFiction/comments/7q7766/terminator_why_doesnt_skynet_just_poison_the/&quot;,&quot;thumbnail&quot;:[{&quot;src&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&quot;,&quot;width&quot;:&quot;225&quot;,&quot;height&quot;:&quot;225&quot;}],&quot;title&quot;:&quot;[Terminator] Why doesn't Skynet just poison the atmosphere if they ...&quot;,&quot;snippet&quot;:&quot;Skynet uses Terminators because, so far as it is concerned100  5049  100  5049    0     0   9350      0 --:--:-- --:--:-- --:--:--  9332e humans. It's goal is to \nfulfill ..
+  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0[{&#34;link&#34;:&#34;https://www.reddit.com/r/movies/comments/1jqo8m/in_the_terminator_franchise_what_does_skynet/&#34;,&#34;title&#34;:&#34;In the Terminator franchise, what does Skynet actually want? : movies&#34;,&#34;snippet&#34;:&#34;Skynet perceived this as an attack and came to the conclusion that all of \nhumanity would attempt to destroy it. To defend itself, Skynet launched nuclear \nmissiles ...&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/incremental_games/comments/akfdz3/skynet_in_alpha_v2_10min_feedback_welcome/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcSq88CbTfa-lnWG4n7Y3xEVP4mD4A66tKWsBRRKJi7uPmPhacMeeVuexYI&#34;,&#34;width&#34;:&#34;310&#34;,&#34;height&#34;:&#34;163&#34;}],&#34;title&#34;:&#34;Skynet. In Alpha v2 (~10min). Feedback welcome ...&#34;,&#34;snippet&#34;:&#34;r/incremental_games: This subreddit is for lovers of games that feature an \nincremental mechanism, such as unlocking progressively more powerful …&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/DeepBrainChain/comments/8rar5b/deepbrain_chain_launches_skynet_project/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&#34;,&#34;width&#34;:&#34;225&#34;,&#34;height&#34;:&#34;225&#34;}],&#34;title&#34;:&#34;DeepBrain Chain Launches &#39;&#39;Skynet Project&#39;&#39;— Recruiting AI ...&#34;,&#34;snippet&#34;:&#34;To achieve that, DeepBrain Chain Foundation will activate the &#39;&#39;Skynet Project&#39;&#39; \non June 15th Beijing time and, recruit AI computing power from the globe.&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/OutOfTheLoop/comments/24obct/what_is_skynet_and_why_do_people_reference_it/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&#34;,&#34;width&#34;:&#34;225&#34;,&#34;height&#34;:&#34;225&#34;}],&#34;title&#34;:&#34;What is Skynet and why do people reference it often? : OutOfTheLoop&#34;,&#34;snippet&#34;:&#34;It is a reference to the movie Terminator. Skynet is the fictional computer entity \nwhich becomes self-aware and takes over all other computers it is linked to. Then\n, ...&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/linux/comments/2vyhr6/apparently_terminator_runs_linux_version/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQSpw8eEnexhK7SlaTQPtFUIqBZYb-Qt5Pa28s8fPAMI4uydC7nmbCc_bU&#34;,&#34;width&#34;:&#34;300&#34;,&#34;height&#34;:&#34;168&#34;}],&#34;title&#34;:&#34;Apparently Terminator runs Linux version 4.1.15-1.1381 ...&#34;,&#34;snippet&#34;:&#34;The real question is why skynet bothers making visuals displays for data. \nContinue this thread. level 1. ptrwis. 177 points · 5 years ago. It&#39;s systemd, \nevolved and ...&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/siacoin/comments/elqcyi/taek_teases_skynet_huge_news_in_the_pipeline/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcRcez9TMXJ9S-onsmNDs7ZxIJEdM8hhhneEJgjELCbomsACnBA2ywgnPvo&#34;,&#34;width&#34;:&#34;152&#34;,&#34;height&#34;:&#34;331&#34;}],&#34;title&#34;:&#34;Taek teases Skynet - huge news in the pipeline, game-changing ...&#34;,&#34;snippet&#34;:&#34;r/siacoin: Sia is a cryptocurrency engineered to provide industrial grade cloud \nstorage at consumer prices.&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/incremental_games/comments/98oj1p/skynet_in_alpha_5min_feedback_welcome/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcSq88CbTfa-lnWG4n7Y3xEVP4mD4A66tKWsBRRKJi7uPmPhacMeeVuexYI&#34;,&#34;width&#34;:&#34;310&#34;,&#34;height&#34;:&#34;163&#34;}],&#34;title&#34;:&#34;Skynet. In Alpha (~5min). Feedback welcome : incremental_games&#34;,&#34;snippet&#34;:&#34;r/incremental_games: This subreddit is for lovers of games that feature an \nincremental mechanism, such as unlocking progressively more powerful …&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/AskScienceFiction/comments/3msulj/terminator_why_doesnt_skynet_use_bio_weapons/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&#34;,&#34;width&#34;:&#34;225&#34;,&#34;height&#34;:&#34;225&#34;}],&#34;title&#34;:&#34;[Terminator] why doesn&#39;t skynet use bio weapons? : AskScienceFiction&#34;,&#34;snippet&#34;:&#34;When skynet came online initially it calculated that humanities greatest threat \nwas itself and so it launched our best weapons against Americas most well ...&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/AskScienceFiction/comments/9yp425/terminator_why_does_skynet_only_send_robots_back/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&#34;,&#34;width&#34;:&#34;225&#34;,&#34;height&#34;:&#34;225&#34;}],&#34;title&#34;:&#34;[Terminator] Why does Skynet only send robots back within one life ...&#34;,&#34;snippet&#34;:&#34;Skynet&#39;s existence exists as a mobius strip in time, centered around Judgement \nDay. Judgement Day is inevitable, and nothing can stop it from taking place.&#34;},{&#34;link&#34;:&#34;https://www.reddit.com/r/AskScienceFiction/comments/7q7766/terminator_why_doesnt_skynet_just_poison_the/&#34;,&#34;thumbnail&#34;:[{&#34;src&#34;:&#34;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQrwBIFnOZygv1EKJ1z7TnNeWIfom8Kp0Zgbs6YvM4DXYP0zvra6GNCnh0&#34;,&#34;width&#34;:&#34;225&#34;,&#34;height&#34;:&#34;225&#34;}],&#34;title&#34;:&#34;[Terminator] Why doesn&#39;t Skynet just poison the atmosphere if they ...&#34;,&#34;snippet&#34;:&#34;Skynet uses Terminators because, so far as it is concerned100  5049  100  5049    0     0   9350      0 --:--:-- --:--:-- --:--:--  9332e humans. It&#39;s goal is to \nfulfill ..
 </code></pre><br>
 <p>If we wanted to we could now configure virtual services and destination rules to control traffic to the service entry in a more granular way. The same way we configured traffic for the other services in our mesh.</p>
 <p>And Kiali tracks this ServiceEntry too, let&rsquo;s look at the graph to see how things are visualized.</p>
@@ -530,7 +530,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -790,7 +790,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -902,7 +902,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -912,7 +912,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -995,7 +995,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/readme/index.html b/workshops/pki_workshop/readme/index.html
index c88a59c28..af8581e8f 100644
--- a/workshops/pki_workshop/readme/index.html
+++ b/workshops/pki_workshop/readme/index.html
@@ -349,7 +349,7 @@ <h3 id="additional-resources">Additional Resources</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_1/index.html b/workshops/pki_workshop/unit_lessons/unit_1/index.html
index e47547d55..8b707483a 100644
--- a/workshops/pki_workshop/unit_lessons/unit_1/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_1/index.html
@@ -347,7 +347,7 @@ <h1 id="unit-1-installing-directory-server">Unit 1: Installing Directory Server<
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_10/index.html b/workshops/pki_workshop/unit_lessons/unit_10/index.html
index 647a3d727..8609724df 100644
--- a/workshops/pki_workshop/unit_lessons/unit_10/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_10/index.html
@@ -363,7 +363,7 @@ <h2 id="generate-virtual-token">Generate Virtual Token</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_11/index.html b/workshops/pki_workshop/unit_lessons/unit_11/index.html
index d0e92d81f..b749a816e 100644
--- a/workshops/pki_workshop/unit_lessons/unit_11/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_11/index.html
@@ -360,7 +360,7 @@ <h2 id="example-causercert-profile">Example caUserCert Profile</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_12/index.html b/workshops/pki_workshop/unit_lessons/unit_12/index.html
index a79beb581..cc6641de9 100644
--- a/workshops/pki_workshop/unit_lessons/unit_12/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_12/index.html
@@ -489,7 +489,7 @@ <h3 id="solution-3">Solution</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_2/index.html b/workshops/pki_workshop/unit_lessons/unit_2/index.html
index 5ca7174b1..96e811243 100644
--- a/workshops/pki_workshop/unit_lessons/unit_2/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_2/index.html
@@ -377,7 +377,7 @@ <h2 id="directory-structure">Directory Structure</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_3/index.html b/workshops/pki_workshop/unit_lessons/unit_3/index.html
index 32b10055e..5ce0cf367 100644
--- a/workshops/pki_workshop/unit_lessons/unit_3/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_3/index.html
@@ -453,7 +453,7 @@ <h2 id="tps">TPS</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_4/index.html b/workshops/pki_workshop/unit_lessons/unit_4/index.html
index abe1ffefc..7711e464e 100644
--- a/workshops/pki_workshop/unit_lessons/unit_4/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_4/index.html
@@ -382,7 +382,7 @@ <h2 id="view-each-subsystem-page">View each subsystem page</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_5/index.html b/workshops/pki_workshop/unit_lessons/unit_5/index.html
index 9c73755dd..908482185 100644
--- a/workshops/pki_workshop/unit_lessons/unit_5/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_5/index.html
@@ -525,7 +525,7 @@ <h2 id="pkidaemon">pkidaemon</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_6/index.html b/workshops/pki_workshop/unit_lessons/unit_6/index.html
index 0e4b72b48..7da13a596 100644
--- a/workshops/pki_workshop/unit_lessons/unit_6/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_6/index.html
@@ -414,7 +414,7 @@ <h2 id="certificate-request-web-ui">Certificate Request (Web UI)</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_7/index.html b/workshops/pki_workshop/unit_lessons/unit_7/index.html
index eab72c1a2..fecc19c10 100644
--- a/workshops/pki_workshop/unit_lessons/unit_7/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_7/index.html
@@ -411,7 +411,7 @@ <h2 id="recover-private-key">Recover Private Key</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_8/index.html b/workshops/pki_workshop/unit_lessons/unit_8/index.html
index aa9721c72..ab24c6e70 100644
--- a/workshops/pki_workshop/unit_lessons/unit_8/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_8/index.html
@@ -375,7 +375,7 @@ <h2 id="revoke-certificate-cli">Revoke Certificate (CLI)</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/pki_workshop/unit_lessons/unit_9/index.html b/workshops/pki_workshop/unit_lessons/unit_9/index.html
index f4b533f09..b2bdc5e55 100644
--- a/workshops/pki_workshop/unit_lessons/unit_9/index.html
+++ b/workshops/pki_workshop/unit_lessons/unit_9/index.html
@@ -386,7 +386,7 @@ <h2 id="check-certificate-revocation-list-cli">Check Certificate Revocation List
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.0/index.html b/workshops/rhel_8/exercise1.0/index.html
index 5686073f5..9a0169725 100644
--- a/workshops/rhel_8/exercise1.0/index.html
+++ b/workshops/rhel_8/exercise1.0/index.html
@@ -330,7 +330,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>With predictable release cadence and 10-year enterprise support, RHEL 8 is the safe and stable choice for your enterprise.</p>
 </div>
 <div class="paragraph">
-<p>RHEL 8 uses OpenSCAP on your system, to automate regulatory compliance and security configuration. OpenSCAP is the National Institute of Standards and Technology (NIST)-certified scanner, used by Red Hat. RHEL 8&#8217;s security portfolio also includes a new, system-wide encryption policy and the latest nftables/firewalld firewall.</p>
+<p>RHEL 8 uses OpenSCAP on your system, to automate regulatory compliance and security configuration. OpenSCAP is the National Institute of Standards and Technology (NIST)-certified scanner, used by Red Hat. RHEL 8’s security portfolio also includes a new, system-wide encryption policy and the latest nftables/firewalld firewall.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -432,7 +432,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -692,7 +692,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -804,7 +804,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -814,7 +814,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -900,7 +900,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.1/index.html b/workshops/rhel_8/exercise1.1/index.html
index 0a83b9289..6fa4218f0 100644
--- a/workshops/rhel_8/exercise1.1/index.html
+++ b/workshops/rhel_8/exercise1.1/index.html
@@ -479,7 +479,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -739,7 +739,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -851,7 +851,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -861,7 +861,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -947,7 +947,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.2/index.html b/workshops/rhel_8/exercise1.2/index.html
index 3afd4e1e0..d12300e54 100644
--- a/workshops/rhel_8/exercise1.2/index.html
+++ b/workshops/rhel_8/exercise1.2/index.html
@@ -340,13 +340,13 @@ <h3 id="_section_1_overview_of_the_web_console">Section 1: Overview of the web c
 <div class="content">
 <div class="imageblock left">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_topics.png" alt="cockpit topics" width="450">
+<img src="/workshops/rhel_8/images/cockpit_topics.png" alt="cockpit topics" width="450"/>
 </div>
 <div class="title">Figure 1: Web console functions</div>
 </div>
 <div class="paragraph">
-<p>The various functional sections can be seen in <strong>Figure 1</strong>, and are:<br>
-<br></p>
+<p>The various functional sections can be seen in <strong>Figure 1</strong>, and are:<br/>
+<br/></p>
 </div>
 <div class="dlist">
 <dl>
@@ -357,72 +357,72 @@ <h3 id="_section_1_overview_of_the_web_console">Section 1: Overview of the web c
 <dt class="hdlist1">Logs</dt>
 <dd>
 <p>Displays current <strong>journald</strong> logs from all services
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Storage</dt>
 <dd>
 <p>Displays storage activity graphs, and logs. Enables the management of NFS mounts, RAID devices, volume groups, VDO (deduplication) devices, and iSCSI targets
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Networking</dt>
 <dd>
 <p>Displays network activity, logs, and allows firewall and network maintenance
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Podman Containers</dt>
 <dd>
 <p>Enables the management of container images and running containers
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Virtual Machines</dt>
 <dd>
 <p>Virtual machines can be created, deleted and controlled
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Accounts</dt>
 <dd>
 <p>Allows for the creation, deletion and configuration of user accounts and ssh keys
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Services</dt>
 <dd>
 <p>Displays all system targets, services, sockets, timers and paths, as managed by <strong>systemd</strong>, the root process
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Session Recording</dt>
 <dd>
 <p>Manages recorded sessions, and allows for the configuration of session recorder defaults
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Applications</dt>
 <dd>
 <p>Allows for the installation and removal of web console modules
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Diagnostic Reports</dt>
 <dd>
 <p>Creates diagnostic reports used by Red Hat support, also known as SOSreports
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Kernel Dump</dt>
 <dd>
 <p>Manages kernel debugging dumps, created when the system crashes
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">SELinux</dt>
 <dd>
 <p>Allows for the setting of SELinux to permissive mode, and shows recent SELinux alerts (<strong>AVCs</strong>)
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Software Updates</dt>
 <dd>
 <p>Manages automatic package updating, and allows for the manual installation of updates
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Subscriptions</dt>
 <dd>
 <p>Manages subscriptions attached to the host
-<br></p>
+<br/></p>
 </dd>
 <dt class="hdlist1">Terminal</dt>
 <dd>
@@ -436,14 +436,14 @@ <h3 id="_section_1_overview_of_the_web_console">Section 1: Overview of the web c
 <p>As you can see, many of the day-to-day management of a RHEL system can be accomplished without touching the terminal. This makes RHEL 8 the easiest-to-live-with release, yet!</p>
 </div>
 <div class="paragraph">
-<p>Next, let&#8217;s proceed to a more detailed examination of each module. Please click through the web console on your host, as you read the explanations, here.</p>
+<p>Next, let’s proceed to a more detailed examination of each module. Please click through the web console on your host, as you read the explanations, here.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_section_2_system_module">Section 2: System Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_system.png" alt="cockpit system" height="650">
+<img src="/workshops/rhel_8/images/cockpit_system.png" alt="cockpit system" height="650"/>
 </div>
 <div class="title">Figure 2: Web Console System Module</div>
 </div>
@@ -521,7 +521,7 @@ <h3 id="_section_2_system_module">Section 2: System Module</h3>
 <p>Performance Profile</p>
 </li>
 <li>
-<p>ssh key fingerprints for all created 'root' keys</p>
+<p>ssh key fingerprints for all created &#39;root&#39; keys</p>
 </li>
 <li>
 <p>Toggle to enable or disable storing of metrics.</p>
@@ -532,14 +532,14 @@ <h3 id="_section_2_system_module">Section 2: System Module</h3>
 </dl>
 </div>
 <div class="paragraph">
-<p>Additionally, there are graphs that show the system&#8217;s CPU, memory, disk, and network utilization.  Each graph may be enlarged, by clicking its associated link.</p>
+<p>Additionally, there are graphs that show the system’s CPU, memory, disk, and network utilization.  Each graph may be enlarged, by clicking its associated link.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_section_3_logs_module">Section 3: Logs Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_01_logs.png" alt="cockpit 01 logs" height="650">
+<img src="/workshops/rhel_8/images/cockpit_01_logs.png" alt="cockpit 01 logs" height="650"/>
 </div>
 <div class="title">Figure 3: Web Console Logs Module</div>
 </div>
@@ -551,7 +551,7 @@ <h3 id="_section_3_logs_module">Section 3: Logs Module</h3>
 <h3 id="_section_4_storage_module">Section 4: Storage Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_02_storage.png" alt="cockpit 02 storage" height="650">
+<img src="/workshops/rhel_8/images/cockpit_02_storage.png" alt="cockpit 02 storage" height="650"/>
 </div>
 <div class="title">Figure 4: Web Console Storage Module</div>
 </div>
@@ -563,7 +563,7 @@ <h3 id="_section_4_storage_module">Section 4: Storage Module</h3>
 <h3 id="_section_5_networking_module">Section 5: Networking Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_03_networking.png" alt="cockpit 03 networking" height="650">
+<img src="/workshops/rhel_8/images/cockpit_03_networking.png" alt="cockpit 03 networking" height="650"/>
 </div>
 <div class="title">Figure 5: Web Console Networking Module</div>
 </div>
@@ -575,7 +575,7 @@ <h3 id="_section_5_networking_module">Section 5: Networking Module</h3>
 <h3 id="_section_5_podman_containers_module">Section 5: Podman Containers Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_04_podman.png" alt="cockpit 04 podman" height="650">
+<img src="/workshops/rhel_8/images/cockpit_04_podman.png" alt="cockpit 04 podman" height="650"/>
 </div>
 <div class="title">Figure 6: Web Console Podman Containers Module</div>
 </div>
@@ -587,7 +587,7 @@ <h3 id="_section_5_podman_containers_module">Section 5: Podman Containers Module
 <h3 id="_section_6_virtual_machines_module">Section 6: Virtual Machines Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_05_vms.png" alt="cockpit 05 vms" height="650">
+<img src="/workshops/rhel_8/images/cockpit_05_vms.png" alt="cockpit 05 vms" height="650"/>
 </div>
 <div class="title">Figure 7: Web Console Virtual Machines Module</div>
 </div>
@@ -599,7 +599,7 @@ <h3 id="_section_6_virtual_machines_module">Section 6: Virtual Machines Module</
 <h3 id="_section_7_accounts_module">Section 7: Accounts Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_06_accounts.png" alt="cockpit 06 accounts" height="650">
+<img src="/workshops/rhel_8/images/cockpit_06_accounts.png" alt="cockpit 06 accounts" height="650"/>
 </div>
 <div class="title">Figure 8: Web Console Accounts Module</div>
 </div>
@@ -611,7 +611,7 @@ <h3 id="_section_7_accounts_module">Section 7: Accounts Module</h3>
 <h3 id="_section_8_services_module">Section 8: Services Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_07_services.png" alt="cockpit 07 services" height="650">
+<img src="/workshops/rhel_8/images/cockpit_07_services.png" alt="cockpit 07 services" height="650"/>
 </div>
 <div class="title">Figure 9: Web Console Services Module</div>
 </div>
@@ -623,7 +623,7 @@ <h3 id="_section_8_services_module">Section 8: Services Module</h3>
 <h3 id="_section_9_session_recording_module">Section 9: Session Recording Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_08_sr.png" alt="cockpit 08 sr" height="650">
+<img src="/workshops/rhel_8/images/cockpit_08_sr.png" alt="cockpit 08 sr" height="650"/>
 </div>
 <div class="title">Figure 10: Web Console Session Recording Module</div>
 </div>
@@ -635,7 +635,7 @@ <h3 id="_section_9_session_recording_module">Section 9: Session Recording Module
 <h3 id="_section_10_applications_module">Section 10: Applications Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_09_applications.png" alt="cockpit 09 applications" height="650">
+<img src="/workshops/rhel_8/images/cockpit_09_applications.png" alt="cockpit 09 applications" height="650"/>
 </div>
 <div class="title">Figure 11: Web Console Applications Module</div>
 </div>
@@ -647,7 +647,7 @@ <h3 id="_section_10_applications_module">Section 10: Applications Module</h3>
 <h3 id="_section_11_diagnostic_reports_module">Section 11: Diagnostic Reports Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_10_dr.png" alt="cockpit 10 dr" height="650">
+<img src="/workshops/rhel_8/images/cockpit_10_dr.png" alt="cockpit 10 dr" height="650"/>
 </div>
 <div class="title">Figure 12: Web Console Diagnostic Reports Module</div>
 </div>
@@ -659,7 +659,7 @@ <h3 id="_section_11_diagnostic_reports_module">Section 11: Diagnostic Reports Mo
 <h3 id="_section_12_kernel_dump_module">Section 12: Kernel Dump Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_11_kd.png" alt="cockpit 11 kd" height="650">
+<img src="/workshops/rhel_8/images/cockpit_11_kd.png" alt="cockpit 11 kd" height="650"/>
 </div>
 <div class="title">Figure 13: Web Console Kernel Dump Module</div>
 </div>
@@ -671,7 +671,7 @@ <h3 id="_section_12_kernel_dump_module">Section 12: Kernel Dump Module</h3>
 <h3 id="_section_13_selinux_module">Section 13: SELinux Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_12_selinux.png" alt="cockpit 12 selinux" height="650">
+<img src="/workshops/rhel_8/images/cockpit_12_selinux.png" alt="cockpit 12 selinux" height="650"/>
 </div>
 <div class="title">Figure 14: Web Console SELinux Module</div>
 </div>
@@ -683,7 +683,7 @@ <h3 id="_section_13_selinux_module">Section 13: SELinux Module</h3>
 <h3 id="_section_14_software_update_module">Section 14: Software Update Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_13_su.png" alt="cockpit 13 su" height="650">
+<img src="/workshops/rhel_8/images/cockpit_13_su.png" alt="cockpit 13 su" height="650"/>
 </div>
 <div class="title">Figure 15: Web Console Kernel Dump Module</div>
 </div>
@@ -695,7 +695,7 @@ <h3 id="_section_14_software_update_module">Section 14: Software Update Module</
 <h3 id="_section_15_subscriptions_module">Section 15: Subscriptions Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_14_subscriptions.png" alt="cockpit 14 subscriptions" height="650">
+<img src="/workshops/rhel_8/images/cockpit_14_subscriptions.png" alt="cockpit 14 subscriptions" height="650"/>
 </div>
 <div class="title">Figure 16: Web Console Subscriptions Module</div>
 </div>
@@ -707,12 +707,12 @@ <h3 id="_section_15_subscriptions_module">Section 15: Subscriptions Module</h3>
 <h3 id="_section_16_terminal_module">Section 16: Terminal Module</h3>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_15_terminal.png" alt="cockpit 15 terminal" height="650">
+<img src="/workshops/rhel_8/images/cockpit_15_terminal.png" alt="cockpit 15 terminal" height="650"/>
 </div>
 <div class="title">Figure 17: Web Console Terminal Module</div>
 </div>
 <div class="paragraph">
-<p>The terminal module provides command-line access to the system, similar to an SSH session.  Section 16.1 has some example commands to try if you&#8217;d like to test it out.</p>
+<p>The terminal module provides command-line access to the system, similar to an SSH session.  Section 16.1 has some example commands to try if you’d like to test it out.</p>
 </div>
 <div class="sect3">
 <h4 id="_section_16_1_example_terminal_usage">Section 16.1: Example terminal usage</h4>
@@ -724,13 +724,13 @@ <h5 id="_example_1_use_the_following_command_to_pull_a_rhel_image_from_the_red_h
 </div>
 </div>
 <div class="paragraph">
-<p>Now if you return to the Podman Containers tab (above, in Section 5), you should see this image listed; you may be prompted to start the Podman service as well.  You&#8217;ll see more of podman later in Exercise 8.</p>
+<p>Now if you return to the Podman Containers tab (above, in Section 5), you should see this image listed; you may be prompted to start the Podman service as well.  You’ll see more of podman later in Exercise 8.</p>
 </div>
 </div>
 <div class="sect4">
 <h5 id="_example_2_try_the_skopeo_command">Example 2: Try the Skopeo command</h5>
 <div class="paragraph">
-<p>Skopeo provides the ability to inspect container images stored in a registry. The Inspect feature displays details of the selected image. The 'skopeo inspect' command&#8217;s ability to list all the tags associated with a selected image is a benefit over the docker tool.</p>
+<p>Skopeo provides the ability to inspect container images stored in a registry. The Inspect feature displays details of the selected image. The &#39;skopeo inspect&#39; command’s ability to list all the tags associated with a selected image is a benefit over the docker tool.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -741,7 +741,7 @@ <h5 id="_example_2_try_the_skopeo_command">Example 2: Try the Skopeo command</h5
 <div class="sect4">
 <h5 id="_example_3_list_firewall_rules">Example 3: List firewall rules</h5>
 <div class="paragraph">
-<p>nft is the nftables utility.  Similar to ''iptables -L'', the following lists the system&#8217;s active firewall ruleset:</p>
+<p>nft is the nftables utility.  Similar to &#39;&#39;iptables -L&#39;&#39;, the following lists the system’s active firewall ruleset:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -856,7 +856,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1116,7 +1116,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1228,7 +1228,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1238,7 +1238,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1325,7 +1325,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.3/index.html b/workshops/rhel_8/exercise1.3/index.html
index 026773e19..432106a8f 100644
--- a/workshops/rhel_8/exercise1.3/index.html
+++ b/workshops/rhel_8/exercise1.3/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.3 - Managing Updates Using the Web Console</h1>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve toured the web console, lets work through updating the system.</p>
+<p>Now that you’ve toured the web console, lets work through updating the system.</p>
 </div>
 </div>
 </div>
@@ -338,7 +338,7 @@ <h3 id="_step_1_check_for_available_updates">Step 1: Check for available updates
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/su_updates.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/su_updates.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 1: Packages Available for Updating</div>
 </div>
@@ -347,7 +347,7 @@ <h3 id="_step_1_check_for_available_updates">Step 1: Check for available updates
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/su_updates_expanded.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/su_updates_expanded.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 2: Expanded Updates</div>
 </div>
@@ -365,7 +365,7 @@ <h3 id="_step_2_install_updates">Step 2: Install updates</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/su_updates_restart.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/su_updates_restart.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 3: Updates Recommend a Restart</div>
 </div>
@@ -377,13 +377,13 @@ <h3 id="_step_2_restart_the_system">Step 2: Restart the system</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/su_updates_restarting.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/su_updates_restarting.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 4: System Restarting</div>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/su_updates_disconnected.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/su_updates_disconnected.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 5: Disconnected</div>
 </div>
@@ -401,7 +401,7 @@ <h3 id="_step_4_summary">Step 4: Summary</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/su_updates_summary.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/su_updates_summary.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 6: Update Summary</div>
 </div>
@@ -412,7 +412,7 @@ <h3 id="_step_4_summary">Step 4: Summary</h3>
 <h2 id="_section_2_automatic_updating">Section 2: Automatic Updating</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Next, let&#8217;s take a look at automatic updating.  There is an <code>Automatic Updates</code> switch, at the top of the updates window.</p>
+<p>Next, let’s take a look at automatic updating.  There is an <code>Automatic Updates</code> switch, at the top of the updates window.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1_enable_automatic_updates">Step 1: Enable Automatic Updates</h3>
@@ -421,7 +421,7 @@ <h3 id="_step_1_enable_automatic_updates">Step 1: Enable Automatic Updates</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/au_install_dnf.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/au_install_dnf.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 7: Install the dnf-automatic Package</div>
 </div>
@@ -436,7 +436,7 @@ <h3 id="_step_2_configure_timing">Step 2: Configure Timing</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/au_configure.png" alt="Software Updates" width="900">
+<img src="/workshops/rhel_8/images/au_configure.png" alt="Software Updates" width="900"/>
 </div>
 <div class="title">Figure 8: Configure Automatic Updates and Timing</div>
 </div>
@@ -445,9 +445,9 @@ <h3 id="_step_2_configure_timing">Step 2: Configure Timing</h3>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 33.3333%;">
-<col style="width: 33.3333%;">
-<col style="width: 33.3334%;">
+<col style="width: 33.3333%;"/>
+<col style="width: 33.3333%;"/>
+<col style="width: 33.3334%;"/>
 </colgroup>
 <thead>
 <tr>
@@ -588,7 +588,7 @@ <h3 id="_step_2_configure_timing">Step 2: Configure Timing</h3>
 <h2 id="_summary">Summary</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>We&#8217;ve tried out the RHEL 8 web console&#8217;s manual and automatic updating functionality.  Please ask any questions that seem relevant, and then we can move on to the next section.</p>
+<p>We’ve tried out the RHEL 8 web console’s manual and automatic updating functionality.  Please ask any questions that seem relevant, and then we can move on to the next section.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -690,7 +690,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -950,7 +950,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1062,7 +1062,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1072,7 +1072,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1158,7 +1158,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.4/index.html b/workshops/rhel_8/exercise1.4/index.html
index 3c6197bb0..804748352 100644
--- a/workshops/rhel_8/exercise1.4/index.html
+++ b/workshops/rhel_8/exercise1.4/index.html
@@ -321,8 +321,8 @@ <h1>Exercise 1.4 - Configuring Terminal Session Recording</h1>
 <h2 id="_section_1_deploying_session_recording">Section 1. Deploying Session Recording</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>To be able to deploy the Session Recording solution you need to have the following packages installed: tlog, SSSD, cockpit-session-recording.<br>
-Note that session recording doesn&#8217;t work for graphical desktop sessions or Cockpit terminal sessions.</p>
+<p>To be able to deploy the Session Recording solution you need to have the following packages installed: tlog, SSSD, cockpit-session-recording.<br/>
+Note that session recording doesn’t work for graphical desktop sessions or Cockpit terminal sessions.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1_1_pre_requisites">Step 1.1: Pre-Requisites</h3>
@@ -347,15 +347,15 @@ <h3 id="_step_1_1_pre_requisites">Step 1.1: Pre-Requisites</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-In RHEL 8, software installation is enabled by the new version of the YUM tool (YUM v4), which is based on DNF technology. We use the <code>yum</code> command in all of today&#8217;s documentation, but welcome you to start getting used to typing <code>dnf</code> instead.  Read more here: <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/managing-software-packages_configuring-basic-system-settings">Managing software packages</a>
+In RHEL 8, software installation is enabled by the new version of the YUM tool (YUM v4), which is based on DNF technology. We use the <code>yum</code> command in all of today’s documentation, but welcome you to start getting used to typing <code>dnf</code> instead.  Read more here: <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/managing-software-packages_configuring-basic-system-settings">Managing software packages</a>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -367,7 +367,7 @@ <h3 id="_step_1_2_configuring_the_recorded_users_or_user_groups_with_sssd_from_w
 <h4 id="_step_1_2_1_go_to_the_session_recording_page_in_the_menu_on_the_left_of_the_interface">Step 1.2.1: Go to the Session Recording page in the menu on the left of the interface.</h4>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/TerminalRecording-af59f.png" alt="TerminalRecording af59f">
+<img src="/workshops/rhel_8/images/TerminalRecording-af59f.png" alt="TerminalRecording af59f"/>
 </div>
 </div>
 </div>
@@ -375,20 +375,20 @@ <h4 id="_step_1_2_1_go_to_the_session_recording_page_in_the_menu_on_the_left_of_
 <h4 id="_step_1_2_2_click_on_the_gear_button_in_the_right_top_corner">Step 1.2.2: Click on the gear button in the right top corner.</h4>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/TerminalRecording-9ee56.png" alt="TerminalRecording 9ee56">
+<img src="/workshops/rhel_8/images/TerminalRecording-9ee56.png" alt="TerminalRecording 9ee56"/>
 </div>
 </div>
 </div>
 <div class="sect3">
 <h4 id="_step_1_2_3_set_your_parameters_in_the_sssd_configuration_table">Step 1.2.3: Set your parameters in the SSSD Configuration table.</h4>
 <div class="paragraph">
-<p>There are 2 configuration panes, a General and another for SSSD; scroll down if you don&#8217;t see the SSSD pane.
-To keep things simple, choose the <code>All</code> option in the <code>Scope</code> pull-down menu of the SSSD pane, as shown below.  Optionally choosing <code>Some</code> will allow you to provide comma-separated lists of users and groups whose terminal sessions should be recorded.<br>
+<p>There are 2 configuration panes, a General and another for SSSD; scroll down if you don’t see the SSSD pane.
+To keep things simple, choose the <code>All</code> option in the <code>Scope</code> pull-down menu of the SSSD pane, as shown below.  Optionally choosing <code>Some</code> will allow you to provide comma-separated lists of users and groups whose terminal sessions should be recorded.<br/>
 Be sure to click <code>Save</code> after making a selection.</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/TerminalRecording-60f70.png" alt="TerminalRecording 60f70">
+<img src="/workshops/rhel_8/images/TerminalRecording-60f70.png" alt="TerminalRecording 60f70"/>
 </div>
 </div>
 </div>
@@ -396,7 +396,7 @@ <h4 id="_step_1_2_3_set_your_parameters_in_the_sssd_configuration_table">Step 1.
 <div class="sect2">
 <h3 id="_step_1_3_test_session_recording">Step 1.3: Test Session Recording</h3>
 <div class="paragraph">
-<p>Let&#8217;s create a sample log. SSH back into your server and see what has changed:</p>
+<p>Let’s create a sample log. SSH back into your server and see what has changed:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -404,12 +404,12 @@ <h3 id="_step_1_3_test_session_recording">Step 1.3: Test Session Recording</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>You should see a banner that says "ATTENTION! Your session is being recorded!"</p>
+<p>You should see a banner that says &#34;ATTENTION! Your session is being recorded!&#34;</p>
 </div>
 <div class="ulist">
 <ul>
 <li>
-<p>Enter a few commands. For this demo, we&#8217;ll do <code>uptime</code>, <code>ls -l</code>,<code>df -h</code> and <code>hostname</code></p>
+<p>Enter a few commands. For this demo, we’ll do <code>uptime</code>, <code>ls -l</code>,<code>df -h</code> and <code>hostname</code></p>
 </li>
 </ul>
 </div>
@@ -455,7 +455,7 @@ <h3 id="_step_2_1_playback_with_the_web_console">Step 2.1 Playback with the web
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/TerminalRecording-09d8f.png" alt="TerminalRecording 09d8f">
+<img src="/workshops/rhel_8/images/TerminalRecording-09d8f.png" alt="TerminalRecording 09d8f"/>
 </div>
 </div>
 <div class="paragraph">
@@ -463,7 +463,7 @@ <h3 id="_step_2_1_playback_with_the_web_console">Step 2.1 Playback with the web
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/TerminalRecording-178f1.png" alt="TerminalRecording 178f1">
+<img src="/workshops/rhel_8/images/TerminalRecording-178f1.png" alt="TerminalRecording 178f1"/>
 </div>
 </div>
 <div class="paragraph">
@@ -566,7 +566,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -826,7 +826,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -938,7 +938,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -948,7 +948,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1035,7 +1035,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.5/index.html b/workshops/rhel_8/exercise1.5/index.html
index 6a6029a35..9e14ed702 100644
--- a/workshops/rhel_8/exercise1.5/index.html
+++ b/workshops/rhel_8/exercise1.5/index.html
@@ -324,7 +324,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>RHEL 8 makes it easy to enforce a strong and consistent cryptographic policy on your systems.</p>
 </div>
 <div class="paragraph">
-<p>In the following exercises we&#8217;ll use the new commands for managing your crypto configurations and test them. We will be using the web site <a href="https://badssl.com">badssl.com</a> to test connections using different versions of relevant protocols, such as TLS.</p>
+<p>In the following exercises we’ll use the new commands for managing your crypto configurations and test them. We will be using the web site <a href="https://badssl.com">badssl.com</a> to test connections using different versions of relevant protocols, such as TLS.</p>
 </div>
 </div>
 </div>
@@ -340,7 +340,7 @@ <h2 id="_section_1_viewing_and_changing_the_crypto_policy">Section 1: Viewing an
 </div>
 </div>
 <div class="paragraph">
-<p>You should see something like &#8230;&#8203;</p>
+<p>You should see something like …​</p>
 </div>
 <div class="paragraph">
 <p><code>DEFAULT</code></p>
@@ -353,15 +353,15 @@ <h2 id="_section_1_viewing_and_changing_the_crypto_policy">Section 1: Viewing an
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-The system-wide crypto policies functionality is new to RHEL 8.  It is part of Red Hat&#8217;s efforts to further reduce the attack surface of your RHEL systems and the applications you build on them.
+The system-wide crypto policies functionality is new to RHEL 8.  It is part of Red Hat’s efforts to further reduce the attack surface of your RHEL systems and the applications you build on them.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>To see the effect of the DEFAULT policy, try pasting in this command:</p>
@@ -372,10 +372,10 @@ <h2 id="_section_1_viewing_and_changing_the_crypto_policy">Section 1: Viewing an
 </div>
 </div>
 <div class="paragraph">
-<p>You can see from the 2nd line of output that it cannot make a TLS connection to that site, and reports "unsupported protocol".</p>
+<p>You can see from the 2nd line of output that it cannot make a TLS connection to that site, and reports &#34;unsupported protocol&#34;.</p>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s change the default crypto policy from DEFAULT to something less secure, just for testing purposes.  We&#8217;ll set the crypto policy to LEGACY to temporarily allow insecure TLS 1.1 communication from our system.</p>
+<p>Now let’s change the default crypto policy from DEFAULT to something less secure, just for testing purposes.  We’ll set the crypto policy to LEGACY to temporarily allow insecure TLS 1.1 communication from our system.</p>
 </div>
 <div class="paragraph">
 <p>Change the crypto policy to LEGACY.</p>
@@ -389,7 +389,7 @@ <h2 id="_section_1_viewing_and_changing_the_crypto_policy">Section 1: Viewing an
 <p>Note: You may see a warning requesting a reboot for the policy change to fully take place, but this is not necessary for this exercise.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s test communication to the same site; It should connect successfully, and report TLS v1.1:</p>
+<p>Let’s test communication to the same site; It should connect successfully, and report TLS v1.1:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -496,7 +496,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -756,7 +756,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -868,7 +868,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -878,7 +878,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -964,7 +964,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.6/index.html b/workshops/rhel_8/exercise1.6/index.html
index f90e7f141..7a7a619af 100644
--- a/workshops/rhel_8/exercise1.6/index.html
+++ b/workshops/rhel_8/exercise1.6/index.html
@@ -611,7 +611,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -871,7 +871,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -983,7 +983,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -993,7 +993,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1079,7 +1079,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.7/index.html b/workshops/rhel_8/exercise1.7/index.html
index 8d330ee95..10a3cbb88 100644
--- a/workshops/rhel_8/exercise1.7/index.html
+++ b/workshops/rhel_8/exercise1.7/index.html
@@ -321,12 +321,12 @@ <h1>Exercise 1.7 - OpenSCAP Security Compliance Scanning</h1>
 <h2 id="_overview">Overview</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>RHEL 8 makes it easy to maintain secure and compliant systems with OpenSCAP. <br></p>
+<p>RHEL 8 makes it easy to maintain secure and compliant systems with OpenSCAP. <br/></p>
 </div>
 <div class="sect2">
 <h3 id="_what_is_scap">What is SCAP?</h3>
 <div class="paragraph">
-<p>SCAP (Security Content Automation Protocol) is a NIST project that standardizes the language for describing assessment criteria and findings.  It also provides a vulnerability rating system.  The project&#8217;s home page is <code><a href="https://scap.nist.gov/" class="bare">https://scap.nist.gov/</a></code><br></p>
+<p>SCAP (Security Content Automation Protocol) is a NIST project that standardizes the language for describing assessment criteria and findings.  It also provides a vulnerability rating system.  The project’s home page is <code><a href="https://scap.nist.gov/" class="bare">https://scap.nist.gov/</a></code><br/></p>
 </div>
 <div class="paragraph">
 <p>The essential components of SCAP are:</p>
@@ -354,7 +354,7 @@ <h3 id="_what_is_scap">What is SCAP?</h3>
 </ul>
 </div>
 <div class="paragraph">
-<p>OpenSCAP is a project that implements tools for performing SCAP scans and remediating findings.<br>
+<p>OpenSCAP is a project that implements tools for performing SCAP scans and remediating findings.<br/>
 You can read more about the project at <code><a href="http://www.open-scap.org/" class="bare">http://www.open-scap.org/</a></code> and the repository for their tools and profiles is on GitHub at <code><a href="https://github.com/OpenSCAP/openscap/" class="bare">https://github.com/OpenSCAP/openscap/</a></code>.
 Red Hat ships SCAP content in the SCAP security guide, but the content the OpenSCAP uses is under active development and latest versions of it can be found at: <code><a href="http://www.github.com/ComplianceAsCode" class="bare">http://www.github.com/ComplianceAsCode</a></code>.  Red Hat also maintains security data feeds, including security advisories in OVAL format, at:  <code><a href="https://access.redhat.com/security/data" class="bare">https://access.redhat.com/security/data</a></code>.</p>
 </div>
@@ -365,7 +365,7 @@ <h3 id="_what_is_scap">What is SCAP?</h3>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>In the following exercises we&#8217;ll use the CLI to show how you can validate system compliance.  There are other tools as well, including a GUI utility and another for scanning container images.</p>
+<p>In the following exercises we’ll use the CLI to show how you can validate system compliance.  There are other tools as well, including a GUI utility and another for scanning container images.</p>
 </div>
 </div>
 </div>
@@ -373,7 +373,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_ensure_httpd_and_the_openscap_scanner_are_installed">Section 1: Ensure httpd and the OpenSCAP scanner are installed</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Ensure Apache httpd plus the OpenSCAP scanner and definitions are installed with the command below; it&#8217;s safe to run even if the packages already exist:</p>
+<p>Ensure Apache httpd plus the OpenSCAP scanner and definitions are installed with the command below; it’s safe to run even if the packages already exist:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -381,7 +381,7 @@ <h2 id="_section_1_ensure_httpd_and_the_openscap_scanner_are_installed">Section
 </div>
 </div>
 <div class="paragraph">
-<p>The <mark>scap-security-guide</mark> package contains prepared system profiles for several RHEL releases and system types; they are installed under <strong>/usr/share/xml/scap/ssg/content</strong>. <br>
+<p>The <mark>scap-security-guide</mark> package contains prepared system profiles for several RHEL releases and system types; they are installed under <strong>/usr/share/xml/scap/ssg/content</strong>. <br/>
 You can get a summary of the profiles in a given definition file with the following command:</p>
 </div>
 <div class="listingblock">
@@ -456,7 +456,7 @@ <h2 id="_section_1_ensure_httpd_and_the_openscap_scanner_are_installed">Section
 </div>
 </div>
 <div class="paragraph">
-<p>Towards the bottom of the list, you can see profiles for PCI-DSS and another for OSPP.  The OSPP profile is a general-purpose profile, so it&#8217;s a good choice for testing.</p>
+<p>Towards the bottom of the list, you can see profiles for PCI-DSS and another for OSPP.  The OSPP profile is a general-purpose profile, so it’s a good choice for testing.</p>
 </div>
 </div>
 </div>
@@ -488,15 +488,15 @@ <h2 id="_section_3_perform_an_initial_compliance_scan">Section 3: Perform an ini
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-Issue under investigation: If the command above ends with a one line message saying "Killed", then the report will not generate.  This can be remediated via a reboot until the root cause is found.
+Issue under investigation: If the command above ends with a one line message saying &#34;Killed&#34;, then the report will not generate.  This can be remediated via a reboot until the root cause is found.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>The command above outputs the result of the compliance scan into an Asset Reporting Format (ARF) file, and generates a HTML-based report</p>
@@ -511,7 +511,7 @@ <h2 id="_section_3_perform_an_initial_compliance_scan">Section 3: Perform an ini
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -519,14 +519,14 @@ <h2 id="_section_3_perform_an_initial_compliance_scan">Section 3: Perform an ini
 The FQDN in the URL above is an example.  Yours will need to have the FQDN used to reach your host via the Cockpit Web Console, e.g. <code>node-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span></code>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
-<p>Here&#8217;s a snippet of what the report looks like:</p>
+<p>Here’s a snippet of what the report looks like:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/openscap-example-report.png" alt="openscap example report" width="800">
+<img src="/workshops/rhel_8/images/openscap-example-report.png" alt="openscap example report" width="800"/>
 </div>
 <div class="title">Figure 1: OpenSCAP report</div>
 </div>
@@ -536,16 +536,16 @@ <h2 id="_section_3_perform_an_initial_compliance_scan">Section 3: Perform an ini
 <h2 id="_section_4_automatically_remediate_findings">Section 4: Automatically remediate findings</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>To correct compliance issues found in the scan, we can generate a Bash shell script or an Ansible playbook automatically from the scan&#8217;s findings.  To generate an Ansible playbook, run the following:</p>
+<p>To correct compliance issues found in the scan, we can generate a Bash shell script or an Ansible playbook automatically from the scan’s findings.  To generate an Ansible playbook, run the following:</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">sudo oscap xccdf generate fix --fetch-remote-resources --fix-type ansible --result-id "" /tmp/arf.xml &gt; /tmp/ospp-playbook-fix.yml</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">sudo oscap xccdf generate fix --fetch-remote-resources --fix-type ansible --result-id &#34;&#34; /tmp/arf.xml &gt; /tmp/ospp-playbook-fix.yml</code></pre>
 </div>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -554,10 +554,10 @@ <h2 id="_section_4_automatically_remediate_findings">Section 4: Automatically re
 <mark>sudo oscap xccdf generate fix --fetch-remote-resources --fix-type ansible --profile xccdf_org.ssgproject.content_profile_stig /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml &gt; /tmp/stig-playbook-fix.yml</mark>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
-<p>Review the generated YAML file, <mark>/tmp/ospp-playbook-fix.yml</mark>.  Note that the individual tasks are clearly named and delineated.  Once you&#8217;re comfortable with it, run the playbook with:</p>
+<p>Review the generated YAML file, <mark>/tmp/ospp-playbook-fix.yml</mark>.  Note that the individual tasks are clearly named and delineated.  Once you’re comfortable with it, run the playbook with:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -582,15 +582,15 @@ <h2 id="_section_5_review_changes">Section 5: Review changes</h2>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-Issue under investigation: If the command above ends with a one line message saying "Killed", then the report will not generate.  This can be remediated via a reboot until the root cause is found.
+Issue under investigation: If the command above ends with a one line message saying &#34;Killed&#34;, then the report will not generate.  This can be remediated via a reboot until the root cause is found.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>Once the command completes, open this link in another tab to view the resulting report:</p>
@@ -703,7 +703,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -963,7 +963,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1075,7 +1075,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1085,7 +1085,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1171,7 +1171,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.8/index.html b/workshops/rhel_8/exercise1.8/index.html
index b6a885ab5..471cfa837 100644
--- a/workshops/rhel_8/exercise1.8/index.html
+++ b/workshops/rhel_8/exercise1.8/index.html
@@ -332,7 +332,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_overview_of_buildah_podman_and_skopeo">Section 1: Overview of buildah, podman and skopeo</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p><mark>Buildah</mark> specializes in building OCI images. Buildah&#8217;s commands replicate all of the commands that are found in a Dockerfile. This allows building images with and without Dockerfiles while not requiring any root privileges. The flexibility of building images without Dockerfiles also allows for the integration of other scripting languages into the build process.</p>
+<p><mark>Buildah</mark> specializes in building OCI images. Buildah’s commands replicate all of the commands that are found in a Dockerfile. This allows building images with and without Dockerfiles while not requiring any root privileges. The flexibility of building images without Dockerfiles also allows for the integration of other scripting languages into the build process.</p>
 </div>
 <div class="paragraph">
 <p><mark>Podman</mark> specializes in all of the commands and functions that help you to maintain and modify OCI images, such as pulling and tagging. It also allows you to create, run, and maintain those containers created from those images.</p>
@@ -377,7 +377,7 @@ <h3 id="_step_2_verify_the_container_image_pulled_correctly">Step 2: Verify the
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -385,7 +385,7 @@ <h3 id="_step_2_verify_the_container_image_pulled_correctly">Step 2: Verify the
 Buildah will append <mark>-working-container</mark> to the image name used. If that name already exists, a number will also be appended.  For this exercise, you should see an image with the container name <mark>ubi-working-container</mark>.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -445,7 +445,7 @@ <h3 id="_step_2_install_a_simple_home_page">Step 2: Install a simple home page</
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">echo 'Welcome to the RHEL8 workshop!' &gt; index.html
+<pre class="highlight"><code class="language-bash" data-lang="bash">echo &#39;Welcome to the RHEL8 workshop!&#39; &gt; index.html
 buildah copy ubi-working-container index.html /var/www/html/index.html</code></pre>
 </div>
 </div>
@@ -457,7 +457,7 @@ <h3 id="_step_3_set_httpd_to_start_at_launch">Step 3: Set httpd to start at laun
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">buildah config --cmd "/usr/sbin/httpd -D FOREGROUND" ubi-working-container</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">buildah config --cmd &#34;/usr/sbin/httpd -D FOREGROUND&#34; ubi-working-container</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -528,7 +528,7 @@ <h3 id="_step_1_use_podman_to_inspect_available_images">Step 1: Use podman to in
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -536,7 +536,7 @@ <h3 id="_step_1_use_podman_to_inspect_available_images">Step 1: Use podman to in
 The name matches what was set using <mark>buildah commit</mark>.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -545,7 +545,7 @@ <h3 id="_step_2_use_podman_to_start_the_customized_container_and_bind_port_8080"
 <p>Podman and buildah use the same local image storage locations, which lets us immediately run our new image without specifying the location of the container or system on which the container will run. Note we are using the name httpd that we created in our previous section. As mentioned previously, you can launch, test, and then stop the container as you make each individual change. This can be used for general application testing or debugging of a change made to the container during customization with buildah.</p>
 </div>
 <div class="paragraph">
-<p>the container&#8217;s port 80 is at this point bound to port 8080 so it could be started by a non-root user.</p>
+<p>the container’s port 80 is at this point bound to port 8080 so it could be started by a non-root user.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -576,18 +576,18 @@ <h3 id="_step_3_inspect_container_and_verify_the_application_in_the_container_is
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-You may ask yourself what this "amazing_tharp" business is about in the output above. Podman generates random two word names for new containers, which you can use to refer to specific container.  What two word name was generated for your container?
+You may ask yourself what this &#34;amazing_tharp&#34; business is about in the output above. Podman generates random two word names for new containers, which you can use to refer to specific container.  What two word name was generated for your container?
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
-<p>Further, you can view the container&#8217;s processes with the following:</p>
+<p>Further, you can view the container’s processes with the following:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -619,7 +619,7 @@ <h3 id="_step_3_inspect_container_and_verify_the_application_in_the_container_is
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -627,19 +627,19 @@ <h3 id="_step_3_inspect_container_and_verify_the_application_in_the_container_is
 Note the URL specified matches the port mapping specified on the <mark>podman run</mark> command.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-If you get an error message such as "You don&#8217;t have permission to access this resource.", you may need to inspect the permissions of the index.html file you copied into the container image.
+If you get an error message such as &#34;You don’t have permission to access this resource.&#34;, you may need to inspect the permissions of the index.html file you copied into the container image.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="sect3">
 <h4 id="_step_4_stop_the_container">Step 4: Stop the container</h4>
@@ -675,7 +675,7 @@ <h4 id="_step_4_stop_the_container">Step 4: Stop the container</h4>
 <p>Notice the STATUS field is now reported as Exited.</p>
 </div>
 <div class="paragraph">
-<p>Alternatively, if you would prefer to stop only a single container, you can utilize <mark>podman ps</mark> to identify the Container ID you wish to stop.  (If you&#8217;ve already performed the <mark>stop -a</mark>, you can re-start the container with the <mark>podman run</mark> command shown in Step 2, above.)  Then use the following command, with your unique Container ID number, to shutdown a single instance. For example:</p>
+<p>Alternatively, if you would prefer to stop only a single container, you can utilize <mark>podman ps</mark> to identify the Container ID you wish to stop.  (If you’ve already performed the <mark>stop -a</mark>, you can re-start the container with the <mark>podman run</mark> command shown in Step 2, above.)  Then use the following command, with your unique Container ID number, to shutdown a single instance. For example:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -711,7 +711,7 @@ <h3 id="_step_0_disable_fapolicyd">Step 0: Disable Fapolicyd</h3>
 <div class="sect2">
 <h3 id="_step_1_inspecting_the_httpd_image">Step 1: Inspecting the httpd image</h3>
 <div class="paragraph">
-<p>First let&#8217;s use skopeo to inspect the image.</p>
+<p>First let’s use skopeo to inspect the image.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -721,12 +721,12 @@ <h3 id="_step_1_inspecting_the_httpd_image">Step 1: Inspecting the httpd image</
 <div class="literalblock">
 <div class="content">
 <pre>{
-    "Name": "localhost/httpd",
-    "Digest": "sha256:0dbc14b4aa06a3232087d5fa329b158dfe580686fa00e9383f78ee64e3d3ae0f",
-    "RepoTags": [],
-    "Created": "2020-07-29T03:26:45.369889926Z",
-    "DockerVersion": "",
-    "Labels": {
+    &#34;Name&#34;: &#34;localhost/httpd&#34;,
+    &#34;Digest&#34;: &#34;sha256:0dbc14b4aa06a3232087d5fa329b158dfe580686fa00e9383f78ee64e3d3ae0f&#34;,
+    &#34;RepoTags&#34;: [],
+    &#34;Created&#34;: &#34;2020-07-29T03:26:45.369889926Z&#34;,
+    &#34;DockerVersion&#34;: &#34;&#34;,
+    &#34;Labels&#34;: {
 
 &lt;&lt;output truncate&gt;&gt;
 
@@ -737,7 +737,7 @@ <h3 id="_step_1_inspecting_the_httpd_image">Step 1: Inspecting the httpd image</
 <div class="sect2">
 <h3 id="_step_2_transfer_the_image_into_the_operating_system_image_store">Step 2: Transfer the image into the operating system image store</h3>
 <div class="paragraph">
-<p>First export the image from ec2-user&#8217;s image store into an archive file. Skopeo can export containers into either docker archive or OCI archive if we want to put the container into a file. Using the OCI archive format:</p>
+<p>First export the image from ec2-user’s image store into an archive file. Skopeo can export containers into either docker archive or OCI archive if we want to put the container into a file. Using the OCI archive format:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -793,11 +793,11 @@ <h3 id="_step_2_transfer_the_image_into_the_operating_system_image_store">Step 2
 <div class="sect2">
 <h3 id="_step_3_scan_the_container_image_for_cves">Step 3: Scan the container image for CVEs</h3>
 <div class="paragraph">
-<p>Before using this container image in a system service, let&#8217;s check it for CVEs.  Since RHEL 8.2, the <mark>oscap-podman</mark> utility has been included for scanning container images.  Let&#8217;s see how this works!</p>
+<p>Before using this container image in a system service, let’s check it for CVEs.  Since RHEL 8.2, the <mark>oscap-podman</mark> utility has been included for scanning container images.  Let’s see how this works!</p>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -805,12 +805,12 @@ <h3 id="_step_3_scan_the_container_image_for_cves">Step 3: Scan the container im
 <mark>oscap-podman</mark> requires root privilege.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="sect3">
 <h4 id="_step_3a_download_the_latest_red_hat_security_advisories">Step 3a: Download the latest Red Hat Security Advisories</h4>
 <div class="paragraph">
-<p>Red Hat continuously updates security data feeds on <mark><a href="https://access.redhat.com/security/data" class="bare">https://access.redhat.com/security/data</a></mark>.  Let&#8217;s start by retrieving and decompressing the latest RHEL advisories in OVAL format:</p>
+<p>Red Hat continuously updates security data feeds on <mark><a href="https://access.redhat.com/security/data" class="bare">https://access.redhat.com/security/data</a></mark>.  Let’s start by retrieving and decompressing the latest RHEL advisories in OVAL format:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -821,7 +821,7 @@ <h4 id="_step_3a_download_the_latest_red_hat_security_advisories">Step 3a: Downl
 <div class="sect3">
 <h4 id="_step_3b_scan_a_container_image_with_oscap_podman">Step 3b: Scan a container image with oscap-podman</h4>
 <div class="paragraph">
-<p>Pick an <mark>IMAGE ID</mark> from the previous <mark>sudo podman images</mark> output&#8201;&#8212;&#8201;in this case, the httpd image&#8201;&#8212;&#8201;and run the scan with:</p>
+<p>Pick an <mark>IMAGE ID</mark> from the previous <mark>sudo podman images</mark> output — in this case, the httpd image — and run the scan with:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -841,7 +841,7 @@ <h4 id="_step_3b_scan_a_container_image_with_oscap_podman">Step 3b: Scan a conta
 <div class="sect2">
 <h3 id="_step_4_integrate_container_into_systemd">Step 4: Integrate container into systemd</h3>
 <div class="paragraph">
-<p>To finish this section, let&#8217;s integrate our new container into systemd so you can have it start at boot time and otherwise manage it using systemd. Before getting started, ensure that the webserver started in the openSCAP section is not running:</p>
+<p>To finish this section, let’s integrate our new container into systemd so you can have it start at boot time and otherwise manage it using systemd. Before getting started, ensure that the webserver started in the openSCAP section is not running:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -849,7 +849,7 @@ <h3 id="_step_4_integrate_container_into_systemd">Step 4: Integrate container in
 </div>
 </div>
 <div class="paragraph">
-<p>First prepare the container by creating it using our new image and configuring it to expose port 80. This container will be named "web".</p>
+<p>First prepare the container by creating it using our new image and configuring it to expose port 80. This container will be named &#34;web&#34;.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -908,7 +908,7 @@ <h3 id="_step_4_integrate_container_into_systemd">Step 4: Integrate container in
 </div>
 </div>
 <div class="paragraph">
-<p>Confirm that the container is started and it&#8217;s port 80 is connected to the host&#8217;s port 80.</p>
+<p>Confirm that the container is started and it’s port 80 is connected to the host’s port 80.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -941,12 +941,12 @@ <h3 id="_step_4_integrate_container_into_systemd">Step 4: Integrate container in
 <h2 id="_section_6_some_other_interesting_podman_commands">Section 6: Some other interesting podman commands</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Here are some lesser-known <mark>podman</mark> features that&#8217;re really worth knowing about.</p>
+<p>Here are some lesser-known <mark>podman</mark> features that’re really worth knowing about.</p>
 </div>
 <div class="sect2">
 <h3 id="_exporting_a_container_definition_for_use_in_openshift">Exporting a container definition for use in OpenShift</h3>
 <div class="paragraph">
-<p>If you&#8217;ve built and tested a container with podman, and are happy with the results, you can very easily share that container with OpenShift.</p>
+<p>If you’ve built and tested a container with podman, and are happy with the results, you can very easily share that container with OpenShift.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -954,7 +954,7 @@ <h3 id="_exporting_a_container_definition_for_use_in_openshift">Exporting a cont
 </div>
 </div>
 <div class="paragraph">
-<p>Take a look at the file to see what&#8217;s in it.  If you were in an OpenShift project, you could then import this file with:</p>
+<p>Take a look at the file to see what’s in it.  If you were in an OpenShift project, you could then import this file with:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -1083,7 +1083,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1343,7 +1343,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1455,7 +1455,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1465,7 +1465,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1552,7 +1552,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/exercise1.9/index.html b/workshops/rhel_8/exercise1.9/index.html
index c73913d0e..026cab2eb 100644
--- a/workshops/rhel_8/exercise1.9/index.html
+++ b/workshops/rhel_8/exercise1.9/index.html
@@ -377,7 +377,7 @@ <h2 id="_section_1_installing_rhel_system_roles_and_ansible">Section 1: Installi
 <div class="sect2">
 <h3 id="_step_1_install_required_packages">Step 1: Install required packages</h3>
 <div class="paragraph">
-<p>We need to install two packages RPM packages to use system roles: <code>ansible</code> and <code>rhel-system-roles</code>.  Use subscription-manager to list the Ansible Engine repositories available. Note that the generic "2" repository will always provide the latest release of the 2.X stream as opposed to configuring a more specific version such as 2.8.</p>
+<p>We need to install two packages RPM packages to use system roles: <code>ansible</code> and <code>rhel-system-roles</code>.  Use subscription-manager to list the Ansible Engine repositories available. Note that the generic &#34;2&#34; repository will always provide the latest release of the 2.X stream as opposed to configuring a more specific version such as 2.8.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -438,13 +438,13 @@ <h2 id="_section_2_example_usage_of_the_rhel_system_roles_network_role">Section
 <div class="ulist">
 <ul>
 <li>
-<p>Generally, Ansible is not installed on every system, but rather on a single system designated as the Ansible management or control node who&#8217;s purpose is to manage other systems via Ansible.</p>
+<p>Generally, Ansible is not installed on every system, but rather on a single system designated as the Ansible management or control node who’s purpose is to manage other systems via Ansible.</p>
 </li>
 <li>
-<p>Since we&#8217;re running Ansible on the same instance we&#8217;re changing, the target of the Ansible playbook is <code>localhost</code>.</p>
+<p>Since we’re running Ansible on the same instance we’re changing, the target of the Ansible playbook is <code>localhost</code>.</p>
 </li>
 <li>
-<p>We&#8217;ve added a 2nd network interface to our test system, <code>eth1</code>.</p>
+<p>We’ve added a 2nd network interface to our test system, <code>eth1</code>.</p>
 </li>
 </ul>
 </div>
@@ -474,7 +474,7 @@ <h3 id="_step_1">Step 1:</h3>
           dhcp4: no
           auto6: no
           address:
-           - "10.10.10.{{ 254 | random( start=2) }}/24"
+           - &#34;10.10.10.{{ 254 | random( start=2) }}/24&#34;
   roles:
     - role: rhel-system-roles.network</pre>
 </div>
@@ -486,7 +486,7 @@ <h3 id="_step_1">Step 1:</h3>
 <div class="sect2">
 <h3 id="_step_2">Step 2:</h3>
 <div class="paragraph">
-<p>Now let&#8217;s test access to our <code>localhost</code> using the Ansible ad-hoc command:</p>
+<p>Now let’s test access to our <code>localhost</code> using the Ansible ad-hoc command:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -496,8 +496,8 @@ <h3 id="_step_2">Step 2:</h3>
 <div class="literalblock">
 <div class="content">
 <pre>localhost | SUCCESS =&gt; {
-    "changed": false,
-    "ping": "pong"
+    &#34;changed&#34;: false,
+    &#34;ping&#34;: &#34;pong&#34;
 }</pre>
 </div>
 </div>
@@ -509,20 +509,20 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m setup -a 'gather_subset=network filter=ansible_interfaces'</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible localhost -m setup -a &#39;gather_subset=network filter=ansible_interfaces&#39;</code></pre>
 </div>
 </div>
 <div class="literalblock">
 <div class="content">
 <pre>localhost | SUCCESS =&gt; {
-    "ansible_facts": {
-        "ansible_interfaces": [
-            "lo",
-            "eth1",
-            "eth0"
+    &#34;ansible_facts&#34;: {
+        &#34;ansible_interfaces&#34;: [
+            &#34;lo&#34;,
+            &#34;eth1&#34;,
+            &#34;eth0&#34;
         ]
     },
-    "changed": false
+    &#34;changed&#34;: false
 }</pre>
 </div>
 </div>
@@ -576,16 +576,16 @@ <h3 id="_step_4">Step 4:</h3>
 <div class="sect2">
 <h3 id="_step_5">Step 5:</h3>
 <div class="paragraph">
-<p>Now let&#8217;s run our playbook to create a new connection profile called DBnic, turn off DHCP, and assign a static ip address:</p>
+<p>Now let’s run our playbook to create a new connection profile called DBnic, turn off DHCP, and assign a static ip address:</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ansible-playbook --extra-vars "ansible_python_interpreter=/usr/bin/python3.6" example-network-playbook.yml</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">ansible-playbook --extra-vars &#34;ansible_python_interpreter=/usr/bin/python3.6&#34; example-network-playbook.yml</code></pre>
 </div>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -593,11 +593,11 @@ <h3 id="_step_5">Step 5:</h3>
 Starting in RHEL 8.7, Python 3.9 is the default Python3 interpreter.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'
+<pre>[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match &#39;all&#39;
 
 
 PLAY [localhost] ******************************************************************************************************
@@ -613,7 +613,7 @@ <h3 id="_step_5">Step 5:</h3>
 
 TASK [rhel-system-roles.network : Print network provider] *************************************************************
 ok: [localhost] =&gt; {
-    "msg": "Using network provider: nm"
+    &#34;msg&#34;: &#34;Using network provider: nm&#34;
 }
 
 TASK [rhel-system-roles.network : Install packages] *******************************************************************
@@ -629,10 +629,10 @@ <h3 id="_step_5">Step 5:</h3>
 skipping: [localhost]
 
 TASK [rhel-system-roles.network : Configure networking connection profiles] *******************************************
-[WARNING]: [003] &lt;info&gt;  #0, state:up persistent_state:present, 'DBnic': connection DBnic,
+[WARNING]: [003] &lt;info&gt;  #0, state:up persistent_state:present, &#39;DBnic&#39;: connection DBnic,
 3b54603b-c603-46b9-9bd9-e6fc295e7a11 already up to date
 
-[WARNING]: [004] &lt;info&gt;  #0, state:up persistent_state:present, 'DBnic': up connection DBnic,
+[WARNING]: [004] &lt;info&gt;  #0, state:up persistent_state:present, &#39;DBnic&#39;: up connection DBnic,
 3b54603b-c603-46b9-9bd9-e6fc295e7a11 (not-active)
 
 changed: [localhost]
@@ -648,7 +648,7 @@ <h3 id="_step_5">Step 5:</h3>
 <div class="sect2">
 <h3 id="_step_6">Step 6:</h3>
 <div class="paragraph">
-<p>Now let&#8217;s see how the Ansible playbook changed our network configuration:</p>
+<p>Now let’s see how the Ansible playbook changed our network configuration:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -695,7 +695,7 @@ <h3 id="_step_6">Step 6:</h3>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_summary_what_weve_learned">Summary - What We&#8217;ve Learned</h2>
+<h2 id="_summary_what_weve_learned">Summary - What We’ve Learned</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Linux System Roles based on Ansible playbooks make it easy and consistent to enable specific services and configurations on your RHEL hosts, and across many versions.  We experimented with the <strong>network</strong> system role in this exercise, but <strong>storage</strong>, <strong>kdump (kernel crash dump)</strong>, <strong>selinux</strong>, and <strong>timesync</strong> are also available.</p>
@@ -800,7 +800,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1060,7 +1060,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1172,7 +1172,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1182,7 +1182,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1268,7 +1268,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/index.html b/workshops/rhel_8/index.html
index 35421b9f3..a73feedba 100644
--- a/workshops/rhel_8/index.html
+++ b/workshops/rhel_8/index.html
@@ -331,7 +331,7 @@ <h2 id="_workshop_description">Workshop Description</h2>
 <p>System firmware updating is now built into the GNOME Software tool, using fwupd</p>
 </li>
 <li>
-<p>The system firewall has been upgraded to 'nftables' from 'iptables', which provides significantly better performance.  The firewall manager, 'firewalld', remains the same</p>
+<p>The system firewall has been upgraded to &#39;nftables&#39; from &#39;iptables&#39;, which provides significantly better performance.  The firewall manager, &#39;firewalld&#39;, remains the same</p>
 </li>
 </ul>
 </div>
@@ -364,7 +364,7 @@ <h2 id="_what_you_will_learn">What you will learn</h2>
 <div class="ulist">
 <ul>
 <li>
-<p>What&#8217;s new in RHEL 8</p>
+<p>What’s new in RHEL 8</p>
 </li>
 <li>
 <p>How to use the web console</p>
@@ -601,7 +601,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -861,7 +861,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -973,7 +973,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -983,7 +983,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1036,7 +1036,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/index.xml b/workshops/rhel_8/index.xml
index 147e2b01d..3205b2df4 100644
--- a/workshops/rhel_8/index.xml
+++ b/workshops/rhel_8/index.xml
@@ -4,139 +4,92 @@
     <title>Red Hat Enterprise Linux 8 on Red Hat | Public Sector</title>
     <link>/workshops/rhel_8/</link>
     <description>Recent content in Red Hat Enterprise Linux 8 on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/rhel_8/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/rhel_8/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Welcome to RHEL!</title>
       <link>/workshops/rhel_8/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.0/</guid>
-      <description>Exercise Description Welcome to RHEL!
- Red Hat Enterprise Linux 8 is the intelligent enterprise Linux, providing a secure and consistent foundation across hybrid cloud deployments and the tools enterprises need to deliver services and workloads faster with less effort. RHEL 8 enables delivery of any application, on any architecture, on any cloud, physical, or virtual environment, at any time.
- With predictable release cadence and 10-year enterprise support, RHEL 8 is the safe and stable choice for your enterprise.</description>
+      <description>Exercise Description Welcome to RHEL!&#xA;Red Hat Enterprise Linux 8 is the intelligent enterprise Linux, providing a secure and consistent foundation across hybrid cloud deployments and the tools enterprises need to deliver services and workloads faster with less effort. RHEL 8 enables delivery of any application, on any architecture, on any cloud, physical, or virtual environment, at any time.&#xA;With predictable release cadence and 10-year enterprise support, RHEL 8 is the safe and stable choice for your enterprise.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - What&#39;s New in RHEL 8</title>
       <link>/workshops/rhel_8/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.1/</guid>
-      <description>Application streams Application streams deliver user space packages on a cadence that makes sense for the package rather than as a monolithic distribution. Streams also allow the consolidation of previous distribution channels to a single place.
-   Red Hat Insights Red Hat Insights is included with your Red Hat® Enterprise Linux® 8 subscription. It helps provide a security-focused, reliable, efficient, and scalable infrastructure environment.
-   Image builder Image builder lets customers build images from source RPMs that are deployable to multiple targets quickly and simply, and provides fine-grained control and visibility in to what’s included in a particular image and its history.</description>
+      <description>Application streams Application streams deliver user space packages on a cadence that makes sense for the package rather than as a monolithic distribution. Streams also allow the consolidation of previous distribution channels to a single place.&#xA;Red Hat Insights Red Hat Insights is included with your Red Hat® Enterprise Linux® 8 subscription. It helps provide a security-focused, reliable, efficient, and scalable infrastructure environment.&#xA;Image builder Image builder lets customers build images from source RPMs that are deployable to multiple targets quickly and simply, and provides fine-grained control and visibility in to what’s included in a particular image and its history.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Tour of the Web Console</title>
       <link>/workshops/rhel_8/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.2/</guid>
-      <description>Exercise Description To get started, we will take a tour of the web console. The web console (called cockpit) will be your primary interactive interface to RHEL. The console has a number of functions that enable you to manage most aspects of the installation.
- Connect to your personal lab environment. Ensure that the information in the footer of the page is correctly filled out and the URL for your environment should show up below</description>
+      <description>Exercise Description To get started, we will take a tour of the web console. The web console (called cockpit) will be your primary interactive interface to RHEL. The console has a number of functions that enable you to manage most aspects of the installation.&#xA;Connect to your personal lab environment. Ensure that the information in the footer of the page is correctly filled out and the URL for your environment should show up below</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Managing Updates Using the Web Console</title>
       <link>/workshops/rhel_8/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.3/</guid>
-      <description>Exercise Description Now that you&amp;#8217;ve toured the web console, lets work through updating the system.
-   Section 1: Basic Updating As you did in the previous section, navigate to the Software Updates section of the Web Console, by clicking on the Software Updates link, in the left-hand menu. There will then be a brief interval where Refreshing package information will appear, along with a progress bar. Once that completes, you can proceed with the exercise.</description>
+      <description>Exercise Description Now that you’ve toured the web console, lets work through updating the system.&#xA;Section 1: Basic Updating As you did in the previous section, navigate to the Software Updates section of the Web Console, by clicking on the Software Updates link, in the left-hand menu. There will then be a brief interval where Refreshing package information will appear, along with a progress bar. Once that completes, you can proceed with the exercise.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Configuring Terminal Session Recording</title>
       <link>/workshops/rhel_8/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.4/</guid>
-      <description>Section 1. Deploying Session Recording To be able to deploy the Session Recording solution you need to have the following packages installed: tlog, SSSD, cockpit-session-recording.
-Note that session recording doesn&amp;#8217;t work for graphical desktop sessions or Cockpit terminal sessions.
- Step 1.1: Pre-Requisites In order to work with session recording, your system will need to have the following installed:
-   tlog
-  SSSD (System Security Services Deamon)</description>
+      <description>Section 1. Deploying Session Recording To be able to deploy the Session Recording solution you need to have the following packages installed: tlog, SSSD, cockpit-session-recording. Note that session recording doesn’t work for graphical desktop sessions or Cockpit terminal sessions.&#xA;Step 1.1: Pre-Requisites In order to work with session recording, your system will need to have the following installed:&#xA;tlog&#xA;SSSD (System Security Services Deamon)&#xA;cockpit-session-recording&#xA;For this workshop/lab the environment is already configured to have tlog and SSSD installed, but if you were to install these prerequisites yourself, you would run sudo yum install -y tlog cockpit-session-recording systemd-journal-remote</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Managing Cryptographic Policies</title>
       <link>/workshops/rhel_8/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.5/</guid>
-      <description>Exercise Description RHEL 8 makes it easy to enforce a strong and consistent cryptographic policy on your systems.
- In the following exercises we&amp;#8217;ll use the new commands for managing your crypto configurations and test them. We will be using the web site badssl.com to test connections using different versions of relevant protocols, such as TLS.
-   Section 1: Viewing and changing the crypto policy Show the current crypto policy.</description>
+      <description>Exercise Description RHEL 8 makes it easy to enforce a strong and consistent cryptographic policy on your systems.&#xA;In the following exercises we’ll use the new commands for managing your crypto configurations and test them. We will be using the web site badssl.com to test connections using different versions of relevant protocols, such as TLS.&#xA;Section 1: Viewing and changing the crypto policy Show the current crypto policy.&#xA;update-crypto-policies --show You should see something like …​</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - Managing Software in an Application Stream</title>
       <link>/workshops/rhel_8/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.6/</guid>
-      <description>Overview Application streams are new to RHEL 8 and provide access to the latest tools, languages and libraries, without affecting core system components. This capability gives users access to multiple versions of packages, with a known period of support. These application streams, usually provided as modules, can be thought of as package groups that represent an application, a set of tools, or runtime languages.
-   Section 1: Stream Availability Step 1: Check to see what PostgreSQL streams are available As root, use yum to see what streams are available, for PostgreSQL:</description>
+      <description>Overview Application streams are new to RHEL 8 and provide access to the latest tools, languages and libraries, without affecting core system components. This capability gives users access to multiple versions of packages, with a known period of support. These application streams, usually provided as modules, can be thought of as package groups that represent an application, a set of tools, or runtime languages.&#xA;Section 1: Stream Availability Step 1: Check to see what PostgreSQL streams are available As root, use yum to see what streams are available, for PostgreSQL:</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - OpenSCAP Security Compliance Scanning</title>
       <link>/workshops/rhel_8/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.7/</guid>
-      <description>Overview RHEL 8 makes it easy to maintain secure and compliant systems with OpenSCAP.  What is SCAP? SCAP (Security Content Automation Protocol) is a NIST project that standardizes the language for describing assessment criteria and findings. It also provides a vulnerability rating system. The project&amp;#8217;s home page is https://scap.nist.gov/
- The essential components of SCAP are:
-   XCCDF: The Extensible Configuration Checklist Description Format, to describe security checklists</description>
+      <description>Overview RHEL 8 makes it easy to maintain secure and compliant systems with OpenSCAP. What is SCAP? SCAP (Security Content Automation Protocol) is a NIST project that standardizes the language for describing assessment criteria and findings. It also provides a vulnerability rating system. The project’s home page is https://scap.nist.gov/&#xA;The essential components of SCAP are:&#xA;XCCDF: The Extensible Configuration Checklist Description Format, to describe security checklists&#xA;OVAL®: Open Vulnerability and Assessment Language, a declarative language for making logical assertions about the state of a system</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - Introduction to using buildah, podman and skopeo to work on containers</title>
       <link>/workshops/rhel_8/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.8/</guid>
-      <description>Exercise Description In this exercise, you will build a custom application container utilizing the Red Hat Universal Base Image, customize that image and test the image functionality. After that you will use skopeo to transfer that image from your user local repository to the system repository and configure it to start at boot.
- After completing this section, you will be able to build images from an existing base image using buildah and other host based tools.</description>
+      <description>Exercise Description In this exercise, you will build a custom application container utilizing the Red Hat Universal Base Image, customize that image and test the image functionality. After that you will use skopeo to transfer that image from your user local repository to the system repository and configure it to start at boot.&#xA;After completing this section, you will be able to build images from an existing base image using buildah and other host based tools.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - System Roles with Ansible</title>
       <link>/workshops/rhel_8/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/exercise1.9/</guid>
       <description>Exercise Description RHEL System Roles, announced with the launch of RHEL 8, are a collection of Ansible roles and modules that provide a stable and consistent configuration interface for remote management of Red Hat Enterprise Linux. They address many commmon configuration, security and workload uses on RHEL systems. These roles can manage systems running RHEL 7 and above, easing management of 3 generations of RHEL. The effort is based on development of the Linux System Roles project (link: https://linux-system-roles.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/rhel_8/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/rhel_8/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhel_8/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve enjoyed learning about all the goodness that is RHEL 8!
- What do you think? How can we help you understand new RHEL features better?
- This Participant Guide will remain active for the next two weeks. Please take advantage of it by downloading RHEL8 and installing a test host or VM back at your organization.
- Thank you for your time and participation!</description>
+      <description>That wraps up what we have planned for today. We hope you’ve enjoyed learning about all the goodness that is RHEL 8!&#xA;What do you think? How can we help you understand new RHEL features better?&#xA;This Participant Guide will remain active for the next two weeks. Please take advantage of it by downloading RHEL8 and installing a test host or VM back at your organization.&#xA;Thank you for your time and participation!</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/rhel_8/setup/index.html b/workshops/rhel_8/setup/index.html
index b165b6b62..7e8a207c8 100644
--- a/workshops/rhel_8/setup/index.html
+++ b/workshops/rhel_8/setup/index.html
@@ -317,7 +317,7 @@ <h1>Setup</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/rhel8-isometric.svg" alt="Red Hat Enterprise Linux 8">
+<img src="/workshops/rhel_8/images/rhel8-isometric.svg" alt="Red Hat Enterprise Linux 8"/>
 </div>
 </div>
 </div>
@@ -346,8 +346,8 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <tbody>
 <tr>
@@ -366,7 +366,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </table>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_login.png" alt="cockpit login" height="500">
+<img src="/workshops/rhel_8/images/cockpit_login.png" alt="cockpit login" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Login</div>
 </div>
@@ -375,21 +375,21 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/cockpit_system.png" alt="cockpit system" height="500">
+<img src="/workshops/rhel_8/images/cockpit_system.png" alt="cockpit system" height="500"/>
 </div>
 <div class="title">Figure 2: Web Console System Tab</div>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-Be sure that you can log in to your instances.  If you can&#8217;t log in, start shouting loudly and wave your hands!
+Be sure that you can log in to your instances.  If you can’t log in, start shouting loudly and wave your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -397,7 +397,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -499,7 +499,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -759,7 +759,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -871,7 +871,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -881,7 +881,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -963,7 +963,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhel_8/wrapup/index.html b/workshops/rhel_8/wrapup/index.html
index ec86d51d9..51d233068 100644
--- a/workshops/rhel_8/wrapup/index.html
+++ b/workshops/rhel_8/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrapup</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve enjoyed learning about all the goodness that is RHEL 8!</p>
+<p>That wraps up what we have planned for today.  We hope you’ve enjoyed learning about all the goodness that is RHEL 8!</p>
 </div>
 <div class="paragraph">
 <p>What do you think? How can we help you understand new RHEL features better?</p>
@@ -327,7 +327,7 @@ <h1>Wrapup</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/rhel_8/images/redhat.svg" alt="redhat">
+<img src="/workshops/rhel_8/images/redhat.svg" alt="redhat"/>
 </div>
 </div>
 <div class="paragraph">
@@ -430,7 +430,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -690,7 +690,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -802,7 +802,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -812,7 +812,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -892,7 +892,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/10_storage/index.html b/workshops/rhosp_101/10_storage/index.html
index 421ec1a8d..01c100f08 100644
--- a/workshops/rhosp_101/10_storage/index.html
+++ b/workshops/rhosp_101/10_storage/index.html
@@ -333,10 +333,9 @@ <h1 id="lets-begin-working-with-block-storage">Let&rsquo;s begin working with Bl
 <blockquote>
 <p>Navigate to Volumes -&gt; Volumes using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab9-storage-1.png"/> <figcaption>
-            <h4>Lab 9 Figure 1: Volume Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-1.png"><figcaption>
+      <h4>Lab 9 Figure 1: Volume Listing</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -348,10 +347,9 @@ <h4>Lab 9 Figure 1: Volume Listing</h4>
 Leave <strong>Availability Zone</strong> as is<br>
 Click <strong>Create Volume</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab9-storage-2.png"/> <figcaption>
-            <h4>Lab 9 Figure 2: Create Volume</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-2.png"><figcaption>
+      <h4>Lab 9 Figure 2: Create Volume</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-info">
@@ -359,10 +357,9 @@ <h4>Lab 9 Figure 2: Create Volume</h4>
 <p>You should see an info box appear in the upper right corner of the screen that says something similar to &lsquo;Info: Creating volume &ldquo;student<span class="userid">1</span>-vol-1&rdquo;&rsquo;</p>
 <p>If you did not, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab9-storage-3.png"/> <figcaption>
-            <h4>Lab 9 Figure 3: New Volume Created in Project</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-3.png"><figcaption>
+      <h4>Lab 9 Figure 3: New Volume Created in Project</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -372,10 +369,9 @@ <h4>Lab 9 Figure 3: New Volume Created in Project</h4>
 Leave <strong>Device Name</strong> as is<br>
 Click <strong>Attach Volume</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab9-storage-4.png"/> <figcaption>
-            <h4>Lab 9 Figure 4: Attach Volume to Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-4.png"><figcaption>
+      <h4>Lab 9 Figure 4: Attach Volume to Instance</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-info">
@@ -383,10 +379,9 @@ <h4>Lab 9 Figure 4: Attach Volume to Instance</h4>
 <p>You should see an info box appear in the upper right corner of the screen that says something similar to &lsquo;Info: Attaching volume student<span class="userid">1</span>-vol-1 to instance student<span class="userid">1</span>-cirros-1 on /dev/vdb.&rsquo;</p>
 <p>If you did not, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab9-storage-5.png"/> <figcaption>
-            <h4>Lab 9 Figure 5: New Volume Attached to Instance in Volume Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-5.png"><figcaption>
+      <h4>Lab 9 Figure 5: New Volume Attached to Instance in Volume Listing</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -398,10 +393,9 @@ <h1 id="now-lets-learn-about-object-storage">Now Let&rsquo;s Learn About Object
 <blockquote>
 <p>Navigate to Object Store -&gt; Containers using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab9-storage-6.png"/> <figcaption>
-            <h4>Lab 9 Figure 6: Object Store Container Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-6.png"><figcaption>
+      <h4>Lab 9 Figure 6: Object Store Container Listing</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -410,10 +404,9 @@ <h4>Lab 9 Figure 6: Object Store Container Listing</h4>
 Leave <strong>Not Public</strong> under Container Access selected<br>
 Click <strong>Submit</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab9-storage-7.png"/> <figcaption>
-            <h4>Lab 9 Figure 7: Create Container</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-7.png"><figcaption>
+      <h4>Lab 9 Figure 7: Create Container</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -421,10 +414,9 @@ <h4>Lab 9 Figure 7: Create Container</h4>
 <p>You should see an info box appear in the upper right corner of the screen that says something similar to &ldquo;Success: Container student<span class="userid">1</span>-container created.&rdquo;</p>
 <p>If you did not, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab9-storage-8.png"/> <figcaption>
-            <h4>Lab 9 Figure 8: New Container Created in Object Store</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-8.png"><figcaption>
+      <h4>Lab 9 Figure 8: New Container Created in Object Store</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -435,10 +427,9 @@ <h4>Lab 9 Figure 8: New Container Created in Object Store</h4>
 <p><span class="pficon pficon-info"></span></p>
 <p>The <strong>upload button</strong> looks like a <strong>folder with an up arrow</strong></p>
 </div>
-<figure>
-    <img src="../images/lab9-storage-9.png"/> <figcaption>
-            <h4>Lab 9 Figure 9: Select Container in Object Store</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-9.png"><figcaption>
+      <h4>Lab 9 Figure 9: Select Container in Object Store</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -447,10 +438,9 @@ <h4>Lab 9 Figure 9: Select Container in Object Store</h4>
 Leave <strong>File Name</strong> as is<br>
 Click <strong>Upload File</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab9-storage-10.png"/> <figcaption>
-            <h4>Lab 9 Figure 10: Upload Form for Adding File to Container</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-10.png"><figcaption>
+      <h4>Lab 9 Figure 10: Upload Form for Adding File to Container</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -458,10 +448,9 @@ <h4>Lab 9 Figure 10: Upload Form for Adding File to Container</h4>
 <p>You should see an info box appear in the upper right corner of the screen that says something similar to &ldquo;Success: File student1.pem uploaded.&rdquo;</p>
 <p>If you did not, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab9-storage-11.png"/> <figcaption>
-            <h4>Lab 9 Figure 11: New Object in Container Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab9-storage-11.png"><figcaption>
+      <h4>Lab 9 Figure 11: New Object in Container Listing</h4>
+    </figcaption>
 </figure>
 
 <h1 id="summary">Summary</h1>
@@ -478,7 +467,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -548,7 +537,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -614,7 +603,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -657,7 +646,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/1_introduction/index.html b/workshops/rhosp_101/1_introduction/index.html
index 56863fcbc..dc11f7939 100644
--- a/workshops/rhosp_101/1_introduction/index.html
+++ b/workshops/rhosp_101/1_introduction/index.html
@@ -315,10 +315,9 @@ <h1>Introduction to Red Hat OpenStack Platform</h1>
 
     <h1 id="red-hat-openstack-platform-overview">Red Hat OpenStack Platform Overview</h1>
 <p>Red Hat OpenStack Platform is implemented as a collection of interacting services that control compute, storage, and networking resources. The following diagram provides a high-level overview of the OpenStack core services.</p>
-<figure>
-    <img src="../images/rhosp-service-overview.png"/> <figcaption>
-            <h4>OpenStack Services Overview</h4>
-        </figcaption>
+<figure><img src="../images/rhosp-service-overview.png"><figcaption>
+      <h4>OpenStack Services Overview</h4>
+    </figcaption>
 </figure>
 
 <ol>
@@ -361,7 +360,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -431,7 +430,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -497,7 +496,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -536,7 +535,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/2_login_to_horizon/index.html b/workshops/rhosp_101/2_login_to_horizon/index.html
index 10af606d0..ffca38220 100644
--- a/workshops/rhosp_101/2_login_to_horizon/index.html
+++ b/workshops/rhosp_101/2_login_to_horizon/index.html
@@ -332,19 +332,17 @@ <h2 id="lets-login">Let&rsquo;s Login</h2>
 <p>Your username, based on the form, is: <b>student<span class="userid">1</span></b></p>
 <p>In the screenshot below, see that this is student1 logging in.</p>
 </div>
-<figure>
-    <img src="../images/lab1-horizon-login-screen.png"/> <figcaption>
-            <h4>Lab 1 Figure 1: RHOSP Horizon Login Screen</h4>
-        </figcaption>
+<figure><img src="../images/lab1-horizon-login-screen.png"><figcaption>
+      <h4>Lab 1 Figure 1: RHOSP Horizon Login Screen</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Once logged in you should see your student project overview.</p>
 </blockquote>
-<figure>
-    <img src="../images/lab1-horizon-project-overview.png"/> <figcaption>
-            <h4>Lab 1 Figure 2: Horizon - Project Overview</h4>
-        </figcaption>
+<figure><img src="../images/lab1-horizon-project-overview.png"><figcaption>
+      <h4>Lab 1 Figure 2: Horizon - Project Overview</h4>
+    </figcaption>
 </figure>
 
 <h2 id="so-this-is-what-an-empty-project-looks-like">So this is what an empty project looks like</h2>
@@ -365,7 +363,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -435,7 +433,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -501,7 +499,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -544,7 +542,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/3_managing_networks/index.html b/workshops/rhosp_101/3_managing_networks/index.html
index 2e696ca63..556783c7f 100644
--- a/workshops/rhosp_101/3_managing_networks/index.html
+++ b/workshops/rhosp_101/3_managing_networks/index.html
@@ -324,10 +324,9 @@ <h1 id="examining-project-network-topology">Examining Project Network Topology</
 <blockquote>
 <p>Navigate to Network -&gt; Network Topology using the second level navigation tabs.</p>
 </blockquote>
-<figure>
-    <img src="../images/lab2-neutron-network-topology-1.png"/> <figcaption>
-            <h4>Lab 2 Figure 1: Neutron Network Topology</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-network-topology-1.png"><figcaption>
+      <h4>Lab 2 Figure 1: Neutron Network Topology</h4>
+    </figcaption>
 </figure>
 
 <p>There are two ways to view the project network layout.</p>
@@ -345,10 +344,9 @@ <h2 id="lets-create-our-first-project-network">Let&rsquo;s Create our First Proj
 Enter <strong>private-a</strong> as the <strong>Network Name</strong><br>
 Leave <strong>Enable Admin State</strong> and <strong>Create Subnet</strong> checked and click <strong>Next</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab2-neutron-create-network-1.png"/> <figcaption>
-            <h4>Lab 2 Figure 2: Create Neutron Network</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-network-1.png"><figcaption>
+      <h4>Lab 2 Figure 2: Create Neutron Network</h4>
+    </figcaption>
 </figure>
 
 <h2 id="next-we-will-create-a-subnet">Next We Will Create a Subnet</h2>
@@ -359,10 +357,9 @@ <h2 id="next-we-will-create-a-subnet">Next We Will Create a Subnet</h2>
 Leave <strong>Gateway IP</strong> blank and make sure <strong>Disable Gateway</strong> is not checked<br>
 Click <strong>Next</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab2-neutron-create-network-2.png"/> <figcaption>
-            <h4>Lab 2 Figure 3: Create Neutron Subnet</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-network-2.png"><figcaption>
+      <h4>Lab 2 Figure 3: Create Neutron Subnet</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-info">
@@ -377,10 +374,9 @@ <h2 id="lastly-we-will-enter-the-details-for-the-subnet">Lastly We Will Enter th
 Enter <strong>192.168.0.4</strong> in <strong>DNS Name Servers</strong><br>
 Leave <strong>Host Routes</strong> empty and click <strong>Create</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab2-neutron-create-network-3.png"/> <figcaption>
-            <h4>Lab 2 Figure 4: Enter Neutron Subnet Details</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-network-3.png"><figcaption>
+      <h4>Lab 2 Figure 4: Enter Neutron Subnet Details</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -389,10 +385,9 @@ <h4>Lab 2 Figure 4: Enter Neutron Subnet Details</h4>
 <p>Note that the success and error messages in Horizon only show briefly and then they disappear.</p>
 <p>If this is not the case, let the instructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab2-neutron-create-network-4.png"/> <figcaption>
-            <h4>Lab 2 Figure 5: Neutron Network Topology Showing New Network private-a</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-network-4.png"><figcaption>
+      <h4>Lab 2 Figure 5: Neutron Network Topology Showing New Network private-a</h4>
+    </figcaption>
 </figure>
 
 <h1 id="lets-tie-these-2-networks-together-with-a-neutron-router-for-layer-3-communication">Let&rsquo;s Tie these 2 Networks Together with a Neutron Router for Layer 3 Communication</h1>
@@ -409,10 +404,9 @@ <h2 id="create-a-neutron-router">Create a Neutron Router</h2>
 <p><span class="pficon pficon-info"></span></p>
 <p>Note that you may need to scroll down to see the public network in the External Network drop down.</p>
 </div>
-<figure>
-    <img src="../images/lab2-neutron-create-router-1.png"/> <figcaption>
-            <h4>Lab 2 Figure 6: Create Neutron Router</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-router-1.png"><figcaption>
+      <h4>Lab 2 Figure 6: Create Neutron Router</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -420,10 +414,9 @@ <h4>Lab 2 Figure 6: Create Neutron Router</h4>
 <p>You should see a green success box in the upper right corner of the screen that says <strong>Success: Router router-public was successfully created.</strong> Your network topology should now show 2 networks, public and private-a and 1 router connected to the public network.</p>
 <p>If this is not the case, let the instructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab2-neutron-create-router-2.png"/> <figcaption>
-            <h4>Lab 2 Figure 7: Neutron Network Topology Showing New Router router-public</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-router-2.png"><figcaption>
+      <h4>Lab 2 Figure 7: Neutron Network Topology Showing New Router router-public</h4>
+    </figcaption>
 </figure>
 
 <h2 id="lastly-lets-add-an-interface-for-the-private-a-network-to-router-public">Lastly Let&rsquo;s Add an Interface for the private-a Network to router-public</h2>
@@ -432,20 +425,18 @@ <h2 id="lastly-lets-add-an-interface-for-the-private-a-network-to-router-public"
 You should see a box pop up with information about the router
 Click <strong>Add Interface</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab2-neutron-create-router-4.png"/> <figcaption>
-            <h4>Lab 2 Figure 8: Router Information Box with Add Interface Button</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-router-4.png"><figcaption>
+      <h4>Lab 2 Figure 8: Router Information Box with Add Interface Button</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Select <strong>private-a</strong> as the <strong>Subnet</strong><br>
 Leave <strong>IP Address</strong> blank and click <strong>Submit</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab2-neutron-create-router-5.png"/> <figcaption>
-            <h4>Lab 2 Figure 9: Add Interface Options</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-router-5.png"><figcaption>
+      <h4>Lab 2 Figure 9: Add Interface Options</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -455,10 +446,9 @@ <h4>Lab 2 Figure 9: Add Interface Options</h4>
 <p>If you navigate back to our network topology, it should now show 2 networks, public and private-a and 1 router connected to both the public and private-a networks.</p>
 <p>If this is not the case, let the instructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab2-neutron-create-router-6.png"/> <figcaption>
-            <h4>Lab 2 Figure 10: Neutron Network Topology Showing router-public Attached to Both Networks</h4>
-        </figcaption>
+<figure><img src="../images/lab2-neutron-create-router-6.png"><figcaption>
+      <h4>Lab 2 Figure 10: Neutron Network Topology Showing router-public Attached to Both Networks</h4>
+    </figcaption>
 </figure>
 
 <h1 id="summary">Summary</h1>
@@ -476,7 +466,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -546,7 +536,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -612,7 +602,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -655,7 +645,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/4_managing_floating_ip_addresses/index.html b/workshops/rhosp_101/4_managing_floating_ip_addresses/index.html
index c00ecf6ce..deed75f1b 100644
--- a/workshops/rhosp_101/4_managing_floating_ip_addresses/index.html
+++ b/workshops/rhosp_101/4_managing_floating_ip_addresses/index.html
@@ -334,10 +334,9 @@ <h1 id="lets-go-allocate-some-floating-ip-addresses">Let&rsquo;s Go Allocate Som
 <blockquote>
 <p>Navigate to Network -&gt; Floating IPs using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab3-floating-ips-1.png"/> <figcaption>
-            <h4>Lab 3 Figure 1: Floating IP Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab3-floating-ips-1.png"><figcaption>
+      <h4>Lab 3 Figure 1: Floating IP Listing</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -345,10 +344,9 @@ <h4>Lab 3 Figure 1: Floating IP Listing</h4>
 Make sure <strong>public</strong> is selected for <strong>Pool</strong><br>
 Click <strong>Allocate IP</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab3-floating-ips-2.png"/> <figcaption>
-            <h4>Lab 3 Figure 2: Allocate Floating IP to Project</h4>
-        </figcaption>
+<figure><img src="../images/lab3-floating-ips-2.png"><figcaption>
+      <h4>Lab 3 Figure 2: Allocate Floating IP to Project</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -357,19 +355,17 @@ <h4>Lab 3 Figure 2: Allocate Floating IP to Project</h4>
 <p>Note that you will get a different IP from the pool each time you go through this process.</p>
 <p>If you did not get an IP allocated, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab3-floating-ips-3.png"/> <figcaption>
-            <h4>Lab 3 Figure 3: New Floating IP Allocated to Project</h4>
-        </figcaption>
+<figure><img src="../images/lab3-floating-ips-3.png"><figcaption>
+      <h4>Lab 3 Figure 3: New Floating IP Allocated to Project</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Go through the allocation process 2 more times so that you have a total of 3 floating IPs allocated to your project</p>
 </blockquote>
-<figure>
-    <img src="../images/lab3-floating-ips-4.png"/> <figcaption>
-            <h4>Lab 3 Figure 4: Floating IP List Showing 3 Allocated to Project</h4>
-        </figcaption>
+<figure><img src="../images/lab3-floating-ips-4.png"><figcaption>
+      <h4>Lab 3 Figure 4: Floating IP List Showing 3 Allocated to Project</h4>
+    </figcaption>
 </figure>
 
 <h1 id="summary">Summary</h1>
@@ -391,7 +387,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -461,7 +457,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -527,7 +523,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -570,7 +566,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/5_managing_security_groups/index.html b/workshops/rhosp_101/5_managing_security_groups/index.html
index 546724edf..3abf9eeb5 100644
--- a/workshops/rhosp_101/5_managing_security_groups/index.html
+++ b/workshops/rhosp_101/5_managing_security_groups/index.html
@@ -334,19 +334,17 @@ <h1 id="lets-look-at-the-default-security-group">Let&rsquo;s Look at the Default
 <blockquote>
 <p>Navigate to Network -&gt; Security Groups using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-1.png"/> <figcaption>
-            <h4>Lab 4 Figure 1: Security Group Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-1.png"><figcaption>
+      <h4>Lab 4 Figure 1: Security Group Listing</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Click <strong>Manage Rules</strong> on the right hand side of the row for default security group</p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-2.png"/> <figcaption>
-            <h4>Lab 4 Figure 2: Viewing Rules for default Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-2.png"><figcaption>
+      <h4>Lab 4 Figure 2: Viewing Rules for default Security Group</h4>
+    </figcaption>
 </figure>
 
 <h2 id="now-lets-add-two-rules-to-the-default-security-group-for-icmp-and-ssh">Now Let&rsquo;s Add Two Rules to the default Security Group for ICMP and SSH</h2>
@@ -358,10 +356,9 @@ <h2 id="now-lets-add-two-rules-to-the-default-security-group-for-icmp-and-ssh">N
 Enter <strong>192.168.0.0/23</strong> for <strong>CIDR</strong> (this is our external network)<br>
 Click <strong>Add</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-3.png"/> <figcaption>
-            <h4>Lab 4 Figure 3: Add ICMP Rule to default Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-3.png"><figcaption>
+      <h4>Lab 4 Figure 3: Add ICMP Rule to default Security Group</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -376,10 +373,9 @@ <h4>Lab 4 Figure 3: Add ICMP Rule to default Security Group</h4>
 Enter <strong>192.168.0.0/23</strong> for <strong>CIDR</strong> (this is our external network)<br>
 Click <strong>Add</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-4.png"/> <figcaption>
-            <h4>Lab 4 Figure 4: Add SSH Rule to default Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-4.png"><figcaption>
+      <h4>Lab 4 Figure 4: Add SSH Rule to default Security Group</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -388,20 +384,18 @@ <h4>Lab 4 Figure 4: Add SSH Rule to default Security Group</h4>
 <p>If you did not see a success message, let the intstructor know now</p>
 </div>
 <p>If we now look at the Manage Rules screen for the default security group, we will see our two new rules for ICMP and SSH ingress traffic allowed only from 192.168.0.0/23 CIDR.</p>
-<figure>
-    <img src="../images/lab4-security-groups-5.png"/> <figcaption>
-            <h4>Lab 4 Figure 5: Manage Rules Screen Showing Two New Rules for ICMP and SSH in the default Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-5.png"><figcaption>
+      <h4>Lab 4 Figure 5: Manage Rules Screen Showing Two New Rules for ICMP and SSH in the default Security Group</h4>
+    </figcaption>
 </figure>
 
 <h1 id="now-we-will-create-a-new-security-group-for-web-servers">Now We will Create a New Security Group for Web Servers</h1>
 <blockquote>
 <p>Navigate to Network -&gt; Security Groups using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-1.png"/> <figcaption>
-            <h4>Lab 4 Figure 1: Security Group Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-1.png"><figcaption>
+      <h4>Lab 4 Figure 1: Security Group Listing</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -410,10 +404,9 @@ <h4>Lab 4 Figure 1: Security Group Listing</h4>
 <strong>Description</strong> is optional, but as you can see below, I used it to describe the purpose of this security group<br>
 Click <strong>Create Security Group</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-6.png"/> <figcaption>
-            <h4>Lab 4 Figure 6: Create a New Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-6.png"><figcaption>
+      <h4>Lab 4 Figure 6: Create a New Security Group</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -421,10 +414,9 @@ <h4>Lab 4 Figure 6: Create a New Security Group</h4>
 <p>You should see a green box appear in the upper right corner of the screen that says &ldquo;Success: Successfully created security group: web-server&rdquo;</p>
 <p>If you did not see a success message, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab4-security-groups-7.png"/> <figcaption>
-            <h4>Lab 4 Figure 7: Security Group Listing Showing New web-server Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-7.png"><figcaption>
+      <h4>Lab 4 Figure 7: Security Group Listing Showing New web-server Group</h4>
+    </figcaption>
 </figure>
 
 <h2 id="now-lets-add-two-rules-to-the-web-server-security-group-for-http-and-https">Now Let&rsquo;s Add Two Rules to the web-server Security Group for HTTP and HTTPS</h2>
@@ -436,10 +428,9 @@ <h2 id="now-lets-add-two-rules-to-the-web-server-security-group-for-http-and-htt
 Leave <strong>0.0.0.0/0</strong> for <strong>CIDR</strong><br>
 Click <strong>Add</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-8.png"/> <figcaption>
-            <h4>Lab 4 Figure 8: Add HTTP Rule to web-server Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-8.png"><figcaption>
+      <h4>Lab 4 Figure 8: Add HTTP Rule to web-server Security Group</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -454,10 +445,9 @@ <h4>Lab 4 Figure 8: Add HTTP Rule to web-server Security Group</h4>
 Enter <strong>0.0.0.0/0</strong> for <strong>CIDR</strong> <br>
 Click <strong>Add</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab4-security-groups-9.png"/> <figcaption>
-            <h4>Lab 4 Figure 9: Add HTTPS Rule to web-server Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-9.png"><figcaption>
+      <h4>Lab 4 Figure 9: Add HTTPS Rule to web-server Security Group</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -466,10 +456,9 @@ <h4>Lab 4 Figure 9: Add HTTPS Rule to web-server Security Group</h4>
 <p>If you did not see a success message, let the intstructor know now</p>
 </div>
 <p>If we now look at the Manage Rules screen for the web-server security group, we will see our two new rules for HTTP and HTTPS ingress traffic allowed from all sources.</p>
-<figure>
-    <img src="../images/lab4-security-groups-10.png"/> <figcaption>
-            <h4>Lab 4 Figure 10: Manage Rules Screen Showing Two New Rules for HTTP and HTTPS in the web-server Security Group</h4>
-        </figcaption>
+<figure><img src="../images/lab4-security-groups-10.png"><figcaption>
+      <h4>Lab 4 Figure 10: Manage Rules Screen Showing Two New Rules for HTTP and HTTPS in the web-server Security Group</h4>
+    </figcaption>
 </figure>
 
 <h1 id="summary">Summary</h1>
@@ -485,7 +474,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -555,7 +544,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -621,7 +610,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -664,7 +653,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/6_managing_images/index.html b/workshops/rhosp_101/6_managing_images/index.html
index d1de66be6..e2b154536 100644
--- a/workshops/rhosp_101/6_managing_images/index.html
+++ b/workshops/rhosp_101/6_managing_images/index.html
@@ -326,10 +326,9 @@ <h1 id="lets-go-upload-a-new-image-to-glance">Let&rsquo;s Go Upload a New Image
 <blockquote>
 <p>Navigate to Compute -&gt; Images using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab5-images-1.png"/> <figcaption>
-            <h4>Lab 5 Figure 1: Project Image Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab5-images-1.png"><figcaption>
+      <h4>Lab 5 Figure 1: Project Image Listing</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-info">
@@ -350,10 +349,9 @@ <h4>Lab 5 Figure 1: Project Image Listing</h4>
 Leave <strong>Protected</strong> set to <strong>No</strong><br>
 Click <strong>Create Image</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab5-images-2.png"/> <figcaption>
-            <h4>Lab 5 Figure 2: Details for New cirros Image</h4>
-        </figcaption>
+<figure><img src="../images/lab5-images-2.png"><figcaption>
+      <h4>Lab 5 Figure 2: Details for New cirros Image</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-info">
@@ -366,10 +364,9 @@ <h4>Lab 5 Figure 2: Details for New cirros Image</h4>
 <p>After a little bit, You should see a green box appear in the upper right corner of the screen that says something similar to &ldquo;Success: Image student<span class="userid">1</span>-cirros was successfully created.&rdquo;</p>
 <p>If you did not, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab5-images-3.png"/> <figcaption>
-            <h4>Lab 5 Figure 4: New Image Uploaded to Glance and Available to Project</h4>
-        </figcaption>
+<figure><img src="../images/lab5-images-3.png"><figcaption>
+      <h4>Lab 5 Figure 4: New Image Uploaded to Glance and Available to Project</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-info">
@@ -390,7 +387,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -460,7 +457,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -526,7 +523,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -569,7 +566,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/7_managing_instances/index.html b/workshops/rhosp_101/7_managing_instances/index.html
index 7c9e1d9dc..24c7bca16 100644
--- a/workshops/rhosp_101/7_managing_instances/index.html
+++ b/workshops/rhosp_101/7_managing_instances/index.html
@@ -333,26 +333,23 @@ <h1 id="second-we-need-a-key-pair-before-we-launch-our-first-instance">Second. W
 <blockquote>
 <p>Click <strong>Create Key Pair</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-keypair-1.png"/> <figcaption>
-            <h4>Lab 6 Figure 1: Key Pair list</h4>
-        </figcaption>
+<figure><img src="../images/lab6-keypair-1.png"><figcaption>
+      <h4>Lab 6 Figure 1: Key Pair list</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Enter <strong>student<span class="userid">1</span></strong> for <strong>Key Pair Name</strong><br>
 Click <strong>Create Keypair</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-keypair-2.png"/> <figcaption>
-            <h4>Lab 6 Figure 2: Create New Key Pair</h4>
-        </figcaption>
+<figure><img src="../images/lab6-keypair-2.png"><figcaption>
+      <h4>Lab 6 Figure 2: Create New Key Pair</h4>
+    </figcaption>
 </figure>
 
-<figure>
-    <img src="../images/lab6-keypair-3.png"/> <figcaption>
-            <h4>Lab 6 Figure 3: Key Pair list showing new key pair</h4>
-        </figcaption>
+<figure><img src="../images/lab6-keypair-3.png"><figcaption>
+      <h4>Lab 6 Figure 3: Key Pair list showing new key pair</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-warning">
@@ -364,10 +361,9 @@ <h1 id="lets-go-launch-a-new-instance">Let&rsquo;s Go Launch a New Instance</h1>
 <blockquote>
 <p>Navigate to Compute -&gt; Instances using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-1.png"/> <figcaption>
-            <h4>Lab 6 Figure 4: Project Instance Listing</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-1.png"><figcaption>
+      <h4>Lab 6 Figure 4: Project Instance Listing</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -377,10 +373,9 @@ <h4>Lab 6 Figure 4: Project Instance Listing</h4>
 Enter <strong>2</strong> for <strong>Count</strong><br>
 Click <strong>Next</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-2.png"/> <figcaption>
-            <h4>Lab 6 Figure 5: Details for New Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-2.png"><figcaption>
+      <h4>Lab 6 Figure 5: Details for New Instance</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
@@ -389,50 +384,45 @@ <h4>Lab 6 Figure 5: Details for New Instance</h4>
 Click the <strong>Up Arrow</strong> symbol to the right of <strong>student<span class="userid">1</span>-cirros</strong> to move that image up to the <strong>Allocated</strong> section <br>
 Click <strong>Next</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-3.png"/> <figcaption>
-            <h4>Lab 6 Figure 6: Source for New Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-3.png"><figcaption>
+      <h4>Lab 6 Figure 6: Source for New Instance</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Click the <strong>Up Arrow</strong> symbol to the right of <strong>m1.tiny</strong> to move that flavor up to the <strong>Allocated</strong> section <br>
 Click <strong>Next</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-4.png"/> <figcaption>
-            <h4>Lab 6 Figure 7: Flavor for New Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-4.png"><figcaption>
+      <h4>Lab 6 Figure 7: Flavor for New Instance</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Click the <strong>Up Arrow</strong> symbol to the right of <strong>private-a</strong> to move that network up to the <strong>Allocated</strong> section <br>
 Click on <strong>Security Groups</strong> in the left list of options on with dialog</p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-5.png"/> <figcaption>
-            <h4>Lab 6 Figure 8: Networks for New Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-5.png"><figcaption>
+      <h4>Lab 6 Figure 8: Networks for New Instance</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Leave the <strong>default</strong> security group allocated<br>
 Click <strong>Next</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-6.png"/> <figcaption>
-            <h4>Lab 6 Figure 9: Security Groups for New Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-6.png"><figcaption>
+      <h4>Lab 6 Figure 9: Security Groups for New Instance</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>You can ignore the rest of the option pages<br>
 Click <strong>Launch Instance</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-9.png"/> <figcaption>
-            <h4>Lab 6 Figure 10: Key Pair Selected and Launching New Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-9.png"><figcaption>
+      <h4>Lab 6 Figure 10: Key Pair Selected and Launching New Instance</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -445,10 +435,9 @@ <h4>Lab 6 Figure 10: Key Pair Selected and Launching New Instance</h4>
 <p>The instances will take a little while to become active.</p>
 <p>If for some reason they do not, let the instructor know</p>
 </div>
-<figure>
-    <img src="../images/lab6-instances-10.png"/> <figcaption>
-            <h4>Lab 6 Figure 11: New Instances Created and Active in Project</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-10.png"><figcaption>
+      <h4>Lab 6 Figure 11: New Instances Created and Active in Project</h4>
+    </figcaption>
 </figure>
 
 <h1 id="now-lets-associate-a-floating-ip-address-with-one-of-our-instances">Now Let&rsquo;s Associate a Floating IP Address with one of our instances</h1>
@@ -459,10 +448,9 @@ <h1 id="now-lets-associate-a-floating-ip-address-with-one-of-our-instances">Now
 Leave <strong>Port to be Associated</strong> as is<br>
 Click <strong>Associate</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab6-instances-fip-1.png"/> <figcaption>
-            <h4>Lab 6 Figure 12: Selecting Floating IP to Associate with Our Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-fip-1.png"><figcaption>
+      <h4>Lab 6 Figure 12: Selecting Floating IP to Associate with Our Instance</h4>
+    </figcaption>
 </figure>
 
 <div class="alert alert-success">
@@ -471,16 +459,14 @@ <h4>Lab 6 Figure 12: Selecting Floating IP to Associate with Our Instance</h4>
 <p>Note that your floating IP will be a different address than the one shown here.</p>
 <p>If you did not, let the intstructor know now</p>
 </div>
-<figure>
-    <img src="../images/lab6-instances-fip-2.png"/> <figcaption>
-            <h4>Lab 6 Figure 13: Floating IP Address Associated with Our Instance</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-fip-2.png"><figcaption>
+      <h4>Lab 6 Figure 13: Floating IP Address Associated with Our Instance</h4>
+    </figcaption>
 </figure>
 
-<figure>
-    <img src="../images/lab6-instances-network-topology.png"/> <figcaption>
-            <h4>Lab 6 Figure 14: Network Topology Showing Two New Instances</h4>
-        </figcaption>
+<figure><img src="../images/lab6-instances-network-topology.png"><figcaption>
+      <h4>Lab 6 Figure 14: Network Topology Showing Two New Instances</h4>
+    </figcaption>
 </figure>
 
 <h1 id="summary">Summary</h1>
@@ -497,7 +483,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -567,7 +553,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -633,7 +619,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -676,7 +662,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/8_using_the_cli/index.html b/workshops/rhosp_101/8_using_the_cli/index.html
index 0b954fefa..e27eee3c0 100644
--- a/workshops/rhosp_101/8_using_the_cli/index.html
+++ b/workshops/rhosp_101/8_using_the_cli/index.html
@@ -342,7 +342,7 @@ <h2 id="first-we-need-access-to-a-system-with-the-clis-installed">First, We Need
 <blockquote>
 <p>On Linux or Mac, in your terminal, ssh to 192.168.1.90 on port 22</p>
 </blockquote>
-<pre><code>$ ssh student<span class="userid">1</span>@192.168.1.90
+<pre tabindex="0"><code>$ ssh student<span class="userid">1</span>@192.168.1.90
 </code></pre><p>If on Windows, run putty, enter <strong>192.168.1.90</strong> as the host and <strong>22</strong> as the port.</p>
 <p>You will get asked if you are sure you want to connect. Type <strong>yes</strong> and hit enter.</p>
 <p>Login with your <strong>student<span class="userid">1</span></strong> credentials.</p>
@@ -350,13 +350,13 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>Source your student<span class="userid">1</span>rc file</p>
 </blockquote>
-<pre><code>$ source student<span class="userid">1</span>rc
+<pre tabindex="0"><code>$ source student<span class="userid">1</span>rc
 </code></pre><blockquote>
 <p>Verify that you are connected by running openstack server list</p>
 </blockquote>
-<pre><code>$ openstack server list
+<pre tabindex="0"><code>$ openstack server list
 </code></pre><p>You should see the two instances you created in the previous lab.</p>
-<pre><code>(overcloud) [student1@bastion ~]$ openstack server list
+<pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack server list
 +--------------------------------------+-------------------+--------+-------------------------------------+-----------------+---------+
 | ID                                   | Name              | Status | Networks                            | Image           | Flavor  |
 +--------------------------------------+-------------------+--------+-------------------------------------+-----------------+---------+
@@ -367,17 +367,17 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>First we&rsquo;ll download the image using curl</p>
 </blockquote>
-<pre><code>$ curl -o ~/cirros.img http://192.168.0.8/images/cirros.img
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ curl -o ~/cirros.img http://192.168.0.8/images/cirros.img
+<pre tabindex="0"><code>$ curl -o ~/cirros.img http://192.168.0.8/images/cirros.img
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ curl -o ~/cirros.img http://192.168.0.8/images/cirros.img
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed
 100 44.0M  100 44.0M    0     0   103M      0 --:--:-- --:--:-- --:--:--  103M
 </code></pre><blockquote>
 <p>Upload the cirros test image to glance</p>
 </blockquote>
-<pre><code>
+<pre tabindex="0"><code>
 $ openstack image create --disk-format raw --container-format bare --private --min-disk 1 --min-ram 64 --file ~/cirros.img student<span class="userid">1</span>-cirros-cli
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack image create --disk-format raw --container-format bare --private --min-disk 1 --min-ram 64 --file ~/cirros.img student1-cirros-cli
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack image create --disk-format raw --container-format bare --private --min-disk 1 --min-ram 64 --file ~/cirros.img student1-cirros-cli
 +------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | Field            | Value                                                                                                                                                                                                                                             |
 +------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@@ -391,7 +391,7 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 | min_ram          | 64                                                                                                                                                                                                                                                |
 | name             | student1-cirros-cli                                                                                                                                                                                                                               |
 | owner            | b32431890c454e55920e7bc50b6ddba3                                                                                                                                                                                                                  |
-| properties       | direct_url='rbd://fcd7abfc-9f3e-11e9-8480-52540035d3ce/images/8ac9ad11-8de3-477c-96f7-184f784ed629/snap', locations='[{u'url': u'rbd://fcd7abfc-9f3e-11e9-8480-52540035d3ce/images/8ac9ad11-8de3-477c-96f7-184f784ed629/snap', u'metadata': {}}]' |
+| properties       | direct_url=&#39;rbd://fcd7abfc-9f3e-11e9-8480-52540035d3ce/images/8ac9ad11-8de3-477c-96f7-184f784ed629/snap&#39;, locations=&#39;[{u&#39;url&#39;: u&#39;rbd://fcd7abfc-9f3e-11e9-8480-52540035d3ce/images/8ac9ad11-8de3-477c-96f7-184f784ed629/snap&#39;, u&#39;metadata&#39;: {}}]&#39; |
 | protected        | False                                                                                                                                                                                                                                             |
 | schema           | /v2/schemas/image                                                                                                                                                                                                                                 |
 | size             | 46137344                                                                                                                                                                                                                                          |
@@ -405,8 +405,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>Run openstack image list to see the available images</p>
 </blockquote>
-<pre><code>$ openstack image list
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack image list
+<pre tabindex="0"><code>$ openstack image list
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack image list
 +--------------------------------------+---------------------+--------+
 | ID                                   | Name                | Status |
 +--------------------------------------+---------------------+--------+
@@ -422,8 +422,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>Run the following command to see the existing flavors</p>
 </blockquote>
-<pre><code>$ openstack flavor list
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack flavor list
+<pre tabindex="0"><code>$ openstack flavor list
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack flavor list
 +----+-------------+-------+------+-----------+-------+-----------+
 | ID | Name        |   RAM | Disk | Ephemeral | VCPUs | Is Public |
 +----+-------------+-------+------+-----------+-------+-----------+
@@ -441,8 +441,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>List the existing floating IP addresses</p>
 </blockquote>
-<pre><code>$ openstack floating ip list
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack floating ip list
+<pre tabindex="0"><code>$ openstack floating ip list
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack floating ip list
 +--------------------------------------+---------------------+------------------+--------------------------------------+--------------------------------------+----------------------------------+
 | ID                                   | Floating IP Address | Fixed IP Address | Port                                 | Floating Network                     | Project                          |
 +--------------------------------------+---------------------+------------------+--------------------------------------+--------------------------------------+----------------------------------+
@@ -454,8 +454,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>First create the network</p>
 </blockquote>
-<pre><code>$ openstack network create private-b
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack network create private-b
+<pre tabindex="0"><code>$ openstack network create private-b
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack network create private-b
 +---------------------------+--------------------------------------+
 | Field                     | Value                                |
 +---------------------------+--------------------------------------+
@@ -490,8 +490,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 </code></pre><blockquote>
 <p>Then let&rsquo;s create the private-b subnet</p>
 </blockquote>
-<pre><code>$ openstack subnet create --network private-b --subnet-range 172.16.1.0/24 --dns-nameserver 192.168.0.4 private-b-subnet
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack subnet create --network private-b --subnet-range 172.16.1.0/24 --dns-nameserver 192.168.0.4 private-b-subnet
+<pre tabindex="0"><code>$ openstack subnet create --network private-b --subnet-range 172.16.1.0/24 --dns-nameserver 192.168.0.4 private-b-subnet
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack subnet create --network private-b --subnet-range 172.16.1.0/24 --dns-nameserver 192.168.0.4 private-b-subnet
 +-------------------+--------------------------------------+
 | Field             | Value                                |
 +-------------------+--------------------------------------+
@@ -520,8 +520,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 </code></pre><blockquote>
 <p>List the Neutron Networks and Subnets</p>
 </blockquote>
-<pre><code>$ openstack network list &amp;&amp; openstack subnet list
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack network list &amp;&amp; openstack subnet list
+<pre tabindex="0"><code>$ openstack network list &amp;&amp; openstack subnet list
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack network list &amp;&amp; openstack subnet list
 +--------------------------------------+-----------+--------------------------------------+
 | ID                                   | Name      | Subnets                              |
 +--------------------------------------+-----------+--------------------------------------+
@@ -541,8 +541,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <p>Run the following command to boot a nova instance using the m1.tiny flavor, and the newest cirros image that we uploaded earlier in this lab.<br>
 We will also attach it to the new <strong>private-b</strong> network</p>
 </blockquote>
-<pre><code>$ openstack server create --image student<span class="userid">1</span>-cirros-cli --flavor m1.tiny --key-name student<span class="userid">1</span> --network private-b student<span class="userid">1</span>-cirros-cli-1
-</code></pre><pre><code>(overcloud) [student1@bastion ~]$ openstack server create --image student1-cirros-cli --flavor m1.tiny --key-name student1 --network private-b student1-cirros-cli-1
+<pre tabindex="0"><code>$ openstack server create --image student<span class="userid">1</span>-cirros-cli --flavor m1.tiny --key-name student<span class="userid">1</span> --network private-b student<span class="userid">1</span>-cirros-cli-1
+</code></pre><pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack server create --image student1-cirros-cli --flavor m1.tiny --key-name student1 --network private-b student1-cirros-cli-1
 +-----------------------------+------------------------------------------------------------+
 | Field                       | Value                                                      |
 +-----------------------------+------------------------------------------------------------+
@@ -568,7 +568,7 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 | progress                    | 0                                                          |
 | project_id                  | b32431890c454e55920e7bc50b6ddba3                           |
 | properties                  |                                                            |
-| security_groups             | name='default'                                             |
+| security_groups             | name=&#39;default&#39;                                             |
 | status                      | BUILD                                                      |
 | updated                     | 2019-07-13T20:33:27Z                                       |
 | user_id                     | 1ae2f6781ade4af384fe770c135847b3                           |
@@ -577,8 +577,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 </code></pre><blockquote>
 <p>You can watch openstack server list to see it go through the provisioning process and become active</p>
 </blockquote>
-<pre><code>$ watch openstack server list
-</code></pre><pre><code>Every 2.0s: openstack server list                                                                                                                                                                                      Sat Jul 13 16:39:03 2019
+<pre tabindex="0"><code>$ watch openstack server list
+</code></pre><pre tabindex="0"><code>Every 2.0s: openstack server list                                                                                                                                                                                      Sat Jul 13 16:39:03 2019
 
 +--------------------------------------+-----------------------+--------+-------------------------------------+---------------------+---------+
 | ID                                   | Name                  | Status | Networks                            | Image               | Flavor  |
@@ -600,7 +600,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -670,7 +670,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -736,7 +736,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -779,7 +779,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/9_heat/index.html b/workshops/rhosp_101/9_heat/index.html
index bb1ac2b63..9bb473894 100644
--- a/workshops/rhosp_101/9_heat/index.html
+++ b/workshops/rhosp_101/9_heat/index.html
@@ -332,7 +332,7 @@ <h2 id="first-we-need-access-to-a-system-with-the-clis-installed">First, We Need
 <blockquote>
 <p>On Linux or Mac, in your terminal, ssh to 192.168.1.90 on port 22</p>
 </blockquote>
-<pre><code>$ ssh student<span class="userid">1</span>@192.168.1.90
+<pre tabindex="0"><code>$ ssh student<span class="userid">1</span>@192.168.1.90
 </code></pre><p>If on Windows, run putty, enter <strong>192.168.1.90</strong> as the host and <strong>22</strong> as the port.</p>
 <p>You will get asked if you are sure you want to connect. Type <strong>yes</strong> and hit enter.</p>
 <p>Login with your <strong>student<span class="userid">1</span></strong> credentials.</p>
@@ -340,13 +340,13 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>Source your student<span class="userid">1</span>rc file</p>
 </blockquote>
-<pre><code>$ source student<span class="userid">1</span>rc
+<pre tabindex="0"><code>$ source student<span class="userid">1</span>rc
 </code></pre><blockquote>
 <p>Verify that you are connected by running nova list</p>
 </blockquote>
-<pre><code>$ openstack server list
+<pre tabindex="0"><code>$ openstack server list
 </code></pre><p>You should see the instances you created in the previous labs.</p>
-<pre><code>(overcloud) [student1@bastion ~]$ openstack server list
+<pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack server list
 +--------------------------------------+-----------------------+--------+-------------------------------------+---------------------+---------+
 | ID                                   | Name                  | Status | Networks                            | Image               | Flavor  |
 +--------------------------------------+-----------------------+--------+-------------------------------------+---------------------+---------+
@@ -355,7 +355,7 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 | cbd781be-cc64-4302-b15c-5a7ae805a917 | student1-cirros-2     | ACTIVE | private-a=172.16.0.14               | student1-cirros     | m1.tiny |
 +--------------------------------------+-----------------------+--------+-------------------------------------+---------------------+---------+
 </code></pre><h2 id="now-lets-examine-the-heat-template">Now Let&rsquo;s Examine the Heat Template</h2>
-<pre><code>(overcloud) [student1@bastion ~]$ cat heat-example.yaml 
+<pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ cat heat-example.yaml 
 heat_template_version: 2014-10-16  
 description: A simple server.  
 parameters:
@@ -383,7 +383,7 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
           delete_on_termination: true
           volume_id: { get_resource: volume }
       flavor: {get_param: flavor}
-      metadata: {&quot;metering.stack&quot;: {get_param: &quot;OS::stack_id&quot;}}
+      metadata: {&#34;metering.stack&#34;: {get_param: &#34;OS::stack_id&#34;}}
       key_name: {get_param: keypair}
       networks:
         - port: { get_resource: port }
@@ -414,9 +414,9 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 </code></pre><blockquote>
 <p>Let&rsquo;s Launch a Heat Stack with this Template</p>
 </blockquote>
-<pre><code>$ openstack stack create --parameter keypair=student<span class="userid">1</span> --parameter image=rhel76 -t heat-example.yaml student<span class="userid">1</span>-stack
+<pre tabindex="0"><code>$ openstack stack create --parameter keypair=student<span class="userid">1</span> --parameter image=rhel76 -t heat-example.yaml student<span class="userid">1</span>-stack
 </code></pre><p>Here is an example run.</p>
-<pre><code>(overcloud) [student1@bastion ~]$ openstack stack create --parameter keypair=student1 --parameter image=rhel76 -t heat-example.yaml student1-stack
+<pre tabindex="0"><code>(overcloud) [student1@bastion ~]$ openstack stack create --parameter keypair=student1 --parameter image=rhel76 -t heat-example.yaml student1-stack
 +---------------------+--------------------------------------+
 | Field               | Value                                |
 +---------------------+--------------------------------------+
@@ -431,8 +431,8 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 </code></pre><blockquote>
 <p>You can watch stack list to see the stack go through the provisioning process and become CREATE_COMPLETE</p>
 </blockquote>
-<pre><code>$ watch openstack stack list
-</code></pre><pre><code>Every 2.0s: openstack stack list                                                               Sat Jul 13 17:13:58 2019
+<pre tabindex="0"><code>$ watch openstack stack list
+</code></pre><pre tabindex="0"><code>Every 2.0s: openstack stack list                                                               Sat Jul 13 17:13:58 2019
 
 +--------------------------------------+----------------+-----------------+----------------------+--------------+
 | ID                                   | Stack Name     | Stack Status    | Creation Time        | Updated Time |
@@ -443,29 +443,26 @@ <h2 id="lets-autenticate-to-the-openstack-cloud">Let&rsquo;s Autenticate to the
 <blockquote>
 <p>Navigate to Orchestration -&gt; Stacks using the second level navigation tabs</p>
 </blockquote>
-<figure>
-    <img src="../images/lab8-heat-1.png"/> <figcaption>
-            <h4>Lab 8 Figure 1: Heat Stack List</h4>
-        </figcaption>
+<figure><img src="../images/lab8-heat-1.png"><figcaption>
+      <h4>Lab 8 Figure 1: Heat Stack List</h4>
+    </figcaption>
 </figure>
 
 <blockquote>
 <p>Click on <strong>student<span class="userid">1</span>-stack</strong></p>
 </blockquote>
-<figure>
-    <img src="../images/lab8-heat-2.png"/> <figcaption>
-            <h4>Lab 8 Figure 2: Heat Stack Topology for the New student1-stack</h4>
-        </figcaption>
+<figure><img src="../images/lab8-heat-2.png"><figcaption>
+      <h4>Lab 8 Figure 2: Heat Stack Topology for the New student1-stack</h4>
+    </figcaption>
 </figure>
 
 <h1 id="examining-project-network-topology">Examining Project Network Topology</h1>
 <blockquote>
 <p>Navigate to Network -&gt; Network Topology using the second level navigation tabs.</p>
 </blockquote>
-<figure>
-    <img src="../images/lab8-heat-3.png"/> <figcaption>
-            <h4>Lab 8 Figure 3: Neutron Network Topology</h4>
-        </figcaption>
+<figure><img src="../images/lab8-heat-3.png"><figcaption>
+      <h4>Lab 8 Figure 3: Neutron Network Topology</h4>
+    </figcaption>
 </figure>
 
 <h1 id="summary">Summary</h1>
@@ -482,7 +479,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -552,7 +549,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -618,7 +615,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -661,7 +658,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/fin/index.html b/workshops/rhosp_101/fin/index.html
index 81f735527..fd14d9188 100644
--- a/workshops/rhosp_101/fin/index.html
+++ b/workshops/rhosp_101/fin/index.html
@@ -367,7 +367,7 @@ <h1 id="get-even-deeper">Get even deeper</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/index.html b/workshops/rhosp_101/index.html
index ac9b17ba0..c192f12db 100644
--- a/workshops/rhosp_101/index.html
+++ b/workshops/rhosp_101/index.html
@@ -407,7 +407,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -477,7 +477,7 @@ <h3>Workshop Details</h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -543,7 +543,7 @@ <h3>Workshop Details</h3>
 
     return false;
   });
--->
+
 </script>
 
 
@@ -553,7 +553,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/rhosp_101/index.xml b/workshops/rhosp_101/index.xml
index f0369c4fb..c34727bc3 100644
--- a/workshops/rhosp_101/index.xml
+++ b/workshops/rhosp_101/index.xml
@@ -4,126 +4,85 @@
     <title>Red Hat OpenStack Platform 101 on Red Hat | Public Sector</title>
     <link>/workshops/rhosp_101/</link>
     <description>Recent content in Red Hat OpenStack Platform 101 on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/rhosp_101/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/rhosp_101/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Fin.</title>
       <link>/workshops/rhosp_101/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/fin/</guid>
-      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenStack environment. And hopefully, you have a deeper understanding of how Infrastructure-as-a-Service works.
-Get even deeper Here are some good resources to continue learning OpenStack:
- OpenStack Foundation RDO Project - Our midstream, open source OpenStack distrobution for RHEL variants Red Hat OpenStack Platform Official Docs  There are two ways to get started with RDO: TripleO Quickstart and PackStack</description>
+      <description>That&amp;rsquo;s it! Hopefully, these labs provided you some idea of how to perform common tasks within the OpenStack environment. And hopefully, you have a deeper understanding of how Infrastructure-as-a-Service works.&#xA;Get even deeper Here are some good resources to continue learning OpenStack:&#xA;OpenStack Foundation RDO Project - Our midstream, open source OpenStack distrobution for RHEL variants Red Hat OpenStack Platform Official Docs There are two ways to get started with RDO: TripleO Quickstart and PackStack</description>
     </item>
-    
     <item>
       <title>Introduction to Red Hat OpenStack Platform</title>
       <link>/workshops/rhosp_101/1_introduction/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/1_introduction/</guid>
-      <description>Red Hat OpenStack Platform Overview Red Hat OpenStack Platform is implemented as a collection of interacting services that control compute, storage, and networking resources. The following diagram provides a high-level overview of the OpenStack core services.
-  OpenStack Services Overview    Horizon - User interface built to give a graphical way to interact with OpenStack services Keystone - Identity management service for projects, users, groups, roles, endpoints, etc.</description>
+      <description>Red Hat OpenStack Platform Overview Red Hat OpenStack Platform is implemented as a collection of interacting services that control compute, storage, and networking resources. The following diagram provides a high-level overview of the OpenStack core services.&#xA;OpenStack Services Overview Horizon - User interface built to give a graphical way to interact with OpenStack services Keystone - Identity management service for projects, users, groups, roles, endpoints, etc. Neutron - Software defined networking API service that can be backed by different SDN solutions.</description>
     </item>
-    
     <item>
       <title>Lab 1 - Login to Horizon</title>
       <link>/workshops/rhosp_101/2_login_to_horizon/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/2_login_to_horizon/</guid>
-      <description>Welcome to Red Hat OpenStack Platform (RHOSP)! This lab provides a quick tour of the Horizon dashboard to help you get familiar with the user interface. If you are already familiar with the basics of Horizon simply ensure you can login and have access to your student project.
-Accessing Horizon RHOSP provides a web dashboard that allows you to perform various tasks via a web browser. Let&amp;rsquo;s get started by logging into Horizon and checking the status of the platform.</description>
+      <description>Welcome to Red Hat OpenStack Platform (RHOSP)! This lab provides a quick tour of the Horizon dashboard to help you get familiar with the user interface. If you are already familiar with the basics of Horizon simply ensure you can login and have access to your student project.&#xA;Accessing Horizon RHOSP provides a web dashboard that allows you to perform various tasks via a web browser. Let&amp;rsquo;s get started by logging into Horizon and checking the status of the platform.</description>
     </item>
-    
     <item>
       <title>Lab 2 - Managing Neutron Networks</title>
       <link>/workshops/rhosp_101/3_managing_networks/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/3_managing_networks/</guid>
-      <description>Neutron - Overlay Networking for OpenStack Neutron is an OpenStack project to provide &amp;ldquo;networking as a service&amp;rdquo; between interface devices (e.g., vNICs) managed by other Openstack services (e.g., nova).
-Starting in the Folsom release, Neutron is a core and supported part of the OpenStack platform.
-Examining Project Network Topology  Navigate to Network -&amp;gt; Network Topology using the second level navigation tabs.
-   Lab 2 Figure 1: Neutron Network Topology   There are two ways to view the project network layout.</description>
+      <description>Neutron - Overlay Networking for OpenStack Neutron is an OpenStack project to provide &amp;ldquo;networking as a service&amp;rdquo; between interface devices (e.g., vNICs) managed by other Openstack services (e.g., nova).&#xA;Starting in the Folsom release, Neutron is a core and supported part of the OpenStack platform.&#xA;Examining Project Network Topology Navigate to Network -&amp;gt; Network Topology using the second level navigation tabs.&#xA;Lab 2 Figure 1: Neutron Network Topology There are two ways to view the project network layout.</description>
     </item>
-    
     <item>
       <title>Lab 3 - Managing Floating IP Addresses</title>
       <link>/workshops/rhosp_101/4_managing_floating_ip_addresses/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/4_managing_floating_ip_addresses/</guid>
       <description>Floating IP vs. Private IP Addresses Private IP Address A private IP address is assigned to an instance&amp;rsquo;s network-interface by the DHCP server. The address is visible from within the instance by using a command like “ip a”. The address is typically part of a private network and is used for communication between instances in the same broadcast domain via virtual switch (L2 agent on each compute node). It can also be accessible from instances in other private networks via virtual router (L3 agent).</description>
     </item>
-    
     <item>
       <title>Lab 4 - Managing Security Groups</title>
       <link>/workshops/rhosp_101/5_managing_security_groups/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/5_managing_security_groups/</guid>
-      <description>Security Groups in OpenStack A security group is a named collection of network access rules that are used to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group.
-The associated rules in each security group control the traffic to instances in the group.</description>
+      <description>Security Groups in OpenStack A security group is a named collection of network access rules that are used to limit the types of traffic that have access to instances. When you launch an instance, you can assign one or more security groups to it. If you do not create security groups, new instances are automatically assigned to the default security group, unless you explicitly specify a different security group.&#xA;The associated rules in each security group control the traffic to instances in the group.</description>
     </item>
-    
     <item>
       <title>Lab 5 - Managing Images</title>
       <link>/workshops/rhosp_101/6_managing_images/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/6_managing_images/</guid>
-      <description>Where Shall We Store Our Golden Images? Glance The Image service (glance) project provides a service where users can upload and discover data assets that are meant to be used with other services. This currently includes images and metadata definitions.
-Glance image services include discovering, registering, and retrieving virtual machine (VM) images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image.</description>
+      <description>Where Shall We Store Our Golden Images? Glance The Image service (glance) project provides a service where users can upload and discover data assets that are meant to be used with other services. This currently includes images and metadata definitions.&#xA;Glance image services include discovering, registering, and retrieving virtual machine (VM) images. Glance has a RESTful API that allows querying of VM image metadata as well as retrieval of the actual image.</description>
     </item>
-    
     <item>
       <title>Lab 6 - Managing Instances</title>
       <link>/workshops/rhosp_101/7_managing_instances/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/7_managing_instances/</guid>
-      <description>Now We are Ready to Launch an OpenStack Instance First, What is an Instance? Instances are virtual machines that run inside the OpenStack cloud. You can launch an instance from the following sources:
- Images uploaded to the Image service Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the cinder-volume API Instance snapshot that you took  Second. We need a key pair before we launch our first instance  Navigate to Compute -&amp;gt; Key Pairs using the second level navigation tabs</description>
+      <description>Now We are Ready to Launch an OpenStack Instance First, What is an Instance? Instances are virtual machines that run inside the OpenStack cloud. You can launch an instance from the following sources:&#xA;Images uploaded to the Image service Image that you have copied to a persistent volume. The instance launches from the volume, which is provided by the cinder-volume API Instance snapshot that you took Second. We need a key pair before we launch our first instance Navigate to Compute -&amp;gt; Key Pairs using the second level navigation tabs</description>
     </item>
-    
     <item>
       <title>Lab 7 - Using the OpenStack CLI(s)</title>
       <link>/workshops/rhosp_101/8_using_the_cli/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/8_using_the_cli/</guid>
-      <description>Okay. UIs Are Cool and All, But Can&amp;rsquo;t I Just Use the CLI? Absolutely! There are 3 ways to interact with OpenStack.
- API CLI GUI  In this lab, we are going to walk through some of the activities that we did in the previous labs via the CLI.
-
-When you see a CLI command starting with openstack, the command is part of the Unified CLI.
-When you see a CLI command that starts with a project name like nova, these are the individual CLIs.</description>
+      <description>Okay. UIs Are Cool and All, But Can&amp;rsquo;t I Just Use the CLI? Absolutely! There are 3 ways to interact with OpenStack.&#xA;API CLI GUI In this lab, we are going to walk through some of the activities that we did in the previous labs via the CLI.&#xA;When you see a CLI command starting with openstack, the command is part of the Unified CLI.&#xA;When you see a CLI command that starts with a project name like nova, these are the individual CLIs.</description>
     </item>
-    
     <item>
       <title>Lab 8 - Using Heat to Describe Stacks</title>
       <link>/workshops/rhosp_101/9_heat/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/9_heat/</guid>
-      <description>We Have Done a Ton of Stuff, But All Manually. How Do We Orchestrate? In OpenStack, the answer to that is Heat.
-Heat is the main project for orchestration in OpenStack. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code. A native Heat template format is evolving, but Heat also endeavours to provide compatibility with the AWS CloudFormation template format, so that many existing CloudFormation templates can be launched on OpenStack.</description>
+      <description>We Have Done a Ton of Stuff, But All Manually. How Do We Orchestrate? In OpenStack, the answer to that is Heat.&#xA;Heat is the main project for orchestration in OpenStack. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code. A native Heat template format is evolving, but Heat also endeavours to provide compatibility with the AWS CloudFormation template format, so that many existing CloudFormation templates can be launched on OpenStack.</description>
     </item>
-    
     <item>
       <title>Lab 9 - Managing Block and Object Storage</title>
       <link>/workshops/rhosp_101/10_storage/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/rhosp_101/10_storage/</guid>
-      <description>Working With Block and Object Storage in OpenStack Block Storage is Handled by Cinder The OpenStack Block Storage service works through the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. You can run all the binaries from a single node, or spread across multiple nodes. You can also run them on the same node as other OpenStack services.
-To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts.</description>
+      <description>Working With Block and Object Storage in OpenStack Block Storage is Handled by Cinder The OpenStack Block Storage service works through the interaction of a series of daemon processes named cinder-* that reside persistently on the host machine or machines. You can run all the binaries from a single node, or spread across multiple nodes. You can also run them on the same node as other OpenStack services.&#xA;To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/secure_software_factory/fin/index.html b/workshops/secure_software_factory/fin/index.html
index e1b19c0c6..1d18f9958 100644
--- a/workshops/secure_software_factory/fin/index.html
+++ b/workshops/secure_software_factory/fin/index.html
@@ -350,7 +350,7 @@ <h1 id="thats-it">That&rsquo;s it!</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/index.html b/workshops/secure_software_factory/index.html
index 8a7b43c34..f28b8292b 100644
--- a/workshops/secure_software_factory/index.html
+++ b/workshops/secure_software_factory/index.html
@@ -537,7 +537,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -797,7 +797,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -909,7 +909,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -919,7 +919,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -969,7 +969,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/index.xml b/workshops/secure_software_factory/index.xml
index 3484e2bc3..378631ba1 100644
--- a/workshops/secure_software_factory/index.xml
+++ b/workshops/secure_software_factory/index.xml
@@ -4,249 +4,155 @@
     <title>DevSecOps Workshop - Secure Software Factory on Red Hat | Public Sector</title>
     <link>/workshops/secure_software_factory/</link>
     <description>Recent content in DevSecOps Workshop - Secure Software Factory on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/secure_software_factory/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/secure_software_factory/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Fin</title>
       <link>/workshops/secure_software_factory/fin/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/fin/</guid>
       <description>That&amp;rsquo;s it! Hopefully, you understand how to build a Trusted Software Supply Chain on OpenShift.</description>
     </item>
-    
     <item>
       <title>Lab 01 - Welcome to OpenShift</title>
       <link>/workshops/secure_software_factory/lab01/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab01/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.
-Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content.&#xA;Key Terms We will be using the following terms throughout the workshop labs so here are some basic definitions you should be familiar with. You&amp;rsquo;ll learn more terms along the way, but these are the basics to get you started.</description>
     </item>
-    
     <item>
       <title>Lab 02 - Trusted Software Supply Chain</title>
       <link>/workshops/secure_software_factory/lab02/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab02/</guid>
-      <description>Trusted Software Supply Chain The notion of Trusted Software Supply Chain is that of applying an assembly line approach to software that includes building increasing levels of assurance before marking an artifact as ready to deploy to production.
-In this workshop, you will use build orchestration tools such as Jenkins, Kubernetes, and OpenShift to support implementing and integrating continuous delivery (CD) as the foundation of automating the various stages of the deployment lifecycle are represented – from development, multiple types of testing, user acceptance, staging, to production release.</description>
+      <description>Trusted Software Supply Chain The notion of Trusted Software Supply Chain is that of applying an assembly line approach to software that includes building increasing levels of assurance before marking an artifact as ready to deploy to production.&#xA;In this workshop, you will use build orchestration tools such as Jenkins, Kubernetes, and OpenShift to support implementing and integrating continuous delivery (CD) as the foundation of automating the various stages of the deployment lifecycle are represented – from development, multiple types of testing, user acceptance, staging, to production release.</description>
     </item>
-    
     <item>
       <title>Lab 03 - CI/CD Project and Pods</title>
       <link>/workshops/secure_software_factory/lab03/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab03/</guid>
-      <description>Before moving forward, it is important to understand the difference between Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment.
-Also, a part of this lab we’ll be using using Pipelines in OpenShift for CI/CD, which gives you control over building, deploying, and promoting your applications on OpenShift. Using a combination of the Jenkins Pipeline Build Strategy, Jenkinsfiles, and the OpenShift Domain Specific Language (DSL) (provided by the OpenShift Jenkins Client Plug-in), you can create advanced build, test, deploy, and promote pipelines for any scenario.</description>
+      <description>Before moving forward, it is important to understand the difference between Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment.&#xA;Also, a part of this lab we’ll be using using Pipelines in OpenShift for CI/CD, which gives you control over building, deploying, and promoting your applications on OpenShift. Using a combination of the Jenkins Pipeline Build Strategy, Jenkinsfiles, and the OpenShift Domain Specific Language (DSL) (provided by the OpenShift Jenkins Client Plug-in), you can create advanced build, test, deploy, and promote pipelines for any scenario.</description>
     </item>
-    
     <item>
       <title>Lab 04 - Jenkins and OpenShift</title>
       <link>/workshops/secure_software_factory/lab04/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab04/</guid>
-      <description>Jenkins can be integrated with OpenShift in 3 ways. Today, you&amp;rsquo;ll be working with a containerized Jenkins Server that&amp;rsquo;s fully integrated with OpenShift.
-Login through SSO with Jenkins Go into your CI/CD project and find the running Jenkins Pod.
-Click the external route (https://jenkins…) to go into your Jenkins Server
-Click Login with OpenShift.
-Login with your OpenShift Credentials. You maybe asked to accept authorizations. Go ahead and do so and re-login.</description>
+      <description>Jenkins can be integrated with OpenShift in 3 ways. Today, you&amp;rsquo;ll be working with a containerized Jenkins Server that&amp;rsquo;s fully integrated with OpenShift.&#xA;Login through SSO with Jenkins Go into your CI/CD project and find the running Jenkins Pod.&#xA;Click the external route (https://jenkins…) to go into your Jenkins Server&#xA;Click Login with OpenShift.&#xA;Login with your OpenShift Credentials. You maybe asked to accept authorizations. Go ahead and do so and re-login.</description>
     </item>
-    
     <item>
       <title>Lab 05 - Creating Your Pipeline</title>
       <link>/workshops/secure_software_factory/lab05/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab05/</guid>
-      <description>Today, you will be building your Trusted Software Supply Chain using a Jenkins Pipeline that is integrated with OpenShift.
-In addition to standard Jenkins Pipeline Syntax, the OpenShift Jenkins image provides the OpenShift Domain Specific Language (DSL) (through the OpenShift Jenkins Client Plug-in), which aims to provide a readable, concise, comprehensive, and fluent syntax for rich interactions with an OpenShift API server, allowing for even more control over the build, deployment, and promotion of applications on your OpenShift cluster.</description>
+      <description>Today, you will be building your Trusted Software Supply Chain using a Jenkins Pipeline that is integrated with OpenShift.&#xA;In addition to standard Jenkins Pipeline Syntax, the OpenShift Jenkins image provides the OpenShift Domain Specific Language (DSL) (through the OpenShift Jenkins Client Plug-in), which aims to provide a readable, concise, comprehensive, and fluent syntax for rich interactions with an OpenShift API server, allowing for even more control over the build, deployment, and promotion of applications on your OpenShift cluster.</description>
     </item>
-    
     <item>
       <title>Lab 06 - Build App Stage</title>
       <link>/workshops/secure_software_factory/lab06/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab06/</guid>
-      <description>Add Build App Stage to Pipeline Text File Next, you will add the Build App Stage to your pipeline.
-The git branch step will clone the openshift-tasks project with the git branch locally from your gogs server to your jenkins node. The jenkins node is leveraging the git jenkins plugin to communicate to gogs.
-Please note that we are leveraging the eap-7 branch in our git project and not the master branch.</description>
+      <description>Add Build App Stage to Pipeline Text File Next, you will add the Build App Stage to your pipeline.&#xA;The git branch step will clone the openshift-tasks project with the git branch locally from your gogs server to your jenkins node. The jenkins node is leveraging the git jenkins plugin to communicate to gogs.&#xA;Please note that we are leveraging the eap-7 branch in our git project and not the master branch.</description>
     </item>
-    
     <item>
       <title>Lab 07 - Test Stage</title>
       <link>/workshops/secure_software_factory/lab07/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab07/</guid>
-      <description>Add Test Stage Add the configuration for the Test Stage below to your pipeline text file.
-Maven will run the test stage in the life cycle that we skipped at the previous stages.
-Maven will place the test results in the surefire-reports folder. The maven surefire-reports plugin allows for the generation of reports for your unit tests.
-Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
+      <description>Add Test Stage Add the configuration for the Test Stage below to your pipeline text file.&#xA;Maven will run the test stage in the life cycle that we skipped at the previous stages.&#xA;Maven will place the test results in the surefire-reports folder. The maven surefire-reports plugin allows for the generation of reports for your unit tests.&#xA;Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
     </item>
-    
     <item>
       <title>Lab 08 - Static Application Security Testing</title>
       <link>/workshops/secure_software_factory/lab08/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab08/</guid>
-      <description>Static Application Security Testing Next we will add a Code Analysis Stage into the pipeline.
-We will leverage the Maven Sonar plugin to run SonarQube scanning against our source code.
-SonarQube is an open source static code analysis tool that we can use to automate running security scans against your source code to further improve the security of your application. Every time you check-in code, SonarQube will scan the quality and perform a threat analysis of that code.</description>
+      <description>Static Application Security Testing Next we will add a Code Analysis Stage into the pipeline.&#xA;We will leverage the Maven Sonar plugin to run SonarQube scanning against our source code.&#xA;SonarQube is an open source static code analysis tool that we can use to automate running security scans against your source code to further improve the security of your application. Every time you check-in code, SonarQube will scan the quality and perform a threat analysis of that code.</description>
     </item>
-    
     <item>
       <title>Lab 09 - Archive App</title>
       <link>/workshops/secure_software_factory/lab09/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab09/</guid>
-      <description>Add Archive Stage Archiving the built and tested application into a trusted repository is important to making sure you are building with trusted parts. You assume this application is built properly and all the previous stages have passed. With that confidence, your built and tested application should be immutable in a trusted repository. The repository will version or audit any changes to the application, configuration, and dependencies.
-Add Archive Stage Steps into your pipeline.</description>
+      <description>Add Archive Stage Archiving the built and tested application into a trusted repository is important to making sure you are building with trusted parts. You assume this application is built properly and all the previous stages have passed. With that confidence, your built and tested application should be immutable in a trusted repository. The repository will version or audit any changes to the application, configuration, and dependencies.&#xA;Add Archive Stage Steps into your pipeline.</description>
     </item>
-    
     <item>
       <title>Lab 10 - Create Image Builder</title>
       <link>/workshops/secure_software_factory/lab10/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab10/</guid>
-      <description>Containers Containers are an important foundation for your application in building a Trusted Software Supply Chain. You want a secure and blessed golden container image that your application will inherit security controls from.
-Containers are built using a layered approach. For example, to create a container of a Java web application, you could do so in multiple layers: the OS, the JVM, the web server, and the code itself.
-We can incorporate CVE and vulnerability scanning against images in an automated fashion.</description>
+      <description>Containers Containers are an important foundation for your application in building a Trusted Software Supply Chain. You want a secure and blessed golden container image that your application will inherit security controls from.&#xA;Containers are built using a layered approach. For example, to create a container of a Java web application, you could do so in multiple layers: the OS, the JVM, the web server, and the code itself.&#xA;We can incorporate CVE and vulnerability scanning against images in an automated fashion.</description>
     </item>
-    
     <item>
       <title>Lab 11 - Build Image</title>
       <link>/workshops/secure_software_factory/lab11/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab11/</guid>
-      <description>Add Build Image Stage Add the Build Image Stage into your pipeline.
-The &amp;ldquo;sh&amp;rdquo; are shell commands in your pipeline that are executed on the Jenkins Slave. Maven built the openshift-tasks.war in it the target directory and it will be copied into the created oc-builds directory.
-The startBuild stage is kicked off from Openshift and pointing to the local directory &amp;ldquo;oc-build&amp;rdquo; on the Jenkins slave.
-# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
+      <description>Add Build Image Stage Add the Build Image Stage into your pipeline.&#xA;The &amp;ldquo;sh&amp;rdquo; are shell commands in your pipeline that are executed on the Jenkins Slave. Maven built the openshift-tasks.war in it the target directory and it will be copied into the created oc-builds directory.&#xA;The startBuild stage is kicked off from Openshift and pointing to the local directory &amp;ldquo;oc-build&amp;rdquo; on the Jenkins slave.&#xA;# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
     </item>
-    
     <item>
       <title>Lab 12 - Create and Deploy to Dev</title>
       <link>/workshops/secure_software_factory/lab12/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab12/</guid>
-      <description>Add Create Dev Stage Add Create Dev Stage into the pipeline.
-We first check if an deployment config for the Dev Project already exists. If it does not exists, a new application is created and deployment config is defined for the Dev Project.
-Before a trigger is created, the pipeline sleeps for 10 seconds. A deployment configuration can contain triggers, which drive the creation of new deployment processes in response to events inside the cluster.</description>
+      <description>Add Create Dev Stage Add Create Dev Stage into the pipeline.&#xA;We first check if an deployment config for the Dev Project already exists. If it does not exists, a new application is created and deployment config is defined for the Dev Project.&#xA;Before a trigger is created, the pipeline sleeps for 10 seconds. A deployment configuration can contain triggers, which drive the creation of new deployment processes in response to events inside the cluster.</description>
     </item>
-    
     <item>
       <title>Lab 13 - Promote and Deploy to Stage</title>
       <link>/workshops/secure_software_factory/lab13/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab13/</guid>
-      <description>Add Promote to Stage Enter the Promote to STAGE below into your pipeline.
-We set an approval to promote to the application to the Stage Project. The approval process is a good feature for various gates of your deployments. We also set a 15 minute timeout on the approval. You also tag the tasks image with latest and the version from the pom file.
-# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
+      <description>Add Promote to Stage Enter the Promote to STAGE below into your pipeline.&#xA;We set an approval to promote to the application to the Stage Project. The approval process is a good feature for various gates of your deployments. We also set a 15 minute timeout on the approval. You also tag the tasks image with latest and the version from the pom file.&#xA;# Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit</description>
     </item>
-    
     <item>
       <title>Lab 14 - Run Pipeline</title>
       <link>/workshops/secure_software_factory/lab14/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab14/</guid>
-      <description>Verify Completed Pipeline Before we kick off your pipeline, let&amp;rsquo;s verify it.
-In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit YAML
-Take a look and see if it matches the below text. If not, please correct it.
-apiVersion: v1 kind: BuildConfig metadata: annotations: pipeline.alpha.openshift.io/uses: &#39;[{&amp;quot;name&amp;quot;: &amp;quot;jenkins&amp;quot;, &amp;quot;namespace&amp;quot;: &amp;quot;&amp;quot;, &amp;quot;kind&amp;quot;: &amp;quot;DeploymentConfig&amp;quot;}]&#39; labels: app: cicd-pipeline name: cicd-pipeline name: tasks-pipeline spec: triggers: - type: GitHub github: secret: &amp;quot;secret101&amp;quot; - type: Generic generic: secret: &amp;quot;secret101&amp;quot; runPolicy: Serial source: type: None strategy: jenkinsPipelineStrategy: env: - name: DEV_PROJECT value: dev-userYOUR# - name: STAGE_PROJECT value: stage-userYOUR# jenkinsfile: |- def version, mvnCmd = &amp;quot;mvn -s configuration/cicd-settings-nexus3.</description>
+      <description>Verify Completed Pipeline Before we kick off your pipeline, let&amp;rsquo;s verify it.&#xA;In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit YAML&#xA;Take a look and see if it matches the below text. If not, please correct it.&#xA;apiVersion: v1 kind: BuildConfig metadata: annotations: pipeline.alpha.openshift.io/uses: &amp;#39;[{&amp;#34;name&amp;#34;: &amp;#34;jenkins&amp;#34;, &amp;#34;namespace&amp;#34;: &amp;#34;&amp;#34;, &amp;#34;kind&amp;#34;: &amp;#34;DeploymentConfig&amp;#34;}]&amp;#39; labels: app: cicd-pipeline name: cicd-pipeline name: tasks-pipeline spec: triggers: - type: GitHub github: secret: &amp;#34;secret101&amp;#34; - type: Generic generic: secret: &amp;#34;secret101&amp;#34; runPolicy: Serial source: type: None strategy: jenkinsPipelineStrategy: env: - name: DEV_PROJECT value: dev-userYOUR# - name: STAGE_PROJECT value: stage-userYOUR# jenkinsfile: |- def version, mvnCmd = &amp;#34;mvn -s configuration/cicd-settings-nexus3.</description>
     </item>
-    
     <item>
       <title>Lab 15 - Trigger the Software Supply Chain</title>
       <link>/workshops/secure_software_factory/lab15/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab15/</guid>
-      <description>Trigger the Trusted Software Supply Chain with Code Check-ins Through automation, you will trigger the Trusted Software Supply Chain with code check-ins.
-Verify Webhook in Gogs The Webhook is what triggers your pipeline upon code check-ins. You want your SCM to trigger the pipeline as opposed to Jenkins constantly polling the source code for changes.
-Click on the Gogs route url in the CI/CD project which takes you to the home page.</description>
+      <description>Trigger the Trusted Software Supply Chain with Code Check-ins Through automation, you will trigger the Trusted Software Supply Chain with code check-ins.&#xA;Verify Webhook in Gogs The Webhook is what triggers your pipeline upon code check-ins. You want your SCM to trigger the pipeline as opposed to Jenkins constantly polling the source code for changes.&#xA;Click on the Gogs route url in the CI/CD project which takes you to the home page.</description>
     </item>
-    
     <item>
       <title>Lab 16 - Create Quay Account</title>
       <link>/workshops/secure_software_factory/lab16/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab16/</guid>
-      <description>Create Quay Account Please go to the Quay Login with the link given to you by your instructor
-Click Create Account at the bottom of the page.
-
-Fill in the account information for Quay.
- Username: your assigned username i.e userYOUR# E-mail address: your email address Password: openshift Confirm Password: openshift  Click Create Account
-
- .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.</description>
+      <description>Create Quay Account Please go to the Quay Login with the link given to you by your instructor&#xA;Click Create Account at the bottom of the page.&#xA;Fill in the account information for Quay.&#xA;Username: your assigned username i.e userYOUR# E-mail address: your email address Password: openshift Confirm Password: openshift Click Create Account&#xA;&amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
     <item>
       <title>Lab 17 - Clair Vulnerability Scan</title>
       <link>/workshops/secure_software_factory/lab17/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab17/</guid>
-      <description>Add Clair Container Scan Add the configuration for the Container Vulnerability Scan below to your pipeline text file.
-
-Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit
-In your pipeline, add and update the following variables after the version and mvnCmd definitions. Please fill in the values between the quotes.
- ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor quayuser : the quay user you created previously quaypass : the quay password you created previously quayrepo : the quay repo you will push your app image to i.</description>
+      <description>Add Clair Container Scan Add the configuration for the Container Vulnerability Scan below to your pipeline text file.&#xA;Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit&#xA;In your pipeline, add and update the following variables after the version and mvnCmd definitions. Please fill in the values between the quotes.&#xA;ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor quayuser : the quay user you created previously quaypass : the quay password you created previously quayrepo : the quay repo you will push your app image to i.</description>
     </item>
-    
     <item>
       <title>Lab 18 - OpenSCAP DISA STIG Scan</title>
       <link>/workshops/secure_software_factory/lab18/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/lab18/</guid>
-      <description>Add OpenSCAP DISA STIG Scan Add the configuration for the OpenSCAP Scan below to your pipeline text file.
-
-Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit
-In your pipeline, verify the following variables are there after the version and mvnCmd definitions. Please fill in the values between the quotes if not done previously.
- ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor  def ocuser = &amp;quot; &amp;quot; def ocpass = &amp;quot; &amp;quot; def ocp = &amp;quot; &amp;quot; For Example:</description>
+      <description>Add OpenSCAP DISA STIG Scan Add the configuration for the OpenSCAP Scan below to your pipeline text file.&#xA;Append to Jenkins Pipeline Configuration In Builds &amp;gt; Pipelines &amp;gt; tasks-pipeline &amp;gt; Actions &amp;gt; Edit&#xA;In your pipeline, verify the following variables are there after the version and mvnCmd definitions. Please fill in the values between the quotes if not done previously.&#xA;ocuser : the openshift user given to you by your insturctor ocpass : the openshift password given to you by your insturctor ocp : the openshift host given to you by your instuctor def ocuser = &amp;#34; &amp;#34; def ocpass = &amp;#34; &amp;#34; def ocp = &amp;#34; &amp;#34; For Example:</description>
     </item>
-    
     <item>
       <title>Login Tour - Wetty</title>
       <link>/workshops/secure_software_factory/login_tour_wetty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/login_tour_wetty/</guid>
-      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-Accessing Wetty Ask your instructor for the wetty URL.
-Login Info login: userYOUR# Password: &amp;lt;Instructor Provided&amp;gt; After logging in, you should see a shell.
-The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
+      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Ask your instructor for the wetty URL.&#xA;Login Info login: userYOUR# Password: &amp;lt;Instructor Provided&amp;gt; After logging in, you should see a shell.&#xA;The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
     </item>
-    
     <item>
       <title>Verify Prerequisites</title>
       <link>/workshops/secure_software_factory/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/secure_software_factory/prerequisites/</guid>
-      <description>Prerequisites 
-This workshop is done entirely through the browser.
-  Chrome is the preferred browser for this workshop   .modal { display: none; position: fixed; z-index: 1; left: 0; top: 0; width: 100%; height: 100%; overflow: auto; background-color: rgb(0,0,0); background-color: rgba(0,0,0,0.4); -webkit-animation-name: fadeIn; -webkit-animation-duration: 0.4s; animation-name: fadeIn; animation-duration: 0.4s } .modal-content { position: fixed; bottom: 0; background-color: #fefefe; width: 100%; -webkit-animation-name: slideIn; -webkit-animation-duration: 0.4s; animation-name: slideIn; animation-duration: 0.</description>
+      <description>Prerequisites This workshop is done entirely through the browser.&#xA;Chrome is the preferred browser for this workshop &amp;times; Workshop Details Domain Workshop Student ID Student ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 Domain rhnaps.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/secure_software_factory/lab01/index.html b/workshops/secure_software_factory/lab01/index.html
index 56a5eea18..f7527bd57 100644
--- a/workshops/secure_software_factory/lab01/index.html
+++ b/workshops/secure_software_factory/lab01/index.html
@@ -340,22 +340,22 @@ <h1 id="accessing-openshift">Accessing OpenShift</h1>
 <h2 id="lets-login-to-the-web-console">Let&rsquo;s Login to the Web Console</h2>
 <p>Use your browser to navigate to the URI provided by your instructor and login with the user/password provided.</p>
 <p>For example:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443
-</code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443
+</span></span></code></pre></div><p><img src="../images/ocp-login.png" width="600"><br/>
 <em>Login Webpage</em></p>
 <p>Once logged in you should see your available projects - or a button to create a project if none exist already.</p>
 <h2 id="lets-try-the-oc-command-line-cli-tool">Let&rsquo;s try the &lsquo;oc&rsquo; command line (CLI) tool</h2>
 <p>Open a terminal and login using the same openshift URI with the oc Login command.  Please add the option &ndash;insecure-skip-tls-verify=true.</p>
 <p>For example:</p>
-<pre><code>$ oc login https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 --insecure-skip-tls-verify=true
+<pre tabindex="0"><code>$ oc login https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 --insecure-skip-tls-verify=true
 Authentication required for https://master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:8443 (openshift)
 Username: user<span class="userid">YOUR#</span>
 Password:
 Login successful.
 </code></pre><p>Check to see what projects you have access to:</p>
-<pre><code>$ oc get projects
+<pre tabindex="0"><code>$ oc get projects
 </code></pre><p>Type the following command to show services, deployment configs, build configurations, and active deployments (this will come in handy later):</p>
-<pre><code>$ oc status
+<pre tabindex="0"><code>$ oc status
 </code></pre><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.
 <style>
@@ -457,7 +457,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -717,7 +717,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -829,7 +829,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -839,7 +839,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -922,7 +922,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab02/index.html b/workshops/secure_software_factory/lab02/index.html
index 5645b58ad..9978f8191 100644
--- a/workshops/secure_software_factory/lab02/index.html
+++ b/workshops/secure_software_factory/lab02/index.html
@@ -320,11 +320,11 @@ <h1>Lab 02 - Trusted Software Supply Chain</h1>
     <h1 id="trusted-software-supply-chain">Trusted Software Supply Chain</h1>
 <p>The notion of Trusted Software Supply Chain is that of applying an assembly line approach to software that includes building increasing levels of assurance before marking an artifact as ready to deploy to production.</p>
 <p>In this workshop, you will use build orchestration tools such as Jenkins, Kubernetes, and OpenShift to support implementing and integrating <a href="https://en.wikipedia.org/wiki/Continuous_delivery">continuous delivery (CD)</a> as the foundation of automating the various stages of the deployment lifecycle are represented – from development, multiple types of testing, user acceptance, staging, to production release.</p>
-<p><img src="../images/trusted_software_supply_chain.png" width="900" /></p>
+<img src="../images/trusted_software_supply_chain.png" width="900" />
 <p>For many organizations, obtaining Authority to Operate (ATO) is an arduous process requiring hundreds of pages of documentation, and can prevent organizations from adopting continuous delivery practices for fear of falling out of compliance. Each phase in our Trusted Software Supply Chain will have a policy defining the stage gate for success and will generate a documentation artifact that will later be used as part of the <a href="https://cloud.gov/docs/compliance/ato-process/">ATO process</a>.</p>
 <p>Having a secure foundation for your applications is a key component to a Trusted Software Supply Chain. In the following lab exercises, your applications will inherit these security controls from the accredited OpenShift platform.</p>
 <p>The approach towards the Authorization and Accreditation (A&amp;A) process with OpenShift follows a Landlord/Tenant model. OpenShift is a container application platform that provides a standardized operating environment and when assessing system boundaries, a delineation should be made between the OpenShift system itself, which operates as a Landlord, and the tenant application, which consumes the OpenShift service.</p>
-<p><img src="../images/security_inheritance_model.png" width="700" /></p>
+<img src="../images/security_inheritance_model.png" width="700" />
 <p>In Landlord/Tenant system security plans (SSP), many security controls are inherited from the Landlord’s SSP, but some controls remain the responsibility of the OpenShift consumers. Following this division of responsibilities illustrated in the diagram above, some controls would be considered the responsibility of the tenant, whereas a good number of controls are already taken care of by the Landlord.</p>
 <style>
 
@@ -425,7 +425,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -685,7 +685,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -797,7 +797,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -807,7 +807,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -890,7 +890,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab03/index.html b/workshops/secure_software_factory/lab03/index.html
index 3ca3da9eb..476523714 100644
--- a/workshops/secure_software_factory/lab03/index.html
+++ b/workshops/secure_software_factory/lab03/index.html
@@ -449,7 +449,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -709,7 +709,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -821,7 +821,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -831,7 +831,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -914,7 +914,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab04/index.html b/workshops/secure_software_factory/lab04/index.html
index 63638ec65..45d820012 100644
--- a/workshops/secure_software_factory/lab04/index.html
+++ b/workshops/secure_software_factory/lab04/index.html
@@ -318,18 +318,18 @@ <h1>Lab 04 - Jenkins and OpenShift</h1>
 </nav>
 
     <p>Jenkins can be integrated with OpenShift in 3 ways.  Today, you&rsquo;ll be working with a containerized Jenkins Server that&rsquo;s fully integrated with OpenShift.</p>
-<p><img src="../images/jenkins_integrated.png" width="900" /></p>
+<img src="../images/jenkins_integrated.png" width="900" />
 <h1 id="login-through-sso-with-jenkins">Login through SSO with Jenkins</h1>
 <p>Go into your CI/CD project and find the running Jenkins Pod.</p>
 <p>Click the external route (https://jenkins…) to go into your Jenkins Server</p>
-<p><img src="../images/jenkins_pod.png" width="900" /></p>
+<img src="../images/jenkins_pod.png" width="900" />
 <p>Click Login with OpenShift.</p>
 <p>Login with your OpenShift Credentials. You maybe asked to accept authorizations. Go ahead and do so and re-login.</p>
-<p><img src="../images/jenkins_ocp_login.png" width="500" /></p>
+<img src="../images/jenkins_ocp_login.png" width="500" />
 <p>You will be asked to authorize access to the jenkins service account.  Go ahead and Allow selected permissions.</p>
-<p><img src="../images/authorize_jenkins_service.png" width="700" /></p>
+<img src="../images/authorize_jenkins_service.png" width="700" />
 <p>You should now see the Jenkins Home Page</p>
-<p><img src="../images/jenkins_home.png" width="900" /></p>
+<img src="../images/jenkins_home.png" width="900" />
 <p>Jenkins follows a master/agent architecture.  Your pipeline will run a process called a Jenkins executor.  A Jenkins executor is one of the basic building blocks which allow a build to run on an agent (e.g. build server). Think of an executor as a single “process ID”, or as the basic unit of resource that Jenkins executes on your machine to run a build.
 <style>
 
@@ -430,7 +430,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -690,7 +690,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -802,7 +802,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -812,7 +812,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -895,7 +895,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab05/index.html b/workshops/secure_software_factory/lab05/index.html
index 0650f0007..31e226326 100644
--- a/workshops/secure_software_factory/lab05/index.html
+++ b/workshops/secure_software_factory/lab05/index.html
@@ -321,13 +321,13 @@ <h1>Lab 05 - Creating Your Pipeline</h1>
 <p>In addition to standard Jenkins Pipeline Syntax, the OpenShift Jenkins image provides the OpenShift Domain Specific Language (DSL) (through the OpenShift Jenkins Client Plug-in), which aims to provide a readable, concise, comprehensive, and fluent syntax for rich interactions with an OpenShift API server, allowing for even more control over the build, deployment, and promotion of applications on your OpenShift cluster.</p>
 <p>Please refer to the <a href="https://github.com/openshift/jenkins-client-plugin#examples">OpenShift Jenkins Pipelin(DSL) Plugin examples documentation</a> for more info.</p>
 <p>First, we will need to create a <a href="https://docs.openshift.com/container-platform/3.11/dev_guide/builds/index.html#defining-a-buildconfig">BuildConfig</a> that employs the <a href="https://docs.openshift.com/container-platform/3.11/architecture/core_concepts/builds_and_image_streams.html#pipeline-build">Pipeline Build</a> strategy for our Trusted Software Supply Chain. In the OpenShift Console, we’ll do this by clicking “Add to Project”, “Import YAML / JSON” while using the CI/CD project.</p>
-<p><img src="../images/import_yaml.png" width="900" /></p>
+<img src="../images/import_yaml.png" width="900" />
 <p>Then copy &amp; paste the following into the YAML/JSON input text field and click Create,</p>
-<pre><code>apiVersion: v1
+<pre tabindex="0"><code>apiVersion: v1
 kind: BuildConfig
 metadata:
     annotations:
-      pipeline.alpha.openshift.io/uses: '[{&quot;name&quot;: &quot;jenkins&quot;, &quot;namespace&quot;: &quot;&quot;, &quot;kind&quot;: &quot;DeploymentConfig&quot;}]'
+      pipeline.alpha.openshift.io/uses: &#39;[{&#34;name&#34;: &#34;jenkins&#34;, &#34;namespace&#34;: &#34;&#34;, &#34;kind&#34;: &#34;DeploymentConfig&#34;}]&#39;
     labels:
       app: cicd-pipeline
       name: cicd-pipeline
@@ -336,10 +336,10 @@ <h1>Lab 05 - Creating Your Pipeline</h1>
     triggers:
       - type: GitHub
         github:
-          secret: &quot;secret101&quot;
+          secret: &#34;secret101&#34;
       - type: Generic
         generic:
-          secret: &quot;secret101&quot;
+          secret: &#34;secret101&#34;
     runPolicy: Serial
     source:
       type: None
@@ -351,20 +351,20 @@ <h1>Lab 05 - Creating Your Pipeline</h1>
         - name: STAGE_PROJECT
           value: stage-user<span class="userid">YOUR#</span>
         jenkinsfile: |-
-          def version, mvnCmd = &quot;mvn -s configuration/cicd-settings-nexus3.xml&quot;
+          def version, mvnCmd = &#34;mvn -s configuration/cicd-settings-nexus3.xml&#34;
           pipeline {
             agent {
-              label 'maven'
+              label &#39;maven&#39;
             }
 </code></pre><p>Close the window once it&rsquo;s imported.</p>
 <p>Then go to “Builds” → “Pipelines” tab.</p>
-<p><img src="../images/builds_pipelines.png" width="900" /></p>
+<img src="../images/builds_pipelines.png" width="900" />
 <p>Verify that you see your &ldquo;tasks pipeline&rdquo; that you just imported.</p>
-<p><img src="../images/tasks_pipeline.png" width="900" /></p>
+<img src="../images/tasks_pipeline.png" width="900" />
 <p>Click on the “tasks-pipeline”</p>
 <p>Click Actions -&gt; Edit YAML</p>
 <p>Update your user Dev and Stage projects to make sure reflects your user #.</p>
-<pre><code>strategy:
+<pre tabindex="0"><code>strategy:
   jenkinsPipelineStrategy:
     env:
     - name: DEV_PROJECT
@@ -374,11 +374,11 @@ <h1>Lab 05 - Creating Your Pipeline</h1>
 </code></pre><p>Also, notice that we will be launching a Maven node/agent to execute our pipeline.</p>
 <p>You will also be declaring variables such as version and mvnCmd to be used later in the pipeline.</p>
 <p>The .xml file refers to maven configurations for your application. The reference to this .xml file from our pipeline can be seen here:</p>
-<pre><code>        jenkinsfile: |-
-          def version, mvnCmd = &quot;mvn -s configuration/cicd-settings-nexus3.xml&quot;
+<pre tabindex="0"><code>        jenkinsfile: |-
+          def version, mvnCmd = &#34;mvn -s configuration/cicd-settings-nexus3.xml&#34;
           pipeline {
             agent {
-              label 'maven'
+              label &#39;maven&#39;
             }
 </code></pre><p>Click Save</p>
 <style>
@@ -480,7 +480,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -740,7 +740,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -852,7 +852,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -862,7 +862,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -945,7 +945,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab06/index.html b/workshops/secure_software_factory/lab06/index.html
index 39d0c0be4..00e8408ef 100644
--- a/workshops/secure_software_factory/lab06/index.html
+++ b/workshops/secure_software_factory/lab06/index.html
@@ -319,42 +319,42 @@ <h1>Lab 06 - Build App Stage</h1>
 
     <h1 id="add-build-app-stage-to-pipeline-text-file">Add Build App Stage to Pipeline Text File</h1>
 <p>Next, you will add the Build App Stage to your pipeline.</p>
-<p><img src="../images/pipeline_build.png" width="900" /></p>
+<img src="../images/pipeline_build.png" width="900" />
 <p>The git branch step will clone the openshift-tasks project with the git branch locally from your gogs server to your jenkins node.  The jenkins node is leveraging the <a href="https://jenkins.io/doc/pipeline/steps/git/">git jenkins plugin</a> to communicate to gogs.</p>
 <p>Please note that we are leveraging the eap-7 branch in our git project and not the master branch.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>  stages {
-    stage('Build App') {
+<pre tabindex="0"><code>  stages {
+    stage(&#39;Build App&#39;) {
       steps {
-        git branch: 'eap-7', url: 'http://gogs:3000/gogs/openshift-tasks.git'
+        git branch: &#39;eap-7&#39;, url: &#39;http://gogs:3000/gogs/openshift-tasks.git&#39;
         script {
-            def pom = readMavenPom file: 'pom.xml'
+            def pom = readMavenPom file: &#39;pom.xml&#39;
             version = pom.version
           }
-          sh &quot;${mvnCmd} install -DskipTests=true&quot;
+          sh &#34;${mvnCmd} install -DskipTests=true&#34;
         }
       }
 </code></pre><p>Your Jenkinsfile should look like this.</p>
-<p><img src="../images/jenkinsfile_buildapp.png" width="900" />
-<br></p>
+<img src="../images/jenkinsfile_buildapp.png" width="900" />
+<br>
 <h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code> }
+<pre tabindex="0"><code> }
 }
 </code></pre><p>Your Jenkinsfile should look like this</p>
-<p><img src="../images/jenkinsfile_buildapp_close.png" width="900" /></p>
+<img src="../images/jenkinsfile_buildapp_close.png" width="900" />
 <p>Click Save</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <p>You should see your first stage run successfully.</p>
-<p><img src="../images/pipelinerun_buildapp.png" width="900" /></p>
+<img src="../images/pipelinerun_buildapp.png" width="900" />
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code> }
+<pre tabindex="0"><code> }
 }
 </code></pre><p>Click Save</p>
 <br>
@@ -477,7 +477,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -737,7 +737,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -849,7 +849,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -859,7 +859,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -942,7 +942,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab07/index.html b/workshops/secure_software_factory/lab07/index.html
index baa731594..c4367c243 100644
--- a/workshops/secure_software_factory/lab07/index.html
+++ b/workshops/secure_software_factory/lab07/index.html
@@ -319,30 +319,30 @@ <h1>Lab 07 - Test Stage</h1>
 
     <h1 id="add-test-stage">Add Test Stage</h1>
 <p>Add the configuration for the Test Stage below to your pipeline text file.</p>
-<p><img src="../images/pipeline_test.png" width="900" /></p>
+<img src="../images/pipeline_test.png" width="900" />
 <p>Maven will run the test stage in the life cycle that we skipped at the previous stages.</p>
 <p>Maven will place the test results in the surefire-reports folder.  The maven surefire-reports plugin allows for the generation of reports for your unit tests.</p>
 <br>
 <h1 id="append-to-jenkins-pipeline-configuration">Append to Jenkins Pipeline Configuration</h1>
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Test') {
+<pre tabindex="0"><code>    stage(&#39;Test&#39;) {
       steps {
-        sh &quot;${mvnCmd} test&quot;
-        step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])
+        sh &#34;${mvnCmd} test&#34;
+        step([$class: &#39;JUnitResultArchiver&#39;, testResults: &#39;**/target/surefire-reports/TEST-*.xml&#39;])
       }
     }
 </code></pre><h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Save your Jenkinsfile.</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Click Save
 <style>
@@ -444,7 +444,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -704,7 +704,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -816,7 +816,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -826,7 +826,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -909,7 +909,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab08/index.html b/workshops/secure_software_factory/lab08/index.html
index 36f0f068e..9531db8d5 100644
--- a/workshops/secure_software_factory/lab08/index.html
+++ b/workshops/secure_software_factory/lab08/index.html
@@ -319,7 +319,7 @@ <h1>Lab 08 - Static Application Security Testing</h1>
 
     <h1 id="static-application-security-testing">Static Application Security Testing</h1>
 <p>Next we will add a Code Analysis Stage into the pipeline.</p>
-<p><img src="../images/pipeline_sonar.png" width="900" /></p>
+<img src="../images/pipeline_sonar.png" width="900" />
 <p>We will leverage the Maven Sonar plugin to run SonarQube scanning against our source code.</p>
 <p>SonarQube is an open source static code analysis tool that we can use to automate running security scans against your source code to further improve the security of your application.  Every time you check-in code, SonarQube will scan the quality and perform a threat analysis of that code.</p>
 <p>We leverage the sonarqube maven plugin and specify the maven goal &ldquo;sonar:sonar&rdquo; to run our project leveraging the sonarqube api.</p>
@@ -338,12 +338,12 @@ <h1 id="static-application-security-testing">Static Application Security Testing
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Code Analysis') {
+<pre tabindex="0"><code>    stage(&#39;Code Analysis&#39;) {
       steps {
         script {
-          sh &quot;${mvnCmd} sonar:sonar -Dsonar.host.url=http://sonarqube:9000 -DskipTests=true&quot;
+          sh &#34;${mvnCmd} sonar:sonar -Dsonar.host.url=http://sonarqube:9000 -DskipTests=true&#34;
         }
       }
     }
@@ -353,14 +353,14 @@ <h1 id="static-application-security-testing">Static Application Security Testing
 <p><img src="../images/sonarqube-analysis.png" width="900"><br/></p>
 <h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Save your Jenkinsfile.</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Click Save</p>
 <style>
@@ -462,7 +462,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -722,7 +722,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -834,7 +834,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -844,7 +844,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -927,7 +927,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab09/index.html b/workshops/secure_software_factory/lab09/index.html
index 330de4b4c..bcb0b03b3 100644
--- a/workshops/secure_software_factory/lab09/index.html
+++ b/workshops/secure_software_factory/lab09/index.html
@@ -320,29 +320,29 @@ <h1>Lab 09 - Archive App</h1>
     <h1 id="add-archive-stage">Add Archive Stage</h1>
 <p>Archiving the built and tested application into a trusted repository is important to making sure you are building with trusted parts.  You assume this application is built properly and all the previous stages have passed.  With that confidence, your built and tested application should be immutable in a trusted repository.  The repository will version or audit any changes to the application, configuration, and dependencies.</p>
 <p>Add Archive Stage Steps into your pipeline.</p>
-<p><img src="../images/pipeline_nexus.png" width="900" /></p>
+<img src="../images/pipeline_nexus.png" width="900" />
 <p>We leveraged the maven nexus plugin for this deployment.  The mvn deploy step is the last step in the maven lifecycle.  The built application is archived into the nexus repository.  We can see it later once we run the pipeline.</p>
 <p>The &ldquo;-P nexus3&rdquo; option activates the nexus3 profile defined in the configuration/cicd-settings-nexus3.xml</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Archive App') {
+<pre tabindex="0"><code>    stage(&#39;Archive App&#39;) {
       steps {
-        sh &quot;${mvnCmd} deploy -DskipTests=true -P nexus3&quot;
+        sh &#34;${mvnCmd} deploy -DskipTests=true -P nexus3&#34;
       }
     }
 </code></pre><h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Save your Jenkinsfile.</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Click Save
 <style>
@@ -444,7 +444,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -704,7 +704,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -816,7 +816,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -826,7 +826,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -909,7 +909,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab10/index.html b/workshops/secure_software_factory/lab10/index.html
index 6c05a7bfe..71a491c0b 100644
--- a/workshops/secure_software_factory/lab10/index.html
+++ b/workshops/secure_software_factory/lab10/index.html
@@ -320,30 +320,30 @@ <h1>Lab 10 - Create Image Builder</h1>
     <h1 id="containers">Containers</h1>
 <p>Containers are an important foundation for your application in building a Trusted Software Supply Chain.  You want a secure and blessed golden container image that your application will inherit security controls from.</p>
 <p>Containers are built using a layered approach. For example, to create a container of a Java web application, you could do so in multiple layers: the OS, the JVM, the web server, and the code itself.</p>
-<p><img src="../images/golden_images.png" width="900" /></p>
+<img src="../images/golden_images.png" width="900" />
 <p>We can incorporate CVE and vulnerability scanning against images in an automated fashion.  Any image change is scanned to improve the inherited security of your application.  We have partners such as Black Duck and Twistlock that do container image scanning.  Also, as a result of Red Hat&rsquo;s acquisition of CoreOS, we now offer Quay as an enterprise-grade registry that does vulnerability scanning.</p>
 <p>We can also cryptographically sign your image so you know your container is running with a verified container image.</p>
 <br>
 # Start with Quality Parts
 <p>Red Hat has a container registry that provides certified Red Hat and third-party container images that will be the foundation of your container images.  Our Registry also has a health index of the image so you know the state of the image.</p>
-<p><img src="../images/rh_container_catalog.png" width="900" /></p>
+<img src="../images/rh_container_catalog.png" width="900" />
 <br>
 # Add Create Image Builder Stage
 <p>Next we will add the Create <a href="https://docs.openshift.com/container-platform/3.11/architecture/core_concepts/builds_and_image_streams.html">Image Builder</a> Stage into your pipeline.</p>
-<p><img src="../images/pipeline_build_image.png" width="900" /></p>
+<img src="../images/pipeline_build_image.png" width="900" />
 <p>This step will create a new build.  We will be leveraging a trusted JBoss EAP 7 container.</p>
 <p>The golden image will will be using for our applications is jboss-eap70-openshift:1.5.  Again, you&rsquo;ll want a hardened, secured, patched and up to date container image as a foundation for your application.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Create Image Builder') {
+<pre tabindex="0"><code>    stage(&#39;Create Image Builder&#39;) {
       when {
         expression {
           openshift.withCluster() {
             openshift.withProject(env.DEV_PROJECT) {
-              return !openshift.selector(&quot;bc&quot;, &quot;tasks&quot;).exists();
+              return !openshift.selector(&#34;bc&#34;, &#34;tasks&#34;).exists();
             }
           }
         }
@@ -352,7 +352,7 @@ <h1 id="containers">Containers</h1>
         script {
           openshift.withCluster() {
             openshift.withProject(env.DEV_PROJECT) {
-              openshift.newBuild(&quot;--name=tasks&quot;, &quot;--image-stream=jboss-eap70-openshift:1.5&quot;, &quot;--binary=true&quot;)
+              openshift.newBuild(&#34;--name=tasks&#34;, &#34;--image-stream=jboss-eap70-openshift:1.5&#34;, &#34;--binary=true&#34;)
             }
           }
         }
@@ -360,14 +360,14 @@ <h1 id="containers">Containers</h1>
     }
 </code></pre><h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Save your Jenkinsfile.</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Click Save</p>
 <style>
@@ -469,7 +469,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -729,7 +729,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -841,7 +841,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -851,7 +851,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -934,7 +934,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab11/index.html b/workshops/secure_software_factory/lab11/index.html
index db21774a3..d236af16c 100644
--- a/workshops/secure_software_factory/lab11/index.html
+++ b/workshops/secure_software_factory/lab11/index.html
@@ -319,23 +319,23 @@ <h1>Lab 11 - Build Image</h1>
 
     <h1 id="add-build-image-stage">Add Build Image Stage</h1>
 <p>Add the Build Image Stage into your pipeline.</p>
-<p><img src="../images/pipeline_oc_build_image.png" width="900" /></p>
+<img src="../images/pipeline_oc_build_image.png" width="900" />
 <p>The &ldquo;sh&rdquo; are shell commands in your pipeline that are executed on the Jenkins Slave.  Maven built the openshift-tasks.war in it the target directory and it will be copied into the created oc-builds directory.</p>
 <p>The startBuild stage is kicked off from Openshift and pointing to the local directory &ldquo;oc-build&rdquo; on the Jenkins slave.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Build Image') {
+<pre tabindex="0"><code>    stage(&#39;Build Image&#39;) {
       steps {
-        sh &quot;rm -rf oc-build &amp;&amp; mkdir -p oc-build/deployments&quot;
-        sh &quot;cp target/openshift-tasks.war oc-build/deployments/ROOT.war&quot;
+        sh &#34;rm -rf oc-build &amp;&amp; mkdir -p oc-build/deployments&#34;
+        sh &#34;cp target/openshift-tasks.war oc-build/deployments/ROOT.war&#34;
 
         script {
           openshift.withCluster() {
             openshift.withProject(env.DEV_PROJECT) {
-              openshift.selector(&quot;bc&quot;, &quot;tasks&quot;).startBuild(&quot;--from-dir=oc-build&quot;, &quot;--wait=true&quot;)
+              openshift.selector(&#34;bc&#34;, &#34;tasks&#34;).startBuild(&#34;--from-dir=oc-build&#34;, &#34;--wait=true&#34;)
             }
           }
         }
@@ -343,14 +343,14 @@ <h1 id="add-build-image-stage">Add Build Image Stage</h1>
     }
 </code></pre><h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Save your Jenkinsfile.</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Click Save
 <style>
@@ -452,7 +452,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -712,7 +712,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -824,7 +824,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -834,7 +834,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -917,7 +917,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab12/index.html b/workshops/secure_software_factory/lab12/index.html
index 9d03828ca..d1d1852b9 100644
--- a/workshops/secure_software_factory/lab12/index.html
+++ b/workshops/secure_software_factory/lab12/index.html
@@ -319,20 +319,20 @@ <h1>Lab 12 - Create and Deploy to Dev</h1>
 
     <h1 id="add-create-dev-stage">Add Create Dev Stage</h1>
 <p>Add Create Dev Stage into the pipeline.</p>
-<p><img src="../images/pipeline_create_dev.png" width="900" /></p>
+<img src="../images/pipeline_create_dev.png" width="900" />
 <p>We first check if an deployment config for the Dev Project already exists.  If it does not exists, a new application is created and deployment config is defined for the Dev Project.</p>
 <p>Before a trigger is created, the pipeline sleeps for 10 seconds.  A deployment configuration can contain triggers, which drive the creation of new deployment processes in response to events inside the cluster.  In this case, the trigger is set to a manual deployment of the tasks deployment config.  The deployment will happen in Deploy Stage.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Create DEV') {
+<pre tabindex="0"><code>    stage(&#39;Create DEV&#39;) {
       when {
         expression {
           openshift.withCluster() {
             openshift.withProject(env.DEV_PROJECT) {
-              return !openshift.selector('dc', 'tasks').exists()
+              return !openshift.selector(&#39;dc&#39;, &#39;tasks&#39;).exists()
             }
           }
         }
@@ -341,14 +341,14 @@ <h1 id="add-create-dev-stage">Add Create Dev Stage</h1>
         script {
           openshift.withCluster() {
             openshift.withProject(env.DEV_PROJECT) {
-              def app = openshift.newApp(&quot;tasks:latest&quot;)
-              app.narrow(&quot;svc&quot;).expose();
+              def app = openshift.newApp(&#34;tasks:latest&#34;)
+              app.narrow(&#34;svc&#34;).expose();
 
-              def dc = openshift.selector(&quot;dc&quot;, &quot;tasks&quot;)
+              def dc = openshift.selector(&#34;dc&#34;, &#34;tasks&#34;)
               while (dc.object().spec.replicas != dc.object().status.availableReplicas) {
                   sleep 10
               }
-              openshift.set(&quot;triggers&quot;, &quot;dc/tasks&quot;, &quot;--manual&quot;)
+              openshift.set(&#34;triggers&#34;, &#34;dc/tasks&#34;, &#34;--manual&#34;)
             }
           }
         }
@@ -356,19 +356,19 @@ <h1 id="add-create-dev-stage">Add Create Dev Stage</h1>
     }
 </code></pre><h1 id="deploy-dev-stage">Deploy Dev Stage</h1>
 <p>Enter the Deploy Dev Stage to your pipeline text file.</p>
-<p><img src="../images/pipeline_deploy_dev.png" width="900" /></p>
+<img src="../images/pipeline_deploy_dev.png" width="900" />
 <p>OpenShift deploys the application and it&rsquo;s deployment configuration to Dev as previously defined from the Create Dev Stage.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Deploy DEV') {
+<pre tabindex="0"><code>    stage(&#39;Deploy DEV&#39;) {
       steps {
         script {
           openshift.withCluster() {
             openshift.withProject(env.DEV_PROJECT) {
-              openshift.selector(&quot;dc&quot;, &quot;tasks&quot;).rollout().latest();
+              openshift.selector(&#34;dc&#34;, &#34;tasks&#34;).rollout().latest();
             }
           }
         }
@@ -376,14 +376,14 @@ <h1 id="add-create-dev-stage">Add Create Dev Stage</h1>
     }
 </code></pre><h1 id="test-your-pipeline">Test Your Pipeline</h1>
 <p>If you&rsquo;d like to do a test of first pipeline stage, add the following brackets at the end of your Jenkinsfile. Make sure to append to the beginning of the last line.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Save your Jenkinsfile.</p>
 <p>Go back to Builds &gt; Pipelines</p>
 <p>Click Start Pipeline</p>
 <h1 id="delete-brackets">Delete Brackets</h1>
 <p>Please delete the brackets you just added once testing is complete. We can add them later if you&rsquo;d like to test your pipeline as you go along.</p>
-<pre><code>  }
+<pre tabindex="0"><code>  }
 }
 </code></pre><p>Click Save
 <style>
@@ -485,7 +485,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -745,7 +745,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -857,7 +857,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -867,7 +867,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -950,7 +950,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab13/index.html b/workshops/secure_software_factory/lab13/index.html
index 5e78d2058..c4e073dd4 100644
--- a/workshops/secure_software_factory/lab13/index.html
+++ b/workshops/secure_software_factory/lab13/index.html
@@ -319,48 +319,48 @@ <h1>Lab 13 - Promote and Deploy to Stage</h1>
 
     <h1 id="add-promote-to-stage">Add Promote to Stage</h1>
 <p>Enter the Promote to STAGE below into your pipeline.</p>
-<p><img src="../images/pipeline_promote.png" width="900" /></p>
+<img src="../images/pipeline_promote.png" width="900" />
 <p>We set an approval to promote to the application to the Stage Project.  The approval process is a good feature for various gates of your deployments.  We also set a 15 minute timeout on the approval.  You also tag the tasks image with latest and the version from the pom file.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Promote to STAGE?') {
+<pre tabindex="0"><code>    stage(&#39;Promote to STAGE?&#39;) {
       steps {
-        timeout(time:15, unit:'MINUTES') {
-            input message: &quot;Promote to STAGE?&quot;, ok: &quot;Promote&quot;
+        timeout(time:15, unit:&#39;MINUTES&#39;) {
+            input message: &#34;Promote to STAGE?&#34;, ok: &#34;Promote&#34;
         }
 
         script {
           openshift.withCluster() {
-            openshift.tag(&quot;${env.DEV_PROJECT}/tasks:latest&quot;, &quot;${env.STAGE_PROJECT}/tasks:${version}&quot;)
+            openshift.tag(&#34;${env.DEV_PROJECT}/tasks:latest&#34;, &#34;${env.STAGE_PROJECT}/tasks:${version}&#34;)
           }
         }
       }
     }
 </code></pre><h1 id="add-deploy-stage">Add Deploy Stage</h1>
 <p>Add the Deploy Stage into your pipeline.</p>
-<p><img src="../images/pipeline_deploy_stage.png" width="900" /></p>
+<img src="../images/pipeline_deploy_stage.png" width="900" />
 <p>If the deployment config for the application already exists in the Stage Project or Environment the deployment config , service, and route are deleted.  This allows for the pipeline to be rerun.</p>
 <p>The new-app is recreated in the Stage Environment from the image that you tagged in the previous stage.  The image also has a route created for with the svc.expose command.</p>
 <br>
 # Append to Jenkins Pipeline Configuration
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>Append the text below to the bottom of the Jenkins Pipeline Configuration.  Please make sure to append to the beginning of the next line.</p>
-<pre><code>    stage('Deploy STAGE') {
+<pre tabindex="0"><code>    stage(&#39;Deploy STAGE&#39;) {
       steps {
         script {
           openshift.withCluster() {
             openshift.withProject(env.STAGE_PROJECT) {
-              if (openshift.selector('dc', 'tasks').exists()) {
-                openshift.selector('dc', 'tasks').delete()
-                openshift.selector('svc', 'tasks').delete()
-                openshift.selector('route', 'tasks').delete()
+              if (openshift.selector(&#39;dc&#39;, &#39;tasks&#39;).exists()) {
+                openshift.selector(&#39;dc&#39;, &#39;tasks&#39;).delete()
+                openshift.selector(&#39;svc&#39;, &#39;tasks&#39;).delete()
+                openshift.selector(&#39;route&#39;, &#39;tasks&#39;).delete()
               }
 
-              openshift.newApp(&quot;tasks:${version}&quot;).narrow(&quot;svc&quot;).expose()
+              openshift.newApp(&#34;tasks:${version}&#34;).narrow(&#34;svc&#34;).expose()
             }
           }
         }
@@ -468,7 +468,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -728,7 +728,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -840,7 +840,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -850,7 +850,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -933,7 +933,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab14/index.html b/workshops/secure_software_factory/lab14/index.html
index d52379652..905476769 100644
--- a/workshops/secure_software_factory/lab14/index.html
+++ b/workshops/secure_software_factory/lab14/index.html
@@ -320,13 +320,13 @@ <h1>Lab 14 - Run Pipeline</h1>
     <h1 id="verify-completed-pipeline">Verify Completed Pipeline</h1>
 <p>Before we kick off your pipeline, let&rsquo;s verify it.</p>
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit YAML</p>
-<p><img src="../images/pipeline_actions_edityaml.png" width="900" /></p>
+<img src="../images/pipeline_actions_edityaml.png" width="900" />
 <p>Take a look and see if it matches the below text.  If not, please correct it.</p>
-<pre><code>apiVersion: v1
+<pre tabindex="0"><code>apiVersion: v1
 kind: BuildConfig
 metadata:
     annotations:
-      pipeline.alpha.openshift.io/uses: '[{&quot;name&quot;: &quot;jenkins&quot;, &quot;namespace&quot;: &quot;&quot;, &quot;kind&quot;: &quot;DeploymentConfig&quot;}]'
+      pipeline.alpha.openshift.io/uses: &#39;[{&#34;name&#34;: &#34;jenkins&#34;, &#34;namespace&#34;: &#34;&#34;, &#34;kind&#34;: &#34;DeploymentConfig&#34;}]&#39;
     labels:
       app: cicd-pipeline
       name: cicd-pipeline
@@ -335,10 +335,10 @@ <h1 id="verify-completed-pipeline">Verify Completed Pipeline</h1>
     triggers:
       - type: GitHub
         github:
-          secret: &quot;secret101&quot;
+          secret: &#34;secret101&#34;
       - type: Generic
         generic:
-          secret: &quot;secret101&quot;
+          secret: &#34;secret101&#34;
     runPolicy: Serial
     source:
       type: None
@@ -350,47 +350,47 @@ <h1 id="verify-completed-pipeline">Verify Completed Pipeline</h1>
         - name: STAGE_PROJECT
           value: stage-user<span class="userid">YOUR#</span>
         jenkinsfile: |-
-          def version, mvnCmd = &quot;mvn -s configuration/cicd-settings-nexus3.xml&quot;
+          def version, mvnCmd = &#34;mvn -s configuration/cicd-settings-nexus3.xml&#34;
 
           pipeline {
             agent {
-              label 'maven'
+              label &#39;maven&#39;
             }
             stages {
-              stage('Build App') {
+              stage(&#39;Build App&#39;) {
                 steps {
-                  git branch: 'eap-7', url: 'http://gogs:3000/gogs/openshift-tasks.git'
+                  git branch: &#39;eap-7&#39;, url: &#39;http://gogs:3000/gogs/openshift-tasks.git&#39;
                   script {
-                      def pom = readMavenPom file: 'pom.xml'
+                      def pom = readMavenPom file: &#39;pom.xml&#39;
                       version = pom.version
                   }
-                  sh &quot;${mvnCmd} install -DskipTests=true&quot;
+                  sh &#34;${mvnCmd} install -DskipTests=true&#34;
                 }
               }
-              stage('Test') {
+              stage(&#39;Test&#39;) {
                 steps {
-                  sh &quot;${mvnCmd} test&quot;
-                  step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])
+                  sh &#34;${mvnCmd} test&#34;
+                  step([$class: &#39;JUnitResultArchiver&#39;, testResults: &#39;**/target/surefire-reports/TEST-*.xml&#39;])
                 }
               }
-              stage('Code Analysis') {
+              stage(&#39;Code Analysis&#39;) {
                 steps {
                   script {
-                    sh &quot;${mvnCmd} sonar:sonar -Dsonar.host.url=http://sonarqube:9000 -DskipTests=true&quot;
+                    sh &#34;${mvnCmd} sonar:sonar -Dsonar.host.url=http://sonarqube:9000 -DskipTests=true&#34;
                   }
                 }
               }
-              stage('Archive App') {
+              stage(&#39;Archive App&#39;) {
                 steps {
-                  sh &quot;${mvnCmd} deploy -DskipTests=true -P nexus3&quot;
+                  sh &#34;${mvnCmd} deploy -DskipTests=true -P nexus3&#34;
                 }
               }
-              stage('Create Image Builder') {
+              stage(&#39;Create Image Builder&#39;) {
                 when {
                   expression {
                     openshift.withCluster() {
                       openshift.withProject(env.DEV_PROJECT) {
-                        return !openshift.selector(&quot;bc&quot;, &quot;tasks&quot;).exists();
+                        return !openshift.selector(&#34;bc&#34;, &#34;tasks&#34;).exists();
                       }
                     }
                   }
@@ -399,32 +399,32 @@ <h1 id="verify-completed-pipeline">Verify Completed Pipeline</h1>
                   script {
                     openshift.withCluster() {
                       openshift.withProject(env.DEV_PROJECT) {
-                        openshift.newBuild(&quot;--name=tasks&quot;, &quot;--image-stream=jboss-eap70-openshift:1.5&quot;, &quot;--binary=true&quot;)
+                        openshift.newBuild(&#34;--name=tasks&#34;, &#34;--image-stream=jboss-eap70-openshift:1.5&#34;, &#34;--binary=true&#34;)
                       }
                     }
                   }
                 }
               }
-              stage('Build Image') {
+              stage(&#39;Build Image&#39;) {
                 steps {
-                  sh &quot;rm -rf oc-build &amp;&amp; mkdir -p oc-build/deployments&quot;
-                  sh &quot;cp target/openshift-tasks.war oc-build/deployments/ROOT.war&quot;
+                  sh &#34;rm -rf oc-build &amp;&amp; mkdir -p oc-build/deployments&#34;
+                  sh &#34;cp target/openshift-tasks.war oc-build/deployments/ROOT.war&#34;
 
                   script {
                     openshift.withCluster() {
                       openshift.withProject(env.DEV_PROJECT) {
-                        openshift.selector(&quot;bc&quot;, &quot;tasks&quot;).startBuild(&quot;--from-dir=oc-build&quot;, &quot;--wait=true&quot;)
+                        openshift.selector(&#34;bc&#34;, &#34;tasks&#34;).startBuild(&#34;--from-dir=oc-build&#34;, &#34;--wait=true&#34;)
                       }
                     }
                   }
                 }
               }
-              stage('Create DEV') {
+              stage(&#39;Create DEV&#39;) {
                 when {
                   expression {
                     openshift.withCluster() {
                       openshift.withProject(env.DEV_PROJECT) {
-                        return !openshift.selector('dc', 'tasks').exists()
+                        return !openshift.selector(&#39;dc&#39;, &#39;tasks&#39;).exists()
                       }
                     }
                   }
@@ -433,55 +433,55 @@ <h1 id="verify-completed-pipeline">Verify Completed Pipeline</h1>
                   script {
                     openshift.withCluster() {
                       openshift.withProject(env.DEV_PROJECT) {
-                        def app = openshift.newApp(&quot;tasks:latest&quot;)
-                        app.narrow(&quot;svc&quot;).expose();
+                        def app = openshift.newApp(&#34;tasks:latest&#34;)
+                        app.narrow(&#34;svc&#34;).expose();
 
-                        def dc = openshift.selector(&quot;dc&quot;, &quot;tasks&quot;)
+                        def dc = openshift.selector(&#34;dc&#34;, &#34;tasks&#34;)
                         while (dc.object().spec.replicas != dc.object().status.availableReplicas) {
                             sleep 10
                         }
-                        openshift.set(&quot;triggers&quot;, &quot;dc/tasks&quot;, &quot;--manual&quot;)
+                        openshift.set(&#34;triggers&#34;, &#34;dc/tasks&#34;, &#34;--manual&#34;)
                       }
                     }
                   }
                 }
               }
-              stage('Deploy DEV') {
+              stage(&#39;Deploy DEV&#39;) {
                 steps {
                   script {
                     openshift.withCluster() {
                       openshift.withProject(env.DEV_PROJECT) {
-                        openshift.selector(&quot;dc&quot;, &quot;tasks&quot;).rollout().latest();
+                        openshift.selector(&#34;dc&#34;, &#34;tasks&#34;).rollout().latest();
                       }
                     }
                   }
                 }
               }
-              stage('Promote to STAGE?') {
+              stage(&#39;Promote to STAGE?&#39;) {
                 steps {
-                  timeout(time:15, unit:'MINUTES') {
-                      input message: &quot;Promote to STAGE?&quot;, ok: &quot;Promote&quot;
+                  timeout(time:15, unit:&#39;MINUTES&#39;) {
+                      input message: &#34;Promote to STAGE?&#34;, ok: &#34;Promote&#34;
                   }
 
                   script {
                     openshift.withCluster() {
-                      openshift.tag(&quot;${env.DEV_PROJECT}/tasks:latest&quot;, &quot;${env.STAGE_PROJECT}/tasks:${version}&quot;)
+                      openshift.tag(&#34;${env.DEV_PROJECT}/tasks:latest&#34;, &#34;${env.STAGE_PROJECT}/tasks:${version}&#34;)
                     }
                   }
                 }
               }
-              stage('Deploy STAGE') {
+              stage(&#39;Deploy STAGE&#39;) {
                 steps {
                   script {
                     openshift.withCluster() {
                       openshift.withProject(env.STAGE_PROJECT) {
-                        if (openshift.selector('dc', 'tasks').exists()) {
-                          openshift.selector('dc', 'tasks').delete()
-                          openshift.selector('svc', 'tasks').delete()
-                          openshift.selector('route', 'tasks').delete()
+                        if (openshift.selector(&#39;dc&#39;, &#39;tasks&#39;).exists()) {
+                          openshift.selector(&#39;dc&#39;, &#39;tasks&#39;).delete()
+                          openshift.selector(&#39;svc&#39;, &#39;tasks&#39;).delete()
+                          openshift.selector(&#39;route&#39;, &#39;tasks&#39;).delete()
                         }
 
-                        openshift.newApp(&quot;tasks:${version}&quot;).narrow(&quot;svc&quot;).expose()
+                        openshift.newApp(&#34;tasks:${version}&#34;).narrow(&#34;svc&#34;).expose()
                       }
                     }
                   }
@@ -493,7 +493,7 @@ <h1 id="verify-completed-pipeline">Verify Completed Pipeline</h1>
 </code></pre><br>
 # Verify your user Dev and Stage projects
 <p>In your pipeline text file, make sure &lt;user&gt; reflects your user # and project.</p>
-<pre><code>- name: DEV_PROJECT
+<pre tabindex="0"><code>- name: DEV_PROJECT
   value: dev-user<span class="userid">YOUR#</span>
 - name: STAGE_PROJECT
   value: stage-user<span class="userid">YOUR#</span>
@@ -620,7 +620,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -880,7 +880,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -992,7 +992,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1002,7 +1002,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1085,7 +1085,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab15/index.html b/workshops/secure_software_factory/lab15/index.html
index 3a45ae172..e130ef938 100644
--- a/workshops/secure_software_factory/lab15/index.html
+++ b/workshops/secure_software_factory/lab15/index.html
@@ -326,7 +326,7 @@ <h1 id="verify-webhook-in-gogs">Verify Webhook in Gogs</h1>
 <p>Go to the openshift-tasks repository.</p>
 <p>Select Settings.</p>
 <p>Select Webhooks</p>
-<p>Verify the Webhook.  Make sure the url includes the name &lsquo;tasks-pipeline&rsquo; of the your imported pipeline.</p>
+<p>Verify the Webhook.  Make sure the url includes the name &rsquo;tasks-pipeline&rsquo; of the your imported pipeline.</p>
 <p><img src="../images/gogs-webhook.png" width="900"><br/></p>
 <p>This should match the webhook of the pipeline you previously created except the domain will be openshift.default.svc.cluster.local because the gogs pod calls the internal dns to resolve the address.</p>
 <p>The webhook url is located in builds &gt; pipeline &gt; tasks-pipeline &gt; configuration &gt; generic webhook url</p>
@@ -478,7 +478,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -738,7 +738,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -850,7 +850,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -860,7 +860,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -943,7 +943,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab16/index.html b/workshops/secure_software_factory/lab16/index.html
index 67b84fd36..c67cae389 100644
--- a/workshops/secure_software_factory/lab16/index.html
+++ b/workshops/secure_software_factory/lab16/index.html
@@ -432,7 +432,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -692,7 +692,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -804,7 +804,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -814,7 +814,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -897,7 +897,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab17/index.html b/workshops/secure_software_factory/lab17/index.html
index 4b941bd92..60276ddc3 100644
--- a/workshops/secure_software_factory/lab17/index.html
+++ b/workshops/secure_software_factory/lab17/index.html
@@ -323,7 +323,7 @@ <h1 id="add-clair-container-scan">Add Clair Container Scan</h1>
 <br>
 <h1 id="append-to-jenkins-pipeline-configuration">Append to Jenkins Pipeline Configuration</h1>
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>In your pipeline, add and update the following variables after the version and mvnCmd definitions.  Please fill in the values between the quotes.</p>
 <ul>
 <li>ocuser : the openshift user given to you by your insturctor</li>
@@ -333,29 +333,29 @@ <h1 id="append-to-jenkins-pipeline-configuration">Append to Jenkins Pipeline Con
 <li>quaypass : the quay password you created previously</li>
 <li>quayrepo : the quay repo you will push your app image to i.e. tasks</li>
 </ul>
-<pre><code>def ocuser = &quot; &quot;
-def ocpass = &quot; &quot;
-def ocp = &quot; &quot;
-def quayuser = &quot; &quot;
-def quaypass = &quot; &quot;
-def quayrepo = &quot; &quot;
+<pre tabindex="0"><code>def ocuser = &#34; &#34;
+def ocpass = &#34; &#34;
+def ocp = &#34; &#34;
+def quayuser = &#34; &#34;
+def quaypass = &#34; &#34;
+def quayrepo = &#34; &#34;
 </code></pre><p>For Example:</p>
-<pre><code>def ocuser = &quot;user<span class="userid">YOUR#</span>&quot;
-def ocpass = &quot;openshift&quot;
-def ocp = &quot;master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>&quot;
-def quayuser = &quot;user<span class="userid">YOUR#</span>&quot;
-def quaypass = &quot;openshift&quot;
-def quayrepo = &quot;jboss-eap70-openshift&quot;
+<pre tabindex="0"><code>def ocuser = &#34;user<span class="userid">YOUR#</span>&#34;
+def ocpass = &#34;openshift&#34;
+def ocp = &#34;master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>&#34;
+def quayuser = &#34;user<span class="userid">YOUR#</span>&#34;
+def quaypass = &#34;openshift&#34;
+def quayrepo = &#34;jboss-eap70-openshift&#34;
 </code></pre><p>In your pipeline, replace the Jenkins agent &lsquo;maven&rsquo; with &lsquo;jenkins-slave-image-mgmt&rsquo;.</p>
-<pre><code>pipeline {
+<pre tabindex="0"><code>pipeline {
   agent {
-    label 'jenkins-slave-image-mgmt'
+    label &#39;jenkins-slave-image-mgmt&#39;
   }
 </code></pre><p>In your pipeline, add the Vulnerability Scan Stage after the Build Image Stage.</p>
-<pre><code>    stage('Clair Container Vulnerability Scan') {
+<pre tabindex="0"><code>    stage(&#39;Clair Container Vulnerability Scan&#39;) {
       steps {
-            sh &quot;oc login -u $ocuser -p $ocpass --insecure-skip-tls-verify https://$ocp 2&gt;&amp;1&quot;
-            sh 'skopeo --debug copy --src-creds=&quot;$(oc whoami)&quot;:&quot;$(oc whoami -t)&quot; --src-tls-verify=false --dest-tls-verify=false' + &quot; --dest-creds=$quayuser:$quaypass docker://docker-registry.default.svc:5000/cicd-$ocuser/jboss-eap70-openshift:1.5 docker://quay-enterprise-quay-enterprise.apps.$ocp/$quayuser/$quayrepo:1.5&quot;
+            sh &#34;oc login -u $ocuser -p $ocpass --insecure-skip-tls-verify https://$ocp 2&gt;&amp;1&#34;
+            sh &#39;skopeo --debug copy --src-creds=&#34;$(oc whoami)&#34;:&#34;$(oc whoami -t)&#34; --src-tls-verify=false --dest-tls-verify=false&#39; + &#34; --dest-creds=$quayuser:$quaypass docker://docker-registry.default.svc:5000/cicd-$ocuser/jboss-eap70-openshift:1.5 docker://quay-enterprise-quay-enterprise.apps.$ocp/$quayuser/$quayrepo:1.5&#34;
         }
     }
 </code></pre><p>Save your Jenkins file</p>
@@ -479,7 +479,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -739,7 +739,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -851,7 +851,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -861,7 +861,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -944,7 +944,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/lab18/index.html b/workshops/secure_software_factory/lab18/index.html
index 2c565caa2..4c8675862 100644
--- a/workshops/secure_software_factory/lab18/index.html
+++ b/workshops/secure_software_factory/lab18/index.html
@@ -323,32 +323,32 @@ <h1 id="add-openscap-disa-stig-scan">Add OpenSCAP DISA STIG Scan</h1>
 <br>
 <h1 id="append-to-jenkins-pipeline-configuration">Append to Jenkins Pipeline Configuration</h1>
 <p>In Builds &gt; Pipelines &gt; tasks-pipeline &gt; Actions &gt; Edit</p>
-<p><img src="../images/pipeline_actions_edit.png" width="900" /></p>
+<img src="../images/pipeline_actions_edit.png" width="900" />
 <p>In your pipeline, verify the following variables are there after the version and mvnCmd definitions.  Please fill in the values between the quotes if not done previously.</p>
 <ul>
 <li>ocuser : the openshift user given to you by your insturctor</li>
 <li>ocpass : the openshift password given to you by your insturctor</li>
 <li>ocp : the openshift host given to you by your instuctor</li>
 </ul>
-<pre><code>def ocuser = &quot; &quot;
-def ocpass = &quot; &quot;
-def ocp = &quot; &quot;
+<pre tabindex="0"><code>def ocuser = &#34; &#34;
+def ocpass = &#34; &#34;
+def ocp = &#34; &#34;
 </code></pre><p>For Example:</p>
-<pre><code>def ocuser = &quot;user<span class="userid">YOUR#</span>&quot;
-def ocpass = &quot;openshift&quot;
-def ocp = &quot;master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>&quot;
+<pre tabindex="0"><code>def ocuser = &#34;user<span class="userid">YOUR#</span>&#34;
+def ocpass = &#34;openshift&#34;
+def ocp = &#34;master.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>&#34;
 </code></pre><p>In your pipeline, make sure you replaced the Jenkins agent &lsquo;maven&rsquo; with &lsquo;jenkins-slave-image-mgmt&rsquo;.</p>
-<pre><code>pipeline {
+<pre tabindex="0"><code>pipeline {
   agent {
-    label 'jenkins-slave-image-mgmt'
+    label &#39;jenkins-slave-image-mgmt&#39;
   }
 </code></pre><p>In your pipeline, add the OpenSCAP DISA STIG Scan after the Container Vulnerability Scan Stage.</p>
-<pre><code>    stage('OSCAP DISA STIG Scan') {
+<pre tabindex="0"><code>    stage(&#39;OSCAP DISA STIG Scan&#39;) {
       steps {
-          sh &quot;oc login -u $ocuser -p $ocpass --insecure-skip-tls-verify https://$ocp 2&gt;&amp;1&quot;
-          sh &quot;sshpass -p $ocpass ssh -oStrictHostKeyChecking=no -t $ocuser@$ocp docker login -u $ocuser -p &quot; + '&quot;$(oc whoami -t)&quot;' + &quot; docker-registry-default.apps.$ocp&quot;
-          sh &quot;sshpass -p $ocpass ssh -oStrictHostKeyChecking=no -t $ocuser@$ocp docker pull docker-registry-default.apps.$ocp/dev-$ocuser/tasks:latest&quot;
-          sh &quot;sshpass -p $ocpass ssh -oStrictHostKeyChecking=no -t $ocuser@$ocp sudo oscap-docker image docker-registry-default.apps.$ocp/dev-$ocuser/tasks:latest xccdf eval --profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa --report report.html /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml&quot;
+          sh &#34;oc login -u $ocuser -p $ocpass --insecure-skip-tls-verify https://$ocp 2&gt;&amp;1&#34;
+          sh &#34;sshpass -p $ocpass ssh -oStrictHostKeyChecking=no -t $ocuser@$ocp docker login -u $ocuser -p &#34; + &#39;&#34;$(oc whoami -t)&#34;&#39; + &#34; docker-registry-default.apps.$ocp&#34;
+          sh &#34;sshpass -p $ocpass ssh -oStrictHostKeyChecking=no -t $ocuser@$ocp docker pull docker-registry-default.apps.$ocp/dev-$ocuser/tasks:latest&#34;
+          sh &#34;sshpass -p $ocpass ssh -oStrictHostKeyChecking=no -t $ocuser@$ocp sudo oscap-docker image docker-registry-default.apps.$ocp/dev-$ocuser/tasks:latest xccdf eval --profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa --report report.html /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml&#34;
         }
       } 
 </code></pre><p>Save your Jenkins file</p>
@@ -464,7 +464,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -724,7 +724,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -836,7 +836,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -846,7 +846,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -929,7 +929,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/login_tour_wetty/index.html b/workshops/secure_software_factory/login_tour_wetty/index.html
index a59a88da8..79867a043 100644
--- a/workshops/secure_software_factory/login_tour_wetty/index.html
+++ b/workshops/secure_software_factory/login_tour_wetty/index.html
@@ -322,10 +322,10 @@ <h1 id="introduction-to-wetty-browser-based-ssh">Introduction to Wetty (Browser-
 <h1 id="accessing-wetty">Accessing Wetty</h1>
 <p>Ask your instructor for the wetty URL.</p>
 <h3 id="login-info">Login Info</h3>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">login:    user<span class="userid">YOUR#</span>
-Password: &lt;Instructor Provided&gt;
-</code></pre></div><p>After logging in, you should see a shell.</p>
-<p><img src="../images/wetty.png" width="1000" /></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>login:    user<span class="userid">YOUR#</span>
+</span></span><span style="display:flex;"><span>Password: &lt;Instructor Provided&gt;
+</span></span></code></pre></div><p>After logging in, you should see a shell.</p>
+<img src="../images/wetty.png" width="1000" />
 <p>The wetty instance will already have the &lsquo;oc&rsquo; command installed on them. The &lsquo;oc&rsquo; command is used to connect to the OpenShift Master.</p>
 <style>
 
@@ -426,7 +426,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -686,7 +686,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -798,7 +798,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -808,7 +808,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -891,7 +891,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/prerequisites/index.html b/workshops/secure_software_factory/prerequisites/index.html
index dc2d21a40..2436959ff 100644
--- a/workshops/secure_software_factory/prerequisites/index.html
+++ b/workshops/secure_software_factory/prerequisites/index.html
@@ -420,7 +420,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -680,7 +680,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -792,7 +792,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -802,7 +802,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -881,7 +881,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/secure_software_factory/readme/index.html b/workshops/secure_software_factory/readme/index.html
index b912b9ad5..f3503df82 100644
--- a/workshops/secure_software_factory/readme/index.html
+++ b/workshops/secure_software_factory/readme/index.html
@@ -315,7 +315,7 @@ <h1 id="batch-delete">Batch Delete</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/index.html b/workshops/security_container_intro/index.html
index e80f936ce..4655cd038 100644
--- a/workshops/security_container_intro/index.html
+++ b/workshops/security_container_intro/index.html
@@ -295,14 +295,14 @@ <h3 id="_red_hat_summit_2020">Red Hat Summit 2020</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_container_intro/images/container-tools.png" alt="Container Tools Image">
+<img src="/workshops/security_container_intro/images/container-tools.png" alt="Container Tools Image"/>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_abstract">Abstract</h3>
 <div class="paragraph">
-<p>Linux containers provide convenient application packaging and run-time isolation in multi-tenant environments. However, the security implications of running containerized applications is often taken for granted. For example, today it is very easy to pull container images from the internet and run them in the enterprise without examining their content and authenticity. In this lab, you&#8217;ll complete a series of hands on exercises aimed at understanding the concepts, challenges and best practices associated with deploying containers in a secure fashion.</p>
+<p>Linux containers provide convenient application packaging and run-time isolation in multi-tenant environments. However, the security implications of running containerized applications is often taken for granted. For example, today it is very easy to pull container images from the internet and run them in the enterprise without examining their content and authenticity. In this lab, you’ll complete a series of hands on exercises aimed at understanding the concepts, challenges and best practices associated with deploying containers in a secure fashion.</p>
 </div>
 </div>
 </div>
@@ -471,7 +471,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -731,7 +731,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -843,7 +843,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -853,7 +853,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -906,7 +906,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/index.xml b/workshops/security_container_intro/index.xml
index bd5df30ca..908760565 100644
--- a/workshops/security_container_intro/index.xml
+++ b/workshops/security_container_intro/index.xml
@@ -4,96 +4,71 @@
     <title>Container Security - A Practical Introduction on Red Hat | Public Sector</title>
     <link>/workshops/security_container_intro/</link>
     <description>Recent content in Container Security - A Practical Introduction on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/security_container_intro/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/security_container_intro/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Conclusion - Closing thoughts &amp; homework</title>
       <link>/workshops/security_container_intro/lab99-conclusion/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab99-conclusion/</guid>
       <description>As a final homework assignment, we encourage you to watch a video entitled the State of Container Security that Sally and Urvashi presented at an OpenShift Commons briefing on March 27, 2020. Their talk goes into additional detail on many of the concepts covered in this lab along with a sneak peak at future work by the upstream community. They also show some great demos that you will want to see.</description>
     </item>
-    
     <item>
       <title>Lab 1.0 - Workshop introduction</title>
       <link>/workshops/security_container_intro/lab01-intro/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab01-intro/</guid>
-      <description>Table of Contents Important Conventions used in this lab Getting access to the servers     This lab session is a low-level, hands-on introduction to container security using the container tools included with Red Hat Enterprise Linux 8. It is intended to be consumed as a series of self paced exercises.
- Prerequisites   An introductory knowledge of Linux and containers is helpful.
-  Basic text editing skills using vim or nano.</description>
+      <description>This lab session is a low-level, hands-on introduction to container security using the container tools included with Red Hat Enterprise Linux 8. It is intended to be consumed as a series of self paced exercises.&#xA;Prerequisites An introductory knowledge of Linux and containers is helpful.&#xA;Basic text editing skills using vim or nano.&#xA;Lab Environment&#xA;Figure 1. Lab Environment Table 1. Lab Resources Server Function bastion&#xA;External ssh and container host</description>
     </item>
-    
     <item>
       <title>Lab 2.0 - Container registries</title>
       <link>/workshops/security_container_intro/lab02-registry/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab02-registry/</guid>
-      <description>Table of Contents Configuring the registries Node 1 Testing the registries Node 2 Testing the registries Configuring and testing the bastion     During this module you will configure both nodes to host secure container registries. The registry software runs in a container and listens on port 5000. Configuring the registry consists of generating a self-signed SSL certificate and running the container. Two simple bash scripts are provided to do this.</description>
+      <description>During this module you will configure both nodes to host secure container registries. The registry software runs in a container and listens on port 5000. Configuring the registry consists of generating a self-signed SSL certificate and running the container. Two simple bash scripts are provided to do this. Once the registries are configured and running, the curl command can be used to test basic connectivity.&#xA;Configuring the registries Node 1 Login to node1-0.</description>
     </item>
-    
     <item>
       <title>Lab 3.0 - Intro to Podman and base images</title>
       <link>/workshops/security_container_intro/lab03-podman/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab03-podman/</guid>
-      <description>Table of Contents What is a pod? The Universal Base Image Tagging and pushing images to a remote registry Working with root and rootless containers. Stopping and removing containers Container process information User Namespace Support Auditing containers UID Mapping Challenge References     What is a pod? A pod is a group of one or more containers with shared storage, network and a specification for how to run the containers.</description>
+      <description>What is a pod? A pod is a group of one or more containers with shared storage, network and a specification for how to run the containers. In this module you’ll be working at the container level. Since you are here to learn more about container security, we have a quick review of container basics then get right into the good stuff.&#xA;Podman (Pod Manager) is a fully featured container engine that is a simple daemon-less tool.</description>
     </item>
-    
     <item>
       <title>Lab 4.0 - Linux kernel capabilities</title>
       <link>/workshops/security_container_intro/lab04-isolation/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab04-isolation/</guid>
-      <description>Table of Contents Capabilities Exploring the capabilities of containers. Examining container processes Capabilities Challenge #1 Capabilities Challenge #2 Capabilities Challenge #3 Example Solutions to Challenges     Containers provide a certain degree of process isolation via kernel namespaces. In this module, we’ll examine the capabilities of a process running in a containerized namespace. Specifically we&amp;#8217;ll look at how Linux capabilities can be used to grant a particular or subset of root privileges to a process running in a container.</description>
+      <description>Containers provide a certain degree of process isolation via kernel namespaces. In this module, we’ll examine the capabilities of a process running in a containerized namespace. Specifically we’ll look at how Linux capabilities can be used to grant a particular or subset of root privileges to a process running in a container.&#xA;It would be worth taking a few minutes to read this blog post before beginning this lab.</description>
     </item>
-    
     <item>
       <title>Lab 5.0 - SELinux container integration</title>
       <link>/workshops/security_container_intro/lab05-selinux/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab05-selinux/</guid>
-      <description>Table of Contents !Namespaced Warmup Exercise Bind Mounts and Labeling Private Mounts Shared Mounts Read-Only Containers     In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations where the other security mechanisms fail. By default, podman processes are labeled with container_runtime_t and they are prevented from doing (almost) all SELinux operations. But processes within containers do not know that they are running within a container.</description>
+      <description>In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations where the other security mechanisms fail. By default, podman processes are labeled with container_runtime_t and they are prevented from doing (almost) all SELinux operations. But processes within containers do not know that they are running within a container. SELinux-aware applications are going to attempt to do SELinux operations, especially if they are running as root.</description>
     </item>
-    
     <item>
       <title>Lab 6.0 - Container inspection with Podman &amp; Skopeo</title>
       <link>/workshops/security_container_intro/lab06-inspecting/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab06-inspecting/</guid>
-      <description>Table of Contents Podman inspect Podman diff Podman live mounts Working with Skopeo Inspecting images     Container images can easily be pulled from any public registry and run on a container host but is this good practice? Can you trust this image and what are its contents? A better practice would be to inspect the image before running it.
- Podman inspect Use podman to inspect the registry.</description>
+      <description>Container images can easily be pulled from any public registry and run on a container host but is this good practice? Can you trust this image and what are its contents? A better practice would be to inspect the image before running it.&#xA;Podman inspect Use podman to inspect the registry.access.redhat.com/ubi8/ubi image. Remember, this image must be present in local storage. Examine the output to determine who is the maintainer and what is the version of that image?</description>
     </item>
-    
     <item>
       <title>Lab 7.0 - Container image signing</title>
       <link>/workshops/security_container_intro/lab07-signing/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab07-signing/</guid>
-      <description>Table of Contents Configuring the signature claim store Generating key pairs Working with trust policies Pulling signed images Create a trust policy for Red Hat images. Blocking a registry     In this lab, you will use podman to sign container images and create trust policies to control access to registries.
- To begin the image signing procedure, a signature claim is generated by encrypting a container image manifest using a private gpg key.</description>
+      <description>In this lab, you will use podman to sign container images and create trust policies to control access to registries.&#xA;To begin the image signing procedure, a signature claim is generated by encrypting a container image manifest using a private gpg key. The signature claims are stored in a file system or web server where they can be decrypted later and used to pull signed images.&#xA;The procedure is reversed when pulling signed images.</description>
     </item>
-    
     <item>
       <title>Lab 8.0 - Composing containers with Buildah</title>
       <link>/workshops/security_container_intro/lab08-builds/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_container_intro/lab08-builds/</guid>
-      <description>Table of Contents Building from Universal Base Images Build using Docker (BuD)   This module will introduce Buildah, a command line tool for building Open Container Initiative compatible container images. Buildah is easy to incorporate into scripts and build pipelines, and best of all, it doesn&amp;#8217;t require a running container daemon to build its image. You can read more about Buildah at the buildah.io web site. Also, have a look at the buildah chapter in the RHEL 8 documentation.</description>
+      <description>This module will introduce Buildah, a command line tool for building Open Container Initiative compatible container images. Buildah is easy to incorporate into scripts and build pipelines, and best of all, it doesn’t require a running container daemon to build its image. You can read more about Buildah at the buildah.io web site. Also, have a look at the buildah chapter in the RHEL 8 documentation.&#xA;Building from Universal Base Images Below are the basic steps for building a container image from a UBI.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/security_container_intro/lab01-intro/index.html b/workshops/security_container_intro/lab01-intro/index.html
index a980ed837..8ac9b2447 100644
--- a/workshops/security_container_intro/lab01-intro/index.html
+++ b/workshops/security_container_intro/lab01-intro/index.html
@@ -313,17 +313,7 @@ <h1>Lab 1.0 - Workshop introduction</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_important">Important</a>
-<ul class="sectlevel2">
-<li><a href="#_conventions_used_in_this_lab">Conventions used in this lab</a></li>
-<li><a href="#_getting_access_to_the_servers">Getting access to the servers</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="paragraph">
 <p>This lab session is a low-level, hands-on introduction to container security using the container tools included with Red Hat Enterprise Linux 8. It is intended to be consumed as a series of self paced exercises.</p>
 </div>
@@ -343,15 +333,15 @@ <h1>Lab 1.0 - Workshop introduction</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_container_intro/images/lab-diagram.png" alt="Lab diagram">
+<img src="/workshops/security_container_intro/images/lab-diagram.png" alt="Lab diagram"/>
 </div>
 <div class="title">Figure 1. Lab Environment</div>
 </div>
 <table class="tableblock frame-all grid-all stretch">
 <caption class="title">Table 1. Lab Resources</caption>
 <colgroup>
-<col style="width: 50%;">
-<col style="width: 50%;">
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
 </colgroup>
 <thead>
 <tr>
@@ -381,7 +371,7 @@ <h2 id="_important">Important</h2>
 <div class="sectionbody">
 <div class="admonitionblock tip">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-tip" title="Tip"></i>
 </td>
@@ -389,7 +379,7 @@ <h2 id="_important">Important</h2>
 These servers can not be rebuilt in a timely fashion.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="ulist">
 <div class="title">TIPS</div>
@@ -444,14 +434,14 @@ <h4 id="_use_ssh_to_login_to_the_nodes_from_the_bastion">Use <code>ssh</code> to
 </div>
 </div>
 <div class="paragraph">
-<p>For each node, you will be asked to confirm that the key fingerprint is OK, as you haven&#8217;t logged into it, before.</p>
+<p>For each node, you will be asked to confirm that the key fingerprint is OK, as you haven’t logged into it, before.</p>
 </div>
 <div class="paragraph">
 <p>Node 1:</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>The authenticity of host 'node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span> (10.0.2.128)' can't be established.
+<pre>The authenticity of host &#39;node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span> (10.0.2.128)&#39; can&#39;t be established.
 ECDSA key fingerprint is SHA256:X6KOWD5YgDqcGxnSKDgT0ZYWqBeG8yw9CKTvgFwT6sQ.
 Are you sure you want to continue connecting (yes/no/[fingerprint])?</pre>
 </div>
@@ -472,7 +462,7 @@ <h4 id="_use_ssh_to_login_to_the_nodes_from_the_bastion">Use <code>ssh</code> to
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>The authenticity of host 'node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span> (10.0.2.125)' can't be established.
+<pre>The authenticity of host &#39;node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span> (10.0.2.125)&#39; can&#39;t be established.
 ECDSA key fingerprint is SHA256:n2/LxFOXS2of8osIEcY/5911N6OmqaJJpsYRgnVrsiA.
 Are you sure you want to continue connecting (yes/no/[fingerprint])?</pre>
 </div>
@@ -489,7 +479,7 @@ <h4 id="_use_ssh_to_login_to_the_nodes_from_the_bastion">Use <code>ssh</code> to
 <p>Logout when done.</p>
 </div>
 <div class="paragraph">
-<p>Now, let&#8217;s move on to lab #2!</p>
+<p>Now, let’s move on to lab #2!</p>
 </div>
 <div class="paragraph">
 <style>
@@ -591,7 +581,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -851,7 +841,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -963,7 +953,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -973,7 +963,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1057,7 +1047,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab02-registry/index.html b/workshops/security_container_intro/lab02-registry/index.html
index 79831f629..add8a1b41 100644
--- a/workshops/security_container_intro/lab02-registry/index.html
+++ b/workshops/security_container_intro/lab02-registry/index.html
@@ -317,20 +317,7 @@ <h1>Lab 2.0 - Container registries</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#anchor-1">Configuring the registries</a>
-<ul class="sectlevel2">
-<li><a href="#_node_1">Node 1</a></li>
-<li><a href="#_testing_the_registries">Testing the registries</a></li>
-<li><a href="#_node_2">Node 2</a></li>
-<li><a href="#_testing_the_registries_2">Testing the registries</a></li>
-<li><a href="#_configuring_and_testing_the_bastion">Configuring and testing the bastion</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="paragraph">
 <p>During this module you will configure both nodes to host secure container registries.
 The registry software runs in a container and listens on port 5000. Configuring the
@@ -352,14 +339,14 @@ <h3 id="_node_1">Node 1</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>You&#8217;ll be asked to confirm the key fingerprint, the first time that you login. Please answer <code>yes</code>.</p>
+<p>You’ll be asked to confirm the key fingerprint, the first time that you login. Please answer <code>yes</code>.</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>The authenticity of host 'node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span> (10.0.2.88)' can't be established.
+<pre>The authenticity of host &#39;node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span> (10.0.2.88)&#39; can&#39;t be established.
 ECDSA key fingerprint is SHA256:t019FDEhEgp1uhivEZy1gwqaNaXM75tOem4MHpmLRaw.
 Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
-Warning: Permanently added 'node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>,10.0.2.88' (ECDSA) to the list of known hosts.
+Warning: Permanently added &#39;node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>,10.0.2.88&#39; (ECDSA) to the list of known hosts.
 Last login: Tue Jan 12 02:10:26 2021 from 10.0.2.245
 [ec2-user@ip-10-0-2-88 ~]$</pre>
 </div>
@@ -389,7 +376,7 @@ <h3 id="_node_1">Node 1</h3>
 <pre>Generating a RSA private key
 ........................................................++++
 .......................................++++
-writing new private key to 'myserver.key'
+writing new private key to &#39;myserver.key&#39;
 -----
 Signature ok
 subject=C = CH, O = Summit, CN = node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>
@@ -439,7 +426,7 @@ <h3 id="_testing_the_registries">Testing the registries</h3>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>{"repositories":[]}</pre>
+<pre>{&#34;repositories&#34;:[]}</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -462,14 +449,14 @@ <h3 id="_node_2">Node 2</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>You&#8217;ll be asked to confirm the key fingerprint, the first time that you login. Please answer <code>yes</code>.</p>
+<p>You’ll be asked to confirm the key fingerprint, the first time that you login. Please answer <code>yes</code>.</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>The authenticity of host 'jajcs.node2.0.rhnaps.io (10.0.2.88)' can't be established.
+<pre>The authenticity of host &#39;jajcs.node2.0.rhnaps.io (10.0.2.88)&#39; can&#39;t be established.
 ECDSA key fingerprint is SHA256:t019FDEhEgp1uhivEZy1gwqaNaXM75tOem4MHpmLRaw.
 Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
-Warning: Permanently added 'jajcs.node2.0.rhnaps.io,10.0.2.88' (ECDSA) to the list of known hosts.
+Warning: Permanently added &#39;jajcs.node2.0.rhnaps.io,10.0.2.88&#39; (ECDSA) to the list of known hosts.
 Last login: Tue Jan 12 02:10:26 2021 from 10.0.2.245
 [ec2-user@ip-10-0-2-88 ~]$</pre>
 </div>
@@ -499,7 +486,7 @@ <h3 id="_node_2">Node 2</h3>
 <pre>Generating a RSA private key
 ........................................................++++
 .......................................++++
-writing new private key to 'myserver.key'
+writing new private key to &#39;myserver.key&#39;
 -----
 Signature ok
 subject=C = CH, O = Summit, CN = node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>
@@ -549,7 +536,7 @@ <h3 id="_testing_the_registries_2">Testing the registries</h3>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>{"repositories":[]}</pre>
+<pre>{&#34;repositories&#34;:[]}</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -573,7 +560,7 @@ <h3 id="_configuring_and_testing_the_bastion">Configuring and testing the bastio
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>{"repositories":[]}</pre>
+<pre>{&#34;repositories&#34;:[]}</pre>
 </div>
 </div>
 <div class="listingblock">
@@ -583,7 +570,7 @@ <h3 id="_configuring_and_testing_the_bastion">Configuring and testing the bastio
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>{"repositories":[]}</pre>
+<pre>{&#34;repositories&#34;:[]}</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -689,7 +676,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -949,7 +936,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1061,7 +1048,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1071,7 +1058,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1158,7 +1145,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab03-podman/index.html b/workshops/security_container_intro/lab03-podman/index.html
index 75cdd82a2..f8626acd7 100644
--- a/workshops/security_container_intro/lab03-podman/index.html
+++ b/workshops/security_container_intro/lab03-podman/index.html
@@ -317,30 +317,12 @@ <h1>Lab 3.0 - Intro to Podman and base images</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_what_is_a_pod">What is a pod?</a>
-<ul class="sectlevel2">
-<li><a href="#_the_universal_base_image">The Universal Base Image</a></li>
-<li><a href="#_tagging_and_pushing_images_to_a_remote_registry">Tagging and pushing images to a remote registry</a></li>
-<li><a href="#_working_with_root_and_rootless_containers">Working with root and rootless containers.</a></li>
-<li><a href="#_stopping_and_removing_containers">Stopping and removing containers</a></li>
-<li><a href="#_container_process_information">Container process information</a></li>
-<li><a href="#_user_namespace_support">User Namespace Support</a></li>
-<li><a href="#_auditing_containers">Auditing containers</a></li>
-<li><a href="#_uid_mapping">UID Mapping</a></li>
-<li><a href="#_challenge">Challenge</a></li>
-<li><a href="#_references">References</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="sect1">
 <h2 id="_what_is_a_pod">What is a pod?</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>A pod is a group of one or more containers with shared storage, network and a specification for how to run the containers. In this module you&#8217;ll be working at the container level. Since you are here to learn more about
+<p>A pod is a group of one or more containers with shared storage, network and a specification for how to run the containers. In this module you’ll be working at the container level. Since you are here to learn more about
 container security, we have a quick review of
 container basics then get right into the good stuff.</p>
 </div>
@@ -361,7 +343,7 @@ <h3 id="_the_universal_base_image">The Universal Base Image</h3>
 <p>For this first part of the lab, we will be using the most current Fedora (the community upstream distribution for Red Hat Enterprise Linux) container image.</p>
 </div>
 <div class="paragraph">
-<p>Pull the latest Fedora image from RedHat&#8217;s container registry:</p>
+<p>Pull the latest Fedora image from RedHat’s container registry:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -370,7 +352,7 @@ <h3 id="_the_universal_base_image">The Universal Base Image</h3>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>Resolved "fedora" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
+<pre>Resolved &#34;fedora&#34; as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
 Trying to pull registry.fedoraproject.org/fedora:latest...
 Getting image source signatures
 Copying blob ca594071dfff done
@@ -389,10 +371,10 @@ <h3 id="_the_universal_base_image">The Universal Base Image</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Notice that pulling Fedora does not require authentication from RedHat&#8217;s registries.</p>
+<p>Notice that pulling Fedora does not require authentication from RedHat’s registries.</p>
 </div>
 <div class="paragraph">
-<p>Next, we&#8217;ll work with the registries that were configured
+<p>Next, we’ll work with the registries that were configured
 in the previous modules.</p>
 </div>
 </div>
@@ -491,17 +473,17 @@ <h3 id="_tagging_and_pushing_images_to_a_remote_registry">Tagging and pushing im
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>{"repositories":["fedora/latest"]}</pre>
+<pre>{&#34;repositories&#34;:[&#34;fedora/latest&#34;]}</pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_working_with_root_and_rootless_containers">Working with root and rootless containers.</h3>
 <div class="paragraph">
-<p>Podman supports storing and running root and rootless containers. Effectively, each user manages it&#8217;s own containers.</p>
+<p>Podman supports storing and running root and rootless containers. Effectively, each user manages it’s own containers.</p>
 </div>
 <div class="paragraph">
-<p>The UBI container images should be loaded into the podman&#8217;s local image storage for both root and rootless (ec2-user) usage.</p>
+<p>The UBI container images should be loaded into the podman’s local image storage for both root and rootless (ec2-user) usage.</p>
 </div>
 <div class="paragraph">
 <p>Confirm these images exist using <code>podman</code>. Note the <code>podman</code> command may be run as <strong>root</strong> (privileged) or as a <strong>root-less</strong> (non-privileged) user.</p>
@@ -531,7 +513,7 @@ <h3 id="_working_with_root_and_rootless_containers">Working with root and rootle
 </div>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s start with a few warmup exercises. Note that a random <em>container ID</em> is returned when the container starts.</p>
+<p>Let’s start with a few warmup exercises. Note that a random <em>container ID</em> is returned when the container starts.</p>
 </div>
 <div class="paragraph">
 <p>Run a rootless container:</p>
@@ -602,7 +584,7 @@ <h3 id="_working_with_root_and_rootless_containers">Working with root and rootle
 </div>
 </div>
 <div class="paragraph">
-<p>Note that podman automatically pulled down the UBI image for each request. This is because we hadn&#8217;t used that image, before.</p>
+<p>Note that podman automatically pulled down the UBI image for each request. This is because we hadn’t used that image, before.</p>
 </div>
 </div>
 <div class="sect2">
@@ -701,11 +683,11 @@ <h3 id="_user_namespace_support">User Namespace Support</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Compare those ID&#8217;s to the same process running in the hosts' namespace:</p>
+<p>Compare those ID’s to the same process running in the hosts&#39; namespace:</p>
 </div>
 <div class="admonitionblock tip">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-tip" title="Tip"></i>
 </td>
@@ -713,10 +695,10 @@ <h3 id="_user_namespace_support">User Namespace Support</h3>
 Take note of 2 important concepts from this example.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
-<p>The <code>sleep</code> process in the container is owned by <code>root</code> but the process on the host is owned by <code>ec2-user</code>. This is user namespaces in action. The <strong>fork/exec</strong> model used by podman improves the security auditing of containers. It allows an administrator to identify users that run containers as root. Container engines that use a <strong><strong>client/server</strong></strong> model can&#8217;t provide this.</p>
+<p>The <code>sleep</code> process in the container is owned by <code>root</code> but the process on the host is owned by <code>ec2-user</code>. This is user namespaces in action. The <strong>fork/exec</strong> model used by podman improves the security auditing of containers. It allows an administrator to identify users that run containers as root. Container engines that use a <strong><strong>client/server</strong></strong> model can’t provide this.</p>
 </div>
 <div class="paragraph">
 <p>The <code>sleep</code> process in the container has a PID of 1 but on the host the PID is <strong>rootless</strong> (a PID &gt;1). This is kernel namespaces in action.</p>
@@ -737,7 +719,7 @@ <h3 id="_auditing_containers">Auditing containers</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo podman run --name sleepy --rm -it registry.access.redhat.com/ubi8/ubi bash -c "cat /proc/self/loginuid;echo"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo podman run --name sleepy --rm -it registry.access.redhat.com/ubi8/ubi bash -c &#34;cat /proc/self/loginuid;echo&#34;</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -754,7 +736,7 @@ <h3 id="_auditing_containers">Auditing containers</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Run a privileged container that bind mounts the host&#8217;s file system then touches <code>/etc/shadow</code>:</p>
+<p>Run a privileged container that bind mounts the host’s file system then touches <code>/etc/shadow</code>:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -766,7 +748,7 @@ <h3 id="_auditing_containers">Auditing containers</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo ausearch -m path -ts recent -i | grep touch | grep --color=auto 'auid=[^ ]*'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo ausearch -m path -ts recent -i | grep touch | grep --color=auto &#39;auid=[^ ]*&#39;</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -776,7 +758,7 @@ <h3 id="_auditing_containers">Auditing containers</h3>
 </div>
 <div class="admonitionblock tip">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-tip" title="Tip"></i>
 </td>
@@ -786,13 +768,13 @@ <h3 id="_auditing_containers">Auditing containers</h3>
 In other words, the malicious user is unknown.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_uid_mapping">UID Mapping</h3>
 <div class="paragraph">
-<p>A container administrator can make use podman&#8217;s <strong>--uidmap</strong> option to force a range of UID&#8217;s to be used. See <strong>podman-run(1)</strong> for details.</p>
+<p>A container administrator can make use podman’s <strong>--uidmap</strong> option to force a range of UID’s to be used. See <strong>podman-run(1)</strong> for details.</p>
 </div>
 <div class="paragraph">
 <p>Run a container that maps <strong>5000</strong> UIDs starting at <strong>100,000</strong>. This example maps uids <strong>0-5000</strong> in the container to the uids <strong>100,000 - 104,999</strong> on the host:</p>
@@ -1005,7 +987,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1265,7 +1247,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1377,7 +1359,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1387,7 +1369,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1474,7 +1456,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab04-isolation/index.html b/workshops/security_container_intro/lab04-isolation/index.html
index d2e67bdac..4fea61c02 100644
--- a/workshops/security_container_intro/lab04-isolation/index.html
+++ b/workshops/security_container_intro/lab04-isolation/index.html
@@ -317,23 +317,9 @@ <h1>Lab 4.0 - Linux kernel capabilities</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_capabilities">Capabilities</a>
-<ul class="sectlevel2">
-<li><a href="#_exploring_the_capabilities_of_containers">Exploring the capabilities of containers.</a></li>
-<li><a href="#_examining_container_processes">Examining container processes</a></li>
-<li><a href="#_capabilities_challenge_1">Capabilities Challenge #1</a></li>
-<li><a href="#_capabilities_challenge_2">Capabilities Challenge #2</a></li>
-<li><a href="#_capabilities_challenge_3">Capabilities Challenge #3</a></li>
-<li><a href="#_example_solutions_to_challenges">Example Solutions to Challenges</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="paragraph">
-<p>Containers provide a certain degree of process isolation via kernel namespaces. In this module, we’ll examine the capabilities of a process running in a containerized namespace. Specifically we&#8217;ll look at how Linux capabilities can be used to grant a particular or subset of root privileges to a process running in a container.</p>
+<p>Containers provide a certain degree of process isolation via kernel namespaces. In this module, we’ll examine the capabilities of a process running in a containerized namespace. Specifically we’ll look at how Linux capabilities can be used to grant a particular or subset of root privileges to a process running in a container.</p>
 </div>
 <div class="paragraph">
 <p>It would be worth taking a few minutes to read this <a href="http://rhelblog.redhat.com/2016/10/17/secure-your-containers-with-this-one-weird-trick">blog post</a> before beginning this lab.</p>
@@ -414,7 +400,7 @@ <h2 id="_capabilities">Capabilities</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>Notice that all 38 capability bits are set indicating this process has a full set of capabilities. In a later exercise, you&#8217;ll discover that a container
+<p>Notice that all 38 capability bits are set indicating this process has a full set of capabilities. In a later exercise, you’ll discover that a container
 running as <strong>root</strong> has a filtered set of capabilities by default but this can be changed at run time.</p>
 </div>
 <div class="paragraph">
@@ -431,7 +417,7 @@ <h2 id="_capabilities">Capabilities</h2>
 </div>
 </div>
 <div class="paragraph">
-<p><strong>NOTE: for those interested, capability '38' allows the following:</strong></p>
+<p><strong>NOTE: for those interested, capability &#39;38&#39; allows the following:</strong></p>
 </div>
 <div class="literalblock">
 <div class="content">
@@ -443,7 +429,7 @@ <h2 id="_capabilities">Capabilities</h2>
 </div>
 </div>
 <div class="paragraph">
-<p><strong>NOTE: for those interested, capability '39' allows the following:</strong></p>
+<p><strong>NOTE: for those interested, capability &#39;39&#39; allows the following:</strong></p>
 </div>
 <div class="literalblock">
 <div class="content">
@@ -463,7 +449,7 @@ <h2 id="_capabilities">Capabilities</h2>
 </div>
 </div>
 <div class="paragraph">
-<p>In comparison, '200' indicates the immutable capability (CAP_LINUX_IMMUTABLE):</p>
+<p>In comparison, &#39;200&#39; indicates the immutable capability (CAP_LINUX_IMMUTABLE):</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -494,7 +480,7 @@ <h3 id="_exploring_the_capabilities_of_containers">Exploring the capabilities of
 </div>
 </div>
 <div class="paragraph">
-<p>Next run a rootless container as <code>--user=0</code> and look at it’s capabilities. Note that it&#8217;s capabilities are filtered from that of a root process on the host.</p>
+<p>Next run a rootless container as <code>--user=0</code> and look at it’s capabilities. Note that it’s capabilities are filtered from that of a root process on the host.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -531,7 +517,7 @@ <h3 id="_examining_container_processes">Examining container processes</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Use <code>podman top</code> to examine the container&#8217;s capabilities.</p>
+<p>Use <code>podman top</code> to examine the container’s capabilities.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -578,7 +564,7 @@ <h3 id="_capabilities_challenge_1">Capabilities Challenge #1</h3>
 <div class="listingblock">
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo yum install bc -y
-echo 'obase=16;ibase=16;9+1' | bc</code></pre>
+echo &#39;obase=16;ibase=16;9+1&#39; | bc</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -599,7 +585,7 @@ <h3 id="_capabilities_challenge_2">Capabilities Challenge #2</h3>
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">podman run --rm -ti --user 0 --name temp registry.access.redhat.com/ubi8/ubi bash
 savethedate=$(date)
-date -s "$savethedate"</code></pre>
+date -s &#34;$savethedate&#34;</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -617,7 +603,7 @@ <h3 id="_capabilities_challenge_2">Capabilities Challenge #2</h3>
 <div class="sect2">
 <h3 id="_capabilities_challenge_3">Capabilities Challenge #3</h3>
 <div class="paragraph">
-<p>You have been given a container image to deploy (<code>quay.io/bkozdemb/hello</code>). The application needs to use the <code>chattr</code> utility but must not be allowed to <code>ping</code> any hosts. Use what you&#8217;ve learned about capabilities to properly deploy this application using <code>podman</code>.</p>
+<p>You have been given a container image to deploy (<code>quay.io/bkozdemb/hello</code>). The application needs to use the <code>chattr</code> utility but must not be allowed to <code>ping</code> any hosts. Use what you’ve learned about capabilities to properly deploy this application using <code>podman</code>.</p>
 </div>
 <div class="paragraph">
 <p>For example, <code>ping</code> succeeds but <code>chattr</code> fails. We want the opposite.</p>
@@ -674,7 +660,7 @@ <h3 id="_example_solutions_to_challenges">Example Solutions to Challenges</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">echo 'obase=16;ibase=16;FFFFFFFFFF-A80427FB' | bc</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">echo &#39;obase=16;ibase=16;FFFFFFFFFF-A80427FB&#39; | bc</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -702,7 +688,7 @@ <h3 id="_example_solutions_to_challenges">Example Solutions to Challenges</h3>
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo podman run --rm -ti --user 0 --name temp --cap-add=sys_time registry.access.redhat.com/ubi8/ubi bash
 savethedate=$(date)
-date -s "$savethedate"</code></pre>
+date -s &#34;$savethedate&#34;</code></pre>
 </div>
 </div>
 <div class="literalblock">
@@ -739,7 +725,7 @@ <h3 id="_example_solutions_to_challenges">Example Solutions to Challenges</h3>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>rm: cannot remove 'file': Operation not permitted</pre>
+<pre>rm: cannot remove &#39;file&#39;: Operation not permitted</pre>
 </div>
 </div>
 <div class="listingblock">
@@ -888,7 +874,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1148,7 +1134,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1260,7 +1246,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1270,7 +1256,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1357,7 +1343,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab05-selinux/index.html b/workshops/security_container_intro/lab05-selinux/index.html
index 50eddb104..128cc6ed4 100644
--- a/workshops/security_container_intro/lab05-selinux/index.html
+++ b/workshops/security_container_intro/lab05-selinux/index.html
@@ -317,20 +317,7 @@ <h1>Lab 5.0 - SELinux container integration</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_namespaced">!Namespaced</a>
-<ul class="sectlevel2">
-<li><a href="#_warmup_exercise">Warmup Exercise</a></li>
-<li><a href="#_bind_mounts_and_labeling">Bind Mounts and Labeling</a></li>
-<li><a href="#_private_mounts">Private Mounts</a></li>
-<li><a href="#_shared_mounts">Shared Mounts</a></li>
-<li><a href="#_read_only_containers">Read-Only Containers</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="paragraph">
 <p>In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations where the other security mechanisms fail. By default, <code>podman</code> processes are labeled with <code>container_runtime_t</code> and they are prevented from doing (almost) all SELinux operations.  But processes within containers do not know that they are running within a container.  SELinux-aware applications are going to attempt to do SELinux operations, especially if they are running as root. With RHEL, we write an SELinux policy that says that the container process running as <code>container_runtime_t</code> can only read/write files with the <code>container_file_t</code> label.</p>
 </div>
@@ -433,7 +420,7 @@ <h3 id="_bind_mounts_and_labeling">Bind Mounts and Labeling</h3>
 <p>As you learned above, bind mounts allow a container to mount a directory on the host for general application usage. This lab will help you understand how selinux behaves in different bind mounting scenarios.</p>
 </div>
 <div class="paragraph">
-<p>On the bastion, let&#8217;s create a directory named <code>/data</code>. Make note of the file permissions. Could a container read or write to this directory?</p>
+<p>On the bastion, let’s create a directory named <code>/data</code>. Make note of the file permissions. Could a container read or write to this directory?</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -558,7 +545,7 @@ <h3 id="_bind_mounts_and_labeling">Bind Mounts and Labeling</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Take sealerts&#8217;s suggestion of changing the label type of the <code>/data</code> directory to <code>container_file_t</code>:</p>
+<p>Take sealerts’s suggestion of changing the label type of the <code>/data</code> directory to <code>container_file_t</code>:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -648,7 +635,7 @@ <h3 id="_bind_mounts_and_labeling">Bind Mounts and Labeling</h3>
 <div class="sect2">
 <h3 id="_private_mounts">Private Mounts</h3>
 <div class="paragraph">
-<p>Now you&#8217;ll let podman create the SELinux labels. To change a label in the container context, you can add either of two suffixes <code>:z</code> or <code>:Z</code> to the volume mount. These suffixes tell podman to relabel file objects on the shared volumes. The <code>:Z</code> option tells podman to label the content with a private unshared label.</p>
+<p>Now you’ll let podman create the SELinux labels. To change a label in the container context, you can add either of two suffixes <code>:z</code> or <code>:Z</code> to the volume mount. These suffixes tell podman to relabel file objects on the shared volumes. The <code>:Z</code> option tells podman to label the content with a private unshared label.</p>
 </div>
 <div class="paragraph">
 <p>Repeat the scenario above but instead add the <code>:Z</code> option to bind mount the <code>/private</code> directory then try to create a file in the <code>/private</code> directory from the container’s namespace.</p>
@@ -780,7 +767,7 @@ <h3 id="_read_only_containers">Read-Only Containers</h3>
 <p>Imagine a scenario where an application gets compromised. The first thing the bad guy wants to do is to write an exploit into the container, so the next time the application starts up, it starts up with the exploit in place. If the container was read-only it would prevent leaving a backdoor in place and be forced to start the cycle from the beginning.</p>
 </div>
 <div class="paragraph">
-<p>Container engines added a read-only feature but it presents challenges since many applications need to write to temporary directories like <code>/run</code> or <code>/tmp</code> and when these directories are read-only, the apps fail. Red Hat’s approach leverages <code>tmpfs</code>. It&#8217;s a nice solution to this problem because it eliminates data exposure on the host. As a recommended practice, run all applications in production in this mode and only allow write operations to known directories.</p>
+<p>Container engines added a read-only feature but it presents challenges since many applications need to write to temporary directories like <code>/run</code> or <code>/tmp</code> and when these directories are read-only, the apps fail. Red Hat’s approach leverages <code>tmpfs</code>. It’s a nice solution to this problem because it eliminates data exposure on the host. As a recommended practice, run all applications in production in this mode and only allow write operations to known directories.</p>
 </div>
 <div class="paragraph">
 <p>To experiment with this feature, run a read-only container and specify a few writable file systems using the <code>--tmpfs</code> option:</p>
@@ -800,7 +787,7 @@ <h3 id="_read_only_containers">Read-Only Containers</h3>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>mkdir: cannot create directory '/newdir': Read-only file system</pre>
+<pre>mkdir: cannot create directory &#39;/newdir&#39;: Read-only file system</pre>
 </div>
 </div>
 <div class="listingblock">
@@ -811,7 +798,7 @@ <h3 id="_read_only_containers">Read-Only Containers</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>We&#8217;ve covered a lot of ground here on Dan&#8217;s favorite topic. You should feel good.</p>
+<p>We’ve covered a lot of ground here on Dan’s favorite topic. You should feel good.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -913,7 +900,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1173,7 +1160,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1285,7 +1272,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1295,7 +1282,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1382,7 +1369,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab06-inspecting/index.html b/workshops/security_container_intro/lab06-inspecting/index.html
index 23db24473..b80e84ca2 100644
--- a/workshops/security_container_intro/lab06-inspecting/index.html
+++ b/workshops/security_container_intro/lab06-inspecting/index.html
@@ -317,19 +317,7 @@ <h1>Lab 6.0 - Container inspection with Podman &amp; Skopeo</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_podman_inspect">Podman inspect</a>
-<ul class="sectlevel2">
-<li><a href="#_podman_diff">Podman diff</a></li>
-<li><a href="#_podman_live_mounts">Podman live mounts</a></li>
-<li><a href="#_working_with_skopeo">Working with Skopeo</a></li>
-<li><a href="#_inspecting_images">Inspecting images</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="paragraph">
 <p>Container images can easily be pulled from any public registry and run on a container host but is this good practice? Can you trust this image and what are its contents? A better practice would be to inspect the image before running it.</p>
 </div>
@@ -374,7 +362,7 @@ <h3 id="_podman_live_mounts">Podman live mounts</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Next, enter the container&#8217;s namespace, create some data then <code>exit</code> back to the host.</p>
+<p>Next, enter the container’s namespace, create some data then <code>exit</code> back to the host.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -418,7 +406,7 @@ <h3 id="_podman_live_mounts">Podman live mounts</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>How might you search this container&#8217;s file system for all programs that are owned by root and have the SETUID bit set?</p>
+<p>How might you search this container’s file system for all programs that are owned by root and have the SETUID bit set?</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -439,7 +427,7 @@ <h3 id="_podman_live_mounts">Podman live mounts</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Un-mount the container when you&#8217;re finished.</p>
+<p>Un-mount the container when you’re finished.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -484,11 +472,11 @@ <h3 id="_inspecting_images">Inspecting images</h3>
 <div class="literalblock">
 <div class="content">
 <pre>{
-    "Name": "registry.access.redhat.com/ubi8/ubi",
-    "Digest": "sha256:1f0e6e1f451ff020b3b44c1c4c34d85db5ffa0fc1bb0490d6a32957a7a06b67f"
+    &#34;Name&#34;: &#34;registry.access.redhat.com/ubi8/ubi&#34;,
+    &#34;Digest&#34;: &#34;sha256:1f0e6e1f451ff020b3b44c1c4c34d85db5ffa0fc1bb0490d6a32957a7a06b67f&#34;
 ,
-    "RepoTags": [
-        "8.1",
+    &#34;RepoTags&#34;: [
+        &#34;8.1&#34;,
         ...
         ...
         ...
@@ -614,7 +602,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -874,7 +862,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -986,7 +974,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -996,7 +984,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1083,7 +1071,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab07-signing/index.html b/workshops/security_container_intro/lab07-signing/index.html
index 080342939..05a19b3cd 100644
--- a/workshops/security_container_intro/lab07-signing/index.html
+++ b/workshops/security_container_intro/lab07-signing/index.html
@@ -317,20 +317,7 @@ <h1>Lab 7.0 - Container image signing</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_configuring_the_signature_claim_store">Configuring the signature claim store</a>
-<ul class="sectlevel2">
-<li><a href="#_generating_key_pairs">Generating key pairs</a></li>
-<li><a href="#_working_with_trust_policies">Working with trust policies</a></li>
-<li><a href="#_pulling_signed_images">Pulling signed images</a></li>
-<li><a href="#_create_a_trust_policy_for_red_hat_images">Create a trust policy for Red Hat images.</a></li>
-<li><a href="#_blocking_a_registry">Blocking a registry</a></li>
-</ul>
-</li>
-</ul>
-</div>
+    
 <div class="paragraph">
 <p>In this lab, you will use <code>podman</code> to sign container images and create trust policies to control access to registries.</p>
 </div>
@@ -342,7 +329,7 @@ <h1>Lab 7.0 - Container image signing</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_container_intro/images/encrypt.png" alt="Image Encryption">
+<img src="/workshops/security_container_intro/images/encrypt.png" alt="Image Encryption"/>
 </div>
 </div>
 <div class="paragraph">
@@ -350,7 +337,7 @@ <h1>Lab 7.0 - Container image signing</h1>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_container_intro/images/decrypt.png" alt="Image Decryption">
+<img src="/workshops/security_container_intro/images/decrypt.png" alt="Image Decryption"/>
 </div>
 </div>
 <div class="sect1">
@@ -406,7 +393,7 @@ <h2 id="_configuring_the_signature_claim_store">Configuring the signature claim
 <div class="sect2">
 <h3 id="_generating_key_pairs">Generating key pairs</h3>
 <div class="paragraph">
-<p>Generate the gpg key pair. You&#8217;ll be prompted to set a pass phrase. Set it to <code>1234567890</code> so you don&#8217;t forget. :)</p>
+<p>Generate the gpg key pair. You’ll be prompted to set a pass phrase. Set it to <code>1234567890</code> so you don’t forget. :)</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -414,7 +401,7 @@ <h3 id="_generating_key_pairs">Generating key pairs</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Now export the public key. You&#8217;ll need it later.</p>
+<p>Now export the public key. You’ll need it later.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -498,7 +485,7 @@ <h3 id="_generating_key_pairs">Generating key pairs</h3>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>{"repositories":["fedora/latest"]}</pre>
+<pre>{&#34;repositories&#34;:[&#34;fedora/latest&#34;]}</pre>
 </div>
 </div>
 </div>
@@ -563,7 +550,7 @@ <h3 id="_pulling_signed_images">Pulling signed images</h3>
 <div class="content">
 <pre>Trying to pull https://node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest...
   Running image docker://node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest:latest is rejected by policy.
-Error: error pulling image "node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest": unable to pull node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest: unable to pull image: Source image rejected: Running image docker://node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest:latest is rejected by policy.</pre>
+Error: error pulling image &#34;node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest&#34;: unable to pull node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest: unable to pull image: Source image rejected: Running image docker://node1-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest:latest is rejected by policy.</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -615,7 +602,7 @@ <h3 id="_pulling_signed_images">Pulling signed images</h3>
 <div class="sect2">
 <h3 id="_create_a_trust_policy_for_red_hat_images">Create a trust policy for Red Hat images.</h3>
 <div class="paragraph">
-<p>In this exercise, you will create a trust policy that allows only signed images to be pulled from Red Hat&#8217;s Container Catalog.</p>
+<p>In this exercise, you will create a trust policy that allows only signed images to be pulled from Red Hat’s Container Catalog.</p>
 </div>
 <div class="paragraph">
 <p>First, try a pull and it should fail because of the default policy.</p>
@@ -629,7 +616,7 @@ <h3 id="_create_a_trust_policy_for_red_hat_images">Create a trust policy for Red
 <div class="content">
 <pre>Trying to pull registry.access.redhat.com/ubi8/ubi...
   Running image docker://registry.access.redhat.com/ubi8/ubi:latest is rejected by policy.
-Error: error pulling image "registry.access.redhat.com/ubi8/ubi": unable to pull registry.access.redhat.com/ubi8/ubi: unable to pull image: Source image rejected: Running image docker://registry.access.redhat.com/ubi8/ubi:latest is rejected by policy.</pre>
+Error: error pulling image &#34;registry.access.redhat.com/ubi8/ubi&#34;: unable to pull registry.access.redhat.com/ubi8/ubi: unable to pull image: Source image rejected: Running image docker://registry.access.redhat.com/ubi8/ubi:latest is rejected by policy.</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -735,7 +722,7 @@ <h3 id="_blocking_a_registry">Blocking a registry</h3>
 </ul>
 </div>
 <div class="paragraph">
-<p>Take what you&#8217;ve learned and give each a try.</p>
+<p>Take what you’ve learned and give each a try.</p>
 </div>
 <div class="paragraph">
 <p>Now try to pull the image from <code>node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span></code>, it should fail.</p>
@@ -749,7 +736,7 @@ <h3 id="_blocking_a_registry">Blocking a registry</h3>
 <div class="content">
 <pre>Trying to pull https://node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest...
   Running image docker://node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest:latest is rejected by policy.
-Error: error pulling image "node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest": unable to pull node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest: unable to pull image: Source image rejected: Running image docker://node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest:latest is rejected by policy.</pre>
+Error: error pulling image &#34;node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest&#34;: unable to pull node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest: unable to pull image: Source image rejected: Running image docker://node2-<span class="userid">0</span>.<span class="prefix">example</span>.<span class="domain">redhatgov.io</span>:5000/fedora/latest:latest is rejected by policy.</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -852,7 +839,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1112,7 +1099,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1224,7 +1211,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1234,7 +1221,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1321,7 +1308,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab08-builds/index.html b/workshops/security_container_intro/lab08-builds/index.html
index 3f196f532..66bf3aa08 100644
--- a/workshops/security_container_intro/lab08-builds/index.html
+++ b/workshops/security_container_intro/lab08-builds/index.html
@@ -317,18 +317,12 @@ <h1>Lab 8.0 - Composing containers with Buildah</h1>
   </ul>
 </nav>
 
-    <div id="toc" class="toc">
-<div id="toctitle">Table of Contents</div>
-<ul class="sectlevel1">
-<li><a href="#_building_from_universal_base_images">Building from Universal Base Images</a></li>
-<li><a href="#_build_using_docker_bud">Build using Docker (BuD)</a></li>
-</ul>
-</div>
+    
 <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph">
 <p>This module will introduce <em>Buildah</em>, a command line tool for building <a href="https://https://www.opencontainers.org/">Open Container Initiative</a>
-compatible container images. <em>Buildah</em> is easy to incorporate into scripts and build pipelines, and best of all, it doesn&#8217;t require a running container daemon to build its image. You can read more about <em>Buildah</em> at the <a href="https://buildah.io">buildah.io</a> web site. Also, have a look at the <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#building-container-images-with-buildah_building-running-and-managing-containers">buildah</a> chapter in the RHEL 8 documentation.</p>
+compatible container images. <em>Buildah</em> is easy to incorporate into scripts and build pipelines, and best of all, it doesn’t require a running container daemon to build its image. You can read more about <em>Buildah</em> at the <a href="https://buildah.io">buildah.io</a> web site. Also, have a look at the <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#building-container-images-with-buildah_building-running-and-managing-containers">buildah</a> chapter in the RHEL 8 documentation.</p>
 </div>
 </div>
 </div>
@@ -349,10 +343,10 @@ <h2 id="_building_from_universal_base_images">Building from Universal Base Image
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">echo "The container is working." &gt; index.html
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">echo &#34;The container is working.&#34; &gt; index.html
 buildah copy myapp index.html /
-buildah config --cmd 'python3 -m http.server' myapp
-buildah config --author "me_at_myorg_dot_com @twitter-handle" --label name=myapp myapp
+buildah config --cmd &#39;python3 -m http.server&#39; myapp
+buildah config --author &#34;me_at_myorg_dot_com @twitter-handle&#34; --label name=myapp myapp
 buildah commit myapp myapp
 podman run -d --name=test -p8000:8000 localhost/myapp</code></pre>
 </div>
@@ -395,12 +389,12 @@ <h2 id="_build_using_docker_bud">Build using Docker (BuD)</h2>
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">cat &gt; Dockerfile &lt;&lt;EOF
 FROM registry.access.redhat.com/ubi8/ubi
-LABEL description="Minimal python web server" maintainer="yourname@mail.net"
+LABEL description=&#34;Minimal python web server&#34; maintainer=&#34;yourname@mail.net&#34;
 RUN dnf -y update; dnf -y clean all
 RUN dnf -y install python3 --setopt install_weak_deps=false; dnf -y clean all
-RUN echo "The python http.server module is running." &gt; /index.html
+RUN echo &#34;The python http.server module is running.&#34; &gt; /index.html
 EXPOSE 8000
-CMD [ "/usr/bin/python3",  "-m", "http.server" ]
+CMD [ &#34;/usr/bin/python3&#34;,  &#34;-m&#34;, &#34;http.server&#34; ]
 EOF</code></pre>
 </div>
 </div>
@@ -415,7 +409,7 @@ <h2 id="_build_using_docker_bud">Build using Docker (BuD)</h2>
 <div class="literalblock">
 <div class="content">
 <pre>STEP 1: FROM registry.access.redhat.com/ubi8/ubi
-STEP 2: LABEL description="Minimal python web server" maintainer="yourname@mail.net"
+STEP 2: LABEL description=&#34;Minimal python web server&#34; maintainer=&#34;yourname@mail.net&#34;
 ...
 ...
 ...
@@ -589,7 +583,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -849,7 +843,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -961,7 +955,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -971,7 +965,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1057,7 +1051,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_container_intro/lab99-conclusion/index.html b/workshops/security_container_intro/lab99-conclusion/index.html
index f121bbe5b..9f74245e1 100644
--- a/workshops/security_container_intro/lab99-conclusion/index.html
+++ b/workshops/security_container_intro/lab99-conclusion/index.html
@@ -422,7 +422,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -682,7 +682,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -794,7 +794,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -804,7 +804,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -884,7 +884,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.0/index.html b/workshops/security_containers/exercise1.0/index.html
index 8e61f460c..39ce20440 100644
--- a/workshops/security_containers/exercise1.0/index.html
+++ b/workshops/security_containers/exercise1.0/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.0 - Intro to Cockpit</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/cockpit.png" alt="cockpit">
+<img src="/workshops/security_containers/images/cockpit.png" alt="cockpit"/>
 </div>
 </div>
 </div>
@@ -438,7 +438,7 @@ <h3 id="_step_1_examine_the_system_display_navigate_using_the_left_side_menu">St
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/overview.png" alt="System">
+<img src="/workshops/security_containers/images/overview.png" alt="System"/>
 </div>
 </div>
 </div>
@@ -456,12 +456,12 @@ <h3 id="_step_2_examine_services_by_clicking_the_system_services_tab_at_the_top_
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/services.png" alt="Services">
+<img src="/workshops/security_containers/images/services.png" alt="Services"/>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_3_examine_the_containers_and_images_navigate_to_containers_using_the_left_side_menu">Step 3. Examine the Containers and images. Navigate to "Containers" using the left-side menu.</h3>
+<h3 id="_step_3_examine_the_containers_and_images_navigate_to_containers_using_the_left_side_menu">Step 3. Examine the Containers and images. Navigate to &#34;Containers&#34; using the left-side menu.</h3>
 <div class="paragraph">
 <p><strong>Containers:</strong> Lists all images available on the system, all running and
 non-running containers, combined CPU &amp; memory usage graphs, and a storage
@@ -475,7 +475,7 @@ <h3 id="_step_3_examine_the_containers_and_images_navigate_to_containers_using_t
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/containers1.png" alt="Containers">
+<img src="/workshops/security_containers/images/containers1.png" alt="Containers"/>
 </div>
 </div>
 </div>
@@ -483,7 +483,7 @@ <h3 id="_step_3_examine_the_containers_and_images_navigate_to_containers_using_t
 <h3 id="_step_4_search_for_download_fedora">Step 4. Search For &amp; Download Fedora</h3>
 <div class="paragraph">
 <p>Use the following commandline to search for and download Fedora.
-Type in "docker.io/fedora" in order to search the online Docker registry.</p>
+Type in &#34;docker.io/fedora&#34; in order to search the online Docker registry.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -492,12 +492,12 @@ <h3 id="_step_4_search_for_download_fedora">Step 4. Search For &amp; Download Fe
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/search.png" alt="Search for Fedora">
+<img src="/workshops/security_containers/images/search.png" alt="Search for Fedora"/>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_5_run_the_fedora_image_simply_by_clicking_run">Step 5. Run the Fedora image simply by clicking 'Run'.</h3>
+<h3 id="_step_5_run_the_fedora_image_simply_by_clicking_run">Step 5. Run the Fedora image simply by clicking &#39;Run&#39;.</h3>
 <div class="listingblock">
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">Click: Run</code></pre>
@@ -505,11 +505,11 @@ <h3 id="_step_5_run_the_fedora_image_simply_by_clicking_run">Step 5. Run the Fed
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/run.png" alt="Run the Fedora image">
+<img src="/workshops/security_containers/images/run.png" alt="Run the Fedora image"/>
 </div>
 </div>
 <div class="paragraph">
-<p>Then, add a command to run the image. ("Sleep" is a generic enough command.)</p>
+<p>Then, add a command to run the image. (&#34;Sleep&#34; is a generic enough command.)</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -518,7 +518,7 @@ <h3 id="_step_5_run_the_fedora_image_simply_by_clicking_run">Step 5. Run the Fed
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/run-image.png" alt="Run with options">
+<img src="/workshops/security_containers/images/run-image.png" alt="Run with options"/>
 </div>
 </div>
 </div>
@@ -527,37 +527,37 @@ <h3 id="_step_6_view_metadata">Step 6. View metadata</h3>
 <div class="paragraph">
 <p>Click on the newly created container to view all of the metadata about the
 container. Shows the state, the command executed, the container and image
-IDs, a timestamp, as well as the container&#8217;s own terminal.</p>
+IDs, a timestamp, as well as the container’s own terminal.</p>
 </div>
 <div class="paragraph">
 <p>Click on the newly created container [&gt;]</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/detail1.png" alt="Image Detail">
+<img src="/workshops/security_containers/images/detail1.png" alt="Image Detail"/>
 </div>
 </div>
 <div class="paragraph">
-<p>Expand the view and see all of the metadata about the container. Shows the state, the command executed, the container&#8217;s and image&#8217;s IDs, a timestamp, as well as the container&#8217;s own terminal:</p>
+<p>Expand the view and see all of the metadata about the container. Shows the state, the command executed, the container’s and image’s IDs, a timestamp, as well as the container’s own terminal:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/detail.png" alt="Image Detail">
+<img src="/workshops/security_containers/images/detail.png" alt="Image Detail"/>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_7_navigate_to_tools_via_the_left_side_menu_to_examine_subscriptions_accounts_diagnostics_and_terminal_features">Step 7. Navigate to 'Tools' via the left-side menu, to examine subscriptions, accounts, diagnostics, and terminal features.</h3>
+<h3 id="_step_7_navigate_to_tools_via_the_left_side_menu_to_examine_subscriptions_accounts_diagnostics_and_terminal_features">Step 7. Navigate to &#39;Tools&#39; via the left-side menu, to examine subscriptions, accounts, diagnostics, and terminal features.</h3>
 <div class="paragraph">
 <div class="title">Features and Capabilities</div>
-<p><strong>Tools:</strong> (Terminal)<br>
-<strong>Subscriptions:</strong> Displays what Red Hat products are installed and subscribed.<br>
+<p><strong>Tools:</strong> (Terminal)<br/>
+<strong>Subscriptions:</strong> Displays what Red Hat products are installed and subscribed.<br/>
 <strong>Accounts:</strong> Shows which administrative (root) and other users have accounts on
-the system.<br>
+the system.<br/>
 <strong>Diagnostic report:</strong> Collects system configuration and diagnostics information
-and prepares a report, in an XZ format.<br>
+and prepares a report, in an XZ format.<br/>
 <strong>Terminal:</strong> Opens a Terminal (command line) session to the Cockpit system.
-From there, you can run any commands available to the user you are logged in as.<br></p>
+From there, you can run any commands available to the user you are logged in as.<br/></p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -568,7 +568,7 @@ <h3 id="_step_7_navigate_to_tools_via_the_left_side_menu_to_examine_subscription
 <div class="sect2">
 <h3 id="_step_8_delete_the_container">Step 8. Delete the Container</h3>
 <div class="paragraph">
-<p>When you&#8217;ve completed examining Cockpit, stop and delete the container using the following command.</p>
+<p>When you’ve completed examining Cockpit, stop and delete the container using the following command.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -577,7 +577,7 @@ <h3 id="_step_8_delete_the_container">Step 8. Delete the Container</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/stop.png" alt="Stop">
+<img src="/workshops/security_containers/images/stop.png" alt="Stop"/>
 </div>
 </div>
 <div class="listingblock">
@@ -587,7 +587,7 @@ <h3 id="_step_8_delete_the_container">Step 8. Delete the Container</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/refresh.png" alt="Refresh">
+<img src="/workshops/security_containers/images/refresh.png" alt="Refresh"/>
 </div>
 </div>
 <div class="listingblock">
@@ -597,7 +597,7 @@ <h3 id="_step_8_delete_the_container">Step 8. Delete the Container</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/trash.png" alt="Trash">
+<img src="/workshops/security_containers/images/trash.png" alt="Trash"/>
 </div>
 </div>
 <div class="listingblock">
@@ -607,7 +607,7 @@ <h3 id="_step_8_delete_the_container">Step 8. Delete the Container</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/delete.png" alt="Delete">
+<img src="/workshops/security_containers/images/delete.png" alt="Delete"/>
 </div>
 </div>
 <div class="paragraph">
@@ -710,7 +710,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -970,7 +970,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1082,7 +1082,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1092,7 +1092,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1179,7 +1179,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.1/index.html b/workshops/security_containers/exercise1.1/index.html
index f23a90901..6af839576 100644
--- a/workshops/security_containers/exercise1.1/index.html
+++ b/workshops/security_containers/exercise1.1/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/file.png" alt="file">
+<img src="/workshops/security_containers/images/file.png" alt="file"/>
 </div>
 </div>
 </div>
@@ -336,7 +336,7 @@ <h2 id="_exercise_1_1_reproducible_and_trustworthy_dockerfiles">Exercise 1.1 - R
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve gotten a sense of how Cockpit works, we are going to start
+<p>Now that you’ve gotten a sense of how Cockpit works, we are going to start
 digging in at the command line on Container security. You can use either the
 Terminal in Cockpit from your browser, a SSH terminal or Terminal client like
 PuTTy. The choice is yours.</p>
@@ -380,18 +380,18 @@ <h3 id="_step_2_securely_downloading_software_in_dockerfiles">Step 2. Securely D
                         114F43EE0176B71C7BC219DD50A3051F888C628D
 ENV NODE_VERSION 0.10.38
 ENV NPM_VERSION 2.10.0
-RUN curl -SLO "http://nodejs.org/dist/v$NODE_VERSION/node-v\
-$NODE_VERSION-linux-x64.tar.gz" \ <i class="conum" data-value="2"></i><b>(2)</b>
-&amp;&amp; curl -SLO "http://nodejs.org/dist/v$NODE_VERSION/\
-SHASUMS256.txt.asc" \ <i class="conum" data-value="3"></i><b>(3)</b>
+RUN curl -SLO &#34;http://nodejs.org/dist/v$NODE_VERSION/node-v\
+$NODE_VERSION-linux-x64.tar.gz&#34; \ <i class="conum" data-value="2"></i><b>(2)</b>
+&amp;&amp; curl -SLO &#34;http://nodejs.org/dist/v$NODE_VERSION/\
+SHASUMS256.txt.asc&#34; \ <i class="conum" data-value="3"></i><b>(3)</b>
 &amp;&amp; gpg --verify SHASUMS256.txt.asc \ <i class="conum" data-value="4"></i><b>(4)</b>
-&amp;&amp; grep " node-v$NODE_VERSION-linux-x64.tar.gz\$" \
+&amp;&amp; grep &#34; node-v$NODE_VERSION-linux-x64.tar.gz\$&#34; \
             SHASUMS256.txt.asc | sha256sum -c - <i class="conum" data-value="5"></i><b>(5)</b></code></pre>
 </div>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Gets the GNU Privacy Guard (GPG) keys used to sign the Node.js download.
 Here, we do have to trust that these are the correct keys. Downloads the
@@ -415,7 +415,7 @@ <h3 id="_step_2_securely_downloading_software_in_dockerfiles">Step 2. Securely D
 <td><i class="conum" data-value="5"></i><b>5</b></td>
 <td>Tests that the checksum matches the tarball by using the sha256sum tool.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -465,7 +465,7 @@ <h2 id="_step_3_creating_an_original_checksum">Step 3. Creating an original chec
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -474,7 +474,7 @@ <h2 id="_step_3_creating_an_original_checksum">Step 3. Creating an original chec
 paste <code>control + v</code>, then escape and write the file <code>esc</code>, <code>:wq</code>.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="title">Dockerfile Redis with verified software download</div>
@@ -485,7 +485,7 @@ <h2 id="_step_3_creating_an_original_checksum">Step 3. Creating an original chec
 RUN cd /tmp &amp;&amp; \
     curl -sSL -o redis.tar.gz \
     http://download.redis.io/releases/redis-5.0.1.tar.gz &amp;&amp; \
-    echo "32a3accc9ac63896eeb7a3bf27ab667b095ba30a *redis.tar.gz" | sha1sum -c -
+    echo &#34;32a3accc9ac63896eeb7a3bf27ab667b095ba30a *redis.tar.gz&#34; | sha1sum -c -
 
 RUN cd /tmp &amp;&amp; \
     tar xvzf redis.tar.gz &amp;&amp; \
@@ -497,19 +497,19 @@ <h2 id="_step_3_creating_an_original_checksum">Step 3. Creating an original chec
     mkdir -p /etc/redis &amp;&amp; \
     cp -f *.conf /etc/redis &amp;&amp; \
     rm -rf /tmp/redis-5.0.1* &amp;&amp; \
-    sed -i 's/^\(bind .*\)$/# \1/' /etc/redis/redis.conf &amp;&amp; \
-    sed -i 's/^\(daemonize .*\)$/# \1/' /etc/redis/redis.conf &amp;&amp; \
-    sed -i 's/^\(dir .*\)$/# \1\ndir \/data/' /etc/redis/redis.conf &amp;&amp; \
-    sed -i 's/^\(logfile .*\)$/# \1/' /etc/redis/redis.conf
+    sed -i &#39;s/^\(bind .*\)$/# \1/&#39; /etc/redis/redis.conf &amp;&amp; \
+    sed -i &#39;s/^\(daemonize .*\)$/# \1/&#39; /etc/redis/redis.conf &amp;&amp; \
+    sed -i &#39;s/^\(dir .*\)$/# \1\ndir \/data/&#39; /etc/redis/redis.conf &amp;&amp; \
+    sed -i &#39;s/^\(logfile .*\)$/# \1/&#39; /etc/redis/redis.conf
 
 # Define mountable directories.
-VOLUME ["/data"]
+VOLUME [&#34;/data&#34;]
 
 # Define working directory.
 WORKDIR /data
 
 # Define default command.
-CMD ["redis-server", "/etc/redis/redis.conf"]
+CMD [&#34;redis-server&#34;, &#34;/etc/redis/redis.conf&#34;]
 
 # Expose ports.
 EXPOSE 6379</code></pre>
@@ -565,14 +565,14 @@ <h2 id="_step_5_run_the_container">Step 5. Run the container</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseccec3b3573a222f5c9def6a9e7ea9d85" class="collapsed">
+      <a data-toggle="collapse" href="#collapsefa4bd49e2de4d901afa54df4c8a97656" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapseccec3b3573a222f5c9def6a9e7ea9d85" class="panel-collapse collapse ">
+  <div id="collapsefa4bd49e2de4d901afa54df4c8a97656" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
@@ -587,30 +587,30 @@ <h4 class="panel-title">
 11:C 10 Nov 2018 16:53:04.041 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/re
 dis.conf
                 _._
-           _.-``__ ''-._
-      _.-``    `.  `_.  ''-._           Redis 5.0.1 (00000000/0) 64 bit
-  .-`` .-```.  ```\/    _.,_ ''-._
- (    '      ,       .-`  | `,    )     Running in standalone mode
- |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
- |    `-._   `._    /     _.-'    |     PID: 11
-  `-._    `-._  `-./  _.-'    _.-'
- |`-._`-._    `-.__.-'    _.-'_.-'|
- |    `-._`-._        _.-'_.-'    |           http://redis.io
-  `-._    `-._`-.__.-'_.-'    _.-'
- |`-._`-._    `-.__.-'    _.-'_.-'|
- |    `-._`-._        _.-'_.-'    |
-  `-._    `-._`-.__.-'_.-'    _.-'
-      `-._    `-.__.-'    _.-'
-          `-._        _.-'
-              `-.__.-'
+           _.-``__ &#39;&#39;-._
+      _.-``    `.  `_.  &#39;&#39;-._           Redis 5.0.1 (00000000/0) 64 bit
+  .-`` .-```.  ```\/    _.,_ &#39;&#39;-._
+ (    &#39;      ,       .-`  | `,    )     Running in standalone mode
+ |`-._`-...-` __...-.``-._|&#39;` _.-&#39;|     Port: 6379
+ |    `-._   `._    /     _.-&#39;    |     PID: 11
+  `-._    `-._  `-./  _.-&#39;    _.-&#39;
+ |`-._`-._    `-.__.-&#39;    _.-&#39;_.-&#39;|
+ |    `-._`-._        _.-&#39;_.-&#39;    |           http://redis.io
+  `-._    `-._`-.__.-&#39;_.-&#39;    _.-&#39;
+ |`-._`-._    `-.__.-&#39;    _.-&#39;_.-&#39;|
+ |    `-._`-._        _.-&#39;_.-&#39;    |
+  `-._    `-._`-.__.-&#39;_.-&#39;    _.-&#39;
+      `-._    `-.__.-&#39;    _.-&#39;
+          `-._        _.-&#39;
+              `-.__.-&#39;
 
 11:M 10 Nov 2018 16:53:04.043 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value o
 f 128.
 11:M 10 Nov 2018 16:53:04.043 # Server initialized
-11:M 10 Nov 2018 16:53:04.043 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overc
-ommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
+11:M 10 Nov 2018 16:53:04.043 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add &#39;vm.overc
+ommit_memory = 1&#39; to /etc/sysctl.conf and then reboot or run the command &#39;sysctl vm.overcommit_memory=1&#39; for this to take effect.
 11:M 10 Nov 2018 16:53:04.043 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage iss
-ues with Redis. To fix this issue run the command 'echo never &gt; /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in o
+ues with Redis. To fix this issue run the command &#39;echo never &gt; /sys/kernel/mm/transparent_hugepage/enabled&#39; as root, and add it to your /etc/rc.local in o
 rder to retain the setting after a reboot. Redis must be restarted after THP is disabled.
 11:M 10 Nov 2018 16:53:04.043 * Ready to accept connections</code></pre>
 </div>
@@ -736,7 +736,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -996,7 +996,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1108,7 +1108,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1118,7 +1118,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1204,7 +1204,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.2/index.html b/workshops/security_containers/exercise1.2/index.html
index 57dd2fc68..456ea038b 100644
--- a/workshops/security_containers/exercise1.2/index.html
+++ b/workshops/security_containers/exercise1.2/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.2 - Docker `USER`</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/term.png" alt="term">
+<img src="/workshops/security_containers/images/term.png" alt="term"/>
 </div>
 </div>
 </div>
@@ -336,7 +336,7 @@ <h2 id="_exercise_1_2_docker_user">Exercise 1.2 - Docker <code>USER</code></h2>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Now that you&#8217;ve gotten a sense of software provenance in Dockerfiles lets take
+<p>Now that you’ve gotten a sense of software provenance in Dockerfiles lets take
 a look at the <code>USER</code> in <code>Dockerfiles</code>.</p>
 </div>
 <div class="paragraph">
@@ -366,7 +366,7 @@ <h3 id="_step_1_reusing_an_image_with_a_non_root_user">Step 1. Reusing an Image
 <pre class="highlight"><code class="language-bash" data-lang="bash">FROM fedora:29
 
 RUN groupadd -r swuser -g 433 &amp;&amp; \
-    useradd -u 431 -r -g swuser -s /sbin/nologin -c "Docker image user" swuser
+    useradd -u 431 -r -g swuser -s /sbin/nologin -c &#34;Docker image user&#34; swuser
 
 USER root
 
@@ -405,7 +405,7 @@ <h3 id="_step_2_build_the_dockerfile">Step 2. Build the <code>Dockerfile</code><
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -414,7 +414,7 @@ <h3 id="_step_2_build_the_dockerfile">Step 2. Build the <code>Dockerfile</code><
 <code>control + v</code>, then escape and write the file <code>esc</code>, <code>:wq</code>.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="title">Dockerfile</div>
@@ -422,7 +422,7 @@ <h3 id="_step_2_build_the_dockerfile">Step 2. Build the <code>Dockerfile</code><
 <pre class="highlight"><code class="language-bash" data-lang="bash">FROM fedora:29
 
 RUN groupadd -r swuser -g 433 &amp;&amp; \
-    useradd -u 431 -r -g swuser -s /sbin/nologin -c "Docker image user" swuser
+    useradd -u 431 -r -g swuser -s /sbin/nologin -c &#34;Docker image user&#34; swuser
 
 USER root
 
@@ -461,7 +461,7 @@ <h3 id="_step_4_run_and_test_the_image">Step 4. Run and Test the image</h3>
 <div class="ulist">
 <ul>
 <li>
-<p><a href="http://www.projectatomic.io/blog/2015/08/why-we-dont-let-non-root-users-run-docker-in-centos-fedora-or-rhel/">Why we don&#8217;t let non-root users run Docker in CentOS, Fedora, or RHEL</a></p>
+<p><a href="http://www.projectatomic.io/blog/2015/08/why-we-dont-let-non-root-users-run-docker-in-centos-fedora-or-rhel/">Why we don’t let non-root users run Docker in CentOS, Fedora, or RHEL</a></p>
 </li>
 <li>
 <p><a href="http://www.projectatomic.io/docs/docker-image-author-guidance/">Guidance for Docker Image Authors</a>
@@ -564,7 +564,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -824,7 +824,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -936,7 +936,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -946,7 +946,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1035,7 +1035,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.3/index.html b/workshops/security_containers/exercise1.3/index.html
index 8d18db19c..f4ebd32fa 100644
--- a/workshops/security_containers/exercise1.3/index.html
+++ b/workshops/security_containers/exercise1.3/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.3 - Remove setuid/setgid Binaries</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/code.png" alt="code">
+<img src="/workshops/security_containers/images/code.png" alt="code"/>
 </div>
 </div>
 </div>
@@ -390,7 +390,7 @@ <h3 id="_step_1_find_a_list_of_binaries">Step 1. Find a list of binaries</h3>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_2_defang_the_binaries">Step 2. "Defang" the binaries</h3>
+<h3 id="_step_2_defang_the_binaries">Step 2. &#34;Defang&#34; the binaries</h3>
 <div class="paragraph">
 <p>You can then “defang” the binaries with <code>chmod a-s</code> to remove the suid bit.
 For example, you can create a defanged Debian image with the following Dockerfile:</p>
@@ -470,7 +470,7 @@ <h3 id="_step_6_run_the_command_on_your_rhel_host">Step 6. Run the command on yo
 </div>
 </div>
 <div class="paragraph">
-<p>It&#8217;s more likely that your Dockerfile will rely on a setuid/setgid binary than
+<p>It’s more likely that your Dockerfile will rely on a setuid/setgid binary than
 your application. Therefore, you can always perform this step near the end,
 after any such calls and before changing the user (removing setuid binaries is
 pointless if the application runs with root privileges).</p>
@@ -576,7 +576,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -836,7 +836,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -948,7 +948,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -958,7 +958,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1045,7 +1045,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.4/index.html b/workshops/security_containers/exercise1.4/index.html
index 436d4f6ba..dc65cd84b 100644
--- a/workshops/security_containers/exercise1.4/index.html
+++ b/workshops/security_containers/exercise1.4/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.4 - CGroups</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/cgroups.png" alt="cgroups">
+<img src="/workshops/security_containers/images/cgroups.png" alt="cgroups"/>
 </div>
 </div>
 </div>
@@ -511,7 +511,7 @@ <h3 id="_step_1_lets_run_a_container_with_512_limit_of_cpu_shares">Step 1. Lets
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_2_determine_the_containers_share_usage">Step 2. Determine the container&#8217;s share usage</h3>
+<h3 id="_step_2_determine_the_containers_share_usage">Step 2. Determine the container’s share usage</h3>
 <div class="paragraph">
 <p>Now lets see how many shares this container is using.</p>
 </div>
@@ -554,7 +554,7 @@ <h4 class="panel-title">
 
 </div>
 <div class="paragraph">
-<p>CPU shares are defined as a value between 0-1024, however when idle the container will use all available shares until another process needs to use the existing shares. Let&#8217;s run a example where another container needs to run and we divide up the shares equally.</p>
+<p>CPU shares are defined as a value between 0-1024, however when idle the container will use all available shares until another process needs to use the existing shares. Let’s run a example where another container needs to run and we divide up the shares equally.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -739,7 +739,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -999,7 +999,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1111,7 +1111,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1121,7 +1121,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1208,7 +1208,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.5/index.html b/workshops/security_containers/exercise1.5/index.html
index dcf855913..cf09ccd3e 100644
--- a/workshops/security_containers/exercise1.5/index.html
+++ b/workshops/security_containers/exercise1.5/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.5 - Namespaces</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/namespaces.png" alt="namespaces">
+<img src="/workshops/security_containers/images/namespaces.png" alt="namespaces"/>
 </div>
 </div>
 </div>
@@ -342,7 +342,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>PID namespaces enable processes in different containers to have the same PID (process identifier). This means each container can have its own init (PID1) process that manages various system initialization tasks, as well as the container life cycle.</p>
 </div>
 <div class="paragraph">
-<p>Also, each container has its unique /proc directory. Note that from within the container, you can only monitor those processes running inside this container. In other words, the container is only aware of its native processes and can not "see" the processes running in different parts of the system. It is the host operating system that is aware of processes running inside of the container, but assigns them different PID numbers.</p>
+<p>Also, each container has its unique /proc directory. Note that from within the container, you can only monitor those processes running inside this container. In other words, the container is only aware of its native processes and can not &#34;see&#34; the processes running in different parts of the system. It is the host operating system that is aware of processes running inside of the container, but assigns them different PID numbers.</p>
 </div>
 </div>
 </div>
@@ -350,7 +350,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <h2 id="_section_1_launching_a_container">Section 1: Launching a container</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Launch a container in it&#8217;s own namespace and see what process it can see from inside the container.</p>
+<p>Launch a container in it’s own namespace and see what process it can see from inside the container.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -365,14 +365,14 @@ <h2 id="_section_1_launching_a_container">Section 1: Launching a container</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse10b5f71423bcb12f7e7c6a5f9f01139f" class="collapsed">
+      <a data-toggle="collapse" href="#collapsed977a41fede90d22a6ab39f5bc940168" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapse10b5f71423bcb12f7e7c6a5f9f01139f" class="panel-collapse collapse ">
+  <div id="collapsed977a41fede90d22a6ab39f5bc940168" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -384,11 +384,11 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>The only process we can see is just our last command <code>ps aux</code>.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 
     </div>
@@ -511,7 +511,7 @@ <h2 id="_section_3_network_namespace">Section 3: Network Namespace</h2>
 <p>Network namespaces provide isolation of network controllers, system resources associated with networking, firewall and routing tables. This allows container to use separate virtual network stack, loopback device and process space. You can add virtual or real devices to the container, assign them their own IP Addresses and even full iptables rules.</p>
 </div>
 <div class="paragraph">
-<p>Network namespaces allow containers to be created with unique IP address and interfaces. Let&#8217;s run a container and examine the default container network interface.</p>
+<p>Network namespaces allow containers to be created with unique IP address and interfaces. Let’s run a container and examine the default container network interface.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -526,14 +526,14 @@ <h2 id="_section_3_network_namespace">Section 3: Network Namespace</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsef006917b314f462473e0c75886e27d9d" class="collapsed">
+      <a data-toggle="collapse" href="#collapsece811346c8d39dc916bfb4241c52dc6a" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapsef006917b314f462473e0c75886e27d9d" class="panel-collapse collapse ">
+  <div id="collapsece811346c8d39dc916bfb4241c52dc6a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -555,7 +555,7 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Loopback</td>
 </tr>
@@ -563,7 +563,7 @@ <h4 class="panel-title">
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>eth0</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 
     </div>
@@ -575,7 +575,7 @@ <h4 class="panel-title">
 
 </div>
 <div class="paragraph">
-<p>By default a container&#8217;s network is isolated with it&#8217;s own IP and interface. By changing the namespace to host by using the <code>--net</code> flag, the process will have access to the host machines network interface.</p>
+<p>By default a container’s network is isolated with it’s own IP and interface. By changing the namespace to host by using the <code>--net</code> flag, the process will have access to the host machines network interface.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -590,14 +590,14 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseca63f838c68f061164106554b1be2e35" class="collapsed">
+      <a data-toggle="collapse" href="#collapse2b9138188cf5a73e07ec40ea41b4d7e4" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapseca63f838c68f061164106554b1be2e35" class="panel-collapse collapse ">
+  <div id="collapse2b9138188cf5a73e07ec40ea41b4d7e4" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -625,7 +625,7 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Loopback</td>
 </tr>
@@ -637,7 +637,7 @@ <h4 class="panel-title">
 <td><i class="conum" data-value="3"></i><b>3</b></td>
 <td>cni-podman0</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p><strong>--net=container:NAME_or_ID</strong>: This puts the container’s processes inside of the network stack that has already been created inside of another container. The new container’s processes will be confined to their own filesystem and process list and resource limits, but will share the same IP address and port numbers as the first container, and processes on the two containers will be able to connect to each other over the loopback interface.</p>
@@ -673,7 +673,7 @@ <h2 id="_section_4_sharing_network_namespaces">Section 4: Sharing Network Namesp
 <p>Containers have a default security model that enforces isolation at the kernel level for process separation as well as network separation between containers. Sometimes you may need to debug a application or container and need to attach or share a containers namespace. Sharing namespaces should only be done in certain situations that require it, but for development it may be appropriate for debugging.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s examine how we can share the networking namespace between containers. We will launch a nginx container that will bind to port 80 inside it&#8217;s container network interface.</p>
+<p>Let’s examine how we can share the networking namespace between containers. We will launch a nginx container that will bind to port 80 inside it’s container network interface.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -724,7 +724,7 @@ <h4 class="panel-title">
 
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s use the <code>--net=container:</code> flag to attach to the <code>http</code> containers network interface and try the curl command again.</p>
+<p>Now let’s use the <code>--net=container:</code> flag to attach to the <code>http</code> containers network interface and try the curl command again.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -739,14 +739,14 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse891c31456330882e723f940188056a50" class="collapsed">
+      <a data-toggle="collapse" href="#collapse23a1be0e0f30ab17fcb7441420fc3b8c" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapse891c31456330882e723f940188056a50" class="panel-collapse collapse ">
+  <div id="collapse23a1be0e0f30ab17fcb7441420fc3b8c" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -770,9 +770,9 @@ <h4 class="panel-title">
 configuration is required.&lt;/p&gt;
 
 &lt;p&gt;For online documentation and support please refer to
-&lt;a href="http://nginx.org/"&gt;nginx.org&lt;/a&gt;.&lt;br/&gt;
+&lt;a href=&#34;http://nginx.org/&#34;&gt;nginx.org&lt;/a&gt;.&lt;br/&gt;
 Commercial support is available at
-&lt;a href="http://nginx.com/"&gt;nginx.com&lt;/a&gt;.&lt;/p&gt;
+&lt;a href=&#34;http://nginx.com/&#34;&gt;nginx.com&lt;/a&gt;.&lt;/p&gt;
 
 &lt;p&gt;&lt;em&gt;Thank you for using nginx.&lt;/em&gt;&lt;/p&gt;
 &lt;/body&gt;
@@ -781,11 +781,11 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Welcome to nginx! This is the default Nginx message and shows that we were able to share a namespace to connect to this container.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 
     </div>
@@ -812,14 +812,14 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsed59d2054ec92cd87cbc1ca3ffe5de118" class="collapsed">
+      <a data-toggle="collapse" href="#collapse5ed77f2e27826985e2c3cdb7f07e70e2" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapsed59d2054ec92cd87cbc1ca3ffe5de118" class="panel-collapse collapse ">
+  <div id="collapse5ed77f2e27826985e2c3cdb7f07e70e2" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -832,7 +832,7 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Nginx master process</td>
 </tr>
@@ -840,7 +840,7 @@ <h4 class="panel-title">
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>Nginx worker process</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 
     </div>
@@ -952,7 +952,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1212,7 +1212,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1324,7 +1324,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1334,7 +1334,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1420,7 +1420,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.6/index.html b/workshops/security_containers/exercise1.6/index.html
index 5cecd35a9..99d2f297b 100644
--- a/workshops/security_containers/exercise1.6/index.html
+++ b/workshops/security_containers/exercise1.6/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.6 - Read Only Containers</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/readonly.png" alt="readonly">
+<img src="/workshops/security_containers/images/readonly.png" alt="readonly"/>
 </div>
 </div>
 </div>
@@ -336,7 +336,7 @@ <h2 id="_exercise_1_6_read_only_containers">Exercise 1.6 - Read Only Containers<
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Let&#8217;s move on to "Read Only" Containers. This exercise will examine read-only containers and how to manage them.</p>
+<p>Let’s move on to &#34;Read Only&#34; Containers. This exercise will examine read-only containers and how to manage them.</p>
 </div>
 <div class="paragraph">
 <p><strong>Overview</strong></p>
@@ -363,7 +363,7 @@ <h2 id="_exercise_description">Exercise Description</h2>
 but stored in volatile memory instead of a persistent storage device.</em></p>
 </div>
 <div class="paragraph">
-<p>It&#8217;s a nice solution to this problem because it eliminates data exposure on the
+<p>It’s a nice solution to this problem because it eliminates data exposure on the
 host.</p>
 </div>
 <div class="paragraph">
@@ -512,7 +512,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -772,7 +772,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -884,7 +884,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -894,7 +894,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -981,7 +981,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.7/index.html b/workshops/security_containers/exercise1.7/index.html
index 99896cbd0..83ff821d1 100644
--- a/workshops/security_containers/exercise1.7/index.html
+++ b/workshops/security_containers/exercise1.7/index.html
@@ -380,27 +380,27 @@ <h3 id="_step_2_copy_the_1_chmod_json_text_below_and_paste_it_into_the_terminal_
 <div class="listingblock">
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">{
-    "defaultAction": "SCMP_ACT_ALLOW",
-    "architectures": [
-        "SCMP_ARCH_X86_64",
-        "SCMP_ARCH_X86",
-        "SCMP_ARCH_X32"
+    &#34;defaultAction&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+    &#34;architectures&#34;: [
+        &#34;SCMP_ARCH_X86_64&#34;,
+        &#34;SCMP_ARCH_X86&#34;,
+        &#34;SCMP_ARCH_X32&#34;
     ],
-    "syscalls": [
+    &#34;syscalls&#34;: [
         {
-            "name": "chmod",
-            "action": "SCMP_ACT_ERRNO",
-            "args": []
+            &#34;name&#34;: &#34;chmod&#34;,
+            &#34;action&#34;: &#34;SCMP_ACT_ERRNO&#34;,
+            &#34;args&#34;: []
         },
         {
-            "name": "chown",
-            "action": "SCMP_ACT_ERRNO",
-            "args": []
+            &#34;name&#34;: &#34;chown&#34;,
+            &#34;action&#34;: &#34;SCMP_ACT_ERRNO&#34;,
+            &#34;args&#34;: []
         },
         {
-            "name": "chown32",
-            "action": "SCMP_ACT_ERRNO",
-            "args": []
+            &#34;name&#34;: &#34;chown32&#34;,
+            &#34;action&#34;: &#34;SCMP_ACT_ERRNO&#34;,
+            &#34;args&#34;: []
         }
     ]
 }</code></pre>
@@ -411,15 +411,15 @@ <h3 id="_step_2_copy_the_1_chmod_json_text_below_and_paste_it_into_the_terminal_
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">"syscalls": [
+<pre class="highlight"><code class="language-bash" data-lang="bash">&#34;syscalls&#34;: [
         {
-            "name": "chmod",                <i class="conum" data-value="1"></i><b>(1)</b>
-            "action": "SCMP_ACT_ERRNO",     <i class="conum" data-value="2"></i><b>(2)</b></code></pre>
+            &#34;name&#34;: &#34;chmod&#34;,                <i class="conum" data-value="1"></i><b>(1)</b>
+            &#34;action&#34;: &#34;SCMP_ACT_ERRNO&#34;,     <i class="conum" data-value="2"></i><b>(2)</b></code></pre>
 </div>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td><strong>chmod</strong>:  is the command and system call which may change the access permissions to file system objects (files and directories). It may also alter special mode flags. The request is filtered by the umask. The name is an abbreviation of change mode.</td>
 </tr>
@@ -427,7 +427,7 @@ <h3 id="_step_2_copy_the_1_chmod_json_text_below_and_paste_it_into_the_terminal_
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td><strong>SCMP_ACT_ERRNO</strong>: Basically this blocks the chmod syscall. Man page: The thread will receive a return value of errno when it calls a syscall that matches the filter rule.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -493,7 +493,7 @@ <h2 id="_section_2_syscall_identification">Section 2: Syscall Identification</h2
 <div class="sect2">
 <h3 id="_step_1_run_fedora">Step 1. Run Fedora</h3>
 <div class="paragraph">
-<p>Let&#8217;s run a instance of Fedora and use the same <code>1_chmod.json</code> profile to try and limit the <code>chmod</code> command inside the container.</p>
+<p>Let’s run a instance of Fedora and use the same <code>1_chmod.json</code> profile to try and limit the <code>chmod</code> command inside the container.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -527,20 +527,20 @@ <h3 id="_step_2_add_the_strace_program_to_trace_chmod">Step 2. Add the strace pr
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseeb2619956e9acdb78a222bead5c9100f" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec6991928573d6dcc9e57b840af85c780" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapseeb2619956e9acdb78a222bead5c9100f" class="panel-collapse collapse ">
+  <div id="collapsec6991928573d6dcc9e57b840af85c780" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">stat("/etc/hosts", {st_mode=S_IFREG|0644, st_size=174, ...}) = 0
-fchmodat(AT_FDCWD, "/etc/hosts", 0400)  = 0
+<pre class="highlight"><code class="language-bash" data-lang="bash">stat(&#34;/etc/hosts&#34;, {st_mode=S_IFREG|0644, st_size=174, ...}) = 0
+fchmodat(AT_FDCWD, &#34;/etc/hosts&#34;, 0400)  = 0
 +++ exited with 0 +++</code></pre>
 </div>
 </div>
@@ -567,14 +567,14 @@ <h3 id="_step_3_create_a_seccomp_profile_using_new_mappings">Step 3. Create a se
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse8287504d40b392995412a9340f50f868" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4a46d62432b37685c7d294424d26c655" class="collapsed">
       
         Seccomp Profile
       </a>
     </h4>
   </div>
   
-  <div id="collapse8287504d40b392995412a9340f50f868" class="panel-collapse collapse ">
+  <div id="collapse4a46d62432b37685c7d294424d26c655" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
@@ -584,22 +584,22 @@ <h4 class="panel-title">
 <div class="title">2_chmod_fedora.json</div>
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">{
-    "defaultAction": "SCMP_ACT_ALLOW",
-    "architectures": [
-        "SCMP_ARCH_X86_64",
-        "SCMP_ARCH_X86",
-        "SCMP_ARCH_X32"
+    &#34;defaultAction&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+    &#34;architectures&#34;: [
+        &#34;SCMP_ARCH_X86_64&#34;,
+        &#34;SCMP_ARCH_X86&#34;,
+        &#34;SCMP_ARCH_X32&#34;
     ],
-    "syscalls": [
+    &#34;syscalls&#34;: [
         {
-            "name": "fchmodat",
-            "action": "SCMP_ACT_ERRNO",
-            "args": []
+            &#34;name&#34;: &#34;fchmodat&#34;,
+            &#34;action&#34;: &#34;SCMP_ACT_ERRNO&#34;,
+            &#34;args&#34;: []
         },
         {
-            "name": "fchownat",
-            "action": "SCMP_ACT_ERRNO",
-            "args": []
+            &#34;name&#34;: &#34;fchownat&#34;,
+            &#34;action&#34;: &#34;SCMP_ACT_ERRNO&#34;,
+            &#34;args&#34;: []
         }
     ]
 }</code></pre>
@@ -624,10 +624,10 @@ <h4 class="panel-title">
 <div class="sect2">
 <h3 id="_step_4_create_a_seccomp_profile_with_syscall_mapping">Step 4. Create a seccomp profile with syscall mapping</h3>
 <div class="paragraph">
-<p>We have now found the correct syscall to add to our seccomp profile. Let&#8217;s create a seccomp profile with our new syscall mapping. Now we can create a seccomp profile called <code>2_chmod_fedora.json</code> using vim, or your favorite editor. You can copy and paste the seccomp profile above into this profile.</p>
+<p>We have now found the correct syscall to add to our seccomp profile. Let’s create a seccomp profile with our new syscall mapping. Now we can create a seccomp profile called <code>2_chmod_fedora.json</code> using vim, or your favorite editor. You can copy and paste the seccomp profile above into this profile.</p>
 </div>
 <div class="paragraph">
-<p>Now that you have your new profile created, let&#8217;s run the container again and see if our new seccomp profile blocks <code>chmod</code> &amp; <code>chown</code> from working.</p>
+<p>Now that you have your new profile created, let’s run the container again and see if our new seccomp profile blocks <code>chmod</code> &amp; <code>chown</code> from working.</p>
 </div>
 <div class="listingblock">
 <div class="title">chmod</div>
@@ -643,19 +643,19 @@ <h3 id="_step_4_create_a_seccomp_profile_with_syscall_mapping">Step 4. Create a
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsea1b10be9667b6029af5bef985a9839f8" class="collapsed">
+      <a data-toggle="collapse" href="#collapse379ce5a577a5828a2d9b1941aac38a1a" class="collapsed">
       
         Chmod Result
       </a>
     </h4>
   </div>
   
-  <div id="collapsea1b10be9667b6029af5bef985a9839f8" class="panel-collapse collapse ">
+  <div id="collapse379ce5a577a5828a2d9b1941aac38a1a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">chmod: changing permissions of '/etc/hosts': Operation not permitted</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">chmod: changing permissions of &#39;/etc/hosts&#39;: Operation not permitted</code></pre>
 </div>
 </div>
 
@@ -681,19 +681,19 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseb929fe3dcdb0bdd986a77cc33d4f9610" class="collapsed">
+      <a data-toggle="collapse" href="#collapse40eb259a8de59ce873562eebbced1c19" class="collapsed">
       
         Chown Result
       </a>
     </h4>
   </div>
   
-  <div id="collapseb929fe3dcdb0bdd986a77cc33d4f9610" class="panel-collapse collapse ">
+  <div id="collapse40eb259a8de59ce873562eebbced1c19" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">chown: changing ownership of '/etc/hosts': Operation not permitted</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">chown: changing ownership of &#39;/etc/hosts&#39;: Operation not permitted</code></pre>
 </div>
 </div>
 
@@ -712,12 +712,12 @@ <h4 class="panel-title">
 <h2 id="_section_3_limiting_network_syscalls">Section 3: Limiting Network Syscalls</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Docker presents the socket syscall to containers by default, this may not be a capability you want your containers to have in certain situations. Let&#8217;s look at another example where we use the powerful networking tool, <a href="https://linux.die.net/man/1/nc">Netcat</a>. Netcat is used for just about anything under the sun involving TCP or UDP. It can open TCP connections, send UDP packets, listen on arbitrary TCP and UDP ports, do port scanning, and deal with both IPv4 and IPv6.</p>
+<p>Docker presents the socket syscall to containers by default, this may not be a capability you want your containers to have in certain situations. Let’s look at another example where we use the powerful networking tool, <a href="https://linux.die.net/man/1/nc">Netcat</a>. Netcat is used for just about anything under the sun involving TCP or UDP. It can open TCP connections, send UDP packets, listen on arbitrary TCP and UDP ports, do port scanning, and deal with both IPv4 and IPv6.</p>
 </div>
 <div class="sect2">
 <h3 id="_step_1_run_a_container_with_netcat_installed">Step 1. Run a container with Netcat installed.</h3>
 <div class="paragraph">
-<p>Let&#8217;s run a container with Netcat installed in it and listen for local traffic on port 999.</p>
+<p>Let’s run a container with Netcat installed in it and listen for local traffic on port 999.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -736,7 +736,7 @@ <h3 id="_step_1_run_a_container_with_netcat_installed">Step 1. Run a container w
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Netcat successfully connected. Use <code>Control + C</code> to exit Netcat.</td>
 </tr>
@@ -744,7 +744,7 @@ <h3 id="_step_1_run_a_container_with_netcat_installed">Step 1. Run a container w
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td><code>exit</code> to exit the container.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>We were able to bind to the localhost and listen for traffic on port 999. In Step 2 we will disable networking in this container.</p>
@@ -835,24 +835,24 @@ <h3 id="_step_3">Step 3:</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsedfb4fb6830e841c41e5880c33fd5cdec" class="collapsed">
+      <a data-toggle="collapse" href="#collapsedf17a7df2a5dd2ea3bf600026c46e741" class="collapsed">
       
         Seccomp Profile
       </a>
     </h4>
   </div>
   
-  <div id="collapsedfb4fb6830e841c41e5880c33fd5cdec" class="panel-collapse collapse ">
+  <div id="collapsedf17a7df2a5dd2ea3bf600026c46e741" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">{
-   "defaultAction":"SCMP_ACT_ALLOW",
-   "syscalls":[
+   &#34;defaultAction&#34;:&#34;SCMP_ACT_ALLOW&#34;,
+   &#34;syscalls&#34;:[
       {
-         "name":"socket",
-         "action":"SCMP_ACT_ERRNO"
+         &#34;name&#34;:&#34;socket&#34;,
+         &#34;action&#34;:&#34;SCMP_ACT_ERRNO&#34;
       }
    ]
 }</code></pre>
@@ -871,7 +871,7 @@ <h4 class="panel-title">
 <div class="sect2">
 <h3 id="_step_5_test_the_new_seccomp_profile">Step 5. Test the new seccomp profile</h3>
 <div class="paragraph">
-<p>Now that you have your new profile created, let&#8217;s run the container again and see if our new seccomp profile blocks Netcat from working.</p>
+<p>Now that you have your new profile created, let’s run the container again and see if our new seccomp profile blocks Netcat from working.</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -887,11 +887,11 @@ <h3 id="_step_5_test_the_new_seccomp_profile">Step 5. Test the new seccomp profi
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Netcat is blocked from connecting to a network socket, via the seccomp profile.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -1004,7 +1004,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1264,7 +1264,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1376,7 +1376,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1386,7 +1386,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1473,7 +1473,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.8/index.html b/workshops/security_containers/exercise1.8/index.html
index b5f8edf21..18c6ae059 100644
--- a/workshops/security_containers/exercise1.8/index.html
+++ b/workshops/security_containers/exercise1.8/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.8 - SELinux</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/selinux.png" alt="selinux">
+<img src="/workshops/security_containers/images/selinux.png" alt="selinux"/>
 </div>
 </div>
 </div>
@@ -336,7 +336,7 @@ <h2 id="_exercise_1_8_selinux">Exercise 1.8 - SELinux</h2>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Let&#8217;s move on to Security Enhanced Linux (SELinux). We will cover SELinux basics, Docker SELinux security policy and the "SELinux Coloring Book."</p>
+<p>Let’s move on to Security Enhanced Linux (SELinux). We will cover SELinux basics, Docker SELinux security policy and the &#34;SELinux Coloring Book.&#34;</p>
 </div>
 </div>
 </div>
@@ -370,7 +370,7 @@ <h3 id="_step_1_create_the_following_directories">Step 1. Create the following d
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">echo "SELINUX" &gt; data/file1.txt</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">echo &#34;SELINUX&#34; &gt; data/file1.txt</code></pre>
 </div>
 </div>
 <div class="listingblock">
@@ -442,7 +442,7 @@ <h3 id="_step_6_append_text_from_the_container_to_the_file">Step 6. Append text
 <div class="listingblock">
 <div class="title">Append text</div>
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">sudo podman run -v $(pwd)/data:/data fedora sh -c 'echo "Thank You For Attending" &gt;&gt; /data/file1.txt'</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">sudo podman run -v $(pwd)/data:/data fedora sh -c &#39;echo &#34;Thank You For Attending&#34; &gt;&gt; /data/file1.txt&#39;</code></pre>
 </div>
 </div>
 <div class="listingblock">
@@ -464,7 +464,7 @@ <h2 id="_section_2_container_selinux_security_policy">Section 2: Container SELin
 </div>
 <div class="paragraph">
 <p>The libvirt security policy is a series of SELinux policies that defines two
-methods of isolating virtual machines. Generally, virtual machines are prevented from accessing specific parts of the network. Specifically, individual virtual machines are denied access to each other&#8217;s resources.</p>
+methods of isolating virtual machines. Generally, virtual machines are prevented from accessing specific parts of the network. Specifically, individual virtual machines are denied access to each other’s resources.</p>
 </div>
 <div class="paragraph">
 <p>Red Hat extends the libvirt-SELinux model to containers. The Container SELinux role
@@ -513,14 +513,14 @@ <h2 id="_section_3_selinux_coloring_book">Section 3: SELinux Coloring Book</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse18837bf4cc4411285f561fa946afce91" class="collapsed">
+      <a data-toggle="collapse" href="#collapse5d1ce48e5f4d2bd3991bda08a8b0656d" class="collapsed">
       
         SELinux Coloring Book
       </a>
     </h4>
   </div>
   
-  <div id="collapse18837bf4cc4411285f561fa946afce91" class="panel-collapse collapse ">
+  <div id="collapse5d1ce48e5f4d2bd3991bda08a8b0656d" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
@@ -539,7 +539,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/selinux1.png" alt="Processes">
+<img src="/workshops/security_containers/images/selinux1.png" alt="Processes"/>
 </div>
 </div>
 <div class="paragraph">
@@ -558,7 +558,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/selinux2.png" alt="Objects">
+<img src="/workshops/security_containers/images/selinux2.png" alt="Objects"/>
 </div>
 </div>
 <div class="paragraph">
@@ -578,7 +578,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/selinux3.png" alt="Objects">
+<img src="/workshops/security_containers/images/selinux3.png" alt="Objects"/>
 </div>
 </div>
 <div class="paragraph">
@@ -590,7 +590,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/selinux4.png" alt="Objects">
+<img src="/workshops/security_containers/images/selinux4.png" alt="Objects"/>
 </div>
 </div>
 <div class="paragraph">
@@ -599,7 +599,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/selinux7.png" alt="Stopped by Kernel">
+<img src="/workshops/security_containers/images/selinux7.png" alt="Stopped by Kernel"/>
 </div>
 </div>
 
@@ -727,7 +727,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -987,7 +987,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1099,7 +1099,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1109,7 +1109,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1197,7 +1197,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/exercise1.9/index.html b/workshops/security_containers/exercise1.9/index.html
index ecc03cc0d..158f45b2a 100644
--- a/workshops/security_containers/exercise1.9/index.html
+++ b/workshops/security_containers/exercise1.9/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.9 - Linux Kernel Capabilities</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/kernel.png" alt="kernel">
+<img src="/workshops/security_containers/images/kernel.png" alt="kernel"/>
 </div>
 </div>
 </div>
@@ -449,7 +449,7 @@ <h3 id="_step_3_drop_all_capabilities_and_add_specific_ones_back_in_whitelisting
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Blacklisting: Specifying each capability you want to drop.</td>
 </tr>
@@ -457,7 +457,7 @@ <h3 id="_step_3_drop_all_capabilities_and_add_specific_ones_back_in_whitelisting
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>Whitelisting: Dropping all and adding back the ones you need.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -807,7 +807,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1067,7 +1067,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1179,7 +1179,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1189,7 +1189,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1275,7 +1275,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/index.html b/workshops/security_containers/index.html
index 704fbff63..d85389126 100644
--- a/workshops/security_containers/index.html
+++ b/workshops/security_containers/index.html
@@ -559,7 +559,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -819,7 +819,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -931,7 +931,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -941,7 +941,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -995,7 +995,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/index.xml b/workshops/security_containers/index.xml
index 157eaffaa..0fd9658c9 100644
--- a/workshops/security_containers/index.xml
+++ b/workshops/security_containers/index.xml
@@ -4,139 +4,92 @@
     <title>Container Security Workshop on Red Hat | Public Sector</title>
     <link>/workshops/security_containers/</link>
     <description>Recent content in Container Security Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/security_containers/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/security_containers/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Intro to Cockpit</title>
       <link>/workshops/security_containers/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.0/</guid>
-      <description>Exercise 1.0 - Intro to Cockpit   Exercise Description In this workshop, you will learn to navigate Cockpit and examine its features and capabilities.
- What is Cockpit? A remote manager for GNU/Linux servers
- Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser.
- Cockpit makes it easy for any sysadmin to perform simple tasks, such as administering storage, inspecting journals and starting and stopping services.</description>
+      <description>Exercise 1.0 - Intro to Cockpit Exercise Description In this workshop, you will learn to navigate Cockpit and examine its features and capabilities.&#xA;What is Cockpit? A remote manager for GNU/Linux servers&#xA;Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser.&#xA;Cockpit makes it easy for any sysadmin to perform simple tasks, such as administering storage, inspecting journals and starting and stopping services.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles</title>
       <link>/workshops/security_containers/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.1/</guid>
-      <description>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles   Exercise Description Now that you&amp;#8217;ve gotten a sense of how Cockpit works, we are going to start digging in at the command line on Container security. You can use either the Terminal in Cockpit from your browser, a SSH terminal or Terminal client like PuTTy. The choice is yours.
-   Section 1: Best Practices Step 1.</description>
+      <description>Exercise 1.1 - Reproducible and Trustworthy Dockerfiles Exercise Description Now that you’ve gotten a sense of how Cockpit works, we are going to start digging in at the command line on Container security. You can use either the Terminal in Cockpit from your browser, a SSH terminal or Terminal client like PuTTy. The choice is yours.&#xA;Section 1: Best Practices Step 1. Always specify a tag in FROM instructions. FROM redis is bad, because it pulls the latest tag, which changes over time and can be expected to move with major version changes.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Docker `USER`</title>
       <link>/workshops/security_containers/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.2/</guid>
-      <description>Exercise 1.2 - Docker USER   Exercise Description Now that you&amp;#8217;ve gotten a sense of software provenance in Dockerfiles lets take a look at the USER in Dockerfiles.
- By default, containers run as root. A container running as root has full control of the host system. As container technology matures, more secure default options may become available. For now, requiring root is dangerous for others and may not be available in all environments.</description>
+      <description>Exercise 1.2 - Docker USER Exercise Description Now that you’ve gotten a sense of software provenance in Dockerfiles lets take a look at the USER in Dockerfiles.&#xA;By default, containers run as root. A container running as root has full control of the host system. As container technology matures, more secure default options may become available. For now, requiring root is dangerous for others and may not be available in all environments.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - Remove setuid/setgid Binaries</title>
       <link>/workshops/security_containers/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.3/</guid>
-      <description>Exercise 1.3 - Remove setuid/setgid Binaries   Exercise Description This exercise covers permissions that can be set for setuid and setgid binaries and best practices for managing them.
-   SETUID/SETGID Overview There are two special permissions that can be set on executable files: Set User ID (setuid) and Set Group ID (sgid). These permissions allow the file being executed to be executed with the privileges of the owner or the group.</description>
+      <description>Exercise 1.3 - Remove setuid/setgid Binaries Exercise Description This exercise covers permissions that can be set for setuid and setgid binaries and best practices for managing them.&#xA;SETUID/SETGID Overview There are two special permissions that can be set on executable files: Set User ID (setuid) and Set Group ID (sgid). These permissions allow the file being executed to be executed with the privileges of the owner or the group. For example, if a file was owned by the root user and has the setuid bit set, no matter who executed the file it would always run with root user privileges.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - CGroups</title>
       <link>/workshops/security_containers/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.4/</guid>
-      <description>Exercise 1.4 - CGroups   Exercise Description The Device Cgroup is primary in isolating and limiting containers to their own shares of CPU, memory, disk I/O, network, etc., otherwise the container will be denied. This exercise covers management of memory and CPU limitations.
-   Section 1: Memory Limits Container technology uses Cgroups to control and limit the amount of system resources a container can use, and provide administrators with fine-grained control over allocating, prioritizing, denying, managing and monitoring system resources.</description>
+      <description>Exercise 1.4 - CGroups Exercise Description The Device Cgroup is primary in isolating and limiting containers to their own shares of CPU, memory, disk I/O, network, etc., otherwise the container will be denied. This exercise covers management of memory and CPU limitations.&#xA;Section 1: Memory Limits Container technology uses Cgroups to control and limit the amount of system resources a container can use, and provide administrators with fine-grained control over allocating, prioritizing, denying, managing and monitoring system resources.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Namespaces</title>
       <link>/workshops/security_containers/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.5/</guid>
-      <description>Exercise 1.5 - Namespaces   Exercise Description In this exercise, we will examine how to use namespaces to manage initialization processes, in multiple containers.
- PID namespaces enable processes in different containers to have the same PID (process identifier). This means each container can have its own init (PID1) process that manages various system initialization tasks, as well as the container life cycle.
- Also, each container has its unique /proc directory.</description>
+      <description>Exercise 1.5 - Namespaces Exercise Description In this exercise, we will examine how to use namespaces to manage initialization processes, in multiple containers.&#xA;PID namespaces enable processes in different containers to have the same PID (process identifier). This means each container can have its own init (PID1) process that manages various system initialization tasks, as well as the container life cycle.&#xA;Also, each container has its unique /proc directory. Note that from within the container, you can only monitor those processes running inside this container.</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - Read Only Containers</title>
       <link>/workshops/security_containers/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.6/</guid>
-      <description>Exercise 1.6 - Read Only Containers   Exercise Description Let&amp;#8217;s move on to &#34;Read Only&#34; Containers. This exercise will examine read-only containers and how to manage them.
- Overview
- Imagine a scenario where an application gets compromised. The first thing the bad guy wants to do is to patch a backdoor into the application, so that the next time the application starts up, it starts up with the backdoor in place.</description>
+      <description>Exercise 1.6 - Read Only Containers Exercise Description Let’s move on to &amp;#34;Read Only&amp;#34; Containers. This exercise will examine read-only containers and how to manage them.&#xA;Overview&#xA;Imagine a scenario where an application gets compromised. The first thing the bad guy wants to do is to patch a backdoor into the application, so that the next time the application starts up, it starts up with the backdoor in place. If the container was read-­only it would prevent leaving a backdoor in place and be forced to start the cycle from the beginning.</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - Seccomp</title>
       <link>/workshops/security_containers/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.7/</guid>
-      <description>Exercise 1.7 - Seccomp   Exercise Description Secure Computing Mode (seccomp) is a kernel feature that enables you to filter system calls to the kernel from a container. The combination of restricted and allowed calls are arranged in profiles, and you can pass different profiles to different containers. Seccomp provides more fine-grained control than capabilities, giving an attacker a limited number of syscalls from the container. This exercise examines how seccomp works and how it can be employed to provide container security.</description>
+      <description>Exercise 1.7 - Seccomp Exercise Description Secure Computing Mode (seccomp) is a kernel feature that enables you to filter system calls to the kernel from a container. The combination of restricted and allowed calls are arranged in profiles, and you can pass different profiles to different containers. Seccomp provides more fine-grained control than capabilities, giving an attacker a limited number of syscalls from the container. This exercise examines how seccomp works and how it can be employed to provide container security.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - SELinux</title>
       <link>/workshops/security_containers/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.8/</guid>
-      <description>Exercise 1.8 - SELinux   Exercise Description Let&amp;#8217;s move on to Security Enhanced Linux (SELinux). We will cover SELinux basics, Docker SELinux security policy and the &#34;SELinux Coloring Book.&#34;
-   Section 1: Basics of SELINUX In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations, where the other security mechanisms fail. With SELinux on Docker, we write policy that says that the container process running as svirt_lxc_net_t can only read/write files with the svirt_sandbox_file_t label.</description>
+      <description>Exercise 1.8 - SELinux Exercise Description Let’s move on to Security Enhanced Linux (SELinux). We will cover SELinux basics, Docker SELinux security policy and the &amp;#34;SELinux Coloring Book.&amp;#34;&#xA;Section 1: Basics of SELINUX In this section, we’ll cover the basics of SELinux and containers. SELinux policy prevents a lot of break out situations, where the other security mechanisms fail. With SELinux on Docker, we write policy that says that the container process running as svirt_lxc_net_t can only read/write files with the svirt_sandbox_file_t label.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - Linux Kernel Capabilities</title>
       <link>/workshops/security_containers/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/exercise1.9/</guid>
-      <description>Exercise 1.9 - Linux Kernel Capabilities   Exercise Description In this exercise, we will examine Linux capabilities: how they are defined, their purpose,and how they affect security.
- Linux Capabilities Defined
- According to the capabilities man page;
- Capabilities are distinct units of privilege that can be independently enabled or disabled.
- Capabilities were added to the kernel around 15 or so years ago, to try to divide up the power of root.</description>
+      <description>Exercise 1.9 - Linux Kernel Capabilities Exercise Description In this exercise, we will examine Linux capabilities: how they are defined, their purpose,and how they affect security.&#xA;Linux Capabilities Defined&#xA;According to the capabilities man page;&#xA;Capabilities are distinct units of privilege that can be independently enabled or disabled.&#xA;Capabilities were added to the kernel around 15 or so years ago, to try to divide up the power of root. Originally the kernel allocated a 32-bit bitmask to define these capabilities.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/security_containers/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/setup/</guid>
-      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
+      <description>What you will learn: Red Hat Web Console - Terminal This lab provides a quick tour of the browser based Terminal via the Red Hat Web Console. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Red Hat Enterprise Linux Web Console (cockpit) Use this URL to access the Web Console node, just change the workshop name (if applicable).</description>
     </item>
-    
     <item>
       <title>Wrap Up</title>
       <link>/workshops/security_containers/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_containers/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about Container Security that you can apply in your daily role.
- What do you think? How can we help you understand Container Security better?
- Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your Container education.
- This Participant Guide will remain active for the next two weeks.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about Container Security that you can apply in your daily role.&#xA;What do you think? How can we help you understand Container Security better?&#xA;Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your Container education.&#xA;This Participant Guide will remain active for the next two weeks.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/security_containers/setup/index.html b/workshops/security_containers/setup/index.html
index 5fce55ecf..075db7e1d 100644
--- a/workshops/security_containers/setup/index.html
+++ b/workshops/security_containers/setup/index.html
@@ -337,7 +337,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/cockpit_login.png" alt="cockpit login" height="500">
+<img src="/workshops/security_containers/images/cockpit_login.png" alt="cockpit login" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Login</div>
 </div>
@@ -346,21 +346,21 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_containers/images/cockpit_terminal.png" alt="cockpit terminal" height="500">
+<img src="/workshops/security_containers/images/cockpit_terminal.png" alt="cockpit terminal" height="500"/>
 </div>
 <div class="title">Figure 1: Web Console Terminal Tab</div>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-Be sure you can log in to your instances.  If you can&#8217;t log in start shouting, loudly, and waving your hands!
+Be sure you can log in to your instances.  If you can’t log in start shouting, loudly, and waving your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -368,7 +368,7 @@ <h2 id="_accessing_red_hat_enterprise_linux_web_console_cockpit">Accessing Red H
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -470,7 +470,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -730,7 +730,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -842,7 +842,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -852,7 +852,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -934,7 +934,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_containers/wrapup/index.html b/workshops/security_containers/wrapup/index.html
index b24676a96..844cdef58 100644
--- a/workshops/security_containers/wrapup/index.html
+++ b/workshops/security_containers/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrap Up</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something
+<p>That wraps up what we have planned for today.  We hope you’ve learned something
 valuable about Container Security that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
@@ -367,7 +367,7 @@ <h1>Wrap Up</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.0/index.html b/workshops/security_openshift/exercise1.0/index.html
index 50fab724e..4d04698b1 100644
--- a/workshops/security_openshift/exercise1.0/index.html
+++ b/workshops/security_openshift/exercise1.0/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.0 - Deploy OpenShift</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/openshift-ocp.svg" alt="openshift ocp">
+<img src="/workshops/security_openshift/images/openshift-ocp.svg" alt="openshift ocp"/>
 </div>
 </div>
 <div class="paragraph">
@@ -362,11 +362,11 @@ <h3 id="_step_1">Step 1:</h3>
 <p>Next use the following command to bring up the cluster on your local machine.</p>
 </div>
 <div class="paragraph">
-<p>&lt;div class="alert alert-warning"&gt;</p>
+<p>&lt;div class=&#34;alert alert-warning&#34;&gt;</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>&lt;span class="pficon pficon-warning-triangle-o"&gt;&lt;/span&gt;</pre>
+<pre>&lt;span class=&#34;pficon pficon-warning-triangle-o&#34;&gt;&lt;/span&gt;</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -408,11 +408,11 @@ <h3 id="_step_1">Step 1:</h3>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>OpenShift Web Console, EXAMPLE: <code><a href="https://107.21.72.239:8443" class="bare">https://107.21.72.239:8443</a></code>  or use the DNS name with your student number, Example: <code><a href="https://openshiftsecurity.0.redhatgov.io:8443" class="bare">https://openshiftsecurity.0.redhatgov.io:8443</a></code></td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -437,7 +437,7 @@ <h3 id="_step_2">Step 2:</h3>
 <div class="listingblock">
 <div class="title">create new project</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">oc new-project flask --description="Python Flask App" --display-name="Flask App"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">oc new-project flask --description=&#34;Python Flask App&#34; --display-name=&#34;Flask App&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -480,7 +480,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/login-ocp.png" alt="login ocp">
+<img src="/workshops/security_openshift/images/login-ocp.png" alt="login ocp"/>
 </div>
 <div class="title">Figure 1. OpenShift Main Login</div>
 </div>
@@ -489,7 +489,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/flask-app.png" alt="flask app">
+<img src="/workshops/security_openshift/images/flask-app.png" alt="flask app"/>
 </div>
 <div class="title">Figure 2. Flask App</div>
 </div>
@@ -504,7 +504,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/create-route.png" alt="create route">
+<img src="/workshops/security_openshift/images/create-route.png" alt="create route"/>
 </div>
 <div class="title">Figure 3. create route</div>
 </div>
@@ -520,19 +520,19 @@ <h3 id="_step_3">Step 3:</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsec32e30114960effaeaad995e56ca8757" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7ec800931703c6ba1263d9ed28b348b7" class="collapsed">
       
         Result!
       </a>
     </h4>
   </div>
   
-  <div id="collapsec32e30114960effaeaad995e56ca8757" class="panel-collapse collapse ">
+  <div id="collapse7ec800931703c6ba1263d9ed28b348b7" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/ocp-result.png" alt="ocp result">
+<img src="/workshops/security_openshift/images/ocp-result.png" alt="ocp result"/>
 </div>
 </div>
 
@@ -581,9 +581,9 @@ <h2 id="_extra_credit">Extra credit</h2>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
-<td>This sets OpenShift&#8217;s public name to the public ip of the AMI, via the AWS
+<td>This sets OpenShift’s public name to the public ip of the AMI, via the AWS
 metadata service (169.254.169.254).</td>
 </tr>
 <tr>
@@ -601,7 +601,7 @@ <h2 id="_extra_credit">Extra credit</h2>
 <td>To persist data across restarts, specify a valid host directory when
 starting your cluster with <code>oc</code> cluster up.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -644,7 +644,7 @@ <h2 id="_extra_credit">Extra credit</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.1/index.html b/workshops/security_openshift/exercise1.1/index.html
index 88c3ee46a..d3edb808d 100644
--- a/workshops/security_openshift/exercise1.1/index.html
+++ b/workshops/security_openshift/exercise1.1/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.1 - OpenShift Templates</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/kernel.png" alt="kernel">
+<img src="/workshops/security_openshift/images/kernel.png" alt="kernel"/>
 </div>
 </div>
 </div>
@@ -348,7 +348,7 @@ <h3 id="_step_1">Step 1:</h3>
 <div class="listingblock">
 <div class="title">See Template Parameters</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">oc new-project template --description="Exploring Templates" --display-name="Templates"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">oc new-project template --description=&#34;Exploring Templates&#34; --display-name=&#34;Templates&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -368,23 +368,23 @@ <h3 id="_step_1">Step 1:</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse782ff53fb027fa7f13cc00600574a813" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7e3c6edeb755c8afd8bfa02569d5a4ea" class="collapsed">
       
         Results
       </a>
     </h4>
   </div>
   
-  <div id="collapse782ff53fb027fa7f13cc00600574a813" class="panel-collapse collapse ">
+  <div id="collapse7e3c6edeb755c8afd8bfa02569d5a4ea" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <table class="tableblock frame-all grid-all" style="width: 80%;">
 <caption class="title">Table 1. Windtrainer workouts</caption>
 <colgroup>
-<col style="width: 17.647%;">
-<col style="width: 58.8235%;">
-<col style="width: 11.7647%;">
-<col style="width: 11.7648%;">
+<col style="width: 17.647%;"/>
+<col style="width: 58.8235%;"/>
+<col style="width: 11.7647%;"/>
+<col style="width: 11.7648%;"/>
 </colgroup>
 <thead>
 <tr>
@@ -509,7 +509,7 @@ <h4 class="panel-title">
 <div class="sect2">
 <h3 id="_step_2">Step 2:</h3>
 <div class="paragraph">
-<p>Lets take a deeper look at Templates by switching over to a higher privileged user to be able to edit the Template with your built in editor of choice, (it&#8217;s VIM).</p>
+<p>Lets take a deeper look at Templates by switching over to a higher privileged user to be able to edit the Template with your built in editor of choice, (it’s VIM).</p>
 </div>
 <div class="listingblock">
 <div class="title">Login as the System user</div>
@@ -547,15 +547,15 @@ <h3 id="_step_3">Step 3:</h3>
 <div class="listingblock">
 <div class="title">Multiple OpenShift objects created</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">secret "nodejs-mongo-persistent" created
-service "nodejs-mongo-persistent" created
-route "nodejs-mongo-persistent" created
-imagestream "nodejs-mongo-persistent" created
-buildconfig "nodejs-mongo-persistent" created
-deploymentconfig "nodejs-mongo-persistent" created
-persistentvolumeclaim "mongodb" created
-service "mongodb" created
-deploymentconfig "mongodb" created</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">secret &#34;nodejs-mongo-persistent&#34; created
+service &#34;nodejs-mongo-persistent&#34; created
+route &#34;nodejs-mongo-persistent&#34; created
+imagestream &#34;nodejs-mongo-persistent&#34; created
+buildconfig &#34;nodejs-mongo-persistent&#34; created
+deploymentconfig &#34;nodejs-mongo-persistent&#34; created
+persistentvolumeclaim &#34;mongodb&#34; created
+service &#34;mongodb&#34; created
+deploymentconfig &#34;mongodb&#34; created</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -566,7 +566,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/node-route.png" alt="node route">
+<img src="/workshops/security_openshift/images/node-route.png" alt="node route"/>
 </div>
 </div>
 <div class="paragraph">
@@ -577,19 +577,19 @@ <h3 id="_step_3">Step 3:</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse25a2468f718b43f2452dba6a26425b8e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7c4b7204006ef7167989c8ac58d8d51a" class="collapsed">
       
         Results
       </a>
     </h4>
   </div>
   
-  <div id="collapse25a2468f718b43f2452dba6a26425b8e" class="panel-collapse collapse ">
+  <div id="collapse7c4b7204006ef7167989c8ac58d8d51a" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/node-mongo.png" alt="node mongo">
+<img src="/workshops/security_openshift/images/node-mongo.png" alt="node mongo"/>
 </div>
 </div>
 
@@ -643,7 +643,7 @@ <h4 class="panel-title">
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.2/index.html b/workshops/security_openshift/exercise1.2/index.html
index 8c3ba001e..e863a181b 100644
--- a/workshops/security_openshift/exercise1.2/index.html
+++ b/workshops/security_openshift/exercise1.2/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.2 - Linux Kernel Capabilities</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/kernel.png" alt="kernel">
+<img src="/workshops/security_openshift/images/kernel.png" alt="kernel"/>
 </div>
 </div>
 <div class="paragraph">
@@ -370,11 +370,11 @@ <h2 id="_what_are_linux_capabilities">What are Linux Capabilities?</h2>
 to protect the host system from the containers.</p>
 </div>
 <div class="paragraph">
-<p>&lt;div class="alert alert-warning"&gt;</p>
+<p>&lt;div class=&#34;alert alert-warning&#34;&gt;</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>&lt;span class="pficon pficon-warning-triangle-o"&gt;&lt;/span&gt;</pre>
+<pre>&lt;span class=&#34;pficon pficon-warning-triangle-o&#34;&gt;&lt;/span&gt;</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -457,7 +457,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Blacklisting: Specifying each capability you want to drop.</td>
 </tr>
@@ -465,7 +465,7 @@ <h3 id="_step_3">Step 3:</h3>
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>Whitelisting: Dropping all and adding back the ones you need.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>The main point is that it is easier to be specific and only allow the capabilities that you know your application needs. However Blacklisting can still be very effective in removing the capabilities you are sure you do not want.</p>
@@ -483,11 +483,11 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Container ID to copy</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <p>Then stop and remove the Container.</p>
@@ -791,7 +791,7 @@ <h4 class="panel-title">
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.3/index.html b/workshops/security_openshift/exercise1.3/index.html
index d9c173c88..c1bbbf9a1 100644
--- a/workshops/security_openshift/exercise1.3/index.html
+++ b/workshops/security_openshift/exercise1.3/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.3 - SELinux</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/selinux.png" alt="selinux">
+<img src="/workshops/security_openshift/images/selinux.png" alt="selinux"/>
 </div>
 </div>
 <div class="paragraph">
@@ -395,7 +395,7 @@ <h3 id="_step_1">Step 1:</h3>
 
 mkdir data
 
-echo "SELINUX" &gt; data/file1.txt
+echo &#34;SELINUX&#34; &gt; data/file1.txt
 
 cat data/file1.txt</code></pre>
 </div>
@@ -470,7 +470,7 @@ <h3 id="_step_3">Step 3:</h3>
 <div class="listingblock">
 <div class="title">append text</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo docker run -v $(pwd)/data:/data fedora sh -c 'echo "REDHAT" &gt;&gt; /data/file1.txt'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">sudo docker run -v $(pwd)/data:/data fedora sh -c &#39;echo &#34;REDHAT&#34; &gt;&gt; /data/file1.txt&#39;</code></pre>
 </div>
 </div>
 <div class="listingblock">
@@ -542,14 +542,14 @@ <h2 id="_selinux_coloring_book">SELinux Coloring Book</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse90a40c17b31514c783f6a5af8179fe27" class="collapsed">
+      <a data-toggle="collapse" href="#collapse1710fae6a9c41f845f46672260516775" class="collapsed">
       
         SELinux Coloring Book
       </a>
     </h4>
   </div>
   
-  <div id="collapse90a40c17b31514c783f6a5af8179fe27" class="panel-collapse collapse ">
+  <div id="collapse1710fae6a9c41f845f46672260516775" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="paragraph">
@@ -568,7 +568,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/selinux1.png" alt="Processes">
+<img src="/workshops/security_openshift/images/selinux1.png" alt="Processes"/>
 </div>
 </div>
 <div class="paragraph">
@@ -587,7 +587,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/selinux2.png" alt="Objects">
+<img src="/workshops/security_openshift/images/selinux2.png" alt="Objects"/>
 </div>
 </div>
 <div class="paragraph">
@@ -607,7 +607,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/selinux3.png" alt="Objects">
+<img src="/workshops/security_openshift/images/selinux3.png" alt="Objects"/>
 </div>
 </div>
 <div class="paragraph">
@@ -619,7 +619,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/selinux4.png" alt="Objects">
+<img src="/workshops/security_openshift/images/selinux4.png" alt="Objects"/>
 </div>
 </div>
 <div class="paragraph">
@@ -628,7 +628,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/selinux7.png" alt="Stopped by Kernel">
+<img src="/workshops/security_openshift/images/selinux7.png" alt="Stopped by Kernel"/>
 </div>
 </div>
 
@@ -700,7 +700,7 @@ <h2 id="_selinux_resources">SELinux Resources</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.4/index.html b/workshops/security_openshift/exercise1.4/index.html
index d458a9789..cc68b9221 100644
--- a/workshops/security_openshift/exercise1.4/index.html
+++ b/workshops/security_openshift/exercise1.4/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.4 - Skopeo</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/skopeo.png" alt="skopeo">
+<img src="/workshops/security_openshift/images/skopeo.png" alt="skopeo"/>
 </div>
 </div>
 <div class="paragraph">
@@ -330,7 +330,7 @@ <h1>Exercise 1.4 - Skopeo</h1>
 </div>
 <div class="paragraph">
 <p>Skopeo is able to inspect a repository on a Docker registry and fetch images
-layers. By inspect I mean it fetches the repository&#8217;s manifest and it is able
+layers. By inspect I mean it fetches the repository’s manifest and it is able
 to show you a docker inspect-like json output about a whole repository or a
 tag.</p>
 </div>
@@ -366,7 +366,7 @@ <h3 id="_step_1">Step 1:</h3>
 <div class="listingblock">
 <div class="title">inspect fedora on Docker Hub</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://docker.io/fedora | jq '.'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://docker.io/fedora | jq &#39;.&#39;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -375,7 +375,7 @@ <h3 id="_step_1">Step 1:</h3>
 <div class="listingblock">
 <div class="title">parse Digest</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://docker.io/fedora | jq '.Digest'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://docker.io/fedora | jq &#39;.Digest&#39;</code></pre>
 </div>
 </div>
 </div>
@@ -448,17 +448,17 @@ <h3 id="_step_3">Step 3:</h3>
 <div class="listingblock">
 <div class="title">Mongodb image with Kubernetes labels</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://centos/mongodb-26-centos7 | jq '.'
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://centos/mongodb-26-centos7 | jq &#39;.&#39;
 
-skopeo inspect docker://centos/mongodb-26-centos7 | jq '.Labels'</code></pre>
+skopeo inspect docker://centos/mongodb-26-centos7 | jq &#39;.Labels&#39;</code></pre>
 </div>
 </div>
 <div class="listingblock">
 <div class="title">Wildfly image with Kubernetes labels</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://openshift/wildfly-101-centos7  | jq '.'
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">skopeo inspect docker://openshift/wildfly-101-centos7  | jq &#39;.&#39;
 
-skopeo inspect docker://openshift/wildfly-101-centos7 | jq '.Labels'</code></pre>
+skopeo inspect docker://openshift/wildfly-101-centos7 | jq &#39;.Labels&#39;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -507,7 +507,7 @@ <h3 id="_step_3">Step 3:</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.5/index.html b/workshops/security_openshift/exercise1.5/index.html
index 442cf26cf..1ee372b58 100644
--- a/workshops/security_openshift/exercise1.5/index.html
+++ b/workshops/security_openshift/exercise1.5/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.5 - Atomic Scanner</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/atomic-scan.png" alt="atomic scan">
+<img src="/workshops/security_openshift/images/atomic-scan.png" alt="atomic scan"/>
 </div>
 </div>
 <div class="paragraph">
@@ -367,7 +367,7 @@ <h3 id="_step_1">Step 1:</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s see what types of scanners are available</p>
+<p>Let’s see what types of scanners are available</p>
 </div>
 <div class="listingblock">
 <div class="title">List scanners</div>
@@ -392,7 +392,7 @@ <h3 id="_step_1">Step 1:</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Now let&#8217;s take a look at RHEL7.6 (latest)</p>
+<p>Now let’s take a look at RHEL7.6 (latest)</p>
 </div>
 <div class="listingblock">
 <div class="title">Atomic default scan OpenSCAP</div>
@@ -453,7 +453,7 @@ <h3 id="_step_2">Step 2:</h3>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <div class="title">Important</div>
 </td>
@@ -461,7 +461,7 @@ <h3 id="_step_2">Step 2:</h3>
 Notice <code>.</code> it means in the current directory.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="title">see the newly built container</div>
@@ -488,21 +488,21 @@ <h3 id="_step_2">Step 2:</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse3048be6d454cec1ea8349a6fed791c04" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4a8b0ccc4e312dd3b58e401112fd2a95" class="collapsed">
       
         Result
       </a>
     </h4>
   </div>
   
-  <div id="collapse3048be6d454cec1ea8349a6fed791c04" class="panel-collapse collapse ">
+  <div id="collapse4a8b0ccc4e312dd3b58e401112fd2a95" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">docker run -it --rm --privileged -v /etc/atomic.d/:/host/etc/atomic.d/ example_plugin sh /install.sh
 Copying example_plugin configuration file to host filesystem...
-'/example_plugin' -&gt; '/host/etc/atomic.d/example_plugin'</code></pre>
+&#39;/example_plugin&#39; -&gt; &#39;/host/etc/atomic.d/example_plugin&#39;</code></pre>
 </div>
 </div>
 
@@ -751,15 +751,15 @@ <h2 id="_additional_fun">Additional Fun</h2>
 scanner_name: example_plugin
 image_name: example_plugin
 default_scan: rpm-list
-custom_args: ['-v', '/tmp/foobar:/foobar']
+custom_args: [&#39;-v&#39;, &#39;/tmp/foobar:/foobar&#39;]
 scans: [
  { name: rpm-list,
-   args: ['python', 'list_rpms.py', 'list-rpms'],
-   description: "List all RPMS",
+   args: [&#39;python&#39;, &#39;list_rpms.py&#39;, &#39;list-rpms&#39;],
+   description: &#34;List all RPMS&#34;,
  },
  { name: get-os,
-   args: ['python', 'list_rpms.py', 'get-os'],
-   description: "Get the OS of the object",
+   args: [&#39;python&#39;, &#39;list_rpms.py&#39;, &#39;get-os&#39;],
+   description: &#34;Get the OS of the object&#34;,
  }
 ]</code></pre>
 </div>
@@ -817,7 +817,7 @@ <h2 id="_additional_fun">Additional Fun</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.6/index.html b/workshops/security_openshift/exercise1.6/index.html
index 16348bacc..0e166b703 100644
--- a/workshops/security_openshift/exercise1.6/index.html
+++ b/workshops/security_openshift/exercise1.6/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.6 - SCC &amp; Seccomp</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/scc-node.png" alt="scc node">
+<img src="/workshops/security_openshift/images/scc-node.png" alt="scc node"/>
 </div>
 </div>
 <div class="paragraph">
@@ -411,14 +411,14 @@ <h3 id="_step_2">Step 2:</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse5c9b5a05b64d0beff65802e6eb44dd28" class="collapsed">
+      <a data-toggle="collapse" href="#collapse56f4dd371a394840aba67f33178b5a93" class="collapsed">
       
         Restricted SCC
       </a>
     </h4>
   </div>
   
-  <div id="collapse5c9b5a05b64d0beff65802e6eb44dd28" class="panel-collapse collapse ">
+  <div id="collapse56f4dd371a394840aba67f33178b5a93" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -456,7 +456,7 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Linux Capabilities to be dropped.</td>
 </tr>
@@ -468,7 +468,7 @@ <h4 class="panel-title">
 <td><i class="conum" data-value="3"></i><b>3</b></td>
 <td>SELinux options</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 
     </div>
@@ -487,7 +487,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="paragraph">
 <p>As most people at this workshop are security minded people we will skip over
-<strong>adding</strong> permissions and capabilities to containers, let&#8217;s look at how tighten
+<strong>adding</strong> permissions and capabilities to containers, let’s look at how tighten
 things up. We will look at <strong>dropping</strong> certain Linux Capabilities in this SCC
 file.</p>
 </div>
@@ -527,7 +527,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-note" title="Note"></i>
 </td>
@@ -537,7 +537,7 @@ <h3 id="_step_3">Step 3:</h3>
 <code>:wq</code>.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -592,14 +592,14 @@ <h3 id="_step_4_add_scc_to_a_service_account">Step 4: Add SCC to a service accou
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse992b7ae0f9cb3883ac79778e69b8679e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7e7bfefdc03b697fd1bcfd4614f76b80" class="collapsed">
       
         drop-capabilities result
       </a>
     </h4>
   </div>
   
-  <div id="collapse992b7ae0f9cb3883ac79778e69b8679e" class="panel-collapse collapse ">
+  <div id="collapse7e7bfefdc03b697fd1bcfd4614f76b80" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -637,7 +637,7 @@ <h4 class="panel-title">
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Linux Capabilities to be dropped.</td>
 </tr>
@@ -645,7 +645,7 @@ <h4 class="panel-title">
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>Linux Capabilities are allowed, currently none.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 
     </div>
@@ -667,7 +667,7 @@ <h2 id="_seccomp">Seccomp</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/seccomp-int.png" alt="seccomp int">
+<img src="/workshops/security_openshift/images/seccomp-int.png" alt="seccomp int"/>
 </div>
 </div>
 <div class="paragraph">
@@ -698,11 +698,11 @@ <h2 id="_seccomp">Seccomp</h2>
 be made, rather than a full filter specification.</p>
 </div>
 <div class="paragraph">
-<p>&lt;div class="alert alert-warning"&gt;</p>
+<p>&lt;div class=&#34;alert alert-warning&#34;&gt;</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>&lt;span class="pficon pficon-warning-triangle-o"&gt;&lt;/span&gt;</pre>
+<pre>&lt;span class=&#34;pficon pficon-warning-triangle-o&#34;&gt;&lt;/span&gt;</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -736,7 +736,7 @@ <h3 id="_pod_container_configurations">Pod &amp; Container Configurations</h3>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>profile applies to all containers in the pod that do not override</td>
 </tr>
@@ -744,7 +744,7 @@ <h3 id="_pod_container_configurations">Pod &amp; Container Configurations</h3>
 <td><i class="conum" data-value="2"></i><b>2</b></td>
 <td>container-specific profile override</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect2">
@@ -752,7 +752,7 @@ <h3 id="_policy_examples">Policy Examples:</h3>
 <div class="sect3">
 <h4 id="_unconfined_profile">Unconfined profile</h4>
 <div class="paragraph">
-<p>Here&#8217;s an example of a pod that uses the unconfined profile:</p>
+<p>Here’s an example of a pod that uses the unconfined profile:</p>
 </div>
 <div class="listingblock">
 <div class="title">unconfined</div>
@@ -771,17 +771,17 @@ <h4 id="_unconfined_profile">Unconfined profile</h4>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>Use Kubernetes Pods metadata lables to define the Seccomp profile. This one is using a unconfined profile.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 <div class="sect3">
 <h4 id="_custom_restrictive_profile">Custom restrictive profile</h4>
 <div class="paragraph">
-<p>Here&#8217;s an example of a Pod that uses a profile called <code>example-explorer-profile</code>. This is a sample program that only can set permissions on files and move them to diffrent locations.</p>
+<p>Here’s an example of a Pod that uses a profile called <code>example-explorer-profile</code>. This is a sample program that only can set permissions on files and move them to diffrent locations.</p>
 </div>
 <div class="listingblock">
 <div class="title">custom restricted</div>
@@ -796,12 +796,12 @@ <h4 id="_custom_restrictive_profile">Custom restrictive profile</h4>
   containers:
     - name: explorer
       image: gcr.io/google_containers/explorer:1.0
-      args: ["-port=8080"]
+      args: [&#34;-port=8080&#34;]
       ports:
         - containerPort: 8080
           protocol: TCP
       volumeMounts:
-        - mountPath: "/mount/test-volume"
+        - mountPath: &#34;/mount/test-volume&#34;
           name: test-volume
   volumes:
     - name: test-volume
@@ -810,11 +810,11 @@ <h4 id="_custom_restrictive_profile">Custom restrictive profile</h4>
 </div>
 <div class="colist arabic">
 <table>
-<tr>
+<tbody><tr>
 <td><i class="conum" data-value="1"></i><b>1</b></td>
 <td>This refers to a custom file policy that resides on the localhost and will apply <code>syscall</code> restrictions to the Pod/containers via <code>Secccomp</code>.</td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -828,765 +828,765 @@ <h3 id="_default_docker_seccomp_profile">Default Docker Seccomp Profile</h3>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse8898bfed4baa34391b3b70407ba09050" class="collapsed">
+      <a data-toggle="collapse" href="#collapse170fce730681b0867fa085787ddf0ac3" class="collapsed">
       
         Default Docker Seccomp Profile
       </a>
     </h4>
   </div>
   
-  <div id="collapse8898bfed4baa34391b3b70407ba09050" class="panel-collapse collapse ">
+  <div id="collapse170fce730681b0867fa085787ddf0ac3" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">{
-  "defaultAction": "SCMP_ACT_ERRNO",
-  "archMap": [
+  &#34;defaultAction&#34;: &#34;SCMP_ACT_ERRNO&#34;,
+  &#34;archMap&#34;: [
     {
-      "architecture": "SCMP_ARCH_X86_64",
-      "subArchitectures": [
-        "SCMP_ARCH_X86",
-        "SCMP_ARCH_X32"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_X86_64&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_X86&#34;,
+        &#34;SCMP_ARCH_X32&#34;
       ]
     },
     {
-      "architecture": "SCMP_ARCH_AARCH64",
-      "subArchitectures": [
-        "SCMP_ARCH_ARM"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_AARCH64&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_ARM&#34;
       ]
     },
     {
-      "architecture": "SCMP_ARCH_MIPS64",
-      "subArchitectures": [
-        "SCMP_ARCH_MIPS",
-        "SCMP_ARCH_MIPS64N32"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_MIPS64&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_MIPS&#34;,
+        &#34;SCMP_ARCH_MIPS64N32&#34;
       ]
     },
     {
-      "architecture": "SCMP_ARCH_MIPS64N32",
-      "subArchitectures": [
-        "SCMP_ARCH_MIPS",
-        "SCMP_ARCH_MIPS64"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_MIPS64N32&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_MIPS&#34;,
+        &#34;SCMP_ARCH_MIPS64&#34;
       ]
     },
     {
-      "architecture": "SCMP_ARCH_MIPSEL64",
-      "subArchitectures": [
-        "SCMP_ARCH_MIPSEL",
-        "SCMP_ARCH_MIPSEL64N32"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_MIPSEL64&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_MIPSEL&#34;,
+        &#34;SCMP_ARCH_MIPSEL64N32&#34;
       ]
     },
     {
-      "architecture": "SCMP_ARCH_MIPSEL64N32",
-      "subArchitectures": [
-        "SCMP_ARCH_MIPSEL",
-        "SCMP_ARCH_MIPSEL64"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_MIPSEL64N32&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_MIPSEL&#34;,
+        &#34;SCMP_ARCH_MIPSEL64&#34;
       ]
     },
     {
-      "architecture": "SCMP_ARCH_S390X",
-      "subArchitectures": [
-        "SCMP_ARCH_S390"
+      &#34;architecture&#34;: &#34;SCMP_ARCH_S390X&#34;,
+      &#34;subArchitectures&#34;: [
+        &#34;SCMP_ARCH_S390&#34;
       ]
     }
   ],
-  "syscalls": [
+  &#34;syscalls&#34;: [
     {
-      "names": [
-        "accept",
-        "accept4",
-        "access",
-        "adjtimex",
-        "alarm",
-        "alarm",
-        "bind",
-        "brk",
-        "capget",
-        "capset",
-        "chdir",
-        "chmod",
-        "chown",
-        "chown32",
-        "clock_getres",
-        "clock_gettime",
-        "clock_nanosleep",
-        "close",
-        "connect",
-        "copy_file_range",
-        "creat",
-        "dup",
-        "dup2",
-        "dup3",
-        "epoll_create",
-        "epoll_create1",
-        "epoll_ctl",
-        "epoll_ctl_old",
-        "epoll_pwait",
-        "epoll_wait",
-        "epoll_wait_old",
-        "eventfd",
-        "eventfd2",
-        "execve",
-        "execveat",
-        "exit",
-        "exit_group",
-        "faccessat",
-        "fadvise64",
-        "fadvise64_64",
-        "fallocate",
-        "fanotify_mark",
-        "fchdir",
-        "fchmod",
-        "fchmodat",
-        "fchown",
-        "fchown32",
-        "fchownat",
-        "fcntl",
-        "fcntl64",
-        "fdatasync",
-        "fgetxattr",
-        "flistxattr",
-        "flock",
-        "fork",
-        "fremovexattr",
-        "fsetxattr",
-        "fstat",
-        "fstat64",
-        "fstatat64",
-        "fstatfs",
-        "fstatfs64",
-        "fsync",
-        "ftruncate",
-        "ftruncate64",
-        "futex",
-        "futimesat",
-        "getcpu",
-        "getcwd",
-        "getdents",
-        "getdents64",
-        "getegid",
-        "getegid32",
-        "geteuid",
-        "geteuid32",
-        "getgid",
-        "getgid32",
-        "getgroups",
-        "getgroups32",
-        "getitimer",
-        "getpeername",
-        "getpgid",
-        "getpgrp",
-        "getpid",
-        "getppid",
-        "getpriority",
-        "getrandom",
-        "getresgid",
-        "getresgid32",
-        "getresuid",
-        "getresuid32",
-        "getrlimit",
-        "get_robust_list",
-        "getrusage",
-        "getsid",
-        "getsockname",
-        "getsockopt",
-        "get_thread_area",
-        "gettid",
-        "gettimeofday",
-        "getuid",
-        "getuid32",
-        "getxattr",
-        "inotify_add_watch",
-        "inotify_init",
-        "inotify_init1",
-        "inotify_rm_watch",
-        "io_cancel",
-        "ioctl",
-        "io_destroy",
-        "io_getevents",
-        "ioprio_get",
-        "ioprio_set",
-        "io_setup",
-        "io_submit",
-        "ipc",
-        "kill",
-        "lchown",
-        "lchown32",
-        "lgetxattr",
-        "link",
-        "linkat",
-        "listen",
-        "listxattr",
-        "llistxattr",
-        "_llseek",
-        "lremovexattr",
-        "lseek",
-        "lsetxattr",
-        "lstat",
-        "lstat64",
-        "madvise",
-        "memfd_create",
-        "mincore",
-        "mkdir",
-        "mkdirat",
-        "mknod",
-        "mknodat",
-        "mlock",
-        "mlock2",
-        "mlockall",
-        "mmap",
-        "mmap2",
-        "mprotect",
-        "mq_getsetattr",
-        "mq_notify",
-        "mq_open",
-        "mq_timedreceive",
-        "mq_timedsend",
-        "mq_unlink",
-        "mremap",
-        "msgctl",
-        "msgget",
-        "msgrcv",
-        "msgsnd",
-        "msync",
-        "munlock",
-        "munlockall",
-        "munmap",
-        "nanosleep",
-        "newfstatat",
-        "_newselect",
-        "open",
-        "openat",
-        "pause",
-        "pipe",
-        "pipe2",
-        "poll",
-        "ppoll",
-        "prctl",
-        "pread64",
-        "preadv",
-        "preadv2",
-        "prlimit64",
-        "pselect6",
-        "pwrite64",
-        "pwritev",
-        "pwritev2",
-        "read",
-        "readahead",
-        "readlink",
-        "readlinkat",
-        "readv",
-        "recv",
-        "recvfrom",
-        "recvmmsg",
-        "recvmsg",
-        "remap_file_pages",
-        "removexattr",
-        "rename",
-        "renameat",
-        "renameat2",
-        "restart_syscall",
-        "rmdir",
-        "rt_sigaction",
-        "rt_sigpending",
-        "rt_sigprocmask",
-        "rt_sigqueueinfo",
-        "rt_sigreturn",
-        "rt_sigsuspend",
-        "rt_sigtimedwait",
-        "rt_tgsigqueueinfo",
-        "sched_getaffinity",
-        "sched_getattr",
-        "sched_getparam",
-        "sched_get_priority_max",
-        "sched_get_priority_min",
-        "sched_getscheduler",
-        "sched_rr_get_interval",
-        "sched_setaffinity",
-        "sched_setattr",
-        "sched_setparam",
-        "sched_setscheduler",
-        "sched_yield",
-        "seccomp",
-        "select",
-        "semctl",
-        "semget",
-        "semop",
-        "semtimedop",
-        "send",
-        "sendfile",
-        "sendfile64",
-        "sendmmsg",
-        "sendmsg",
-        "sendto",
-        "setfsgid",
-        "setfsgid32",
-        "setfsuid",
-        "setfsuid32",
-        "setgid",
-        "setgid32",
-        "setgroups",
-        "setgroups32",
-        "setitimer",
-        "setpgid",
-        "setpriority",
-        "setregid",
-        "setregid32",
-        "setresgid",
-        "setresgid32",
-        "setresuid",
-        "setresuid32",
-        "setreuid",
-        "setreuid32",
-        "setrlimit",
-        "set_robust_list",
-        "setsid",
-        "setsockopt",
-        "set_thread_area",
-        "set_tid_address",
-        "setuid",
-        "setuid32",
-        "setxattr",
-        "shmat",
-        "shmctl",
-        "shmdt",
-        "shmget",
-        "shutdown",
-        "sigaltstack",
-        "signalfd",
-        "signalfd4",
-        "sigreturn",
-        "socket",
-        "socketcall",
-        "socketpair",
-        "splice",
-        "stat",
-        "stat64",
-        "statfs",
-        "statfs64",
-        "symlink",
-        "symlinkat",
-        "sync",
-        "sync_file_range",
-        "syncfs",
-        "sysinfo",
-        "syslog",
-        "tee",
-        "tgkill",
-        "time",
-        "timer_create",
-        "timer_delete",
-        "timerfd_create",
-        "timerfd_gettime",
-        "timerfd_settime",
-        "timer_getoverrun",
-        "timer_gettime",
-        "timer_settime",
-        "times",
-        "tkill",
-        "truncate",
-        "truncate64",
-        "ugetrlimit",
-        "umask",
-        "uname",
-        "unlink",
-        "unlinkat",
-        "utime",
-        "utimensat",
-        "utimes",
-        "vfork",
-        "vmsplice",
-        "wait4",
-        "waitid",
-        "waitpid",
-        "write",
-        "writev"
+      &#34;names&#34;: [
+        &#34;accept&#34;,
+        &#34;accept4&#34;,
+        &#34;access&#34;,
+        &#34;adjtimex&#34;,
+        &#34;alarm&#34;,
+        &#34;alarm&#34;,
+        &#34;bind&#34;,
+        &#34;brk&#34;,
+        &#34;capget&#34;,
+        &#34;capset&#34;,
+        &#34;chdir&#34;,
+        &#34;chmod&#34;,
+        &#34;chown&#34;,
+        &#34;chown32&#34;,
+        &#34;clock_getres&#34;,
+        &#34;clock_gettime&#34;,
+        &#34;clock_nanosleep&#34;,
+        &#34;close&#34;,
+        &#34;connect&#34;,
+        &#34;copy_file_range&#34;,
+        &#34;creat&#34;,
+        &#34;dup&#34;,
+        &#34;dup2&#34;,
+        &#34;dup3&#34;,
+        &#34;epoll_create&#34;,
+        &#34;epoll_create1&#34;,
+        &#34;epoll_ctl&#34;,
+        &#34;epoll_ctl_old&#34;,
+        &#34;epoll_pwait&#34;,
+        &#34;epoll_wait&#34;,
+        &#34;epoll_wait_old&#34;,
+        &#34;eventfd&#34;,
+        &#34;eventfd2&#34;,
+        &#34;execve&#34;,
+        &#34;execveat&#34;,
+        &#34;exit&#34;,
+        &#34;exit_group&#34;,
+        &#34;faccessat&#34;,
+        &#34;fadvise64&#34;,
+        &#34;fadvise64_64&#34;,
+        &#34;fallocate&#34;,
+        &#34;fanotify_mark&#34;,
+        &#34;fchdir&#34;,
+        &#34;fchmod&#34;,
+        &#34;fchmodat&#34;,
+        &#34;fchown&#34;,
+        &#34;fchown32&#34;,
+        &#34;fchownat&#34;,
+        &#34;fcntl&#34;,
+        &#34;fcntl64&#34;,
+        &#34;fdatasync&#34;,
+        &#34;fgetxattr&#34;,
+        &#34;flistxattr&#34;,
+        &#34;flock&#34;,
+        &#34;fork&#34;,
+        &#34;fremovexattr&#34;,
+        &#34;fsetxattr&#34;,
+        &#34;fstat&#34;,
+        &#34;fstat64&#34;,
+        &#34;fstatat64&#34;,
+        &#34;fstatfs&#34;,
+        &#34;fstatfs64&#34;,
+        &#34;fsync&#34;,
+        &#34;ftruncate&#34;,
+        &#34;ftruncate64&#34;,
+        &#34;futex&#34;,
+        &#34;futimesat&#34;,
+        &#34;getcpu&#34;,
+        &#34;getcwd&#34;,
+        &#34;getdents&#34;,
+        &#34;getdents64&#34;,
+        &#34;getegid&#34;,
+        &#34;getegid32&#34;,
+        &#34;geteuid&#34;,
+        &#34;geteuid32&#34;,
+        &#34;getgid&#34;,
+        &#34;getgid32&#34;,
+        &#34;getgroups&#34;,
+        &#34;getgroups32&#34;,
+        &#34;getitimer&#34;,
+        &#34;getpeername&#34;,
+        &#34;getpgid&#34;,
+        &#34;getpgrp&#34;,
+        &#34;getpid&#34;,
+        &#34;getppid&#34;,
+        &#34;getpriority&#34;,
+        &#34;getrandom&#34;,
+        &#34;getresgid&#34;,
+        &#34;getresgid32&#34;,
+        &#34;getresuid&#34;,
+        &#34;getresuid32&#34;,
+        &#34;getrlimit&#34;,
+        &#34;get_robust_list&#34;,
+        &#34;getrusage&#34;,
+        &#34;getsid&#34;,
+        &#34;getsockname&#34;,
+        &#34;getsockopt&#34;,
+        &#34;get_thread_area&#34;,
+        &#34;gettid&#34;,
+        &#34;gettimeofday&#34;,
+        &#34;getuid&#34;,
+        &#34;getuid32&#34;,
+        &#34;getxattr&#34;,
+        &#34;inotify_add_watch&#34;,
+        &#34;inotify_init&#34;,
+        &#34;inotify_init1&#34;,
+        &#34;inotify_rm_watch&#34;,
+        &#34;io_cancel&#34;,
+        &#34;ioctl&#34;,
+        &#34;io_destroy&#34;,
+        &#34;io_getevents&#34;,
+        &#34;ioprio_get&#34;,
+        &#34;ioprio_set&#34;,
+        &#34;io_setup&#34;,
+        &#34;io_submit&#34;,
+        &#34;ipc&#34;,
+        &#34;kill&#34;,
+        &#34;lchown&#34;,
+        &#34;lchown32&#34;,
+        &#34;lgetxattr&#34;,
+        &#34;link&#34;,
+        &#34;linkat&#34;,
+        &#34;listen&#34;,
+        &#34;listxattr&#34;,
+        &#34;llistxattr&#34;,
+        &#34;_llseek&#34;,
+        &#34;lremovexattr&#34;,
+        &#34;lseek&#34;,
+        &#34;lsetxattr&#34;,
+        &#34;lstat&#34;,
+        &#34;lstat64&#34;,
+        &#34;madvise&#34;,
+        &#34;memfd_create&#34;,
+        &#34;mincore&#34;,
+        &#34;mkdir&#34;,
+        &#34;mkdirat&#34;,
+        &#34;mknod&#34;,
+        &#34;mknodat&#34;,
+        &#34;mlock&#34;,
+        &#34;mlock2&#34;,
+        &#34;mlockall&#34;,
+        &#34;mmap&#34;,
+        &#34;mmap2&#34;,
+        &#34;mprotect&#34;,
+        &#34;mq_getsetattr&#34;,
+        &#34;mq_notify&#34;,
+        &#34;mq_open&#34;,
+        &#34;mq_timedreceive&#34;,
+        &#34;mq_timedsend&#34;,
+        &#34;mq_unlink&#34;,
+        &#34;mremap&#34;,
+        &#34;msgctl&#34;,
+        &#34;msgget&#34;,
+        &#34;msgrcv&#34;,
+        &#34;msgsnd&#34;,
+        &#34;msync&#34;,
+        &#34;munlock&#34;,
+        &#34;munlockall&#34;,
+        &#34;munmap&#34;,
+        &#34;nanosleep&#34;,
+        &#34;newfstatat&#34;,
+        &#34;_newselect&#34;,
+        &#34;open&#34;,
+        &#34;openat&#34;,
+        &#34;pause&#34;,
+        &#34;pipe&#34;,
+        &#34;pipe2&#34;,
+        &#34;poll&#34;,
+        &#34;ppoll&#34;,
+        &#34;prctl&#34;,
+        &#34;pread64&#34;,
+        &#34;preadv&#34;,
+        &#34;preadv2&#34;,
+        &#34;prlimit64&#34;,
+        &#34;pselect6&#34;,
+        &#34;pwrite64&#34;,
+        &#34;pwritev&#34;,
+        &#34;pwritev2&#34;,
+        &#34;read&#34;,
+        &#34;readahead&#34;,
+        &#34;readlink&#34;,
+        &#34;readlinkat&#34;,
+        &#34;readv&#34;,
+        &#34;recv&#34;,
+        &#34;recvfrom&#34;,
+        &#34;recvmmsg&#34;,
+        &#34;recvmsg&#34;,
+        &#34;remap_file_pages&#34;,
+        &#34;removexattr&#34;,
+        &#34;rename&#34;,
+        &#34;renameat&#34;,
+        &#34;renameat2&#34;,
+        &#34;restart_syscall&#34;,
+        &#34;rmdir&#34;,
+        &#34;rt_sigaction&#34;,
+        &#34;rt_sigpending&#34;,
+        &#34;rt_sigprocmask&#34;,
+        &#34;rt_sigqueueinfo&#34;,
+        &#34;rt_sigreturn&#34;,
+        &#34;rt_sigsuspend&#34;,
+        &#34;rt_sigtimedwait&#34;,
+        &#34;rt_tgsigqueueinfo&#34;,
+        &#34;sched_getaffinity&#34;,
+        &#34;sched_getattr&#34;,
+        &#34;sched_getparam&#34;,
+        &#34;sched_get_priority_max&#34;,
+        &#34;sched_get_priority_min&#34;,
+        &#34;sched_getscheduler&#34;,
+        &#34;sched_rr_get_interval&#34;,
+        &#34;sched_setaffinity&#34;,
+        &#34;sched_setattr&#34;,
+        &#34;sched_setparam&#34;,
+        &#34;sched_setscheduler&#34;,
+        &#34;sched_yield&#34;,
+        &#34;seccomp&#34;,
+        &#34;select&#34;,
+        &#34;semctl&#34;,
+        &#34;semget&#34;,
+        &#34;semop&#34;,
+        &#34;semtimedop&#34;,
+        &#34;send&#34;,
+        &#34;sendfile&#34;,
+        &#34;sendfile64&#34;,
+        &#34;sendmmsg&#34;,
+        &#34;sendmsg&#34;,
+        &#34;sendto&#34;,
+        &#34;setfsgid&#34;,
+        &#34;setfsgid32&#34;,
+        &#34;setfsuid&#34;,
+        &#34;setfsuid32&#34;,
+        &#34;setgid&#34;,
+        &#34;setgid32&#34;,
+        &#34;setgroups&#34;,
+        &#34;setgroups32&#34;,
+        &#34;setitimer&#34;,
+        &#34;setpgid&#34;,
+        &#34;setpriority&#34;,
+        &#34;setregid&#34;,
+        &#34;setregid32&#34;,
+        &#34;setresgid&#34;,
+        &#34;setresgid32&#34;,
+        &#34;setresuid&#34;,
+        &#34;setresuid32&#34;,
+        &#34;setreuid&#34;,
+        &#34;setreuid32&#34;,
+        &#34;setrlimit&#34;,
+        &#34;set_robust_list&#34;,
+        &#34;setsid&#34;,
+        &#34;setsockopt&#34;,
+        &#34;set_thread_area&#34;,
+        &#34;set_tid_address&#34;,
+        &#34;setuid&#34;,
+        &#34;setuid32&#34;,
+        &#34;setxattr&#34;,
+        &#34;shmat&#34;,
+        &#34;shmctl&#34;,
+        &#34;shmdt&#34;,
+        &#34;shmget&#34;,
+        &#34;shutdown&#34;,
+        &#34;sigaltstack&#34;,
+        &#34;signalfd&#34;,
+        &#34;signalfd4&#34;,
+        &#34;sigreturn&#34;,
+        &#34;socket&#34;,
+        &#34;socketcall&#34;,
+        &#34;socketpair&#34;,
+        &#34;splice&#34;,
+        &#34;stat&#34;,
+        &#34;stat64&#34;,
+        &#34;statfs&#34;,
+        &#34;statfs64&#34;,
+        &#34;symlink&#34;,
+        &#34;symlinkat&#34;,
+        &#34;sync&#34;,
+        &#34;sync_file_range&#34;,
+        &#34;syncfs&#34;,
+        &#34;sysinfo&#34;,
+        &#34;syslog&#34;,
+        &#34;tee&#34;,
+        &#34;tgkill&#34;,
+        &#34;time&#34;,
+        &#34;timer_create&#34;,
+        &#34;timer_delete&#34;,
+        &#34;timerfd_create&#34;,
+        &#34;timerfd_gettime&#34;,
+        &#34;timerfd_settime&#34;,
+        &#34;timer_getoverrun&#34;,
+        &#34;timer_gettime&#34;,
+        &#34;timer_settime&#34;,
+        &#34;times&#34;,
+        &#34;tkill&#34;,
+        &#34;truncate&#34;,
+        &#34;truncate64&#34;,
+        &#34;ugetrlimit&#34;,
+        &#34;umask&#34;,
+        &#34;uname&#34;,
+        &#34;unlink&#34;,
+        &#34;unlinkat&#34;,
+        &#34;utime&#34;,
+        &#34;utimensat&#34;,
+        &#34;utimes&#34;,
+        &#34;vfork&#34;,
+        &#34;vmsplice&#34;,
+        &#34;wait4&#34;,
+        &#34;waitid&#34;,
+        &#34;waitpid&#34;,
+        &#34;write&#34;,
+        &#34;writev&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {},
-      "excludes": {}
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "personality"
+      &#34;names&#34;: [
+        &#34;personality&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 0,
-          "value": 0,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_EQ"
+          &#34;index&#34;: 0,
+          &#34;value&#34;: 0,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_EQ&#34;
         }
       ],
-      "comment": "",
-      "includes": {},
-      "excludes": {}
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "personality"
+      &#34;names&#34;: [
+        &#34;personality&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 0,
-          "value": 8,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_EQ"
+          &#34;index&#34;: 0,
+          &#34;value&#34;: 8,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_EQ&#34;
         }
       ],
-      "comment": "",
-      "includes": {},
-      "excludes": {}
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "personality"
+      &#34;names&#34;: [
+        &#34;personality&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 0,
-          "value": 131072,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_EQ"
+          &#34;index&#34;: 0,
+          &#34;value&#34;: 131072,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_EQ&#34;
         }
       ],
-      "comment": "",
-      "includes": {},
-      "excludes": {}
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "personality"
+      &#34;names&#34;: [
+        &#34;personality&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 0,
-          "value": 131080,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_EQ"
+          &#34;index&#34;: 0,
+          &#34;value&#34;: 131080,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_EQ&#34;
         }
       ],
-      "comment": "",
-      "includes": {},
-      "excludes": {}
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "personality"
+      &#34;names&#34;: [
+        &#34;personality&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 0,
-          "value": 4294967295,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_EQ"
+          &#34;index&#34;: 0,
+          &#34;value&#34;: 4294967295,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_EQ&#34;
         }
       ],
-      "comment": "",
-      "includes": {},
-      "excludes": {}
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "sync_file_range2"
+      &#34;names&#34;: [
+        &#34;sync_file_range2&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "arches": [
-          "ppc64le"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;arches&#34;: [
+          &#34;ppc64le&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "arm_fadvise64_64",
-        "arm_sync_file_range",
-        "sync_file_range2",
-        "breakpoint",
-        "cacheflush",
-        "set_tls"
+      &#34;names&#34;: [
+        &#34;arm_fadvise64_64&#34;,
+        &#34;arm_sync_file_range&#34;,
+        &#34;sync_file_range2&#34;,
+        &#34;breakpoint&#34;,
+        &#34;cacheflush&#34;,
+        &#34;set_tls&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "arches": [
-          "arm",
-          "arm64"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;arches&#34;: [
+          &#34;arm&#34;,
+          &#34;arm64&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "arch_prctl"
+      &#34;names&#34;: [
+        &#34;arch_prctl&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "arches": [
-          "amd64",
-          "x32"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;arches&#34;: [
+          &#34;amd64&#34;,
+          &#34;x32&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "modify_ldt"
+      &#34;names&#34;: [
+        &#34;modify_ldt&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "arches": [
-          "amd64",
-          "x32",
-          "x86"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;arches&#34;: [
+          &#34;amd64&#34;,
+          &#34;x32&#34;,
+          &#34;x86&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "s390_pci_mmio_read",
-        "s390_pci_mmio_write",
-        "s390_runtime_instr"
+      &#34;names&#34;: [
+        &#34;s390_pci_mmio_read&#34;,
+        &#34;s390_pci_mmio_write&#34;,
+        &#34;s390_runtime_instr&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "arches": [
-          "s390",
-          "s390x"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;arches&#34;: [
+          &#34;s390&#34;,
+          &#34;s390x&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "open_by_handle_at"
+      &#34;names&#34;: [
+        &#34;open_by_handle_at&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_DAC_READ_SEARCH"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_DAC_READ_SEARCH&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "bpf",
-        "clone",
-        "fanotify_init",
-        "lookup_dcookie",
-        "mount",
-        "name_to_handle_at",
-        "perf_event_open",
-        "setdomainname",
-        "sethostname",
-        "setns",
-        "umount",
-        "umount2",
-        "unshare"
+      &#34;names&#34;: [
+        &#34;bpf&#34;,
+        &#34;clone&#34;,
+        &#34;fanotify_init&#34;,
+        &#34;lookup_dcookie&#34;,
+        &#34;mount&#34;,
+        &#34;name_to_handle_at&#34;,
+        &#34;perf_event_open&#34;,
+        &#34;setdomainname&#34;,
+        &#34;sethostname&#34;,
+        &#34;setns&#34;,
+        &#34;umount&#34;,
+        &#34;umount2&#34;,
+        &#34;unshare&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_ADMIN"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_ADMIN&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "clone"
+      &#34;names&#34;: [
+        &#34;clone&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 0,
-          "value": 2080505856,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_MASKED_EQ"
+          &#34;index&#34;: 0,
+          &#34;value&#34;: 2080505856,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_MASKED_EQ&#34;
         }
       ],
-      "comment": "",
-      "includes": {},
-      "excludes": {
-        "caps": [
-          "CAP_SYS_ADMIN"
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {},
+      &#34;excludes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_ADMIN&#34;
         ],
-        "arches": [
-          "s390",
-          "s390x"
+        &#34;arches&#34;: [
+          &#34;s390&#34;,
+          &#34;s390x&#34;
         ]
       }
     },
     {
-      "names": [
-        "clone"
+      &#34;names&#34;: [
+        &#34;clone&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [
         {
-          "index": 1,
-          "value": 2080505856,
-          "valueTwo": 0,
-          "op": "SCMP_CMP_MASKED_EQ"
+          &#34;index&#34;: 1,
+          &#34;value&#34;: 2080505856,
+          &#34;valueTwo&#34;: 0,
+          &#34;op&#34;: &#34;SCMP_CMP_MASKED_EQ&#34;
         }
       ],
-      "comment": "s390 parameter ordering for clone is different",
-      "includes": {
-        "arches": [
-          "s390",
-          "s390x"
+      &#34;comment&#34;: &#34;s390 parameter ordering for clone is different&#34;,
+      &#34;includes&#34;: {
+        &#34;arches&#34;: [
+          &#34;s390&#34;,
+          &#34;s390x&#34;
         ]
       },
-      "excludes": {
-        "caps": [
-          "CAP_SYS_ADMIN"
+      &#34;excludes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_ADMIN&#34;
         ]
       }
     },
     {
-      "names": [
-        "reboot"
+      &#34;names&#34;: [
+        &#34;reboot&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_BOOT"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_BOOT&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "chroot"
+      &#34;names&#34;: [
+        &#34;chroot&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_CHROOT"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_CHROOT&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "delete_module",
-        "init_module",
-        "finit_module",
-        "query_module"
+      &#34;names&#34;: [
+        &#34;delete_module&#34;,
+        &#34;init_module&#34;,
+        &#34;finit_module&#34;,
+        &#34;query_module&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_MODULE"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_MODULE&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "acct"
+      &#34;names&#34;: [
+        &#34;acct&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_PACCT"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_PACCT&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "kcmp",
-        "process_vm_readv",
-        "process_vm_writev",
-        "ptrace"
+      &#34;names&#34;: [
+        &#34;kcmp&#34;,
+        &#34;process_vm_readv&#34;,
+        &#34;process_vm_writev&#34;,
+        &#34;ptrace&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_PTRACE"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_PTRACE&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "iopl",
-        "ioperm"
+      &#34;names&#34;: [
+        &#34;iopl&#34;,
+        &#34;ioperm&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_RAWIO"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_RAWIO&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "settimeofday",
-        "stime",
-        "clock_settime"
+      &#34;names&#34;: [
+        &#34;settimeofday&#34;,
+        &#34;stime&#34;,
+        &#34;clock_settime&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_TIME"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_TIME&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     },
     {
-      "names": [
-        "vhangup"
+      &#34;names&#34;: [
+        &#34;vhangup&#34;
       ],
-      "action": "SCMP_ACT_ALLOW",
-      "args": [],
-      "comment": "",
-      "includes": {
-        "caps": [
-          "CAP_SYS_TTY_CONFIG"
+      &#34;action&#34;: &#34;SCMP_ACT_ALLOW&#34;,
+      &#34;args&#34;: [],
+      &#34;comment&#34;: &#34;&#34;,
+      &#34;includes&#34;: {
+        &#34;caps&#34;: [
+          &#34;CAP_SYS_TTY_CONFIG&#34;
         ]
       },
-      "excludes": {}
+      &#34;excludes&#34;: {}
     }
   ]
 }</code></pre>
@@ -1660,7 +1660,7 @@ <h3 id="_seccomp_refrence">Seccomp Refrence</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.7/index.html b/workshops/security_openshift/exercise1.7/index.html
index 92bcf5c0d..b57a48948 100644
--- a/workshops/security_openshift/exercise1.7/index.html
+++ b/workshops/security_openshift/exercise1.7/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.7 - Red Hat Container Catalog</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/catalog.png" alt="catalog">
+<img src="/workshops/security_openshift/images/catalog.png" alt="catalog"/>
 </div>
 </div>
 <div class="paragraph">
@@ -360,19 +360,19 @@ <h2 id="_get_this_image">Get This Image</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsedff1545d4f0fbe435d813c52e9602ca8" class="collapsed">
+      <a data-toggle="collapse" href="#collapse60622b6793de9fd9e770e7a2c62b35a6" class="collapsed">
       
         Get This Image Example
       </a>
     </h4>
   </div>
   
-  <div id="collapsedff1545d4f0fbe435d813c52e9602ca8" class="panel-collapse collapse ">
+  <div id="collapse60622b6793de9fd9e770e7a2c62b35a6" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/get-this-image.png" alt="get this image">
+<img src="/workshops/security_openshift/images/get-this-image.png" alt="get this image"/>
 </div>
 </div>
 
@@ -392,14 +392,14 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseea20105982306100bd3186a523f5d5db" class="collapsed">
+      <a data-toggle="collapse" href="#collapse02302896eba8cc5522304b743c05e749" class="collapsed">
       
         Multiple Methods for getting RHEL 7
       </a>
     </h4>
   </div>
   
-  <div id="collapseea20105982306100bd3186a523f5d5db" class="panel-collapse collapse ">
+  <div id="collapse02302896eba8cc5522304b743c05e749" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
@@ -412,13 +412,13 @@ <h4 class="panel-title">
 <div class="title">Use Red Hat Satellite to pull RHEL 7</div>
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash"># set the organization
-      ORG="ACME"
+      ORG=&#34;ACME&#34;
       # set the product name
-      PRODUCT="redhat-images"
+      PRODUCT=&#34;redhat-images&#34;
       # create the product
-      hammer product create --name "${PRODUCT}" \
-      --description "container images" \
-      --organization="${ORG}" --organization "${ORG}"</code></pre>
+      hammer product create --name &#34;${PRODUCT}&#34; \
+      --description &#34;container images&#34; \
+      --organization=&#34;${ORG}&#34; --organization &#34;${ORG}&#34;</code></pre>
 </div>
 </div>
 <div class="listingblock">
@@ -527,19 +527,19 @@ <h2 id="_documentation">Documentation</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse85e8a246abf677493860623c100fa2eb" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4793a0109a7466446f4ba763bccc8ad9" class="collapsed">
       
         Documentation Example
       </a>
     </h4>
   </div>
   
-  <div id="collapse85e8a246abf677493860623c100fa2eb" class="panel-collapse collapse ">
+  <div id="collapse4793a0109a7466446f4ba763bccc8ad9" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/catalog-documentation.png" alt="catalog documentation">
+<img src="/workshops/security_openshift/images/catalog-documentation.png" alt="catalog documentation"/>
 </div>
 </div>
 
@@ -576,7 +576,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-a.png" alt="grade a">
+<img src="/workshops/security_openshift/images/grade-a.png" alt="grade a"/>
 </div>
 </div>
 <div class="paragraph">
@@ -584,7 +584,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-b.png" alt="grade b">
+<img src="/workshops/security_openshift/images/grade-b.png" alt="grade b"/>
 </div>
 </div>
 <div class="paragraph">
@@ -592,7 +592,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-c.png" alt="grade c">
+<img src="/workshops/security_openshift/images/grade-c.png" alt="grade c"/>
 </div>
 </div>
 <div class="paragraph">
@@ -600,7 +600,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-d.png" alt="grade d">
+<img src="/workshops/security_openshift/images/grade-d.png" alt="grade d"/>
 </div>
 </div>
 <div class="paragraph">
@@ -608,7 +608,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-e.png" alt="grade e">
+<img src="/workshops/security_openshift/images/grade-e.png" alt="grade e"/>
 </div>
 </div>
 <div class="paragraph">
@@ -616,7 +616,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-f.png" alt="grade f">
+<img src="/workshops/security_openshift/images/grade-f.png" alt="grade f"/>
 </div>
 </div>
 <div class="paragraph">
@@ -624,7 +624,7 @@ <h2 id="_health">Health</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/grade-unknown.png" alt="grade unknown">
+<img src="/workshops/security_openshift/images/grade-unknown.png" alt="grade unknown"/>
 </div>
 </div>
 <div class="paragraph">
@@ -635,19 +635,19 @@ <h2 id="_health">Health</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseafc61dcf297dcad22bd6e4ab180c39e0" class="collapsed">
+      <a data-toggle="collapse" href="#collapse2f7bac2f1a191d08968e7e5bf76a2843" class="collapsed">
       
         Health for RHEL 7 Container Image
       </a>
     </h4>
   </div>
   
-  <div id="collapseafc61dcf297dcad22bd6e4ab180c39e0" class="panel-collapse collapse ">
+  <div id="collapse2f7bac2f1a191d08968e7e5bf76a2843" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/rhel7-health.png" alt="rhel7 health">
+<img src="/workshops/security_openshift/images/rhel7-health.png" alt="rhel7 health"/>
 </div>
 </div>
 
@@ -700,7 +700,7 @@ <h4 class="panel-title">
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.8/index.html b/workshops/security_openshift/exercise1.8/index.html
index c2a9c29b4..9e8958e22 100644
--- a/workshops/security_openshift/exercise1.8/index.html
+++ b/workshops/security_openshift/exercise1.8/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.8 - Red Hat Security API</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sec-api.png" alt="sec api">
+<img src="/workshops/security_openshift/images/sec-api.png" alt="sec api"/>
 </div>
 </div>
 <div class="paragraph">
@@ -346,7 +346,7 @@ <h2 id="_step_1">Step 1:</h2>
 </div>
 <div class="admonitionblock note">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <div class="title">Note</div>
 </td>
@@ -354,7 +354,7 @@ <h2 id="_step_1">Step 1:</h2>
 The <code>jq</code> utility also can clean up and propperly format json when writing to a file, other wise with out it the json would look compressed and hard to read.
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="paragraph">
 <div class="panel-group">
@@ -364,19 +364,19 @@ <h2 id="_step_1">Step 1:</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsea57585faceedde9382622981870c0ebe" class="collapsed">
+      <a data-toggle="collapse" href="#collapsee3132cc6e2cce2690696e1d6a0efc818" class="collapsed">
       
         Sample API Results
       </a>
     </h4>
   </div>
   
-  <div id="collapsea57585faceedde9382622981870c0ebe" class="panel-collapse collapse ">
+  <div id="collapsee3132cc6e2cce2690696e1d6a0efc818" class="panel-collapse collapse ">
   
     <div class="panel-body">
        <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">curl https://access.redhat.com/labs/securitydataapi/cvrf.json | jq '.'
+<pre class="highlight"><code class="language-bash" data-lang="bash">curl https://access.redhat.com/labs/securitydataapi/cvrf.json | jq &#39;.&#39;
 
 
 % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
@@ -384,92 +384,92 @@ <h4 class="panel-title">
 100           611k    0  611k    0     0   393k      0 --:--:--  0:00:01 --:--:--  392k
 [
   {
-    "RHSA": "RHSA-2017:1809",
-    "severity": "important",
-    "released_on": "2017-07-27T03:41:00+00:00",
-    "CVEs": [
-      "CVE-2017-5648",
-      "CVE-2017-5664"
+    &#34;RHSA&#34;: &#34;RHSA-2017:1809&#34;,
+    &#34;severity&#34;: &#34;important&#34;,
+    &#34;released_on&#34;: &#34;2017-07-27T03:41:00+00:00&#34;,
+    &#34;CVEs&#34;: [
+      &#34;CVE-2017-5648&#34;,
+      &#34;CVE-2017-5664&#34;
     ],
-    "bugzillas": [
-      "1441223",
-      "1459158"
+    &#34;bugzillas&#34;: [
+      &#34;1441223&#34;,
+      &#34;1459158&#34;
     ],
-    "released_packages": [
-      "tomcat-0:7.0.69-12.el7_3"
+    &#34;released_packages&#34;: [
+      &#34;tomcat-0:7.0.69-12.el7_3&#34;
     ],
-    "oval": {
-      "has_oval": true,
-      "resource_url": "https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809/oval.json"
+    &#34;oval&#34;: {
+      &#34;has_oval&#34;: true,
+      &#34;resource_url&#34;: &#34;https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809/oval.json&#34;
     },
-    "resource_url": "https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809.json"
+    &#34;resource_url&#34;: &#34;https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809.json&#34;
   },
   {
-    "RHSA": "RHSA-2017:1809",
-    "severity": "important",
-    "released_on": "2017-07-27T03:41:00+00:00",
-    "CVEs": [
-      "CVE-2017-5648",
-      "CVE-2017-5664"
+    &#34;RHSA&#34;: &#34;RHSA-2017:1809&#34;,
+    &#34;severity&#34;: &#34;important&#34;,
+    &#34;released_on&#34;: &#34;2017-07-27T03:41:00+00:00&#34;,
+    &#34;CVEs&#34;: [
+      &#34;CVE-2017-5648&#34;,
+      &#34;CVE-2017-5664&#34;
     ],
-    "bugzillas": [
-      "1441223",
-      "1459158"
+    &#34;bugzillas&#34;: [
+      &#34;1441223&#34;,
+      &#34;1459158&#34;
     ],
-    "released_packages": [
-      "tomcat-0:7.0.69-12.el7_3"
+    &#34;released_packages&#34;: [
+      &#34;tomcat-0:7.0.69-12.el7_3&#34;
     ],
-    "oval": {
-      "has_oval": true,
-      "resource_url": "https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809/oval.json"
+    &#34;oval&#34;: {
+      &#34;has_oval&#34;: true,
+      &#34;resource_url&#34;: &#34;https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809/oval.json&#34;
     },
-    "resource_url": "https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809.json"
+    &#34;resource_url&#34;: &#34;https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1809.json&#34;
   },
   {
-    "RHSA": "RHSA-2017:1802",
-    "severity": "important",
-    "released_on": "2017-07-25T17:45:00+00:00",
-    "CVEs": [
-      "CVE-2017-5645",
-      "CVE-2017-5647",
-      "CVE-2017-5648",
-      "CVE-2017-5664"
+    &#34;RHSA&#34;: &#34;RHSA-2017:1802&#34;,
+    &#34;severity&#34;: &#34;important&#34;,
+    &#34;released_on&#34;: &#34;2017-07-25T17:45:00+00:00&#34;,
+    &#34;CVEs&#34;: [
+      &#34;CVE-2017-5645&#34;,
+      &#34;CVE-2017-5647&#34;,
+      &#34;CVE-2017-5648&#34;,
+      &#34;CVE-2017-5664&#34;
     ],
-    "bugzillas": [
-      "1443635",
-      "1441205",
-      "1441223",
-      "1459158"
+    &#34;bugzillas&#34;: [
+      &#34;1443635&#34;,
+      &#34;1441205&#34;,
+      &#34;1441223&#34;,
+      &#34;1459158&#34;
     ],
-    "released_packages": [],
-    "oval": {
-      "has_oval": false,
-      "resource_url": null
+    &#34;released_packages&#34;: [],
+    &#34;oval&#34;: {
+      &#34;has_oval&#34;: false,
+      &#34;resource_url&#34;: null
     },
-    "resource_url": "https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1802.json"
+    &#34;resource_url&#34;: &#34;https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1802.json&#34;
   },
   {
-    "RHSA": "RHSA-2017:1802",
-    "severity": "important",
-    "released_on": "2017-07-25T17:45:00+00:00",
-    "CVEs": [
-      "CVE-2017-5645",
-      "CVE-2017-5647",
-      "CVE-2017-5648",
-      "CVE-2017-5664"
+    &#34;RHSA&#34;: &#34;RHSA-2017:1802&#34;,
+    &#34;severity&#34;: &#34;important&#34;,
+    &#34;released_on&#34;: &#34;2017-07-25T17:45:00+00:00&#34;,
+    &#34;CVEs&#34;: [
+      &#34;CVE-2017-5645&#34;,
+      &#34;CVE-2017-5647&#34;,
+      &#34;CVE-2017-5648&#34;,
+      &#34;CVE-2017-5664&#34;
     ],
-    "bugzillas": [
-      "1443635",
-      "1441205",
-      "1441223",
-      "1459158"
+    &#34;bugzillas&#34;: [
+      &#34;1443635&#34;,
+      &#34;1441205&#34;,
+      &#34;1441223&#34;,
+      &#34;1459158&#34;
     ],
-    "released_packages": [],
-    "oval": {
-      "has_oval": false,
-      "resource_url": null
+    &#34;released_packages&#34;: [],
+    &#34;oval&#34;: {
+      &#34;has_oval&#34;: false,
+      &#34;resource_url&#34;: null
     },
-    "resource_url": "https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1802.json"
+    &#34;resource_url&#34;: &#34;https://access.redhat.com/labs/securitydataapi/cvrf/RHSA-2017:1802.json&#34;
   }</code></pre>
 </div>
 </div>
@@ -485,7 +485,7 @@ <h4 class="panel-title">
 <div class="listingblock">
 <div class="title">save API results to file</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl https://access.redhat.com/labs/securitydataapi/cvrf.json | jq '.' &gt; cvrf.json</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl https://access.redhat.com/labs/securitydataapi/cvrf.json | jq &#39;.&#39; &gt; cvrf.json</code></pre>
 </div>
 </div>
 <div class="listingblock">
@@ -505,7 +505,7 @@ <h4 class="panel-title">
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/vim-find.png" alt="vim find">
+<img src="/workshops/security_openshift/images/vim-find.png" alt="vim find"/>
 </div>
 </div>
 </div>
@@ -522,17 +522,17 @@ <h2 id="_step_2">Step 2:</h2>
 <div class="listingblock">
 <div class="title">CVE-2016-3703</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl https://access.redhat.com/labs/securitydataapi/cve/CVE-2016-3703 | jq '. | {severity: .threat_severity, details: .details}'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl https://access.redhat.com/labs/securitydataapi/cve/CVE-2016-3703 | jq &#39;. | {severity: .threat_severity, details: .details}&#39;</code></pre>
 </div>
 </div>
 <div class="listingblock">
 <div class="title">API response</div>
 <div class="content">
 <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">{
-  "severity": "Moderate",
-  "details": [
-    "\nRed Hat OpenShift Enterprise 3.2 and 3.1 do not properly validate the origin of a request when anonymous access is granted to a service/proxy or pod/proxy API for a specific pod, which allows remote attackers to access API credentials in the web browser localStorage via an access_token in the query parameter.\n    ",
-    "\nAn origin validation vulnerability was found in OpenShift Enterprise. An attacker could potentially access API credentials stored in a web browser's localStorage if anonymous access was granted to a service/proxy or pod/proxy API for a specific pod, and an authorized access_token was provided in the query parameter.\n    "
+  &#34;severity&#34;: &#34;Moderate&#34;,
+  &#34;details&#34;: [
+    &#34;\nRed Hat OpenShift Enterprise 3.2 and 3.1 do not properly validate the origin of a request when anonymous access is granted to a service/proxy or pod/proxy API for a specific pod, which allows remote attackers to access API credentials in the web browser localStorage via an access_token in the query parameter.\n    &#34;,
+    &#34;\nAn origin validation vulnerability was found in OpenShift Enterprise. An attacker could potentially access API credentials stored in a web browser&#39;s localStorage if anonymous access was granted to a service/proxy or pod/proxy API for a specific pod, and an authorized access_token was provided in the query parameter.\n    &#34;
   ]
 }</code></pre>
 </div>
@@ -546,12 +546,12 @@ <h2 id="_step_3">Step 3:</h2>
 <p><strong>CAT 1</strong></p>
 </div>
 <div class="paragraph">
-<p>Now we can also look just for CAT 1 severity CVE&#8217;s with this query. These might be nice to have in a system that could alert administrators to take action.</p>
+<p>Now we can also look just for CAT 1 severity CVE’s with this query. These might be nice to have in a system that could alert administrators to take action.</p>
 </div>
 <div class="listingblock">
 <div class="title">CAT 1</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl -X GET "https://access.redhat.com/labs/securitydataapi/iava.json" | jq '.[] | select(.severity == "CAT I")'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl -X GET &#34;https://access.redhat.com/labs/securitydataapi/iava.json&#34; | jq &#39;.[] | select(.severity == &#34;CAT I&#34;)&#39;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -560,7 +560,7 @@ <h2 id="_step_3">Step 3:</h2>
 <div class="listingblock">
 <div class="title">get CVE &amp; Title</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl -X GET "https://access.redhat.com/labs/securitydataapi/iava.json" | jq '.[] | select(.severity == "CAT I") | { CVE: .cvelist, "CAT 1 Name": .title }'</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">curl -X GET &#34;https://access.redhat.com/labs/securitydataapi/iava.json&#34; | jq &#39;.[] | select(.severity == &#34;CAT I&#34;) | { CVE: .cvelist, &#34;CAT 1 Name&#34;: .title }&#39;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -607,7 +607,7 @@ <h2 id="_step_3">Step 3:</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/exercise1.9/index.html b/workshops/security_openshift/exercise1.9/index.html
index aebd40f7a..7d755f5e0 100644
--- a/workshops/security_openshift/exercise1.9/index.html
+++ b/workshops/security_openshift/exercise1.9/index.html
@@ -321,7 +321,7 @@ <h1>Exercise 1.9 - Image Streams &amp; Secrets</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/secrets.png" alt="secrets">
+<img src="/workshops/security_openshift/images/secrets.png" alt="secrets"/>
 </div>
 </div>
 </div>
@@ -424,7 +424,7 @@ <h3 id="_step_2">Step 2:</h3>
 <div class="listingblock">
 <div class="title">SSO Project</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">oc new-project sso --description="Red Hat SSO" --display-name="SSO Keycloak"</code></pre>
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">oc new-project sso --description=&#34;Red Hat SSO&#34; --display-name=&#34;SSO Keycloak&#34;</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -432,7 +432,7 @@ <h3 id="_step_2">Step 2:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sso-project.png" alt="sso project">
+<img src="/workshops/security_openshift/images/sso-project.png" alt="sso project"/>
 </div>
 <div class="title">Figure 1. Click SSO Keycloak Project</div>
 </div>
@@ -463,16 +463,16 @@ <h3 id="_step_3">Step 3:</h3>
 <div class="listingblock">
 <div class="title">sso-app-secret.json</div>
 <div class="content">
-<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">"kind": "Secret", <b class="conum">(1)</b>
-"apiVersion": "v1",
-"metadata": {
-    "annotations": {
-        "description": "Default secret file with name 'jboss' and password 'mykeystorepass'"
+<pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">&#34;kind&#34;: &#34;Secret&#34;, <b class="conum">(1)</b>
+&#34;apiVersion&#34;: &#34;v1&#34;,
+&#34;metadata&#34;: {
+    &#34;annotations&#34;: {
+        &#34;description&#34;: &#34;Default secret file with name &#39;jboss&#39; and password &#39;mykeystorepass&#39;&#34;
       },
-        "name": "sso-app-secret" <b class="conum">(2)</b>
+        &#34;name&#34;: &#34;sso-app-secret&#34; <b class="conum">(2)</b>
       },
-        "data": {
-                "keystore.jks": "/u3+7QAAAAIAAAABAAAAAQAF.....&lt;snip&gt; <b class="conum">(3)</b></code></pre>
+        &#34;data&#34;: {
+                &#34;keystore.jks&#34;: &#34;/u3+7QAAAAIAAAABAAAAAQAF.....&lt;snip&gt; <b class="conum">(3)</b></code></pre>
 </div>
 </div>
 <div class="colist arabic">
@@ -518,7 +518,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sso-overview.png" alt="sso overview">
+<img src="/workshops/security_openshift/images/sso-overview.png" alt="sso overview"/>
 </div>
 <div class="title">Figure 2. SSO Keycloak Project</div>
 </div>
@@ -527,7 +527,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sso-auth.png" alt="sso auth">
+<img src="/workshops/security_openshift/images/sso-auth.png" alt="sso auth"/>
 </div>
 </div>
 <div class="paragraph">
@@ -535,7 +535,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sso-admin-console.png" alt="sso admin console">
+<img src="/workshops/security_openshift/images/sso-admin-console.png" alt="sso admin console"/>
 </div>
 </div>
 <div class="paragraph">
@@ -551,12 +551,12 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sso-main-login.png" alt="sso main login">
+<img src="/workshops/security_openshift/images/sso-main-login.png" alt="sso main login"/>
 </div>
 <div class="title">Figure 3. Red Hat SSO Login</div>
 </div>
 <div class="paragraph">
-<p>This is Red Hat&#8217;s SSO server. Red Hat Single Sign-On (RH-SSO) is based on the
+<p>This is Red Hat’s SSO server. Red Hat Single Sign-On (RH-SSO) is based on the
 Keycloak project and enables you to secure your web applications by providing
 Web single sign-on (SSO) capabilities based on popular standards such as SAML
 2.0, OpenID Connect and OAuth 2.0.</p>
@@ -594,7 +594,7 @@ <h3 id="_step_3">Step 3:</h3>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/sso-main.png" alt="sso main">
+<img src="/workshops/security_openshift/images/sso-main.png" alt="sso main"/>
 </div>
 <div class="title">Figure 4. Red Hat SSO Overview</div>
 </div>
@@ -659,7 +659,7 @@ <h3 id="_step_3">Step 3:</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/index.html b/workshops/security_openshift/index.html
index abf48ccfe..814b55b76 100644
--- a/workshops/security_openshift/index.html
+++ b/workshops/security_openshift/index.html
@@ -440,11 +440,11 @@ <h2 id="_labs">Labs</h2>
 
 </div>
 <div class="paragraph">
-<p>&lt;div class="alert alert-success"&gt;</p>
+<p>&lt;div class=&#34;alert alert-success&#34;&gt;</p>
 </div>
 <div class="literalblock">
 <div class="content">
-<pre>&lt;span class="pficon pficon-ok"&gt;&lt;/span&gt;</pre>
+<pre>&lt;span class=&#34;pficon pficon-ok&#34;&gt;&lt;/span&gt;</pre>
 </div>
 </div>
 <div class="paragraph">
@@ -477,7 +477,7 @@ <h2 id="_labs">Labs</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/index.xml b/workshops/security_openshift/index.xml
index 71ba2a82d..a3302cdf8 100644
--- a/workshops/security_openshift/index.xml
+++ b/workshops/security_openshift/index.xml
@@ -4,137 +4,92 @@
     <title>OpenShift Security Workshop on Red Hat | Public Sector</title>
     <link>/workshops/security_openshift/</link>
     <description>Recent content in OpenShift Security Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/security_openshift/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/security_openshift/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Deploy OpenShift</title>
       <link>/workshops/security_openshift/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.0/</guid>
-      <description>OpenShift v3 is a layered system designed to expose underlying Docker-formatted container image and Kubernetes concepts as accurately as possible, with a focus on easy composition of applications by a developer. For example, install Ruby, push code, and add MySQL.
-   OpenShift Step 1: Use the oc command
- These instances have been preconfigured with docker and the oc command. The oc command makes deploying OpenShift for development purposes incredibly easy.</description>
+      <description>OpenShift v3 is a layered system designed to expose underlying Docker-formatted container image and Kubernetes concepts as accurately as possible, with a focus on easy composition of applications by a developer. For example, install Ruby, push code, and add MySQL.&#xA;OpenShift Step 1: Use the oc command&#xA;These instances have been preconfigured with docker and the oc command. The oc command makes deploying OpenShift for development purposes incredibly easy. The oc cluster up command starts a OpenShift all-in-one cluster with a configured registry, router, image streams, and default templates.</description>
     </item>
-    
     <item>
       <title>Exercise 1.1 - OpenShift Templates</title>
       <link>/workshops/security_openshift/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.1/</guid>
       <description>What are OpenShift Templates A template describes a set of objects that can be parameterized and processed to produce a list of objects for creation by OpenShift Container Platform. A template can be processed to create anything you have permission to create within a project, for example services, build configurations, and deployment configurations. A template may also define a set of labels to apply to every object defined in the template.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - Linux Kernel Capabilities</title>
       <link>/workshops/security_openshift/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.2/</guid>
-      <description>Before we get into OpenShift lets explore what Linux Kernel Capabilities are and some of the steps that OpenShift has taken to remove certain capabilities by default.
-   What are Linux Capabilities? According to the capabilities man page;
- Capabilities are distinct units of privilege that can be independently enabled or disabled.
- Capabilities were added to the kernel around 15 or so years ago to try to divide up the power of root.</description>
+      <description>Before we get into OpenShift lets explore what Linux Kernel Capabilities are and some of the steps that OpenShift has taken to remove certain capabilities by default.&#xA;What are Linux Capabilities? According to the capabilities man page;&#xA;Capabilities are distinct units of privilege that can be independently enabled or disabled.&#xA;Capabilities were added to the kernel around 15 or so years ago to try to divide up the power of root.</description>
     </item>
-    
     <item>
       <title>Exercise 1.3 - SELinux</title>
       <link>/workshops/security_openshift/exercise1.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.3/</guid>
-      <description>SELinux is primarily a labeling system that assigns a label (name) to every process and system object. This allows every aspect of kernel operations to be first labeled, second classified, and then ultimately enforced by a set of rules that the provider maintains.
- BENEFITS OF RUNNING SELINUX
-   All processes and files are labeled with a type. A type defines a domain for processes, and a type for files.</description>
+      <description>SELinux is primarily a labeling system that assigns a label (name) to every process and system object. This allows every aspect of kernel operations to be first labeled, second classified, and then ultimately enforced by a set of rules that the provider maintains.&#xA;BENEFITS OF RUNNING SELINUX&#xA;All processes and files are labeled with a type. A type defines a domain for processes, and a type for files. Processes are separated from each other by running in their own domains, and SELinux policy rules define how processes interact with files, as well as how processes interact with each other.</description>
     </item>
-    
     <item>
       <title>Exercise 1.4 - Skopeo</title>
       <link>/workshops/security_openshift/exercise1.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.4/</guid>
-      <description>Skopeo is a command line utility for various operations on container images and image repositories.
- Skopeo is able to inspect a repository on a Docker registry and fetch images layers. By inspect I mean it fetches the repository&amp;#8217;s manifest and it is able to show you a docker inspect-like json output about a whole repository or a tag.
- This tool, in contrast to docker inspect, helps you gather useful information about a repository or a tag before pulling it (using disk space) - e.</description>
+      <description>Skopeo is a command line utility for various operations on container images and image repositories.&#xA;Skopeo is able to inspect a repository on a Docker registry and fetch images layers. By inspect I mean it fetches the repository’s manifest and it is able to show you a docker inspect-like json output about a whole repository or a tag.&#xA;This tool, in contrast to docker inspect, helps you gather useful information about a repository or a tag before pulling it (using disk space) - e.</description>
     </item>
-    
     <item>
       <title>Exercise 1.5 - Atomic Scanner</title>
       <link>/workshops/security_openshift/exercise1.5/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.5/</guid>
-      <description>The atomic command-line tool provides a way to interact and manage Atomic Host systems and containers. It provides a high level, coherent entrypoint to the system and makes it easier to interact with special kinds of containers, such as super-privileged containers, and debugging tools.
- The atomic command uses tools such as docker, ostree and skopeo to manage containers and container host systems. There are also a lot of features built into the atomic command that are not available in the docker command.</description>
+      <description>The atomic command-line tool provides a way to interact and manage Atomic Host systems and containers. It provides a high level, coherent entrypoint to the system and makes it easier to interact with special kinds of containers, such as super-privileged containers, and debugging tools.&#xA;The atomic command uses tools such as docker, ostree and skopeo to manage containers and container host systems. There are also a lot of features built into the atomic command that are not available in the docker command.</description>
     </item>
-    
     <item>
       <title>Exercise 1.6 - SCC &amp; Seccomp</title>
       <link>/workshops/security_openshift/exercise1.6/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.6/</guid>
       <description>In addition to authorization policies that control what a user can do, OpenShift Container Platform provides security context constraints (SCC) that control the actions that a pod can perform and what it has the ability to access. Administrators can manage SCCs using the CLI. This is a great way to lock down you individual application to make sure that they have hardened settings. This applies to applications running on OpenShift.</description>
     </item>
-    
     <item>
       <title>Exercise 1.7 - Red Hat Container Catalog</title>
       <link>/workshops/security_openshift/exercise1.7/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.7/</guid>
-      <description>Red Hat Container Catalog
-  While public registries and uncurated repositories are acceptable for some cloud-native development and proof-of-concept projects, they do not always provide content that is fit for production consumption; enterprise workloads require enterprise-ready tools.   MATTHEW HICKSVICE PRESIDENT, ENGINEERING, OPENSHIFT AND MANAGEMENT, RED HAT
- While container-based applications have begun moving into production, not all containers are created or maintained equally. Every container starts with a Linux base layer, which means that every ISV building container images is distributing Linux content.</description>
+      <description>Red Hat Container Catalog&#xA;While public registries and uncurated repositories are acceptable for some cloud-native development and proof-of-concept projects, they do not always provide content that is fit for production consumption; enterprise workloads require enterprise-ready tools. MATTHEW HICKSVICE PRESIDENT, ENGINEERING, OPENSHIFT AND MANAGEMENT, RED HAT&#xA;While container-based applications have begun moving into production, not all containers are created or maintained equally. Every container starts with a Linux base layer, which means that every ISV building container images is distributing Linux content.</description>
     </item>
-    
     <item>
       <title>Exercise 1.8 - Red Hat Security API</title>
       <link>/workshops/security_openshift/exercise1.8/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.8/</guid>
-      <description>Red Hat Product Security is committed to providing tools and security data to help you better understand security threats. This data has been available on our Security Data page and will now also be available in a machine-consumable format with the Security Data API. This tool will allow customers to programmatically query the API for data that was previously exposed only through files on our Security Data page.</description>
+      <description>Red Hat Product Security is committed to providing tools and security data to help you better understand security threats. This data has been available on our Security Data page and will now also be available in a machine-consumable format with the Security Data API. This tool will allow customers to programmatically query the API for data that was previously exposed only through files on our Security Data page.&#xA;The data provided by the Security Data API is the same as what is found on the Security Data page: OVAL definitions, Common Vulnerability Reporting Framework (CVRF) documents and CVE data.</description>
     </item>
-    
     <item>
       <title>Exercise 1.9 - Image Streams &amp; Secrets</title>
       <link>/workshops/security_openshift/exercise1.9/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/exercise1.9/</guid>
-      <description>Image Stream Image streams can be used to automatically perform an action when new images are created. Builds and deployments can watch an image stream to receive notifications when new images are added and react by performing a build or deployment, respectively.
- For example, if a deployment is using a certain image and a new version of that image is created, a deployment could be automatically performed.</description>
+      <description>Image Stream Image streams can be used to automatically perform an action when new images are created. Builds and deployments can watch an image stream to receive notifications when new images are added and react by performing a build or deployment, respectively.&#xA;For example, if a deployment is using a certain image and a new version of that image is created, a deployment could be automatically performed.&#xA;Secrets A Secret is an object that contains a small amount of sensitive data such as a password, a token, or a key.</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/security_openshift/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/setup/</guid>
-      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for the workshopname.
- https://&amp;lt;workshopname&amp;gt;.master.&amp;lt;student number&amp;gt;.redhatgov.io:8888   After logging in, you should see a shell.</description>
+      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for the workshopname.&#xA;https://&amp;lt;workshopname&amp;gt;.master.&amp;lt;student number&amp;gt;.redhatgov.io:8888 After logging in, you should see a shell.&#xA;Figure 1: wetty Important Be sure you can log in to your instances.</description>
     </item>
-    
     <item>
       <title>Wrap Up</title>
       <link>/workshops/security_openshift/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/security_openshift/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about OpenShift Security that you can apply in your daily role.
- What do you think? How can we help you understand OpenShift Security better?
- Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your OpenShift education.
- This Participant Guide will remain active for the next two weeks.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about OpenShift Security that you can apply in your daily role.&#xA;What do you think? How can we help you understand OpenShift Security better?&#xA;Before you leave, check out the Resources page that is part of this guide. There you can find a ton of links that will further your OpenShift education.&#xA;This Participant Guide will remain active for the next two weeks.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/security_openshift/setup/index.html b/workshops/security_openshift/setup/index.html
index f746d345d..c095fd9e7 100644
--- a/workshops/security_openshift/setup/index.html
+++ b/workshops/security_openshift/setup/index.html
@@ -317,7 +317,7 @@ <h1>Setup</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/container-lab.001.png" alt="Red Hat" width="1000">
+<img src="/workshops/security_openshift/images/container-lab.001.png" alt="Red Hat" width="1000"/>
 </div>
 </div>
 </div>
@@ -346,21 +346,21 @@ <h2 id="_accessing_wetty">Accessing Wetty</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/security_openshift/images/wetty.png" alt="wetty" height="500">
+<img src="/workshops/security_openshift/images/wetty.png" alt="wetty" height="500"/>
 </div>
 <div class="title">Figure 1: wetty</div>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <div class="title">Important</div>
 </td>
 <td class="content">
-Be sure you can log in to your instances.  If you can&#8217;t log in start shouting, loudly, and waving your hands!
+Be sure you can log in to your instances.  If you can’t log in start shouting, loudly, and waving your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -368,7 +368,7 @@ <h2 id="_accessing_wetty">Accessing Wetty</h2>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, everyone should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, everyone should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 </div>
 </div>
@@ -407,7 +407,7 @@ <h2 id="_end_result">End Result</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/security_openshift/wrapup/index.html b/workshops/security_openshift/wrapup/index.html
index cd566a6a5..b45bbbae9 100644
--- a/workshops/security_openshift/wrapup/index.html
+++ b/workshops/security_openshift/wrapup/index.html
@@ -314,7 +314,7 @@ <h1>Wrap Up</h1>
 </nav>
 
     <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something
+<p>That wraps up what we have planned for today.  We hope you’ve learned something
 valuable about OpenShift Security that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
@@ -367,7 +367,7 @@ <h1>Wrap Up</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise1.0/index.html b/workshops/selinux_policy/exercise1.0/index.html
index bb0e7a1d8..bdcf96e04 100644
--- a/workshops/selinux_policy/exercise1.0/index.html
+++ b/workshops/selinux_policy/exercise1.0/index.html
@@ -310,7 +310,7 @@ <h1>Exercise 1.0 - Introduction to Security Enhanced Linux (SELinux)</h1>
     
     
     <li class="next">
-      <a href="/workshops/selinux_policy/exercise1.1/">Next: Exercise 1.1 - Introduction to SELinux &rarr;</a>
+      <a href="/workshops/selinux_policy/exercise1.1/">Next: Exercise 1.1 - SELinux policy in RHEL &rarr;</a>
     </li>
     
     
@@ -321,28 +321,37 @@ <h1>Exercise 1.0 - Introduction to Security Enhanced Linux (SELinux)</h1>
 <h2 id="_history">History</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>In this exercise, we are going to introduce you to Security Enhanced Linux, commonly known as <code>SELinux</code>.</p>
+<p>In this workshop, we are going to introduce you to Security Enhanced Linux, commonly known as <code>SELinux</code>.</p>
+</div>
+<div class="paragraph">
+<p>Standard Linux access policy based on the user, group, and other permissions, known as Discretionary Access Control (DAC), does not enable system administrators to create comprehensive and fine-grained security policies, such as restricting specific applications to only viewing log files, while allowing other applications to append new data to the log files.</p>
 </div>
 <div class="paragraph">
 <p>SELinux is an implementation of the <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/sect-security-enhanced_linux-further_information-other_resources">Flask</a> system security architecture.  The Flask architecture implements MAC, which focuses on providing an administratively-defined security policy that can control all subjects and objects, basing decisions on all security-relevant information. In addition, Flask focuses on the concept of least privilege, which gives a process exactly the rights it needs to perform its given task.</p>
 </div>
 <div class="paragraph">
-<p>The Flask model allows you to express a security policy in a naturally flowing manner, so that parts of the security rules are like parts in a sentence. In Flask, changes are supported so you can tune your policy. Added to this architecture in the security server are type enforcement (TE) and robe-based access control (RBAC) security models, providing fine-grained controls that can be transparent to users and applications.</p>
+<p>The Flask model allows you to express a security policy in a naturally flowing manner, so that parts of the security rules are like parts in a sentence. In Flask, changes are supported so you can tune your policy. Added to this architecture in the security server are <strong>type enforcement</strong> (TE) and role-based access control (RBAC) security models, providing fine-grained controls that can be transparent to users and applications.</p>
 </div>
 <div class="paragraph">
 <p>As a next step in the evolution of SELinux, the NSA integrated SELinux into the Linux kernel using the Linux Security Modules (LSM) framework. SELinux motivated the creation of LSM, at the suggestion of Linus Torvalds, who wanted a modular approach to security instead of accepting just SELinux into the kernel.</p>
 </div>
+<div class="sect2">
+<h3 id="_what_enables_selinux_to_make_access_decisions">What enables SELinux to make access decisions?</h3>
 <div class="paragraph">
-<p>Originally, the SELinux implementation used persistent security IDs (PSIDs) stored in an unused field of the ext2 inode. These numerical representations (i.e., non-human-readable) were mapped by SELinux to a security context label. Unfortunately, this required modifying each file system type to support PSIDs, so was not a scalable solution or one that would be supported upstream in the Linux kernel.</p>
+<p>In short, everything on the system is labeled with a security context:  Files, Directories, Memory, Sockets, TCP/UDP ports and more.</p>
 </div>
 <div class="paragraph">
-<p>The next evolution of SELinux was as a loadable kernel module for the 2.4.&lt;x&gt; series of Linux kernels. This module stored PSIDs in a normal file, and SELinux was able to support more file systems. This solution was not optimal for performance, and was inconsistent across platforms. Finally, the SELinux code was integrated upstream to the 2.6.x kernel, which has full support for LSM and has extended attributes (xattrs) in the ext3 file system. SELinux was moved to using xattrs to store security context information. The xattr namespace provides useful separation for multiple security modules existing on the same system.</p>
+<p>Originally, for files, the SELinux implementation used persistent security IDs (PSIDs) stored in an unused field of the ext2 inode. These numerical representations (i.e., non-human-readable) were mapped by SELinux to a security context label. Unfortunately, this required modifying each file system type to support PSIDs, so was not a scalable solution or one that would be supported upstream in the Linux kernel.</p>
+</div>
+<div class="paragraph">
+<p>The next evolution of SELinux was as a loadable kernel module for the 2.4.&lt;x&gt; series of Linux kernels. This module stored PSIDs in a normal file, and SELinux was able to support more file systems. This solution was not optimal for performance, and was inconsistent across platforms. Finally, the SELinux code was integrated upstream to the 2.6.x kernel, which has full support for LSM and has <strong>extended attributes</strong> (xattrs) in the ext3 file system. SELinux was moved to using xattrs to store security context information. The xattr namespace provides useful separation for multiple security modules existing on the same system.</p>
 </div>
 <div class="paragraph">
 <p>Much of the work to get the kernel ready for upstream, as well as subsequent SELinux development, has been a joint effort between the NSA, Red Hat, and the community of SELinux developers.</p>
 </div>
 </div>
 </div>
+</div>
 <div class="sect1">
 <h2 id="_thanks">Thanks</h2>
 <div class="sectionbody">
@@ -374,7 +383,7 @@ <h2 id="_thanks">Thanks</h2>
     
     
     <li class="next">
-      <a href="/workshops/selinux_policy/exercise1.1/">Next: Exercise 1.1 - Introduction to SELinux &rarr;</a>
+      <a href="/workshops/selinux_policy/exercise1.1/">Next: Exercise 1.1 - SELinux policy in RHEL &rarr;</a>
     </li>
     
     
@@ -390,7 +399,7 @@ <h2 id="_thanks">Thanks</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise1.1/index.html b/workshops/selinux_policy/exercise1.1/index.html
index 4f2912650..1385add14 100644
--- a/workshops/selinux_policy/exercise1.1/index.html
+++ b/workshops/selinux_policy/exercise1.1/index.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
 
-    <title>Exercise 1.1 - Introduction to SELinux | Red Hat | Public Sector</title>
+    <title>Exercise 1.1 - SELinux policy in RHEL | Red Hat | Public Sector</title>
 
     
     
@@ -279,7 +279,7 @@
 
 
 <div class="jumbotron jumbotron-page text-center">
-  <h1>Exercise 1.1 - Introduction to SELinux</h1>
+  <h1>Exercise 1.1 - SELinux policy in RHEL</h1>
 </div>
 
 <div class="container">
@@ -317,206 +317,92 @@ <h1>Exercise 1.1 - Introduction to SELinux</h1>
   </ul>
 </nav>
 
-    <div class="sect1">
-<h2 id="_exercise_description">Exercise Description</h2>
+    <div id="preamble">
 <div class="sectionbody">
 <div class="paragraph">
-<p>To better understand SELinux basic concepts, see the following documentation:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p><a href="https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf">The SELinux Coloring Book</a></p>
-</li>
-<li>
-<p><a href="http://selinuxproject.org/page/FAQ">SELinux Wiki FAQ</a></p>
-</li>
-<li>
-<p><a href="http://freecomputerbooks.com/books/The_SELinux_Notebook-4th_Edition.pdf">The SELinux Notebook</a></p>
-</li>
-</ul>
-</div>
-<div class="sect2">
-<h3 id="_step_1_become_root">Step 1: Become root</h3>
-<div class="paragraph">
-<p>First, go ahead and switch users to root:</p>
-</div>
-<div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo -i</code></pre></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_step_2_what_mode_are_we_in">Step 2: What mode are we in?</h3>
-<div class="paragraph">
-<p>Next, let&#8217;s check to see what SELinux mode your host is in:</p>
-</div>
-<div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">getenforce</code></pre></div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">Enforcing</code></pre>
+<p>What are policies?  A policy is a real-world application of SELinux controls.  This chapter is an overview and examination of SELinux policy for Red Hat Enterprise Linux.</p>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_3_changing_modes">Step 3: Changing modes</h3>
-<div class="paragraph">
-<p>Now, we can change the mode that your host is in:</p>
-</div>
+<h3 id="_what_is_the_targeted_policy">What is the Targeted Policy?</h3>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">setenforce <span style="color:#ae81ff">0</span>
-getenforce</code></pre></div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">Permissive</code></pre>
-</div>
+<p>The SELinux policy is highly configurable. Starting with Red Hat Enterprise Linux 5, Red Hat defaulted to the <strong>targeted policy</strong>. The goal of this policy is to lock down all processes that listen for network connections and pretty much all processes that start at boot.  Under the targeted policy, every subject and object runs in the unconfined_t domain except for the specific targeted daemons. Objects that are in the unconfined_t domain have no restrictions and fall back to using standard Linux security, that is, DAC. The daemons secured by the targeted policy run in their own domains and are restricted via type enforcement in every operation they perform on the system. This way daemons that are exploited or compromised in any way are contained and can only cause limited damage.</p>
 </div>
 <div class="paragraph">
-<p>And we can change it back:</p>
+<p>For example, the http and ntp daemons are both protected in the default targeted policy, and run in the httpd_t and ntpd_t domains, respectively. The ssh daemon, however, is not protected in this policy, and consequently runs in the unconfined_t domain.  The targeted daemons include most common system daemons (dhcpd, httpd, mysqld, named, nscd, ntpd, portmap, postgres, snmpd, squid, syslogd, and winbind) and the list grows with each RHEL generation.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">setenforce <span style="color:#ae81ff">1</span>
-getenforce</code></pre></div>
+<p>Refer to the following sample output, which illustrates the various domains for the daemons mentioned above:</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">Enforcing</code></pre>
+<pre class="highlight"><code>user_u:system_r:httpd_t         25129 ?        00:00:00 httpd
+user_u:system_r:ntpd_t          25176 ?        00:00:00 ntpd
+system_u:system_r:unconfined_t         25245 ? 00:00:00 sshd</code></pre>
 </div>
 </div>
+<div class="sect3">
+<h4 id="_additional_policies_are_available">Additional policies are available:</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Multi-level security (MLS)</p>
+</li>
+<li>
+<p>Minimum</p>
+</li>
+<li>
+<p>Sandbox</p>
+</li>
+</ul>
 </div>
-<div class="sect2">
-<h3 id="_step_4_changing_modes_for_specific_domains">Step 4: Changing modes for specific domains</h3>
 <div class="paragraph">
-<p>You can also set individual SELinux domains (like <code>httpd_t</code>, which controls web server access control) to permissve mode:</p>
+<p>The <strong>MLS</strong> SELinux policy applies a modified principle called Bell-La Padula with write equality. This means that users can read files at their own sensitivity level and lower, but can write only at exactly their own level. This prevents, for example, low-clearance users from writing content into top-secret files.  MLS is the most strict policy and is rarely used in practice.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">semanage permissive -a httpd_t
-semanage permissive -l</code></pre></div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">Builtin Permissive Types
-
-Customized Permissive Types
-
-httpd_t</code></pre>
-</div>
+<p><strong>Minimum</strong> policy is built exactly the same as targeted policy, but installs ONLY the base policy package and the unconfined.pp.  All of the SELinux policy modules from the targeted policy are in the selinux-policy-minimum rpm package but they are not compiled and loaded into the kernel in the post install.</p>
 </div>
 <div class="paragraph">
-<p>And again, we can change it back:</p>
+<p><strong>Sandbox</strong> is a special-purpose policy and utility primarily for testing.  The sandbox security utility adds a set of SELinux policies that allow a system administrator to run an application within a tightly confined SELinux domain. Restrictions on permission to open new files or access to the network can be defined. This enables testing the processing characteristics of untrusted software securely, without risking damage to the system.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">semanage permissive -d httpd_t</code></pre></div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">libsemanage.semanage_direct_remove_key: Removing last permissive_httpd_t module (no other permissive_httpd_t module exists at another priority).</code></pre>
-</div>
+<p>We are only working with Targeted Policy in this workshop.</p>
 </div>
-<div class="paragraph">
-<p>The <code>permissive</code> mode means that either the entire system (the first example) or the specific application constrained by a type (the second example) are allowed to bypass SELinux access controls.  However, even though access controls are disabled, full AVC (access vector cache, where SELinux stores its decisions) logging still happens.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_5_selinux_logging">Step 5: SELinux logging</h3>
-<div class="paragraph">
-<p>SELinux messages are logged to the <code>/var/log/audit/audit.log</code> file.  We can read the messages with this command:</p>
-</div>
-<div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m MAC_POLICY_LOAD -i --just-one</code></pre></div>
-</div>
-<div class="paragraph">
-<p>We have asked the <code>ausearch</code> utility to look for SELinux policies being loaded (<code>-m MAC_POLICY_LOAD</code>), to make the result human-readable (<code>-i</code>), and to return only a single result (<code>--just-one</code>):</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">----
-type=PROCTITLE msg=audit(05/17/2019 23:47:54.147:1896) : proctitle=/sbin/load_policy
-type=SYSCALL msg=audit(05/17/2019 23:47:54.147:1896) : arch=x86_64 syscall=write success=yes exit=3857474 a0=0x4 a1=0x7fb57e597000 a2=0x3adc42 a3=0x7ffc8bb993a0 items=0 ppid=16567 pid=16572 auid=ec2-user uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=pts0 ses=1 comm=load_policy exe=/usr/sbin/load_policy subj=unconfined_u:unconfined_r:load_policy_t:s0-s0:c0.c1023 key=(null)
-type=MAC_POLICY_LOAD msg=audit(05/17/2019 23:47:54.147:1896) : auid=ec2-user ses=1 lsm=selinux res=yes</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Other useful searches include:</p>
-</div>
+<h3 id="_additional_reminders">Additional reminders</h3>
 <div class="ulist">
 <ul>
 <li>
-<p>all denials:</p>
+<p>SELinux policy is consulted after normal DAC controls.  So if DAC permissions already deny a particular access to a file, no further evaluations are done.</p>
 </li>
-</ul>
-</div>
-<div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m avc,user_avc,selinux_err,user_selinux_err</code></pre></div>
-</div>
-<div class="ulist">
-<ul>
 <li>
-<p>denials from today:</p>
+<p>SELinux is a &#34;default deny&#34; system.  Thus, that which is not explicitly permitted is denied.</p>
 </li>
 </ul>
 </div>
+</div>
+<div class="sect2">
+<h3 id="_to_learn_more">To learn more</h3>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m avc -ts today</code></pre></div>
+<p>To better understand SELinux basic concepts, see the following resources:</p>
 </div>
 <div class="ulist">
 <ul>
 <li>
-<p>denials from the last 10 minutes:</p>
+<p><a href="https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf">The SELinux Coloring Book</a></p>
+</li>
+<li>
+<p><a href="http://selinuxproject.org/page/FAQ">SELinux Wiki FAQ</a></p>
+</li>
+<li>
+<p><a href="http://freecomputerbooks.com/books/The_SELinux_Notebook-4th_Edition.pdf">The SELinux Notebook</a></p>
 </li>
 </ul>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m avc -ts recent</code></pre></div>
-</div>
-<div class="paragraph">
-<p>You can try these, if you like, but they may or may not return any results.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_step_6_interpreting_avcs">Step 6: Interpreting AVCs</h3>
-<div class="paragraph">
-<p>If you use <code>ausearch</code> to find AVC messages, you can see exactly what caused SELinux to deny access:</p>
-</div>
-<div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -if ./testaudit -m AVC</code></pre></div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">----
-time-&gt;Mon Nov 17 00:45:36 2008
-type=SYSCALL msg=audit(1226882736.442:86): arch=40000003 syscall=196 success=no exit=-13 a0=b9a1e198 a1=bfc2921c a2=54dff4 a3=2008171 items=0 ppid=2425 pid=2427 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
-type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Here, we can see that the <code>httpd</code> process, ID <code>2427</code>, was disallowed from checking attributes of the file <code>/var/www/html/file1</code>.  Additionally, we can see that the domain of the process was <code>httpd_t</code>, and the file was labeled with the <code>samba_share_t</code> context.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_step_7_getting_advice">Step 7: Getting advice</h3>
-<div class="paragraph">
-<p>There is a neat utility called <code>audit2why</code>, which can make suggestions as to how you might solve SELinux AVC messages.  Let&#8217;s try it on our test error:</p>
-</div>
-<div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -if ./testaudit -m AVC | audit2why</code></pre></div>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
-
-	Was caused by:
-		Missing type enforcement (TE) allow rule.
-
-		You can use audit2allow to generate a loadable module to allow this access.</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>The <code>audit2why</code> utility is telling us that the problem was caused by a missing <code>allow</code> rule, which would grant access for <code>httpd_t</code> processes to <code>samba_share_t</code> files.  This is obviously not the whole story, in this case, but it points us to the problem of the file&#8217;s context being incorrect.</p>
-</div>
-<div class="paragraph">
 <style>
 
  
@@ -616,7 +502,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -876,7 +762,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -988,7 +874,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -998,7 +884,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1044,8 +930,6 @@ <h3>Workshop Details</h3>
 
 </div>
 </div>
-</div>
-</div>
 
 
     
@@ -1085,7 +969,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise1.2/index.html b/workshops/selinux_policy/exercise1.2/index.html
index c2ae811c2..6f6b0b27b 100644
--- a/workshops/selinux_policy/exercise1.2/index.html
+++ b/workshops/selinux_policy/exercise1.2/index.html
@@ -303,14 +303,14 @@ <h1>Exercise 1.2 - SELinux Contexts</h1>
     
     
     <li class="previous">
-      <a href="/workshops/selinux_policy/exercise1.1/">&larr; Previous: Exercise 1.1 - Introduction to SELinux</a>
+      <a href="/workshops/selinux_policy/exercise1.1/">&larr; Previous: Exercise 1.1 - SELinux policy in RHEL</a>
     </li>
     
     
     
     
     <li class="next">
-      <a href="/workshops/selinux_policy/exercise2.0/">Next: Exercise 2.0 - Creating Custom SELinux Policy &rarr;</a>
+      <a href="/workshops/selinux_policy/exercise1.3/">Next: Exercise 1.3 - Altering behavior &rarr;</a>
     </li>
     
     
@@ -321,15 +321,38 @@ <h1>Exercise 1.2 - SELinux Contexts</h1>
 <h2 id="_exercise_description">Exercise Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>All processes and files are labeled with an SELinux context.  The context contains information that SELinux needs to make control decisions.  Contexts contain user, role, type, and level information,</p>
+<p>Let’s peer under the hood a bit to see how SELinux works.
+All processes and files are labeled with an SELinux context; contexts contain user, role, type, and level information.  This is information that SELinux needs to enforce the active policy (eg, make access decisions).  But where do files and directories get their contexts?</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Contexts are set when files are created, based on their parent directory’s context (with a few exceptions)</p>
+</li>
+<li>
+<p>Packages can set contexts as part of installation</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Let’s take a closer look at contexts.</p>
 </div>
 <div class="sect2">
-<h3 id="_step_1_examine_a_context">Step 1: Examine a context</h3>
+<h3 id="_step_1_become_root">Step 1: Become root</h3>
 <div class="paragraph">
-<p>To get started, let&#8217;s check the context of a file in the <code>ec2-user</code> user&#8217;s home directory:</p>
+<p>First, go ahead and switch users to root; we’ll remain in the root shell for the remainder of Exercise 1:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ls -Z ~ec2-user/.vimrc</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo -i</span></span></code></pre></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_2_examine_a_context">Step 2: Examine a context</h3>
+<div class="paragraph">
+<p>To get started, let’s check the context of a file in the <code>ec2-user</code> user’s home directory:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ls -Z ~ec2-user/.vimrc</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -347,13 +370,13 @@ <h3 id="_step_1_examine_a_context">Step 1: Examine a context</h3>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_2_domain_transitions">Step 2: Domain transitions</h3>
+<h3 id="_step_3_domain_transitions">Step 3: Domain transitions</h3>
 <div class="paragraph">
-<p>To demonstrate the difference between confined and unconfined processes, let&#8217;s launch an application which doesn&#8217;t have a defined domain transition:</p>
+<p>To demonstrate the difference between confined and unconfined processes, let’s launch an application which doesn’t have a defined domain transition:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">yes &gt;/dev/null &amp;
-ps -Z | grep yes</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>yes &gt;/dev/null &amp;
+</span></span><span style="display:flex;"><span>ps -Z | grep yes</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -367,10 +390,10 @@ <h3 id="_step_2_domain_transitions">Step 2: Domain transitions</h3>
 <p>On the other hand, if we launch the <code>passwd</code> utility, we will see a different story:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">kill %1
-ps -Z | grep yes
-passwd ec2-user &gt;/dev/null &amp;
-ps -Z | grep passwd</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>kill %1
+</span></span><span style="display:flex;"><span>ps -Z | grep yes
+</span></span><span style="display:flex;"><span>passwd ec2-user &gt;/dev/null &amp;
+</span></span><span style="display:flex;"><span>ps -Z | grep passwd</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -383,26 +406,26 @@ <h3 id="_step_2_domain_transitions">Step 2: Domain transitions</h3>
 <p>See that the third field is <code>passwd_t</code>, indicating that the <code>passwd</code> process has been confined by the <code>passwd_t</code> domain.</p>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s kill that hanging <code>passwd</code> process, and move on:</p>
+<p>Let’s kill that hanging <code>passwd</code> process, and move on:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">kill %1</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>kill %1</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>This changing of the context, when an application in SELinux&#8217;s ruleset is launched, is called a <code>domain transition</code>.</p>
+<p>This changing of the context, when an application in SELinux’s ruleset is launched, is called a <code>domain transition</code>.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_3_useful_utility_1_restorecon">Step 3: Useful utility #1: restorecon</h3>
+<h3 id="_step_4_useful_utility_1_restorecon">Step 4: Useful utility #1: restorecon</h3>
 <div class="paragraph">
-<p>If I had to suggest to a new SELinux user the one thing that they should remember (no, it&#8217;s not <code>setenforce 0</code>!), it&#8217;d be <code>restorecon</code>.  Restorecon will reset the SELinux context to what is defined in the system&#8217;s context database.</p>
+<p>If I had to suggest to a new SELinux user the one thing that they should remember (no, it’s not <code>setenforce 0</code>!), it’d be <code>restorecon</code>.  Restorecon will reset the SELinux context to what is defined in the system’s context database.</p>
 </div>
 <div class="paragraph">
-<p>To try this out, let&#8217;s purposefully set the context incorrectly on our example SELinux AVC log:</p>
+<p>To try this out, let’s purposefully set the context incorrectly on our example SELinux AVC log:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">chcon -t httpd_sys_content_t ./testaudit
-ls -Z ./testaudit</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>chcon -t httpd_sys_content_t ./testaudit
+</span></span><span style="display:flex;"><span>ls -Z ./testaudit</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -410,11 +433,11 @@ <h3 id="_step_3_useful_utility_1_restorecon">Step 3: Useful utility #1: restorec
 </div>
 </div>
 <div class="paragraph">
-<p>And we can change it back, magically, with restorecon.  Note that this would have fixed the problem reported in our test AVC, by setting the context to <code>httpd_sys_content_t</code>:</p>
+<p>And we can change it back, magically, with restorecon:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">restorecon -v ./testaudit
-ls -Z ./testaudit</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>restorecon -v ./testaudit
+</span></span><span style="display:flex;"><span>ls -Z ./testaudit</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -424,7 +447,7 @@ <h3 id="_step_3_useful_utility_1_restorecon">Step 3: Useful utility #1: restorec
 </div>
 </div>
 <div class="paragraph">
-<p>I also slipped in <code>chcon</code>, which you can use to temporarily change the context on a file.</p>
+<p>I also slipped in <code>chcon</code>, which you can use to temporarily change the context on a file.  You’ll get to use several other SELinux CLI tools throughout the day.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -526,7 +549,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -786,7 +809,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -898,7 +921,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -908,7 +931,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -972,14 +995,14 @@ <h3>Workshop Details</h3>
     
     
     <li class="previous">
-      <a href="/workshops/selinux_policy/exercise1.1/">&larr; Previous: Exercise 1.1 - Introduction to SELinux</a>
+      <a href="/workshops/selinux_policy/exercise1.1/">&larr; Previous: Exercise 1.1 - SELinux policy in RHEL</a>
     </li>
     
     
     
     
     <li class="next">
-      <a href="/workshops/selinux_policy/exercise2.0/">Next: Exercise 2.0 - Creating Custom SELinux Policy &rarr;</a>
+      <a href="/workshops/selinux_policy/exercise1.3/">Next: Exercise 1.3 - Altering behavior &rarr;</a>
     </li>
     
     
@@ -995,7 +1018,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise1.3/index.html b/workshops/selinux_policy/exercise1.3/index.html
new file mode 100644
index 000000000..bdceb875c
--- /dev/null
+++ b/workshops/selinux_policy/exercise1.3/index.html
@@ -0,0 +1,1035 @@
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <meta charset="utf-8" />
+    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+    <title>Exercise 1.3 - Altering behavior | Red Hat | Public Sector</title>
+
+    
+    
+    <link rel="stylesheet" href="/node_modules/patternfly/dist/css/patternfly.min.css" />
+    <link rel="stylesheet" href="/node_modules/patternfly/dist/css/patternfly-additions.min.css" />
+
+    
+    <link rel="stylesheet" href="/node_modules/highlight.js/styles/darkula.css" />
+
+    
+    <link rel="stylesheet" href="/css/main.css" />
+    <link rel="stylesheet" href="/css/asciidoc.css" />
+    <link rel="stylesheet" href="/css/custom.css" />
+    <link rel="stylesheet" href="/css/toastr.min.css" />
+
+    
+    <script async src="https://www.googletagmanager.com/gtag/js?id=G-DL741MBBZQ"></script>
+    <script>
+      window.dataLayer = window.dataLayer || [];
+      function gtag(){dataLayer.push(arguments);}
+      gtag('js', new Date());
+
+      gtag('config', 'G-DL741MBBZQ');
+    </script>
+
+    
+    <script id="adobe_dtm" src="//www.redhat.com/dtm.js" type="text/javascript"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/jquery/dist/jquery.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap/dist/js/bootstrap.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/c3/c3.min.js"></script>
+    <script src="/node_modules/patternfly/node_modules/d3/d3.min.js"></script>
+
+    
+    
+    <script src="/node_modules/patternfly/node_modules/datatables/media/js/jquery.dataTables.min.js"></script>
+    <script src="/node_modules/patternfly/node_modules/drmonty-datatables-colvis/js/dataTables.colVis.js"></script>
+    <script src="/node_modules/patternfly/node_modules/datatables.net-colreorder/js/dataTables.colReorder.js"></script>
+
+    
+    
+    <script src="/node_modules/patternfly/dist/js/patternfly.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/patternfly-bootstrap-combobox/js/bootstrap-combobox.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-datepicker/dist/js/bootstrap-datepicker.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/moment/min/moment.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/eonasdan-bootstrap-datetimepicker/build/js/bootstrap-datetimepicker.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-select/dist/js/bootstrap-select.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-switch/dist/js/bootstrap-switch.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-touchspin/dist/jquery.bootstrap-touchspin.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/patternfly-bootstrap-treeview/dist/bootstrap-treeview.min.js"></script>
+
+    
+    <script src="https://cdn.rawgit.com/google/code-prettify/master/loader/run_prettify.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/jquery-match-height/dist/jquery.matchHeight-min.js"></script>
+    
+    <script src="/js/clipboard.min.js"></script>
+    <script src="/js/clip.js"></script>
+
+    
+    <script src="/js/toastr.min.js"></script>
+
+    
+    <script src="/node_modules/highlight.js/lib/highlight.js"></script>
+    <script>hljs.initHighlightingOnLoad();</script>
+  </head>
+  <body class="">
+    
+
+<nav class="navbar navbar-default navbar-inverse navbar-fixed-top " role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse-1">
+        <span class="sr-only">Toggle navigation</span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="/">
+      <svg width=150 height=auto id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 613 145"><defs><style>.cls-1{fill:#e00;}.cls-2{fill:#fff;}</style></defs><path class="cls-1" d="M127.47,83.49c12.51,0,30.61-2.58,30.61-17.46a14,14,0,0,0-.31-3.42l-7.45-32.36c-1.72-7.12-3.23-10.35-15.73-16.6C124.89,8.69,103.76.5,97.51.5,91.69.5,90,8,83.06,8c-6.68,0-11.64-5.6-17.89-5.6-6,0-9.91,4.09-12.93,12.5,0,0-8.41,23.72-9.49,27.16A6.43,6.43,0,0,0,42.53,44c0,9.22,36.3,39.45,84.94,39.45M160,72.07c1.73,8.19,1.73,9.05,1.73,10.13,0,14-15.74,21.77-36.43,21.77C78.54,104,37.58,76.6,37.58,58.49a18.45,18.45,0,0,1,1.51-7.33C22.27,52,.5,55,.5,74.22c0,31.48,74.59,70.28,133.65,70.28,45.28,0,56.7-20.48,56.7-36.65,0-12.72-11-27.16-30.83-35.78"/><path d="M160,72.07c1.73,8.19,1.73,9.05,1.73,10.13,0,14-15.74,21.77-36.43,21.77C78.54,104,37.58,76.6,37.58,58.49a18.45,18.45,0,0,1,1.51-7.33l3.66-9.06A6.43,6.43,0,0,0,42.53,44c0,9.22,36.3,39.45,84.94,39.45,12.51,0,30.61-2.58,30.61-17.46a14,14,0,0,0-.31-3.42Z"/><path class="cls-2" d="M579.74,92.8c0,11.89,7.15,17.67,20.19,17.67a52.11,52.11,0,0,0,11.89-1.68V95a24.84,24.84,0,0,1-7.68,1.16c-5.37,0-7.36-1.68-7.36-6.73V68.3h15.56V54.1H596.78v-18l-17,3.68V54.1H568.49V68.3h11.25Zm-53,.32c0-3.68,3.69-5.47,9.26-5.47a43.12,43.12,0,0,1,10.1,1.26v7.15a21.51,21.51,0,0,1-10.63,2.63c-5.46,0-8.73-2.1-8.73-5.57m5.2,17.56c6,0,10.84-1.26,15.36-4.31v3.37h16.82V74.08c0-13.56-9.14-21-24.39-21-8.52,0-16.94,2-26,6.1l6.1,12.52c6.52-2.74,12-4.42,16.83-4.42,7,0,10.62,2.73,10.62,8.31v2.73a49.53,49.53,0,0,0-12.62-1.58c-14.31,0-22.93,6-22.93,16.73,0,9.78,7.78,17.24,20.19,17.24m-92.44-.94h18.09V80.92h30.29v28.82H506V36.12H487.93V64.41H457.64V36.12H439.55ZM370.62,81.87c0-8,6.31-14.1,14.62-14.1A17.22,17.22,0,0,1,397,72.09V91.54A16.36,16.36,0,0,1,385.24,96c-8.2,0-14.62-6.1-14.62-14.09m26.61,27.87h16.83V32.44l-17,3.68V57.05a28.3,28.3,0,0,0-14.2-3.68c-16.19,0-28.92,12.51-28.92,28.5a28.25,28.25,0,0,0,28.4,28.6,25.12,25.12,0,0,0,14.93-4.83ZM320,67c5.36,0,9.88,3.47,11.67,8.83H308.47C310.15,70.3,314.36,67,320,67M291.33,82c0,16.2,13.25,28.82,30.28,28.82,9.36,0,16.2-2.53,23.25-8.42l-11.26-10c-2.63,2.74-6.52,4.21-11.14,4.21a14.39,14.39,0,0,1-13.68-8.83h39.65V83.55c0-17.67-11.88-30.39-28.08-30.39a28.57,28.57,0,0,0-29,28.81M262,51.58c6,0,9.36,3.78,9.36,8.31S268,68.2,262,68.2H244.11V51.58Zm-36,58.16h18.09V82.92h13.77l13.89,26.82H292l-16.2-29.45a22.27,22.27,0,0,0,13.88-20.72c0-13.25-10.41-23.45-26-23.45H226Z"/></svg>
+      </a>
+    </div>
+    <div class="collapse navbar-collapse navbar-collapse-1">
+      <ul class="nav navbar-nav navbar-right">
+        
+        
+          
+            <li>
+              <a href="/">Home</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="/about/">About</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="/contact/">Contact</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="https://www.redhat.com/en/events">Events</a>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                Workshops <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/agile_integrations_ci/">Agile Integrations Workshop - Citizen Integrator</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/agile_integrations_dev/">Agile Integrations Workshop - Developer</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/ansible_automation/">Ansible Automation Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/ansible_tower_intro/">Ansible Tower - an Introduction</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_container_intro/">Container Security - A Practical Introduction</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/containers_101/">Containers 101 Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/secure_software_factory/">DevSecOps Workshop - Secure Software Factory</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/containers_the_hard_way/">Linux Containers the Hard Way</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/strangling_the_monolith/">Microservices Workshop - Strangling the Monolith</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_4_101/">OpenShift 4 101</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_4_101_dynatrace/">OpenShift 4 101 w/Dynatrace</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_serverless/">OpenShift Serverless</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_service_mesh/">OpenShift Service Mesh</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/rhel_8/">Red Hat Enterprise Linux 8</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/selinux_policy/">SELinux Policy Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_service_mesh_v1.0/">zOpenShift Service Mesh</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                alpha <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/alpha/ansible_with_rhocp_edge/">Applied Ansible Automation - Containerized Edge Workshop</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                Retired <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/ansible_tower_azure/">Ansible Tower Workshop on Azure</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/cloudforms41/">CloudForms Workshops</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_containers/">Container Security Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/jdv_dev/">JBoss Data Virtualization Development</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_101_dcmetromap/">OpenShift 101 - DC Metro Map Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_openshift/">OpenShift Security Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/rhosp_101/">Red Hat OpenStack Platform 101</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/source_to_image/">Source to Image</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+      </ul>
+    </div>
+  </div>
+</nav>
+
+
+
+<div class="jumbotron jumbotron-page text-center">
+  <h1>Exercise 1.3 - Altering behavior</h1>
+</div>
+
+<div class="container">
+  <div class="row">
+    <p class="text-center">
+      
+      <a href="/workshops/selinux_policy">Return to Workshop</a>
+    </p>
+
+    
+
+
+
+
+
+
+
+
+<nav>
+  <ul class="pager">
+    
+    
+    <li class="previous">
+      <a href="/workshops/selinux_policy/exercise1.2/">&larr; Previous: Exercise 1.2 - SELinux Contexts</a>
+    </li>
+    
+    
+    
+    
+    <li class="next">
+      <a href="/workshops/selinux_policy/exercise1.4/">Next: Exercise 1.4 - Troubleshooting &rarr;</a>
+    </li>
+    
+    
+  </ul>
+</nav>
+
+    <div class="sect1">
+<h2 id="_exercise_description">Exercise Description</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Let’s take a look at controlling SELinux behavior.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_exercise_1_3_1">Exercise 1.3.1</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_step_1_what_mode_are_we_in">Step 1: What mode are we in?</h3>
+<div class="paragraph">
+<p>Next, let’s check to see what SELinux mode your host is in:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>getenforce</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">Enforcing</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_2_changing_modes">Step 2: Changing modes</h3>
+<div class="paragraph">
+<p>Now, we can change the mode that your host is in:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>setenforce <span style="color:#ae81ff">0</span>
+</span></span><span style="display:flex;"><span>getenforce</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">Permissive</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And we can change it back:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>setenforce <span style="color:#ae81ff">1</span>
+</span></span><span style="display:flex;"><span>getenforce</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">Enforcing</code></pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_exercise_1_3_2">Exercise 1.3.2</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Booleans</strong> are if-then-else rules written in SELinux Policy. They are convenient &#34;easy buttons&#34; for customizing
+       the way that SELinux Policy rules effect a confined domain, and are designed with many real-world use cases in mind.  For example, allowing httpd to serve files from users&#39; home directories.</p>
+</div>
+<div class="sect2">
+<h3 id="_step_1_list_available_booleans">Step 1: List available booleans</h3>
+<div class="paragraph">
+<p>To list all available booleans with a description of their purpose, use the <code>semanage</code> command:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>semanage boolean -l</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">SELinux boolean                State  Default Description
+
+abrt_anon_write                (off  ,  off)  Allow ABRT to modify public files used for public file transfer services.
+abrt_handle_event              (off  ,  off)  Determine whether ABRT can run in the abrt_handle_event_t domain to handle ABRT event scripts.
+abrt_upload_watch_anon_write   (on   ,   on)  Determine whether abrt-handle-upload can modify public files used for public file transfer services in /var/spool/abrt-upload/.
+antivirus_can_scan_system      (off  ,  off)  Allow antivirus programs to read non security files on a system
+antivirus_use_jit              (off  ,  off)  Determine whether antivirus programs can use JIT compiler.
+...
+httpd_enable_homedirs          (off  ,  off)  Allow httpd to read home directories
+httpd_execmem                  (off  ,  off)  Allow httpd scripts and modules execmem/execstack
+httpd_graceful_shutdown        (off  ,  off)  Allow HTTPD to connect to port 80 for graceful shutdown
+httpd_manage_ipa               (off  ,  off)  Allow httpd processes to manage IPA content
+httpd_mod_auth_ntlm_winbind    (off  ,  off)  Allow Apache to use mod_auth_ntlm_winbind
+httpd_mod_auth_pam             (off  ,  off)  Allow Apache to use mod_auth_pam
+httpd_read_user_content        (off  ,  off)  Allow httpd to read user content
+...</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Take a look at the list of booleans and you’ll see the breadth of options.  Don’t worry, you don’t have to master all of these; there’s about 350 booleans available in RHEL 8!</p>
+</div>
+<div class="paragraph">
+<p>An alternative way to list booleans, but without their descriptions, is:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>getsebool -a</span></span></code></pre></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_2_toggling_booleans">Step 2: Toggling booleans</h3>
+<div class="paragraph">
+<p>Each boolean is easily toggled on or off.  To temporarily toggle a boolean, you can enter:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>setsebool httpd_enable_homedirs on</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<p>This setting allows the Apache web server to access user home directories.  Used in conjunction with <code>httpd_read_user_content</code>, Apache can serve content from users&#39; home directories.</p>
+</div>
+<div class="paragraph">
+<p>To turn this off again, change &#39;on&#39; to &#39;off&#39;:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>setsebool httpd_enable_homedirs off</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<p>To toggle a boolean but make it persistent, use <code>semanage</code> instead of <code>setsebool</code>:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>semanage boolean -m --on httpd_enable_homedirs</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<p>But how do you check if any booleans have been changed from their default?  There’s an option for that!</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>semanage boolean -l -C</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">SELinux boolean                State  Default Description
+
+cups_execmem                   (on   ,   on)  Allow cups execmem/execstack
+virt_sandbox_use_all_caps      (on   ,   on)  Allow sandbox containers to use all capabilities
+virt_use_nfs                   (on   ,   on)  Allow confined virtual guests to manage nfs files</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<style>
+
+ 
+.modal {
+  display: none;  
+  position: fixed;  
+  z-index: 1;  
+  left: 0;
+  top: 0;
+  width: 100%;  
+  height: 100%;  
+  overflow: auto;  
+  background-color: rgb(0,0,0);  
+  background-color: rgba(0,0,0,0.4);  
+  -webkit-animation-name: fadeIn;  
+  -webkit-animation-duration: 0.4s;
+  animation-name: fadeIn;
+  animation-duration: 0.4s
+}
+
+ 
+.modal-content {
+  position: fixed;
+  bottom: 0;
+  background-color: #fefefe;
+  width: 100%;
+  -webkit-animation-name: slideIn;
+  -webkit-animation-duration: 0.4s;
+  animation-name: slideIn;
+  animation-duration: 0.4s
+}
+
+ 
+.close {
+  color: white;
+  float: right;
+  font-size: 28px;
+  font-weight: bold;
+}
+
+.close:hover,
+.close:focus {
+  color: #000;
+  text-decoration: none;
+  cursor: pointer;
+}
+
+.modal-header {
+  padding: 2px 16px;
+  background-color: #000000;
+  color: white;
+}
+
+.modal-body {padding: 2px 16px;}
+
+.modal-footer {
+  padding: 2px 16px;
+  background-color: #000000;
+  color: white;
+}
+
+ 
+@-webkit-keyframes slideIn {
+  from {bottom: -300px; opacity: 0}
+  to {bottom: 0; opacity: 1}
+}
+
+@keyframes slideIn {
+  from {bottom: -300px; opacity: 0}
+  to {bottom: 0; opacity: 1}
+}
+
+@-webkit-keyframes fadeIn {
+  from {opacity: 0}
+  to {opacity: 1}
+}
+
+@keyframes fadeIn {
+  from {opacity: 0}
+  to {opacity: 1}
+}
+</style>
+
+<div id="myModal" class="modal">
+
+  
+  <div class="modal-content">
+    <div class="modal-header">
+      <span class="close">&times;</span>
+      <h3>Workshop Details</h3>
+    </div>
+    <div class="modal-body">
+<div class="row">
+  <div class="col-lg-4 col-md-5 col-sm-12" id="workshopFooterDetails">
+    <table>
+      <tr>
+        <td class="text-right"><b>Domain</b></td>
+        <td><span class="domain"></span></td>
+        <td rowspan="3">
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
+        </td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Workshop</b></td>
+        <td><span class="prefix"></span></td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Student ID</b></td>
+        <td><span class="userid"></span></td>
+      </tr>
+    </table>
+  </div>
+  <div class="col-lg-8 col-md-7 col-sm-12">
+    <form id="footerForm" onsubmit="return false;" class="row" style="padding: 1.75rem 0 0 0;">
+      <div class="form-group col-sm-6 col-md-6 col-lg-2">
+        <label for="userid">Student ID</label>
+        <select id="userid" name="userid">
+          <option value="0">0</option>
+          <option value="1">1</option>
+          <option value="2">2</option>
+          <option value="3">3</option>
+          <option value="4">4</option>
+          <option value="5">5</option>
+          <option value="6">6</option>
+          <option value="7">7</option>
+          <option value="8">8</option>
+          <option value="9">9</option>
+          <option value="10">10</option>
+          <option value="11">11</option>
+          <option value="12">12</option>
+          <option value="13">13</option>
+          <option value="14">14</option>
+          <option value="15">15</option>
+          <option value="16">16</option>
+          <option value="17">17</option>
+          <option value="18">18</option>
+          <option value="19">19</option>
+          <option value="20">20</option>
+          <option value="21">21</option>
+          <option value="22">22</option>
+          <option value="23">23</option>
+          <option value="24">24</option>
+          <option value="25">25</option>
+          <option value="26">26</option>
+          <option value="27">27</option>
+          <option value="28">28</option>
+          <option value="29">29</option>
+          <option value="30">30</option>
+          <option value="31">31</option>
+          <option value="32">32</option>
+          <option value="33">33</option>
+          <option value="34">34</option>
+          <option value="35">35</option>
+          <option value="36">36</option>
+          <option value="37">37</option>
+          <option value="38">38</option>
+          <option value="39">39</option>
+          <option value="40">40</option>
+          <option value="41">41</option>
+          <option value="42">42</option>
+          <option value="43">43</option>
+          <option value="44">44</option>
+          <option value="45">45</option>
+          <option value="46">46</option>
+          <option value="47">47</option>
+          <option value="48">48</option>
+          <option value="49">49</option>
+          <option value="50">50</option>
+          <option value="51">51</option>
+          <option value="52">52</option>
+          <option value="53">53</option>
+          <option value="54">54</option>
+          <option value="55">55</option>
+          <option value="56">56</option>
+          <option value="57">57</option>
+          <option value="58">58</option>
+          <option value="59">59</option>
+          <option value="60">60</option>
+          <option value="61">61</option>
+          <option value="62">62</option>
+          <option value="63">63</option>
+          <option value="64">64</option>
+          <option value="65">65</option>
+          <option value="66">66</option>
+          <option value="67">67</option>
+          <option value="68">68</option>
+          <option value="69">69</option>
+          <option value="70">70</option>
+          <option value="71">71</option>
+          <option value="72">72</option>
+          <option value="73">73</option>
+          <option value="74">74</option>
+          <option value="75">75</option>
+          <option value="76">76</option>
+          <option value="77">77</option>
+          <option value="78">78</option>
+          <option value="79">79</option>
+          <option value="80">80</option>
+          <option value="81">81</option>
+          <option value="82">82</option>
+          <option value="83">83</option>
+          <option value="84">84</option>
+          <option value="85">85</option>
+          <option value="86">86</option>
+          <option value="87">87</option>
+          <option value="88">88</option>
+          <option value="89">89</option>
+          <option value="90">90</option>
+          <option value="91">91</option>
+          <option value="92">92</option>
+          <option value="93">93</option>
+          <option value="94">94</option>
+          <option value="95">95</option>
+          <option value="96">96</option>
+          <option value="97">97</option>
+          <option value="98">98</option>
+          <option value="99">99</option>
+          <option value="100">100</option>
+          <option value="101">101</option>
+          <option value="102">102</option>
+          <option value="103">103</option>
+          <option value="104">104</option>
+          <option value="105">105</option>
+          <option value="106">106</option>
+          <option value="107">107</option>
+          <option value="108">108</option>
+          <option value="109">109</option>
+          <option value="110">110</option>
+          <option value="111">111</option>
+          <option value="112">112</option>
+          <option value="113">113</option>
+          <option value="114">114</option>
+          <option value="115">115</option>
+          <option value="116">116</option>
+          <option value="117">117</option>
+          <option value="118">118</option>
+          <option value="119">119</option>
+          <option value="120">120</option>
+          <option value="121">121</option>
+          <option value="122">122</option>
+          <option value="123">123</option>
+          <option value="124">124</option>
+          <option value="125">125</option>
+          <option value="126">126</option>
+          <option value="127">127</option>
+          <option value="128">128</option>
+          <option value="129">129</option>
+          <option value="130">130</option>
+          <option value="131">131</option>
+          <option value="132">132</option>
+          <option value="133">133</option>
+          <option value="134">134</option>
+          <option value="135">135</option>
+          <option value="136">136</option>
+          <option value="137">137</option>
+          <option value="138">138</option>
+          <option value="139">139</option>
+          <option value="140">140</option>
+          <option value="141">141</option>
+          <option value="142">142</option>
+          <option value="143">143</option>
+          <option value="144">144</option>
+          <option value="145">145</option>
+          <option value="146">146</option>
+          <option value="147">147</option>
+          <option value="148">148</option>
+          <option value="149">149</option>
+          <option value="150">150</option>
+          <option value="151">151</option>
+          <option value="152">152</option>
+          <option value="153">153</option>
+          <option value="154">154</option>
+          <option value="155">155</option>
+          <option value="156">156</option>
+          <option value="157">157</option>
+          <option value="158">158</option>
+          <option value="159">159</option>
+          <option value="160">160</option>
+          <option value="161">161</option>
+          <option value="162">162</option>
+          <option value="163">163</option>
+          <option value="164">164</option>
+          <option value="165">165</option>
+          <option value="166">166</option>
+          <option value="167">167</option>
+          <option value="168">168</option>
+          <option value="169">169</option>
+          <option value="170">170</option>
+          <option value="171">171</option>
+          <option value="172">172</option>
+          <option value="173">173</option>
+          <option value="174">174</option>
+          <option value="175">175</option>
+          <option value="176">176</option>
+          <option value="177">177</option>
+          <option value="178">178</option>
+          <option value="179">179</option>
+          <option value="180">180</option>
+          <option value="181">181</option>
+          <option value="182">182</option>
+          <option value="183">183</option>
+          <option value="184">184</option>
+          <option value="185">185</option>
+          <option value="186">186</option>
+          <option value="187">187</option>
+          <option value="188">188</option>
+          <option value="189">189</option>
+          <option value="190">190</option>
+          <option value="191">191</option>
+          <option value="192">192</option>
+          <option value="193">193</option>
+          <option value="194">194</option>
+          <option value="195">195</option>
+          <option value="196">196</option>
+          <option value="197">197</option>
+          <option value="198">198</option>
+          <option value="199">199</option>
+          <option value="200">200</option>
+        </select>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-4">
+        <label for="domain">Domain</label>
+        <select id="domain" name="domain">
+          <option value="rhnaps.io">rhnaps.io</option>
+          <option value="redhatgov.io">redhatgov.io</option>
+          <option value="az.redhatgov.io">az.redhatgov.io</option>
+          <option value="redhat-fierce.io">redhat-fierce.io</option>
+          <option value="fiercesw.network">fiercesw.network</option>
+          <option value="rhtps.io">rhtps.io</option>
+          <option value="openshiftworkshop.com">openshiftworkshop.com</option>
+          <option value="redhatpsmwsa.com">redhatpsmwsa.com</option>
+          <option value="open.redhat.com">open.redhat.com</option>
+          <option value="opentlc.com">opentlc.com</option>
+          <option value="aroapp.io">aroapp.io</option>
+          <option value="danclark.io">danclark.io</option>
+        </select>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-3">
+        <label for="prefix">Workshop</label>
+        <input id="prefix" name="prefix" type="text" size="16" class="form-control" placeholder="example" onkeyup="this.value = this.value.toLowerCase();this.value = this.value.replace(/[^-.a-zA-Z0-9]/g, '');"/>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-3">
+        <button type="submit" class="btn btn-primary form-control" style="margin-bottom:1rem;">Enter</button>
+        <button type="reset" class="btn btn-default form-control">Default</button>
+      </div>
+    </form>
+  </div>
+</div>
+
+    </div>
+    <div class="modal-footer">
+      <h3></h3>
+    </div>
+  </div>
+
+</div>
+
+<script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
+<script type="text/javascript">
+
+  
+  var Cookies2 = Cookies.noConflict();
+
+  var cookiePathArr = cleanArray(window.location.pathname.split('/'));
+  var cookiePath = '/' + cookiePathArr[0] + '/' + cookiePathArr[1] + '/';
+
+  function cleanArray(actual) {
+    var newArray = new Array();
+    for (var i = 0; i < actual.length; i++) {
+      if (actual[i]) {
+        newArray.push(actual[i]);
+      }
+    }
+    return newArray;
+  }
+  function replaceClassText() {
+    jQuery("span.domain").html(Cookies2.get("domain"));
+    jQuery("span.userid").html(Cookies2.get("userid"));
+    jQuery("span.prefix").html(Cookies2.get("prefix"));
+  }
+  function pageLoadWorkshopFooterTest() {
+    
+    if (Cookies2.get("domain") === undefined) {
+      resetWorkshopFooter();
+    }
+    else {
+      replaceClassText();
+      setWorkshopFooterInputValues()
+    }
+  }
+  function setWorkshopFooterData() {
+    
+    Cookies2.set("domain", jQuery("select#domain").val(), { path: cookiePath, expires: 7 } );
+    Cookies2.set("prefix", jQuery("input#prefix").val().replace(/[^-.a-zA-Z0-9]/g, ''), { path: cookiePath, expires: 7 } );
+    Cookies2.set("userid", jQuery("select#userid").val(), { path: cookiePath, expires: 7 } );
+    replaceClassText();
+    modal.style.display = "none";
+  }
+  function setWorkshopFooterInputValues() {
+    jQuery("select#domain").val(Cookies2.get("domain"));
+    jQuery("input#prefix").val(Cookies2.get("prefix"));
+    jQuery("select#userid").val(Cookies2.get("userid"));
+  }
+  function resetWorkshopFooter() {
+    
+    jQuery("select#domain, select#userid").prop("selectedIndex", 0);
+    jQuery("input#prefix").val(jQuery("input#prefix").attr('placeholder'));
+    
+    Cookies2.set("domain", jQuery("select#domain option").first().val(), { path: cookiePath, expires: 7 } ); 
+    Cookies2.set("userid", jQuery("select#userid option").first().val(), { path: cookiePath, expires: 7 } ); 
+    Cookies2.set("prefix", jQuery("input#prefix").val(), { path: cookiePath, expires: 7 } );
+    
+    
+    replaceClassText();
+  }
+
+
+
+
+  function updateFooter(e){
+    fieldName = '';
+
+    switch(e.id) {
+      case 'userid':
+        fieldName = 'User Id';
+        break;
+      case 'domain':
+        fieldName = 'Domain';
+        break;
+      case 'prefix':
+        fieldName = 'Workshop';
+        break;
+      default:
+        fieldName = 'unknown';
+    }
+    setWorkshopFooterData();
+    toastr["success"](fieldName + " set to " + e.value);
+  }
+
+  jQuery(document).ready(function() {
+    pageLoadWorkshopFooterTest();
+
+
+    
+    var input = document.getElementById("prefix");
+
+    
+    input.addEventListener("keyup", function(event) {
+      
+      if (event.keyCode === 13) {
+        
+        event.preventDefault();
+        
+        
+        updateFooter(input);
+      }
+    });
+
+
+    jQuery("form#footerForm").submit(function() {
+      setWorkshopFooterData();
+      return false; 
+    });
+
+    jQuery("form#footerForm").bind("reset", function() {
+      resetWorkshopFooter();
+      return true;
+    });
+
+    return false;
+  });
+
+</script>
+
+<hr>
+<h3>Workshop Details</h3>
+    <table>
+      <tr>
+        <td class="text-right"><b>Domain</b></td>
+        <td><span class="domain"></span></td>
+        <td rowspan="3">
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
+        </td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Workshop</b></td>
+        <td><span class="prefix"></span></td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Student ID</b></td>
+        <td><span class="userid"></span></td>
+      </tr>
+    </table>
+<button id="myBtn">Configure Workshop</button>
+<hr>
+
+<script>
+
+var modal = document.getElementById("myModal");
+
+
+var btn = document.getElementById("myBtn");
+
+
+var span = document.getElementsByClassName("close")[0];
+
+
+btn.onclick = function() {
+  modal.style.display = "block";
+}
+
+
+span.onclick = function() {
+  modal.style.display = "none";
+}
+
+
+window.onclick = function(event) {
+  if (event.target == modal) {
+    modal.style.display = "none";
+  }
+}
+</script>
+
+
+</div>
+</div>
+</div>
+</div>
+
+
+    
+
+
+
+
+
+
+
+
+<nav>
+  <ul class="pager">
+    
+    
+    <li class="previous">
+      <a href="/workshops/selinux_policy/exercise1.2/">&larr; Previous: Exercise 1.2 - SELinux Contexts</a>
+    </li>
+    
+    
+    
+    
+    <li class="next">
+      <a href="/workshops/selinux_policy/exercise1.4/">Next: Exercise 1.4 - Troubleshooting &rarr;</a>
+    </li>
+    
+    
+  </ul>
+</nav>
+
+    <p class="text-center">
+      
+      <a href="/workshops/selinux_policy">Return to Workshop</a>
+    </p>
+  </div>
+</div>
+
+    <div id="page-footer" class="container">
+      <p class="text-center">
+        Copyright &copy; 2024 Red Hat, Inc.
+      </p>
+    </div>
+    <script type="text/javascript">
+      if (("undefined" !== typeof _satellite) && ("function" === typeof _satellite.pageBottom)) {
+          _satellite.pageBottom();
+      }
+    </script>
+  </body>
+</html>
diff --git a/workshops/selinux_policy/exercise1.4/index.html b/workshops/selinux_policy/exercise1.4/index.html
new file mode 100644
index 000000000..b513e29a9
--- /dev/null
+++ b/workshops/selinux_policy/exercise1.4/index.html
@@ -0,0 +1,1043 @@
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <meta charset="utf-8" />
+    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+    <title>Exercise 1.4 - Troubleshooting | Red Hat | Public Sector</title>
+
+    
+    
+    <link rel="stylesheet" href="/node_modules/patternfly/dist/css/patternfly.min.css" />
+    <link rel="stylesheet" href="/node_modules/patternfly/dist/css/patternfly-additions.min.css" />
+
+    
+    <link rel="stylesheet" href="/node_modules/highlight.js/styles/darkula.css" />
+
+    
+    <link rel="stylesheet" href="/css/main.css" />
+    <link rel="stylesheet" href="/css/asciidoc.css" />
+    <link rel="stylesheet" href="/css/custom.css" />
+    <link rel="stylesheet" href="/css/toastr.min.css" />
+
+    
+    <script async src="https://www.googletagmanager.com/gtag/js?id=G-DL741MBBZQ"></script>
+    <script>
+      window.dataLayer = window.dataLayer || [];
+      function gtag(){dataLayer.push(arguments);}
+      gtag('js', new Date());
+
+      gtag('config', 'G-DL741MBBZQ');
+    </script>
+
+    
+    <script id="adobe_dtm" src="//www.redhat.com/dtm.js" type="text/javascript"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/jquery/dist/jquery.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap/dist/js/bootstrap.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/c3/c3.min.js"></script>
+    <script src="/node_modules/patternfly/node_modules/d3/d3.min.js"></script>
+
+    
+    
+    <script src="/node_modules/patternfly/node_modules/datatables/media/js/jquery.dataTables.min.js"></script>
+    <script src="/node_modules/patternfly/node_modules/drmonty-datatables-colvis/js/dataTables.colVis.js"></script>
+    <script src="/node_modules/patternfly/node_modules/datatables.net-colreorder/js/dataTables.colReorder.js"></script>
+
+    
+    
+    <script src="/node_modules/patternfly/dist/js/patternfly.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/patternfly-bootstrap-combobox/js/bootstrap-combobox.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-datepicker/dist/js/bootstrap-datepicker.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/moment/min/moment.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/eonasdan-bootstrap-datetimepicker/build/js/bootstrap-datetimepicker.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-select/dist/js/bootstrap-select.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-switch/dist/js/bootstrap-switch.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-touchspin/dist/jquery.bootstrap-touchspin.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/patternfly-bootstrap-treeview/dist/bootstrap-treeview.min.js"></script>
+
+    
+    <script src="https://cdn.rawgit.com/google/code-prettify/master/loader/run_prettify.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/jquery-match-height/dist/jquery.matchHeight-min.js"></script>
+    
+    <script src="/js/clipboard.min.js"></script>
+    <script src="/js/clip.js"></script>
+
+    
+    <script src="/js/toastr.min.js"></script>
+
+    
+    <script src="/node_modules/highlight.js/lib/highlight.js"></script>
+    <script>hljs.initHighlightingOnLoad();</script>
+  </head>
+  <body class="">
+    
+
+<nav class="navbar navbar-default navbar-inverse navbar-fixed-top " role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse-1">
+        <span class="sr-only">Toggle navigation</span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="/">
+      <svg width=150 height=auto id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 613 145"><defs><style>.cls-1{fill:#e00;}.cls-2{fill:#fff;}</style></defs><path class="cls-1" d="M127.47,83.49c12.51,0,30.61-2.58,30.61-17.46a14,14,0,0,0-.31-3.42l-7.45-32.36c-1.72-7.12-3.23-10.35-15.73-16.6C124.89,8.69,103.76.5,97.51.5,91.69.5,90,8,83.06,8c-6.68,0-11.64-5.6-17.89-5.6-6,0-9.91,4.09-12.93,12.5,0,0-8.41,23.72-9.49,27.16A6.43,6.43,0,0,0,42.53,44c0,9.22,36.3,39.45,84.94,39.45M160,72.07c1.73,8.19,1.73,9.05,1.73,10.13,0,14-15.74,21.77-36.43,21.77C78.54,104,37.58,76.6,37.58,58.49a18.45,18.45,0,0,1,1.51-7.33C22.27,52,.5,55,.5,74.22c0,31.48,74.59,70.28,133.65,70.28,45.28,0,56.7-20.48,56.7-36.65,0-12.72-11-27.16-30.83-35.78"/><path d="M160,72.07c1.73,8.19,1.73,9.05,1.73,10.13,0,14-15.74,21.77-36.43,21.77C78.54,104,37.58,76.6,37.58,58.49a18.45,18.45,0,0,1,1.51-7.33l3.66-9.06A6.43,6.43,0,0,0,42.53,44c0,9.22,36.3,39.45,84.94,39.45,12.51,0,30.61-2.58,30.61-17.46a14,14,0,0,0-.31-3.42Z"/><path class="cls-2" d="M579.74,92.8c0,11.89,7.15,17.67,20.19,17.67a52.11,52.11,0,0,0,11.89-1.68V95a24.84,24.84,0,0,1-7.68,1.16c-5.37,0-7.36-1.68-7.36-6.73V68.3h15.56V54.1H596.78v-18l-17,3.68V54.1H568.49V68.3h11.25Zm-53,.32c0-3.68,3.69-5.47,9.26-5.47a43.12,43.12,0,0,1,10.1,1.26v7.15a21.51,21.51,0,0,1-10.63,2.63c-5.46,0-8.73-2.1-8.73-5.57m5.2,17.56c6,0,10.84-1.26,15.36-4.31v3.37h16.82V74.08c0-13.56-9.14-21-24.39-21-8.52,0-16.94,2-26,6.1l6.1,12.52c6.52-2.74,12-4.42,16.83-4.42,7,0,10.62,2.73,10.62,8.31v2.73a49.53,49.53,0,0,0-12.62-1.58c-14.31,0-22.93,6-22.93,16.73,0,9.78,7.78,17.24,20.19,17.24m-92.44-.94h18.09V80.92h30.29v28.82H506V36.12H487.93V64.41H457.64V36.12H439.55ZM370.62,81.87c0-8,6.31-14.1,14.62-14.1A17.22,17.22,0,0,1,397,72.09V91.54A16.36,16.36,0,0,1,385.24,96c-8.2,0-14.62-6.1-14.62-14.09m26.61,27.87h16.83V32.44l-17,3.68V57.05a28.3,28.3,0,0,0-14.2-3.68c-16.19,0-28.92,12.51-28.92,28.5a28.25,28.25,0,0,0,28.4,28.6,25.12,25.12,0,0,0,14.93-4.83ZM320,67c5.36,0,9.88,3.47,11.67,8.83H308.47C310.15,70.3,314.36,67,320,67M291.33,82c0,16.2,13.25,28.82,30.28,28.82,9.36,0,16.2-2.53,23.25-8.42l-11.26-10c-2.63,2.74-6.52,4.21-11.14,4.21a14.39,14.39,0,0,1-13.68-8.83h39.65V83.55c0-17.67-11.88-30.39-28.08-30.39a28.57,28.57,0,0,0-29,28.81M262,51.58c6,0,9.36,3.78,9.36,8.31S268,68.2,262,68.2H244.11V51.58Zm-36,58.16h18.09V82.92h13.77l13.89,26.82H292l-16.2-29.45a22.27,22.27,0,0,0,13.88-20.72c0-13.25-10.41-23.45-26-23.45H226Z"/></svg>
+      </a>
+    </div>
+    <div class="collapse navbar-collapse navbar-collapse-1">
+      <ul class="nav navbar-nav navbar-right">
+        
+        
+          
+            <li>
+              <a href="/">Home</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="/about/">About</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="/contact/">Contact</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="https://www.redhat.com/en/events">Events</a>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                Workshops <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/agile_integrations_ci/">Agile Integrations Workshop - Citizen Integrator</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/agile_integrations_dev/">Agile Integrations Workshop - Developer</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/ansible_automation/">Ansible Automation Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/ansible_tower_intro/">Ansible Tower - an Introduction</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_container_intro/">Container Security - A Practical Introduction</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/containers_101/">Containers 101 Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/secure_software_factory/">DevSecOps Workshop - Secure Software Factory</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/containers_the_hard_way/">Linux Containers the Hard Way</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/strangling_the_monolith/">Microservices Workshop - Strangling the Monolith</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_4_101/">OpenShift 4 101</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_4_101_dynatrace/">OpenShift 4 101 w/Dynatrace</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_serverless/">OpenShift Serverless</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_service_mesh/">OpenShift Service Mesh</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/rhel_8/">Red Hat Enterprise Linux 8</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/selinux_policy/">SELinux Policy Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_service_mesh_v1.0/">zOpenShift Service Mesh</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                alpha <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/alpha/ansible_with_rhocp_edge/">Applied Ansible Automation - Containerized Edge Workshop</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                Retired <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/ansible_tower_azure/">Ansible Tower Workshop on Azure</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/cloudforms41/">CloudForms Workshops</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_containers/">Container Security Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/jdv_dev/">JBoss Data Virtualization Development</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_101_dcmetromap/">OpenShift 101 - DC Metro Map Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_openshift/">OpenShift Security Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/rhosp_101/">Red Hat OpenStack Platform 101</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/source_to_image/">Source to Image</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+      </ul>
+    </div>
+  </div>
+</nav>
+
+
+
+<div class="jumbotron jumbotron-page text-center">
+  <h1>Exercise 1.4 - Troubleshooting</h1>
+</div>
+
+<div class="container">
+  <div class="row">
+    <p class="text-center">
+      
+      <a href="/workshops/selinux_policy">Return to Workshop</a>
+    </p>
+
+    
+
+
+
+
+
+
+
+
+<nav>
+  <ul class="pager">
+    
+    
+    <li class="previous">
+      <a href="/workshops/selinux_policy/exercise1.3/">&larr; Previous: Exercise 1.3 - Altering behavior</a>
+    </li>
+    
+    
+    
+    
+    <li class="next">
+      <a href="/workshops/selinux_policy/exercise2.0/">Next: Exercise 2.0 - Creating Custom SELinux Policy &rarr;</a>
+    </li>
+    
+    
+  </ul>
+</nav>
+
+    <div class="sect1">
+<h2 id="_exercise_description">Exercise Description</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Let’s look at some techniques for examing SELinux, as these are useful for troubleshooting.  We’ll build on this in Section 2 of the workshop.</p>
+</div>
+<div class="sect2">
+<h3 id="_step_1_changing_modes_for_specific_domains">Step 1: Changing modes for specific domains</h3>
+<div class="paragraph">
+<p>You can also set individual SELinux domains (like <code>httpd_t</code>, which controls web server access control) to permissve mode:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>semanage permissive -a httpd_t
+</span></span><span style="display:flex;"><span>semanage permissive -l</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">Builtin Permissive Types
+
+Customized Permissive Types
+
+httpd_t</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And again, we can change it back:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>semanage permissive -d httpd_t</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">libsemanage.semanage_direct_remove_key: Removing last permissive_httpd_t module (no other permissive_httpd_t module exists at another priority).</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>permissive</code> mode means that either the entire system (from the previous section) or the specific application constrained by a type (the second example) are allowed to bypass SELinux access controls.  However, even though access controls are disabled, full AVC (access vector cache, where SELinux stores its decisions) logging still happens.  This is useful for debugging a specific application without globally disabling SELinux.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_2_selinux_logging">Step 2: SELinux logging</h3>
+<div class="paragraph">
+<p>SELinux messages are logged to the <code>/var/log/audit/audit.log</code> file.  We can read the messages with this command:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ausearch -m MAC_POLICY_LOAD -i --just-one</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<p>We have asked the <code>ausearch</code> utility to look for SELinux policies being loaded (<code>-m MAC_POLICY_LOAD</code>), to make the result human-readable (<code>-i</code>), and to return only a single result (<code>--just-one</code>):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">----
+type=PROCTITLE msg=audit(05/17/2019 23:47:54.147:1896) : proctitle=/sbin/load_policy
+type=SYSCALL msg=audit(05/17/2019 23:47:54.147:1896) : arch=x86_64 syscall=write success=yes exit=3857474 a0=0x4 a1=0x7fb57e597000 a2=0x3adc42 a3=0x7ffc8bb993a0 items=0 ppid=16567 pid=16572 auid=ec2-user uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=pts0 ses=1 comm=load_policy exe=/usr/sbin/load_policy subj=unconfined_u:unconfined_r:load_policy_t:s0-s0:c0.c1023 key=(null)
+type=MAC_POLICY_LOAD msg=audit(05/17/2019 23:47:54.147:1896) : auid=ec2-user ses=1 lsm=selinux res=yes</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Other useful searches include:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>all denials:</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ausearch -m avc,user_avc,selinux_err,user_selinux_err</span></span></code></pre></div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>denials from today:</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ausearch -m avc -ts today</span></span></code></pre></div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>denials from the last 10 minutes:</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ausearch -m avc -ts recent</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<p>You can try these, if you like, but they may or may not return any results.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_3_interpreting_avcs">Step 3: Interpreting AVCs</h3>
+<div class="paragraph">
+<p>If you use <code>ausearch</code> to find AVC messages, you can see exactly what caused SELinux to deny access:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ausearch -if ./testaudit -m AVC</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">----
+time-&gt;Mon Nov 17 00:45:36 2008
+type=SYSCALL msg=audit(1226882736.442:86): arch=40000003 syscall=196 success=no exit=-13 a0=b9a1e198 a1=bfc2921c a2=54dff4 a3=2008171 items=0 ppid=2425 pid=2427 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4 comm=&#34;httpd&#34; exe=&#34;/usr/sbin/httpd&#34; subj=unconfined_u:system_r:httpd_t:s0 key=(null)
+type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm=&#34;httpd&#34; path=&#34;/var/www/html/file1&#34; dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Here, we can see that the <code>httpd</code> process, ID <code>2427</code>, was disallowed from checking attributes of the file <code>/var/www/html/file1</code>.  Additionally, we can see that the domain of the process was <code>httpd_t</code>, and the file was labeled with the <code>samba_share_t</code> context.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_4_getting_advice">Step 4: Getting advice</h3>
+<div class="paragraph">
+<p>There is a neat utility called <code>audit2why</code>, which can make suggestions as to how you might solve SELinux AVC messages.  Let’s try it on our test error:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ausearch -if ./testaudit -m AVC | audit2why</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm=&#34;httpd&#34; path=&#34;/var/www/html/file1&#34; dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
+
+	Was caused by:
+		Missing type enforcement (TE) allow rule.
+
+		You can use audit2allow to generate a loadable module to allow this access.</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The <code>audit2why</code> utility is telling us that the problem was caused by a missing <code>allow</code> rule, which would grant access for <code>httpd_t</code> processes to <code>samba_share_t</code> files.  This is obviously not the whole story, in this case, but it points us to the problem of the file’s context being incorrect.</p>
+</div>
+<div class="paragraph">
+<p><code>audit2why</code> will also tell you if a boolean is available to avoid a particular AVC error.</p>
+</div>
+<div class="paragraph">
+<p>That’s all for the first half of the workshop.  Go ahead an exit the root shell; the remainder of the workshop will be run as a regular user.</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>exit</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<style>
+
+ 
+.modal {
+  display: none;  
+  position: fixed;  
+  z-index: 1;  
+  left: 0;
+  top: 0;
+  width: 100%;  
+  height: 100%;  
+  overflow: auto;  
+  background-color: rgb(0,0,0);  
+  background-color: rgba(0,0,0,0.4);  
+  -webkit-animation-name: fadeIn;  
+  -webkit-animation-duration: 0.4s;
+  animation-name: fadeIn;
+  animation-duration: 0.4s
+}
+
+ 
+.modal-content {
+  position: fixed;
+  bottom: 0;
+  background-color: #fefefe;
+  width: 100%;
+  -webkit-animation-name: slideIn;
+  -webkit-animation-duration: 0.4s;
+  animation-name: slideIn;
+  animation-duration: 0.4s
+}
+
+ 
+.close {
+  color: white;
+  float: right;
+  font-size: 28px;
+  font-weight: bold;
+}
+
+.close:hover,
+.close:focus {
+  color: #000;
+  text-decoration: none;
+  cursor: pointer;
+}
+
+.modal-header {
+  padding: 2px 16px;
+  background-color: #000000;
+  color: white;
+}
+
+.modal-body {padding: 2px 16px;}
+
+.modal-footer {
+  padding: 2px 16px;
+  background-color: #000000;
+  color: white;
+}
+
+ 
+@-webkit-keyframes slideIn {
+  from {bottom: -300px; opacity: 0}
+  to {bottom: 0; opacity: 1}
+}
+
+@keyframes slideIn {
+  from {bottom: -300px; opacity: 0}
+  to {bottom: 0; opacity: 1}
+}
+
+@-webkit-keyframes fadeIn {
+  from {opacity: 0}
+  to {opacity: 1}
+}
+
+@keyframes fadeIn {
+  from {opacity: 0}
+  to {opacity: 1}
+}
+</style>
+
+<div id="myModal" class="modal">
+
+  
+  <div class="modal-content">
+    <div class="modal-header">
+      <span class="close">&times;</span>
+      <h3>Workshop Details</h3>
+    </div>
+    <div class="modal-body">
+<div class="row">
+  <div class="col-lg-4 col-md-5 col-sm-12" id="workshopFooterDetails">
+    <table>
+      <tr>
+        <td class="text-right"><b>Domain</b></td>
+        <td><span class="domain"></span></td>
+        <td rowspan="3">
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
+        </td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Workshop</b></td>
+        <td><span class="prefix"></span></td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Student ID</b></td>
+        <td><span class="userid"></span></td>
+      </tr>
+    </table>
+  </div>
+  <div class="col-lg-8 col-md-7 col-sm-12">
+    <form id="footerForm" onsubmit="return false;" class="row" style="padding: 1.75rem 0 0 0;">
+      <div class="form-group col-sm-6 col-md-6 col-lg-2">
+        <label for="userid">Student ID</label>
+        <select id="userid" name="userid">
+          <option value="0">0</option>
+          <option value="1">1</option>
+          <option value="2">2</option>
+          <option value="3">3</option>
+          <option value="4">4</option>
+          <option value="5">5</option>
+          <option value="6">6</option>
+          <option value="7">7</option>
+          <option value="8">8</option>
+          <option value="9">9</option>
+          <option value="10">10</option>
+          <option value="11">11</option>
+          <option value="12">12</option>
+          <option value="13">13</option>
+          <option value="14">14</option>
+          <option value="15">15</option>
+          <option value="16">16</option>
+          <option value="17">17</option>
+          <option value="18">18</option>
+          <option value="19">19</option>
+          <option value="20">20</option>
+          <option value="21">21</option>
+          <option value="22">22</option>
+          <option value="23">23</option>
+          <option value="24">24</option>
+          <option value="25">25</option>
+          <option value="26">26</option>
+          <option value="27">27</option>
+          <option value="28">28</option>
+          <option value="29">29</option>
+          <option value="30">30</option>
+          <option value="31">31</option>
+          <option value="32">32</option>
+          <option value="33">33</option>
+          <option value="34">34</option>
+          <option value="35">35</option>
+          <option value="36">36</option>
+          <option value="37">37</option>
+          <option value="38">38</option>
+          <option value="39">39</option>
+          <option value="40">40</option>
+          <option value="41">41</option>
+          <option value="42">42</option>
+          <option value="43">43</option>
+          <option value="44">44</option>
+          <option value="45">45</option>
+          <option value="46">46</option>
+          <option value="47">47</option>
+          <option value="48">48</option>
+          <option value="49">49</option>
+          <option value="50">50</option>
+          <option value="51">51</option>
+          <option value="52">52</option>
+          <option value="53">53</option>
+          <option value="54">54</option>
+          <option value="55">55</option>
+          <option value="56">56</option>
+          <option value="57">57</option>
+          <option value="58">58</option>
+          <option value="59">59</option>
+          <option value="60">60</option>
+          <option value="61">61</option>
+          <option value="62">62</option>
+          <option value="63">63</option>
+          <option value="64">64</option>
+          <option value="65">65</option>
+          <option value="66">66</option>
+          <option value="67">67</option>
+          <option value="68">68</option>
+          <option value="69">69</option>
+          <option value="70">70</option>
+          <option value="71">71</option>
+          <option value="72">72</option>
+          <option value="73">73</option>
+          <option value="74">74</option>
+          <option value="75">75</option>
+          <option value="76">76</option>
+          <option value="77">77</option>
+          <option value="78">78</option>
+          <option value="79">79</option>
+          <option value="80">80</option>
+          <option value="81">81</option>
+          <option value="82">82</option>
+          <option value="83">83</option>
+          <option value="84">84</option>
+          <option value="85">85</option>
+          <option value="86">86</option>
+          <option value="87">87</option>
+          <option value="88">88</option>
+          <option value="89">89</option>
+          <option value="90">90</option>
+          <option value="91">91</option>
+          <option value="92">92</option>
+          <option value="93">93</option>
+          <option value="94">94</option>
+          <option value="95">95</option>
+          <option value="96">96</option>
+          <option value="97">97</option>
+          <option value="98">98</option>
+          <option value="99">99</option>
+          <option value="100">100</option>
+          <option value="101">101</option>
+          <option value="102">102</option>
+          <option value="103">103</option>
+          <option value="104">104</option>
+          <option value="105">105</option>
+          <option value="106">106</option>
+          <option value="107">107</option>
+          <option value="108">108</option>
+          <option value="109">109</option>
+          <option value="110">110</option>
+          <option value="111">111</option>
+          <option value="112">112</option>
+          <option value="113">113</option>
+          <option value="114">114</option>
+          <option value="115">115</option>
+          <option value="116">116</option>
+          <option value="117">117</option>
+          <option value="118">118</option>
+          <option value="119">119</option>
+          <option value="120">120</option>
+          <option value="121">121</option>
+          <option value="122">122</option>
+          <option value="123">123</option>
+          <option value="124">124</option>
+          <option value="125">125</option>
+          <option value="126">126</option>
+          <option value="127">127</option>
+          <option value="128">128</option>
+          <option value="129">129</option>
+          <option value="130">130</option>
+          <option value="131">131</option>
+          <option value="132">132</option>
+          <option value="133">133</option>
+          <option value="134">134</option>
+          <option value="135">135</option>
+          <option value="136">136</option>
+          <option value="137">137</option>
+          <option value="138">138</option>
+          <option value="139">139</option>
+          <option value="140">140</option>
+          <option value="141">141</option>
+          <option value="142">142</option>
+          <option value="143">143</option>
+          <option value="144">144</option>
+          <option value="145">145</option>
+          <option value="146">146</option>
+          <option value="147">147</option>
+          <option value="148">148</option>
+          <option value="149">149</option>
+          <option value="150">150</option>
+          <option value="151">151</option>
+          <option value="152">152</option>
+          <option value="153">153</option>
+          <option value="154">154</option>
+          <option value="155">155</option>
+          <option value="156">156</option>
+          <option value="157">157</option>
+          <option value="158">158</option>
+          <option value="159">159</option>
+          <option value="160">160</option>
+          <option value="161">161</option>
+          <option value="162">162</option>
+          <option value="163">163</option>
+          <option value="164">164</option>
+          <option value="165">165</option>
+          <option value="166">166</option>
+          <option value="167">167</option>
+          <option value="168">168</option>
+          <option value="169">169</option>
+          <option value="170">170</option>
+          <option value="171">171</option>
+          <option value="172">172</option>
+          <option value="173">173</option>
+          <option value="174">174</option>
+          <option value="175">175</option>
+          <option value="176">176</option>
+          <option value="177">177</option>
+          <option value="178">178</option>
+          <option value="179">179</option>
+          <option value="180">180</option>
+          <option value="181">181</option>
+          <option value="182">182</option>
+          <option value="183">183</option>
+          <option value="184">184</option>
+          <option value="185">185</option>
+          <option value="186">186</option>
+          <option value="187">187</option>
+          <option value="188">188</option>
+          <option value="189">189</option>
+          <option value="190">190</option>
+          <option value="191">191</option>
+          <option value="192">192</option>
+          <option value="193">193</option>
+          <option value="194">194</option>
+          <option value="195">195</option>
+          <option value="196">196</option>
+          <option value="197">197</option>
+          <option value="198">198</option>
+          <option value="199">199</option>
+          <option value="200">200</option>
+        </select>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-4">
+        <label for="domain">Domain</label>
+        <select id="domain" name="domain">
+          <option value="rhnaps.io">rhnaps.io</option>
+          <option value="redhatgov.io">redhatgov.io</option>
+          <option value="az.redhatgov.io">az.redhatgov.io</option>
+          <option value="redhat-fierce.io">redhat-fierce.io</option>
+          <option value="fiercesw.network">fiercesw.network</option>
+          <option value="rhtps.io">rhtps.io</option>
+          <option value="openshiftworkshop.com">openshiftworkshop.com</option>
+          <option value="redhatpsmwsa.com">redhatpsmwsa.com</option>
+          <option value="open.redhat.com">open.redhat.com</option>
+          <option value="opentlc.com">opentlc.com</option>
+          <option value="aroapp.io">aroapp.io</option>
+          <option value="danclark.io">danclark.io</option>
+        </select>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-3">
+        <label for="prefix">Workshop</label>
+        <input id="prefix" name="prefix" type="text" size="16" class="form-control" placeholder="example" onkeyup="this.value = this.value.toLowerCase();this.value = this.value.replace(/[^-.a-zA-Z0-9]/g, '');"/>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-3">
+        <button type="submit" class="btn btn-primary form-control" style="margin-bottom:1rem;">Enter</button>
+        <button type="reset" class="btn btn-default form-control">Default</button>
+      </div>
+    </form>
+  </div>
+</div>
+
+    </div>
+    <div class="modal-footer">
+      <h3></h3>
+    </div>
+  </div>
+
+</div>
+
+<script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
+<script type="text/javascript">
+
+  
+  var Cookies2 = Cookies.noConflict();
+
+  var cookiePathArr = cleanArray(window.location.pathname.split('/'));
+  var cookiePath = '/' + cookiePathArr[0] + '/' + cookiePathArr[1] + '/';
+
+  function cleanArray(actual) {
+    var newArray = new Array();
+    for (var i = 0; i < actual.length; i++) {
+      if (actual[i]) {
+        newArray.push(actual[i]);
+      }
+    }
+    return newArray;
+  }
+  function replaceClassText() {
+    jQuery("span.domain").html(Cookies2.get("domain"));
+    jQuery("span.userid").html(Cookies2.get("userid"));
+    jQuery("span.prefix").html(Cookies2.get("prefix"));
+  }
+  function pageLoadWorkshopFooterTest() {
+    
+    if (Cookies2.get("domain") === undefined) {
+      resetWorkshopFooter();
+    }
+    else {
+      replaceClassText();
+      setWorkshopFooterInputValues()
+    }
+  }
+  function setWorkshopFooterData() {
+    
+    Cookies2.set("domain", jQuery("select#domain").val(), { path: cookiePath, expires: 7 } );
+    Cookies2.set("prefix", jQuery("input#prefix").val().replace(/[^-.a-zA-Z0-9]/g, ''), { path: cookiePath, expires: 7 } );
+    Cookies2.set("userid", jQuery("select#userid").val(), { path: cookiePath, expires: 7 } );
+    replaceClassText();
+    modal.style.display = "none";
+  }
+  function setWorkshopFooterInputValues() {
+    jQuery("select#domain").val(Cookies2.get("domain"));
+    jQuery("input#prefix").val(Cookies2.get("prefix"));
+    jQuery("select#userid").val(Cookies2.get("userid"));
+  }
+  function resetWorkshopFooter() {
+    
+    jQuery("select#domain, select#userid").prop("selectedIndex", 0);
+    jQuery("input#prefix").val(jQuery("input#prefix").attr('placeholder'));
+    
+    Cookies2.set("domain", jQuery("select#domain option").first().val(), { path: cookiePath, expires: 7 } ); 
+    Cookies2.set("userid", jQuery("select#userid option").first().val(), { path: cookiePath, expires: 7 } ); 
+    Cookies2.set("prefix", jQuery("input#prefix").val(), { path: cookiePath, expires: 7 } );
+    
+    
+    replaceClassText();
+  }
+
+
+
+
+  function updateFooter(e){
+    fieldName = '';
+
+    switch(e.id) {
+      case 'userid':
+        fieldName = 'User Id';
+        break;
+      case 'domain':
+        fieldName = 'Domain';
+        break;
+      case 'prefix':
+        fieldName = 'Workshop';
+        break;
+      default:
+        fieldName = 'unknown';
+    }
+    setWorkshopFooterData();
+    toastr["success"](fieldName + " set to " + e.value);
+  }
+
+  jQuery(document).ready(function() {
+    pageLoadWorkshopFooterTest();
+
+
+    
+    var input = document.getElementById("prefix");
+
+    
+    input.addEventListener("keyup", function(event) {
+      
+      if (event.keyCode === 13) {
+        
+        event.preventDefault();
+        
+        
+        updateFooter(input);
+      }
+    });
+
+
+    jQuery("form#footerForm").submit(function() {
+      setWorkshopFooterData();
+      return false; 
+    });
+
+    jQuery("form#footerForm").bind("reset", function() {
+      resetWorkshopFooter();
+      return true;
+    });
+
+    return false;
+  });
+
+</script>
+
+<hr>
+<h3>Workshop Details</h3>
+    <table>
+      <tr>
+        <td class="text-right"><b>Domain</b></td>
+        <td><span class="domain"></span></td>
+        <td rowspan="3">
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
+        </td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Workshop</b></td>
+        <td><span class="prefix"></span></td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Student ID</b></td>
+        <td><span class="userid"></span></td>
+      </tr>
+    </table>
+<button id="myBtn">Configure Workshop</button>
+<hr>
+
+<script>
+
+var modal = document.getElementById("myModal");
+
+
+var btn = document.getElementById("myBtn");
+
+
+var span = document.getElementsByClassName("close")[0];
+
+
+btn.onclick = function() {
+  modal.style.display = "block";
+}
+
+
+span.onclick = function() {
+  modal.style.display = "none";
+}
+
+
+window.onclick = function(event) {
+  if (event.target == modal) {
+    modal.style.display = "none";
+  }
+}
+</script>
+
+
+</div>
+</div>
+</div>
+</div>
+
+
+    
+
+
+
+
+
+
+
+
+<nav>
+  <ul class="pager">
+    
+    
+    <li class="previous">
+      <a href="/workshops/selinux_policy/exercise1.3/">&larr; Previous: Exercise 1.3 - Altering behavior</a>
+    </li>
+    
+    
+    
+    
+    <li class="next">
+      <a href="/workshops/selinux_policy/exercise2.0/">Next: Exercise 2.0 - Creating Custom SELinux Policy &rarr;</a>
+    </li>
+    
+    
+  </ul>
+</nav>
+
+    <p class="text-center">
+      
+      <a href="/workshops/selinux_policy">Return to Workshop</a>
+    </p>
+  </div>
+</div>
+
+    <div id="page-footer" class="container">
+      <p class="text-center">
+        Copyright &copy; 2024 Red Hat, Inc.
+      </p>
+    </div>
+    <script type="text/javascript">
+      if (("undefined" !== typeof _satellite) && ("function" === typeof _satellite.pageBottom)) {
+          _satellite.pageBottom();
+      }
+    </script>
+  </body>
+</html>
diff --git a/workshops/selinux_policy/exercise2.0/index.html b/workshops/selinux_policy/exercise2.0/index.html
index d54a47d32..f3ef58a5d 100644
--- a/workshops/selinux_policy/exercise2.0/index.html
+++ b/workshops/selinux_policy/exercise2.0/index.html
@@ -303,7 +303,7 @@ <h1>Exercise 2.0 - Creating Custom SELinux Policy</h1>
     
     
     <li class="previous">
-      <a href="/workshops/selinux_policy/exercise1.2/">&larr; Previous: Exercise 1.2 - SELinux Contexts</a>
+      <a href="/workshops/selinux_policy/exercise1.4/">&larr; Previous: Exercise 1.4 - Troubleshooting</a>
     </li>
     
     
@@ -324,42 +324,56 @@ <h2 id="_exercise_description">Exercise Description</h2>
 <p>In this exercise, we are going to download the code for the example application that we are going to write policy for, and build and install it onto our test system.</p>
 </div>
 <div class="sect2">
-<h3 id="_step_1_change_directories">Step 1: Change directories</h3>
+<h3 id="_step_1_exit_root_shell">Step 1: Exit root shell</h3>
+<div class="paragraph">
+<p>If you haven’t already, exit the root shell we started in Section 1.  Running <code>whoami</code> should not return <code>root</code>:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>whoami</span></span></code></pre></div>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">ec2-user</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_step_2_change_directories">Step 2: Change directories</h3>
 <div class="paragraph">
 <p>Create a <code>src</code> directory, in your home directory.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cd ~
-mkdir src
-cd src</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cd ~
+</span></span><span style="display:flex;"><span>mkdir src
+</span></span><span style="display:flex;"><span>cd src</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_2_check_out_the_source_code_to_the_example_application_from_github">Step 2: Check out the source code to the example application from GitHub</h3>
+<h3 id="_step_3_check_out_the_source_code_to_the_example_application_from_github">Step 3: Check out the source code to the example application from GitHub</h3>
 <div class="paragraph">
 <p>Download the latest code release</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">git clone https://github.com/ajacocks/selinuxlab.git
-cd selinuxlab</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>git clone https://github.com/ajacocks/selinuxlab.git
+</span></span><span style="display:flex;"><span>cd selinuxlab</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_3_deploy_the_lab_application_with_ansible">Step 3: Deploy the lab application, with Ansible</h3>
+<h3 id="_step_4_deploy_the_lab_application_with_ansible">Step 4: Deploy the lab application, with Ansible</h3>
 <div class="paragraph">
 <p>Now, use Ansible to deploy the test application</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ansible-playbook setup-testapp.yml</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ansible-playbook setup-testapp.yml</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_4_application_and_service_info">Step 4: Application and Service Info</h3>
+<h3 id="_step_5_application_and_service_info">Step 5: Application and Service Info</h3>
 <div class="paragraph">
 <p>Take a look at the application, and the associated service, that you just installed</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ls -l /usr/local/sbin/testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ls -l /usr/local/sbin/testapp</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -367,7 +381,7 @@ <h3 id="_step_4_application_and_service_info">Step 4: Application and Service In
 </div>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl status testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl status testapp</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -378,17 +392,16 @@ <h3 id="_step_4_application_and_service_info">Step 4: Application and Service In
 </div>
 </div>
 <div class="sect2">
-<h3 id="_step_5_start_and_enable_the_service">Step 5: Start and enable the service</h3>
+<h3 id="_step_6_start_and_enable_the_service">Step 6: Start and enable the service</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s file up the application</p>
+<p>Now, let’s fire up the application</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl enable testapp
-sudo systemctl start testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl enable --now testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>We can see that the app has been launched by systemd:
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl status testapp</code></pre></div></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl status testapp</span></span></code></pre></div></p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -405,7 +418,7 @@ <h3 id="_step_5_start_and_enable_the_service">Step 5: Start and enable the servi
 </div>
 <div class="paragraph">
 <p>And, we can also see that the app is running <strong>unconfined</strong>, which means that it is running without an SELinux policy, and can take any action that it wants to:
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ps -efZ | grep testapp | grep -v grep</code></pre></div></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ps -efZ | grep testapp | grep -v grep</span></span></code></pre></div></p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -512,7 +525,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -772,7 +785,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -884,7 +897,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -894,7 +907,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -958,7 +971,7 @@ <h3>Workshop Details</h3>
     
     
     <li class="previous">
-      <a href="/workshops/selinux_policy/exercise1.2/">&larr; Previous: Exercise 1.2 - SELinux Contexts</a>
+      <a href="/workshops/selinux_policy/exercise1.4/">&larr; Previous: Exercise 1.4 - Troubleshooting</a>
     </li>
     
     
@@ -981,7 +994,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise2.1/index.html b/workshops/selinux_policy/exercise2.1/index.html
index 306d156ca..1d74dadda 100644
--- a/workshops/selinux_policy/exercise2.1/index.html
+++ b/workshops/selinux_policy/exercise2.1/index.html
@@ -329,10 +329,10 @@ <h3 id="_step_1_generate_an_initial_generic_selinux_policy">Step 1: Generate an
 <p>Create a policy directory, and generate an initial policy.  Use <code>sepolicy generate</code> to generate a policy for the app that we want to enable.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cd ~/src
-mkdir policy
-cd policy
-sepolicy generate --init /usr/local/sbin/testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cd ~/src
+</span></span><span style="display:flex;"><span>mkdir policy
+</span></span><span style="display:flex;"><span>cd policy
+</span></span><span style="display:flex;"><span>sepolicy generate --init /usr/local/sbin/testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>Note the last few lines in the output from <code>sepolicy generate</code>:</p>
@@ -348,7 +348,7 @@ <h3 id="_step_1_generate_an_initial_generic_selinux_policy">Step 1: Generate an
 </div>
 </div>
 <div class="paragraph">
-<p>You will need all of these files to customize the policy, for the application.</p>
+<p>You will need all of these files to customize the policy for the application.</p>
 </div>
 <div class="olist arabic">
 <div class="title">SELinux Policy Source Compnents</div>
@@ -374,7 +374,7 @@ <h3 id="_step_2_compile_the_policy_framework">Step 2: Compile the policy framewo
 <p>Now, compile and load the SELinux policy framework, by running the <code>testapp.sh</code> script.  The script needs to be run with <strong>root</strong> privileges, since it changes the running SELinux configuration:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ./testapp.sh</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ./testapp.sh</span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>The first 9 lines of the output show the policy compilation, the loading of the policy into memory, and the automatic generation of a manpage for the policy:</p>
@@ -384,9 +384,6 @@ <h3 id="_step_2_compile_the_policy_framework">Step 2: Compile the policy framewo
 <pre class="highlight"><code class="language-bash" data-lang="bash">Building and Loading Policy
 + make -f /usr/share/selinux/devel/Makefile testapp.pp
 Compiling targeted testapp module
-/usr/bin/checkmodule:  loading policy configuration from tmp/testapp.tmp
-/usr/bin/checkmodule:  policy configuration loaded
-/usr/bin/checkmodule:  writing binary representation (version 19) to tmp/testapp.mod
 Creating targeted testapp.pp policy package
 rm tmp/testapp.mod tmp/testapp.mod.fc
 + /usr/sbin/semodule -i testapp.pp
@@ -400,45 +397,51 @@ <h3 id="_step_2_compile_the_policy_framework">Step 2: Compile the policy framewo
 <div class="listingblock">
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">+ /sbin/restorecon -F -R -v /usr/local/sbin/testapp
+Relabeled /usr/local/sbin/testapp from system_u:object_r:bin_t:s0 to system_u:object_r:testapp_exec_t:s0
++ /sbin/restorecon -F -R -v /var/run/testapp.pid
+Relabeled /run/testapp.pid from system_u:object_r:var_run_t:s0 to system_u:object_r:testapp_var_run_t:s0
 ++ pwd
 + pwd=/home/ec2-user/src/policy
-+ rpmbuild --define '_sourcedir /home/ec2-user/src/policy' --define '_specdir /home/ec2-user/src/policy' --define '_builddir /home/ec2-user/src/policy' --define '_srcrpmdir /home/ec2-user/src/policy' --define '_rpmdir /home/ec2-user/src/policy' --define '_buildrootdir /home/ec2-user/src/policy/.build' -ba testapp_selinux.spec
-Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.8GjK3r
++ rpmbuild --define &#39;_sourcedir /home/ec2-user/src/policy&#39; --define &#39;_specdir /home/ec2-user/src/policy&#39; --define &#39;_builddir /home/ec2-user/src/policy&#39; --define &#39;_srcrpmdir /home/ec2-user/src/policy&#39; --define &#39;_rpmdir /home/ec2-user/src/policy&#39; --define &#39;_buildrootdir /home/ec2-user/src/policy/.build&#39; -ba testapp_selinux.spec
+Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.apQ8LZ
 + umask 022
 + cd /home/ec2-user/src/policy
-+ '[' /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64 '!=' / ']'
-+ rm -rf /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64
-++ dirname /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64
++ &#39;[&#39; /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64 &#39;!=&#39; / &#39;]&#39;
++ rm -rf /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64
+++ dirname /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64
 + mkdir -p /home/ec2-user/src/policy/.build
-+ mkdir /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64
-+ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/usr/share/selinux/packages
-+ install -m 644 /home/ec2-user/src/policy/testapp.pp /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/usr/share/selinux/packages
-+ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/usr/share/selinux/devel/include/contrib
-+ install -m 644 /home/ec2-user/src/policy/testapp.if /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/usr/share/selinux/devel/include/contrib/
-+ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/usr/share/man/man8/
-+ install -m 644 /home/ec2-user/src/policy/testapp_selinux.8 /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/usr/share/man/man8/testapp_selinux.8
-+ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64/etc/selinux/targeted/contexts/users/
++ mkdir /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64
++ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/usr/share/selinux/packages
++ install -m 644 /home/ec2-user/src/policy/testapp.pp /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/usr/share/selinux/packages
++ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/usr/share/selinux/devel/include/contrib
++ install -m 644 /home/ec2-user/src/policy/testapp.if /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/usr/share/selinux/devel/include/contrib/
++ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/usr/share/man/man8/
++ install -m 644 /home/ec2-user/src/policy/testapp_selinux.8 /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/usr/share/man/man8/testapp_selinux.8
++ install -d /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64/etc/selinux/targeted/contexts/users/
 + /usr/lib/rpm/check-buildroot
-+ /usr/lib/rpm/redhat/brp-compress
-+ /usr/lib/rpm/redhat/brp-strip /usr/bin/strip
-+ /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
-+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
-+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
-+ /usr/lib/rpm/redhat/brp-python-hardlink
-+ /usr/lib/rpm/redhat/brp-java-repack-jars
-Processing files: testapp_selinux-1.0-1.el7.noarch
-Provides: testapp_selinux = 1.0-1.el7
++ /usr/lib/rpm/redhat/brp-ldconfig
+/sbin/ldconfig: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf: No such file or directory
++ /usr/lib/rpm/brp-compress
++ /usr/lib/rpm/brp-strip /usr/bin/strip
++ /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
++ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
++ /usr/lib/rpm/brp-python-bytecompile &#39;&#39; 1
++ /usr/lib/rpm/brp-python-hardlink
++ PYTHON3=/usr/libexec/platform-python
++ /usr/lib/rpm/redhat/brp-mangle-shebangs
+Processing files: testapp_selinux-1.0-1.el8.noarch
+Provides: testapp_selinux = 1.0-1.el8
 Requires(interp): /bin/sh /bin/sh
 Requires(rpmlib): rpmlib(CompressedFileNames) &lt;= 3.0.4-1 rpmlib(FileDigests) &lt;= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) &lt;= 4.0-1
-Requires(post): /bin/sh policycoreutils selinux-policy-base &gt;= 3.13.1-229
+Requires(post): /bin/sh policycoreutils selinux-policy-base &gt;= 3.14.3-139
 Requires(postun): /bin/sh policycoreutils
-Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64
-Wrote: /home/ec2-user/src/policy/testapp_selinux-1.0-1.el7.src.rpm
-Wrote: /home/ec2-user/src/policy/noarch/testapp_selinux-1.0-1.el7.noarch.rpm
-Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.aqm3qv
+Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64
+Wrote: /home/ec2-user/src/policy/testapp_selinux-1.0-1.el8.src.rpm
+Wrote: /home/ec2-user/src/policy/noarch/testapp_selinux-1.0-1.el8.noarch.rpm
+Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.ql2Cxs
 + umask 022
 + cd /home/ec2-user/src/policy
-+ /usr/bin/rm -rf /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el7.x86_64
++ /usr/bin/rm -rf /home/ec2-user/src/policy/.build/testapp_selinux-1.0-1.el8.x86_64
 + exit 0</code></pre>
 </div>
 </div>
@@ -449,9 +452,9 @@ <h3 id="_step_3_check_to_see_your_policy_in_action">Step 3: Check to see your po
 <p>If we reload the application, the newly compiled and loaded policy module will be attached to it:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl stop testapp
-sudo systemctl start testapp
-ps -efZ | grep testapp | grep -v grep</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl stop testapp
+</span></span><span style="display:flex;"><span>sudo systemctl start testapp
+</span></span><span style="display:flex;"><span>ps -efZ | grep testapp | grep -v grep</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -466,7 +469,7 @@ <h3 id="_step_4_how_does_the_application_end_up_with_the_testapp_t_context">Step
 </div>
 <div class="paragraph">
 <p>To see those rules, type this:
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sesearch -T -s init_t -t testapp_exec_t</code></pre></div></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sesearch -T -s init_t -t testapp_exec_t</span></span></code></pre></div></p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -582,7 +585,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -842,7 +845,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -954,7 +957,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -964,7 +967,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1051,7 +1054,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise2.2/index.html b/workshops/selinux_policy/exercise2.2/index.html
index 7ae168af3..56e32fec6 100644
--- a/workshops/selinux_policy/exercise2.2/index.html
+++ b/workshops/selinux_policy/exercise2.2/index.html
@@ -329,7 +329,7 @@ <h3 id="_step_1_check_for_avc_denials">Step 1: Check for AVC denials</h3>
 <p>Now that our app is up and running, we can check the system logs for AVC (access vector cache, where SELinux caches decisions to grant or deny access) denial messages.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts today</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts today</span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>There will (and should!) be quite a few denials returned from <code>ausearch</code>.  Here are some from the example machine:</p>
@@ -338,57 +338,57 @@ <h3 id="_step_1_check_for_avc_denials">Step 1: Check for AVC denials</h3>
 <div class="content">
 <pre class="highlight"><code class="language-bash" data-lang="bash">----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.764:25971): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.764:25971): arch=c000003e syscall=2 success=yes exit=4 a0=401a32 a1=0 a2=1b6 a3=24 items=0 ppid=1 pid=1022 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.764:25971): avc:  denied  { open } for  pid=1022 comm="testapp" path="/proc/meminfo" dev="proc" ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1552588580.764:25971): avc:  denied  { read } for  pid=1022 comm="testapp" name="meminfo" dev="proc" ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1
+type=PROCTITLE msg=audit(1552588580.764:25971): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.764:25971): arch=c000003e syscall=2 success=yes exit=4 a0=401a32 a1=0 a2=1b6 a3=24 items=0 ppid=1 pid=1022 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.764:25971): avc:  denied  { open } for  pid=1022 comm=&#34;testapp&#34; path=&#34;/proc/meminfo&#34; dev=&#34;proc&#34; ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1552588580.764:25971): avc:  denied  { read } for  pid=1022 comm=&#34;testapp&#34; name=&#34;meminfo&#34; dev=&#34;proc&#34; ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.764:25972): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.764:25972): arch=c000003e syscall=41 success=yes exit=3 a0=a a1=2 a2=0 a3=7ffc9a8c3360 items=0 ppid=1022 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.764:25972): avc:  denied  { create } for  pid=1023 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
+type=PROCTITLE msg=audit(1552588580.764:25972): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.764:25972): arch=c000003e syscall=41 success=yes exit=3 a0=a a1=2 a2=0 a3=7ffc9a8c3360 items=0 ppid=1022 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.764:25972): avc:  denied  { create } for  pid=1023 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.765:25973): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.765:25973): arch=c000003e syscall=4 success=yes exit=0 a0=7f22154460c1 a1=7f22110523f0 a2=7f22110523f0 a3=3 items=0 ppid=1022 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.765:25973): avc:  denied  { getattr } for  pid=1023 comm="testapp" path="/etc/resolv.conf" dev="dm-0" ino=67445450 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
+type=PROCTITLE msg=audit(1552588580.765:25973): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.765:25973): arch=c000003e syscall=4 success=yes exit=0 a0=7f22154460c1 a1=7f22110523f0 a2=7f22110523f0 a3=3 items=0 ppid=1022 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.765:25973): avc:  denied  { getattr } for  pid=1023 comm=&#34;testapp&#34; path=&#34;/etc/resolv.conf&#34; dev=&#34;dm-0&#34; ino=67445450 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.765:25974): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.765:25974): arch=c000003e syscall=2 success=yes exit=3 a0=7f22154460c1 a1=80000 a2=1b6 a3=24 items=0 ppid=1022 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.765:25974): avc:  denied  { open } for  pid=1023 comm="testapp" path="/etc/resolv.conf" dev="dm-0" ino=67445450 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1552588580.765:25974): avc:  denied  { read } for  pid=1023 comm="testapp" name="resolv.conf" dev="dm-0" ino=67445450 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
+type=PROCTITLE msg=audit(1552588580.765:25974): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.765:25974): arch=c000003e syscall=2 success=yes exit=3 a0=7f22154460c1 a1=80000 a2=1b6 a3=24 items=0 ppid=1022 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.765:25974): avc:  denied  { open } for  pid=1023 comm=&#34;testapp&#34; path=&#34;/etc/resolv.conf&#34; dev=&#34;dm-0&#34; ino=67445450 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1552588580.765:25974): avc:  denied  { read } for  pid=1023 comm=&#34;testapp&#34; name=&#34;resolv.conf&#34; dev=&#34;dm-0&#34; ino=67445450 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.765:25975): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.765:25975): arch=c000003e syscall=42 success=yes exit=0 a0=3 a1=7f2211053dcc a2=10 a3=7f22110507a0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.765:25975): avc:  denied  { connect } for  pid=1023 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
+type=PROCTITLE msg=audit(1552588580.765:25975): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.765:25975): arch=c000003e syscall=42 success=yes exit=0 a0=3 a1=7f2211053dcc a2=10 a3=7f22110507a0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.765:25975): avc:  denied  { connect } for  pid=1023 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.766:25976): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.766:25976): arch=c000003e syscall=16 success=yes exit=0 a0=3 a1=541b a2=7f2211050ea0 a3=7f22110507a0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.766:25976): avc:  denied  { getattr } for  pid=1023 comm="testapp" path="socket:[1181449]" dev="sockfs" ino=1181449 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
+type=PROCTITLE msg=audit(1552588580.766:25976): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.766:25976): arch=c000003e syscall=16 success=yes exit=0 a0=3 a1=541b a2=7f2211050ea0 a3=7f22110507a0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.766:25976): avc:  denied  { getattr } for  pid=1023 comm=&#34;testapp&#34; path=&#34;socket:[1181449]&#34; dev=&#34;sockfs&#34; ino=1181449 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.769:25977): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.769:25977): arch=c000003e syscall=41 success=yes exit=3 a0=2 a1=1 a2=6 a3=7ffc9a8c35e0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.769:25977): avc:  denied  { create } for  pid=1023 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=PROCTITLE msg=audit(1552588580.769:25977): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.769:25977): arch=c000003e syscall=41 success=yes exit=3 a0=2 a1=1 a2=6 a3=7ffc9a8c35e0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.769:25977): avc:  denied  { create } for  pid=1023 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.769:25978): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.769:25978): arch=c000003e syscall=42 success=no exit=-115 a0=3 a1=7ffc9a8c38d0 a2=10 a3=7ffc9a8c31e0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.769:25978): avc:  denied  { name_connect } for  pid=1023 comm="testapp" dest=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:http_port_t:s0 tclass=tcp_socket permissive=1
-type=AVC msg=audit(1552588580.769:25978): avc:  denied  { connect } for  pid=1023 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=PROCTITLE msg=audit(1552588580.769:25978): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.769:25978): arch=c000003e syscall=42 success=no exit=-115 a0=3 a1=7ffc9a8c38d0 a2=10 a3=7ffc9a8c31e0 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.769:25978): avc:  denied  { name_connect } for  pid=1023 comm=&#34;testapp&#34; dest=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:http_port_t:s0 tclass=tcp_socket permissive=1
+type=AVC msg=audit(1552588580.769:25978): avc:  denied  { connect } for  pid=1023 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.881:25982): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.881:25982): arch=c000003e syscall=55 success=yes exit=0 a0=3 a1=1 a2=4 a3=7ffc9a8c3b20 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.881:25982): avc:  denied  { getopt } for  pid=1023 comm="testapp" laddr=10.0.1.10 lport=57036 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=PROCTITLE msg=audit(1552588580.881:25982): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.881:25982): arch=c000003e syscall=55 success=yes exit=0 a0=3 a1=1 a2=4 a3=7ffc9a8c3b20 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.881:25982): avc:  denied  { getopt } for  pid=1023 comm=&#34;testapp&#34; laddr=10.0.1.10 lport=57036 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
 ----
 time-&gt;Thu Mar 14 14:36:20 2019
-type=PROCTITLE msg=audit(1552588580.881:25983): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1552588580.881:25983): arch=c000003e syscall=52 success=yes exit=0 a0=3 a1=7ffc9a8c39f0 a2=7ffc9a8c39ec a3=7ffc9a8c3460 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1552588580.881:25983): avc:  denied  { getattr } for  pid=1023 comm="testapp" laddr=10.0.1.10 lport=57036 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1</code></pre>
+type=PROCTITLE msg=audit(1552588580.881:25983): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1552588580.881:25983): arch=c000003e syscall=52 success=yes exit=0 a0=3 a1=7ffc9a8c39f0 a2=7ffc9a8c39ec a3=7ffc9a8c3460 items=0 ppid=1 pid=1023 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1552588580.881:25983): avc:  denied  { getattr } for  pid=1023 comm=&#34;testapp&#34; laddr=10.0.1.10 lport=57036 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1</code></pre>
 </div>
 </div>
 </div>
@@ -404,8 +404,8 @@ <h3 id="_step_1_interpret_avc_messages">Step 1: Interpret AVC messages</h3>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1552588580.764:25971): avc:  denied  { open } for  pid=1022 comm="testapp" path="/proc/meminfo" dev="proc" ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1552588580.764:25971): avc:  denied  { read } for  pid=1022 comm="testapp" name="meminfo" dev="proc" ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1552588580.764:25971): avc:  denied  { open } for  pid=1022 comm=&#34;testapp&#34; path=&#34;/proc/meminfo&#34; dev=&#34;proc&#34; ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1552588580.764:25971): avc:  denied  { read } for  pid=1022 comm=&#34;testapp&#34; name=&#34;meminfo&#34; dev=&#34;proc&#34; ino=4026532040 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -418,8 +418,8 @@ <h3 id="_step_2_find_the_right_interface">Step 2: Find the right interface</h3>
 <p>SELinux interface definitions are located in <code>/usr/share/selinux/devel/include</code>, if you install the <code>selinux-policy-devel</code> package.  If we search for <code>/proc</code>, in files named <code>*.if</code> (interface definitions):</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cd /usr/share/selinux/devel/include
-find . -type f -name <span style="color:#e6db74">&#34;*.if&#34;</span> -exec grep -H <span style="color:#e6db74">&#39;/proc&#39;</span> <span style="color:#f92672">{}</span> <span style="color:#ae81ff">\;</span> | grep <span style="color:#e6db74">&#34;system state information&#34;</span></code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cd /usr/share/selinux/devel/include
+</span></span><span style="display:flex;"><span>find . -type f -name <span style="color:#e6db74">&#34;*.if&#34;</span> -exec grep -H <span style="color:#e6db74">&#39;/proc&#39;</span> <span style="color:#f92672">{}</span> <span style="color:#ae81ff">\;</span> | grep <span style="color:#e6db74">&#34;system state information&#34;</span></span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>We see that in the results, there is a line that says:</p>
@@ -430,7 +430,7 @@ <h3 id="_step_2_find_the_right_interface">Step 2: Find the right interface</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>That makes sense, so let&#8217;s see what interface has that comment.  Searching for it finds this stanza:</p>
+<p>That makes sense, so let’s see what interface has that comment.  Searching for it finds this stanza:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -457,25 +457,25 @@ <h3 id="_step_2_find_the_right_interface">Step 2: Find the right interface</h3>
 ##      nor process state information (/proc/pid).
 ##      &lt;/p&gt;
 ## &lt;/desc&gt;
-## &lt;param name="domain"&gt;
+## &lt;param name=&#34;domain&#34;&gt;
 ##      &lt;summary&gt;
 ##      Domain allowed access.
 ##      &lt;/summary&gt;
 ## &lt;/param&gt;
-## &lt;infoflow type="read" weight="10"/&gt;
+## &lt;infoflow type=&#34;read&#34; weight=&#34;10&#34;/&gt;
 ## &lt;rolecap/&gt;
 #
-interface(`kernel_read_system_state',`
+interface(`kernel_read_system_state&#39;,`
         gen_require(`
                 attribute kernel_system_state_reader;
-        ')
+        &#39;)
 
         typeattribute $1 kernel_system_state_reader;
-')</code></pre>
+&#39;)</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p>This interface takes a single parameter (look in the <strong>&lt;param&#8230;&#8203;&gt;</strong> section), which is the name of the SELinux domain to be allowed access.  In this case, the domain name is <code>testapp</code>, matching the name of our application and policy module.</p>
+<p>This interface takes a single parameter (look in the <strong>&lt;param…​&gt;</strong> section), which is the name of the SELinux domain to be allowed access.  In this case, the domain name is <code>testapp</code>, matching the name of our application and policy module.</p>
 </div>
 </div>
 <div class="sect2">
@@ -489,10 +489,33 @@ <h3 id="_step_3_add_the_interface_to_the_policy">Step 3: Add the interface to th
 </div>
 </div>
 <div class="paragraph">
-<p>The file should now look like this:</p>
+<p>Edit the file and add the line above:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cat ~/src/policy/testapp.te</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>vi ~/src/policy/testapp.te</span></span></code></pre></div>
+</div>
+<div class="paragraph">
+<p><br/></p>
+</div>
+<div class="sidebarblock">
+<div class="content">
+<div class="title">A note on editing files</div>
+<div class="admonitionblock tip">
+<table>
+<tbody><tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+We’ll be making frequent edits to <strong>testapp.te</strong> for the remainder of the workshop.  If we don’t spell it out explicitly, go ahead and re-use the above command each time.  And if <strong>vi</strong> isn’t your cup of tea, feel free to install <strong>nano</strong> or another editor instead.
+</td>
+</tr>
+</tbody></table>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>Be sure to save your changes.  Afterwards, it should now look like this:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -537,32 +560,32 @@ <h3 id="_step_3_add_the_interface_to_the_policy">Step 3: Add the interface to th
 </div>
 </div>
 <div class="paragraph">
-<p>Keeping things in alphabetic order doesn&#8217;t make any difference to SELinux, but makes the file easier to read.</p>
+<p>Keeping things in alphabetic order doesn’t make any difference to SELinux, but makes the file easier to read.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_4_recompile_and_reload_the_policy">Step 4: Recompile and reload the policy</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s recompile the policy, and reload it into memory.</p>
+<p>Now, let’s recompile the policy, and reload it into memory.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cd ~/src/policy
-sudo ./testapp.sh</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cd ~/src/policy
+</span></span><span style="display:flex;"><span>sudo ./testapp.sh</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_5_restart_the_application">Step 5: Restart the application</h3>
 <div class="paragraph">
-<p>To see if that fixed the problem, let&#8217;s restart the application:</p>
+<p>To see if that fixed the problem, let’s restart the application:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>&#8230;&#8203;and see if there are any AVC messages about <code>/proc</code>:</p>
+<p>…​and see if there are any AVC messages about <code>/proc</code>:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts recent | grep meminfo | wc -l</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | grep meminfo | wc -l</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -579,7 +602,7 @@ <h3 id="_step_5_restart_the_application">Step 5: Restart the application</h3>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>We&#8217;ve now made our first additions to the type enforcement file.  Hopefully, this is starting to make sense.  Don&#8217;t hesitate to talk to your instructor about anyything that we have done that isn&#8217;t clear.</p>
+<p>We’ve now made our first additions to the type enforcement file.  Hopefully, this is starting to make sense.  Don’t hesitate to talk to your instructor about anyything that we have done that isn’t clear.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -681,7 +704,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -941,7 +964,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1053,7 +1076,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1063,7 +1086,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1149,7 +1172,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise2.3/index.html b/workshops/selinux_policy/exercise2.3/index.html
index bd83c258e..0bae9d7a3 100644
--- a/workshops/selinux_policy/exercise2.3/index.html
+++ b/workshops/selinux_policy/exercise2.3/index.html
@@ -331,20 +331,20 @@ <h2 id="_section_1_http_port_connectivity">Section 1: HTTP Port Connectivity</h2
 <div class="sect2">
 <h3 id="_step_1_check_for_avc_denials">Step 1: Check for AVC denials</h3>
 <div class="paragraph">
-<p>Let&#8217;s restart our app, to get an updated list of denials.</p>
+<p>Let’s restart our app, to get an updated list of denials.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>Let&#8217;s start with one of the denials that will be present in the audit search results, related to connecting on TCP port 80:</p>
+<p>Let’s start with one of the denials that will be present in the audit search results, related to connecting on TCP port 80:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts recent | grep <span style="color:#e6db74">&#39;dest=80&#39;</span></code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | grep <span style="color:#e6db74">&#39;dest=80&#39;</span></span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553181380.518:2594): avc:  denied  { name_connect } for  pid=31221 comm="testapp" dest=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:http_port_t:s0 tclass=tcp_socket permissive=1</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553181380.518:2594): avc:  denied  { name_connect } for  pid=31221 comm=&#34;testapp&#34; dest=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:http_port_t:s0 tclass=tcp_socket permissive=1</code></pre>
 </div>
 </div>
 <div class="paragraph">
@@ -354,10 +354,10 @@ <h3 id="_step_1_check_for_avc_denials">Step 1: Check for AVC denials</h3>
 <div class="sect2">
 <h3 id="_step_2_interpret_avc_messages">Step 2: Interpret AVC messages</h3>
 <div class="paragraph">
-<p>In the message above, you can see that the system has attempted to connect to a remote host on port 80.  This is something that we want to allow.  So, let&#8217;s search for an interface that would allow this kind of connection.  Since networking is controlled by the kernel, we will search in the kernel directory for interface files related to networking:</p>
+<p>In the message above, you can see that the system has attempted to connect to a remote host on port 80.  This is something that we want to allow.  So, let’s search for an interface that would allow this kind of connection.  Since networking is controlled by the kernel, we will search in the kernel directory for interface files related to networking:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ls /usr/share/selinux/devel/include/kernel/*.if | grep net</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>ls /usr/share/selinux/devel/include/kernel/*.if | grep net</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -366,7 +366,7 @@ <h3 id="_step_2_interpret_avc_messages">Step 2: Interpret AVC messages</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Since this isn&#8217;t an unlabeled network, let&#8217;s look in <code>corenetwork.if</code>.  Since this is a <code>name_connect</code> action, let&#8217;s look for connect and http.  Using those criteria, we find:</p>
+<p>Since this isn’t an unlabeled network, let’s look in <code>corenetwork.if</code>.  Since this is a <code>name_connect</code> action, let’s look for connect and http.  Using those criteria, we find:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -374,19 +374,19 @@ <h3 id="_step_2_interpret_avc_messages">Step 2: Interpret AVC messages</h3>
 ## &lt;summary&gt;
 ##      Make a TCP connection to the http port.
 ## &lt;/summary&gt;
-## &lt;param name="domain"&gt;
+## &lt;param name=&#34;domain&#34;&gt;
 ##      &lt;summary&gt;
 ##      Domain allowed access.
 ##      &lt;/summary&gt;
 ## &lt;/param&gt;
 #
-interface(`corenet_tcp_connect_http_port',`
+interface(`corenet_tcp_connect_http_port&#39;,`
         gen_require(`
                 type http_port_t;
-        ')
+        &#39;)
 
         allow $1 http_port_t:tcp_socket name_connect;
-')</code></pre>
+&#39;)</code></pre>
 </div>
 </div>
 </div>
@@ -404,15 +404,15 @@ <h3 id="_step_3_add_the_interface">Step 3: Add the interface</h3>
 <p>And compile your policy, and restart the service:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ./testapp.sh
-sudo systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ./testapp.sh
+</span></span><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>&#8230;&#8203;and last, check to see if there is still an AVC denial:</p>
+<p>…​and last, check to see if there is still an AVC denial:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl restart testapp
-sudo ausearch -m AVC -ts recent | grep <span style="color:#e6db74">&#39;dest=80&#39;</span> | wc -l</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp
+</span></span><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | grep <span style="color:#e6db74">&#39;dest=80&#39;</span> | wc -l</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -422,6 +422,12 @@ <h3 id="_step_3_add_the_interface">Step 3: Add the interface</h3>
 <div class="paragraph">
 <p>Yes!  Another AVC denial fixed.</p>
 </div>
+<div class="paragraph">
+<p>If you <code>ausearch</code> still shows AVCs above, you can alternatively limit the query to the testapp’s current PID; this should confirm the policy is in effect:</p>
+</div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent -p <span style="color:#66d9ef">$(</span>systemctl show testapp --property<span style="color:#f92672">=</span>MainPID | cut -d<span style="color:#f92672">=</span> -f2<span style="color:#66d9ef">)</span> | grep <span style="color:#e6db74">&#39;dest=80&#39;</span> | wc -l</span></span></code></pre></div>
+</div>
 </div>
 </div>
 </div>
@@ -431,37 +437,37 @@ <h2 id="_section_2_socket_permissions">Section 2: Socket Permissions</h2>
 <div class="sect2">
 <h3 id="_step_1_take_a_shortcut">Step 1: Take a Shortcut!</h3>
 <div class="paragraph">
-<p>Now, we&#8217;re going to move on, temporarily, from interfaces to allow/deny settings, in the <code>testapp.te</code> file.  We have several AVC denials around TCP and UDP socket system calls, that SELinux is blocking.</p>
+<p>Now, we’re going to move on, temporarily, from interfaces to allow/deny settings, in the <code>testapp.te</code> file.  We have several AVC denials around TCP and UDP socket system calls, that SELinux is blocking.</p>
 </div>
 <div class="paragraph">
 <p>The AVCs in question are here (there will likely be more, on your host, but they are all in the same sategory):</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span></code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span></span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553190979.189:2931): avc:  denied  { create } for  pid=2042 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
-type=AVC msg=audit(1553190979.189:2932): avc:  denied  { connect } for  pid=2042 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
-type=AVC msg=audit(1553190979.379:2933): avc:  denied  { getopt } for  pid=2042 comm="testapp" laddr=10.0.2.5 lport=60848 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
-type=AVC msg=audit(1553190979.379:2934): avc:  denied  { getattr } for  pid=2042 comm="testapp" laddr=10.0.2.5 lport=60848 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
-type=AVC msg=audit(1553191083.531:2965): avc:  denied  { create } for  pid=2042 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
-type=AVC msg=audit(1553191083.531:2966): avc:  denied  { connect } for  pid=2042 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
-type=AVC msg=audit(1553191083.548:2967): avc:  denied  { getattr } for  pid=2042 comm="testapp" path="socket:[314409]" dev="sockfs" ino=314409 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553190979.189:2931): avc:  denied  { create } for  pid=2042 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=AVC msg=audit(1553190979.189:2932): avc:  denied  { connect } for  pid=2042 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=AVC msg=audit(1553190979.379:2933): avc:  denied  { getopt } for  pid=2042 comm=&#34;testapp&#34; laddr=10.0.2.5 lport=60848 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=AVC msg=audit(1553190979.379:2934): avc:  denied  { getattr } for  pid=2042 comm=&#34;testapp&#34; laddr=10.0.2.5 lport=60848 faddr=5.9.243.187 fport=80 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=tcp_socket permissive=1
+type=AVC msg=audit(1553191083.531:2965): avc:  denied  { create } for  pid=2042 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
+type=AVC msg=audit(1553191083.531:2966): avc:  denied  { connect } for  pid=2042 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
+type=AVC msg=audit(1553191083.548:2967): avc:  denied  { getattr } for  pid=2042 comm=&#34;testapp&#34; path=&#34;socket:[314409]&#34; dev=&#34;sockfs&#34; ino=314409 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_let_audit2why_interpret_for_you">Step 2: Let <code>audit2why</code> interpret for you</h3>
 <div class="paragraph">
-<p>Next, let&#8217;s ask the system to convert an AVC to English, for us:</p>
+<p>Next, let’s ask the system to convert an AVC to English, for us:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC | egrep <span style="color:#e6db74">&#39;udp&#39;</span> | head -1 | audit2why</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC | egrep <span style="color:#e6db74">&#39;udp&#39;</span> | head -1 | audit2why</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553112150.906:909): avc:  denied  { create } for  pid=9772 comm="testapp" scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
+<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553112150.906:909): avc:  denied  { create } for  pid=9772 comm=&#34;testapp&#34; scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:system_r:testapp_t:s0 tclass=udp_socket permissive=1
 
 	Was caused by:
 		Missing type enforcement (TE) allow rule.
@@ -470,16 +476,16 @@ <h3 id="_step_2_let_audit2why_interpret_for_you">Step 2: Let <code>audit2why</co
 </div>
 </div>
 <div class="paragraph">
-<p>You can see that, in this case, <code>audit2why</code> wasn&#8217;t significantly helpful, other than telling us that we need to add a new <code>allow</code> statement to our <code>testapp.te</code> file.</p>
+<p>You can see that, in this case, <code>audit2why</code> wasn’t significantly helpful, other than telling us that we need to add a new <code>allow</code> statement to our <code>testapp.te</code> file.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_3_use_audit2allow_to_suggest_changes">Step 3: Use <code>audit2allow</code> to suggest changes</h3>
 <div class="paragraph">
-<p>So, now we&#8217;ll take the advice that <code>audit2why</code> gave us, and let <code>audit2allow</code> generate some policy allow statements.  You always have to be careful with <code>audit2allow</code>, since it will generate rules for anything that you feed it, and won&#8217;t necessarily pick the most optimal solution.</p>
+<p>So, now we’ll take the advice that <code>audit2why</code> gave us, and let <code>audit2allow</code> generate some policy allow statements.  You always have to be careful with <code>audit2allow</code>, since it will generate rules for anything that you feed it, and won’t necessarily pick the most optimal solution.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | audit2allow</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | audit2allow</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -495,7 +501,7 @@ <h3 id="_step_3_use_audit2allow_to_suggest_changes">Step 3: Use <code>audit2allo
 <p>The file should now look like this:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cat ~/src/policy/testapp.te</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cat ~/src/policy/testapp.te</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -544,31 +550,31 @@ <h3 id="_step_3_use_audit2allow_to_suggest_changes">Step 3: Use <code>audit2allo
 </div>
 </div>
 <div class="paragraph">
-<p>Keeping things in alphabetic order doesn&#8217;t make any difference to SELinux, but makes the file easier to read.</p>
+<p>Keeping things in alphabetic order doesn’t make any difference to SELinux, but makes the file easier to read.</p>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_4_recompile_and_reload_the_policy">Step 4: Recompile and reload the policy</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s recompile the policy, and reload it into memory.</p>
+<p>Now, let’s recompile the policy, and reload it into memory.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ./testapp.sh</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ./testapp.sh</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_5_restart_the_application">Step 5: Restart the application</h3>
 <div class="paragraph">
-<p>To see if that fixed the problem, let&#8217;s restart the application:</p>
+<p>To see if that fixed the problem, let’s restart the application:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>&#8230;&#8203;and see if there are any AVC messages about TCP or UDP:</p>
+<p>…​and see if there are any AVC messages about TCP or UDP:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | wc -l</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent -p <span style="color:#66d9ef">$(</span>systemctl show testapp --property<span style="color:#f92672">=</span>MainPID | cut -d<span style="color:#f92672">=</span> -f2<span style="color:#66d9ef">)</span> | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | wc -l</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -585,7 +591,7 @@ <h3 id="_step_5_restart_the_application">Step 5: Restart the application</h3>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, we&#8217;re down to only a few more AVC denials to handle.  Hopefully, you&#8217;re getting a handle on how to find appropriate interfaces and allow rules, for SELinux.</p>
+<p>At this point, we’re down to only a few more AVC denials to handle.  Hopefully, you’re getting a handle on how to find appropriate interfaces and allow rules, for SELinux.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -687,7 +693,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -947,7 +953,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1059,7 +1065,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1069,7 +1075,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1155,7 +1161,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise2.4/index.html b/workshops/selinux_policy/exercise2.4/index.html
index 2f3c682f1..1f45eefae 100644
--- a/workshops/selinux_policy/exercise2.4/index.html
+++ b/workshops/selinux_policy/exercise2.4/index.html
@@ -310,7 +310,7 @@ <h1>Exercise 2.4 - Finishing the Policy</h1>
     
     
     <li class="next">
-      <a href="/workshops/selinux_policy/wrapup/">Next: Wrapup &rarr;</a>
+      <a href="/workshops/selinux_policy/exercise2.5/">Next: Exercise 2.5 - Tips &amp; Tricks &rarr;</a>
     </li>
     
     
@@ -331,22 +331,22 @@ <h2 id="_section_1_a_last_ish_interface">Section 1: A Last-ish Interface</h2>
 <div class="sect2">
 <h3 id="_step_1_check_for_avc_denials">Step 1: Check for AVC denials</h3>
 <div class="paragraph">
-<p>Let&#8217;s again restart our app, to get an updated list of denials.</p>
+<p>Let’s again restart our app, to get an updated list of denials.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>We only have a few denials left, and you will see that they all (probably!) reference <code>/etc/resolv.conf</code> or to <code>/etc/hosts</code>.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;^type=AVC&#39;</span></code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;^type=AVC&#39;</span></span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553195947.854:3270): avc:  denied  { getattr } for  pid=4651 comm="testapp" path="/etc/resolv.conf" dev="dm-0" ino=9311517 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1553195947.854:3271): avc:  denied  { open } for  pid=4651 comm="testapp" path="/etc/hosts" dev="dm-0" ino=8389746 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1553195947.854:3271): avc:  denied  { read } for  pid=4651 comm="testapp" name="hosts" dev="dm-0" ino=8389746 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1</code></pre>
+<pre class="highlight"><code class="language-bash" data-lang="bash">type=AVC msg=audit(1553195947.854:3270): avc:  denied  { getattr } for  pid=4651 comm=&#34;testapp&#34; path=&#34;/etc/resolv.conf&#34; dev=&#34;dm-0&#34; ino=9311517 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1553195947.854:3271): avc:  denied  { open } for  pid=4651 comm=&#34;testapp&#34; path=&#34;/etc/hosts&#34; dev=&#34;dm-0&#34; ino=8389746 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1553195947.854:3271): avc:  denied  { read } for  pid=4651 comm=&#34;testapp&#34; name=&#34;hosts&#34; dev=&#34;dm-0&#34; ino=8389746 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1</code></pre>
 </div>
 </div>
 </div>
@@ -382,34 +382,34 @@ <h3 id="_step_2_interpret_avc_messages">Step 2: Interpret AVC messages</h3>
 ##              &lt;li&gt;sysnet_use_portmap()&lt;/li&gt;
 ##      &lt;/ul&gt;
 ## &lt;/desc&gt;
-## &lt;param name="domain"&gt;
+## &lt;param name=&#34;domain&#34;&gt;
 ##      &lt;summary&gt;
 ##      Domain allowed access.
 ##      &lt;/summary&gt;
 ## &lt;/param&gt;
 #
-interface(`sysnet_read_config',`
+interface(`sysnet_read_config&#39;,`
         gen_require(`
                 type net_conf_t;
-        ')
+        &#39;)
 
         files_search_etc($1)
         allow $1 net_conf_t:file read_file_perms;
 
-        ifdef(`distro_debian',`
+        ifdef(`distro_debian&#39;,`
                 files_search_pids($1)
                 allow $1 net_conf_t:dir list_dir_perms;
                 read_files_pattern($1, net_conf_t, net_conf_t)
-        ')
+        &#39;)
 
-        ifdef(`distro_redhat',`
+        ifdef(`distro_redhat&#39;,`
         files_search_all_pids($1)
         init_search_pid_dirs($1)
                 allow $1 net_conf_t:dir list_dir_perms;
                 allow $1 net_conf_t:lnk_file read_lnk_file_perms;
                 read_files_pattern($1, net_conf_t, net_conf_t)
-        ')
-')</code></pre>
+        &#39;)
+&#39;)</code></pre>
 </div>
 </div>
 </div>
@@ -427,15 +427,15 @@ <h3 id="_step_3_add_the_interface">Step 3: Add the interface</h3>
 <p>And compile your policy, and restart the service:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">./testapp.sh
-systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ./testapp.sh
+</span></span><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>&#8230;&#8203;and last, check to see if there are still any AVC denials:</p>
+<p>…​and last, check to see if there are still any AVC denials:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">systemctl restart testapp
-ausearch -m AVC -ts recent | wc -l</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp
+</span></span><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent -p <span style="color:#66d9ef">$(</span>systemctl show testapp --property<span style="color:#f92672">=</span>MainPID | cut -d<span style="color:#f92672">=</span> -f2<span style="color:#66d9ef">)</span> | wc -l</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -443,7 +443,7 @@ <h3 id="_step_3_add_the_interface">Step 3: Add the interface</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Ah, well! Let&#8217;s try to handle those last AVCs.</p>
+<p>Ah, well! Let’s try to handle those last AVCs.</p>
 </div>
 </div>
 </div>
@@ -454,41 +454,41 @@ <h2 id="_section_2_a_last_interface_no_really">Section 2: A Last Interface (no,
 <div class="sect2">
 <h3 id="_step_1_check_for_avc_denials_2">Step 1: Check for AVC denials</h3>
 <div class="paragraph">
-<p>Let&#8217;s get an updated list of denials:</p>
+<p>Let’s get an updated list of denials:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;^type=AVC&#39;</span></code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent -p <span style="color:#66d9ef">$(</span>systemctl show testapp --property<span style="color:#f92672">=</span>MainPID | cut -d<span style="color:#f92672">=</span> -f2<span style="color:#66d9ef">)</span> | egrep <span style="color:#e6db74">&#39;^type=AVC&#39;</span></span></span></code></pre></div>
 </div>
 <div class="paragraph">
 <p>The last few denials should reference <code>openssl</code> and <code>pki</code>:</p>
 </div>
 <div class="listingblock">
 <div class="content">
-<pre class="highlight"><code class="language-bash" data-lang="bash">ausearch -m AVC -ts recent
+<pre class="highlight"><code class="language-bash" data-lang="bash">sudo ausearch -m AVC -ts recent
 ----
 time-&gt;Tue Jun 29 15:36:12 2021
-type=PROCTITLE msg=audit(1624980972.923:10134): proctitle="/usr/local/sbin/testapp"
-type=PATH msg=audit(1624980972.923:10134): item=0 name="/etc/pki/tls/openssl.cnf" inode=5283193 dev=103:02 mode=0100644 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:cert_t:s0 nametype=NORMAL cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
-type=CWD msg=audit(1624980972.923:10134): cwd="/"
-type=SYSCALL msg=audit(1624980972.923:10134): arch=c000003e syscall=257 success=yes exit=3 a0=ffffff9c a1=15c12a0 a2=0 a3=0 items=1 ppid=63073 pid=63074 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1624980972.923:10134): avc:  denied  { open } for  pid=63074 comm="testapp" path="/etc/pki/tls/openssl.cnf" dev="nvme0n1p2" ino=5283193 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1624980972.923:10134): avc:  denied  { read } for  pid=63074 comm="testapp" name="openssl.cnf" dev="nvme0n1p2" ino=5283193 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=file permissive=1
-type=AVC msg=audit(1624980972.923:10134): avc:  denied  { search } for  pid=63074 comm="testapp" name="pki" dev="nvme0n1p2" ino=8410010 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=dir permissive=1
+type=PROCTITLE msg=audit(1624980972.923:10134): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=PATH msg=audit(1624980972.923:10134): item=0 name=&#34;/etc/pki/tls/openssl.cnf&#34; inode=5283193 dev=103:02 mode=0100644 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:cert_t:s0 nametype=NORMAL cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
+type=CWD msg=audit(1624980972.923:10134): cwd=&#34;/&#34;
+type=SYSCALL msg=audit(1624980972.923:10134): arch=c000003e syscall=257 success=yes exit=3 a0=ffffff9c a1=15c12a0 a2=0 a3=0 items=1 ppid=63073 pid=63074 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1624980972.923:10134): avc:  denied  { open } for  pid=63074 comm=&#34;testapp&#34; path=&#34;/etc/pki/tls/openssl.cnf&#34; dev=&#34;nvme0n1p2&#34; ino=5283193 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1624980972.923:10134): avc:  denied  { read } for  pid=63074 comm=&#34;testapp&#34; name=&#34;openssl.cnf&#34; dev=&#34;nvme0n1p2&#34; ino=5283193 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=file permissive=1
+type=AVC msg=audit(1624980972.923:10134): avc:  denied  { search } for  pid=63074 comm=&#34;testapp&#34; name=&#34;pki&#34; dev=&#34;nvme0n1p2&#34; ino=8410010 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=dir permissive=1
 ----
 time-&gt;Tue Jun 29 15:36:12 2021
-type=PROCTITLE msg=audit(1624980972.923:10135): proctitle="/usr/local/sbin/testapp"
-type=SYSCALL msg=audit(1624980972.923:10135): arch=c000003e syscall=5 success=yes exit=0 a0=3 a1=7ffcd2c0c890 a2=7ffcd2c0c890 a3=7fa695266e80 items=0 ppid=63073 pid=63074 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="testapp" exe="/usr/local/sbin/testapp" subj=system_u:system_r:testapp_t:s0 key=(null)
-type=AVC msg=audit(1624980972.923:10135): avc:  denied  { getattr } for  pid=63074 comm="testapp" path="/etc/pki/tls/openssl.cnf" dev="nvme0n1p2" ino=5283193 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=file permissive=1</code></pre>
+type=PROCTITLE msg=audit(1624980972.923:10135): proctitle=&#34;/usr/local/sbin/testapp&#34;
+type=SYSCALL msg=audit(1624980972.923:10135): arch=c000003e syscall=5 success=yes exit=0 a0=3 a1=7ffcd2c0c890 a2=7ffcd2c0c890 a3=7fa695266e80 items=0 ppid=63073 pid=63074 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=&#34;testapp&#34; exe=&#34;/usr/local/sbin/testapp&#34; subj=system_u:system_r:testapp_t:s0 key=(null)
+type=AVC msg=audit(1624980972.923:10135): avc:  denied  { getattr } for  pid=63074 comm=&#34;testapp&#34; path=&#34;/etc/pki/tls/openssl.cnf&#34; dev=&#34;nvme0n1p2&#34; ino=5283193 scontext=system_u:system_r:testapp_t:s0 tcontext=system_u:object_r:cert_t:s0 tclass=file permissive=1</code></pre>
 </div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_2_find_an_interface">Step 2: Find an interface</h3>
 <div class="paragraph">
-<p>Let&#8217;s search for an interface, referencing <code>ssl certificate</code> and <code>read</code> as that&#8217;s what&#8217;s being reported:</p>
+<p>Let’s search for an interface, referencing <code>ssl certificate</code> and <code>read</code> as that’s what’s being reported:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">find /usr/share/selinux/devel/include -type f -name <span style="color:#e6db74">&#34;*.if&#34;</span> -exec grep -iH <span style="color:#e6db74">&#39;ssl certificate&#39;</span> <span style="color:#f92672">{}</span> <span style="color:#ae81ff">\;</span> | grep -i read</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>find /usr/share/selinux/devel/include -type f -name <span style="color:#e6db74">&#34;*.if&#34;</span> -exec grep -iH <span style="color:#e6db74">&#39;ssl certificate&#39;</span> <span style="color:#f92672">{}</span> <span style="color:#ae81ff">\;</span> | grep -i read</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -500,7 +500,7 @@ <h3 id="_step_2_find_an_interface">Step 2: Find an interface</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>From the list above, we aren&#8217;t touching <code>home directories</code>, so the others are involved with reading SSL certificates. Let&#8217;s open <code>miscfiles.if</code> and see what we can find, that matches the most basic, <code>Read generic SSL certificates</code>:</p>
+<p>From the list above, we aren’t touching <code>home directories</code>, so the others are involved with reading SSL certificates. Let’s open <code>miscfiles.if</code> and see what we can find, that matches the most basic, <code>Read generic SSL certificates</code>:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -508,14 +508,14 @@ <h3 id="_step_2_find_an_interface">Step 2: Find an interface</h3>
 ## &lt;summary&gt;
 ##      Read generic SSL certificates.
 ## &lt;/summary&gt;
-## &lt;param name="domain"&gt;
+## &lt;param name=&#34;domain&#34;&gt;
 ##      &lt;summary&gt;
 ##      Domain allowed access.
 ##      &lt;/summary&gt;
 ## &lt;/param&gt;
 ## &lt;rolecap/&gt;
 #
-interface(`miscfiles_read_generic_certs',`</code></pre>
+interface(`miscfiles_read_generic_certs&#39;,`</code></pre>
 </div>
 </div>
 </div>
@@ -533,25 +533,25 @@ <h3 id="_step_3_add_the_interface_2">Step 3: Add the interface</h3>
 <div class="sect2">
 <h3 id="_step_4_recompile_the_policy">Step 4: Recompile the policy</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s recompile the policy, and reload it into memory.</p>
+<p>Now, let’s recompile the policy, and reload it into memory.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">./testapp.sh</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ./testapp.sh</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_5_restart_the_application">Step 5: Restart the application</h3>
 <div class="paragraph">
-<p>To see if that fixed the problem, let&#8217;s restart the application:</p>
+<p>To see if that fixed the problem, let’s restart the application:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>&#8230;&#8203;and see if there are any AVC messages left:</p>
+<p>…​and see if there are any AVC messages left:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | wc -l</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | wc -l</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -559,7 +559,7 @@ <h3 id="_step_5_restart_the_application">Step 5: Restart the application</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>Fantastic, we&#8217;ve knocked them all out.</p>
+<p>Fantastic, we’ve knocked them all out.</p>
 </div>
 </div>
 </div>
@@ -581,7 +581,7 @@ <h3 id="_step_1_change_the_domain_to_enforcing">Step 1: Change the Domain to Enf
 <p>Once we do that, the final version of your policy should look like this:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cat testapp.te</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cat testapp.te</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -596,7 +596,7 @@ <h3 id="_step_1_change_the_domain_to_enforcing">Step 1: Change the Domain to Enf
 type testapp_exec_t;
 init_daemon_domain(testapp_t, testapp_exec_t)
 
-permissive testapp_t;
+#permissive testapp_t;
 
 type testapp_var_run_t;
 files_pid_file(testapp_var_run_t)
@@ -636,25 +636,25 @@ <h3 id="_step_1_change_the_domain_to_enforcing">Step 1: Change the Domain to Enf
 <div class="sect2">
 <h3 id="_step_3_recompile_and_reload_the_policy">Step 3: Recompile and reload the policy</h3>
 <div class="paragraph">
-<p>Now, let&#8217;s recompile the policy, and reload it into memory.</p>
+<p>Now, let’s recompile the policy, and reload it into memory.</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">./testapp.sh</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ./testapp.sh</span></span></code></pre></div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_step_4_restart_the_application">Step 4: Restart the application</h3>
 <div class="paragraph">
-<p>To see if that fixed the problem, let&#8217;s restart the application:</p>
+<p>To see if that fixed the problem, let’s restart the application:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">systemctl restart testapp</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo systemctl restart testapp</span></span></code></pre></div>
 </div>
 <div class="paragraph">
-<p>&#8230;&#8203;and see if there are any AVC messages left:</p>
+<p>…​and see if there are any AVC messages left:</p>
 </div>
 <div class="paragraph">
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | wc -l</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo ausearch -m AVC -ts recent | egrep <span style="color:#e6db74">&#39;tcp|udp&#39;</span> | wc -l</span></span></code></pre></div>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -662,16 +662,13 @@ <h3 id="_step_4_restart_the_application">Step 4: Restart the application</h3>
 </div>
 </div>
 <div class="paragraph">
-<p>And we are done.</p>
-</div>
-</div>
+<p>Additionally, you can confirm that there aren’t any domains in permissive mode:</p>
 </div>
+<div class="paragraph">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>sudo semanage permissive -l</span></span></code></pre></div>
 </div>
-<div class="sect1">
-<h2 id="_end_result">End Result</h2>
-<div class="sectionbody">
 <div class="paragraph">
-<p>This is the conclusion of the SELinux policy workshop.  Please ask any questions that you have left, and thanks so much for coming!</p>
+<p>And we are done.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -773,7 +770,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1033,7 +1030,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1145,7 +1142,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1155,7 +1152,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1202,6 +1199,7 @@ <h3>Workshop Details</h3>
 </div>
 </div>
 </div>
+</div>
 
 
     
@@ -1225,7 +1223,7 @@ <h3>Workshop Details</h3>
     
     
     <li class="next">
-      <a href="/workshops/selinux_policy/wrapup/">Next: Wrapup &rarr;</a>
+      <a href="/workshops/selinux_policy/exercise2.5/">Next: Exercise 2.5 - Tips &amp; Tricks &rarr;</a>
     </li>
     
     
@@ -1241,7 +1239,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/exercise2.5/index.html b/workshops/selinux_policy/exercise2.5/index.html
new file mode 100644
index 000000000..a302c1aae
--- /dev/null
+++ b/workshops/selinux_policy/exercise2.5/index.html
@@ -0,0 +1,967 @@
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <meta charset="utf-8" />
+    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+    <title>Exercise 2.5 - Tips &amp; Tricks | Red Hat | Public Sector</title>
+
+    
+    
+    <link rel="stylesheet" href="/node_modules/patternfly/dist/css/patternfly.min.css" />
+    <link rel="stylesheet" href="/node_modules/patternfly/dist/css/patternfly-additions.min.css" />
+
+    
+    <link rel="stylesheet" href="/node_modules/highlight.js/styles/darkula.css" />
+
+    
+    <link rel="stylesheet" href="/css/main.css" />
+    <link rel="stylesheet" href="/css/asciidoc.css" />
+    <link rel="stylesheet" href="/css/custom.css" />
+    <link rel="stylesheet" href="/css/toastr.min.css" />
+
+    
+    <script async src="https://www.googletagmanager.com/gtag/js?id=G-DL741MBBZQ"></script>
+    <script>
+      window.dataLayer = window.dataLayer || [];
+      function gtag(){dataLayer.push(arguments);}
+      gtag('js', new Date());
+
+      gtag('config', 'G-DL741MBBZQ');
+    </script>
+
+    
+    <script id="adobe_dtm" src="//www.redhat.com/dtm.js" type="text/javascript"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/jquery/dist/jquery.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap/dist/js/bootstrap.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/c3/c3.min.js"></script>
+    <script src="/node_modules/patternfly/node_modules/d3/d3.min.js"></script>
+
+    
+    
+    <script src="/node_modules/patternfly/node_modules/datatables/media/js/jquery.dataTables.min.js"></script>
+    <script src="/node_modules/patternfly/node_modules/drmonty-datatables-colvis/js/dataTables.colVis.js"></script>
+    <script src="/node_modules/patternfly/node_modules/datatables.net-colreorder/js/dataTables.colReorder.js"></script>
+
+    
+    
+    <script src="/node_modules/patternfly/dist/js/patternfly.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/patternfly-bootstrap-combobox/js/bootstrap-combobox.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-datepicker/dist/js/bootstrap-datepicker.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/moment/min/moment.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/eonasdan-bootstrap-datetimepicker/build/js/bootstrap-datetimepicker.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-select/dist/js/bootstrap-select.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-switch/dist/js/bootstrap-switch.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/bootstrap-touchspin/dist/jquery.bootstrap-touchspin.min.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/patternfly-bootstrap-treeview/dist/bootstrap-treeview.min.js"></script>
+
+    
+    <script src="https://cdn.rawgit.com/google/code-prettify/master/loader/run_prettify.js"></script>
+
+    
+    <script src="/node_modules/patternfly/node_modules/jquery-match-height/dist/jquery.matchHeight-min.js"></script>
+    
+    <script src="/js/clipboard.min.js"></script>
+    <script src="/js/clip.js"></script>
+
+    
+    <script src="/js/toastr.min.js"></script>
+
+    
+    <script src="/node_modules/highlight.js/lib/highlight.js"></script>
+    <script>hljs.initHighlightingOnLoad();</script>
+  </head>
+  <body class="">
+    
+
+<nav class="navbar navbar-default navbar-inverse navbar-fixed-top " role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse-1">
+        <span class="sr-only">Toggle navigation</span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="/">
+      <svg width=150 height=auto id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 613 145"><defs><style>.cls-1{fill:#e00;}.cls-2{fill:#fff;}</style></defs><path class="cls-1" d="M127.47,83.49c12.51,0,30.61-2.58,30.61-17.46a14,14,0,0,0-.31-3.42l-7.45-32.36c-1.72-7.12-3.23-10.35-15.73-16.6C124.89,8.69,103.76.5,97.51.5,91.69.5,90,8,83.06,8c-6.68,0-11.64-5.6-17.89-5.6-6,0-9.91,4.09-12.93,12.5,0,0-8.41,23.72-9.49,27.16A6.43,6.43,0,0,0,42.53,44c0,9.22,36.3,39.45,84.94,39.45M160,72.07c1.73,8.19,1.73,9.05,1.73,10.13,0,14-15.74,21.77-36.43,21.77C78.54,104,37.58,76.6,37.58,58.49a18.45,18.45,0,0,1,1.51-7.33C22.27,52,.5,55,.5,74.22c0,31.48,74.59,70.28,133.65,70.28,45.28,0,56.7-20.48,56.7-36.65,0-12.72-11-27.16-30.83-35.78"/><path d="M160,72.07c1.73,8.19,1.73,9.05,1.73,10.13,0,14-15.74,21.77-36.43,21.77C78.54,104,37.58,76.6,37.58,58.49a18.45,18.45,0,0,1,1.51-7.33l3.66-9.06A6.43,6.43,0,0,0,42.53,44c0,9.22,36.3,39.45,84.94,39.45,12.51,0,30.61-2.58,30.61-17.46a14,14,0,0,0-.31-3.42Z"/><path class="cls-2" d="M579.74,92.8c0,11.89,7.15,17.67,20.19,17.67a52.11,52.11,0,0,0,11.89-1.68V95a24.84,24.84,0,0,1-7.68,1.16c-5.37,0-7.36-1.68-7.36-6.73V68.3h15.56V54.1H596.78v-18l-17,3.68V54.1H568.49V68.3h11.25Zm-53,.32c0-3.68,3.69-5.47,9.26-5.47a43.12,43.12,0,0,1,10.1,1.26v7.15a21.51,21.51,0,0,1-10.63,2.63c-5.46,0-8.73-2.1-8.73-5.57m5.2,17.56c6,0,10.84-1.26,15.36-4.31v3.37h16.82V74.08c0-13.56-9.14-21-24.39-21-8.52,0-16.94,2-26,6.1l6.1,12.52c6.52-2.74,12-4.42,16.83-4.42,7,0,10.62,2.73,10.62,8.31v2.73a49.53,49.53,0,0,0-12.62-1.58c-14.31,0-22.93,6-22.93,16.73,0,9.78,7.78,17.24,20.19,17.24m-92.44-.94h18.09V80.92h30.29v28.82H506V36.12H487.93V64.41H457.64V36.12H439.55ZM370.62,81.87c0-8,6.31-14.1,14.62-14.1A17.22,17.22,0,0,1,397,72.09V91.54A16.36,16.36,0,0,1,385.24,96c-8.2,0-14.62-6.1-14.62-14.09m26.61,27.87h16.83V32.44l-17,3.68V57.05a28.3,28.3,0,0,0-14.2-3.68c-16.19,0-28.92,12.51-28.92,28.5a28.25,28.25,0,0,0,28.4,28.6,25.12,25.12,0,0,0,14.93-4.83ZM320,67c5.36,0,9.88,3.47,11.67,8.83H308.47C310.15,70.3,314.36,67,320,67M291.33,82c0,16.2,13.25,28.82,30.28,28.82,9.36,0,16.2-2.53,23.25-8.42l-11.26-10c-2.63,2.74-6.52,4.21-11.14,4.21a14.39,14.39,0,0,1-13.68-8.83h39.65V83.55c0-17.67-11.88-30.39-28.08-30.39a28.57,28.57,0,0,0-29,28.81M262,51.58c6,0,9.36,3.78,9.36,8.31S268,68.2,262,68.2H244.11V51.58Zm-36,58.16h18.09V82.92h13.77l13.89,26.82H292l-16.2-29.45a22.27,22.27,0,0,0,13.88-20.72c0-13.25-10.41-23.45-26-23.45H226Z"/></svg>
+      </a>
+    </div>
+    <div class="collapse navbar-collapse navbar-collapse-1">
+      <ul class="nav navbar-nav navbar-right">
+        
+        
+          
+            <li>
+              <a href="/">Home</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="/about/">About</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="/contact/">Contact</a>
+            </li>
+          
+        
+          
+            <li>
+              <a href="https://www.redhat.com/en/events">Events</a>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                Workshops <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/agile_integrations_ci/">Agile Integrations Workshop - Citizen Integrator</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/agile_integrations_dev/">Agile Integrations Workshop - Developer</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/ansible_automation/">Ansible Automation Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/ansible_tower_intro/">Ansible Tower - an Introduction</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_container_intro/">Container Security - A Practical Introduction</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/containers_101/">Containers 101 Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/secure_software_factory/">DevSecOps Workshop - Secure Software Factory</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/containers_the_hard_way/">Linux Containers the Hard Way</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/strangling_the_monolith/">Microservices Workshop - Strangling the Monolith</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_4_101/">OpenShift 4 101</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_4_101_dynatrace/">OpenShift 4 101 w/Dynatrace</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_serverless/">OpenShift Serverless</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_service_mesh/">OpenShift Service Mesh</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/rhel_8/">Red Hat Enterprise Linux 8</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/selinux_policy/">SELinux Policy Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_service_mesh_v1.0/">zOpenShift Service Mesh</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                alpha <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/alpha/ansible_with_rhocp_edge/">Applied Ansible Automation - Containerized Edge Workshop</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+          
+            <li class="dropdown">
+              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
+                Retired <b class="caret"></b>
+              </a>
+              <ul class="dropdown-menu">
+                
+                  <li>
+                    <a href="/workshops/ansible_tower_azure/">Ansible Tower Workshop on Azure</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/cloudforms41/">CloudForms Workshops</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_containers/">Container Security Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/jdv_dev/">JBoss Data Virtualization Development</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/openshift_101_dcmetromap/">OpenShift 101 - DC Metro Map Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/security_openshift/">OpenShift Security Workshop</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/rhosp_101/">Red Hat OpenStack Platform 101</a>
+                  </li>
+                
+                  <li>
+                    <a href="/workshops/source_to_image/">Source to Image</a>
+                  </li>
+                
+              </ul>
+            </li>
+          
+        
+      </ul>
+    </div>
+  </div>
+</nav>
+
+
+
+<div class="jumbotron jumbotron-page text-center">
+  <h1>Exercise 2.5 - Tips &amp; Tricks</h1>
+</div>
+
+<div class="container">
+  <div class="row">
+    <p class="text-center">
+      
+      <a href="/workshops/selinux_policy">Return to Workshop</a>
+    </p>
+
+    
+
+
+
+
+
+
+
+
+<nav>
+  <ul class="pager">
+    
+    
+    <li class="previous">
+      <a href="/workshops/selinux_policy/exercise2.4/">&larr; Previous: Exercise 2.4 - Finishing the Policy</a>
+    </li>
+    
+    
+    
+    
+    <li class="next">
+      <a href="/workshops/selinux_policy/wrapup/">Next: Wrapup &rarr;</a>
+    </li>
+    
+    
+  </ul>
+</nav>
+
+    <h1 id="_tips_tricks" class="sect0">Tips &amp; tricks</h1>
+<div class="paragraph">
+<p>This is the conclusion of the SELinux policy workshop.  Here’s some closing tips to help you work with SELinux.
+Please ask any questions that you have left, and thanks so much for coming!</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Set a folder’s context to mimic another:</p>
+</li>
+</ul>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>mkdir -p /var/new_www/html
+matchpathcon /var/www/html /var/new_www/html
+semanage fcontext -a -e /var/www /var/new_www
+restorecon -Rv /var/</pre>
+</div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>List ports associated with all service domains:</p>
+</li>
+</ul>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>semanage port -l</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And then, add a port to an existing service’s domain, such as httpd:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-bash" data-lang="bash">semanage port -a -t http_port_t -p tcp 8888</code></pre>
+</div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Cause entire system to be re-labeled at next boot:</p>
+</li>
+</ul>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>fixfiles onboot</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>or</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>touch /.autorelabel</pre>
+</div>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Get detail reports of access errors (requires optional <strong>setroubleshoot</strong> package):</p>
+</li>
+</ul>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>sealert -l &#34;*&#34;</pre>
+</div>
+</div>
+<div class="paragraph">
+<style>
+
+ 
+.modal {
+  display: none;  
+  position: fixed;  
+  z-index: 1;  
+  left: 0;
+  top: 0;
+  width: 100%;  
+  height: 100%;  
+  overflow: auto;  
+  background-color: rgb(0,0,0);  
+  background-color: rgba(0,0,0,0.4);  
+  -webkit-animation-name: fadeIn;  
+  -webkit-animation-duration: 0.4s;
+  animation-name: fadeIn;
+  animation-duration: 0.4s
+}
+
+ 
+.modal-content {
+  position: fixed;
+  bottom: 0;
+  background-color: #fefefe;
+  width: 100%;
+  -webkit-animation-name: slideIn;
+  -webkit-animation-duration: 0.4s;
+  animation-name: slideIn;
+  animation-duration: 0.4s
+}
+
+ 
+.close {
+  color: white;
+  float: right;
+  font-size: 28px;
+  font-weight: bold;
+}
+
+.close:hover,
+.close:focus {
+  color: #000;
+  text-decoration: none;
+  cursor: pointer;
+}
+
+.modal-header {
+  padding: 2px 16px;
+  background-color: #000000;
+  color: white;
+}
+
+.modal-body {padding: 2px 16px;}
+
+.modal-footer {
+  padding: 2px 16px;
+  background-color: #000000;
+  color: white;
+}
+
+ 
+@-webkit-keyframes slideIn {
+  from {bottom: -300px; opacity: 0}
+  to {bottom: 0; opacity: 1}
+}
+
+@keyframes slideIn {
+  from {bottom: -300px; opacity: 0}
+  to {bottom: 0; opacity: 1}
+}
+
+@-webkit-keyframes fadeIn {
+  from {opacity: 0}
+  to {opacity: 1}
+}
+
+@keyframes fadeIn {
+  from {opacity: 0}
+  to {opacity: 1}
+}
+</style>
+
+<div id="myModal" class="modal">
+
+  
+  <div class="modal-content">
+    <div class="modal-header">
+      <span class="close">&times;</span>
+      <h3>Workshop Details</h3>
+    </div>
+    <div class="modal-body">
+<div class="row">
+  <div class="col-lg-4 col-md-5 col-sm-12" id="workshopFooterDetails">
+    <table>
+      <tr>
+        <td class="text-right"><b>Domain</b></td>
+        <td><span class="domain"></span></td>
+        <td rowspan="3">
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
+        </td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Workshop</b></td>
+        <td><span class="prefix"></span></td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Student ID</b></td>
+        <td><span class="userid"></span></td>
+      </tr>
+    </table>
+  </div>
+  <div class="col-lg-8 col-md-7 col-sm-12">
+    <form id="footerForm" onsubmit="return false;" class="row" style="padding: 1.75rem 0 0 0;">
+      <div class="form-group col-sm-6 col-md-6 col-lg-2">
+        <label for="userid">Student ID</label>
+        <select id="userid" name="userid">
+          <option value="0">0</option>
+          <option value="1">1</option>
+          <option value="2">2</option>
+          <option value="3">3</option>
+          <option value="4">4</option>
+          <option value="5">5</option>
+          <option value="6">6</option>
+          <option value="7">7</option>
+          <option value="8">8</option>
+          <option value="9">9</option>
+          <option value="10">10</option>
+          <option value="11">11</option>
+          <option value="12">12</option>
+          <option value="13">13</option>
+          <option value="14">14</option>
+          <option value="15">15</option>
+          <option value="16">16</option>
+          <option value="17">17</option>
+          <option value="18">18</option>
+          <option value="19">19</option>
+          <option value="20">20</option>
+          <option value="21">21</option>
+          <option value="22">22</option>
+          <option value="23">23</option>
+          <option value="24">24</option>
+          <option value="25">25</option>
+          <option value="26">26</option>
+          <option value="27">27</option>
+          <option value="28">28</option>
+          <option value="29">29</option>
+          <option value="30">30</option>
+          <option value="31">31</option>
+          <option value="32">32</option>
+          <option value="33">33</option>
+          <option value="34">34</option>
+          <option value="35">35</option>
+          <option value="36">36</option>
+          <option value="37">37</option>
+          <option value="38">38</option>
+          <option value="39">39</option>
+          <option value="40">40</option>
+          <option value="41">41</option>
+          <option value="42">42</option>
+          <option value="43">43</option>
+          <option value="44">44</option>
+          <option value="45">45</option>
+          <option value="46">46</option>
+          <option value="47">47</option>
+          <option value="48">48</option>
+          <option value="49">49</option>
+          <option value="50">50</option>
+          <option value="51">51</option>
+          <option value="52">52</option>
+          <option value="53">53</option>
+          <option value="54">54</option>
+          <option value="55">55</option>
+          <option value="56">56</option>
+          <option value="57">57</option>
+          <option value="58">58</option>
+          <option value="59">59</option>
+          <option value="60">60</option>
+          <option value="61">61</option>
+          <option value="62">62</option>
+          <option value="63">63</option>
+          <option value="64">64</option>
+          <option value="65">65</option>
+          <option value="66">66</option>
+          <option value="67">67</option>
+          <option value="68">68</option>
+          <option value="69">69</option>
+          <option value="70">70</option>
+          <option value="71">71</option>
+          <option value="72">72</option>
+          <option value="73">73</option>
+          <option value="74">74</option>
+          <option value="75">75</option>
+          <option value="76">76</option>
+          <option value="77">77</option>
+          <option value="78">78</option>
+          <option value="79">79</option>
+          <option value="80">80</option>
+          <option value="81">81</option>
+          <option value="82">82</option>
+          <option value="83">83</option>
+          <option value="84">84</option>
+          <option value="85">85</option>
+          <option value="86">86</option>
+          <option value="87">87</option>
+          <option value="88">88</option>
+          <option value="89">89</option>
+          <option value="90">90</option>
+          <option value="91">91</option>
+          <option value="92">92</option>
+          <option value="93">93</option>
+          <option value="94">94</option>
+          <option value="95">95</option>
+          <option value="96">96</option>
+          <option value="97">97</option>
+          <option value="98">98</option>
+          <option value="99">99</option>
+          <option value="100">100</option>
+          <option value="101">101</option>
+          <option value="102">102</option>
+          <option value="103">103</option>
+          <option value="104">104</option>
+          <option value="105">105</option>
+          <option value="106">106</option>
+          <option value="107">107</option>
+          <option value="108">108</option>
+          <option value="109">109</option>
+          <option value="110">110</option>
+          <option value="111">111</option>
+          <option value="112">112</option>
+          <option value="113">113</option>
+          <option value="114">114</option>
+          <option value="115">115</option>
+          <option value="116">116</option>
+          <option value="117">117</option>
+          <option value="118">118</option>
+          <option value="119">119</option>
+          <option value="120">120</option>
+          <option value="121">121</option>
+          <option value="122">122</option>
+          <option value="123">123</option>
+          <option value="124">124</option>
+          <option value="125">125</option>
+          <option value="126">126</option>
+          <option value="127">127</option>
+          <option value="128">128</option>
+          <option value="129">129</option>
+          <option value="130">130</option>
+          <option value="131">131</option>
+          <option value="132">132</option>
+          <option value="133">133</option>
+          <option value="134">134</option>
+          <option value="135">135</option>
+          <option value="136">136</option>
+          <option value="137">137</option>
+          <option value="138">138</option>
+          <option value="139">139</option>
+          <option value="140">140</option>
+          <option value="141">141</option>
+          <option value="142">142</option>
+          <option value="143">143</option>
+          <option value="144">144</option>
+          <option value="145">145</option>
+          <option value="146">146</option>
+          <option value="147">147</option>
+          <option value="148">148</option>
+          <option value="149">149</option>
+          <option value="150">150</option>
+          <option value="151">151</option>
+          <option value="152">152</option>
+          <option value="153">153</option>
+          <option value="154">154</option>
+          <option value="155">155</option>
+          <option value="156">156</option>
+          <option value="157">157</option>
+          <option value="158">158</option>
+          <option value="159">159</option>
+          <option value="160">160</option>
+          <option value="161">161</option>
+          <option value="162">162</option>
+          <option value="163">163</option>
+          <option value="164">164</option>
+          <option value="165">165</option>
+          <option value="166">166</option>
+          <option value="167">167</option>
+          <option value="168">168</option>
+          <option value="169">169</option>
+          <option value="170">170</option>
+          <option value="171">171</option>
+          <option value="172">172</option>
+          <option value="173">173</option>
+          <option value="174">174</option>
+          <option value="175">175</option>
+          <option value="176">176</option>
+          <option value="177">177</option>
+          <option value="178">178</option>
+          <option value="179">179</option>
+          <option value="180">180</option>
+          <option value="181">181</option>
+          <option value="182">182</option>
+          <option value="183">183</option>
+          <option value="184">184</option>
+          <option value="185">185</option>
+          <option value="186">186</option>
+          <option value="187">187</option>
+          <option value="188">188</option>
+          <option value="189">189</option>
+          <option value="190">190</option>
+          <option value="191">191</option>
+          <option value="192">192</option>
+          <option value="193">193</option>
+          <option value="194">194</option>
+          <option value="195">195</option>
+          <option value="196">196</option>
+          <option value="197">197</option>
+          <option value="198">198</option>
+          <option value="199">199</option>
+          <option value="200">200</option>
+        </select>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-4">
+        <label for="domain">Domain</label>
+        <select id="domain" name="domain">
+          <option value="rhnaps.io">rhnaps.io</option>
+          <option value="redhatgov.io">redhatgov.io</option>
+          <option value="az.redhatgov.io">az.redhatgov.io</option>
+          <option value="redhat-fierce.io">redhat-fierce.io</option>
+          <option value="fiercesw.network">fiercesw.network</option>
+          <option value="rhtps.io">rhtps.io</option>
+          <option value="openshiftworkshop.com">openshiftworkshop.com</option>
+          <option value="redhatpsmwsa.com">redhatpsmwsa.com</option>
+          <option value="open.redhat.com">open.redhat.com</option>
+          <option value="opentlc.com">opentlc.com</option>
+          <option value="aroapp.io">aroapp.io</option>
+          <option value="danclark.io">danclark.io</option>
+        </select>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-3">
+        <label for="prefix">Workshop</label>
+        <input id="prefix" name="prefix" type="text" size="16" class="form-control" placeholder="example" onkeyup="this.value = this.value.toLowerCase();this.value = this.value.replace(/[^-.a-zA-Z0-9]/g, '');"/>
+      </div>
+      <div class="form-group col-sm-6 col-md-6 col-lg-3">
+        <button type="submit" class="btn btn-primary form-control" style="margin-bottom:1rem;">Enter</button>
+        <button type="reset" class="btn btn-default form-control">Default</button>
+      </div>
+    </form>
+  </div>
+</div>
+
+    </div>
+    <div class="modal-footer">
+      <h3></h3>
+    </div>
+  </div>
+
+</div>
+
+<script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
+<script type="text/javascript">
+
+  
+  var Cookies2 = Cookies.noConflict();
+
+  var cookiePathArr = cleanArray(window.location.pathname.split('/'));
+  var cookiePath = '/' + cookiePathArr[0] + '/' + cookiePathArr[1] + '/';
+
+  function cleanArray(actual) {
+    var newArray = new Array();
+    for (var i = 0; i < actual.length; i++) {
+      if (actual[i]) {
+        newArray.push(actual[i]);
+      }
+    }
+    return newArray;
+  }
+  function replaceClassText() {
+    jQuery("span.domain").html(Cookies2.get("domain"));
+    jQuery("span.userid").html(Cookies2.get("userid"));
+    jQuery("span.prefix").html(Cookies2.get("prefix"));
+  }
+  function pageLoadWorkshopFooterTest() {
+    
+    if (Cookies2.get("domain") === undefined) {
+      resetWorkshopFooter();
+    }
+    else {
+      replaceClassText();
+      setWorkshopFooterInputValues()
+    }
+  }
+  function setWorkshopFooterData() {
+    
+    Cookies2.set("domain", jQuery("select#domain").val(), { path: cookiePath, expires: 7 } );
+    Cookies2.set("prefix", jQuery("input#prefix").val().replace(/[^-.a-zA-Z0-9]/g, ''), { path: cookiePath, expires: 7 } );
+    Cookies2.set("userid", jQuery("select#userid").val(), { path: cookiePath, expires: 7 } );
+    replaceClassText();
+    modal.style.display = "none";
+  }
+  function setWorkshopFooterInputValues() {
+    jQuery("select#domain").val(Cookies2.get("domain"));
+    jQuery("input#prefix").val(Cookies2.get("prefix"));
+    jQuery("select#userid").val(Cookies2.get("userid"));
+  }
+  function resetWorkshopFooter() {
+    
+    jQuery("select#domain, select#userid").prop("selectedIndex", 0);
+    jQuery("input#prefix").val(jQuery("input#prefix").attr('placeholder'));
+    
+    Cookies2.set("domain", jQuery("select#domain option").first().val(), { path: cookiePath, expires: 7 } ); 
+    Cookies2.set("userid", jQuery("select#userid option").first().val(), { path: cookiePath, expires: 7 } ); 
+    Cookies2.set("prefix", jQuery("input#prefix").val(), { path: cookiePath, expires: 7 } );
+    
+    
+    replaceClassText();
+  }
+
+
+
+
+  function updateFooter(e){
+    fieldName = '';
+
+    switch(e.id) {
+      case 'userid':
+        fieldName = 'User Id';
+        break;
+      case 'domain':
+        fieldName = 'Domain';
+        break;
+      case 'prefix':
+        fieldName = 'Workshop';
+        break;
+      default:
+        fieldName = 'unknown';
+    }
+    setWorkshopFooterData();
+    toastr["success"](fieldName + " set to " + e.value);
+  }
+
+  jQuery(document).ready(function() {
+    pageLoadWorkshopFooterTest();
+
+
+    
+    var input = document.getElementById("prefix");
+
+    
+    input.addEventListener("keyup", function(event) {
+      
+      if (event.keyCode === 13) {
+        
+        event.preventDefault();
+        
+        
+        updateFooter(input);
+      }
+    });
+
+
+    jQuery("form#footerForm").submit(function() {
+      setWorkshopFooterData();
+      return false; 
+    });
+
+    jQuery("form#footerForm").bind("reset", function() {
+      resetWorkshopFooter();
+      return true;
+    });
+
+    return false;
+  });
+
+</script>
+
+<hr>
+<h3>Workshop Details</h3>
+    <table>
+      <tr>
+        <td class="text-right"><b>Domain</b></td>
+        <td><span class="domain"></span></td>
+        <td rowspan="3">
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
+        </td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Workshop</b></td>
+        <td><span class="prefix"></span></td>
+      </tr>
+      <tr>
+        <td class="text-right"><b>Student ID</b></td>
+        <td><span class="userid"></span></td>
+      </tr>
+    </table>
+<button id="myBtn">Configure Workshop</button>
+<hr>
+
+<script>
+
+var modal = document.getElementById("myModal");
+
+
+var btn = document.getElementById("myBtn");
+
+
+var span = document.getElementsByClassName("close")[0];
+
+
+btn.onclick = function() {
+  modal.style.display = "block";
+}
+
+
+span.onclick = function() {
+  modal.style.display = "none";
+}
+
+
+window.onclick = function(event) {
+  if (event.target == modal) {
+    modal.style.display = "none";
+  }
+}
+</script>
+
+
+</div>
+
+
+    
+
+
+
+
+
+
+
+
+<nav>
+  <ul class="pager">
+    
+    
+    <li class="previous">
+      <a href="/workshops/selinux_policy/exercise2.4/">&larr; Previous: Exercise 2.4 - Finishing the Policy</a>
+    </li>
+    
+    
+    
+    
+    <li class="next">
+      <a href="/workshops/selinux_policy/wrapup/">Next: Wrapup &rarr;</a>
+    </li>
+    
+    
+  </ul>
+</nav>
+
+    <p class="text-center">
+      
+      <a href="/workshops/selinux_policy">Return to Workshop</a>
+    </p>
+  </div>
+</div>
+
+    <div id="page-footer" class="container">
+      <p class="text-center">
+        Copyright &copy; 2024 Red Hat, Inc.
+      </p>
+    </div>
+    <script type="text/javascript">
+      if (("undefined" !== typeof _satellite) && ("function" === typeof _satellite.pageBottom)) {
+          _satellite.pageBottom();
+      }
+    </script>
+  </body>
+</html>
diff --git a/workshops/selinux_policy/index.html b/workshops/selinux_policy/index.html
index 6aba60afe..5ccdba658 100644
--- a/workshops/selinux_policy/index.html
+++ b/workshops/selinux_policy/index.html
@@ -288,7 +288,7 @@ <h1>SELinux Policy Workshop</h1>
 <h2 id="_workshop_description">Workshop Description</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>Writing your own SELinux policies doesn&#8217;t have to be a terrifying prospect!  This workshop will walk you through the process of creating a custom policy for a source-compiled application, using the advanced tooling present in Red Hat Enterprise Linux.</p>
+<p>Writing your own SELinux policies doesn’t have to be a terrifying prospect!  This workshop will walk you through the process of creating a custom policy for a source-compiled application, using the advanced tooling present in Red Hat Enterprise Linux.</p>
 </div>
 </div>
 </div>
@@ -341,7 +341,7 @@ <h2 id="_what_you_will_learn">What you will learn</h2>
 <h2 id="_overview">Overview</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>The SELinux policy workshop is meant for anyone who needs to create application policies for applications that lack them. Some previous experience with SELinux is expected, but you don&#8217;t have to be a master. Also, knowledge of RHEL and general Linux functionality is required. We are going to start with a short overview and then we’ll get into the lab as soon as possible. That is where we will spend most of our time.</p>
+<p>The SELinux policy workshop is meant for anyone who needs to create application policies for applications that lack them. Some previous experience with SELinux is expected, but you don’t have to be a master. Also, knowledge of RHEL and general Linux functionality is required. We are going to start with a short overview and then we’ll get into the lab as soon as possible. That is where we will spend most of our time.</p>
 </div>
 </div>
 </div>
@@ -355,32 +355,32 @@ <h2 id="_your_responsibilities">Your Responsibilities</h2>
 <p>Participate. We are going to cut you loose with SELinux, in just a little while. Have questions. Have opinions.</p>
 </div>
 <div class="paragraph">
-<p>Bring a laptop.  It doesn&#8217;t matter what OS it runs, but you will need either the Firefox or Chrome web browser installed. If, for some reason, you don&#8217;t have a laptop, let your instructor know, or try to find someone to share with.</p>
+<p>Bring a laptop.  It doesn’t matter what OS it runs, but you will need either the Firefox or Chrome web browser installed. If, for some reason, you don’t have a laptop, let your instructor know, or try to find someone to share with.</p>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>When we want you to type something in, we&#8217;ll use a frame like this:
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cat /etc/hosts</code></pre></div></p>
+<p>When we want you to type something in, we’ll use a frame like this:
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cat /etc/hosts</span></span></code></pre></div></p>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
 <div class="paragraph">
-<p>When we want to show you the output from a command, we&#8217;ll use a different frame, like this one:</p>
+<p>When we want to show you the output from a command, we’ll use a different frame, like this one:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -390,7 +390,7 @@ <h2 id="_your_responsibilities">Your Responsibilities</h2>
 </div>
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -416,7 +416,7 @@ <h2 id="_exercises">Exercises</h2>
 
 <ul>
   <li>
-    <a href="/workshops/selinux_policy/exercise1.1/">Exercise 1.1 - Introduction to SELinux</a>
+    <a href="/workshops/selinux_policy/exercise1.1/">Exercise 1.1 - SELinux policy in RHEL</a>
   </li>
 </ul>
 
@@ -426,6 +426,18 @@ <h2 id="_exercises">Exercises</h2>
   </li>
 </ul>
 
+<ul>
+  <li>
+    <a href="/workshops/selinux_policy/exercise1.3/">Exercise 1.3 - Altering behavior</a>
+  </li>
+</ul>
+
+<ul>
+  <li>
+    <a href="/workshops/selinux_policy/exercise1.4/">Exercise 1.4 - Troubleshooting</a>
+  </li>
+</ul>
+
 <ul>
   <li>
     <a href="/workshops/selinux_policy/exercise2.0/">Exercise 2.0 - Creating Custom SELinux Policy</a>
@@ -456,6 +468,12 @@ <h2 id="_exercises">Exercises</h2>
   </li>
 </ul>
 
+<ul>
+  <li>
+    <a href="/workshops/selinux_policy/exercise2.5/">Exercise 2.5 - Tips &amp; Tricks</a>
+  </li>
+</ul>
+
 <ul>
   <li>
     <a href="/workshops/selinux_policy/wrapup/">Wrapup</a>
@@ -564,7 +582,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -824,7 +842,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -936,7 +954,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -946,7 +964,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -999,7 +1017,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/index.xml b/workshops/selinux_policy/index.xml
index c7ef59441..ce0bd7207 100644
--- a/workshops/selinux_policy/index.xml
+++ b/workshops/selinux_policy/index.xml
@@ -4,124 +4,99 @@
     <title>SELinux Policy Workshop on Red Hat | Public Sector</title>
     <link>/workshops/selinux_policy/</link>
     <description>Recent content in SELinux Policy Workshop on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/selinux_policy/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/selinux_policy/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Exercise 1.0 - Introduction to Security Enhanced Linux (SELinux)</title>
       <link>/workshops/selinux_policy/exercise1.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise1.0/</guid>
-      <description>History In this exercise, we are going to introduce you to Security Enhanced Linux, commonly known as SELinux.
- SELinux is an implementation of the Flask system security architecture. The Flask architecture implements MAC, which focuses on providing an administratively-defined security policy that can control all subjects and objects, basing decisions on all security-relevant information. In addition, Flask focuses on the concept of least privilege, which gives a process exactly the rights it needs to perform its given task.</description>
+      <description>History In this workshop, we are going to introduce you to Security Enhanced Linux, commonly known as SELinux.&#xA;Standard Linux access policy based on the user, group, and other permissions, known as Discretionary Access Control (DAC), does not enable system administrators to create comprehensive and fine-grained security policies, such as restricting specific applications to only viewing log files, while allowing other applications to append new data to the log files.</description>
     </item>
-    
     <item>
-      <title>Exercise 1.1 - Introduction to SELinux</title>
+      <title>Exercise 1.1 - SELinux policy in RHEL</title>
       <link>/workshops/selinux_policy/exercise1.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise1.1/</guid>
-      <description>Exercise Description To better understand SELinux basic concepts, see the following documentation:
-   The SELinux Coloring Book
-  SELinux Wiki FAQ
-  The SELinux Notebook
-   Step 1: Become root First, go ahead and switch users to root:
- sudo -i   Step 2: What mode are we in? Next, let&amp;#8217;s check to see what SELinux mode your host is in:
- getenforce  Enforcing    Step 3: Changing modes Now, we can change the mode that your host is in:</description>
+      <description>What are policies? A policy is a real-world application of SELinux controls. This chapter is an overview and examination of SELinux policy for Red Hat Enterprise Linux.&#xA;What is the Targeted Policy? The SELinux policy is highly configurable. Starting with Red Hat Enterprise Linux 5, Red Hat defaulted to the targeted policy. The goal of this policy is to lock down all processes that listen for network connections and pretty much all processes that start at boot.</description>
     </item>
-    
     <item>
       <title>Exercise 1.2 - SELinux Contexts</title>
       <link>/workshops/selinux_policy/exercise1.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise1.2/</guid>
-      <description>Exercise Description All processes and files are labeled with an SELinux context. The context contains information that SELinux needs to make control decisions. Contexts contain user, role, type, and level information,
- Step 1: Examine a context To get started, let&amp;#8217;s check the context of a file in the ec2-user user&amp;#8217;s home directory:
- ls -Z ~ec2-user/.vimrc  unconfined_u:object_r:user_home_t:s0 /home/ec2-user/.vimrc   As a side note, the -Z flag is present, in a wide variety of common CLI tools, including ls and ps.</description>
+      <description>Exercise Description Let’s peer under the hood a bit to see how SELinux works. All processes and files are labeled with an SELinux context; contexts contain user, role, type, and level information. This is information that SELinux needs to enforce the active policy (eg, make access decisions). But where do files and directories get their contexts?&#xA;Contexts are set when files are created, based on their parent directory’s context (with a few exceptions)</description>
+    </item>
+    <item>
+      <title>Exercise 1.3 - Altering behavior</title>
+      <link>/workshops/selinux_policy/exercise1.3/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/selinux_policy/exercise1.3/</guid>
+      <description>Exercise Description Let’s take a look at controlling SELinux behavior.&#xA;Exercise 1.3.1 Step 1: What mode are we in? Next, let’s check to see what SELinux mode your host is in:&#xA;getenforce Enforcing Step 2: Changing modes Now, we can change the mode that your host is in:&#xA;setenforce 0 getenforce Permissive And we can change it back:&#xA;setenforce 1 getenforce Enforcing Exercise 1.3.2 Booleans are if-then-else rules written in SELinux Policy.</description>
+    </item>
+    <item>
+      <title>Exercise 1.4 - Troubleshooting</title>
+      <link>/workshops/selinux_policy/exercise1.4/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/selinux_policy/exercise1.4/</guid>
+      <description>Exercise Description Let’s look at some techniques for examing SELinux, as these are useful for troubleshooting. We’ll build on this in Section 2 of the workshop.&#xA;Step 1: Changing modes for specific domains You can also set individual SELinux domains (like httpd_t, which controls web server access control) to permissve mode:&#xA;semanage permissive -a httpd_t semanage permissive -l Builtin Permissive Types Customized Permissive Types httpd_t And again, we can change it back:</description>
     </item>
-    
     <item>
       <title>Exercise 2.0 - Creating Custom SELinux Policy</title>
       <link>/workshops/selinux_policy/exercise2.0/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.0/</guid>
-      <description>Exercise Description In this exercise, we are going to download the code for the example application that we are going to write policy for, and build and install it onto our test system.
- Step 1: Change directories Create a src directory, in your home directory.
- cd ~ mkdir src cd src   Step 2: Check out the source code to the example application from GitHub Download the latest code release</description>
+      <description>Exercise Description In this exercise, we are going to download the code for the example application that we are going to write policy for, and build and install it onto our test system.&#xA;Step 1: Exit root shell If you haven’t already, exit the root shell we started in Section 1. Running whoami should not return root:&#xA;whoami ec2-user Step 2: Change directories Create a src directory, in your home directory.</description>
     </item>
-    
     <item>
       <title>Exercise 2.1 - Generating a generic policy</title>
       <link>/workshops/selinux_policy/exercise2.1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.1/</guid>
-      <description>Exercise Description In this exercise, we are going to automatically generate an SELinux policy framework, and learn to handle AVC messages that are generated by SELinux, when the application violates the policy.
- Step 1: Generate an initial generic SELinux policy Create a policy directory, and generate an initial policy. Use sepolicy generate to generate a policy for the app that we want to enable.
- cd ~/src mkdir policy cd policy sepolicy generate --init /usr/local/sbin/testapp  Note the last few lines in the output from sepolicy generate:</description>
+      <description>Exercise Description In this exercise, we are going to automatically generate an SELinux policy framework, and learn to handle AVC messages that are generated by SELinux, when the application violates the policy.&#xA;Step 1: Generate an initial generic SELinux policy Create a policy directory, and generate an initial policy. Use sepolicy generate to generate a policy for the app that we want to enable.&#xA;cd ~/src mkdir policy cd policy sepolicy generate --init /usr/local/sbin/testapp Note the last few lines in the output from sepolicy generate:</description>
     </item>
-    
     <item>
       <title>Exercise 2.2 - Creating a Custom SELinux Application Policy</title>
       <link>/workshops/selinux_policy/exercise2.2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.2/</guid>
-      <description>Exercise Description This exercise will walk you through the steps required to handle AVC messages that are generated by SELinux, when an application violates existing policy. We will modify the already-created generic policy, in order to allow the application to run correctly, when we switch the policy to enforcing mode.
- Step 1: Check for AVC denials Now that our app is up and running, we can check the system logs for AVC (access vector cache, where SELinux caches decisions to grant or deny access) denial messages.</description>
+      <description>Exercise Description This exercise will walk you through the steps required to handle AVC messages that are generated by SELinux, when an application violates existing policy. We will modify the already-created generic policy, in order to allow the application to run correctly, when we switch the policy to enforcing mode.&#xA;Step 1: Check for AVC denials Now that our app is up and running, we can check the system logs for AVC (access vector cache, where SELinux caches decisions to grant or deny access) denial messages.</description>
     </item>
-    
     <item>
       <title>Exercise 2.3 - Creating Policy Rules for Network Access</title>
       <link>/workshops/selinux_policy/exercise2.3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.3/</guid>
-      <description>Exercise Description In this exercise, we will continue the modification of the generic application polocy to allow network traffic to be generated by the test application. There are several rules that will be needed, to handle a variety of AVC denials.
-   Section 1: HTTP Port Connectivity Step 1: Check for AVC denials Let&amp;#8217;s restart our app, to get an updated list of denials.
- sudo systemctl restart testapp  Let&amp;#8217;s start with one of the denials that will be present in the audit search results, related to connecting on TCP port 80:</description>
+      <description>Exercise Description In this exercise, we will continue the modification of the generic application polocy to allow network traffic to be generated by the test application. There are several rules that will be needed, to handle a variety of AVC denials.&#xA;Section 1: HTTP Port Connectivity Step 1: Check for AVC denials Let’s restart our app, to get an updated list of denials.&#xA;sudo systemctl restart testapp Let’s start with one of the denials that will be present in the audit search results, related to connecting on TCP port 80:</description>
     </item>
-    
     <item>
       <title>Exercise 2.4 - Finishing the Policy</title>
       <link>/workshops/selinux_policy/exercise2.4/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/exercise2.4/</guid>
-      <description>Exercise Description In this final exercise, we will finish the testapp SELinux policy.
-   Section 1: A Last-ish Interface Step 1: Check for AVC denials Let&amp;#8217;s again restart our app, to get an updated list of denials.
- systemctl restart testapp  We only have a few denials left, and you will see that they all (probably!) reference /etc/resolv.conf or to /etc/hosts.
- ausearch -m AVC -ts recent | egrep &amp;#39;^type=AVC&amp;#39;  type=AVC msg=audit(1553195947.</description>
+      <description>Exercise Description In this final exercise, we will finish the testapp SELinux policy.&#xA;Section 1: A Last-ish Interface Step 1: Check for AVC denials Let’s again restart our app, to get an updated list of denials.&#xA;sudo systemctl restart testapp We only have a few denials left, and you will see that they all (probably!) reference /etc/resolv.conf or to /etc/hosts.&#xA;sudo ausearch -m AVC -ts recent | egrep &amp;#39;^type=AVC&amp;#39; type=AVC msg=audit(1553195947.</description>
+    </item>
+    <item>
+      <title>Exercise 2.5 - Tips &amp; Tricks</title>
+      <link>/workshops/selinux_policy/exercise2.5/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      <guid>/workshops/selinux_policy/exercise2.5/</guid>
+      <description>Tips &amp;amp; tricks This is the conclusion of the SELinux policy workshop. Here’s some closing tips to help you work with SELinux. Please ask any questions that you have left, and thanks so much for coming!&#xA;Set a folder’s context to mimic another:&#xA;mkdir -p /var/new_www/html matchpathcon /var/www/html /var/new_www/html semanage fcontext -a -e /var/www /var/new_www restorecon -Rv /var/ List ports associated with all service domains:&#xA;semanage port -l And then, add a port to an existing service’s domain, such as httpd:</description>
     </item>
-    
     <item>
       <title>Setup</title>
       <link>/workshops/selinux_policy/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/setup/</guid>
-      <description>What you will learn: Cockpit (Browser-based Admin Interface) This lab provides a quick tour of the browser based admin interface client &#39;Cockpit&#39;. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-   Accessing Cockpit Use this URL to access the Cockpit node, just change the workshop name (if applicable). Ask your instructor for the workshop name.</description>
+      <description>What you will learn: Cockpit (Browser-based Admin Interface) This lab provides a quick tour of the browser based admin interface client &amp;#39;Cockpit&amp;#39;. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Cockpit Use this URL to access the Cockpit node, just change the workshop name (if applicable). Ask your instructor for the workshop name.&#xA;https://node-0.example.redhatgov.io:9090/system/terminal The login screen looks like this:</description>
     </item>
-    
     <item>
       <title>Wrapup</title>
       <link>/workshops/selinux_policy/wrapup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/selinux_policy/wrapup/</guid>
-      <description>That wraps up what we have planned for today. We hope you&amp;#8217;ve learned something valuable about SELinux policies that you can apply in your daily role.
- What do you think? How can we help you understand SELinux better?
- Before you leave, check out the Resources page that is part of this guide. There, you can find a ton of links that will further your SELinux education.
- This Participant Guide will remain active for the next two weeks.</description>
+      <description>That wraps up what we have planned for today. We hope you’ve learned something valuable about SELinux policies that you can apply in your daily role.&#xA;What do you think? How can we help you understand SELinux better?&#xA;Before you leave, check out the Resources below; you will find useful links that will further your SELinux education.&#xA;This Participant Guide will remain available. Please take advantage of it by creating your own SELinux policy back at your organization.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/selinux_policy/setup/index.html b/workshops/selinux_policy/setup/index.html
index 2917c741b..568821655 100644
--- a/workshops/selinux_policy/setup/index.html
+++ b/workshops/selinux_policy/setup/index.html
@@ -317,7 +317,7 @@ <h1>Setup</h1>
 <div class="sectionbody">
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/selinux_policy/images/tower.002.png" alt="Tower">
+<img src="/workshops/selinux_policy/images/tower.002.png" alt="Tower"/>
 </div>
 </div>
 </div>
@@ -326,7 +326,7 @@ <h1>Setup</h1>
 <h2 id="_what_you_will_learn_cockpit_browser_based_admin_interface">What you will learn: Cockpit (Browser-based Admin Interface)</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>This lab provides a quick tour of the browser based admin interface client 'Cockpit'. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.</p>
+<p>This lab provides a quick tour of the browser based admin interface client &#39;Cockpit&#39;. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.</p>
 </div>
 </div>
 </div>
@@ -346,7 +346,7 @@ <h2 id="_accessing_cockpit">Accessing Cockpit</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/selinux_policy/images/selinux-cockpit-login-filled.png" alt="selinux cockpit login filled" height="500">
+<img src="/workshops/selinux_policy/images/selinux-cockpit-login-filled.png" alt="selinux cockpit login filled" height="500"/>
 </div>
 <div class="title">Figure 1: Cockpit Login Screen</div>
 </div>
@@ -355,19 +355,19 @@ <h2 id="_accessing_cockpit">Accessing Cockpit</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/selinux_policy/images/selinux-cockpit-system.png" alt="selinux cockpit system" height="500">
+<img src="/workshops/selinux_policy/images/selinux-cockpit-system.png" alt="selinux cockpit system" height="500"/>
 </div>
 <div class="title">Figure 2: Cockpit System Panel</div>
 </div>
 <div class="paragraph">
-<p>Now, let&#8217;s do a quick tour of the tabs, in Cockpit, that we will be using, in this workshop.</p>
+<p>Now, let’s do a quick tour of the tabs, in Cockpit, that we will be using, in this workshop.</p>
 </div>
 <div class="paragraph">
 <p>First, click on the <code>SELinux</code> link, in the panel on the left side of the screen.  You should see a panel like this:</p>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/selinux_policy/images/selinux-cockpit-selinux.png" alt="selinux cockpit selinux" height="500">
+<img src="/workshops/selinux_policy/images/selinux-cockpit-selinux.png" alt="selinux cockpit selinux" height="500"/>
 </div>
 <div class="title">Figure 3: Cockpit SELinux Panel</div>
 </div>
@@ -379,7 +379,7 @@ <h2 id="_accessing_cockpit">Accessing Cockpit</h2>
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/selinux_policy/images/selinux-cockpit-terminal.png" alt="selinux cockpit terminal" height="500">
+<img src="/workshops/selinux_policy/images/selinux-cockpit-terminal.png" alt="selinux cockpit terminal" height="500"/>
 </div>
 <div class="title">Figure 4: Cockpit Terminal Panel</div>
 </div>
@@ -388,15 +388,15 @@ <h2 id="_accessing_cockpit">Accessing Cockpit</h2>
 </div>
 <div class="admonitionblock important">
 <table>
-<tr>
+<tbody><tr>
 <td class="icon">
 <i class="fa icon-important" title="Important"></i>
 </td>
 <td class="content">
-Be sure you can log in to your instances.  If you can&#8217;t log in start shouting, loudly, and waving your hands!
+Be sure you can log in to your instances.  If you can’t log in start shouting, loudly, and waving your hands!
 </td>
 </tr>
-</table>
+</tbody></table>
 </div>
 </div>
 </div>
@@ -404,7 +404,7 @@ <h2 id="_accessing_cockpit">Accessing Cockpit</h2>
 <h2 id="_end_result">End Result</h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>At this point, you should have logged into your node.  If you haven&#8217;t, let us know so we can get you fixed up.</p>
+<p>At this point, you should have logged into your node.  If you haven’t, let us know so we can get you fixed up.</p>
 </div>
 <div class="paragraph">
 <style>
@@ -506,7 +506,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -766,7 +766,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -878,7 +878,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -888,7 +888,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -970,7 +970,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/selinux_policy/wrapup/index.html b/workshops/selinux_policy/wrapup/index.html
index 4bc8a002a..65c42c108 100644
--- a/workshops/selinux_policy/wrapup/index.html
+++ b/workshops/selinux_policy/wrapup/index.html
@@ -303,7 +303,7 @@ <h1>Wrapup</h1>
     
     
     <li class="previous">
-      <a href="/workshops/selinux_policy/exercise2.4/">&larr; Previous: Exercise 2.4 - Finishing the Policy</a>
+      <a href="/workshops/selinux_policy/exercise2.5/">&larr; Previous: Exercise 2.5 - Tips &amp; Tricks</a>
     </li>
     
     
@@ -313,24 +313,64 @@ <h1>Wrapup</h1>
   </ul>
 </nav>
 
-    <div class="paragraph">
-<p>That wraps up what we have planned for today.  We hope you&#8217;ve learned something valuable about SELinux policies that you can apply in your daily role.</p>
+    <div id="preamble">
+<div class="sectionbody">
+<div class="paragraph">
+<p>That wraps up what we have planned for today.  We hope you’ve learned something valuable about SELinux policies that you can apply in your daily role.</p>
 </div>
 <div class="paragraph">
 <p>What do you think? How can we help you understand SELinux better?</p>
 </div>
 <div class="paragraph">
-<p>Before you leave, check out the <strong>Resources</strong> page that is part of this guide.  There, you can find a ton of links that will further your SELinux education.</p>
+<p>Before you leave, check out the <strong>Resources</strong> below; you will find useful links that will further your SELinux education.</p>
 </div>
 <div class="paragraph">
-<p>This <strong>Participant Guide</strong> will remain active for the next two weeks.  Please take advantage of it by creating your own SELinux policy back at your organization.</p>
+<p>This <strong>Participant Guide</strong> will remain available.  Please take advantage of it by creating your own SELinux policy back at your organization.</p>
 </div>
 <div class="paragraph">
 <p>Thank you for your time and participation!</p>
 </div>
+</div>
+</div>
+<h1 id="_resources" class="sect0">Resources</h1>
+<div class="sect2">
+<h3 id="_fun_stuff">Fun Stuff</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="https://stopdisablingselinux.com/" class="bare">https://stopdisablingselinux.com/</a></p>
+</li>
+<li>
+<p><a href="https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf">SELinux coloring book</a></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_knowledge_articles">Knowledge Articles</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="https://access.redhat.com/articles/6964380">SELinux as a security pillar of an operating system - Real-world benefits and examples</a></p>
+</li>
+<li>
+<p><a href="https://access.redhat.com/articles/2191331">Basic SELinux Troubleshooting in CLI</a></p>
+</li>
+<li>
+<p><a href="https://access.redhat.com/articles/6999267">Quick start to write a custom SELinux policy</a></p>
+</li>
+<li>
+<p><a href="https://access.redhat.com/articles/7047896">SELinux hardening with Ansible (makes note of several booleans)</a></p>
+</li>
+<li>
+<p><a href="https://www.redhat.com/sysadmin/change-selinux-settings-boolean">How to modify SELinux settings with booleans</a></p>
+</li>
+</ul>
+</div>
 <div class="imageblock">
 <div class="content">
-<img src="/workshops/selinux_policy/images/redhat.svg" alt="redhat">
+<img src="/workshops/selinux_policy/images/redhat.svg" alt="redhat"/>
+</div>
 </div>
 </div>
 
@@ -349,7 +389,7 @@ <h1>Wrapup</h1>
     
     
     <li class="previous">
-      <a href="/workshops/selinux_policy/exercise2.4/">&larr; Previous: Exercise 2.4 - Finishing the Policy</a>
+      <a href="/workshops/selinux_policy/exercise2.5/">&larr; Previous: Exercise 2.5 - Tips &amp; Tricks</a>
     </li>
     
     
@@ -368,7 +408,7 @@ <h1>Wrapup</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/conclusion/index.html b/workshops/source_to_image/conclusion/index.html
index 245807674..2ca0fa1d9 100644
--- a/workshops/source_to_image/conclusion/index.html
+++ b/workshops/source_to_image/conclusion/index.html
@@ -371,7 +371,7 @@ <h1 id="additional-resources">Additional Resources</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/containerize_app/index.html b/workshops/source_to_image/containerize_app/index.html
index 239970980..dd9e12cba 100644
--- a/workshops/source_to_image/containerize_app/index.html
+++ b/workshops/source_to_image/containerize_app/index.html
@@ -322,23 +322,23 @@ <h1 id="introduction">Introduction</h1>
 <p>Fortunately we can build from a Dockerfile using the <strong>oc</strong> command line tool.  For those on your own computer, we recommend trying it this way as well.</p>
 <h2 id="step-1---create-a-new-project">Step 1 - Create a New Project</h2>
 <p>Create a new project for your containerized gochat application.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc new-project gochat-container-user<span class="userid">YOUR#</span>
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-project gochat-container-user<span class="userid">YOUR#</span>
 
 </code></pre><h2 id="step-2---build-from-dockerfile">Step 2 - Build from Dockerfile</h2>
 <p>Start a new build from the Dockerfile in the <a href="https://github.com/kevensen/gochat-client-container">gochat-container</a> repository.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc new-build https://github.com/kevensen/gochat-client-container -e CHAT_SERVER=gochat-server.gochat-server.svc.cluster.local:8080
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-build https://github.com/kevensen/gochat-client-container -e CHAT_SERVER=gochat-server.gochat-server.svc.cluster.local:8080
 </code></pre><h2 id="step-3---lets-take-a-pause">Step 3 - Let&rsquo;s Take a Pause</h2>
 <p>Watch the deployment</p>
-<pre><code class="language-terminal" data-lang="terminal">oc logs -f bc/gochat-client-container
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc logs -f bc/gochat-client-container
 </code></pre><p>Then <strong>ctrl-c</strong> once you&rsquo;ve had enough.</p>
 <h2 id="step-4---deploy-from-imagestream">Step 4 - Deploy from ImageStream</h2>
-<pre><code class="language-terminal" data-lang="terminal">oc new-app gochat-client-container
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-app gochat-client-container
 </code></pre><h2 id="step-5---expose-the-containerized-gochat-app">Step 5 - Expose the Containerized Gochat App</h2>
-<pre><code class="language-terminal" data-lang="terminal">oc expose svc gochat-client-container
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc expose svc gochat-client-container
 </code></pre><h2 id="step-6---annotate-the-service-account-to-use-openshift-authorization">Step 6 - Annotate the Service Account to Use OpenShift Authorization</h2>
 <p>As in the previous lab, we must annotate the service account for the Gochat Client to communicate to the OpenShift API for user credential verification.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1='{&quot;kind&quot;:&quot;OAuthRedirectReference&quot;,&quot;apiVersion&quot;:&quot;v1&quot;,&quot;reference&quot;:{&quot;kind&quot;:&quot;Route&quot;,&quot;name&quot;:&quot;gochat-client-container&quot;}}' --overwrite
-</code></pre><pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1=&#39;{&#34;kind&#34;:&#34;OAuthRedirectReference&#34;,&#34;apiVersion&#34;:&#34;v1&#34;,&#34;reference&#34;:{&#34;kind&#34;:&#34;Route&#34;,&#34;name&#34;:&#34;gochat-client-container&#34;}}&#39; --overwrite
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
 </code></pre><h2 id="step-7---access-the-app">Step 7 - Access the App</h2>
 <p>Go back to the OpenShift WebUI and click on the &ldquo;gochat&rdquo; URL.</p>
 <div class="panel-group">
@@ -403,17 +403,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse25334dab422259edec074ef48abe1742" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec7de9cf6870f4812de3e9c44da5d5129" class="collapsed">
       
         OpenShift WebUI Login
       </a>
     </h4>
   </div>
   
-  <div id="collapse25334dab422259edec074ef48abe1742" class="panel-collapse collapse ">
+  <div id="collapsec7de9cf6870f4812de3e9c44da5d5129" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/webui.png" width="1000" /></p>
+       <img src="../images/webui.png" width="1000" />
 
     </div>
   </div>
@@ -552,7 +552,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -812,7 +812,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -924,7 +924,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -934,7 +934,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1017,7 +1017,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/dice/index.html b/workshops/source_to_image/dice/index.html
index ac6980f73..f3c2d3849 100644
--- a/workshops/source_to_image/dice/index.html
+++ b/workshops/source_to_image/dice/index.html
@@ -319,58 +319,58 @@ <h1>Lab - Roll Dice</h1>
 
     <p>In an attempt at nostalgia, we are going to once again create an S2I builder, this time for a Fortran app.  Yes, <strong>Fortran</strong>.  The objective is to make our little chat program a bit more interesting.</p>
 <h2 id="step-1---create-the-s2i-project">Step 1 - Create the S2I Project</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">s2i create fortran-s2i fortran-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">s2i create fortran-s2i fortran-s2i
 </code></pre><h2 id="step-2---edit-the-dockerfile">Step 2 - Edit the Dockerfile</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/fortran-s2i/Dockerfile
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/fortran-s2i/Dockerfile
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/fortran-s2i/Dockerfile
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/fortran-s2i/Dockerfile
 </code></pre><p>Copy the following text and paste it in to the editor.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-Dockerfile" data-lang="Dockerfile"><span style="color:#75715e"># fortran-s2i</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">FROM</span><span style="color:#e6db74"> openshift/base-centos7</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">LABEL</span> maintainer<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;Kenneth Evensen &lt;kdevensen@gmail.com&gt;&#34;</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> BUILDER_VERSION 1.0<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">LABEL</span> io.k8s.description<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;Platform for building Fortran apps&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.k8s.display-name<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;builder 1.0.0&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.openshift.tags<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;fortran&#34;</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> yum install -y gcc-gfortran <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>    yum clean all <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>    rm -rf /var/cache/yum/*<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">COPY</span> ./s2i/bin/ /usr/libexec/s2i<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> chown -R 1001:1001 /opt/app-root<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">USER</span><span style="color:#e6db74"> 1001</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">CMD</span> [<span style="color:#e6db74">&#34;/usr/libexec/s2i/usage&#34;</span>]<span style="color:#960050;background-color:#1e0010">
-</span></code></pre></div><p>To exit vi:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-Dockerfile" data-lang="Dockerfile"><span style="display:flex;"><span><span style="color:#75715e"># fortran-s2i</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">FROM</span><span style="color:#e6db74"> openshift/base-centos7</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">LABEL</span> maintainer<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;Kenneth Evensen &lt;kdevensen@gmail.com&gt;&#34;</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> BUILDER_VERSION 1.0<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">LABEL</span> io.k8s.description<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;Platform for building Fortran apps&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.k8s.display-name<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;builder 1.0.0&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.openshift.tags<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;fortran&#34;</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> yum install -y gcc-gfortran <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>    yum clean all <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>    rm -rf /var/cache/yum/*<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">COPY</span> ./s2i/bin/ /usr/libexec/s2i<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> chown -R 1001:1001 /opt/app-root<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">USER</span><span style="color:#e6db74"> 1001</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">CMD</span> [<span style="color:#e6db74">&#34;/usr/libexec/s2i/usage&#34;</span>]<span style="color:#960050;background-color:#1e0010">
+</span></span></span></code></pre></div><p>To exit vi:</p>
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-3---edit-the-assemble-script">Step 3 - Edit the Assemble Script</h2>
-<pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/fortran-s2i/s2i/bin/assemble
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/fortran-s2i/s2i/bin/assemble
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/fortran-s2i/s2i/bin/assemble
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/fortran-s2i/s2i/bin/assemble
 </code></pre><p>Copy the following into the editor.</p>
-<pre><code class="language-terminal" data-lang="terminal">#!/bin/bash -e
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">#!/bin/bash -e
 
-echo &quot;---&gt; Installing application source...&quot;
+echo &#34;---&gt; Installing application source...&#34;
 cp -Rf /tmp/src/. ./
 
-echo &quot;---&gt; Building application from source...&quot;
+echo &#34;---&gt; Building application from source...&#34;
 gfortran app.f90 -o /opt/app-root/fortran-app
 </code></pre><p>To exit vi:</p>
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-4---edit-the-run-script">Step 4 - Edit the Run Script</h2>
-<pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/fortran-s2i/s2i/bin/run
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/fortran-s2i/s2i/bin/run
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/fortran-s2i/s2i/bin/run
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/fortran-s2i/s2i/bin/run
 </code></pre><p>Copy the following into the editor.</p>
-<pre><code class="language-terminal" data-lang="terminal">#!/bin/bash -e
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">#!/bin/bash -e
 exec /opt/app-root/fortran-app $ARGS
 </code></pre><p>To exit vi:</p>
 <p>shift+z</p>
@@ -378,15 +378,15 @@ <h2 id="step-4---edit-the-run-script">Step 4 - Edit the Run Script</h2>
 <h2 id="step-5---enusre-you-are-still-in-the-gochat-s2i-porject">Step 5 - Enusre You are Still in the Gochat-s2i Porject</h2>
 <p>In the Wetty terminal, change to the <strong>gochat-s2i-user<span class="userid">YOUR#</span>
 </strong> project space</p>
-<pre><code class="language-terminal" data-lang="terminal">oc project gochat-s2i-user<span class="userid">YOUR#</span>
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc project gochat-s2i-user<span class="userid">YOUR#</span>
 
 </code></pre><h2 id="step-6---create-the-fortran-s2i-builder-image">Step 6 - Create the Fortran S2I Builder Image</h2>
 <p>Create a new build for the Fortran S2I builder image</p>
-<pre><code class="language-terminal" data-lang="terminal">oc new-build fortran-s2i/ --to=fortran-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-build fortran-s2i/ --to=fortran-s2i
 </code></pre><p>Start the new build for the Fortran S2I builder image</p>
-<pre><code class="language-terminal" data-lang="terminal">oc start-build fortran-s2i --from-dir=fortran-s2i/
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc start-build fortran-s2i --from-dir=fortran-s2i/
 </code></pre><h2 id="step-7---create-the-fortran-dice-container-from-source">Step 7 - Create the Fortran-Dice Container from Source</h2>
-<pre><code class="language-terminal" data-lang="terminal">oc new-build https://github.com/kevensen/fortran-dice.git --image-stream=fortran-s2i --name=dice --allow-missing-imagestream-tags
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-build https://github.com/kevensen/fortran-dice.git --image-stream=fortran-s2i --name=dice --allow-missing-imagestream-tags
 </code></pre><h2 id="step-8---roll-some-dice">Step 8 - Roll Some Dice</h2>
 <p>In the chat window, try:</p>
 <p><strong>//roll</strong></p>
@@ -491,7 +491,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -751,7 +751,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -863,7 +863,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -873,7 +873,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -956,7 +956,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/gochat_s2i/index.html b/workshops/source_to_image/gochat_s2i/index.html
index bab9ce1e4..e588ebe28 100644
--- a/workshops/source_to_image/gochat_s2i/index.html
+++ b/workshops/source_to_image/gochat_s2i/index.html
@@ -319,14 +319,14 @@ <h1>Lab - Gochat S2I</h1>
 
     <h2 id="step-1---create-a-new-project-space">Step 1 - Create a New Project Space</h2>
 <p>In the Wetty terminal, create a new project.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc new-project gochat-s2i-user<span class="userid">YOUR#</span>
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-project gochat-s2i-user<span class="userid">YOUR#</span>
 
 </code></pre><h2 id="step-2---create-the-golang-s2i-builder-image">Step 2 - Create the Golang S2I Builder Image</h2>
 <p>Create a new build for the Golang S2I builder image</p>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">oc new-build golang-s2i/ --to=golang-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-build golang-s2i/ --to=golang-s2i
 </code></pre><p>Start the new build for the Golang S2I builder image</p>
-<pre><code class="language-terminal" data-lang="terminal">oc start-build golang-s2i --from-dir=golang-s2i/
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc start-build golang-s2i --from-dir=golang-s2i/
 </code></pre><h2 id="step-3---import-yaml-template-in-to-openshift">Step 3 - Import YAML Template in to OpenShift</h2>
 <p>In the OpenShift WebUI, on the catalog page, seclect Import YAML/JSON
 <div class="panel-group">
@@ -336,17 +336,17 @@ <h2 id="step-1---create-a-new-project-space">Step 1 - Create a New Project Space
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse48781342b8ef8c48fb2b54edfb3c63f9" class="collapsed">
+      <a data-toggle="collapse" href="#collapse3b118d092849163359ad6c5a63650259" class="collapsed">
       
         Import YAML/JSON
       </a>
     </h4>
   </div>
   
-  <div id="collapse48781342b8ef8c48fb2b54edfb3c63f9" class="panel-collapse collapse ">
+  <div id="collapse3b118d092849163359ad6c5a63650259" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/import_yaml_json.png" width="600" /></p>
+       <img src="../images/import_yaml_json.png" width="600" />
 
     </div>
   </div>
@@ -367,161 +367,161 @@ <h2 id="step-4---configure-the-import">Step 4 - Configure the Import</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse67bac97790c72c2661fabb8ec6b7f790" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef9d7b662e6dc96dc5610eb5f27f87a5b" class="collapsed">
       
         Golang Template
       </a>
     </h4>
   </div>
   
-  <div id="collapse67bac97790c72c2661fabb8ec6b7f790" class="panel-collapse collapse ">
+  <div id="collapsef9d7b662e6dc96dc5610eb5f27f87a5b" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-yaml" data-lang="yaml"><span style="color:#66d9ef">apiVersion</span>: v1
-<span style="color:#66d9ef">kind</span>: Template
-<span style="color:#66d9ef">labels</span>:
-  <span style="color:#66d9ef">template</span>: golang
-<span style="color:#66d9ef">metadata</span>:
-  <span style="color:#66d9ef">annotations</span>:
-    <span style="color:#66d9ef">description</span>: A basic builder for Golang applications
-    <span style="color:#66d9ef">iconClass</span>: icon-go-gopher
-    <span style="color:#66d9ef">openshift.io/display-name</span>: Golang
-    <span style="color:#66d9ef">openshift.io/long-description</span>: This template defines resources needed to develop
-      a Golang application, including a build configuration, application deployment
-      configuration, and database deployment configuration.
-    <span style="color:#66d9ef">openshift.io/provider-display-name</span>: Community
-    <span style="color:#66d9ef">template.openshift.io/bindable</span>: <span style="color:#e6db74">&#34;false&#34;</span>
-    <span style="color:#66d9ef">tags</span>: golang
-  <span style="color:#66d9ef">creationTimestamp</span>: <span style="color:#66d9ef">null</span>
-  <span style="color:#66d9ef">name</span>: golang
-<span style="color:#66d9ef">objects</span>:
-- <span style="color:#66d9ef">apiVersion</span>: v1
-  <span style="color:#66d9ef">kind</span>: ImageStream
-  <span style="color:#66d9ef">metadata</span>:
-    <span style="color:#66d9ef">annotations</span>:
-      <span style="color:#66d9ef">description</span>: Keeps track of changes in the application image
-    <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-- <span style="color:#66d9ef">apiVersion</span>: v1
-  <span style="color:#66d9ef">kind</span>: BuildConfig
-  <span style="color:#66d9ef">metadata</span>:
-    <span style="color:#66d9ef">annotations</span>:
-      <span style="color:#66d9ef">description</span>: Defines how to build the application
-    <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-  <span style="color:#66d9ef">spec</span>:
-    <span style="color:#66d9ef">output</span>:
-      <span style="color:#66d9ef">to</span>:
-        <span style="color:#66d9ef">kind</span>: ImageStreamTag
-        <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}:latest
-    <span style="color:#66d9ef">source</span>:
-      <span style="color:#66d9ef">contextDir</span>: ${APP_CONTEXT_DIR}
-      <span style="color:#66d9ef">git</span>:
-        <span style="color:#66d9ef">ref</span>: ${APP_SOURCE_REPOSITORY_REF}
-        <span style="color:#66d9ef">uri</span>: ${APP_SOURCE_REPOSITORY_URL}
-      <span style="color:#66d9ef">type</span>: Git
-    <span style="color:#66d9ef">strategy</span>:
-      <span style="color:#66d9ef">sourceStrategy</span>:
-        <span style="color:#66d9ef">from</span>:
-          <span style="color:#66d9ef">kind</span>: ImageStreamTag
-          <span style="color:#66d9ef">name</span>: golang-s2i:latest
-      <span style="color:#66d9ef">type</span>: Source
-    <span style="color:#66d9ef">triggers</span>:
-    - <span style="color:#66d9ef">type</span>: ImageChange
-    - <span style="color:#66d9ef">type</span>: ConfigChange
-    - <span style="color:#66d9ef">github</span>:
-        <span style="color:#66d9ef">secret</span>: ${APP_GITHUB_WEBHOOK_SECRET}
-      <span style="color:#66d9ef">type</span>: GitHub
-- <span style="color:#66d9ef">apiVersion</span>: v1
-  <span style="color:#66d9ef">kind</span>: DeploymentConfig
-  <span style="color:#66d9ef">metadata</span>:
-    <span style="color:#66d9ef">annotations</span>:
-      <span style="color:#66d9ef">description</span>: Defines how to deploy the application server
-    <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-  <span style="color:#66d9ef">spec</span>:
-    <span style="color:#66d9ef">replicas</span>: <span style="color:#ae81ff">1</span>
-    <span style="color:#66d9ef">selector</span>:
-      <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-    <span style="color:#66d9ef">strategy</span>:
-      <span style="color:#66d9ef">type</span>: Rolling
-    <span style="color:#66d9ef">template</span>:
-      <span style="color:#66d9ef">metadata</span>:
-        <span style="color:#66d9ef">labels</span>:
-          <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-        <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-      <span style="color:#66d9ef">spec</span>:
-        <span style="color:#66d9ef">containers</span>:
-        - <span style="color:#66d9ef">env</span>:
-          - <span style="color:#66d9ef">name</span>: ARGS
-            <span style="color:#66d9ef">value</span>: ${APP_ARGS}
-          <span style="color:#66d9ef">image</span>: ${APPLICATION_NAME}
-          <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-          <span style="color:#66d9ef">ports</span>:
-          - <span style="color:#66d9ef">containerPort</span>: <span style="color:#ae81ff">8080</span>
-    <span style="color:#66d9ef">triggers</span>:
-    - <span style="color:#66d9ef">imageChangeParams</span>:
-        <span style="color:#66d9ef">automatic</span>: <span style="color:#66d9ef">true</span>
-        <span style="color:#66d9ef">containerNames</span>:
-        - ${APPLICATION_NAME}
-        <span style="color:#66d9ef">from</span>:
-          <span style="color:#66d9ef">kind</span>: ImageStreamTag
-          <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}:latest
-      <span style="color:#66d9ef">type</span>: ImageChange
-    - <span style="color:#66d9ef">type</span>: ConfigChange
-- <span style="color:#66d9ef">apiVersion</span>: v1
-  <span style="color:#66d9ef">kind</span>: Service
-  <span style="color:#66d9ef">metadata</span>:
-    <span style="color:#66d9ef">annotations</span>:
-      <span style="color:#66d9ef">description</span>: Exposes and load balances the application pods
-    <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-  <span style="color:#66d9ef">spec</span>:
-    <span style="color:#66d9ef">ports</span>:
-    - <span style="color:#66d9ef">name</span>: web
-      <span style="color:#66d9ef">port</span>: <span style="color:#ae81ff">8080</span>
-      <span style="color:#66d9ef">targetPort</span>: <span style="color:#ae81ff">8080</span>
-    <span style="color:#66d9ef">selector</span>:
-      <span style="color:#66d9ef">name</span>: ${APPLICATION_NAME}
-- <span style="color:#66d9ef">apiVersion</span>: v1
-  <span style="color:#66d9ef">id</span>: ${APPLICATION_NAME}
-  <span style="color:#66d9ef">kind</span>: Route
-  <span style="color:#66d9ef">metadata</span>:
-    <span style="color:#66d9ef">annotations</span>:
-      <span style="color:#66d9ef">description</span>: Route for application<span style="color:#e6db74">&#39;s http service.
-</span><span style="color:#e6db74">    labels:
-</span><span style="color:#e6db74">      application: ${APPLICATION_NAME}
-</span><span style="color:#e6db74">    name: ${APPLICATION_NAME}
-</span><span style="color:#e6db74">  spec:
-</span><span style="color:#e6db74">    host: ${APPLICATION_DOMAIN}
-</span><span style="color:#e6db74">    to:
-</span><span style="color:#e6db74">      name: ${APPLICATION_NAME}
-</span><span style="color:#e6db74">parameters:
-</span><span style="color:#e6db74">- description: The URL of the repository with your Golang application code
-</span><span style="color:#e6db74">  name: APP_SOURCE_REPOSITORY_URL
-</span><span style="color:#e6db74">  displayName: Application Source URL
-</span><span style="color:#e6db74">- description: Set this to a branch name, tag or other ref of your repository if you
-</span><span style="color:#e6db74">    are not using the default branch
-</span><span style="color:#e6db74">  name: APP_SOURCE_REPOSITORY_REF
-</span><span style="color:#e6db74">  displayName: Application Source Branch
-</span><span style="color:#e6db74">- description: Set this to the relative path to your project if it is not in the root
-</span><span style="color:#e6db74">    of your repository
-</span><span style="color:#e6db74">  name: APP_CONTEXT_DIR
-</span><span style="color:#e6db74">  displayName: Application Source Directory
-</span><span style="color:#e6db74">- description: A secret string used to configure the GitHub webhook for the app repo
-</span><span style="color:#e6db74">  from: &#39;</span>[a-zA-Z0<span style="color:#ae81ff">-9</span>]{<span style="color:#ae81ff">40</span>}<span style="color:#e6db74">&#39;
-</span><span style="color:#e6db74">  generate: expression
-</span><span style="color:#e6db74">  name: APP_GITHUB_WEBHOOK_SECRET
-</span><span style="color:#e6db74">  displayName: Application GitHub Web Hook Secret
-</span><span style="color:#e6db74">- description: The name for the application.
-</span><span style="color:#e6db74">  name: APPLICATION_NAME
-</span><span style="color:#e6db74">  required: true
-</span><span style="color:#e6db74">  value: golang-app
-</span><span style="color:#e6db74">  displayName: Application Name
-</span><span style="color:#e6db74">- description: &#39;</span>Custom hostname for service routes.  Leave blank for default hostname,
-    <span style="color:#66d9ef">e.g.</span>: &lt;application-name&gt;.&lt;project&gt;.&lt;default-domain-suffix&gt;&#39;
-  <span style="color:#66d9ef">name</span>: APPLICATION_DOMAIN
-  <span style="color:#66d9ef">displayName</span>: Application Domain
-- <span style="color:#66d9ef">description</span>: Command line arguments to provide to the Golang application
-  <span style="color:#66d9ef">name</span>: APP_ARGS
-  <span style="color:#66d9ef">displayName</span>: Application Command Line Arguments
-</code></pre></div>
+       <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#f92672">apiVersion</span>: <span style="color:#ae81ff">v1</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">kind</span>: <span style="color:#ae81ff">Template</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">labels</span>:
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">template</span>: <span style="color:#ae81ff">golang</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">annotations</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">description</span>: <span style="color:#ae81ff">A basic builder for Golang applications</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">iconClass</span>: <span style="color:#ae81ff">icon-go-gopher</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">openshift.io/display-name</span>: <span style="color:#ae81ff">Golang</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">openshift.io/long-description</span>: <span style="color:#ae81ff">This template defines resources needed to develop</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#ae81ff">a Golang application, including a build configuration, application deployment</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#ae81ff">configuration, and database deployment configuration.</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">openshift.io/provider-display-name</span>: <span style="color:#ae81ff">Community</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">template.openshift.io/bindable</span>: <span style="color:#e6db74">&#34;false&#34;</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">tags</span>: <span style="color:#ae81ff">golang</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">creationTimestamp</span>: <span style="color:#66d9ef">null</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">golang</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">objects</span>:
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">apiVersion</span>: <span style="color:#ae81ff">v1</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">ImageStream</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">annotations</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Keeps track of changes in the application image</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">apiVersion</span>: <span style="color:#ae81ff">v1</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">BuildConfig</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">annotations</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Defines how to build the application</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">spec</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">output</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">to</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">ImageStreamTag</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}:latest</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">source</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">contextDir</span>: <span style="color:#ae81ff">${APP_CONTEXT_DIR}</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">git</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">ref</span>: <span style="color:#ae81ff">${APP_SOURCE_REPOSITORY_REF}</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">uri</span>: <span style="color:#ae81ff">${APP_SOURCE_REPOSITORY_URL}</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">type</span>: <span style="color:#ae81ff">Git</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">strategy</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">sourceStrategy</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">from</span>:
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">ImageStreamTag</span>
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">name</span>: <span style="color:#ae81ff">golang-s2i:latest</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">type</span>: <span style="color:#ae81ff">Source</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">triggers</span>:
+</span></span><span style="display:flex;"><span>    - <span style="color:#f92672">type</span>: <span style="color:#ae81ff">ImageChange</span>
+</span></span><span style="display:flex;"><span>    - <span style="color:#f92672">type</span>: <span style="color:#ae81ff">ConfigChange</span>
+</span></span><span style="display:flex;"><span>    - <span style="color:#f92672">github</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">secret</span>: <span style="color:#ae81ff">${APP_GITHUB_WEBHOOK_SECRET}</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">type</span>: <span style="color:#ae81ff">GitHub</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">apiVersion</span>: <span style="color:#ae81ff">v1</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">DeploymentConfig</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">annotations</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Defines how to deploy the application server</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">spec</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">replicas</span>: <span style="color:#ae81ff">1</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">selector</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">strategy</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">type</span>: <span style="color:#ae81ff">Rolling</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">template</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">labels</span>:
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">spec</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">containers</span>:
+</span></span><span style="display:flex;"><span>        - <span style="color:#f92672">env</span>:
+</span></span><span style="display:flex;"><span>          - <span style="color:#f92672">name</span>: <span style="color:#ae81ff">ARGS</span>
+</span></span><span style="display:flex;"><span>            <span style="color:#f92672">value</span>: <span style="color:#ae81ff">${APP_ARGS}</span>
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">image</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">ports</span>:
+</span></span><span style="display:flex;"><span>          - <span style="color:#f92672">containerPort</span>: <span style="color:#ae81ff">8080</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">triggers</span>:
+</span></span><span style="display:flex;"><span>    - <span style="color:#f92672">imageChangeParams</span>:
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">automatic</span>: <span style="color:#66d9ef">true</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">containerNames</span>:
+</span></span><span style="display:flex;"><span>        - <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>        <span style="color:#f92672">from</span>:
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">ImageStreamTag</span>
+</span></span><span style="display:flex;"><span>          <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}:latest</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">type</span>: <span style="color:#ae81ff">ImageChange</span>
+</span></span><span style="display:flex;"><span>    - <span style="color:#f92672">type</span>: <span style="color:#ae81ff">ConfigChange</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">apiVersion</span>: <span style="color:#ae81ff">v1</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">Service</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">annotations</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Exposes and load balances the application pods</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">spec</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">ports</span>:
+</span></span><span style="display:flex;"><span>    - <span style="color:#f92672">name</span>: <span style="color:#ae81ff">web</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">port</span>: <span style="color:#ae81ff">8080</span>
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">targetPort</span>: <span style="color:#ae81ff">8080</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">selector</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">apiVersion</span>: <span style="color:#ae81ff">v1</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">id</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">kind</span>: <span style="color:#ae81ff">Route</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">metadata</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">annotations</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Route for application&#39;s http service.</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">labels</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">application</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">spec</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">host</span>: <span style="color:#ae81ff">${APPLICATION_DOMAIN}</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#f92672">to</span>:
+</span></span><span style="display:flex;"><span>      <span style="color:#f92672">name</span>: <span style="color:#ae81ff">${APPLICATION_NAME}</span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">parameters</span>:
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#ae81ff">The URL of the repository with your Golang application code</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APP_SOURCE_REPOSITORY_URL</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application Source URL</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Set this to a branch name, tag or other ref of your repository if you</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#ae81ff">are not using the default branch</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APP_SOURCE_REPOSITORY_REF</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application Source Branch</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Set this to the relative path to your project if it is not in the root</span>
+</span></span><span style="display:flex;"><span>    <span style="color:#ae81ff">of your repository</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APP_CONTEXT_DIR</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application Source Directory</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#ae81ff">A secret string used to configure the GitHub webhook for the app repo</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">from</span>: <span style="color:#e6db74">&#39;[a-zA-Z0-9]{40}&#39;</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">generate</span>: <span style="color:#ae81ff">expression</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APP_GITHUB_WEBHOOK_SECRET</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application GitHub Web Hook Secret</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#ae81ff">The name for the application.</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APPLICATION_NAME</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">required</span>: <span style="color:#66d9ef">true</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">value</span>: <span style="color:#ae81ff">golang-app</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application Name</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#e6db74">&#39;Custom hostname for service routes.  Leave blank for default hostname,
+</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    e.g.: &lt;application-name&gt;.&lt;project&gt;.&lt;default-domain-suffix&gt;&#39;</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APPLICATION_DOMAIN</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application Domain</span>
+</span></span><span style="display:flex;"><span>- <span style="color:#f92672">description</span>: <span style="color:#ae81ff">Command line arguments to provide to the Golang application</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">name</span>: <span style="color:#ae81ff">APP_ARGS</span>
+</span></span><span style="display:flex;"><span>  <span style="color:#f92672">displayName</span>: <span style="color:#ae81ff">Application Command Line Arguments</span>
+</span></span></code></pre></div>
     </div>
   </div>
 </div>
@@ -538,17 +538,17 @@ <h2 id="step-5---create-the-import">Step 5 - Create the Import</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsea2a3613879c4ecdb9f8b20c105f3c529" class="collapsed">
+      <a data-toggle="collapse" href="#collapsefa2eca167eaceec4a82f77d89dcaadbe" class="collapsed">
       
         Configure Import YAML/JSON
       </a>
     </h4>
   </div>
   
-  <div id="collapsea2a3613879c4ecdb9f8b20c105f3c529" class="panel-collapse collapse ">
+  <div id="collapsefa2eca167eaceec4a82f77d89dcaadbe" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/import_config.png" width="700" /></p>
+       <img src="../images/import_config.png" width="700" />
 
     </div>
   </div>
@@ -567,17 +567,17 @@ <h2 id="step-6---add-the-template">Step 6 - Add the Template</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse11f0e04d346924cf9d7f226728655bf2" class="collapsed">
+      <a data-toggle="collapse" href="#collapseef49f28af3f7cf1be3552c3175922076" class="collapsed">
       
         Add Template
       </a>
     </h4>
   </div>
   
-  <div id="collapse11f0e04d346924cf9d7f226728655bf2" class="panel-collapse collapse ">
+  <div id="collapseef49f28af3f7cf1be3552c3175922076" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/add_template.png" width="400" /></p>
+       <img src="../images/add_template.png" width="400" />
 
     </div>
   </div>
@@ -597,17 +597,17 @@ <h2 id="step-7---select-the-template">Step 7 - Select the Template</h2>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse5333d7b429b5174599385c49eaf53b96" class="collapsed">
+      <a data-toggle="collapse" href="#collapse81cac5af9185144d99d2e8e2b54540d2" class="collapsed">
       
         Select Template
       </a>
     </h4>
   </div>
   
-  <div id="collapse5333d7b429b5174599385c49eaf53b96" class="panel-collapse collapse ">
+  <div id="collapse81cac5af9185144d99d2e8e2b54540d2" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/select_from_project.png" width="600" /></p>
+       <img src="../images/select_from_project.png" width="600" />
 
     </div>
   </div>
@@ -625,17 +625,17 @@ <h2 id="step-8---really-select-the-template">Step 8 - Really Select the Template
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse8909cdb1ad14b2fdd8c92add43a17dca" class="collapsed">
+      <a data-toggle="collapse" href="#collapsedae65372d6c8a17756af7cb545e934ec" class="collapsed">
       
         Really Select Template
       </a>
     </h4>
   </div>
   
-  <div id="collapse8909cdb1ad14b2fdd8c92add43a17dca" class="panel-collapse collapse ">
+  <div id="collapsedae65372d6c8a17756af7cb545e934ec" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/golang_template.png" width="600" /></p>
+       <img src="../images/golang_template.png" width="600" />
 
     </div>
   </div>
@@ -652,12 +652,12 @@ <h2 id="step-9---configure-the-deployment">Step 9 - Configure the Deployment</h2
 <p>In the <strong>Application Source URL</strong> field, enter <a href="https://github.com/kevensen/openshift-gochat-client.git">https://github.com/kevensen/openshift-gochat-client.git</a></p>
 <p>In the <strong>Application Name</strong> field, enter <strong>gochat-client</strong></p>
 <p>In the <strong>Application Command Line Arguments</strong> field, enter the following:</p>
-<pre><code class="language-terminal" data-lang="terminal">-host :8080 -chatServer gochat-server.gochat-server.svc.cluster.local:8080 -templatePath /opt/app-root/gopath/src/github.com/kevensen/openshift-gochat-client/templates -logtostderr -insecure
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">-host :8080 -chatServer gochat-server.gochat-server.svc.cluster.local:8080 -templatePath /opt/app-root/gopath/src/github.com/kevensen/openshift-gochat-client/templates -logtostderr -insecure
 </code></pre><p>Click <strong>Create</strong></p>
 <h2 id="step-10---annotate-the-service-account-to-use-openshift-authorization">Step 10 - Annotate the Service Account to Use OpenShift Authorization</h2>
 <p>As in the previous lab, we must annotate the service account for the Gochat Client to communicate to the OpenShift API for user credential verification.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1='{&quot;kind&quot;:&quot;OAuthRedirectReference&quot;,&quot;apiVersion&quot;:&quot;v1&quot;,&quot;reference&quot;:{&quot;kind&quot;:&quot;Route&quot;,&quot;name&quot;:&quot;gochat-client&quot;}}' --overwrite
-</code></pre><pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1=&#39;{&#34;kind&#34;:&#34;OAuthRedirectReference&#34;,&#34;apiVersion&#34;:&#34;v1&#34;,&#34;reference&#34;:{&#34;kind&#34;:&#34;Route&#34;,&#34;name&#34;:&#34;gochat-client&#34;}}&#39; --overwrite
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
 </code></pre><h2 id="step-11---sign-in-to-the-app">Step 11 - Sign in to the App</h2>
 <p>Click the blue &ldquo;Login&rdquo; button.
 <div class="panel-group">
@@ -694,17 +694,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse25334dab422259edec074ef48abe1742" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec7de9cf6870f4812de3e9c44da5d5129" class="collapsed">
       
         OpenShift WebUI Login
       </a>
     </h4>
   </div>
   
-  <div id="collapse25334dab422259edec074ef48abe1742" class="panel-collapse collapse ">
+  <div id="collapsec7de9cf6870f4812de3e9c44da5d5129" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/webui.png" width="1000" /></p>
+       <img src="../images/webui.png" width="1000" />
 
     </div>
   </div>
@@ -841,7 +841,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1101,7 +1101,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1213,7 +1213,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1223,7 +1223,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1306,7 +1306,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/index.html b/workshops/source_to_image/index.html
index 30bae469d..54bc9a18d 100644
--- a/workshops/source_to_image/index.html
+++ b/workshops/source_to_image/index.html
@@ -464,7 +464,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -724,7 +724,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -836,7 +836,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -846,7 +846,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -896,7 +896,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/index.xml b/workshops/source_to_image/index.xml
index 09f48889e..84abf94b6 100644
--- a/workshops/source_to_image/index.xml
+++ b/workshops/source_to_image/index.xml
@@ -4,101 +4,64 @@
     <title>Source to Image on Red Hat | Public Sector</title>
     <link>/workshops/source_to_image/</link>
     <description>Recent content in Source to Image on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/source_to_image/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/source_to_image/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Conclusion</title>
       <link>/workshops/source_to_image/conclusion/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/conclusion/</guid>
-      <description>Congratulations You have gone through a methodical process to develop container technology that is custom to a framework, yet repeatable. We have:
-  Run the application from the command line to understand what it does and how it is supposed to behave.
-  Containerized the applicaiton.
-  Built Source-to-Image mechanisms that allow us to inject raw source code to be built inside the container.
-  Created an OpenShift template to make repeated deployments easier.</description>
+      <description>Congratulations You have gone through a methodical process to develop container technology that is custom to a framework, yet repeatable. We have:&#xA;Run the application from the command line to understand what it does and how it is supposed to behave.&#xA;Containerized the applicaiton.&#xA;Built Source-to-Image mechanisms that allow us to inject raw source code to be built inside the container.&#xA;Created an OpenShift template to make repeated deployments easier.</description>
     </item>
-    
     <item>
       <title>Lab - Containerize the App</title>
       <link>/workshops/source_to_image/containerize_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/containerize_app/</guid>
-      <description>Introduction Now we want to containerize the Gochat app. If you are using the CLI on your own computer, you could use the docker command. However, if you are in the Wetty terminal, remember you are actually in a container. We could have exposed the container socket on the host to your Wetty container. However, this would break the security model.
-Fortunately we can build from a Dockerfile using the oc command line tool.</description>
+      <description>Introduction Now we want to containerize the Gochat app. If you are using the CLI on your own computer, you could use the docker command. However, if you are in the Wetty terminal, remember you are actually in a container. We could have exposed the container socket on the host to your Wetty container. However, this would break the security model.&#xA;Fortunately we can build from a Dockerfile using the oc command line tool.</description>
     </item>
-    
     <item>
       <title>Lab - Gochat S2I</title>
       <link>/workshops/source_to_image/gochat_s2i/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/gochat_s2i/</guid>
-      <description>Step 1 - Create a New Project Space In the Wetty terminal, create a new project.
-oc new-project gochat-s2i-userYOUR# Step 2 - Create the Golang S2I Builder Image Create a new build for the Golang S2I builder image
-cd ~ oc new-build golang-s2i/ --to=golang-s2i Start the new build for the Golang S2I builder image
-oc start-build golang-s2i --from-dir=golang-s2i/ Step 3 - Import YAML Template in to OpenShift In the OpenShift WebUI, on the catalog page, seclect Import YAML/JSON Import YAML/JSON        Step 4 - Configure the Import Select the project to which you want to import the template</description>
+      <description>Step 1 - Create a New Project Space In the Wetty terminal, create a new project.&#xA;oc new-project gochat-s2i-userYOUR# Step 2 - Create the Golang S2I Builder Image Create a new build for the Golang S2I builder image&#xA;cd ~ oc new-build golang-s2i/ --to=golang-s2i Start the new build for the Golang S2I builder image&#xA;oc start-build golang-s2i --from-dir=golang-s2i/ Step 3 - Import YAML Template in to OpenShift In the OpenShift WebUI, on the catalog page, seclect Import YAML/JSON Import YAML/JSON Step 4 - Configure the Import Select the project to which you want to import the template</description>
     </item>
-    
     <item>
       <title>Lab - Roll Dice</title>
       <link>/workshops/source_to_image/dice/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/dice/</guid>
-      <description>In an attempt at nostalgia, we are going to once again create an S2I builder, this time for a Fortran app. Yes, Fortran. The objective is to make our little chat program a bit more interesting.
-Step 1 - Create the S2I Project cd ~ s2i create fortran-s2i fortran-s2i Step 2 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/fortran-s2i/Dockerfile vi ~/fortran-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
+      <description>In an attempt at nostalgia, we are going to once again create an S2I builder, this time for a Fortran app. Yes, Fortran. The objective is to make our little chat program a bit more interesting.&#xA;Step 1 - Create the S2I Project cd ~ s2i create fortran-s2i fortran-s2i Step 2 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/fortran-s2i/Dockerfile vi ~/fortran-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
     </item>
-    
     <item>
       <title>Lab - Run the App</title>
       <link>/workshops/source_to_image/run_the_app/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/run_the_app/</guid>
-      <description>Step 1 - Create a Route to the Gochat Service First we expose the pod with a service.
-oc expose dc wetty --port=8080 --target-port=8080 --name=gochat Then we expose the service with a route.
-oc expose svc gochat Step 2 - Download the App Source go get -d github.com/kevensen/openshift-gochat-client Step 3 - Build the App cd go/src/github.com/kevensen/openshift-gochat-client glide install -v &amp;amp;&amp;amp; go install Step 4 - Annotate the Service Account to Use OpenShift Authorization These annotations allow for the Gochat Client to communicate to the OpenShift API for user credential verification.</description>
+      <description>Step 1 - Create a Route to the Gochat Service First we expose the pod with a service.&#xA;oc expose dc wetty --port=8080 --target-port=8080 --name=gochat Then we expose the service with a route.&#xA;oc expose svc gochat Step 2 - Download the App Source go get -d github.com/kevensen/openshift-gochat-client Step 3 - Build the App cd go/src/github.com/kevensen/openshift-gochat-client glide install -v &amp;amp;&amp;amp; go install Step 4 - Annotate the Service Account to Use OpenShift Authorization These annotations allow for the Gochat Client to communicate to the OpenShift API for user credential verification.</description>
     </item>
-    
     <item>
       <title>Lab - Source-to-Image</title>
       <link>/workshops/source_to_image/source_to_image/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/source_to_image/</guid>
-      <description>Step 1 - Create a new Project Space In the Wetty terminal, create a new project.
-oc new-project s2i-userYOUR# Step 2 - Go Get S2I Library cd ~ go get github.com/openshift/source-to-image Step 3 - Build the S2I Tooling cd $GOPATH/src/github.com/openshift/source-to-image hack/build-go.sh export PATH=$PATH:${GOPATH}/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64/ Step 4 - Create the S2I Project cd ~ s2i create golang-s2i golang-s2i Now let&amp;rsquo;s inspect the project directory
-tree -a golang-s2i Step 5 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/golang-s2i/Dockerfile vi ~/golang-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
+      <description>Step 1 - Create a new Project Space In the Wetty terminal, create a new project.&#xA;oc new-project s2i-userYOUR# Step 2 - Go Get S2I Library cd ~ go get github.com/openshift/source-to-image Step 3 - Build the S2I Tooling cd $GOPATH/src/github.com/openshift/source-to-image hack/build-go.sh export PATH=$PATH:${GOPATH}/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64/ Step 4 - Create the S2I Project cd ~ s2i create golang-s2i golang-s2i Now let&amp;rsquo;s inspect the project directory&#xA;tree -a golang-s2i Step 5 - Edit the Dockerfile cd ~ cat /dev/null &amp;gt; ~/golang-s2i/Dockerfile vi ~/golang-s2i/Dockerfile Copy the following text and paste it in to the editor.</description>
     </item>
-    
     <item>
       <title>Prerequisites</title>
       <link>/workshops/source_to_image/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/prerequisites/</guid>
-      <description>Getting Started If you choose to work from your own command line, instead of the web terminal (Wetty) environment, that&amp;rsquo;s just fine! You&amp;rsquo;ll have to install a few of utilities first.
-Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.
-Install git Click here for instructions on how to install Git on your workstation.
-Install golang Click here for instructions on how to install Golang.</description>
+      <description>Getting Started If you choose to work from your own command line, instead of the web terminal (Wetty) environment, that&amp;rsquo;s just fine! You&amp;rsquo;ll have to install a few of utilities first.&#xA;Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.&#xA;Install git Click here for instructions on how to install Git on your workstation.&#xA;Install golang Click here for instructions on how to install Golang.</description>
     </item>
-    
     <item>
       <title>The Setup</title>
       <link>/workshops/source_to_image/setup/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/source_to_image/setup/</guid>
-      <description>Step 1 - Log in to the Web User Interface The workshop moderator will provide you with the URL, your username, and password.
-OpenShift WebUI Login        Step 2 - Create a Project for Your Wetty Terminal Create a new project by clicking the &amp;ldquo;New Project&amp;rdquo; button in the upper right of the WebUI.
-Create a Project        Step 3 - Name Your Project Name your project as follows.</description>
+      <description>Step 1 - Log in to the Web User Interface The workshop moderator will provide you with the URL, your username, and password.&#xA;OpenShift WebUI Login Step 2 - Create a Project for Your Wetty Terminal Create a new project by clicking the &amp;ldquo;New Project&amp;rdquo; button in the upper right of the WebUI.&#xA;Create a Project Step 3 - Name Your Project Name your project as follows.&#xA;wetty-userYOUR# Name the Project Step 4 - Add Wetty to the Project In the Search Catalog bar, enter the name of the template to search for, in this case wetty-persistant.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/source_to_image/prerequisites/index.html b/workshops/source_to_image/prerequisites/index.html
index d17d59b40..45e81c85b 100644
--- a/workshops/source_to_image/prerequisites/index.html
+++ b/workshops/source_to_image/prerequisites/index.html
@@ -420,7 +420,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -680,7 +680,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -792,7 +792,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -802,7 +802,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -881,7 +881,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/run_the_app/index.html b/workshops/source_to_image/run_the_app/index.html
index 2bb851d4b..bed566e48 100644
--- a/workshops/source_to_image/run_the_app/index.html
+++ b/workshops/source_to_image/run_the_app/index.html
@@ -319,21 +319,21 @@ <h1>Lab - Run the App</h1>
 
     <h2 id="step-1---create-a-route-to-the-gochat-service">Step 1 - Create a Route to the Gochat Service</h2>
 <p>First we expose the pod with a service.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc expose dc wetty --port=8080 --target-port=8080 --name=gochat
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc expose dc wetty --port=8080 --target-port=8080 --name=gochat
 </code></pre><p>Then we expose the service with a route.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc expose svc gochat
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc expose svc gochat
 </code></pre><h2 id="step-2---download-the-app-source">Step 2 - Download the App Source</h2>
-<pre><code class="language-terminal" data-lang="terminal">go get -d github.com/kevensen/openshift-gochat-client
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">go get -d github.com/kevensen/openshift-gochat-client
 </code></pre><h2 id="step-3---build-the-app">Step 3 - Build the App</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd go/src/github.com/kevensen/openshift-gochat-client
-</code></pre><pre><code class="language-terminal" data-lang="terminal">glide install -v &amp;&amp; go install
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd go/src/github.com/kevensen/openshift-gochat-client
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">glide install -v &amp;&amp; go install
 </code></pre><h2 id="step-4---annotate-the-service-account-to-use-openshift-authorization">Step 4 - Annotate the Service Account to Use OpenShift Authorization</h2>
 <p>These annotations allow for the Gochat Client to communicate to the OpenShift API for user credential verification.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1='{&quot;kind&quot;:&quot;OAuthRedirectReference&quot;,&quot;apiVersion&quot;:&quot;v1&quot;,&quot;reference&quot;:{&quot;kind&quot;:&quot;Route&quot;,&quot;name&quot;:&quot;gochat&quot;}}' --overwrite
-</code></pre><pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1=&#39;{&#34;kind&#34;:&#34;OAuthRedirectReference&#34;,&#34;apiVersion&#34;:&#34;v1&#34;,&#34;reference&#34;:{&#34;kind&#34;:&#34;Route&#34;,&#34;name&#34;:&#34;gochat&#34;}}&#39; --overwrite
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
 </code></pre><h2 id="step-5---run-the-app">Step 5 - Run the App</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">openshift-gochat-client -host :8080 -chatServer gochat-server.gochat-server.svc.cluster.local:8080 -templatePath go/src/github.com/kevensen/openshift-gochat-client/templates -logtostderr -insecure
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">openshift-gochat-client -host :8080 -chatServer gochat-server.gochat-server.svc.cluster.local:8080 -templatePath go/src/github.com/kevensen/openshift-gochat-client/templates -logtostderr -insecure
 </code></pre><h2 id="step-6---access-the-app">Step 6 - Access the App</h2>
 <p>Go back to the OpenShift WebUI and click on the &ldquo;gochat&rdquo; URL.</p>
 <div class="panel-group">
@@ -398,17 +398,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse25334dab422259edec074ef48abe1742" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec7de9cf6870f4812de3e9c44da5d5129" class="collapsed">
       
         OpenShift WebUI Login
       </a>
     </h4>
   </div>
   
-  <div id="collapse25334dab422259edec074ef48abe1742" class="panel-collapse collapse ">
+  <div id="collapsec7de9cf6870f4812de3e9c44da5d5129" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/webui.png" width="1000" /></p>
+       <img src="../images/webui.png" width="1000" />
 
     </div>
   </div>
@@ -547,7 +547,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -807,7 +807,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -919,7 +919,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -929,7 +929,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1012,7 +1012,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/setup/index.html b/workshops/source_to_image/setup/index.html
index 96f672bbb..22d590091 100644
--- a/workshops/source_to_image/setup/index.html
+++ b/workshops/source_to_image/setup/index.html
@@ -326,17 +326,17 @@ <h2 id="step-1---log-in-to-the-web-user-interface">Step 1 - Log in to the Web Us
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse25334dab422259edec074ef48abe1742" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec7de9cf6870f4812de3e9c44da5d5129" class="collapsed">
       
         OpenShift WebUI Login
       </a>
     </h4>
   </div>
   
-  <div id="collapse25334dab422259edec074ef48abe1742" class="panel-collapse collapse ">
+  <div id="collapsec7de9cf6870f4812de3e9c44da5d5129" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/webui.png" width="1000" /></p>
+       <img src="../images/webui.png" width="1000" />
 
     </div>
   </div>
@@ -532,7 +532,7 @@ <h4 class="panel-title">
 
 <h2 id="step-12---create-a-shared-screen">Step 12 - Create a Shared Screen</h2>
 <p>Creating a shared screen will allow the moderators to assist you better by viewing your terminal session.</p>
-<pre><code class="language-terminal" data-lang="terminal">screen -m -S shared-user<span class="userid">YOUR#</span>
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">screen -m -S shared-user<span class="userid">YOUR#</span>
 
 </code></pre><style>
 
@@ -633,7 +633,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -893,7 +893,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1005,7 +1005,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1015,7 +1015,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1098,7 +1098,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/source_to_image/source_to_image/index.html b/workshops/source_to_image/source_to_image/index.html
index 4216881c0..428dc4e33 100644
--- a/workshops/source_to_image/source_to_image/index.html
+++ b/workshops/source_to_image/source_to_image/index.html
@@ -319,68 +319,68 @@ <h1>Lab - Source-to-Image</h1>
 
     <h2 id="step-1---create-a-new-project-space">Step 1 - Create a new Project Space</h2>
 <p>In the Wetty terminal, create a new project.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc new-project s2i-user<span class="userid">YOUR#</span>
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-project s2i-user<span class="userid">YOUR#</span>
 
 </code></pre><h2 id="step-2---go-get-s2i-library">Step 2 - Go Get S2I Library</h2>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">cd ~
-</code></pre></div><pre><code class="language-terminal" data-lang="terminal">go get github.com/openshift/source-to-image
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>cd ~
+</span></span></code></pre></div><pre tabindex="0"><code class="language-terminal" data-lang="terminal">go get github.com/openshift/source-to-image
 </code></pre><h2 id="step-3---build-the-s2i-tooling">Step 3 - Build the S2I Tooling</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd $GOPATH/src/github.com/openshift/source-to-image
-</code></pre><pre><code class="language-terminal" data-lang="terminal">hack/build-go.sh
-</code></pre><pre><code class="language-terminal" data-lang="terminal">export PATH=$PATH:${GOPATH}/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64/
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd $GOPATH/src/github.com/openshift/source-to-image
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">hack/build-go.sh
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">export PATH=$PATH:${GOPATH}/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64/
 </code></pre><h2 id="step-4---create-the-s2i-project">Step 4 - Create the S2I Project</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">s2i create golang-s2i golang-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">s2i create golang-s2i golang-s2i
 </code></pre><p>Now let&rsquo;s inspect the project directory</p>
-<pre><code class="language-terminal" data-lang="terminal">tree -a golang-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">tree -a golang-s2i
 </code></pre><h2 id="step-5---edit-the-dockerfile">Step 5 - Edit the Dockerfile</h2>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/Dockerfile
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/Dockerfile
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/Dockerfile
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/Dockerfile
 </code></pre><p>Copy the following text and paste it in to the editor.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-Dockerfile" data-lang="Dockerfile"><span style="color:#75715e"># golang-s2i</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">FROM</span><span style="color:#e6db74"> fedora</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> BUILDER_VERSION 1.0<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> HOME /opt/app-root<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> GOPATH $HOME/gopath<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> PATH $PATH:$GOROOT/bin:$GOBIN<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">LABEL</span> io.k8s.description<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;Platform for building go based programs&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.k8s.display-name<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;gobuilder 0.0.1&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.openshift.expose-services<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;8080:http&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.openshift.tags<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;gobuilder,0.0.1&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.openshift.s2i.scripts-url<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;image:///usr/local/s2i&#34;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>      io.openshift.s2i.destination<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;/opt/app-root/destination&#34;</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> yum clean all <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>    yum install -y git-remote-bzr <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>                   golang <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>		           glide <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>    yum clean all <span style="color:#f92672">&amp;&amp;</span> rm -rf /var/cache/yum/*<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">COPY</span> ./s2i/bin/ /usr/local/s2i<span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> useradd -u <span style="color:#ae81ff">1001</span> -r -g <span style="color:#ae81ff">0</span> -d <span style="color:#e6db74">${</span>HOME<span style="color:#e6db74">}</span> -s /sbin/nologin -c <span style="color:#e6db74">&#34;Default Application User&#34;</span> default <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>    mkdir -p /opt/app-root/destination/<span style="color:#f92672">{</span>src,artifacts<span style="color:#f92672">}</span> <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\ </span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span>    chown -R 1001:0 $HOME <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
-</span><span style="color:#ae81ff"></span>    chmod -R og+rwx <span style="color:#e6db74">${</span>HOME<span style="color:#e6db74">}</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">WORKDIR</span><span style="color:#e6db74"> ${HOME}</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">USER</span><span style="color:#e6db74"> 1001</span><span style="color:#960050;background-color:#1e0010">
-</span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">EXPOSE</span><span style="color:#e6db74"> 8080</span><span style="color:#960050;background-color:#1e0010">
-</span></code></pre></div><p>To exit vi:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-Dockerfile" data-lang="Dockerfile"><span style="display:flex;"><span><span style="color:#75715e"># golang-s2i</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">FROM</span><span style="color:#e6db74"> fedora</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> BUILDER_VERSION 1.0<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> HOME /opt/app-root<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> GOPATH $HOME/gopath<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">ENV</span> PATH $PATH:$GOROOT/bin:$GOBIN<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">LABEL</span> io.k8s.description<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;Platform for building go based programs&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.k8s.display-name<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;gobuilder 0.0.1&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.openshift.expose-services<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;8080:http&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.openshift.tags<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;gobuilder,0.0.1&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.openshift.s2i.scripts-url<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;image:///usr/local/s2i&#34;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>      io.openshift.s2i.destination<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;/opt/app-root/destination&#34;</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> yum clean all <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>    yum install -y git-remote-bzr <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>                   golang <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>		           glide <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>    yum clean all <span style="color:#f92672">&amp;&amp;</span> rm -rf /var/cache/yum/*<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">COPY</span> ./s2i/bin/ /usr/local/s2i<span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">RUN</span> useradd -u <span style="color:#ae81ff">1001</span> -r -g <span style="color:#ae81ff">0</span> -d <span style="color:#e6db74">${</span>HOME<span style="color:#e6db74">}</span> -s /sbin/nologin -c <span style="color:#e6db74">&#34;Default Application User&#34;</span> default <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>    mkdir -p /opt/app-root/destination/<span style="color:#f92672">{</span>src,artifacts<span style="color:#f92672">}</span> <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\ </span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span>    chown -R 1001:0 $HOME <span style="color:#f92672">&amp;&amp;</span> <span style="color:#ae81ff">\
+</span></span></span><span style="display:flex;"><span><span style="color:#ae81ff"></span>    chmod -R og+rwx <span style="color:#e6db74">${</span>HOME<span style="color:#e6db74">}</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">WORKDIR</span><span style="color:#e6db74"> ${HOME}</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">USER</span><span style="color:#e6db74"> 1001</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span><span style="display:flex;"><span><span style="color:#960050;background-color:#1e0010"></span><span style="color:#66d9ef">EXPOSE</span><span style="color:#e6db74"> 8080</span><span style="color:#960050;background-color:#1e0010">
+</span></span></span></code></pre></div><p>To exit vi:</p>
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-6---edit-the-assemble-script">Step 6 - Edit the Assemble Script</h2>
-<pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/assemble
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/assemble
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/assemble
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/assemble
 </code></pre><p>Copy the following into the editor.</p>
-<pre><code class="language-terminal" data-lang="terminal">#!/bin/bash
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">#!/bin/bash
 #
-# S2I assemble script for the 'golang-s2i' image.
-export GO_REPO=$(echo $OPENSHIFT_BUILD_SOURCE | sed --expression='s/\.git//g' | sed --expression='s/https:\/\///g')
-if [ -z &quot;$GO_REPO&quot; ]; then
-  export GO_REPO=$(grep ^package /opt/app-root/destination/src/glide.yaml | sed 's/package: //')
+# S2I assemble script for the &#39;golang-s2i&#39; image.
+export GO_REPO=$(echo $OPENSHIFT_BUILD_SOURCE | sed --expression=&#39;s/\.git//g&#39; | sed --expression=&#39;s/https:\/\///g&#39;)
+if [ -z &#34;$GO_REPO&#34; ]; then
+  export GO_REPO=$(grep ^package /opt/app-root/destination/src/glide.yaml | sed &#39;s/package: //&#39;)
 fi
 
 mkdir -p $GOPATH/src/$GO_REPO
@@ -390,12 +390,12 @@ <h2 id="step-6---edit-the-assemble-script">Step 6 - Edit the Assemble Script</h2
 rm -rf /opt/app-root/destination/src/*
 
 # Restore build artifacts
-if [ &quot;$(ls /opt/app-root/destination/artifacts/ 2&gt;/dev/null)&quot; ]; then
-    echo &quot;Using artifacts from previous build.&quot;
+if [ &#34;$(ls /opt/app-root/destination/artifacts/ 2&gt;/dev/null)&#34; ]; then
+    echo &#34;Using artifacts from previous build.&#34;
     mv /opt/app-root/destination/artifacts/vendor $GOPATH/src/$GO_REPO/vendor
 else
     pushd $GOPATH/src/$GO_REPO
-    echo &quot;Obtaining artifacts.&quot;
+    echo &#34;Obtaining artifacts.&#34;
     glide install -v
     popd
 
@@ -406,23 +406,23 @@ <h2 id="step-6---edit-the-assemble-script">Step 6 - Edit the Assemble Script</h2
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-7---edit-the-run-script">Step 7 - Edit the Run Script</h2>
-<pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/run
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/run
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/run
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/run
 </code></pre><p>Copy the following into the editor.</p>
-<pre><code class="language-terminal" data-lang="terminal">#!/bin/bash
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">#!/bin/bash
 exec /opt/app-root/goexec $ARGS
 </code></pre><p>To exit vi:</p>
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-8---edit-the-save-artifacts-script">Step 8 - Edit the Save Artifacts Script</h2>
-<pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/save-artifacts
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/save-artifacts
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/save-artifacts
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/save-artifacts
 </code></pre><p>Copy the following into the editor.</p>
-<pre><code class="language-terminal" data-lang="terminal">#!/bin/bash
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">#!/bin/bash
 
-export GO_REPO=$(echo $OPENSHIFT_BUILD_SOURCE | sed --expression='s/\.git//g' | sed --expression='s/https:\/\///g')
-if [ -z &quot;$GO_REPO&quot; ]; then
-  export GO_REPO=$(grep ^package /opt/app-root/destination/src/glide.yaml | sed 's/package: //')
+export GO_REPO=$(echo $OPENSHIFT_BUILD_SOURCE | sed --expression=&#39;s/\.git//g&#39; | sed --expression=&#39;s/https:\/\///g&#39;)
+if [ -z &#34;$GO_REPO&#34; ]; then
+  export GO_REPO=$(grep ^package /opt/app-root/destination/src/glide.yaml | sed &#39;s/package: //&#39;)
 fi
 cd $GOPATH/src/$GO_REPO
 tar cf - vendor
@@ -430,32 +430,32 @@ <h2 id="step-8---edit-the-save-artifacts-script">Step 8 - Edit the Save Artifact
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-9---edit-the-usage-script">Step 9 - Edit the Usage Script</h2>
-<pre><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/usage
-</code></pre><pre><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/usage
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cat /dev/null &gt; ~/golang-s2i/s2i/bin/usage
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">vi ~/golang-s2i/s2i/bin/usage
 </code></pre><p>Create your own script!  Use the following as an example.</p>
-<pre><code class="language-terminal" data-lang="terminal">#!/bin/bash
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">#!/bin/bash
 
-echo &quot;Hello Golang&quot;
+echo &#34;Hello Golang&#34;
 </code></pre><p>To exit vi:</p>
 <p>shift+z</p>
 <p>shift+z</p>
 <h2 id="step-10---create-the-golang-s2i-builder-image">Step 10 - Create the Golang S2I Builder Image</h2>
 <p>Create a new build for the Golang S2I builder image</p>
-<pre><code class="language-terminal" data-lang="terminal">cd ~
-</code></pre><pre><code class="language-terminal" data-lang="terminal">oc new-build golang-s2i/ --to=golang-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">cd ~
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-build golang-s2i/ --to=golang-s2i
 </code></pre><p>Start the new build for the Golang S2I builder image</p>
-<pre><code class="language-terminal" data-lang="terminal">oc start-build golang-s2i --from-dir=golang-s2i/
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc start-build golang-s2i --from-dir=golang-s2i/
 </code></pre><h2 id="step-11---wait-for-build-to-complete">Step 11 - Wait for Build to Complete</h2>
 <p>Watch the deployment</p>
-<pre><code class="language-terminal" data-lang="terminal">oc logs -f bc/golang-s2i
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc logs -f bc/golang-s2i
 </code></pre><h2 id="step-12---deploy-the-app-from-the-s2i-builder-image">Step 12 - Deploy the App from the S2I Builder Image</h2>
-<pre><code class="language-terminal" data-lang="terminal">oc new-app https://github.com/kevensen/openshift-gochat-client.git --image-stream=golang-s2i --env ARGS=&quot;-host :8080 -chatServer gochat-server.gochat-server.svc.cluster.local:8080 -templatePath /opt/app-root/gopath/src/github.com/kevensen/openshift-gochat-client/templates -logtostderr -insecure&quot;
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc new-app https://github.com/kevensen/openshift-gochat-client.git --image-stream=golang-s2i --env ARGS=&#34;-host :8080 -chatServer gochat-server.gochat-server.svc.cluster.local:8080 -templatePath /opt/app-root/gopath/src/github.com/kevensen/openshift-gochat-client/templates -logtostderr -insecure&#34;
 </code></pre><h2 id="step-13---expose-the-app">Step 13 - Expose the App</h2>
-<pre><code class="language-terminal" data-lang="terminal">oc expose svc openshift-gochat-client
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc expose svc openshift-gochat-client
 </code></pre><h2 id="step-14---annotate-the-service-account-to-use-openshift-authorization">Step 14 - Annotate the Service Account to Use OpenShift Authorization</h2>
 <p>As in the previous lab, we must annotate the service account for the Gochat Client to communicate to the OpenShift API for user credential verification.</p>
-<pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1='{&quot;kind&quot;:&quot;OAuthRedirectReference&quot;,&quot;apiVersion&quot;:&quot;v1&quot;,&quot;reference&quot;:{&quot;kind&quot;:&quot;Route&quot;,&quot;name&quot;:&quot;openshift-gochat-client&quot;}}' --overwrite
-</code></pre><pre><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
+<pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirectreference.1=&#39;{&#34;kind&#34;:&#34;OAuthRedirectReference&#34;,&#34;apiVersion&#34;:&#34;v1&#34;,&#34;reference&#34;:{&#34;kind&#34;:&#34;Route&#34;,&#34;name&#34;:&#34;openshift-gochat-client&#34;}}&#39; --overwrite
+</code></pre><pre tabindex="0"><code class="language-terminal" data-lang="terminal">oc annotate sa/default serviceaccounts.openshift.io/oauth-redirecturi.1=auth/callback/openshift --overwrite
 </code></pre><h2 id="step-15---sign-in-to-the-app">Step 15 - Sign in to the App</h2>
 <p>Click the blue &ldquo;Login&rdquo; button.
 <div class="panel-group">
@@ -492,17 +492,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse25334dab422259edec074ef48abe1742" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec7de9cf6870f4812de3e9c44da5d5129" class="collapsed">
       
         OpenShift WebUI Login
       </a>
     </h4>
   </div>
   
-  <div id="collapse25334dab422259edec074ef48abe1742" class="panel-collapse collapse ">
+  <div id="collapsec7de9cf6870f4812de3e9c44da5d5129" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../images/webui.png" width="1000" /></p>
+       <img src="../images/webui.png" width="1000" />
 
     </div>
   </div>
@@ -639,7 +639,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-        <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+        <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -899,7 +899,7 @@ <h3></h3>
 
 <script type="text/javascript" src="/node_modules/js-cookie/src/js.cookie.js"></script>
 <script type="text/javascript">
-<!--
+
   
   var Cookies2 = Cookies.noConflict();
 
@@ -1011,7 +1011,7 @@ <h3></h3>
 
     return false;
   });
--->
+
 </script>
 
 <hr>
@@ -1021,7 +1021,7 @@ <h3>Workshop Details</h3>
         <td class="text-right"><b>Domain</b></td>
         <td><span class="domain"></span></td>
         <td rowspan="3">
-          <img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" alt="Red Hat Logo" />
+          <img src="/images/Logo-Red_Hat-C-Standard-RGB-small.png" alt="Red Hat Logo" />
         </td>
       </tr>
       <tr>
@@ -1104,7 +1104,7 @@ <h3>Workshop Details</h3>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/index.html b/workshops/strangling_the_monolith/index.html
index f99143853..ebbe14d46 100644
--- a/workshops/strangling_the_monolith/index.html
+++ b/workshops/strangling_the_monolith/index.html
@@ -359,7 +359,7 @@ <h2 id="labs">Labs</h2>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/index.xml b/workshops/strangling_the_monolith/index.xml
index 4faff4f3f..e96dc8213 100644
--- a/workshops/strangling_the_monolith/index.xml
+++ b/workshops/strangling_the_monolith/index.xml
@@ -4,75 +4,50 @@
     <title>Microservices Workshop - Strangling the Monolith on Red Hat | Public Sector</title>
     <link>/workshops/strangling_the_monolith/</link>
     <description>Recent content in Microservices Workshop - Strangling the Monolith on Red Hat | Public Sector</description>
-    <generator>Hugo -- gohugo.io</generator>
+    <generator>Hugo</generator>
     <language>en-us</language>
-    
-	<atom:link href="/workshops/strangling_the_monolith/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <atom:link href="/workshops/strangling_the_monolith/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Lab - Building and Deploying a Fast-Moving Monolith</title>
       <link>/workshops/strangling_the_monolith/lab1/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/lab1/</guid>
-      <description>FAST-MOVING MONOLITH  Large organizations have a tremendous amount of resources invested in existing monolith applications Looking for a sane way to capture the benefits of containers and orchestration without having to complete rewrite OpenShift provides the platform for their existing investment with the benefit of a path forward for microservice based apps in the future  FAST-MOVING MONOLITH ADVANTAGES  Easier to develop since all dependencies are included Single code base for teams to work on No API backwards compatibility issues since all logic is packaged with the application Single deployable unit  Step 1  In this lab, the coolstore monolith will be built and deployed to OpenShift from your local workstation demonstrating a typical Java application developer workflow A sample pipeline is included which will be used to deploy across dev and prod environment   First, deploy the coolstore monolith dev project (don’t forget to include -b app-partner when you run git clone - this is the branch in use for this lab!</description>
+      <description>FAST-MOVING MONOLITH Large organizations have a tremendous amount of resources invested in existing monolith applications Looking for a sane way to capture the benefits of containers and orchestration without having to complete rewrite OpenShift provides the platform for their existing investment with the benefit of a path forward for microservice based apps in the future FAST-MOVING MONOLITH ADVANTAGES Easier to develop since all dependencies are included Single code base for teams to work on No API backwards compatibility issues since all logic is packaged with the application Single deployable unit Step 1 In this lab, the coolstore monolith will be built and deployed to OpenShift from your local workstation demonstrating a typical Java application developer workflow A sample pipeline is included which will be used to deploy across dev and prod environment First, deploy the coolstore monolith dev project (don’t forget to include -b app-partner when you run git clone - this is the branch in use for this lab!</description>
     </item>
-    
     <item>
       <title>Lab - Login &amp; Tour of OpenShift</title>
       <link>/workshops/strangling_the_monolith/login_tour_oc/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/login_tour_oc/</guid>
-      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift you can skip this lab - after making sure you can login.
-Wetty Environment Links Your instructor will assign you an OpenShift environment and login.
-Please click &amp;ldquo;Return to Workshop&amp;rdquo; above to view the OpenShift Environment Links.</description>
+      <description>Welcome to OpenShift! This lab provides a quick tour of the console to help you get familiar with the user interface along with some key terminology we will use in subsequent lab content. If you are already familiar with the basics of OpenShift you can skip this lab - after making sure you can login.&#xA;Wetty Environment Links Your instructor will assign you an OpenShift environment and login.&#xA;Please click &amp;ldquo;Return to Workshop&amp;rdquo; above to view the OpenShift Environment Links.</description>
     </item>
-    
     <item>
       <title>Lab - Login &amp; Tour of Wetty</title>
       <link>/workshops/strangling_the_monolith/login_tour_wetty/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/login_tour_wetty/</guid>
-      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.
-Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for rthe workshopname.
-https://&amp;lt;workshopname&amp;gt;.wetty.redhatgov.io:8888 After logging in, you should see a shell.
-The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
+      <description>Introduction to Wetty (Browser-based SSH) This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.&#xA;Accessing Wetty Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for rthe workshopname.&#xA;https://&amp;lt;workshopname&amp;gt;.wetty.redhatgov.io:8888 After logging in, you should see a shell.&#xA;The wetty instance will already have the &amp;lsquo;oc&amp;rsquo; command installed on them.</description>
     </item>
-    
     <item>
       <title>Lab - Microservice Integration Patterns</title>
       <link>/workshops/strangling_the_monolith/lab3/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/lab3/</guid>
-      <description>Microservice Integration Patterns  In previous labs, we created two new microservices with the intention of replacing functionality (“strangling”) the monolithic application. Currently no traffic is routed to them. If you were to re-route traffic from the monolith’s /services/products API to the new catalog service’s /services/catalog endpoint, you would be missing the inventory data. In this lab we will consider different options and architectures for integrating the microservices’ functionality into our app.</description>
+      <description>Microservice Integration Patterns In previous labs, we created two new microservices with the intention of replacing functionality (“strangling”) the monolithic application. Currently no traffic is routed to them. If you were to re-route traffic from the monolith’s /services/products API to the new catalog service’s /services/catalog endpoint, you would be missing the inventory data. In this lab we will consider different options and architectures for integrating the microservices’ functionality into our app.</description>
     </item>
-    
     <item>
       <title>Lab - Strangle Your Monolith</title>
       <link>/workshops/strangling_the_monolith/lab2/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/lab2/</guid>
-      <description>Strangling the Monolith Design Pattern  Strangling - incrementally replacing functionality in app with something better (cheaper, faster, easier to maintain). As functionality is replaced, “dead” parts of monolith can be removed/retired. You can also wait for all functionality to be replaced before retiring anything! You can optionally include new functionality during strangulation to make it more attractive to business stakeholders.  
-https://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/
- Steps for Strangling the Monolith   Strangle Monolith   Strangle Monolith         Add a Microservice   Add a Microservice         And Another   And Another         Squeeze Monolith   Squeeze Monolith         And Remove Dead   And Remove Dead        Step 1  In this lab, you will begin to ‘strangle’ the coolstore monolith by implementing two of its services as external microservices, split along business boundaries Once implemented, traffic destined to the original monolith’s services will be redirected (via OpenShift software-defined routing) to the new services We will be using the Fabric8 Maven Plugin to automatically deploy to openshift    First, build and deploy the catalog microservice (Based on Spring Boot)   $ cd ~/coolstore $ git clone -b app-partner https://github.</description>
+      <description>Strangling the Monolith Design Pattern Strangling - incrementally replacing functionality in app with something better (cheaper, faster, easier to maintain). As functionality is replaced, “dead” parts of monolith can be removed/retired. You can also wait for all functionality to be replaced before retiring anything! You can optionally include new functionality during strangulation to make it more attractive to business stakeholders. https://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/&#xA;Steps for Strangling the Monolith Strangle Monolith Strangle Monolith Add a Microservice Add a Microservice And Another And Another Squeeze Monolith Squeeze Monolith And Remove Dead And Remove Dead Step 1 In this lab, you will begin to ‘strangle’ the coolstore monolith by implementing two of its services as external microservices, split along business boundaries Once implemented, traffic destined to the original monolith’s services will be redirected (via OpenShift software-defined routing) to the new services We will be using the Fabric8 Maven Plugin to automatically deploy to openshift First, build and deploy the catalog microservice (Based on Spring Boot) $ cd ~/coolstore $ git clone -b app-partner https://github.</description>
     </item>
-    
     <item>
       <title>Prerequisites</title>
       <link>/workshops/strangling_the_monolith/prerequisites/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
       <guid>/workshops/strangling_the_monolith/prerequisites/</guid>
-      <description>If we provided you a laptop or cloud environment. We already set all this up for you — feel free to skip everything below!
- Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.
-Install git Click here for instructions on how to install Git on your workstation.
-Create GitHub account Click here for instructions on how to setup an account.</description>
+      <description>If we provided you a laptop or cloud environment. We already set all this up for you — feel free to skip everything below!&#xA;Install oc Click here for instructions on how to install the OpenShift Container Platform CLI.&#xA;Install git Click here for instructions on how to install Git on your workstation.&#xA;Create GitHub account Click here for instructions on how to setup an account.</description>
     </item>
-    
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/workshops/strangling_the_monolith/lab1/index.html b/workshops/strangling_the_monolith/lab1/index.html
index c800728d0..8dca2a302 100644
--- a/workshops/strangling_the_monolith/lab1/index.html
+++ b/workshops/strangling_the_monolith/lab1/index.html
@@ -338,17 +338,17 @@ <h1 id="step-1">Step 1</h1>
 <blockquote>
 <p>First, deploy the coolstore monolith dev project (don’t forget to include -b app-partner when you run git clone - this is the branch in use for this lab!):</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ mkdir ~/coolstore
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd ~/coolstore
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ git clone -b app-partner https://github.com/epe105/monolith
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd monolith
-</code></pre></div><div class="alert alert-info">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ mkdir ~/coolstore
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd ~/coolstore
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ git clone -b app-partner https://github.com/epe105/monolith
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd monolith
+</span></span></code></pre></div><div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>Please update <code>&lt;USERNAME&gt;</code> below with your assigned username</p>
 </div>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project coolstore-&lt;USERNAME&gt;
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc process -f src/main/openshift/template.json | oc create -f -
-</code></pre></div><h1 id="step-2">Step 2</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project coolstore-&lt;USERNAME&gt;
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc process -f src/main/openshift/template.json | oc create -f -
+</span></span></code></pre></div><h1 id="step-2">Step 2</h1>
 <blockquote>
 <p>Notice there is no deployment yet as there is no build yet:</p>
 </blockquote>
@@ -359,17 +359,17 @@ <h1 id="step-1">Step 1</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseb56a8a76c5b3eeab3986e156c71c086d" class="collapsed">
+      <a data-toggle="collapse" href="#collapse3d474e07b770e80a2333db54a4859f01" class="collapsed">
       
         OpenShift Dev Deployment
       </a>
     </h4>
   </div>
   
-  <div id="collapseb56a8a76c5b3eeab3986e156c71c086d" class="panel-collapse collapse ">
+  <div id="collapse3d474e07b770e80a2333db54a4859f01" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc_coolstore_dev1.png" width="1000" /></p>
+       <img src="../img/lab1_oc_coolstore_dev1.png" width="1000" />
 
     </div>
   </div>
@@ -393,10 +393,10 @@ <h1 id="step-3">Step 3</h1>
 <blockquote>
 <p>Build the coolstore monolith (.war file) locally and deploy into the OpenShift via the binary build:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd ~/coolstore/monolith
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ mvn clean package -Popenshift
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc start-build coolstore --from-file deployments/ROOT.war --follow
-</code></pre></div><h1 id="step-4">Step 4</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd ~/coolstore/monolith
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ mvn clean package -Popenshift
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc start-build coolstore --from-file deployments/ROOT.war --follow
+</span></span></code></pre></div><h1 id="step-4">Step 4</h1>
 <ul>
 <li>Binary builds still produce Linux container images and are stored into the container registry.</li>
 </ul>
@@ -410,17 +410,17 @@ <h1 id="step-3">Step 3</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse6a47a3538a8acfd929a02d45f05f6ab3" class="collapsed">
+      <a data-toggle="collapse" href="#collapse1de685bc6a5c67b9d06ed738301b864b" class="collapsed">
       
         OpenShift Cool Store Build
       </a>
     </h4>
   </div>
   
-  <div id="collapse6a47a3538a8acfd929a02d45f05f6ab3" class="panel-collapse collapse ">
+  <div id="collapse1de685bc6a5c67b9d06ed738301b864b" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc_build_coolstore1.png" width="1000" /></p>
+       <img src="../img/lab1_oc_build_coolstore1.png" width="1000" />
 
     </div>
   </div>
@@ -440,17 +440,17 @@ <h1 id="step-5">Step 5</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse015d3b7ce5dcbf5cd877eb010785e0d0" class="collapsed">
+      <a data-toggle="collapse" href="#collapse0211283f1d5310854962361a2946cdae" class="collapsed">
       
         Cool Store UI
       </a>
     </h4>
   </div>
   
-  <div id="collapse015d3b7ce5dcbf5cd877eb010785e0d0" class="panel-collapse collapse ">
+  <div id="collapse0211283f1d5310854962361a2946cdae" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc_coolstore_gui1.png" width="1000" /></p>
+       <img src="../img/lab1_oc_coolstore_gui1.png" width="1000" />
 
     </div>
   </div>
@@ -471,30 +471,29 @@ <h1 id="step-6">Step 6</h1>
 <blockquote>
 <p>Make note of POSTGRESQL_PASSWORD</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc env dc/coolstore-dev-postgresql --list       <span style="color:#75715e"># copy value of POSTGRESQL_PASSWORD to clipboard</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc env dc/coolstore-dev-postgresql --list       <span style="color:#75715e"># copy value of POSTGRESQL_PASSWORD to clipboard</span>
+</span></span></code></pre></div><blockquote>
 <p>Make note of postgresql pod</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><blockquote>
 <p>oc rsh into postresql pod</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc rsh coolstore-dev-postgresql-1-3rfuw
-sh-4.2$ psql -h $HOSTNAME -d $POSTGRESQL_DATABASE -U $POSTGRESQL_USER
-Password <span style="color:#66d9ef">for</span> user userV31:XXXXXXXX
-psql <span style="color:#f92672">(</span>9.5.4<span style="color:#f92672">)</span>
-Type <span style="color:#e6db74">&#34;help&#34;</span> <span style="color:#66d9ef">for</span> help.
-
-monolith<span style="color:#f92672">=</span>&gt; <span style="color:#66d9ef">select</span> * from INVENTORY;
-monolith<span style="color:#f92672">=</span>&gt; <span style="color:#66d9ef">select</span> * from PRODUCT_CATALOG;
-
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc rsh coolstore-dev-postgresql-1-3rfuw
+</span></span><span style="display:flex;"><span>sh-4.2$ psql -h $HOSTNAME -d $POSTGRESQL_DATABASE -U $POSTGRESQL_USER
+</span></span><span style="display:flex;"><span>Password <span style="color:#66d9ef">for</span> user userV31:XXXXXXXX
+</span></span><span style="display:flex;"><span>psql <span style="color:#f92672">(</span>9.5.4<span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>Type <span style="color:#e6db74">&#34;help&#34;</span> <span style="color:#66d9ef">for</span> help.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>monolith<span style="color:#f92672">=</span>&gt; <span style="color:#66d9ef">select</span> * from INVENTORY;
+</span></span><span style="display:flex;"><span>monolith<span style="color:#f92672">=</span>&gt; <span style="color:#66d9ef">select</span> * from PRODUCT_CATALOG;
+</span></span></code></pre></div><blockquote>
 <p>Exit out of psql and then the postgresql pod</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">monolith<span style="color:#f92672">=</span>&gt; <span style="color:#ae81ff">\q</span>
-sh-4.2$ exit
-exit
-</code></pre></div><h1 id="step-7">Step 7</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>monolith<span style="color:#f92672">=</span>&gt; <span style="color:#ae81ff">\q</span>
+</span></span><span style="display:flex;"><span>sh-4.2$ exit
+</span></span><span style="display:flex;"><span>exit
+</span></span></code></pre></div><h1 id="step-7">Step 7</h1>
 <ul>
 <li>The coolstore-dev build and deployment is responsible for building new versions of the app after code changes and deploying them to the development environment.</li>
 <li>Production environments will ideally use different projects, and even different nodes in an OpenShift cluster. For simplicity we have dev and prod in the same project.</li>
@@ -502,8 +501,8 @@ <h1 id="step-6">Step 6</h1>
 <blockquote>
 <p>Create the production deployment objects that will be used to promote builds from dev to prod using the supplied CI/CD pipeline:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc process -f ~/coolstore/monolith/src/main/openshift/template-prod.json | oc create -f -
-</code></pre></div><h1 id="step-8">Step 8</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc process -f ~/coolstore/monolith/src/main/openshift/template-prod.json | oc create -f -
+</span></span></code></pre></div><h1 id="step-8">Step 8</h1>
 <ul>
 <li>Several types of OpenShift objects are created:
 <ul>
@@ -520,12 +519,11 @@ <h1 id="step-6">Step 6</h1>
 <blockquote>
 <p>Inspect the pipeline and observe the steps it executes during the pipeline run. Notice at the end of the script, the latest coolstore image is tagged with :prod, triggering a production deployment:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get bc/monolith-pipeline -o yaml
-...
-          openshiftTag<span style="color:#f92672">(</span>sourceStream: <span style="color:#e6db74">&#39;coolstore&#39;</span>, sourceTag: <span style="color:#e6db74">&#39;latest&#39;</span>, namespace: <span style="color:#e6db74">&#39;&#39;</span>, destinationStream: <span style="color:#e6db74">&#39;coolstore&#39;</span>, destinationTag: <span style="color:#e6db74">&#39;prod&#39;</span>, destinationNamespace: <span style="color:#e6db74">&#39;&#39;</span><span style="color:#f92672">)</span>
-...
-
-</code></pre></div><h1 id="step-9">Step 9</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get bc/monolith-pipeline -o yaml
+</span></span><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>          openshiftTag<span style="color:#f92672">(</span>sourceStream: <span style="color:#e6db74">&#39;coolstore&#39;</span>, sourceTag: <span style="color:#e6db74">&#39;latest&#39;</span>, namespace: <span style="color:#e6db74">&#39;&#39;</span>, destinationStream: <span style="color:#e6db74">&#39;coolstore&#39;</span>, destinationTag: <span style="color:#e6db74">&#39;prod&#39;</span>, destinationNamespace: <span style="color:#e6db74">&#39;&#39;</span><span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div><h1 id="step-9">Step 9</h1>
 <blockquote>
 <p>Wait for the jenkins service to be completely available, then execute the pipeline by navigating to Builds→ Pipelines and click on Start Pipeline next to the Monolith Pipeline:</p>
 </blockquote>
@@ -536,17 +534,17 @@ <h1 id="step-6">Step 6</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse560d2c7b3dbb21dfe18953457733577b" class="collapsed">
+      <a data-toggle="collapse" href="#collapse7c0a6fcea806fdea28c451c5a8eddf9b" class="collapsed">
       
         Monolith Pipeline
       </a>
     </h4>
   </div>
   
-  <div id="collapse560d2c7b3dbb21dfe18953457733577b" class="panel-collapse collapse ">
+  <div id="collapse7c0a6fcea806fdea28c451c5a8eddf9b" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc_pipeline_coolstore1.png" width="1000" /></p>
+       <img src="../img/lab1_oc_pipeline_coolstore1.png" width="1000" />
 
     </div>
   </div>
@@ -572,17 +570,17 @@ <h1 id="step-10">Step 10</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse4ebf36ae42a4f8fea67f59df34213a40" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef92ca6cbe42a302b789d92b9e321c507" class="collapsed">
       
         Pipelines
       </a>
     </h4>
   </div>
   
-  <div id="collapse4ebf36ae42a4f8fea67f59df34213a40" class="panel-collapse collapse ">
+  <div id="collapsef92ca6cbe42a302b789d92b9e321c507" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc_pipeline_coolstore2.png" width="1000" /></p>
+       <img src="../img/lab1_oc_pipeline_coolstore2.png" width="1000" />
 
     </div>
   </div>
@@ -602,17 +600,17 @@ <h1 id="step-11">Step 11</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapseffd164e44f4bd80ada120afbd3f9021a" class="collapsed">
+      <a data-toggle="collapse" href="#collapse2d8236af0ac360e627075276978bc2c1" class="collapsed">
       
         OpenShift Dev and Prod Container Deployment
       </a>
     </h4>
   </div>
   
-  <div id="collapseffd164e44f4bd80ada120afbd3f9021a" class="panel-collapse collapse ">
+  <div id="collapse2d8236af0ac360e627075276978bc2c1" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc__coolstore_prod1.png" width="1000" /></p>
+       <img src="../img/lab1_oc__coolstore_prod1.png" width="1000" />
 
     </div>
   </div>
@@ -632,17 +630,17 @@ <h1 id="step-12">Step 12</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsed65181f1de18895b52c0743d35db69cc" class="collapsed">
+      <a data-toggle="collapse" href="#collapseeb702c58413161c930af021a5b05a100" class="collapsed">
       
         Scale Down Dev Containers
       </a>
     </h4>
   </div>
   
-  <div id="collapsed65181f1de18895b52c0743d35db69cc" class="panel-collapse collapse ">
+  <div id="collapseeb702c58413161c930af021a5b05a100" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab1_oc_dev_containers1.png" width="1000" /></p>
+       <img src="../img/lab1_oc_dev_containers1.png" width="1000" />
 
     </div>
   </div>
@@ -654,8 +652,8 @@ <h4 class="panel-title">
 <div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>If your build pipeline fails to start, you can manually tag the images:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc tag coolstore:latest coolstore:prod
-</code></pre></div></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc tag coolstore:latest coolstore:prod
+</span></span></code></pre></div></div>
 
 
     
@@ -695,7 +693,7 @@ <h4 class="panel-title">
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/lab2/index.html b/workshops/strangling_the_monolith/lab2/index.html
index 859dce809..dbaaf53ec 100644
--- a/workshops/strangling_the_monolith/lab2/index.html
+++ b/workshops/strangling_the_monolith/lab2/index.html
@@ -324,7 +324,7 @@ <h1 id="strangling-the-monolith-design-pattern">Strangling the Monolith Design P
 <li>You can also wait for all functionality to be replaced before retiring anything!</li>
 <li>You can optionally include new functionality during strangulation to make it more attractive to business stakeholders.</li>
 </ul>
-<p><img src="../img/lab2_stm_over_time.png" width="700" /></p>
+<img src="../img/lab2_stm_over_time.png" width="700" />
 <div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p><a href="https://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/">https://paulhammant.com/2013/07/14/legacy-application-strangulation-case-studies/</a></p>
@@ -342,17 +342,17 @@ <h1 id="steps-for-strangling-the-monolith">Steps for Strangling the Monolith</h1
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse6cf39d9b768548781241936321fa54db" class="collapsed">
+      <a data-toggle="collapse" href="#collapse445b336ca98736b7195e32abeacc0a6e" class="collapsed">
       
         Strangle Monolith
       </a>
     </h4>
   </div>
   
-  <div id="collapse6cf39d9b768548781241936321fa54db" class="panel-collapse collapse ">
+  <div id="collapse445b336ca98736b7195e32abeacc0a6e" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_str_mon_arch1.png" width="400" /></p>
+       <img src="../img/lab2_str_mon_arch1.png" width="400" />
 
     </div>
   </div>
@@ -373,17 +373,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse73984d32fd71ab16a26b26c7c5b2bee0" class="collapsed">
+      <a data-toggle="collapse" href="#collapsedf2d954fec33ec16858b188f2806f38c" class="collapsed">
       
         Add a Microservice
       </a>
     </h4>
   </div>
   
-  <div id="collapse73984d32fd71ab16a26b26c7c5b2bee0" class="panel-collapse collapse ">
+  <div id="collapsedf2d954fec33ec16858b188f2806f38c" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_str_mon_arch2.png" width="400" /></p>
+       <img src="../img/lab2_str_mon_arch2.png" width="400" />
 
     </div>
   </div>
@@ -404,17 +404,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse97b384fb54726c14ad91471e3caa24d4" class="collapsed">
+      <a data-toggle="collapse" href="#collapse4f1bee95625fda204e6509e9844f28dd" class="collapsed">
       
         And Another
       </a>
     </h4>
   </div>
   
-  <div id="collapse97b384fb54726c14ad91471e3caa24d4" class="panel-collapse collapse ">
+  <div id="collapse4f1bee95625fda204e6509e9844f28dd" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_str_mon_arch3.png" width="400" /></p>
+       <img src="../img/lab2_str_mon_arch3.png" width="400" />
 
     </div>
   </div>
@@ -435,17 +435,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse8c8adeab91e9d3a048a7db06ed1f0477" class="collapsed">
+      <a data-toggle="collapse" href="#collapse9d249eec941f3149f305bbc7e325a53e" class="collapsed">
       
         Squeeze Monolith
       </a>
     </h4>
   </div>
   
-  <div id="collapse8c8adeab91e9d3a048a7db06ed1f0477" class="panel-collapse collapse ">
+  <div id="collapse9d249eec941f3149f305bbc7e325a53e" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_str_mon_arch4.png" width="400" /></p>
+       <img src="../img/lab2_str_mon_arch4.png" width="400" />
 
     </div>
   </div>
@@ -466,17 +466,17 @@ <h4 class="panel-title">
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsefa84431f0802f2e4468bde4909c49720" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef618b717be5b2304861ccc4b96951d75" class="collapsed">
       
         And Remove Dead
       </a>
     </h4>
   </div>
   
-  <div id="collapsefa84431f0802f2e4468bde4909c49720" class="panel-collapse collapse ">
+  <div id="collapsef618b717be5b2304861ccc4b96951d75" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_str_mon_arch5.png" width="400" /></p>
+       <img src="../img/lab2_str_mon_arch5.png" width="400" />
 
     </div>
   </div>
@@ -496,28 +496,28 @@ <h1 id="step-1">Step 1</h1>
 <li>First, build and deploy the catalog microservice (Based on Spring Boot)</li>
 </ul>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd ~/coolstore
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ git clone -b app-partner https://github.com/epe105/catalog
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd catalog
-</code></pre></div><div class="alert alert-warning">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd ~/coolstore
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ git clone -b app-partner https://github.com/epe105/catalog
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd catalog
+</span></span></code></pre></div><div class="alert alert-warning">
 <p><span class="pficon pficon-warning-triangle-o"></span></p>
 <p>Please update <code>&lt;USERNAME&gt;</code> below with your assigned username</p>
 </div>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project coolstore-&lt;USERNAME&gt;
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ mvn clean fabric8:deploy -Popenshift -DskipTests
-</code></pre></div><h1 id="step-2">Step 2</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project coolstore-&lt;USERNAME&gt;
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ mvn clean fabric8:deploy -Popenshift -DskipTests
+</span></span></code></pre></div><h1 id="step-2">Step 2</h1>
 <blockquote>
 <p>Once the new catalog service is deployed, test it with curl:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get route/catalog
-NAME      HOST/PORT                                              PATH      SERVICES   PORT      TERMINATION
-catalog   catalog-coolstore-&lt;USERNAME&gt;.apps.ocp.naps-redhat.com            catalog    <span style="color:#ae81ff">8080</span>
-</code></pre></div><p>Curl using the HOST/PORT from the previous step</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ curl http://catalog-coolstore--USERNAME&gt;.apps.ocp.naps-redhat.com/api/catalog
-
-<span style="color:#f92672">[{</span><span style="color:#e6db74">&#34;itemId&#34;</span>:<span style="color:#e6db74">&#34;329299&#34;</span>,<span style="color:#e6db74">&#34;name&#34;</span>:<span style="color:#e6db74">&#34;Red Fedora&#34;</span>,<span style="color:#e6db74">&#34;desc&#34;</span>:<span style="color:#e6db74">&#34;Official Red Hat Fedora&#34;</span>,<span style="color:#e6db74">&#34;price&#34;</span>:34.99<span style="color:#f92672">}</span>,<span style="color:#f92672">{</span><span style="color:#e6db74">&#34;itemId&#34;</span>:<span style="color:#e6db74">&#34;329199&#34;</span>,<span style="color:#e6db74">&#34;name&#34;</span>:<span style="color:#e6db74">&#34;Forge Laptop Sticker&#34;</span>,<span style="color:#e6db74">&#34;desc&#34;</span>:<span style="color:#e6db74">&#34;JBoss Community Forge Project Sticker&#34;</span>,<span style="color:#e6db74">&#34;price&#34;</span>:8.5<span style="color:#f92672">}</span>
-...
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get route/catalog
+</span></span><span style="display:flex;"><span>NAME      HOST/PORT                                              PATH      SERVICES   PORT      TERMINATION
+</span></span><span style="display:flex;"><span>catalog   catalog-coolstore-&lt;USERNAME&gt;.apps.ocp.naps-redhat.com            catalog    <span style="color:#ae81ff">8080</span>
+</span></span></code></pre></div><p>Curl using the HOST/PORT from the previous step</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ curl http://catalog-coolstore--USERNAME&gt;.apps.ocp.naps-redhat.com/api/catalog
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#f92672">[{</span><span style="color:#e6db74">&#34;itemId&#34;</span>:<span style="color:#e6db74">&#34;329299&#34;</span>,<span style="color:#e6db74">&#34;name&#34;</span>:<span style="color:#e6db74">&#34;Red Fedora&#34;</span>,<span style="color:#e6db74">&#34;desc&#34;</span>:<span style="color:#e6db74">&#34;Official Red Hat Fedora&#34;</span>,<span style="color:#e6db74">&#34;price&#34;</span>:34.99<span style="color:#f92672">}</span>,<span style="color:#f92672">{</span><span style="color:#e6db74">&#34;itemId&#34;</span>:<span style="color:#e6db74">&#34;329199&#34;</span>,<span style="color:#e6db74">&#34;name&#34;</span>:<span style="color:#e6db74">&#34;Forge Laptop Sticker&#34;</span>,<span style="color:#e6db74">&#34;desc&#34;</span>:<span style="color:#e6db74">&#34;JBoss Community Forge Project Sticker&#34;</span>,<span style="color:#e6db74">&#34;price&#34;</span>:8.5<span style="color:#f92672">}</span>
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div><blockquote>
 <p>You can also test it by clicking on the route to the catalog service and adding /api/catalog to the URL:</p>
 </blockquote>
 <div class="panel-group">
@@ -527,17 +527,17 @@ <h1 id="step-1">Step 1</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapsef889dd0be6a15f8c0b24e83308d6b450" class="collapsed">
+      <a data-toggle="collapse" href="#collapsec224f9abf1b55426db4addf47eb102b3" class="collapsed">
       
         Catalog API Service
       </a>
     </h4>
   </div>
   
-  <div id="collapsef889dd0be6a15f8c0b24e83308d6b450" class="panel-collapse collapse ">
+  <div id="collapsec224f9abf1b55426db4addf47eb102b3" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_curl_catalog_srvc_browser.png" width="1000" /></p>
+       <img src="../img/lab2_curl_catalog_srvc_browser.png" width="1000" />
 
     </div>
   </div>
@@ -550,16 +550,16 @@ <h1 id="step-3">Step 3</h1>
 <blockquote>
 <p>Now we will do the same for the Inventory service, based on WildFly Swarm:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd ~/coolstore
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ git clone -b app-partner https://github.com/epe105/inventory
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd inventory
-</code></pre></div><div class="alert alert-warning">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd ~/coolstore
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ git clone -b app-partner https://github.com/epe105/inventory
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd inventory
+</span></span></code></pre></div><div class="alert alert-warning">
 <p><span class="pficon pficon-warning-triangle-o"></span></p>
 <p>Please update <code>&lt;USERNAME&gt;</code> below with your assigned username</p>
 </div>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project coolstore-&lt;USERNAME&gt;
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ mvn clean fabric8:deploy -Popenshift  -DskipTests
-</code></pre></div><ul>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project coolstore-&lt;USERNAME&gt;
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ mvn clean fabric8:deploy -Popenshift  -DskipTests
+</span></span></code></pre></div><ul>
 <li>The catalog microservice is responsible for retrieving and returning a list of products and their descriptions (price, images, etc).</li>
 <li>The inventory service is responsible for retrieving and returning inventory for a given product.</li>
 <li>The catalog service does not specifically know about or care about inventory. In the next lab we will combine the two!</li>
@@ -575,42 +575,42 @@ <h1 id="step-4">Step 4</h1>
 <blockquote>
 <p>Get the POSTGRESQL_PASSWORD</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc env dc/inventory-database --list <span style="color:#75715e"># get the POSTGRESQL_PASSWORD</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc env dc/inventory-database --list <span style="color:#75715e"># get the POSTGRESQL_PASSWORD</span>
+</span></span></code></pre></div><blockquote>
 <p>Get the postgresql pod</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get pods
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get pods
+</span></span></code></pre></div><blockquote>
 <p>oc rsh into the postgresql pod from the previous step</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc rsh inventory-database-1-kkxs2
-sh-4.2$ psql -h $HOSTNAME -d $POSTGRESQL_DATABASE -U $POSTGRESQL_USER
-Password <span style="color:#66d9ef">for</span> user userV31:XXXXXXXX
-psql <span style="color:#f92672">(</span>9.5.4<span style="color:#f92672">)</span>
-Type <span style="color:#e6db74">&#34;help&#34;</span> <span style="color:#66d9ef">for</span> help.
-
-monolith<span style="color:#f92672">=</span>&gt; <span style="color:#66d9ef">select</span> * from inventory;
- itemid |               link                | location | quantity
---------+-----------------------------------+----------+----------
- <span style="color:#ae81ff">329299</span> | http://maps.google.com/?q<span style="color:#f92672">=</span>Raleigh | Raleigh  |      <span style="color:#ae81ff">736</span>
-...
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc rsh inventory-database-1-kkxs2
+</span></span><span style="display:flex;"><span>sh-4.2$ psql -h $HOSTNAME -d $POSTGRESQL_DATABASE -U $POSTGRESQL_USER
+</span></span><span style="display:flex;"><span>Password <span style="color:#66d9ef">for</span> user userV31:XXXXXXXX
+</span></span><span style="display:flex;"><span>psql <span style="color:#f92672">(</span>9.5.4<span style="color:#f92672">)</span>
+</span></span><span style="display:flex;"><span>Type <span style="color:#e6db74">&#34;help&#34;</span> <span style="color:#66d9ef">for</span> help.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>monolith<span style="color:#f92672">=</span>&gt; <span style="color:#66d9ef">select</span> * from inventory;
+</span></span><span style="display:flex;"><span> itemid |               link                | location | quantity
+</span></span><span style="display:flex;"><span>--------+-----------------------------------+----------+----------
+</span></span><span style="display:flex;"><span> <span style="color:#ae81ff">329299</span> | http://maps.google.com/?q<span style="color:#f92672">=</span>Raleigh | Raleigh  |      <span style="color:#ae81ff">736</span>
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div><blockquote>
 <p>Exit out of psql and then the postgresql pod</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">monolith<span style="color:#f92672">=</span>&gt; <span style="color:#ae81ff">\q</span>
-sh-4.2$ exit
-exit
-</code></pre></div><h1 id="step-5">Step 5</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>monolith<span style="color:#f92672">=</span>&gt; <span style="color:#ae81ff">\q</span>
+</span></span><span style="display:flex;"><span>sh-4.2$ exit
+</span></span><span style="display:flex;"><span>exit
+</span></span></code></pre></div><h1 id="step-5">Step 5</h1>
 <blockquote>
 <p>Once the new service is deployed, test it with curl<br>
 You should get a JSON object representing the inventory availability of product 329299</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get route/inventory
-NAME        HOST/PORT                                                  PATH      SERVICES    PORT      TERMINATION
-inventory   inventory-coolstore-&lt;USERNAME&gt;.apps.ocp.naps-redhat.com              inventory   <span style="color:#ae81ff">8080</span>
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ curl http://inventory-coolstore-&lt;USERNAME&gt;.apps.ocp.naps-redhat.com/api/inventory/329299
-<span style="color:#f92672">{</span><span style="color:#e6db74">&#34;itemId&#34;</span>:<span style="color:#e6db74">&#34;329299&#34;</span>,<span style="color:#e6db74">&#34;location&#34;</span>:<span style="color:#e6db74">&#34;Raleigh&#34;</span>,<span style="color:#e6db74">&#34;quantity&#34;</span>:736,<span style="color:#e6db74">&#34;link&#34;</span>:<span style="color:#e6db74">&#34;http://maps.google.com/?q=Raleigh&#34;</span><span style="color:#f92672">}</span>
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get route/inventory
+</span></span><span style="display:flex;"><span>NAME        HOST/PORT                                                  PATH      SERVICES    PORT      TERMINATION
+</span></span><span style="display:flex;"><span>inventory   inventory-coolstore-&lt;USERNAME&gt;.apps.ocp.naps-redhat.com              inventory   <span style="color:#ae81ff">8080</span>
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ curl http://inventory-coolstore-&lt;USERNAME&gt;.apps.ocp.naps-redhat.com/api/inventory/329299
+</span></span><span style="display:flex;"><span><span style="color:#f92672">{</span><span style="color:#e6db74">&#34;itemId&#34;</span>:<span style="color:#e6db74">&#34;329299&#34;</span>,<span style="color:#e6db74">&#34;location&#34;</span>:<span style="color:#e6db74">&#34;Raleigh&#34;</span>,<span style="color:#e6db74">&#34;quantity&#34;</span>:736,<span style="color:#e6db74">&#34;link&#34;</span>:<span style="color:#e6db74">&#34;http://maps.google.com/?q=Raleigh&#34;</span><span style="color:#f92672">}</span>
+</span></span></code></pre></div><blockquote>
 <p>You can also test it by clicking on the route to the inventory service and adding /api/inventory/329299 to the URL</p>
 </blockquote>
 <div class="panel-group">
@@ -620,17 +620,17 @@ <h1 id="step-4">Step 4</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse1d1e8d8f0c44d77188f19f877e4fc9ad" class="collapsed">
+      <a data-toggle="collapse" href="#collapsebad8f99d6bac18e7bb3362ec6e3c2120" class="collapsed">
       
         Inventory API Service
       </a>
     </h4>
   </div>
   
-  <div id="collapse1d1e8d8f0c44d77188f19f877e4fc9ad" class="panel-collapse collapse ">
+  <div id="collapsebad8f99d6bac18e7bb3362ec6e3c2120" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab2_curl_inventory_srvc_browser.png" width="1000" /></p>
+       <img src="../img/lab2_curl_inventory_srvc_browser.png" width="1000" />
 
     </div>
   </div>
@@ -643,7 +643,7 @@ <h1 id="strangling-your-monolith-lab-architecture">Strangling Your Monolith Lab
 <blockquote>
 <p>Once the new Microservices are deployed, this is the Architecture of this Lab</p>
 </blockquote>
-<p><img src="../img/lab3_arch1.png" width="700" /></p>
+<img src="../img/lab3_arch1.png" width="700" />
 
 
     
@@ -683,7 +683,7 @@ <h1 id="strangling-your-monolith-lab-architecture">Strangling Your Monolith Lab
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/lab3/index.html b/workshops/strangling_the_monolith/lab3/index.html
index 9cf4b51eb..eb0d00250 100644
--- a/workshops/strangling_the_monolith/lab3/index.html
+++ b/workshops/strangling_the_monolith/lab3/index.html
@@ -342,7 +342,7 @@ <h1 id="microservice-integration-patterns">Microservice Integration Patterns</h1
 </ul>
 </li>
 </ul>
-<p><img src="../img/lab3_phone2.png" width="500" /></p>
+<img src="../img/lab3_phone2.png" width="500" />
 <blockquote>
 <p>Option 2: Chaining</p>
 </blockquote>
@@ -367,7 +367,7 @@ <h1 id="microservice-integration-patterns">Microservice Integration Patterns</h1
 <li>Complex “stack traces” when things go wrong (tracing libraries a must)</li>
 <li>Exposes internal structure of app logic (the first microservice in the chain would be difficult to change)</li>
 </ul>
-<p><img src="../img/lab3_phone3.png" width="700" /></p>
+<img src="../img/lab3_phone3.png" width="700" />
 </li>
 </ul>
 <blockquote>
@@ -394,7 +394,7 @@ <h1 id="microservice-integration-patterns">Microservice Integration Patterns</h1
 <ul>
 <li>Possible bottleneck depending on difficulty of adding new services</li>
 </ul>
-<p><img src="../img/lab3_phone4.png" width="500" /></p>
+<img src="../img/lab3_phone4.png" width="500" />
 </li>
 </ul>
 <h1 id="step-1">Step 1</h1>
@@ -406,16 +406,16 @@ <h1 id="step-1">Step 1</h1>
 <blockquote>
 <p>First, deploy the API gateway:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd ~/coolstore
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ git clone -b app-partner https://github.com/epe105/gateway
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd gateway
-</code></pre></div><div class="alert alert-warning">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd ~/coolstore
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ git clone -b app-partner https://github.com/epe105/gateway
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd gateway
+</span></span></code></pre></div><div class="alert alert-warning">
 <p><span class="pficon pficon-warning-triangle-o"></span></p>
 <p>Please update <code>&lt;USERNAME&gt;</code> below with your assigned username</p>
 </div>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project coolstore-&lt;USERNAME&gt;
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ mvn clean fabric8:deploy -Popenshift -DskipTests
-</code></pre></div><h1 id="step-2">Step 2</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project coolstore-&lt;USERNAME&gt;
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ mvn clean fabric8:deploy -Popenshift -DskipTests
+</span></span></code></pre></div><h1 id="step-2">Step 2</h1>
 <ul>
 <li>The Coolstore Gateway microservice is a Spring Boot application that implements its logic using an Apache Camel route.</li>
 </ul>
@@ -423,59 +423,59 @@ <h1 id="step-1">Step 1</h1>
 <p>Take a look at the code for the Gateway in your browser :
 <a href="https://github.com/modernize-legacy-apps/gateway/blob/master/src/main/java/com/redhat/coolstore/api_gateway/ProductGateway.java">https://github.com/epe105/gateway/blob/master/src/main/java/com/redhat/coolstore/api_gateway/ProductGateway.java</a></p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-php" data-lang="php"><span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">59</span>restConfiguration()
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">60</span>		.contextPath(&#34;/services&#34;).apiContextPath(&#34;/services-docs&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">61</span>		.apiProperty(&#34;host&#34;, &#34;&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">62</span>		.apiProperty(&#34;api.title&#34;, &#34;CoolStore Gateway API&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">63</span>		.apiProperty(&#34;api.version&#34;, &#34;1.0&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">64</span>		.component(&#34;servlet&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">65</span>		.bindingMode(RestBindingMode.json);</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;display:grid;"><code class="language-php" data-lang="php"><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">59</span><span><span style="color:#a6e22e">restConfiguration</span>()
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">60</span><span>		<span style="color:#f92672">.</span><span style="color:#a6e22e">contextPath</span>(<span style="color:#e6db74">&#34;/services&#34;</span>)<span style="color:#f92672">.</span><span style="color:#a6e22e">apiContextPath</span>(<span style="color:#e6db74">&#34;/services-docs&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">61</span><span>		<span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;host&#34;</span>, <span style="color:#e6db74">&#34;&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">62</span><span>		<span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;api.title&#34;</span>, <span style="color:#e6db74">&#34;CoolStore Gateway API&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">63</span><span>		<span style="color:#f92672">.</span><span style="color:#a6e22e">apiProperty</span>(<span style="color:#e6db74">&#34;api.version&#34;</span>, <span style="color:#e6db74">&#34;1.0&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">64</span><span>		<span style="color:#f92672">.</span><span style="color:#a6e22e">component</span>(<span style="color:#e6db74">&#34;servlet&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">65</span><span>		<span style="color:#f92672">.</span><span style="color:#a6e22e">bindingMode</span>(<span style="color:#a6e22e">RestBindingMode</span><span style="color:#f92672">.</span><span style="color:#a6e22e">json</span>);</span></span></code></pre></div>
 <ul>
 <li>The beginning of this route uses the Camel Java DSL (Domain-Specific Language) to configure the REST system and define the base paths of the API itself (/services) and paths to Swagger documentation (/services-docs).</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-php" data-lang="php"><span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">67</span>rest(&#34;/products&#34;).description(&#34;Access the CoolStore products and their availability&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">68</span>            .produces(MediaType.APPLICATION_JSON_VALUE)</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;display:grid;"><code class="language-php" data-lang="php"><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">67</span><span><span style="color:#a6e22e">rest</span>(<span style="color:#e6db74">&#34;/products&#34;</span>)<span style="color:#f92672">.</span><span style="color:#a6e22e">description</span>(<span style="color:#e6db74">&#34;Access the CoolStore products and their availability&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">68</span><span>            <span style="color:#f92672">.</span><span style="color:#a6e22e">produces</span>(<span style="color:#a6e22e">MediaType</span><span style="color:#f92672">.</span><span style="color:#a6e22e">APPLICATION_JSON_VALUE</span>)</span></span></code></pre></div>
 <ul>
 <li>This begins the REST DSL portion, defining the primary access point for the catalog of products (/products) and the format of the data it produces (JSON)</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-php" data-lang="php"><span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">70</span>.get(&#34;/&#34;).description(&#34;Retrieves the product catalog, including inventory availability&#34;).outType(Product.class)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">71</span>    .route().id(&#34;productRoute&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">72</span>          .setBody(simple(&#34;null&#34;))
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">73</span>          .removeHeaders(&#34;CamelHttp*&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">74</span>          .recipientList(simple(&#34;http4://{{env:CATALOG_ENDPOINT:catalog:8080}}/api/catalog&#34;)).end()
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">75</span>          .unmarshal(productFormatter)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">76</span>          .split(body()).parallelProcessing()
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">77</span>          .enrich(&#34;direct:inventory&#34;, new InventoryEnricher())
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">78</span>      .end()	            
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">79</span>.endRest();</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;display:grid;"><code class="language-php" data-lang="php"><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">70</span><span><span style="color:#f92672">.</span><span style="color:#a6e22e">get</span>(<span style="color:#e6db74">&#34;/&#34;</span>)<span style="color:#f92672">.</span><span style="color:#a6e22e">description</span>(<span style="color:#e6db74">&#34;Retrieves the product catalog, including inventory availability&#34;</span>)<span style="color:#f92672">.</span><span style="color:#a6e22e">outType</span>(<span style="color:#a6e22e">Product</span><span style="color:#f92672">.</span><span style="color:#a6e22e">class</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">71</span><span>    <span style="color:#f92672">.</span><span style="color:#a6e22e">route</span>()<span style="color:#f92672">.</span><span style="color:#a6e22e">id</span>(<span style="color:#e6db74">&#34;productRoute&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">72</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">setBody</span>(<span style="color:#a6e22e">simple</span>(<span style="color:#e6db74">&#34;null&#34;</span>))
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">73</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">removeHeaders</span>(<span style="color:#e6db74">&#34;CamelHttp*&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">74</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">recipientList</span>(<span style="color:#a6e22e">simple</span>(<span style="color:#e6db74">&#34;http4://{{env:CATALOG_ENDPOINT:catalog:8080}}/api/catalog&#34;</span>))<span style="color:#f92672">.</span><span style="color:#a6e22e">end</span>()
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">75</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">unmarshal</span>(<span style="color:#a6e22e">productFormatter</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">76</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">split</span>(<span style="color:#a6e22e">body</span>())<span style="color:#f92672">.</span><span style="color:#a6e22e">parallelProcessing</span>()
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">77</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">enrich</span>(<span style="color:#e6db74">&#34;direct:inventory&#34;</span>, <span style="color:#66d9ef">new</span> <span style="color:#a6e22e">InventoryEnricher</span>())
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">78</span><span>      <span style="color:#f92672">.</span><span style="color:#a6e22e">end</span>()	            
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">79</span><span><span style="color:#f92672">.</span><span style="color:#a6e22e">endRest</span>();</span></span></code></pre></div>
 <ul>
 <li>This configures the endpoint for retrieving a list of products by first contacting the Catalog microservice, .split()ing the resulting list, and enriching (via enrich()) each of the products with its inventory by passing each product to the direct:inventory route.</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-php" data-lang="php"><span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 94</span>from(&#34;direct:inventory&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 95</span>          .id(&#34;inventoryRoute&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 96</span>          .setHeader(&#34;itemId&#34;, simple(&#34;${body.itemId}&#34;))            
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 97</span>    .setBody(simple(&#34;null&#34;))
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 98</span>    .removeHeaders(&#34;CamelHttp*&#34;)
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 99</span>          .recipientList(simple(&#34;http4://{{env:INVENTORY_ENDPOINT:inventory:8080}}/api/inventory/${header.itemId}&#34;)).end()
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">100</span>          .setHeader(&#34;CamelJacksonUnmarshalType&#34;, simple(Inventory.class.getName()))
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">101</span>          .unmarshal().json(JsonLibrary.Jackson, Inventory.class);</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;display:grid;"><code class="language-php" data-lang="php"><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 94</span><span><span style="color:#a6e22e">from</span>(<span style="color:#e6db74">&#34;direct:inventory&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 95</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">id</span>(<span style="color:#e6db74">&#34;inventoryRoute&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 96</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">setHeader</span>(<span style="color:#e6db74">&#34;itemId&#34;</span>, <span style="color:#a6e22e">simple</span>(<span style="color:#e6db74">&#34;</span><span style="color:#e6db74">${</span>body.itemId<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span>))            
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 97</span><span>    <span style="color:#f92672">.</span><span style="color:#a6e22e">setBody</span>(<span style="color:#a6e22e">simple</span>(<span style="color:#e6db74">&#34;null&#34;</span>))
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 98</span><span>    <span style="color:#f92672">.</span><span style="color:#a6e22e">removeHeaders</span>(<span style="color:#e6db74">&#34;CamelHttp*&#34;</span>)
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"> 99</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">recipientList</span>(<span style="color:#a6e22e">simple</span>(<span style="color:#e6db74">&#34;http4://{{env:INVENTORY_ENDPOINT:inventory:8080}}/api/inventory/</span><span style="color:#e6db74">${</span>header.itemId<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span>))<span style="color:#f92672">.</span><span style="color:#a6e22e">end</span>()
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">100</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">setHeader</span>(<span style="color:#e6db74">&#34;CamelJacksonUnmarshalType&#34;</span>, <span style="color:#a6e22e">simple</span>(<span style="color:#a6e22e">Inventory</span><span style="color:#f92672">.</span><span style="color:#a6e22e">class</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getName</span>()))
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">101</span><span>          <span style="color:#f92672">.</span><span style="color:#a6e22e">unmarshal</span>()<span style="color:#f92672">.</span><span style="color:#a6e22e">json</span>(<span style="color:#a6e22e">JsonLibrary</span><span style="color:#f92672">.</span><span style="color:#a6e22e">Jackson</span>, <span style="color:#a6e22e">Inventory</span><span style="color:#f92672">.</span><span style="color:#a6e22e">class</span>);</span></span></code></pre></div>
 <ul>
 <li>This is the direct:inventory route, which takes in a Product object (in the body()) and calls out to the Inventory microservice to retrieve its inventory. The resulting inventory is placed back into the Camel exchange for enrichment by the enricher:</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-php" data-lang="php"><span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">108</span>@Override
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">109</span>public Exchange aggregate(Exchange original, Exchange resource) {
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">110</span>
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">111</span>	// Add the discovered availability to the product and set it back
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">112</span>	Product p = original.getIn().getBody(Product.class);
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">113</span>	Inventory i = resource.getIn().getBody(Inventory.class);
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">114</span>	p.setQuantity(i.getQuantity());
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">115</span>	p.setLocation(i.getLocation());
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">116</span>	p.setLink(i.getLink());
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">117</span>	original.getOut().setBody(p);
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">118</span>
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">119</span>	return original;
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">120</span>
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">121</span>}</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;display:grid;"><code class="language-php" data-lang="php"><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">108</span><span><span style="color:#f92672">@</span><span style="color:#a6e22e">Override</span>
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">109</span><span><span style="color:#66d9ef">public</span> <span style="color:#a6e22e">Exchange</span> <span style="color:#a6e22e">aggregate</span>(<span style="color:#a6e22e">Exchange</span> <span style="color:#a6e22e">original</span>, <span style="color:#a6e22e">Exchange</span> <span style="color:#a6e22e">resource</span>) {
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">110</span><span>
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">111</span><span>	<span style="color:#75715e">// Add the discovered availability to the product and set it back
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">112</span><span><span style="color:#75715e"></span>	<span style="color:#a6e22e">Product</span> <span style="color:#a6e22e">p</span> <span style="color:#f92672">=</span> <span style="color:#a6e22e">original</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getIn</span>()<span style="color:#f92672">.</span><span style="color:#a6e22e">getBody</span>(<span style="color:#a6e22e">Product</span><span style="color:#f92672">.</span><span style="color:#a6e22e">class</span>);
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">113</span><span>	<span style="color:#a6e22e">Inventory</span> <span style="color:#a6e22e">i</span> <span style="color:#f92672">=</span> <span style="color:#a6e22e">resource</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getIn</span>()<span style="color:#f92672">.</span><span style="color:#a6e22e">getBody</span>(<span style="color:#a6e22e">Inventory</span><span style="color:#f92672">.</span><span style="color:#a6e22e">class</span>);
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">114</span><span>	<span style="color:#a6e22e">p</span><span style="color:#f92672">.</span><span style="color:#a6e22e">setQuantity</span>(<span style="color:#a6e22e">i</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getQuantity</span>());
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">115</span><span>	<span style="color:#a6e22e">p</span><span style="color:#f92672">.</span><span style="color:#a6e22e">setLocation</span>(<span style="color:#a6e22e">i</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getLocation</span>());
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">116</span><span>	<span style="color:#a6e22e">p</span><span style="color:#f92672">.</span><span style="color:#a6e22e">setLink</span>(<span style="color:#a6e22e">i</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getLink</span>());
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">117</span><span>	<span style="color:#a6e22e">original</span><span style="color:#f92672">.</span><span style="color:#a6e22e">getOut</span>()<span style="color:#f92672">.</span><span style="color:#a6e22e">setBody</span>(<span style="color:#a6e22e">p</span>);
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">118</span><span>
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">119</span><span>	<span style="color:#66d9ef">return</span> <span style="color:#a6e22e">original</span>;
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">120</span><span>
+</span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">121</span><span>}</span></span></code></pre></div>
 <ul>
 <li>This is the enricher logic which takes the Product and matching Inventory objects, enriches the Product object with information from the Inventory object, and returns it.</li>
 <li>The resulting list sent back to the client is the list of products, each of which is enriched with inventory information</li>
@@ -484,7 +484,7 @@ <h1 id="step-1">Step 1</h1>
 <h1 id="step-3">Step 3</h1>
 <ul>
 <li>Now that the gateway microservice is deployed, let’s hook it into the application using OpenShift routing.</li>
-<li>A route is a way to expose a service by giving it an externally-reachable hostname like <a href="http://www.example.com">www.example.com</a>, or in our example www-coolstore.<domain></li>
+<li>A route is a way to expose a service by giving it an externally-reachable hostname like <a href="https://www.example.com">www.example.com</a>, or in our example www-coolstore.<domain></li>
 <li>Routes can be created using oc expose command line, or through the GUI.</li>
 <li>Path based routes specify a path component that can be compared against a URL such that multiple routes can be served using the same underlying service/pod, each with a different path.</li>
 <li>In this case, we already have a route that sends all traffic destined for our monolith to the monolith deployment.</li>
@@ -494,7 +494,7 @@ <h1 id="step-3">Step 3</h1>
 <p>Navigate to Applications → Routes to list the current routes.<br>
 Notice the www route is the primary route for our monolith:</p>
 </blockquote>
-<p><img src="../img/lab3_route1.png" width="1000" /></p>
+  <img src="../img/lab3_route1.png" width="1000" />
 <h1 id="step-4">Step 4</h1>
 <blockquote>
 <ul>
@@ -520,17 +520,17 @@ <h1 id="step-4">Step 4</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse435ff668501f34d823f8354e17f1a95e" class="collapsed">
+      <a data-toggle="collapse" href="#collapse1bb3ed4cdea0d3fb238ced8bfd33f2a6" class="collapsed">
       
         Create Route
       </a>
     </h4>
   </div>
   
-  <div id="collapse435ff668501f34d823f8354e17f1a95e" class="panel-collapse collapse ">
+  <div id="collapse1bb3ed4cdea0d3fb238ced8bfd33f2a6" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab3_create_route.png" width="1000" /></p>
+       <img src="../img/lab3_create_route.png" width="1000" />
 
     </div>
   </div>
@@ -550,17 +550,17 @@ <h1 id="step-5">Step 5</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse775e295deb3bf9aa9cfabba0d64329cb" class="collapsed">
+      <a data-toggle="collapse" href="#collapseb9568f44ca403a0bfffe9a9d97d426be" class="collapsed">
       
         Test New Route to Cool Store
       </a>
     </h4>
   </div>
   
-  <div id="collapse775e295deb3bf9aa9cfabba0d64329cb" class="panel-collapse collapse ">
+  <div id="collapseb9568f44ca403a0bfffe9a9d97d426be" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab3_coolstore_before.png" width="1000" /></p>
+       <img src="../img/lab3_coolstore_before.png" width="1000" />
 
     </div>
   </div>
@@ -579,32 +579,33 @@ <h1 id="step-6">Step 6</h1>
 <p>Open the gateway source code file and un-comment the lines that implement a filter based on product ID (around line 80). The highlighted code shows you the predicate used for the filter</p>
 </blockquote>
 <p>Use vi to make changes in the code.  If you need help in using vi, please click <a href="https://www.cs.colostate.edu/helpdocs/vi.html">here</a></p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ vi ~/coolstore/gateway/src/main/java/com/redhat/coolstore/api_gateway/ProductGateway.java
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-php" data-lang="php"><span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">77</span>//
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">78</span>// Uncomment the below lines to filter out products
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">79</span>//
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">80</span>//		.process(exchange -&gt; {
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">81</span>//                    List&lt;<span style="color:#f92672">Product</span>&gt; originalProductList = (List&lt;<span style="color:#f92672">Product</span>&gt;)exchange.getIn().getBody(List.class);
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">82</span>//                    List&lt;<span style="color:#f92672">Product</span>&gt; newProductList = originalProductList.stream().filter(product -&gt;
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">83</span>//							!(&#34;329299&#34;.equals(product.itemId)))
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">84</span>//						.collect(Collectors.toList());
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">85</span>//                    exchange.getIn().setBody(newProductList);
-<span style="margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">86</span>//                })</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ vi ~/coolstore/gateway/src/main/java/com/redhat/coolstore/api_gateway/ProductGateway.java
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;display:grid;"><code class="language-php" data-lang="php"><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">77</span><span><span style="color:#75715e">//
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">78</span><span><span style="color:#75715e">// Uncomment the below lines to filter out products
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">79</span><span><span style="color:#75715e">//
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">80</span><span><span style="color:#75715e">//		.process(exchange -&gt; {
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">81</span><span><span style="color:#75715e">//                    List&lt;Product&gt; originalProductList = (List&lt;Product&gt;)exchange.getIn().getBody(List.class);
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">82</span><span><span style="color:#75715e">//                    List&lt;Product&gt; newProductList = originalProductList.stream().filter(product -&gt;
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">83</span><span><span style="color:#75715e">//							!(&#34;329299&#34;.equals(product.itemId)))
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">84</span><span><span style="color:#75715e">//						.collect(Collectors.toList());
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">85</span><span><span style="color:#75715e">//                    exchange.getIn().setBody(newProductList);
+</span></span></span><span style="display:flex;"><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f">86</span><span><span style="color:#75715e">//                })
+</span></span></span></code></pre></div>
 <blockquote>
 <p>Save your changes and quit</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ shift + Z
-$ shift + Z
-</code></pre></div><h1 id="step-7">Step 7</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ shift + Z
+</span></span><span style="display:flex;"><span>$ shift + Z
+</span></span></code></pre></div><h1 id="step-7">Step 7</h1>
 <ul>
 <li>Re-deploy the modified code using the same procedure as before:</li>
 </ul>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ cd ~/coolstore/gateway
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ mvn clean fabric8:deploy -Popenshift -DskipTests
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc logs -f dc/gateway
-...
---&gt; Success       <span style="color:#75715e"># --&gt; wait for it!</span>
-</code></pre></div><h1 id="step-8">Step 8</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ cd ~/coolstore/gateway
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ mvn clean fabric8:deploy -Popenshift -DskipTests
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc logs -f dc/gateway
+</span></span><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>--&gt; Success       <span style="color:#75715e"># --&gt; wait for it!</span>
+</span></span></code></pre></div><h1 id="step-8">Step 8</h1>
 <ul>
 <li>Once the new version of the code is deployed and up and running, reload the browser and the Red Hat Fedora product should be gone:</li>
 </ul>
@@ -615,17 +616,17 @@ <h1 id="step-6">Step 6</h1>
   <div class="panel-heading">
     <h4 class="panel-title">
       
-      <a data-toggle="collapse" href="#collapse1114c6b3ae3f8d4903d10760736c64e8" class="collapsed">
+      <a data-toggle="collapse" href="#collapsef00dc90725a09601403066ac218f7800" class="collapsed">
       
         See Changes to Cool Store
       </a>
     </h4>
   </div>
   
-  <div id="collapse1114c6b3ae3f8d4903d10760736c64e8" class="panel-collapse collapse ">
+  <div id="collapsef00dc90725a09601403066ac218f7800" class="panel-collapse collapse ">
   
     <div class="panel-body">
-       <p><img src="../img/lab3_coolstore_after.png" width="1000" /></p>
+       <img src="../img/lab3_coolstore_after.png" width="1000" />
 
     </div>
   </div>
@@ -639,7 +640,7 @@ <h1 id="congratulations">Congratulations!!!</h1>
 <li>Our monolith’s UI is now talking to our new Camel-based API Gateway to retrieve products and inventories from our WildFly Swarm and Spring Boot microservices!</li>
 <li>Further strangling can eventually eliminate the monolith entirely.</li>
 </ul>
-<p><img src="../img/lab3_api_gtw_arch1.png" width="600" /></p>
+<img src="../img/lab3_api_gtw_arch1.png" width="600" />
 
 
     
@@ -675,7 +676,7 @@ <h1 id="congratulations">Congratulations!!!</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/login_tour_oc/index.html b/workshops/strangling_the_monolith/login_tour_oc/index.html
index 2eb57487e..b079434bd 100644
--- a/workshops/strangling_the_monolith/login_tour_oc/index.html
+++ b/workshops/strangling_the_monolith/login_tour_oc/index.html
@@ -343,8 +343,8 @@ <h1 id="lets-login">Let&rsquo;s Login</h1>
 <blockquote>
 <p>Navigate to the URI provided by your instructor and login with the user/password provided (if there&rsquo;s an icon on the Desktop, just double click that)</p>
 </blockquote>
-<p><img src="../img/ose-login.png" width="1000" />
-<em>Login Webpage</em></p>
+<img src="../img/ose-login.png" width="1000" />
+*Login Webpage*
 <p>Once logged in you should see your available projects.</p>
 <p>An OpenShift project allows a community of users (or a user) to organize and manage their content in isolation from other communities. Each project has its own resources, policies (who can or cannot perform actions), and constraints (quotas and limits on resources, etc). Projects act as a &ldquo;wrapper&rdquo; around all the application services and endpoints you (or your teams) are using for your work.</p>
 <p>Users must be given access to projects by administrators, or if allowed to create projects, automatically have access to their own projects.</p>
@@ -371,33 +371,33 @@ <h1 id="lets-try-the-command-line">Let&rsquo;s try the command line</h1>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Open a terminal and login using the same URI/user/password with following command:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc login <span style="color:#f92672">[</span>URI<span style="color:#f92672">]</span> --insecure-skip-tls-verify<span style="color:#f92672">=</span>true
-</code></pre></div><p>See example below:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc login https://&lt;workshopname&gt;master.0.redhatgov.io:8443 --insecure-skip-tls-verify<span style="color:#f92672">=</span>true
-</code></pre></div><blockquote>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc login <span style="color:#f92672">[</span>URI<span style="color:#f92672">]</span> --insecure-skip-tls-verify<span style="color:#f92672">=</span>true
+</span></span></code></pre></div><p>See example below:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc login https://&lt;workshopname&gt;master.0.redhatgov.io:8443 --insecure-skip-tls-verify<span style="color:#f92672">=</span>true
+</span></span></code></pre></div><blockquote>
 <p><i class="fa fa-terminal"></i> Check to see what projects you have access to:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc get projects
-</code></pre></div><h1 id="it-looks-empty-via-the-command-line-too">It looks empty via the command line too</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc get projects
+</span></span></code></pre></div><h1 id="it-looks-empty-via-the-command-line-too">It looks empty via the command line too</h1>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Type the following command to use the demo project (replace &lsquo;demo&rsquo; with the project you want to use if there isn&rsquo;t a demo project):</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc new-project demo
-</code></pre></div><div class="alert alert-info">
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc new-project demo
+</span></span></code></pre></div><div class="alert alert-info">
 <p><span class="pficon pficon-info"></span></p>
 <p>You may recieve the message &ldquo;Error from server: project &ldquo;demo&rdquo; already exists&rdquo;. Try another project name i.e. your first initial and lastname.</p>
 </div>
 <blockquote>
 <p><i class="fa fa-terminal"></i> If you create more than one project, then you can switch projects with the following command:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc project <span style="color:#f92672">[</span>NAME<span style="color:#f92672">]</span>
-</code></pre></div><h1 id="help-about-any-command">Help about any command</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc project <span style="color:#f92672">[</span>NAME<span style="color:#f92672">]</span>
+</span></span></code></pre></div><h1 id="help-about-any-command">Help about any command</h1>
 <p>To see the full list of commands supported, run <code>oc help</code>.</p>
 <blockquote>
 <p><i class="fa fa-terminal"></i> Type the following command to read more information about services, deployment configs, build configurations, and active deployments:</p>
 </blockquote>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">$ oc status -h
-</code></pre></div><h1 id="summary">Summary</h1>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ oc status -h
+</span></span></code></pre></div><h1 id="summary">Summary</h1>
 <p>You should now be ready to get hands-on with our workshop labs.</p>
 
 
@@ -438,7 +438,7 @@ <h1 id="lets-try-the-command-line">Let&rsquo;s try the command line</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/login_tour_wetty/index.html b/workshops/strangling_the_monolith/login_tour_wetty/index.html
index fefe645a8..345cbc1f9 100644
--- a/workshops/strangling_the_monolith/login_tour_wetty/index.html
+++ b/workshops/strangling_the_monolith/login_tour_wetty/index.html
@@ -321,9 +321,9 @@ <h1 id="introduction-to-wetty-browser-based-ssh">Introduction to Wetty (Browser-
 <p>This lab provides a quick tour of the browser based SSH client Wetty. To help you get familiar with lab environment along with some key terminology we will use in subsequent lab content.</p>
 <h1 id="accessing-wetty">Accessing Wetty</h1>
 <p>Use this URL to access the Wetty node, just change the workshopname. Ask your instructor for rthe workshopname.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash">https://&lt;workshopname&gt;.wetty.redhatgov.io:8888
-</code></pre></div><p>After logging in, you should see a shell.</p>
-<p><img src="../img/wetty.png" width="1000" /></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>https://&lt;workshopname&gt;.wetty.redhatgov.io:8888
+</span></span></code></pre></div><p>After logging in, you should see a shell.</p>
+<img src="../img/wetty.png" width="1000" />
 <p>The wetty instance will already have the &lsquo;oc&rsquo; command installed on them. The &lsquo;oc&rsquo; command is used to connect to the OpenShift Master.</p>
 
 
@@ -364,7 +364,7 @@ <h1 id="accessing-wetty">Accessing Wetty</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">
diff --git a/workshops/strangling_the_monolith/prerequisites/index.html b/workshops/strangling_the_monolith/prerequisites/index.html
index e69e7f22b..e5e58046b 100644
--- a/workshops/strangling_the_monolith/prerequisites/index.html
+++ b/workshops/strangling_the_monolith/prerequisites/index.html
@@ -358,7 +358,7 @@ <h1 id="create-github-account">Create GitHub account</h1>
 
     <div id="page-footer" class="container">
       <p class="text-center">
-        Copyright &copy; 2023 Red Hat, Inc.
+        Copyright &copy; 2024 Red Hat, Inc.
       </p>
     </div>
     <script type="text/javascript">