diff --git a/perydAffilFwork.adoc b/perydAffilFwork.adoc
index a387e6d..3e62ce2 100644
--- a/perydAffilFwork.adoc
+++ b/perydAffilFwork.adoc
@@ -44,11 +44,11 @@ And then we already talked about the little icon. So it is part of the constitue
 
 I don't remember when it was, but it was a while back we tried to implement affiliation framework and had a lot of hurdles. So we ended up just so that we could meet this need delivering. I just created like a sql script that the Dba's had on a cron job that would run every night to identify current employees, former employees, current students, and former students, so that when new apps came into the system it would check and see, because they did not want
 those applications to update any bio demo data for existing current employees, for example, or existing current students and things like that. So that's where that comes in currently. We've gone live with affiliation framework like two weeks ago when it went Live any discrepancies, you know, do doing, reporting. We can um use it to continue our co-manage integration efforts and things like that. But I thought it would be interesting to show you guys, some of the counts that we have with our current um affiliations. And I, broke out the instructor, one, because that one is not dependent on job data, obviously right. So So the ones that have, for example, adjunct faculty. There's three hundred and thirty-eight
-but as you can see here, Um, we have e instructor assigned to six hundred and sixty-eight that are set up as instructor type adjunct in the instructor visor table, and that is because we do have an issue with getting those higher forms in a timely fashion and things like that. So the instructor. Affiliation code is intended to be sort of a high level. We don't want to say that you are an adjunct, because you can be a teaching assistant, or a Gsi, or graduate student structure, full time, faculty, or whatever. And currently, unfortunately, in our people's soft um system. These instructor types are not maintained. Uh. So there's not a high degree of confidence, and and using those as our as our source to say, Yes, you are now jumped right, because we know of instances where, for example, we have full time faculty that come in,
+but as you can see here, Um, we have e instructor assigned to six hundred and sixty-eight that are set up as instructor type adjunct in the instructor visor table, and that is because we do have an issue with getting those higher forms in a timely fashion and things like that. So the instructor. Affiliation code is intended to be sort of a high level. We don't want to say that you are an adjunct, because you can be a teaching assistant, or a Gsi, or graduate student structure, full time, faculty, or whatever. And currently, unfortunately, in our peoplesoft system. These instructor types are not maintained, So there's not a high degree of confidence, and using those as our as our source to say, Yes, you are now assigned right. We know of instances where, for example, we have full time faculty that come in,
 
 244
 00:32:12.110 --> 00:32:29.800
-Pery Doan: and then they retire, and then so they're in this table. This full time faculty. They retire. They come back as adjuncts, and nobody updates this to adjunct again. So we're moving in other projects to try to improve that data quality, and we have made a lot of progress in trying to sync it up with what job data says and things like that. But we're still not at one hundred percent confidence
+Pery Doan: so they're in this table as full time faculty. They retire. They come back as adjuncts, and nobody updates their role to adjunct again. So we're moving in other projects to try to improve that data quality, and we have made a lot of progress in trying to sync it up with what job data says and things like that. But we're still not at one hundred percent confidence
 
 246
 00:32:38.840 --> 00:32:52.109