Minor fixes

Author: ezrichards

astudentsguide/chapters/goodcode/goodcode.md

@@ -50,8 +50,8 @@ but you will get better and better at it with practice.
 
 Writing good code is good, but when you think on a larger scale of a good
 system, there are other considerations. In September 2024, two Google engineers, Paul 
-Christopher and Rob Warner, came and gave a tech talk to [Mines ACM](https://acm.mines.edu) [^ref4],
-had a really memorable quote:
+Christopher and Rob Warner, came and gave a tech talk to [Mines ACM](https://acm.mines.edu) [^ref4]
+which had a really memorable quote:
 
 > The things that are expensive to change are the things that are hardest and most important to get right. Building good systems means making good decisions, not writing good code.
 

astudentsguide/chapters/mindsetattitude/gettingthingsdone.md

@@ -135,7 +135,7 @@ come up; and you'll have the freedom and bandwidth to deal with it.
 Despite all that I've said here, don't enter the **productivity trap**. The productivity
 trap is the idea that you have to be productive 100% of the time; you don't *have* to,
 and in most cases, you *literally can't be* [^ref5]. Sure, if you're pushing toward something great
-you can make sacrifices, but otherwise, say no (see the next section).
+you can make sacrifices, but otherwise, say no (see *Saying no*).
 
 Similar to this is the **self-improvement trap**: you're always buying things and just
 waiting for that one thing that's going to change and fix your whole life (no thanks to our