diff --git a/posts/2021-05-03-time-rant.md b/posts/2021-05-03-time-rant.md
index 3f28b0b..268f8e8 100644
--- a/posts/2021-05-03-time-rant.md
+++ b/posts/2021-05-03-time-rant.md
@@ -11,14 +11,13 @@ standard should Bob use to schedule the call? How about
 should be able to use it, right?
 
 Unfortunately, life is not so simple. If Bob scheduled a call for “05:00 UTC”,
-one other person would show up on-time. The rest will try to join at 17:00
-(05:00 p.m.) in whatever their local time zone is. This insanity is the reason
-why [countdown timers](https://www.timeanddate.com/countdown/create)
-are so common nowadays.
+one other person will show up on-time. The rest will try to join at 17:00
+(05:00 p.m.) in whatever their local time zone is. Frustrating situations like
+these are responsible for
+[countdown timers](https://www.timeanddate.com/countdown/create)
+becoming so common nowadays.
 
-
-
-This insanity has been driving people insane since the beginning of time, but
+This insanity has been driving people mad since the beginning of time, but
 this is not the fault of individual people who don’t understand what “UTC” is.
 This is a systemic issue which ought to be corrected. If everybody learns to
 read analog clocks in primary school, they should learn about time zones as
@@ -59,7 +58,7 @@ the time and displaying it to users.
 
 As far as most people should be concerned, offsets are just acronyms that
 represent offsets from UTC. For example, [Central European Time](https://www.timeanddate.com/time/zones/cet)
-(CET) is one hours ahead of UTC. This means that it is also represented as
+(CET) is one hour ahead of UTC. This means that it is also represented as
 UTC+1 or UTC+0100. Some time zones need more than an hour of precision as well.
 For example, [Newfoundland Standard Time](https://www.timeanddate.com/time/zones/nst)
 (NST) is represented as UTC-3:30 or UTC-0330.