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 的說明準確時即完成。