Add image alt text and fix typos in Cars/Fastly blog posts

Replace placeholder alt text on every figure with descriptions of the
actual drawings, and fix a few typos while keeping the writing style.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: kixelated

src/pages/blog/cars2.mdx

@@ -20,8 +20,8 @@ MoQ be fast. 🚀
 Cars 2™ is a 2011 American animated comedy film produced by Pixar Animation Studios for Walt Disney Pictures.
 
 <figure>
-	![Cars 2](/blog/cars2/queen.png)
-	<figcaption>staring Lightning McQueen, the devilishly handsome race car</figcaption>
+	![A hand-drawn doodle of a race car resembling Lightning McQueen, dark with green accents and a "69", labeled "it me"](/blog/cars2/queen.png)
+	<figcaption>starring Lightning McQueen, the devilishly handsome race car</figcaption>
 </figure>
 
 ## Cars 2: Electric Boogaloo
@@ -72,7 +72,7 @@ And milliseconds might be the difference between winning and losing.
 **FUN FACT**: Sports ~betting~ prediction markets are a thing. Degenerate users love lower latency.
 
 <figure>
-	![Cars 2](/blog/cars2/speed2.png)
+	![A hand-drawn speedometer with "Losing" and "Winning" at each end, the needle pushed past a marked "HLS/DASH limit"](/blog/cars2/speed2.png)
 	<figcaption>crank that dial</figcaption>
 </figure>
 
@@ -116,7 +116,7 @@ Each MoQ subscriber independently decides how long to wait for each frame:
 So your real-time feed might be lossy af, but the VOD is pristine.
 
 <figure>
-	![Cars 2](/blog/cars2/backfill.png)
+	![A doodle contrasting a glitchy, crossed-out "Realtime" race car frame with a clean "Backfill" version of the same car](/blog/cars2/backfill.png)
 	<figcaption>If I ever own a racing team, it's going to be called The Backfill Boyes</figcaption>
 </figure>
 
@@ -144,7 +144,7 @@ You can delta encode a lot of things, [even JSON](https://datatracker.ietf.org/d
 Just like I delta encoded your mom last night.
 
 <figure>
-	![Cars 2](/blog/cars2/mom.png)
+	![A doodle equation: a round stick figure plus the green MoQ cat logo equals a Lightning McQueen-style race car](/blog/cars2/mom.png)
 	<figcaption>yes, a ur mom joke in `<current_year>`</figcaption>
 </figure>
 
@@ -203,7 +203,7 @@ This is known colloquially as "big deal" when flakey venue internet and expensiv
 Run a self-hosted relay at each track, aggregate all of the feeds automatically, and publish them to a CDN.
 
 <figure>
-	![Cars 2](/blog/cars2/fanout.png)
+	![A diagram of one car publishing to a relay that fans out across a CDN of interconnected relays to many subscribers](/blog/cars2/fanout.png)
 	<figcaption>literally infinite viewers from a single, semi-reliable feed</figcaption>
 </figure>
 

src/pages/blog/moq-cars-fastly.mdx

@@ -23,7 +23,7 @@ Pick your poison.
 We're going to learn about the numerous ways you can use MoQ **in the fast lane**.
 
 <figure>
-	![Fastly Lane](/blog/cars2/f1.png)
+	![A hand-traced drawing of a black and red Formula 1 car labeled "Zoom Zoom" and "MoQ"](/blog/cars2/f1.png)
 	<figcaption>Either way, you're getting a badly traced picture of a car. At least it's not AI generated.</figcaption>
 </figure>
 
@@ -65,7 +65,7 @@ Like yeah duh, waiting is always going to result in better picture quality.
 But the hypothesis is that some users **prefer lower latency** at the **expense of quality**.
 
 <figure>
-	![Fastly Lane](/blog/cars2/speed.png)
+	![A hand-drawn speedometer with "quality" and "latency" at each end, the needle pushed past a marked "HLS/DASH limit"](/blog/cars2/speed.png)
 	<figcaption>The ability to crank that dial is what makes MoQ, MoQ</figcaption>
 </figure>
 
@@ -85,7 +85,7 @@ There's absolutely a tradeoff here.
 But that's also the beauty of MoQ, it's a configurable latency dial you can crank up or down.
 
 <figure>
-	![Fastly Lane](/blog/cars2/latency.png)
+	![A diagram comparing MoQ, which drops 2 seconds of content in the middle of the stream, with HLS/DASH, which adds 2 seconds of latency at the end](/blog/cars2/latency.png)
 	<figcaption>**THE DECISION**: You either miss 2 seconds of the action, or spend 2 seconds buffering</figcaption>
 </figure>
 
@@ -94,7 +94,7 @@ We just allow a lower latency floor.
 
 
 ## MoQ for the Cars
-While I originally made MoQ for the fans, companies insisting on running it on the cars.
+While I originally made MoQ for the fans, companies insist on running it on the cars.
 Or the drones.
 [Or the boats](https://moq.dev/blog/on-a-boat).
 
@@ -117,7 +117,7 @@ The old stuff doesn't get dropped, **it gets queued in RAM** (up to a TTL).
 When bandwidth recovers, we can **backfill old footage** instead of losing it forever.
 
 <figure>
-	![Fastly Lane](/blog/cars2/backfill2.png)
+	![A drawing contrasting a broken-up, crossed-out "Realtime" F1 car feed with a complete "Backfill" version](/blog/cars2/backfill2.png)
 	<figcaption>If I ever own a racing team, it's going to be called The Backfill Boys</figcaption>
 </figure>
 
@@ -145,11 +145,11 @@ It's just delta encoded data.
 You can delta encode a lot of things, [even JSON](https://datatracker.ietf.org/doc/html/rfc7386).
 
 Networks are finite, so we split up media into pieces.
-Each inidividual track, group, frame, packet, *could* be dropped without terminating the media stream.
+Each individual track, group, frame, packet, *could* be dropped without terminating the media stream.
 The reality is that some bytes are just less valuable than others.
 
 The hard part is putting humpty back together.
-That's why use timestamps; they tell us when stuff happened relative to other stuff.
+That's why we use timestamps; they tell us when stuff happened relative to other stuff.
 Even metadata gets stamped so it can be associated with audio/video frames.
 
 You can, and should, take the red pill and use MoQ for **EVERYTHING**.
@@ -193,7 +193,7 @@ Run a few moq-relay instances at each race track, aggregating all of the feeds a
 ez pz
 
 <figure>
-	![Fastly Lane](/blog/cars2/fanout2.png)
+	![A diagram of an F1 car publishing to a relay that fans out across interconnected relays to many subscribers](/blog/cars2/fanout2.png)
 	<figcaption>literally infinite viewers from a single, semi-reliable feed</figcaption>
 </figure>