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 
ExecutionEnvironment = require('ExecutionEnvironment');
  require('ReactFeatureFlags').disableNewFiberFeatures = false;
  PropTypes = require('prop-types');
  React = require('react');
  ReactDOM = require('react-dom');
  ReactDOMFeatureFlags = require('ReactDOMFeatureFlags');
  ReactTestUtils = require('react-dom/test-utils');
  
  
  
  jest.resetModuleRegistry();
  if (typeof onAfterResetModules === 'function') {
    onAfterResetModules();
  }
  require('ReactFeatureFlags').disableNewFiberFeatures = false;
  ReactDOMServer = require('react-dom/server');
}
describe('ReactDOMServerIntegration', () => {
  beforeEach(() => {
    resetModules();
    ExecutionEnvironment.canUseDOM = false;
  });
  describe('basic rendering', function() {
    itRenders('a blank div', async render => {
      const e = await render(<div />);
      expect(e.tagName).toBe('DIV');
    });
    itRenders('a self-closing tag', async render => {
      const e = await render(<br />);
      expect(e.tagName).toBe('BR');