add timestamps and hashes, minor edits to guide intro

website/api/intro.html

@@ -1,7 +1,7 @@
 <hr> <!-- this improves readability on e.g. elinks and w3m -->
 <h2 id="introduction">Introduction</h2>
 
-<p>Version: 0.6.0 (2013-09-XX)</p>
+<p>Version: 0.6.0 (2013-09-21)</p>
 <p><b>Work in progress</b></p>
 
 <h3>Document scope</h3>

website/download/download.html

@@ -9,7 +9,8 @@
 <tr><th>Date</th><th>Filename</th><th>Description</th><th>MD5</th></tr>
 </thead>
 <tbody>
-<tr><td>2013-09-XX</td><td><a href="duktape-0.6.0.tar.xz">duktape-0.6.0.tar.xz</a></td><td>alpha, first round of work on public API</td><td class="hash">XXX</td></tr>
+<tr><td>2013-09-21</td><td><a href="duktape-0.6.0.tar.xz">duktape-0.6.0.tar.xz</a></td><td>alpha, first round of work on public API</td><td class="hash">fa384a42a27d996313e0192c51c50b4a</td></tr>
+
 </tbody>
 </table>
 
@@ -26,7 +27,7 @@ stuff.  You only need a full release if you intend to change the internals of Du
 <tr><td>2013-03-16</td><td><a href="duktape-full-0.3.0.tar.xz">duktape-full-0.3.0.tar.xz</a></td><td>early alpha, global object, Object, String added, missing built-ins</td><td class="hash">9fecfa2c3d5e99efc53d64b653556ba7</td></tr>
 <tr><td>2013-03-31</td><td><a href="duktape-full-0.4.0.tar.xz">duktape-full-0.4.0.tar.xz</a></td><td>early alpha, Array, Number added, completing built-ins</td><td class="hash">86e2452a895192370b19a0861565c8d7</td></tr>
 <tr><td>2013-05-17</td><td><a href="duktape-full-0.5.0.tar.xz">duktape-full-0.5.0.tar.xz</a></td><td>alpha, built-in number conversion primitives</td><td class="hash">987e83e0fa0197288d06a601129c845c</td></tr>
-<tr><td>2013-09-XX</td><td><a href="duktape-full-0.6.0.tar.xz">duktape-full-0.6.0.tar.xz</a></td><td>(see above)</td><td>XXX</td></tr>
+<tr><td>2013-09-21</td><td><a href="duktape-full-0.6.0.tar.xz">duktape-full-0.6.0.tar.xz</a></td><td>(see above)</td><td class="hash">e37c151a1c0efab3c63aa30b7164d346</td></tr>
 </tbody>
 </table>
 

website/guide/intro.html

@@ -1,7 +1,7 @@
 <hr> <!-- this improves readability on e.g. elinks and w3m -->
 <h2 id="introduction">Introduction</h2>
 
-<p>Version: 0.6.0 (2013-09-XX)</p>
+<p>Version: 0.6.0 (2013-09-21)</p>
 <p><b>Work in progress</b></p>
 
 <h3>Document scope</h3>
@@ -66,11 +66,11 @@ features (some are visible to applications, while others are internal):</p>
 Ecmascript compliance requires regular expression and Unicode support.</p>
 
 <p><b>Portability</b>.  Minimal system dependencies are nice when porting,
-so Duktape depends on very few system libraries: number formatting and
-parsing, regular expressions, and Unicode are all implemented internally
-in Duktape.  One of the few dependencies that cannot be fully eliminated is
-system date/time integration.  This is confined to the implementation of
-the <tt>Date</tt> built-in.</p>
+so Duktape depends on very few system libraries.  For example, number
+formatting and parsing, regular expressions, and Unicode are all implemented
+internally by Duktape.  One of the few dependencies that cannot be fully
+eliminated is system date/time integration.  This is confined to the
+implementation of the <tt>Date</tt> built-in.</p>
 
 <p><b>Easy C interface</b>.  The interface between Duktape and C programs
 should be natural and error-tolerant.  As a particular issue, string
@@ -88,7 +88,8 @@ so there is no practical way of competing with very advanced JIT-based engines
 like SpiderMonkey (and its optimized variants) or Google V8.  Performance
 should still be reasonable for typical embedded programs.
 <a href="http://www.lua.org/">Lua</a> is a good benchmark in this respect.
-(Adding optional, modular support for JITing later would be nice.)</p>
+(Adding optional, modular support for JITing or perhaps off-line compilation
+would be nice.)</p>
 
 <p><b>ASCII string performance</b>.  It's important that operations dealing
 with plain ASCII strings be very fast: ASCII dominates most embedded use.