Fossil

• Constructs like "<blockquote><pre>" are now simply "<pre>"
• Ditto "<blockquote><b>" for command examples, which then allowed me to get rid of explicit "br" elements; pre does that for us.
• Where it was used merely to get an indent for a code block, we're now using pre or verbatim instead, depending on whether we need embedded HTML and/or pre-wrap handling. (Not the same thing as the prior item.) In some places, this let us replace use of HTML-escaped code blocks in pre with verbatim equivalents, not needing the escaping, allownig the doc source to read more like the rendered HTML.
• Use of blockquotes to get hierarchical indenting is no longer necessary; the skin does that. A good example is indenting ol and ul lists under the parent paragraph; additional manual indenting is no longer necessary.

The only remaining instances of "blockquote" under www/ are necessary:

1. The copyright release doc is plain HTML, without the fossil-doc wrapper, giving it no access to the new skin improvements.
2. One MD doc wants a blockquote in the middle of a list, and the current parsing rules don't let us use ">" there.
3. The skinning docs talk about styling blockquote elements at one point; it isn't a use of the tag, it is a prose reference to it.

• in Markdown nested lists, where blank lines should render the list items as separate paragraphs just as at the list's top level; since it does not, if you want a line break, you either have to wrap the item in "p" tags or do the double-br hack.
• in Wiki where blank lines within a list give you a separate list in the HTML output; this is fine for bullet lists, but with numbered lists it causes the numbering to restart unless you do the same sort of manual HTML workaround as with the prior item
• in plain HTML docs and wiki docs between "nowiki" tags

In many places, this cleanup gets rid of pointless stray "p" tags, placating HTML verifiers. ... (file: [32d45d6374] check-in: [1fd407f61a] user: wyoung branch: trunk, size: 11724)

Where possible, changed constructs like

<a name="foo"></a><h3>

<h3 id="foo">

Also fixed a few cases where the link target came after a header so the browser would scroll the header off the screen when visiting the targeted section.

Added a 50em pad at the bottom of one such edited doc to allow the intra-doc link targets to be useful since it's a short enough doc that on sufficiently tall browser windows, scrolling isn't possible, so using those anchors has no visible effect. ... (file: [5548f5376c] check-in: [93cee1f56e] user: wyoung branch: trunk, size: 11893)