Clarify prop drilling and introduce Context API (#1510)

* 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.

* ci: apply automated fixes

* Update src/routes/(0)concepts/(0)components/(2)props.mdx

unpack "cumbersome"  with
"cluttered and confusing"

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

Author: mizulu

src/routes/(0)concepts/(0)components/(2)props.mdx

@@ -127,11 +127,8 @@ 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 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.