From d75055e1deaa8fe8c1c84b32dbe295b02a6ccbe6 Mon Sep 17 00:00:00 2001
From: mizulu <202852165+mizulu@users.noreply.github.com>
Date: Sun, 10 May 2026 11:21:25 -0400
Subject: [PATCH 1/3] Clarify prop drilling and introduce Context API

Refine explanation of prop drilling and introduce Solid's Context API as a solution for managing state across nested components.
---
 src/routes/(0)concepts/(0)components/(2)props.mdx | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/src/routes/(0)concepts/(0)components/(2)props.mdx b/src/routes/(0)concepts/(0)components/(2)props.mdx
index bba5be4dbf..d76d265387 100644
--- a/src/routes/(0)concepts/(0)components/(2)props.mdx
+++ b/src/routes/(0)concepts/(0)components/(2)props.mdx
@@ -127,11 +127,9 @@ function ColoredList(props) {
 
 ## Prop drilling
 
-Prop drilling is a term used to describe the process of passing props through multiple layers of components.
-While it can be a useful pattern, it can also lead to problems.
-When components are nested deeply, passing props through each component can become difficult to manage.
-Additionally, this can lead to components receiving props that they do not need, unnecessary re-renders, and trouble refactoring.
-
-Since components in Solid do not own state, props are not needed to pass state between components, but may be used.
-Because of this, there may be times when you need to pass props through multiple layers of components.
-A common solution to this problem is to use [Context](/concepts/context) to pass state to deeply nested components without having to pass props through each component in between.
+Prop drilling refers to passing props through multiple layers of components.
+While this is a valid pattern, it can become cumbersome in larger component trees, especially when intermediate components receive values they do not directly use.
+
+When multiple components across different levels need access to the same data, Solid’s [Context](/concepts/context) API provides a cleaner alternative. [Context](/concepts/context) allows you to supply values to deeply nested components without manually threading props through each layer.
+
+

From b7b150dceb8a602a8a269e02057b089b852dfead Mon Sep 17 00:00:00 2001
From: "autofix-ci[bot]" <114827586+autofix-ci[bot]@users.noreply.github.com>
Date: Sun, 10 May 2026 15:26:35 +0000
Subject: [PATCH 2/3] ci: apply automated fixes

---
 src/routes/(0)concepts/(0)components/(2)props.mdx | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/routes/(0)concepts/(0)components/(2)props.mdx b/src/routes/(0)concepts/(0)components/(2)props.mdx
index d76d265387..8eab479e9b 100644
--- a/src/routes/(0)concepts/(0)components/(2)props.mdx
+++ b/src/routes/(0)concepts/(0)components/(2)props.mdx
@@ -131,5 +131,3 @@ Prop drilling refers to passing props through multiple layers of components.
 While this is a valid pattern, it can become cumbersome in larger component trees, especially when intermediate components receive values they do not directly use.
 
 When multiple components across different levels need access to the same data, Solid’s [Context](/concepts/context) API provides a cleaner alternative. [Context](/concepts/context) allows you to supply values to deeply nested components without manually threading props through each layer.
-
-

From 4f209f5f486f0aed6b4e68c86e85918d650a2a76 Mon Sep 17 00:00:00 2001
From: mizulu <202852165+mizulu@users.noreply.github.com>
Date: Sun, 10 May 2026 12:26:51 -0400
Subject: [PATCH 3/3] Update src/routes/(0)concepts/(0)components/(2)props.mdx

unpack "cumbersome"  with
"cluttered and confusing"
---
 src/routes/(0)concepts/(0)components/(2)props.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/routes/(0)concepts/(0)components/(2)props.mdx b/src/routes/(0)concepts/(0)components/(2)props.mdx
index 8eab479e9b..4e8f892eff 100644
--- a/src/routes/(0)concepts/(0)components/(2)props.mdx
+++ b/src/routes/(0)concepts/(0)components/(2)props.mdx
@@ -128,6 +128,7 @@ function ColoredList(props) {
 ## Prop drilling
 
 Prop drilling refers to passing props through multiple layers of components.
-While this is a valid pattern, it can become cumbersome in larger component trees, especially when intermediate components receive values they do not directly use.
+While this is a valid pattern, it can cause props to become cluttered and confusing
+in larger component trees, especially when intermediate components receive values they do not directly use.
 
 When multiple components across different levels need access to the same data, Solid’s [Context](/concepts/context) API provides a cleaner alternative. [Context](/concepts/context) allows you to supply values to deeply nested components without manually threading props through each layer.