The page is discussing the fact that these tags are obsolete and in doing so also uses the obsolete tags themselves to demonstrate their usage. This means that this page will show up in the linter.
It might be preferable to either replace those obsolete tags with Templatestyles, inline styling, or simply use screenshots because if / when these tags do become obsolete the rendering here will not show things as intended in certain browsers.
Actually I had knowingly decided to use them in a first time in order to compare and prove their rendering with their alternatives, in a dynamic way which a screenshot could not provide.
So to my mind these examples are not "ironic" but a relic to treat at the very end of the migration process they describe.
Well, that's counter intuitive, it is like a doctors telling a patient that smoking is bad for them while they actually smoke in front of the patient (and make the patient worse). A documentation that talks about good practices should avoid bad practices while doing it, because it encourages the reader to simply ignore such contradiction or simply believe that its authors are either lying or don't know what they are talking about.
It is likely that people already have a hard time believing that doing something like this is worth their time as the prior thread shows. Including such "live" examples will likely make matters worse.
