rename orchestrates to calls

Author: poteto

src/content/reference/react/index.md

@@ -15,7 +15,7 @@ The React reference documentation is broken down into functional subsections:
 React has idioms — or rules — for how to express patterns in a way that is easy to understand and yields high-quality applications:
 
 * [Components and Hooks must be pure](/reference/rules/components-and-hooks-must-be-pure) – Purity makes your code easier to understand, debug, and allows React to automatically optimize your components and hooks correctly.
-* [React orchestrates Components and Hooks](/reference/rules/react-orchestrates-components-and-hooks) – React is responsible for rendering components and hooks when necessary to optimize the user experience.
+* [React calls Components and Hooks](/reference/rules/react-calls-components-and-hooks) – React is responsible for rendering components and hooks when necessary to optimize the user experience.
 * [Rules of Hooks](/reference/rules/rules-of-hooks) – Hooks are defined using JavaScript functions, but they represent a special type of reusable UI logic with restrictions on where they can be called.
 
 ## React {/*react*/}

src/content/reference/rules/index.md

@@ -42,12 +42,12 @@ The Rules of React are proven rules used at companies like Meta that help you ma
 
 ---
 
-## React orchestrates Components and Hooks {/*react-orchestrates-components-and-hooks*/}
+## React calls Components and Hooks {/*react-calls-components-and-hooks*/}
 
-[React is responsible for rendering components and hooks when necessary to optimize the user experience.](/reference/rules/react-orchestrates-components-and-hooks) It is declarative: you tell React what to render in your component’s logic, and React will figure out how best to display it to your user.
+[React is responsible for rendering components and hooks when necessary to optimize the user experience.](/reference/rules/react-calls-components-and-hooks) It is declarative: you tell React what to render in your component’s logic, and React will figure out how best to display it to your user.
 
-* [Never call component functions directly](/reference/rules/react-orchestrates-components-and-hooks#never-call-component-functions-directly) – Components should only be used in JSX. Don’t call them as regular functions.
-* [Never pass around hooks as regular values](/reference/rules/react-orchestrates-components-and-hooks#never-pass-around-hooks-as-regular-values) – Hooks should only be called inside of components. Never pass it around as a regular value.
+* [Never call component functions directly](/reference/rules/react-calls-components-and-hooks#never-call-component-functions-directly) – Components should only be used in JSX. Don’t call them as regular functions.
+* [Never pass around hooks as regular values](/reference/rules/react-calls-components-and-hooks#never-pass-around-hooks-as-regular-values) – Hooks should only be called inside of components. Never pass it around as a regular value.
 
 ---
 

src/content/reference/rules/react-orchestrates-components-and-hooks.md renamed to src/content/reference/rules/react-calls-components-and-hooks.md

@@ -1,5 +1,5 @@
 ---
-title: React orchestrates Components and Hooks
+title: React calls Components and Hooks
 ---
 
 <Intro>
@@ -11,9 +11,9 @@ React is responsible for rendering components and hooks when necessary to optimi
 ---
 
 ## Never call component functions directly {/*never-call-component-functions-directly*/}
-Components should only be used in JSX. Don't call them as regular functions.
+Components should only be used in JSX. Don't call them as regular functions. React should call it.
 
-React must decide when your component function is called during rendering. In React, you do this using JSX.
+React must decide when your component function is called [during rendering](/reference/rules/components-and-hooks-must-be-pure#how-does-react-run-your-code). In React, you do this using JSX.
 
 ```js {2}
 function BlogPost() {
@@ -27,7 +27,7 @@ function BlogPost() {
 }
 ```
 
-If a component contains hooks, it's easy to violate the Rules of Hooks when components are called directly in a loop or conditionally.
+If a component contains hooks, it's easy to violate the [Rules of Hooks](/reference/rules/rules-of-hooks) when components are called directly in a loop or conditionally.
 
 Letting React orchestrate rendering also allows a number of benefits:
 
@@ -39,7 +39,7 @@ Letting React orchestrate rendering also allows a number of benefits:
 
 ## Never pass around hooks as regular values {/*never-pass-around-hooks-as-regular-values*/}
 
-Hooks should only be called inside of components. Never pass it around as a regular value.
+Hooks should only be called inside of components or hooks. Never pass it around as a regular value.
 
 Hooks allow you to augment a component with React features. They should always be called as a function, and never passed around as a regular value. This enables _local reasoning_, or the ability for developers to understand everything a component can do by looking at that component in isolation.
 

src/content/reference/rules/rules-of-hooks.md

@@ -12,7 +12,7 @@ Hooks are defined using JavaScript functions, but they represent a special type
 
 ##  Only call Hooks at the top level {/*only-call-hooks-at-the-top-level*/}
 
-Don’t call Hooks inside loops, conditions, or nested functions. Instead, always use Hooks at the top level of your React function, before any early returns.
+Don’t call Hooks inside loops, conditions, nested functions, or in `try`/`catch`/`finally` blocks. Instead, always use Hooks at the **top level** of your React function, before any early returns.
 
 By following this rule, you ensure that Hooks are called in the same order each time a component renders. That’s what allows React to correctly preserve the state of Hooks between multiple `useState` and `useEffect` calls.
 
@@ -82,7 +82,7 @@ useState('Poppins')        // 🔴 2 (but was 3). Fail to read the surname state
 useEffect(updateTitle)     // 🔴 3 (but was 4). Fail to replace the effect
 ```
 
-React wouldn’t know what to return for the second useState Hook call. React expected that the second Hook call in this component corresponds to the persistForm effect, just like during the previous render, but it doesn’t anymore. From that point, every next Hook call after the one we skipped would also shift by one, leading to bugs.
+React wouldn’t know what to return for the second `useState` Hook call. React expected that the second Hook call in this component corresponds to the persistForm effect, just like during the previous render, but it doesn’t anymore. From that point, every next Hook call after the one we skipped would also shift by one, leading to bugs.
 
 This is why Hooks must be called on the top level of our components. If we want to run an effect conditionally, we can put that condition inside our Hook:
 

src/sidebarReference.json

@@ -11,8 +11,8 @@
           "path": "/reference/rules/components-and-hooks-must-be-pure"
         },
         {
-          "title": "React orchestrates Components and Hooks",
-          "path": "/reference/rules/react-orchestrates-components-and-hooks"
+          "title": "React calls Components and Hooks",
+          "path": "/reference/rules/react-calls-components-and-hooks"
         },
         {
           "title": "Rules of Hooks",