Angular: In Lifecycle Hooks docs, it's not clear that ngOnChanges is not called when inputs are not used

I'm submitting a...

[x] Documentation issue or request

Current behavior

Lifecycle Hooks page says this about ngOnChanges():

called before ngOnInit() and whenever one or more data-bound input properties change

and this about ngOnInit():

called [...] after the first ngOnChanges()

It's not clear from that description that ngOnChanges() will _not_ be called if the component is used _without_ providing any inputs.

Expected behavior

Documentation should be more clear about ngOnChanges() behavior: specifically, if a component has inputs declared but they are not used, then ngOnChanges() will _not_ be called before ngOnInit()

Minimal reproduction of the problem with instructions

https://stackblitz.com/edit/angular-ngonchanges

What is the motivation / use case for changing the behavior?

Judging from the of the docs, one may have an impression that ngOnChanges() will always be called first before ngOnInit() for a component with inputs, even if those inputs are not used by parent template/component.

This may lead to not-so-obvious accidental errors, such as removing ngOnInit() if it duplicates start-up logic of a component from ngOnChanges().