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.

Öffne den Abschnitt „Approach 1“ in der verlinkten Suspense-Dokumentation und vergleiche dessen Beschreibung von componentDidMount mit der Klarstellung in issue #9117. Aktualisiere die Formulierung so, dass das Mounten in einen DOM-Knoten nicht damit gleichgesetzt wird, an das Dokument angehängt oder auf dem Bildschirm sichtbar zu sein; die Arbeit ist erledigt, wenn die Erklärung von fetch-on-render korrekt ist.