docs: change the unnecessarily mocking tone of the React docs

[andrii-bodnar]

Description

#1904

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Examples update

Checklist

• I have read the CONTRIBUTING and CODE_OF_CONDUCT docs
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 4, 2024 7:37am

[github-actions]

size-limit report 📦

Path	Size
./packages/core/dist/index.mjs	2.86 KB (0%)
./packages/detect-locale/dist/index.mjs	723 B (0%)
./packages/react/dist/index.mjs	1.67 KB (0%)
./packages/remote-loader/dist/index.mjs	7.26 KB (0%)

[vonovak]

I'd say we should not only remove the mocking tone but explicitly admit / warn that Trans changes the standard JSX behavior.

It's true it doesn't make sense to write <Trans>{isOpen && <Modal />}</Trans> but it makes sense to write more complicated JSX as noted in #1904

[andrii-bodnar]

@vonovak do you have any ideas on how to note this compactly without giving another example for this specific case?

[vonovak]

I think, considering #1906 we can merge this as-is