Clarify moq-lite standards compliance and CDN compatibility (#84)

Co-authored-by: Claude <noreply@anthropic.com>

Author: kixelated

src/pages/index.mdx

@@ -40,7 +40,8 @@ There's a new way to achieve **real-time latency** in the browser, including con
 - 🔧 **Customizable**: Hardware accelerated encoding, the rest is in your control.
 
 ### *Standards
-This website uses a [fork](/blog/transfork) of the IETF draft called [moq-lite](https://doc.moq.dev/concept/layer/moq-lite) and a media layer called [hang](https://doc.moq.dev/concept/layer/hang).
+This website uses [moq-lite](https://doc.moq.dev/concept/layer/moq-lite), a subset of the IETF [moq-transport](https://datatracker.ietf.org/doc/draft-ietf-moq-transport/) draft.
+moq-lite is forwards compatible with moq-transport, so it works with any moq-transport CDN (ex. [Cloudflare](/blog/first-cdn)).
 The principles behind MoQ are fantastic, but standards are **SLOW** and involve too much arguing.
 My goal is to build something simple that you can use *now*, even if it's not a standard *yet*.