Suspense documentation incorrectly conflates `componentDidMount` with "component has rendered on the screen"

In the "Approach 1" section:

We call this approach “fetch-on-render” because it doesn’t start fetching until after the component has rendered on the screen. This leads to a problem known as a “waterfall”.

However, @gaearon has previously clarified out that componentDidMount only guarantees that the React tree has been mounted onto a DOM node, not that that DOM node is attached to the document/visible on screen: https://github.com/facebook/react/issues/9117#issuecomment-284228870

The componentDidMount would fire because the mounting has happened. However, as you can see, the div I’m mounting into is not actually part of the page’s DOM. Therefore, the component’s DOM node is also not in the document even though it has mounted into its container.

打开链接的 Suspense 文档中的“Approach 1”部分，并将其中对 componentDidMount 的描述与 issue #9117 中的澄清进行比较。更新措辞，使挂载到 DOM 节点不再等同于附加到文档或在屏幕上可见；当 fetch-on-render 的说明准确时即完成。