chore: typo in core concepts docs (#725)

svenweb · web-flow · commit 0bac19d9c57c · 2025-02-05T16:43:09.000+08:00
diff --git a/site/docs/concepts/user-components.md b/site/docs/concepts/user-components.md
@@ -156,7 +156,7 @@ Text.craft = {
 
 
 ## Related Components
-What happens if you need to design some component to complement our  user component? For instance, if we were planning on building a Toolbar somewhere in our page editor, we would like the Toolbar to display a bunch of text inputs to allow the user the edit the currently selected component. It would be great if we could retrieve a specific component that has all the relevant inputs for the user to edit the currently selected component.
+What happens if you need to design some component to complement our  user component? For instance, if we were planning on building a Toolbar somewhere in our page editor, we would like the Toolbar to display a bunch of text inputs to allow the user to edit the currently selected component. It would be great if we could retrieve a specific component that has all the relevant inputs for the user to edit the currently selected component.
 
 
 This is where related components become useful. These components share the same corresponding `Node` as the actual user component, hence the `useNode` hook that we have been using all this while will be made available to these components as well. 
@@ -351,4 +351,4 @@ const Container = ({background, title, children}) => {
   }
 }
 ```
--->
+-->

Original file line number	Diff line number	Diff line change
`@@ -156,7 +156,7 @@ Text.craft = {`
`156`	`156`
`157`	`157`
`158`	`158`	`## Related Components`
`159`		`-What happens if you need to design some component to complement our user component? For instance, if we were planning on building a Toolbar somewhere in our page editor, we would like the Toolbar to display a bunch of text inputs to allow the user the edit the currently selected component. It would be great if we could retrieve a specific component that has all the relevant inputs for the user to edit the currently selected component.`
	`159`	`+What happens if you need to design some component to complement our user component? For instance, if we were planning on building a Toolbar somewhere in our page editor, we would like the Toolbar to display a bunch of text inputs to allow the user to edit the currently selected component. It would be great if we could retrieve a specific component that has all the relevant inputs for the user to edit the currently selected component.`
`160`	`160`
`161`	`161`
`162`	`162`	This is where related components become useful. These components share the same corresponding `Node` as the actual user component, hence the `useNode` hook that we have been using all this while will be made available to these components as well.
`@@ -351,4 +351,4 @@ const Container = ({background, title, children}) => {`
`351`	`351`	`}`
`352`	`352`	`}`
`353`	`353`	```
`354`		`--->`
	`354`	`+-->`