docs(api): avoid headings in decorators

[petebacondarwin]

The Component decorator has headings in the content for individual members of the "component interface" which do not render nicely and confuse the table of contents. See https://next.angular.io/api/core/Component#simple-example

[jenniferfell]

Can we disallow H2 H3 etc in API reference markup everywhere? In other words, all headings are ones that are generated based on appropriate dgeni tagging or the generation tools?

Can we disallow H2 H3 etc in tables? If the generator finds something that would be a heading inside a table, then it makes that text just bold on its own line?

Either of those would fix the TOC for existing content.

Longer term, obviously, a rewrite of this kind of content the complete answer, but I know we have content to migrate that might have done this.

[jenniferfell]

Update from Judy: Headers should only be allowed in Usage Notes, and it should only be H3 or lower

[petebacondarwin]

I will implement a check for this.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}