Merge pull request #625 from reactjs/sync-d4e42ab2

carburo · gaearon · hwanyoungChoi · web-flow · commit 5162933e2f1c · 2023-02-06T08:10:27.000-05:00
* Fix typo

* Update reference Profiler.md (#5502)

* Fix typo, closes #5505

* Update conference lists for beta docs (#5529)

* Update past conferences chronological list

* Update React India 2023 dates on beta docs

* Fix conference order for past conferences 2022

* Fix failing header id lint error

:

;
lld
;

* Announce  react india 2023 conference dates (#5525)

* Update instructions to Babel 7

* Added react nexus to the conference list (#5536)

* Add missing word (#5537)

* Resolve merge conflicts

---------

Co-authored-by: Dan Abramov &lt;dan.abramov@gmail.com&gt;
Co-authored-by: Cony &lt;cony.choi@kidsnote.com&gt;
Co-authored-by: Sahil Mhapsekar &lt;saheel.mhapsekar@gmail.com&gt;
Co-authored-by: Kiran Abburi &lt;akiran@users.noreply.github.com&gt;
Co-authored-by: Beau House &lt;58791971+beau-house@users.noreply.github.com&gt;
Co-authored-by: Rainer Martinez &lt;rmartinezfraga@gmail.com&gt;
diff --git a/beta/src/content/community/conferences.md b/beta/src/content/community/conferences.md
@@ -10,21 +10,6 @@ Do you know of a local React.js conference? Add it here! (Please keep the list c
 
 ## Upcoming Conferences {/*upcoming-conferences*/}
 
-### React Global Online Summit 22.2 by Geekle {/*react-global-online-summit-222-by-geekle*/}
-November 8 - 9, 2022 - Online Summit
-
-[Website](https://events.geekle.us/react3/) - [LinkedIn](https://www.linkedin.com/posts/geekle-us_event-react-reactjs-activity-6964904611207864320-gpDx?utm_source=share&utm_medium=member_desktop)
-
-### Remix Conf Europe 2022 {/*remix-conf-europe-2022*/}
-November 18, 2022, 7am PST / 10am EST / 4pm CET - remote event
-
-[Website](https://remixconf.eu/) - [Twitter](https://twitter.com/remixconfeu)
-
-### React Day Berlin 2022 {/*react-day-berlin-2022*/}
-December 2, 2022. In-person in Berlin, Germany + remote (hybrid event)
-
-[Website](https://reactday.berlin) - [Twitter](https://twitter.com/reactdayberlin) - [Facebook](https://www.facebook.com/reactdayberlin/) - [Videos](https://www.youtube.com/c/ReactConferences)
-
 ### RemixConf 2023 {/*remixconf-2023*/}
 May, 2023. Salt Lake City, UT
 
@@ -50,8 +35,28 @@ June 27th, 2023. Tel Aviv, Israel
 
 [Website](https://www.react-next.com/) - [Facebook](https://www.facebook.com/ReactNextConf) - [Youtube](https://www.youtube.com/@ReactNext)
 
+### React India 2023 {/*react-india-2023*/}
+Oct 5 - 7, 2023. In-person in Goa, India (hybrid event) + Oct 3 2023 - remote day 
+
+[Website](https://www.reactindia.io) - [Twitter](https://twitter.com/react_india) - [Facebook](https://www.facebook.com/ReactJSIndia) - [Youtube](https://www.youtube.com/channel/UCaFbHCBkPvVv1bWs_jwYt3w)
+
 ## Past Conferences {/*past-conferences*/}
 
+### React Day Berlin 2022 {/*react-day-berlin-2022*/}
+December 2, 2022. In-person in Berlin, Germany + remote (hybrid event)
+
+[Website](https://reactday.berlin) - [Twitter](https://twitter.com/reactdayberlin) - [Facebook](https://www.facebook.com/reactdayberlin/) - [Videos](https://www.youtube.com/c/ReactConferences)
+
+### React Global Online Summit 22.2 by Geekle {/*react-global-online-summit-222-by-geekle*/}
+November 8 - 9, 2022 - Online Summit
+
+[Website](https://events.geekle.us/react3/) - [LinkedIn](https://www.linkedin.com/posts/geekle-us_event-react-reactjs-activity-6964904611207864320-gpDx?utm_source=share&utm_medium=member_desktop)
+
+### Remix Conf Europe 2022 {/*remix-conf-europe-2022*/}
+November 18, 2022, 7am PST / 10am EST / 4pm CET - remote event
+
+[Website](https://remixconf.eu/) - [Twitter](https://twitter.com/remixconfeu)
+
 ### React Advanced 2022 {/*react-advanced-2022*/}
 October 21 & 25, 2022. In-person in London, UK + remote (hybrid event)
 
diff --git a/beta/src/content/learn/add-react-to-a-website.md b/beta/src/content/learn/add-react-to-a-website.md
@@ -196,7 +196,7 @@ Añadir JSX a un proyecto no requiere herramientas complicadas como un [*bundler
 Ve a la carpeta de tu proyecto en la terminal, y pega estos dos comandos (**¡Asegúrate de tener instalado [Node.js](https://nodejs.org/)!**):
 
 1. `npm init -y` (si falla, [aquí hay una solución](https://gist.github.com/gaearon/246f6380610e262f8a648e3e51cad40d))
-2. `npm install babel-cli@6 babel-preset-react-app@3`
+2. `npm install @babel/cli@7 babel-preset-react-app@10`
 
 Solo necesitas npm para instalar el preprocesador de JSX. No lo necesitarás para nada más. Tanto React como el código de la aplicación se pueden quedar como etiquetas `<script>` sin cambios.
 
@@ -207,7 +207,7 @@ Solo necesitas npm para instalar el preprocesador de JSX. No lo necesitarás par
 Puedes preprocesar JSX de forma tal que cada vez que guardes un archivo con JSX dentro, la transformación se vuelva a ejecutar y convierta el JSX en un archivo nuevo con JavaScript simple que el navegador puede entender. Aquí puedes ver cómo hacer la configuración:
 
 1. Crea una carpeta llamada **`src`**.
-2. En tu terminal, ejecuta este comando: `npx babel --watch src --out-dir . --presets react-app/prod ` (¡No esperes a que termine! Este comando inicia un *watcher* (observador) automático para las ediciones de JSX dentro de `src`).
+2. En tu terminal, ejecuta este comando: `npx babel --watch src --out-dir . --presets babel-preset-react-app/prod ` (¡No esperes a que termine! Este comando inicia un *watcher* (observador) automático para las ediciones de JSX dentro de `src`).
 3. Mueve tu **`like-button.js`** con JSX ([¡debería lucir así!](https://gist.githubusercontent.com/gaearon/be5ae0fbf563d6c5fe5c1563907b13d2/raw/4c0d0b8c7f4fcb341720424c28c72059f8174c62/like-button.js)) a la nueva carpeta **`src`**.
 
 El *watcher* creará un **`like-button.js`** preprocesado con el código JavaScript simple que es adecuado para un navegador.
diff --git a/beta/src/content/reference/react-dom/components/select.md b/beta/src/content/reference/react-dom/components/select.md
@@ -223,7 +223,7 @@ select { display: block; margin-top: 10px; width: 200px; }
 
 ### Reading the select box value when submitting a form {/*reading-the-select-box-value-when-submitting-a-form*/}
 
-Add a [`<form>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form) around your textarea with a [`<button type="submit">`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button) inside. It will call your `<form onSubmit>` event handler. By default, the browser will send the form data to the current URL and refresh the page. You can override that behavior by calling `e.preventDefault()`. To read the form data, use [`new FormData(e.target)`](https://developer.mozilla.org/en-US/docs/Web/API/FormData).
+Add a [`<form>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form) around your select box with a [`<button type="submit">`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button) inside. It will call your `<form onSubmit>` event handler. By default, the browser will send the form data to the current URL and refresh the page. You can override that behavior by calling `e.preventDefault()`. To read the form data, use [`new FormData(e.target)`](https://developer.mozilla.org/en-US/docs/Web/API/FormData).
 <Sandpack>
 
 ```js
diff --git a/beta/src/content/reference/react-dom/hydrate.md b/beta/src/content/reference/react-dom/hydrate.md
@@ -64,7 +64,7 @@ React se unirá al HTML que existe dentro del nodo DOM `domNode`, y se encargar
 
 Llama a `hydrate` para unir un  <CodeStep step={1}>componente de React</CodeStep> a un <CodeStep step={2}>nodo DOM del navegador</CodeStep> renderizado por el servidor.
 
-```js [[1, 3, "document.getElementById('root')"], [2, 3, "<App />"]]
+```js [[1, 3, "<App />"], [2, 3, "document.getElementById('root')"]]
 import {hydrate} from 'react-dom';
 
 hydrate(<App />, document.getElementById('root'));
diff --git a/beta/src/content/reference/react/Profiler.md b/beta/src/content/reference/react/Profiler.md
@@ -54,7 +54,7 @@ function onRender(id, phase, actualDuration, baseDuration, startTime, commitTime
 #### Parameters {/*onrender-parameters*/}
 
 * `id`: The string `id` prop of the `<Profiler>` tree that has just committed. This lets you identify which part of the tree was committed if you are using multiple profilers.
-* `phase`: Either `"mount"` or `"update"`. This lets you know whether the tree has just been mounted for the first time or re-rendered due to a change in props, state, or hooks.
+* `phase`: `"mount"`, `"update"` or `"nested-update"`. This lets you know whether the tree has just been mounted for the first time or re-rendered due to a change in props, state, or hooks.
 * `actualDuration`: The number of milliseconds spent rendering the `<Profiler>` and its descendants for the current update. This indicates how well the subtree makes use of memoization (e.g. [`memo`](/reference/react/memo) and [`useMemo`](/reference/react/useMemo)). Ideally this value should decrease significantly after the initial mount as many of the descendants will only need to re-render if their specific props change.
 * `baseDuration`: The number of milliseconds estimating how much time it would take to re-render the entire `<Profiler>` subtree without any optimizations. It is calculated by summing up the most recent render durations of each component in the tree. This value estimates a worst-case cost of rendering (e.g. the initial mount or a tree with no memoization). Compare `actualDuration` against it to see if memoization is working.
 * `startTime`: A numeric timestamp for when React began rendering the current update.
diff --git a/beta/src/content/reference/react/useMemo.md b/beta/src/content/reference/react/useMemo.md
@@ -633,7 +633,7 @@ Un nodo de JSX como `<List items={visibleTodos} />` es un objeto como `{ type: L
 
 Sin embargo, si React ve exactamente el mismo JSX que durante el renderizado anterior, no intentará volver a renderizar tu componente. Esto se debe a que los nodos JSX son [inmutables.](https://es.wikipedia.org/wiki/Objeto_inmutable) Un objeto de nodo JSX no podría haber cambiado con el tiempo, por lo que React sabe que es seguro omitir un nuevo renderizado. Sin embargo, para que esto funcione, el nodo tiene que *ser realmente el mismo objeto*, no simplemente tener el mismo aspecto en el código. Esto es lo que hace `useMemo` en este ejemplo.
 
-Envolver manualmente los nodos JSX en `useMemo` no es conveniente. Por ejemplo, no puedes hacerlo condicionalmente. Es por esto que lo común es envolver los componentes con [`memo`](/reference/react/memo) en lugar de envolver los nodos de JSX.
+Envolver manualmente los nodos JSX en `useMemo` no es conveniente. Por ejemplo, no puedes hacerlo condicionalmente. Comúnmente es por esto que se envuelven los componentes con [`memo`](/reference/react/memo) en lugar de envolver los nodos de JSX.
 
 </DeepDive>
 
diff --git a/content/community/conferences.md b/content/community/conferences.md
@@ -52,6 +52,16 @@ June 27th, 2023. Tel Aviv, Israel
 
 [Website](https://www.react-next.com/) - [Facebook](https://www.facebook.com/ReactNextConf) - [Youtube](https://www.youtube.com/@ReactNext)
 
+### React Nexus 2023 {#react-nexus-2023}
+July 07 & 08, 2023. In-person in Bangalore, India
+
+[Website](https://reactnexus.com/) - [Twitter](https://twitter.com/ReactNexus) - [Linkedin](https://www.linkedin.com/company/react-nexus) - [YouTube](https://www.youtube.com/reactify_in)
+
+### React India 2023 {#react-india-2023}
+Oct 5 - 7, 2023. In-person in Goa, India (hybrid event) + Oct 3 2023 - remote day 
+
+[Website](https://www.reactindia.io) - [Twitter](https://twitter.com/react_india) - [Facebook](https://www.facebook.com/ReactJSIndia) - [Youtube](https://www.youtube.com/channel/UCaFbHCBkPvVv1bWs_jwYt3w)
+
 ## Past Conferences {#past-conferences}
 
 ### React Advanced 2022 {#react-advanced-2022}
