Skip to content

Commit 026fd7c

Browse files
committed
Update readme.
1 parent d2a3e9f commit 026fd7c

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

spec/index.html

+5-4
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,9 @@ <h1>Getting Started</h1>
2727
npm install -g ecmarkup
2828
ecmarkup spec.html out.html
2929
</pre>
30-
<p>It's likely you will want to use Ecmarkup's `elements.css` file as well, which is under the css folder in the Ecmarkup's root directory. You could also link to https://bterlson.github.io/ecmarkup/elements.css which will contain the latest styles for the forseeable future.</p>
30+
31+
<h2>Stylesheet</h2>
32+
<p>Styles are provided by `elements.css` under the `css` directory. You may also link to https://bterlson.github.io/ecmarkup/elements.css which will contain the latest styles for the forseeable future.</p>
3133
</emu-clause>
3234
<emu-clause id="clauses">
3335
<h1>Clauses</h1>
@@ -151,10 +153,9 @@ <h2>Example</h2>
151153

152154
<emu-clause id="grammar">
153155
<h1>Specifying Grammar</h1>
154-
<p>Specifying ECMAScript grammars is the most complex aspect of Ecmarkup. A number of elements and attributes are required to precisely specify productions. These are explained in the following subclauses.</p>
155-
<emu-note>It is my hope that one day we will have a nice, clearly readable, easily parsible, unambiguous plaintext format for the grammar. That day is, sadly, not today.</emu-note>
156-
<h2>Examples</h2>
156+
<p>There are two ways to specify grammar in Ecmarkup: using the <a href="#emu-production">emu-production</a> element and related elements, or by using the <a href="#emu-grammar">emu-grammar</a> element which allows specifying grammar using a plaintext format.</p>
157157

158+
<h2>Examples</h2>
158159
<b>WhileStatement</b>
159160
<pre><code class="language-html">&lt;emu-production name="WhileStatement">
160161
&lt;emu-rhs>while ( &lt;emu-nt>Expression&lt;/emu-nt> ) &lt;emu-nt>Statement&lt;/emu-nt>&lt;/emu-rhs>

0 commit comments

Comments
 (0)