Update transfork.mdx

Soften the transfork blog a bit

web/src/pages/blog/transfork.mdx

@@ -14,8 +14,8 @@ I've flown out to 8 in-person meetings, attended at least 30 remote meetings, le
 I have spent so much of my limited time on this planet working on this endeavor.
 
 Unfortunately, this is the end of my involvement.
-I think the [MoQ working group](https://datatracker.ietf.org/group/moq/about/) will produce _something_ in 3-5 years, but it's not something that I plan to use with the current direction.
-I'm going to focus on implementing cool shit now, instead of "standard" stuff later.
+I think the [MoQ working group](https://datatracker.ietf.org/group/moq/about/) will produce _something_ in 3-5 years, but it's not something that I plan to use.
+I'm going to focus on my own MoQ fork in the short-term, even if standardization is the "correct" long-term direction.
 
 ## What Happened?
 
@@ -41,7 +41,7 @@ When a user asks how to use MoQ, I don't have an answer except for: "_it depends
 The [transport draft](https://www.ietf.org/archive/id/draft-ietf-moq-transport-06.html) has become so abstracted and optional, with few reliable properties.
 It's a Temo Swiss Army Knife; capable of doing everything badly instead of the one thing it should focus on: _live media_.
 
-And to be clear, this isn't entirely Cisco's fault.
+And to be clear, this isn't Cisco's fault.
 They have the right intentions and of them are frankly brilliant (shoutout to Cullen, Mo, Christian).
 However, the power dynamics in the MoQ working group are broken until there are other stakeholders who actually care about media.
 
@@ -59,8 +59,7 @@ To this end, I've created:
 
 I swear there used to be [fork emoji](https://www.reddit.com/r/MandelaEffect/comments/16eq2nx/fork_emoji/).
 
-The demos on this site use both of course.
-I'm working on documenting everything and fixing any outstanding bugs after the hard fork.
+The demos on this site use both of course, but I still need to update a lot of documentation and fix any new bugs. 
 
 ## New Release
 
@@ -91,13 +90,14 @@ If you want to stick with the IETF standard, that's fine but you gotta hit the f
 ## What's Next?
 
 I'm going to continue investing all of my free time (and hopefully some of my professional time) into MoQ.
-But the time that would have been spent arguing to be better spent actually implementing cool shit.
-The next step is a conferencing demo.
+But the time that would have been spent arguing to be better spent actually implementing cool shit: the next step is a conferencing demo.
 
 I would highly encourage that anyone else do the same.
 If you're an individual, startup, or a massive company alike, I would recommend that you don't block on the IETF.
-Use the tech that is available today (ex. WebTransport + WebCodecs) instead of a promised standard.
+It's a great organization, but standards are an intentionally slow process designed by committee and all of the baggage that entails.
 
+I think MoQ needs to move faster.
+Use the tech that is available today (ex. WebTransport + WebCodecs) instead of a promised standard.
 You can always hit [me](https://github.com/kixelated) up on [Discord](https://discord.gg/FCYF3p99mr) if you want to use MoQ and crave more advice.
 I can't promise that it will be good advice though.