* Remove starting react project from setup page
* Fix typo

fix 18.3.0 release changelog link

...(#7414)

* Update nextjs link with the latest URL
The previous link redirected users to a 404 page.
* Update src/content/reference/react/useDeferredValue.md
---------
Co-authored-by: Ricky <rickhanlonii@gmail.com>

* Update input.md
Fix typo about input
* Update src/content/reference/react-dom/components/input.md
---------
Co-authored-by: Ricky <rickhanlonii@gmail.com>

* clarify alert message behavior in issue #7494
Reworded the explanation regarding the alert message in the documentation to better describe its behavior. The alert shows the previously entered name, with an initial value set to an empty string.
* Update src/content/learn/state-a-components-memory.md
* Update src/content/learn/state-a-components-memory.md
---------
Co-authored-by: Ricky <rickhanlonii@gmail.com>

* Fix broken header link
* Update sunsetting-create-react-app.md

...r <style> when using the `precedence` property (#7643)

This is the exact same fix as #6422 as the example is duplicated between the useOptimistic and <form> pages.

...7654)

* Update index.md
Invalid link to bluesky account
* Update index.md
Fixed invalid bluesky link for react.dev

Ports over the fix in the facebook/react repo for this workflow. We don't have to wait for it to be labeled first, now that we have the reusable maintainer check.

Defaults permissions to none for all workflows, and only request extra permissions when needed.
Similar to facebook/react#32708, prefer the less permissive `pull_request` trigger instead.

* [ci] Fix permissions and don't use pull_request_target
Defaults permissions to none for all workflows, and only request extra permissions when needed.
Similar to facebook/react#32708, prefer the less permissive `pull_request` trigger instead.
* [ci] Pin 3rd party actions to specific hash

facebook/react#32727 removes the `is_remote` param.

* Add React Prague community
* Update link

* Remove captureOwnerStack canary banner
* Update nav and site config

Fixes #8097
The refactored example in the "Chains of computations" section uses
an incorrect condition that changes the game logic from the original.
The original Effect-based code advances the round after 4 gold cards:
- Increments first (0→1, 1→2, 2→3, 3→4)
- Then checks `goldCardCount > 3` (true when count is 4)
The refactored code with `goldCardCount <= 3` allows 5 gold cards:
- Checks before incrementing
- Allows counts 0, 1, 2, 3 to increment (4 values)
- Advances on the 5th card (when count is 4)
This fix changes the condition to `goldCardCount < 3`:
- Allows counts 0, 1, 2 to increment (3 values)
- Advances on the 4th card (when count is 3)
- Matches the original behavior
Verified by tracing execution logic and building the docs site locally.
Co-authored-by: PaulyBearCoding <PaulyBearCoding@users.noreply.github.com>

...section (#8143)

...ave-dev` to `—save-dev`) (#8146)
* Skip smartypants on TerminalBlock
* Improve TerminalBlock HTML tags
* Remove unnecessary TerminalBlock escapes from docs
* Bump DISK_CACHE_BREAKER

...) (#8176)