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 
});
    itRenders('a self-closing tag as a child', async render => {
      const e = await render(<div><br /></div>);
      expect(e.childNodes.length).toBe(1);
      expect(e.firstChild.tagName).toBe('BR');
    });
    if (ReactDOMFeatureFlags.useFiber) {
      itRenders('a string', async render => {
        let e = await render('Hello');
        expect(e.nodeType).toBe(3);
        expect(e.nodeValue).toMatch('Hello');
      });
      itRenders('a number', async render => {
        let e = await render(42);
        expect(e.nodeType).toBe(3);
        expect(e.nodeValue).toMatch('42');
      });
      itRenders('an array with one child', async render => {
        let e = await render([<div key={1}>text1</div>]);
        let parent = e.parentNode;
        expect(parent.childNodes[0].tagName).toBe('DIV');
      });
      itRenders('an array with several children', async render => {
        let Header = props => {
          return <p>header</p>;
        };
        let Footer = props => {
          return [<h2 key={1}>footer</h2>, <h3 key={2}>about</h3>];
        };
        let e = await render([