update

Author: amirhhashemi

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

@@ -17,19 +17,20 @@ description: >-
 ---
 
 The `createEffect` primitive creates a reactive computation.
-It automatically tracks reactive values, such as [signals](/concepts/signals), that are accessed within the provided function.
+It automatically tracks reactive values, such as [signals](/concepts/signals), accessed within the provided function.
 This function will re-run whenever any of its dependencies change.
 
 ## Execution Timing
 
-- 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**.
+- The initial execution of effects is scheduled to occur **after the current rendering phase completes**.
+  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.
 
+- After the initial execution, effects will re-run whenever any of their dependencies change.
+  When multiple dependencies are updated within the same batch, the effect will only run once.
 - The order in which effects run is **not guaranteed**.
-- 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.
 
@@ -103,7 +104,7 @@ import { createSignal, createEffect } from "solid-js";
 function Counter() {
 	const [count, setCount] = createSignal(0);
 
-	// Every time count changes this effect re-runs.
+	// Every time count changes, this effect re-runs.
 	createEffect(() => {
 		console.log("Count incremented! New value: ", count());
 	});

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

@@ -16,20 +16,22 @@ description: >-
   effects as DOM creates, before refs are set or connected.
 ---
 
-The `createRenderEffect` primitive creates a reactive computation that automatically tracks reactive values, such as signals, accessed within the provided function.
+The `createRenderEffect` primitive creates a reactive computation that automatically tracks reactive values, such as [signals](/concepts/signals), accessed within the provided function.
 This function re-runs whenever any of its dependencies change.
 
-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 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**.
+- The initial execution of render effects occurs **during the current rendering phase**.
+  It runs synchronously 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**.
-- When multiple dependencies are updated within the same batch, the render effect will only run once.
+- After the initial execution, render effects will re-run whenever any of their dependencies change.
+
+  The order in which render effects re-run is **not guaranteed**.
+
+  When multiple dependencies are updated within the same batch, the render effect will only run once.
+
 - Render effects always run **after** any pure computations (such as [memos](/concepts/derived-values/memos)) within the same update cycle.
 
 ## Import