diff --git a/data/workshop/exercise3.mdx b/data/workshop/exercise3.mdx
index 9a30c79..fc6790f 100644
--- a/data/workshop/exercise3.mdx
+++ b/data/workshop/exercise3.mdx
@@ -14,6 +14,14 @@ In a broad sense many OpenShift features are added via [Operators](https://www.r
In the previous exercise we mirrored some new operator bundles into our disconnected network. In this exercise we'll install those operators and explore the features they provide us via [Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources) they provide.
+> Note: For some trivia, Red Hat created and open sourced the [Operator Framework](https://github.com/operator-framework), then later contributed the project to the Cloud Native Computing Foundation in 2021, ensuring all organisations can benefit from our experience building and supporting operator driven clusters since ~2016.
+
+
+| |
+|:-----------------------------------------------------------------------------:|
+| *The Operator Framework* |
+
+
## 3.1 - Installing compliance operator
@@ -76,4 +84,12 @@ spec:
EOF
```
+If you check back on your web console, after a short wait the **Advanced Cluser Security for Kubernetes** operator should now show as `✅ Succeeded`.
+
+
+| |
+|:-----------------------------------------------------------------------------:|
+| *List of installed operators* |
+
+
diff --git a/public/static/images/compliance/installed-operators-1.png b/public/static/images/compliance/installed-operators-1.png
new file mode 100644
index 0000000..d99a2d1
Binary files /dev/null and b/public/static/images/compliance/installed-operators-1.png differ
diff --git a/public/static/images/compliance/operator-framework.png b/public/static/images/compliance/operator-framework.png
new file mode 100644
index 0000000..8192874
Binary files /dev/null and b/public/static/images/compliance/operator-framework.png differ