fix more broken markdown links

We fix more markdown links in markdown files that refer to files
internally to the web site.

Added tmp tools to find and print various markdown links:

* `tmp/md-links.sh` - print all markdown links
* `tmp/md-token-links.sh` - print all markdown links that start with a **%%TOKEN%%**
* `tmp/md-local-links.sh` - print all markdown links to a local file
* `tmp/md-link-paths.sh` - print local file paths referenced in markdown links

Fixed a number of markdown formatting problems with `thanks-for-help.md`.
Fixed markdown links to files in `thanks-for-help.md`.  Improved
heading levels in `thanks-for-help.md`, and made entry sections consistent.

Changed all markdown links that end in "))" to end in a better way.

Explained in `markdown.md` why we are avoiding markdown links that
end in "))".

Ran `make www` to perform the above.

TODO: Fix stuff we broke by mistake doing the above.

TODO: Fix more broken markdown links.

1992/buzzard.2/README.md

@@ -137,7 +137,7 @@ part.
 
 For more information on what you can do once you've piped [third](%%REPO_URL%%/1992/buzzard.2/third) into
 first, type `help` and consult
-[FORTH](https://en.wikipedia.org/wiki/Forth_(programming_language)) manuals for
+[FORTH](https://en.wikipedia.org/wiki/Forth_(programming_language)) manuals for
 further reference.  Six sample THIRD programs are included in the files
 `demo1.th` through `demo6.th`.  See [buzzard.2.README.html](buzzard.2.README.html)
 for more information.
@@ -190,7 +190,7 @@ answer the question "what will this do when I run it".  A reader who has
 deciphered `first` to this point may think they know the answer to this
 question, but they may not know the answer to the more important question, "what
 will this program do when given the right input?"
-[FORTH](https://en.wikipedia.org/wiki/Forth_(programming_language)) aficionados,
+[FORTH](https://en.wikipedia.org/wiki/Forth_(programming_language)) aficionados,
 and especially FORTH implementers, may recognize the similarity of the internal
 compiler format to many FORTH internal representations, and, being aware that
 FORTH interpreters can often be self-compiling, may be suspicious that this

1992/vern/README.md

@@ -147,8 +147,8 @@ by comparing the function pointer with the function itself).
 Fourth, there are no independent routines for generating potential moves.
 Instead, the program generates its moves by brute force: for every piece it
 controls on the board, it attempts to move it to every square on the board.
-Those moves that are legal it then explores to see their effects (using
-[alpha-beta search](https://en.wikipedia.org/wiki/Alpha-beta_pruning)).  This
+Those moves that are legal it then explores to see their effects, using
+[alpha-beta search](https://en.wikipedia.org/wiki/Alpha-beta_pruning).  This
 tactic somewhat obfuscates the algorithm used by the program.
 
 Finally, there are three key constants that occur throughout the program:  `64`,

1992/vern/index.html

@@ -499,8 +499,8 @@ by comparing the function pointer with the function itself).</p>
 <p>Fourth, there are no independent routines for generating potential moves.
 Instead, the program generates its moves by brute force: for every piece it
 controls on the board, it attempts to move it to every square on the board.
-Those moves that are legal it then explores to see their effects (using
-<a href="https://en.wikipedia.org/wiki/Alpha-beta_pruning">alpha-beta search</a>). This
+Those moves that are legal it then explores to see their effects, using
+<a href="https://en.wikipedia.org/wiki/Alpha-beta_pruning">alpha-beta search</a>. This
 tactic somewhat obfuscates the algorithm used by the program.</p>
 <p>Finally, there are three key constants that occur throughout the program: <code>64</code>,
 <code>8</code>, and <code>3</code> (<code>lg 8</code>). Rather than making these available at compile-time,