Some JSX docs updates

Author: cknitt

pages/docs/react/latest/beyond-jsx.mdx

@@ -14,7 +14,7 @@ JSX is a syntax sugar that allows us to use React components in an HTML like man
 
 **Note:** This section requires knowledge about the low level apis for [creating elements](./elements-and-jsx#creating-elements-from-component-functions), such as `React.createElement` or `ReactDOM.createDOMElementVariadic`.
 
-> **Note:** This page assumes your `rescript.json` to be set to `"jsx": { "version": 4 }` to apply the right JSX transformations. 
+> **Note:** The output shown for the examples on this page assumes your `rescript.json` to be set to `"jsx": { "version": 4, "mode": "classic" }`. We will update it for automatic mode soon.
 
 ## Component Types
 

pages/docs/react/latest/elements-and-jsx.mdx

@@ -12,7 +12,7 @@ Elements are the smallest building blocks of React apps. This page will explain
 
 </Intro>
 
-> **Note:** This page assumes your `rescript.json` to be set to `"jsx": { "version": 4 }`, otherwise your JSX will not be transformed to its React specific form. 
+> **Note:** The output shown for the examples on this page assumes your `rescript.json` to be set to `"jsx": { "version": 4, "mode": "classic" }`. We will update it for automatic mode soon.
 
 ## Element Basics
 

pages/docs/react/latest/extensions-of-props.mdx

@@ -6,7 +6,7 @@ canonical: "/docs/react/latest/spread-props"
 
 # Extensions of Props
 
-> **Note:** This page assumes your `rescript.json` to be set to `"jsx": { "version": 4 }` to apply the right JSX transformations.
+> **Note:** The output shown for the examples on this page assumes your `rescript.json` to be set to `"jsx": { "version": 4, "mode": "classic" }`. We will update it for automatic mode soon.
 
 ## Spread props
 

pages/docs/react/latest/installation.mdx

@@ -8,10 +8,10 @@ canonical: "/docs/react/latest/installation"
 
 **Requirements:**
 
-- `rescript@10.1` or later
+- `rescript@11.0` or later
 - `[email protected]` or later
 
-Add following dependency to your ReScript project (in case you don't have any project yet, check out the [installation instructions](/docs/manual/latest/installation) in the manual):
+Add the following dependency to your ReScript project (in case you don't have any project yet, check out the [installation instructions](/docs/manual/latest/installation)):
 
 ```
 npm install @rescript/react
@@ -21,14 +21,14 @@ Then add the following setting to your existing `rescript.json`:
 
 ```json
 {
-  "jsx": { "version": 4, "mode": "classic" },
+  "jsx": { "version": 4, "mode": "automatic" },
   "bs-dependencies": ["@rescript/react"]
 }
 ```
 
-> The [new jsx transform](https://ko.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html) of ReactJS is available with `mode: "automatic"`.
+> `mode: "automatic"` means that the new JSX runtime introduced in React 17 (`react/jsx-runtime`) is used. This should be the default for new projects.
 
-**Note** JSX v4 is newly introduced with the idiomatic record-based representation of a component. If your dependencies are not compatible with v4 yet, then you can use v3 in the same project. Check out the details in [Migrate from v3](/docs/react/latest/migrate-react)
+**Note:** In case your dependencies are not compatible with version 4 of the ReScript JSX transformation yet, then you can use v3 in the same project. Check out the details in [Migrate from v3](/docs/react/latest/migrate-react).
 
 To test your setup, create a new `.res` file in your source directory and add the following code:
 

pages/docs/react/latest/introduction.mdx

@@ -6,7 +6,7 @@ canonical: "/docs/react/latest/introduction"
 
 # ReScript & React
 
-ReScript offers first class bindings for [ReactJS](https://reactjs.org) and is designed and built by people using ReScript and React in large mission critical React codebases. The bindings are compatible with modern React versions (>= v18.0).
+ReScript offers first class bindings for [ReactJS](https://react.dev) and is designed and built by people using ReScript and React in large mission critical React codebases. The bindings are compatible with modern React versions (>= v18.0).
 
 The ReScript philosophy is to compile as closely to idiomatic JS code as possible; in the case of ReactJS, we made no exception, so it's not only easy to transfer all the React knowledge to the ReScript platform, but also straightforward to integrate with existing ReactJS codebases and libraries.
 
@@ -22,7 +22,7 @@ All our documented examples can be compiled in our [ReScript Playground](/try) a
 
 > **This documentation assumes basic knowledge about ReactJS.**
 >
-> Please note that even though we will cover many basic React concepts, it might still be necessary to have a look at the official [ReactJS](https://reactjs.org) resources, especially if you are a complete beginner with React.
+> Please note that even though we will cover many basic React concepts, it might still be necessary to have a look at the official [ReactJS](https://react.dev) resources, especially if you are a complete beginner with React.
 
 ## Development
 

pages/docs/react/latest/migrate-react.mdx

@@ -6,7 +6,7 @@ canonical: "/docs/react/latest/migrate-react"
 
 # Migrate from JSX v3
 
-JSX v4 introduces a new idiomatic record-based representation of components which is incompatible with v3. Because of this, either the entire project or dependencies need to be compiled in V4 mode, or some compatibility features need to be used to mix V3 and V4 in the same project. This page describes how to migrate from v3 to v4.
+JSX v4 introduces a new idiomatic record-based representation of components which is incompatible with v3. Because of this, either the entire project or dependencies need to be compiled in v4 mode, or some compatibility features need to be used to mix v3 and v4 in the same project. This page describes how to migrate from v3 to v4.
 
 ## Configuration
 
@@ -28,24 +28,26 @@ Then add the new JSX configuration:
 
 **Note** JSX v4 requires the rescript compiler 10.1 or higher, and rescript-react version 0.11 or higher. In addition, react version 18.0 is required.
 
-### Classic and Automatic Mode
+### Automatic and Classic Mode
 
-Classic mode is the default and generates calls to `React.createElement` just as with V3.
+Automatic mode uses the new JSX runtime (`react/jsx-runtime`) introduced in React 17.
 
 ```json
 {
-  "jsx": { "version": 4, "mode": "classic" }
+  "jsx": { "version": 4, "mode": "automatic" }
 }
 ```
 
-Automatic mode is an experimental mode that generate calls to `_jsx` functions (similar to TypeScript's `react-jsx` mode)
+Classic mode generates calls to the legacy `React.createElement` API just as with v3.
 
 ```json
 {
-  "jsx": { "version": 4, "mode": "automatic" }
+  "jsx": { "version": 4, "mode": "classic" }
 }
 ```
 
+Currently, if no mode is specified, `classic` is still used as the default. However, that may change in future ReScript versions. We recommend using `automatic` mode for new and migrated projects.
+
 ### File-level config
 
 The top-level attribute `@@jsxConfig` is used to update the `jsx` config for the rest of the file (or until the next config update). Only the values mentioned are updated, the others are left unchanged.
@@ -84,9 +86,9 @@ JSX v3 is still available with the latest version of compiler and rescript-react
 }
 ```
 
-To build certain dependencies in V3 compatibility mode, whatever the version used in the root project, use `"v3-dependencies"`. The listed dependencies will be built in V3 mode, and in addition `-open ReactV3` is added to the compiler options.
+To build certain dependencies in v3 compatibility mode, whatever the version used in the root project, use `"v3-dependencies"`. The listed dependencies will be built in v3 mode, and in addition `-open ReactV3` is added to the compiler options.
 
-## Migration of V3 components
+## Migration of v3 components
 
 Some components in existing projects are written in a way that is dependent on the v3 internal representation. Here are a few examples of how to convert them to v4.
 
@@ -179,7 +181,7 @@ let make = () => {
 }
 ```
 
-To this: In v3, there is an inconsistency between `ref` as prop and `ref_` as argument. With JSX V4, `ref` is only allowed as an argument.
+To this: In v3, there is an inconsistency between `ref` as prop and `ref_` as argument. With JSX v4, `ref` is only allowed as an argument.
 
 ```res
 module FancyInput = {