http://www.s48.org/development.html: minor fixes

Ivan Shmakov <[email protected]> Sat, 25 Oct 2008 22:49:21 +0700
Newsgroups	gmane.lisp.scheme.scheme48
Message-ID	<[email protected]>
	May I suggest the following changes?

 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN""http://www.w3.org/TR/REC-html40/loose.dtd">

	Shouldn't a space, or LF, be here?  Like:

   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
             "http://www.w3.org/TR/REC-html40/loose.dtd">

 | <p>To check out one of these, do:</p>
 | <pre>     hg clone &lt;url&gt; &lt;dir&gt;
 | </pre>
 | <p>This will place a clone of the repository in <code>&lt;dir&gt;</code>.</p>

	Wouldn't angle brackets (`&lang;', `&rang;') be better than
	ASCII `<', `>' here?

--cut: /usr/share/xml/entities/xhtml/xhtml-symbol.ent--
<!ENTITY lang     "&#9001;" ><!-- left-pointing angle bracket = bra,
                               U+2329 ISOtech -->
<!-- lang is NOT the same character as U+003C 'less than'
     or U+2039 'single left-pointing angle quotation mark' -->
<!ENTITY rang     "&#9002;" ><!-- right-pointing angle bracket = ket,
                               U+232A ISOtech -->
<!-- rang is NOT the same character as U+003E 'greater than'
     or U+203A 'single right-pointing angle quotation mark' -->
--cut: /usr/share/xml/entities/xhtml/xhtml-symbol.ent--

 | <p>As a rule of thumb, you need to rerun <code>autoconf</code> (or
 |   <code>autoreconf</code> - look in <code>autogen.sh</code> for the

	Here, the em-dash (`&mdash;') should be used, and not a
	hyphen/minus (`-'.)

 |   correct command) when <code>configure.in</code> was changed; rerun
[...]
 |   doubt, rerun it all. </p>

 | <p>When making changes <code>configure.in</code>, <pre>

	Should probably be:

   <p>When making changes to <code>configure.in</code>, <pre>

	instead.

 |     ./config.status --recheck &amp;&amp; ./config.status
 |   </pre>is equivalent to re-running <code>configure</code>
 |   with all the arguments specified on its previous
 |   invocation.</p>

	It may also be noted that it makes the form:

$ VARIABLE=VALUE .../configure OPTION...

	inferior to the similar:

$ .../configure VARIABLE=VALUE OPTION...

	form, because, though they're almost identical, the latter form
	will store these VARIABLE=VALUE pairs in config.status (along
	with any other options specified), thus allowing them to be
	recalled with $ ./config.status --recheck.

	Also, why not to put more ASCII LFs into the file?  In
	particular, that would allow `diff's to be much more readable.