diff --git a/ps2grouper.adoc b/ps2grouper.adoc
index 4c8de56..e9e8d7d 100644
--- a/ps2grouper.adoc
+++ b/ps2grouper.adoc
@@ -5,8 +5,6 @@ Ethan Kromhout, 2 Nov 2022
 I wanted to talk about how our data currently gets from Peoplesoft to Grouper.
 There's maybe a story that I didn't include about how grouper data gets indirectly to peoplesoft. But maybe I can comment about that at the end.
 
-image::images/uncInfMat.jpg[Informatica path]
-
 We've got three main paths the data goes through to get from from Peoplesoft to to Grouper. 
 
 image::images/unc3flows.png[three paths]
@@ -14,8 +12,6 @@ image::images/unc3flows.png[three paths]
 The first path is the the largest and most complex is our our homegrown Java app. We call it directory manager, but it's basically been
 the place where the business logic happens for deciding people's, affiliation states and things like that, and getting those things published out to, particularly, the Open LDAP Directory, but also Active Directory.
 
-image::images/uncInfMat.jpg[Informatica path]
-
 So that path through Directory Manager includes our oldest integration, which is with campus solutions. We brought up campus solutions in 2009 well ahead of bringing up the HR And finance modules. The integrations are messaging and the reason for those two different transports are that the original campus solutions integration was all messaging.
 
 The original campus solutions integration was all messaging based, and then we just found that later a polling strategy was perhaps at least as effective as the messaging we were doing.