Small intro tweaks

astudentsguide/chapters/foreword/foreword.md

@@ -1,9 +1,9 @@
 # Foreword
 
-Hi, my name is Ethan Richards, and at the time of writing (late 2024), I'm a senior in
+Hi, my name is Ethan Richards, and at the time of writing, I'm a senior in
 Computer Science at the [Colorado School of Mines](https://www.mines.edu). I'm 
-working on finishing up my undergraduate degree (graduating May 2025), but I am
-also pursuing my masters and will graduate with that degree in December 2025.
+working on finishing up my undergraduate degree and will graduate with that in 
+May 2025. I am also pursuing my masters and will graduate with that degree in December 2025.
 
 I'll make this foreword brief and answer the questions that you're probably
 asking: *What gives me the qualifications to write a book about computer science
@@ -19,8 +19,8 @@ I had various involvement with other roles for about 3 years. I also helped orga
 [Mines High School Programming Competition](https://mineshspc.com) for two years.
 
 Outside of academia, I started programming when I was in middle school, fascinated by how 
-I could use Java to modify Minecraft. I have had one internship (and another for my dad's 
-company, if you want to count that), with another lined up for Summer 2025. 
+I could use Java to modify Minecraft. I have had one internship and another for my dad's 
+company, if you want to count that, with another lined up for Summer 2025. 
 
 Of course, all of this does not make me an expert by any means, and I still have a lot
 to learn and experience (and I hope that's the most you ever hear me brag). The purpose 

astudentsguide/chapters/introduction/whatiscs.md

@@ -23,11 +23,11 @@ says: "Software Engineering is the process of designing, developing, testing, an
 suspiciously close to the [Wikipedia definition](https://en.wikipedia.org/wiki/Software_engineering),
 but I think we're all in agreement here.
 
-Software engineering isn't *just* sitting and writing code for eye-straining amounts of time;
+Software engineering ("SWE") isn't *just* sitting and writing code for eye-straining amounts of time;
 it's about designing things that solve problems and serve real people's needs. It's about testing 
 to ensure safety in critical operations, and designing the software with longevity in mind.
 
-## What's the difference?
+## What's the difference between CS & SWE?
 
 Once upon a time, I thought there was no difference. I was quickly corrected. Software engineering is a subset 
 of computer science, but as mentioned, it's not **all** of computer science. A lot of professors and important 
@@ -40,8 +40,8 @@ job outcome from a computer science degree [^ref2].
 
 ## What *isn't* software engineering?
 
-I might be too much of an idealist, but I don't think software engineering is about the paycheck.
-It shouldn't be. I'm always pretty grossed out and disappointed by the people looking at 
+I don't think software engineering is about the paycheck. It shouldn't be. 
+I'm always pretty grossed out and disappointed by the people looking at 
 [levels.fyi](https://www.levels.fyi) comparisons of which company is going to give them $900k a
 year and work them into the ground; or the relatively newfound [ghost software engineers](https://www.businessinsider.com/tech-companies-ghost-engineers-stanford-underperformers-coding-2024-11), 
 who work multiple remote jobs and get paid more for doing less [^ref3].