Clauses are referenced using their id and are numbered automatically based on document position. Ecmarkdown syntax can be used in descendent text nodes as well. Text nodes are parsed as Ecmarkdown Fragments.
+Clauses are referenced using their id and are numbered automatically based on document position. Ecmarkdown syntax can be used in descendent text nodes as well. Text nodes are parsed as Ecmarkdown Fragments. Clauses always begin with an `<h1>` element.
+ +This clause is normative optional.
Ecmarkup produces special formatting behaviour for an `<emu-clause>` with an ID ending in `terms-and-definitions`. No action is required on an editor's part to properly format that clause as long as it uses similar markup to any other clause, i.e. an `<h1>` element followed by one or more `<p>` or `<emu-clause>` elements.
+Using a `<dfn>` element in the clause title is optional, and will allow ecmarkup to link back to the term anywhere it is used in the rest of the document. See
+ <emu-clause id="sec-terms-and-definitions">
+ <h1>Terms and definitions</h1>
+ <emu-clause id="term-technical-definition">
+ <h1>technical definition</h1>
+ <p>descriptive text aligning with Ecma house style, providing text that could be swapped in for the term without impacting readability</p>
+ </emu-clause>
+ <emu-clause id="term-ecma">
+ <h1><dfn>Ecma International</dfn></h1>
+ <p>international standards organization responsible for technology-related standards since 1959</p>
+ </emu-clause>
+ </emu-clause>
+
+ Terms can be defined using the `<dfn>` element. Any uses of that term will be automatically linked to the clause containing the definition, or, if the `<dfn>` element has an `id`, to the `<dfn>` itself. This can be suppressed with the `emu-not-ref` element.
+Terms can be defined inline using the `<dfn>` element. Any uses of that term will be automatically linked to the clause containing the definition, or, if the `<dfn>` element has an `id`, to the `<dfn>` itself. This can be suppressed with the `emu-not-ref` element.
When the term starts with a lowercase English letter, usages of the term with the first letter capitalized will also link.
Create a code listing using `<pre><code>`. The `code` element takes a class of `javascript`, `html`, or any other language provided by highlightjs. Ecmarkup will trim any leading blank lines and also normalize the indentation based on the indentation of the first line.
Ecmarkup supports producing a document aligned with Ecma house style. If the ecmarkup document is intended to be formally released by Ecma International, there are some structural requirements it shall follow.
+Each `<emu-intro>`, `<emu-clause>`, and `<emu-annex>` element shall have a unique ID, optionally beginning with the prefix `sec-`.
+ +This section is a work in progress.
+Ecma technical reports begin with an unnumbered introduction (using a single `<emu-intro>` element), then the following numbered clauses:
+ +(Refer to the Ecma house style guide for more detailed information.)
+This section is a work in progress.
+Ecma standards conforming to Ecma house style begin with an unnumbered introduction clause (using a single `<emu-intro>` element), followed by the following numbered clauses:
+ +(Refer to the Ecma house style guide for more detailed information.)
+