diff --git a/content/resources/operator/_index.md b/content/resources/operator/_index.md
index 5fa0c1fb..c5245a6a 100644
--- a/content/resources/operator/_index.md
+++ b/content/resources/operator/_index.md
@@ -26,7 +26,6 @@ Check out more resources:
 * [Contributions from the Gen3 Community](https://github.com/uc-cdis/compose-services/blob/master/docs/useful_links.md)
 
 ## 1. Gen3 on Helm
-![Gen3 on Helm](img/compose-services.svg)
 
 [Gen3 on Helm](https://github.com/uc-cdis/gen3-helm) is the new preferred way to deploy a Gen3 commons or mesh. Using Helm, a package manager for Kubernetes, Gen3 can be installed against any cluster, including a local one such as Minikube or Rancher Desktop.
 
@@ -35,8 +34,6 @@ This option is suitable for all deployments. If you are ready to get started, yo
 
 ### Cloud Automation (legacy)
 
-![Cloud Automation](img/cloud-automation.svg)
-
 [Gen3 Cloud Automation](https://github.com/uc-cdis/cloud-automation/blob/master/doc/csoc-free-commons-steps.md) was used in the past to deploy Gen3 data commons in production environments on Amazon Web Services, Google Cloud Platform, Microsoft Azure, and OpenStack environments. **It is preserved for legacy reasons.  In the future it may no longer be supported so we encourage all Gen3 operators to make the switch to Gen3 helm.**
 
 Cloud Automation is fully featured supporting integrated logging, security, and compliance steps. With cloud Automation, we utilize Kubernetes to orchestrate our services into a scalable environment that can be run in a cost efficient manner for many tens to thousands of users.