Why don't we mention the concept of callBack props in the 'Lifting State Up' page?

There are times the source of the detailed or complete data is best isolated in a child component rather than trying to lift the state up and creating large parent component. The large parent component that has all the state, goes against the concepts of code isolation and separation of concerns,

Given this, why not add a note to https://reactjs.org/docs/lifting-state-up.html that talks about callback props?
There are 3 issues i'm aware of with callback props:

1. that warning that the parent component is still rendering: solution: launch the event handler code asynchronously
   2): In async functions, after await(), we should check whether the component is still mounted.
   3): whenever a function is passed as a prop it must be frozen and then only added to the useEffect() dependency chain (better to add all dependencies for useEffect rather than ignore the warning)

從 reactjs.org/docs/lifting-state-up.html 的「Lifting State Up」頁面開始，檢視 callback props 與其中指引的關係。評估 issue 中列出的三項疑慮，並判斷頁面是否應加入準確的說明。完成的標準是：文件包含清楚且有技術依據的解釋，或是有理由地拒絕 issue 中提出的新增內容。