With the checkin of #10362, the code to render to a stream now looks like:

```
import { renderToStream } from 'react-dom/server'

renderToStream(<div>some text</div>).pipe(response);
```

This is great! I am, however, a little concerned about taking the word "node" out of the mix, because I'm thinking that we may eventually want to render to [**browser** streams](https://www.w3.org/TR/streams-api/), which are a really neat feature that can be used in concert with "service-worker-side rendering". I would propose renaming `renderToStream` to `renderToNodeStream` and `renderToStaticStream` to `renderToStaticNodeStream`.  This would give room for `renderToBrowserStream` in the future.

If I make a PR on this, would it have a chance of being accepted? 

cc @gaearon & @sebmarkbage 
expectTextNode(e.childNodes[4], ' ');
          } else {
            expect(e.childNodes.length).toBe(3);
            expectTextNode(e.childNodes[0], ' ');
            expectTextNode(e.childNodes[1], ' ');
            expectTextNode(e.childNodes[2], ' ');
          }
        } else {
          
          
          expect(e.childNodes.length).toBe(9);
          expectTextNode(e.childNodes[0], ' ');
          expectTextNode(e.childNodes[3], ' ');
          expectTextNode(e.childNodes[6], ' ');
        }
      });
      itRenders('a div with text sibling to a node', async render => {
        const e = await render(<div>Text<span>More Text</span></div>);
        let spanNode;
        if (ReactDOMFeatureFlags.useFiber) {
          
          
          expect(e.childNodes.length).toBe(2);
          spanNode = e.childNodes[1];
        } else {
          
          
          expect(e.childNodes.length).toBe(4);
          spanNode = e.childNodes[3];
        }