diff --git a/content/log/2022/big-tech-hiring.md b/content/log/2022/big-tech-hiring.md
index 7efe26e..9e6e700 100644
--- a/content/log/2022/big-tech-hiring.md
+++ b/content/log/2022/big-tech-hiring.md
@@ -284,15 +284,15 @@ Now let's talk business. I will be running an [Uber Mock
 Interview][uber-mock-interview] on 2022 June 29th. The mock interview
 familiarizes potential candidates with the interview process, hopefully
 reducing uncertainty, and thus stress. Listening for a presentation about
-Uber's interview process sounds boring; looking at a live interview does not.
-For obvious reasons, we cannot live-stream a candidate, so we will do the next
+Uber's interview process sounds boring; looking at a live interview — much less
+so. For obvious reasons, we cannot live-stream a candidate, we will do the next
 best thing: conduct an interview which is for all intents and purposes real,
-except I will not get or lose a job if I fail it.
+except I will not get or lose a job if I make or fail it.
 
 So we will be conducting a mock interview. Because it should be educational
 *and* fun, this is what we will do:
 1. I will not know the exercise beforehand. We will all see it, including
-   myself, at the same time.
+   myself, at the same moment.
 2. I have not done a technical interview for >6 years now, so I did *a bit* of
    preparation. Not too much though, like most of us when applying for a job.
 3. I may fail the interview, therefore I know I will be stressed more than at
@@ -323,5 +323,3 @@ Many thanks to Abhinav Gupta and Tim Miller for reading drafts of this.
   me for a referral. Keep in mind, though, that I will spend some time to
   understand whether I believe you are a good fit. See the post for my
   criteria.
-
-