Merge branch 'main' into renovate/pnpm-11.x

Author: kodiakhq[bot]

src/routes/(0)concepts/(1)control-flow/(0)conditional-rendering.mdx

@@ -25,7 +25,7 @@ Solid offers dedicated components to handle conditional rendering in a more stra
 
 ## Show
 
-`<Show>` renders its children when a condition is evaluated to be true.
+[`<Show>`](/reference/components/show) renders its children when a condition is evaluated to be true.
 Similar to the [ternary operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Conditional_Operator) in JavaScript, it uses control logic flow within JSX to determine what to render.
 
 `<Show>` has a `when` property that is used to determine whether or not to render its children.

src/routes/(0)concepts/(1)control-flow/(1)list-rendering.mdx

@@ -21,7 +21,7 @@ description: >-
 
 List rendering allows you to generate multiple elements from a collection of data, such as an array or object, where each element corresponds to an item in the collection.
 
-When dealing with dynamic data, Solid offers two ways to render lists: the `<For>` and `<Index>` components.
+When dealing with dynamic data, Solid offers two ways to render lists: the [`<For>`](/reference/components/for) and `<Index>` components.
 Both of these components help you loop over data collections to generate elements, however, they both cater to different scenarios.
 
 ## `<For>`

src/routes/(0)concepts/(1)control-flow/(2)dynamic.mdx

@@ -18,7 +18,7 @@ description: >-
   flexible UIs with runtime component selection.
 ---
 
-`<Dynamic>` is a Solid component that allows you to render components dynamically based on data.
+[`<Dynamic>`](/reference/components/dynamic) is a Solid component that allows you to render components dynamically based on data.
 By passing either a string representing a [native HTML element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element) or a component function to the `component` prop, you can render the chosen component with the remaining props you provide.
 
 ```jsx

src/routes/(0)concepts/(1)control-flow/(4)portal.mdx

@@ -19,7 +19,7 @@ description: >-
 ---
 
 When an element requires rendering outside of the usual document flow, challenges related to stacking contents and z-index can interfere with the desired intention or look of an application.
-`<Portal>` helps with this by putting elements in a different place in the document, bringing an element into the document flow so they can render as expected.
+[`<Portal>`](/reference/components/portal) helps with this by putting elements in a different place in the document, bringing an element into the document flow so they can render as expected.
 
 ```jsx
 import { Portal } from "solid-js/web";

src/routes/reference/lifecycle/on-mount.mdx

@@ -52,6 +52,14 @@ Non-tracking function executed once on mount.
 - By the time `onMount` runs, refs have already been assigned.
 - Returning a function from `fn` does not register cleanup. Use [`onCleanup`](/reference/lifecycle/on-cleanup) inside `onMount` when cleanup is needed.
 
+:::note
+"Mounted" in Solid refers to when a component is rendered within the reactive tree, not when it is physically inserted into the DOM.
+If you store JSX in a variable before conditionally rendering it, `onMount` runs when that JSX is evaluated, even if the elements have not yet been added to the visible page.
+Similarly, [`onCleanup`](/reference/lifecycle/on-cleanup) runs based on the reactive ownership tree rather than DOM removal.
+
+For cases where you need to detect actual DOM insertion or removal, consider using a [`ref`](/concepts/refs) callback or the [Lifecycle primitives from solid-primitives](https://github.com/solidjs-community/solid-primitives/tree/main/packages/lifecycle).
+:::
+
 ## Examples
 
 ### Access a ref after mount