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)

Comece pela página “Lifting State Up” em reactjs.org/docs/lifting-state-up.html e analise como callback props se relacionam com as orientações apresentadas nela. Avalie as três preocupações listadas no issue e determine se uma observação precisa deve ser incluída na página. Considera-se concluído quando a documentação inclui uma explicação clara e tecnicamente fundamentada ou quando a adição proposta no issue é recusada com justificativa.