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 
render() {
              return {x: 123};
            }
          }
          await render(<ObjectComponent />, 1);
        },
        ReactDOMFeatureFlags.useFiber
          ? 'Objects are not valid as a React child (found: object with keys ' +
              '{x}). If you meant to render a collection of children, use ' +
              'an array instead.'
          : 'A valid React element (or null) must be returned. ' +
              'You may have returned undefined, an array or some other invalid object.',
      );
      itThrowsWhenRendering(
        'top-level object',
        async render => {
          await render({x: 123});
        },
        ReactDOMFeatureFlags.useFiber
          ? 'Objects are not valid as a React child (found: object with keys ' +
              '{x}). If you meant to render a collection of children, use ' +
              'an array instead.'