diff --git a/content/echoes/ts-array-variance-standup.dj b/content/echoes/ts-array-variance-standup.dj
index 2747fd4..8944ea3 100644
--- a/content/echoes/ts-array-variance-standup.dj
+++ b/content/echoes/ts-array-variance-standup.dj
@@ -74,7 +74,7 @@ The issue is that (informally), at every point, TypeScript keeps track of the ti
 ```ts
 const nums: number[] = [0]
 const arr: (number | string)[] = nums
-arr.push("oops") // works
+arr.push("oops") // works, even though we're still referencing the same array!
 ```
 
 Duck typing the procedure multiple times (as suggested by Casey) will not fix the issue, as the issue is not tied to procedures in the first place. As stated above, the issue arises from TypeScript' treatment of array variance, which could be trivially fixed if backwards compatibility wasn't a concern.