feat: add quay vs openshift registry overview

content/modules/ROOT/pages/m3/module-03.3.adoc

@@ -6,6 +6,16 @@ include::../style.adoc[]
 
 Until now, you've been acting in the role of a platform engineer. Let's switch persona to that of a developer: `dev1`. 
 
+Let's assume that this developer needs to create a development environment to work on a new feature - we can use a Software Template to assist with this this task. A prerequisite to using this template is that the developer has a Quay account, so their code can be built into a container image and pushed to an image registry for storage and scanning. 
+
+While OpenShift has a built-in image registry, there are various reasons we're using Quay as our image registry:
+
+* Security scanning for container images via Clair.
+* Support for image signing and trust policies.
+* Vulnerability detection with detailed reports.
+* RBAC and repository/organisation permissions.
+* Better suited for multi-tenant and multi-cluster environments.
+
 === Login to {product_name_rhdh} as a Developer
 
 . Navigate to the *Settings* side-menu and click on the kebab menu in the *Profile* card
@@ -19,7 +29,7 @@ image:m3/rhdh-sign-out.png[Signing out of {product_name_rhdh}]
 
 === Create an Account in Quay
 
-You'll need an account in Quay to push your developers container images to.
+You'll need an account in Quay to push your developer's container images to.
 
 . Visit the https://quay.{openshift_cluster_ingress_domain}[Quay Registry^, window="quay"] deployed in your workshop environment.
 . Click the *Create Account* link.