Add missing operatorgroup for rhacs operator install.

data/workshop/exercise2.mdx

@@ -208,7 +208,7 @@ Once the updates are applied we can then check that our new operators are availa
 3. Click **Connect** and when prompted enter the password in your environment spreadsheet row, then click **Send credentials**.
 4. A Firefox browser window should already be open, you can manually start if using the top left applications menu if needed.
 5. Click the bookmark toolbar option for **DISCO - OpenShift**.
-6. Log in when prompted with the username **kubeadmin** and the kubeadmin password listed in your environment spreadsheet (you can also find this password in your highside bastion ssh session by running `cat /mnt/high-side-data/auth/kubeadmin-password`).
+6. Log in when prompted with the username **kubeadmin** and the kubeadmin password listed in your environment spreadsheet (you can also find this password in your highside bastion ssh session by running `cat /mnt/high-side-data/auth/kubeadmin-password`). Note that to paste in the web based vnc session you need to use the left hand panel to pass the clipboard content through to the session.
 7. Navigate to **Operators** on the left menu, and then click **OperatorHub**, you should see the newly mirrored operators are now available in your disconnected cluster!
 
 <Zoom>

data/workshop/exercise3.mdx

@@ -64,6 +64,13 @@ spec:
   finalizers:
   - kubernetes
 
+---
+apiVersion: operators.coreos.com/v1
+kind: OperatorGroup
+metadata:
+  name: rhacs-operator
+  namespace: rhacs-operator
+
 ---
 apiVersion: operators.coreos.com/v1alpha1
 kind: Subscription

data/workshop/exercise4.mdx

@@ -17,8 +17,8 @@ Before we get into the technical implementation let's take a moment to get up to
 
 Fundamentally you install RHACS as a set of containers in your OpenShift Container Platform or Kubernetes cluster. RHACS includes the following services:
 
-1. **Central** services you install on a designated "hub" cluster.
-2. **Secured cluster** services you install on each cluster you want to secure by RHACS.
+1. **Central** services you install on a designated "hub" cluster. Central installs the Central, Scanner, and Scanner DB services. The Central service provides access to a user interface through a web UI or the RHACS portal. It also handles API interactions and provides persistent storage. Scanner analyzes images for known vulnerabilities. It uses Scanner DB as a cache for vulnerability definitions.
+2. **Secured cluster** services you install on each cluster you want to secure by RHACS. This installs the Collector, Sensor, and Admission Controller services. Collector collects runtime information on container security and network activity. It then sends data to Sensor, which monitors your Kubernetes cluster for policy detection and enforcement. Admission Controller monitors workloads and prevents users from creating them in RHACS when they violate security policies.
 
 <Zoom>
 |![workshop](/static/images/compliance/acs-architecture-kubernetes.png)         |