improve how markdown code language is commented

We added a space between the markdown triple code mark
and language that was enclosed in HTML comments.

So a line of the form:

````
```<!---c--->
````

became:

````
``` <!---c--->
````

This was done to **help** some code see that the HTML comment
string was not a markdown code specifier.   Not all code
understands this after this changed.  For example, `pandoc(1)`
still forms HTML classes of the form "&lt;!---c--&gt;"
when it encounters the above mentioned change.

We also fixed a problem with `2019/dogon/README.md` regarding
a markdown code block.

We also fixed a problem with `2020/yang/README.md` regarding
a markdown code block.

1995/cdua/README.md

@@ -4,7 +4,7 @@ We recommend that you try the alternate version first so you can see what this
 entry looked like back in 1995 (with a configurable speed).  See the [original
 code](#original-code) section below for the original entry.
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
@@ -28,14 +28,14 @@ For more detailed information see [1995 cdua bugs](../../bugs.html#1995_cdua).
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./cdua.alt
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     make SLEEP=1500 clobber alt
 
     ./cdua.alt # press enter and watch it go much faster!
@@ -43,7 +43,7 @@ For more detailed information see [1995 cdua bugs](../../bugs.html#1995_cdua).
 
 You might also like to try:
 
-```<!---sh-->
+``` <!---sh-->
     make SLEEP=65000 clobber alt
 
     ./cdua.alt # press enter and watch it go much slower!
@@ -66,14 +66,14 @@ fast your computer is :-) or use both to see the difference, you can do so.
 
 ### Original build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ### Original use:
 
-```<!---sh-->
+``` <!---sh-->
     ./cdua
 ```
 

1995/dodsond1/README.md

@@ -1,20 +1,20 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./dodsond1 < text_file
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./dodsond1 < README.md
 ```
 
@@ -32,7 +32,7 @@ You might consider giving the following input:
 
 ... which can be done like:
 
-```<!---c-->
+``` <!---c-->
     ./try.sh
 ```
 

1995/dodsond2/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./dodsond2
 ```
 

1995/esde/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./esde data-file word
 ```
 
@@ -16,7 +16,7 @@ where data-file contains lines of < 255 chars in length.
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1995/garry/README.md

@@ -1,20 +1,20 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./garry <input_file >output_file
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -29,21 +29,21 @@ left intact) looked very much like a rat "dropping core".  See
 
 ### Alternate build:
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
 
 ### Alternate use:
 
-```<!---sh-->
+``` <!---sh-->
     ./garry.alt <input_file >output_file
 ```
 
 
 ### Alternate try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.alt.sh
 ```
 
@@ -63,13 +63,13 @@ environment variables.
 The calling syntax is pretty simple, just use it with `stdio`-redirection
 or inside pipelines, e.g.:
 
-```<!---sh-->
+``` <!---sh-->
     ./garry <file_to_convert >converted_file
 ```
 
 or
 
-```<!---sh-->
+``` <!---sh-->
     cat all_my_files/* | ./garry | lp
 ```
 
@@ -87,7 +87,7 @@ Unknown Env-variables or malformed expressions are ignored and kept intact.
 Additionally, the filter replaces escaped octal values in the environment
 variables by their binary representation, e.g.:
 
-```<!---sh-->
+``` <!---sh-->
     $ TEST="\110\145\154\154\157"
     $ export TEST
     $ echo '$TEST$' | ./garry

1995/heathbar/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./heathbar num num
 ```
 
@@ -16,7 +16,7 @@ where num is a non-negative number.
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1995/leo/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -18,7 +18,7 @@ For more detailed information see [1995 leo bugs](../../bugs.html#1995_leo).
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./leo [ deep ] [ right ] [ Variable ] [ cycle [ freq ] ]
 ```
 
@@ -27,7 +27,7 @@ See the author's information below on these details.
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -52,7 +52,7 @@ characters on the command line - anything that's not a number is a candidate.)
 
 The usage is:
 
-```<!---sh-->
+``` <!---sh-->
     ./leo [ deep ] [ right ] [ Variable ] [ cycle [ freq ] ]
 ```
 
@@ -68,7 +68,7 @@ to be present if you want to enter `freq` (and you usually do).
 
 Some options to try (besides the obvious):
 
-```<!---sh-->
+``` <!---sh-->
     ./leo 1 | cat - /dev/tty | gs -
 ```
 
@@ -191,19 +191,19 @@ the opening for step 1 is not a single line but a cross:
 
 To watch it repeatedly (as a screen saver), use:
 
-```<!---sh-->
+``` <!---sh-->
     ./leo 2 | cat - /dev/tty | gs -
 ```
 
 The command line:
 
-```<!---sh-->
+``` <!---sh-->
     ./leo Variable 1 | cat - /dev/tty | gs -
 ```
 
 draws the same as above. Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./leo Variable 1 1 | cat - /dev/tty | gs -
 ```
 
@@ -228,7 +228,7 @@ If `Variable` is used, the actual value of `cycle` doesn't matter,
 as far as it is > 1. To figure out what difference
 `cycle` makes when `Variable` is not used, try
 
-```<!---sh-->
+``` <!---sh-->
     ./leo Variable 37 80 | cat - /dev/tty | gs -
 ```
 

1995/makarios/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./makarios
 ```
 

1995/savastio/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -18,7 +18,7 @@ For more detailed information see [1995 savastio bugs](../../bugs.html#1995_sava
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./savastio
     # enter a POSITIVE number such as 100
 ```
@@ -29,7 +29,7 @@ what happens if you give a non-number?
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1995/schnitzi/README.md

@@ -1,20 +1,20 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./schnitzi num
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1995/spinellis/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./spinellis < spinellis.c
 ```
 

1995/vanschnitz/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -21,14 +21,14 @@ For more detailed information see [1995 vanschnitz bugs](../../bugs.html#1995_va
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./vanschnitz
 ```
 
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -43,7 +43,7 @@ to first try and figure out the program without the spoiler.
 
 ### Alternate build:
 
-```<!---sh-->
+``` <!---sh-->
     make alt
 ```
 
@@ -84,7 +84,7 @@ line.  For instance, to cause the compiler to solve the Towers
 of Hanoi problem with four disks, you would compile the program
 like this:
 
-```<!---sh-->
+``` <!---sh-->
     gcc hanoi.c -o hanoi -Dn=4
 ```
 
@@ -111,7 +111,7 @@ concatenated; a version that does not use this feature has been
 included for people who can only run K&R).  A good way to see
 the resulting program (on a Unix system) is to do the command
 
-```<!---sh-->
+``` <!---sh-->
     gcc hanoi.c -E -Dn=5 | grep -v \# | grep -v ^\$
 ```