update

Author: amirhhashemi

src/routes/reference/basic-reactivity/create-effect.mdx

@@ -17,19 +17,21 @@ description: >-
 ---
 
 The `createEffect` primitive creates a reactive computation.
-It automatically tracks reactive values, such as signals, that are accessed within the provided function.
-This function re-runs whenever any of its dependencies change.
+It automatically tracks reactive values, such as [signals](/concepts/signals), that are accessed within the provided function.
+This function will re-run whenever any of its dependencies change.
 
 ## Execution Timing
 
-- The initial run of an effect is scheduled to run **after the current rendering phase completes**.
-  - This means it runs after all synchronous code in a component has been executed and the DOM elements have been created, but **before the browser paints them to the screen**.
-  - As a result, [refs](/concepts/refs) **are set** before the effect runs for the first time, even though the DOM nodes may **not be attached to the main document tree**.
-    This is particularly relevant when using [`children`](/reference/component-apis/children).
-- If multiple dependencies are updated within the same batch, the effect only runs once.
-- Effects always run **after** any pure computations (like [memos](/concepts/derived-values/memos)) in the same update cycle.
+- The initial execution of an effect is scheduled to occur **after the current rendering phase completes**.
+  This means it runs after all synchronous code in a component has executed and the DOM elements have been created, but **before the browser renders them on the screen**.
+
+  As a result, [refs](/concepts/refs) **are set** before the effect runs for the first time, even though the DOM nodes may **not be attached to the main document tree**.
+  This is particularly relevant when using the [`children`](/reference/component-apis/children) function.
+
 - The order in which effects run is **not guaranteed**.
-- Effects are **not run** during Server-Side Rendering (SSR) or the initial client hydration.
+- When multiple dependencies are updated within the same batch, the effect will only run once.
+- Effects always run **after** any pure computations (such as [memos](/concepts/derived-values/memos)) within the same update cycle.
+- Effects **are not executed** during Server-Side Rendering (SSR) or during the initial client hydration.
 
 ## Import
 
@@ -62,16 +64,16 @@ function createEffect<Next, Init>(
 - **Type:** `EffectFunction<undefined | NoInfer<Next> | EffectFunction<Init | Next, Next>`
 - **Required:** Yes
 
-The function to run.
-It receives the value returned from the previous run, or the initial `value` on the first run.
-The value it returns is passed to the next run.
+The function to execute as the effect.
+It receives the value returned from the previous execution, or the initial `value` during its first run.
+The value returned by this function will be passed to the next execution.
 
 ### `value`
 
 - **Type:** `Init`
 - **Required:** No
 
-The initial value passed to `fn` on its first run.
+The initial value that is passed to `fn` during its first execution.
 
 ### `options`
 
@@ -85,7 +87,7 @@ An optional configuration object with the following properties:
 - **Type:** `string`
 - **Required:** No
 
-A name for the effect, used for identification in debugging tools like [Solid Debugger](https://github.com/thetarnav/solid-devtools).
+A name for the effect, which can be useful for identification in debugging tools like the [Solid Debugger](https://github.com/thetarnav/solid-devtools).
 
 ## Return value
 

src/routes/reference/secondary-primitives/create-render-effect.mdx

@@ -10,27 +10,27 @@ tags:
   - immediate
   - refs
   - lifecycle
-version: '1.0'
+version: "1.0"
 description: >-
   Execute effects immediately during rendering with createRenderEffect. Run side
   effects as DOM creates, before refs are set or connected.
 ---
 
-The `createRenderEffect` primitive creates a reactive computation.
-It automatically tracks reactive values, such as signals, that are accessed within the provided function.
+The `createRenderEffect` primitive creates a reactive computation that automatically tracks reactive values, such as signals, accessed within the provided function.
 This function re-runs whenever any of its dependencies change.
 
-Unlike [`createEffect`](/reference/basic-reactivity/create-effect), which runs after the rendering phase is complete, `createRenderEffect` runs immediately as the component is being rendered.
+In contrast to [`createEffect`](/reference/basic-reactivity/create-effect), which executes after the rendering phase is complete, `createRenderEffect` runs immediately during the component's rendering phase.
 
 ## Execution Timing
 
-- The initial run of a render effect happens during the current rendering phase.
-- It runs as DOM elements are being created and updated, but before they are mounted.
-  As a result, refs are _not_ set before a render effect runs for the first time.
-- If multiple dependencies are updated within the same batch, the render effect only runs once.
-- Effects always run after any pure computations (like [memos](/concepts/derived-values/memos)) in the same update cycle.
-- The order in which render effects run is not guaranteed.
-- Render effects are not run during Server-Side Rendering (SSR).
+- The initial execution of a render effect occurs **during the current rendering phase**.
+  It runs while DOM elements are being created and updated, but **before they are mounted**.
+
+  As a result, refs are **not set** before the render effect runs for the first time.
+
+- After the initial run, the order in which render effects run is **not guaranteed**.
+- If multiple dependencies are updated within the same batch, the render effect runs only once.
+- Render effects always run **after** any pure computations (such as [memos](/concepts/derived-values/memos)) within the same update cycle.
 
 ## Import
 
@@ -63,16 +63,16 @@ function createRenderEffect<Next, Init>(
 - **Type:** `EffectFunction<undefined | NoInfer<Next> | EffectFunction<Init | Next, Next>`
 - **Required:** Yes
 
-The function to run.
-It receives the value returned from the previous run, or the initial `value` on the first run.
-The value it returns is passed to the next run.
+The function to execute as the render effect.
+It receives the value returned from the previous execution, or the initial `value` during its the first run.
+The value returned by this function will be passed to the next execution.
 
 ### `value`
 
 - **Type:** `Init`
 - **Required:** No
 
-The initial value passed to `fn` on its first run.
+The initial value that is passed to `fn` during its first execution.
 
 ### `options`
 
@@ -86,7 +86,7 @@ An optional configuration object with the following properties:
 - **Type:** `string`
 - **Required:** No
 
-A name for the render effect, used for identification in debugging tools like [Solid Debugger](https://github.com/thetarnav/solid-devtools).
+A name for the render effect, which can be useful for identification in debugging tools like the [Solid Debugger](https://github.com/thetarnav/solid-devtools).
 
 ## Return value