HOC in the example is not pure function with zero side effects?

To me the statement on https://github.com/reactjs/reactjs.org/blob/master/content/docs/higher-order-components.md appear to be untrue:
A HOC is a pure function with zero side-effects.
where just above the HOC is returning container that surely has side effects: mutation of state:

// This function takes a component...
function withSubscription(WrappedComponent, selectData) {
  // ...and returns another component...
  return class extends React.Component {
    constructor(props) {
      super(props);
      this.handleChange = this.handleChange.bind(this);
      this.state = {
        data: selectData(DataSource, props)
      };
    }

    componentDidMount() {
      // ... that takes care of the subscription...
      DataSource.addChangeListener(this.handleChange);
    }

    componentWillUnmount() {
      DataSource.removeChangeListener(this.handleChange);
    }

    handleChange() {
      this.setState({
        data: selectData(DataSource, this.props)
      });
    }

    render() {
      // ... and renders the wrapped component with the fresh data!
      // Notice that we pass through any additional props
      return <WrappedComponent data={this.state.data} {...this.props} />;
    }
  };
}

Do you agree?

Start with content/docs/higher-order-components.md at the statement that a HOC is a pure function with zero side-effects and compare it with the included withSubscription example. Review the surrounding explanation and the five-comment discussion, then clarify the wording so the statement and example are consistent. Done means the documentation accurately describes the side effects shown by the example.