Ecma has some rules on how standards should be structured: TOOLS-013-1.pdf
This PR:
Adds the Introduction to the TOC, but withuot a number (see 6.1.4)
Makes "Scope" the first normative section of the spec, describing what the spec covers (see 6.2.1)
Renamed "Terminology" to "Terms and definitions (see 6.3.1), and used the bikeshed syntax for definition lists.
Similarly to how it's done in the ECMAScript spec, I added an "About this Specification" section at the beginning that basically says "the online document is the most up-to-date version".
I moved the license at the end, like the ECMAScript spec does.
Ecma has some rules on how standards should be structured: TOOLS-013-1.pdf
This PR: