Rename createRoot & createBlockingRoot to unstable_createRoot & unst…

[raghav0622]

[concurrent mode docs] Rename createRoot & createBlockingRoot with unstable_createRoot & unstable_createBlockingRoot with refrence to latest changes in experimental apis in pr
facebook/react#18825

also closes #2960 (comment)

Issue Number: 2960

[facebook-github-bot]

Hi @raghav0622!

Thank you for your pull request and welcome to our community.We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.

In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[gaearon]

Hmm why didn't CI trigger a website build..

[gaearon]

It's not just createRoot, there's also useTransition, etc. It gets pretty noisy if you add it everywhere in the docs.

I think what we should do instead is to add a new section in Adopting that explains each export is behind unstable_. And has a map of them.

[raghav0622]

It's not just createRoot, there's also useTransition, etc. It gets pretty noisy if you add it everywhere in the docs.

I think what we should do instead is to add a new section in Adopting that explains each export is behind unstable_. And has a map of them.

but still the code examples would need unstable_ as it would be ambigious if unstable is omitted from code examples. i'll create a new pr with separate section explaining unstable