Address references to *.hint with some exceptions

In years < 2001 (with the exception of ferguson2/) that still have
reference to *.hint files they have been changed to README.md with the
following exception: in 1998/dorssel there was a dorssel.hint2. This was
changed to dorssel.hint since the dorssel.hint was changed to README.md
a while back. The references to dorssel.hint2 were changed to without
the 2.

There was an out of date reference in faq.html file to a .hint file as
well that was updated to README.md; the dorssel2.hint in years.html was
changed to the new name.

With that the only files that have to be updated are those that are >=
2001. I still have to check for hint.* however.

1998/dorssel/README.md

@@ -10,84 +10,86 @@
 
         make all
 
-### To run
+### To run:
 
 	echo Simple as 123 | ./dorssel
 	echo '.... --- .--  -.. --- . ...  .. -  -.. ---  - .... .- -' | ./dorssel
 
-## Judges' comments
+## Judges' comments:
 
-    How does the program decide which way to convert?
+How does the program decide which way to convert?
 
-    What obsolescent feature are we talking about?  (No, it's not a
-    C language feature.)
+What obsolescent feature are we talking about?  (No, it's not a
+C language feature.)
 
-    The author suggests that you try to answer the following questions:
+The author suggests that you try to answer the following questions:
 
-	- Which character in the initializing string is totally irrelevant?
-	- Which two relevant characters in the initializing string may be
-	  exchanged without altering the behavior?
-	- Which characters in the initializing string are somewhat irrelevant,
-	  and to what values may they be changed without altering the behavior?
-	- Which characters may be used to enlarge the initializing string by
-	  one without altering the behavior ?
+- Which character in the initializing string is totally irrelevant?
 
-    Extra credit: Change the program so that it does not SHOUT IN ALL CAPS.
+- Which two relevant characters in the initializing string may be exchanged
+without altering the behavior?
 
-    You might also want to read the dorssel.hint2 file.
+- Which characters in the initializing string are somewhat irrelevant, and to
+what values may they be changed without altering the behavior?
 
-## Author's comments
+- Which characters may be used to enlarge the initializing string by one without
+altering the behavior ?
 
-    Usage
-    =====
 
-    This program converts ASCII to Morse code, and vice versa.
+Extra credit: Change the program so that it does not SHOUT IN ALL CAPS.
 
-    The program reads in lines from standard input and writes its result to
-    standard output.  The direction of conversion is determined on a per
-    line basis.  Each line must consist of a maximum of 952 characters
-    followed by a new line character, they must not contain any NUL
-    characters.  Otherwise, some characters may be lost in the conversion.
+You might also want to read the [dorssel.hint](dorssel.hint) file.
 
-    - Encoding to Morse code:
-      The program knows the Morse codes for all Latin letters (a-z, case
-      insensitive) and decimal digits (0-9).  Any other characters are
-      replaced by an ASCII space ' '.  Morse code per converted character is
-      written as a sequence of '.' and '-' characters, each sequence
-      followed by a space.
+## Author's comments:
 
-    - Decoding from Morse code:
-      Morse code should be typed as sequences of '.' and '-' characters,
-      separated by a space.  Extra spaces will be echoed back (to separate
-      words).  Unknown sequences will be converted to a '?' character.
+Usage
+=====
 
-    Notes
-    =====
+This program converts ASCII to Morse code, and vice versa.
 
-    The program assumes both source and execution character sets to be
-    ASCII.  As far as I can tell, the program is conforming and does not
-    invoke undefined behavior.
+The program reads in lines from standard input and writes its result to
+standard output.  The direction of conversion is determined on a per
+line basis.  Each line must consist of a maximum of 952 characters
+followed by a new line character, they must not contain any NUL
+characters.  Otherwise, some characters may be lost in the conversion.
 
-    Hints
-    =====
+- Encoding to Morse code: The program knows the Morse codes for all Latin
+letters (a-z, case insensitive) and decimal digits (0-9).  Any other characters
+are replaced by an ASCII space ' '.  Morse code per converted character is
+written as a sequence of '.' and '-' characters, each sequence followed by a
+space.
 
-    - Try
+- Decoding from Morse code: Morse code should be typed as sequences of '.' and
+'-' characters, separated by a space.  Extra spaces will be echoed back (to
+separate words).  Unknown sequences will be converted to a '?' character.
+
+Notes
+=====
+
+The program assumes both source and execution character sets to be
+ASCII.  As far as I can tell, the program is conforming and does not
+invoke undefined behavior.
+
+Hints
+=====
+
+Try
 
           ./dorssel < dorssel.c | ./dorssel
 
-      to see what variables, numbers, and functions are used.  (Does a
-      better job than most C beautifiers).
+to see what variables, numbers, and functions are used.  (Does a
+better job than most C beautifiers).
 
-    - Filter your text twice (as in the previous sample) to obtain a version
-      of your text that can be reversibly morsified, i.e.
+- Filter your text twice (as in the previous sample) to obtain a version of your
+text that can be reversibly morsified, i.e.
 
           ./dorssel | ./dorssel | ./dorssel | ./dorssel
 
-      is the same as
+is the same as
 
           ./dorssel | ./dorssel
 
-    - The file "dorssel.hint2" contains all the information needed to
-      understand this program.  For an obfuscated spoiler, try
+- The file "dorssel.hint" contains all the information needed to understand this
+program.  For an obfuscated spoiler, try
 
-          ./dorssel < dorssel.hint2
+          ./dorssel < dorssel.hint