[docs] Fix typo in CHANGELOG.md

[gjoseph]

No description provided.

[oliviertassinari]

It looks like that publishing on npm has created some attention. We should probably batch npm release + GitHub release + Blog post + Tweet the next time we face this situation. @gjoseph Thanks

[flaviendelangle]

I think we all agree on that
But to do so, we have to start working on the blog post at least one week earlier.
The question here for me was more : Was it worth delaying the release until the blog post was merged, given the fact that we started this blog post too late ?
And I think it was the good decision not to do so. We delayed it by 3 working days. We are now 6 working days after we started the release PR and we still don't have merged the blog post (Matt approved it so I hope we will be able to merge it on Monday).

[oliviertassinari]

we have to start working on the blog post at least one week earlier.

Agree, MUI Core v5 blog post was 4 weeks in the making. For the magnitude of the changes in X v5, at least 7 days sounds great. It would probably move faster once we have a dedicated DevRel that becomes owner/accountable for the final content, someone that can guarantee it reach a specific quality target. Right now, Matt & I are bottlenecks.

Was it worth delaying the release until the blog post was merged, given the fact that we started this blog post too late?

From my perspective, I think that it's always worth it, no matter the conditions. I'm saying this because I have never seen a popular open-source project publish a new major version without an announcement (or maybe it happened but didn't notice)

Still, I think that we could shift the question to: is it always worth polishing the blog post further? Or at some point, we can call it good enough, ship even if it's not at the level we target to unlock the value blocked?

I hope we will be able to merge it on Monday

I'm giving it a final look.