diff --git a/ps2grouper.adoc b/ps2grouper.adoc
index a99f5c9..ced7e54 100644
--- a/ps2grouper.adoc
+++ b/ps2grouper.adoc
@@ -7,12 +7,12 @@ There's maybe a story that I didn't include about how grouper data gets indirect
 
 We've got three main paths the data goes through to get from from Peoplesoft to to Grouper. 
 
-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 first path, 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/unc3flows.jpg[Directory Manager]
 
-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.
+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.
 So when we did the integrations with HR And Finance, those were done as as SOAP transport integrations and either way it's It's pretty close to real time. So the the information that's pushed by messaging. And unless there is a ton of changes that back things the updates are near real-time.