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.

1987/biggar/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     some_command | ./biggar | od -c
 
     ./biggar < file | od -c
@@ -16,7 +16,7 @@
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 

1987/heckbert/README.md

@@ -1,6 +1,6 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
@@ -10,7 +10,7 @@ To compile on a 16 bit machine, change 300000 to 30000.
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./heckbert col < file
 ```
 
@@ -19,7 +19,7 @@ where col is the number of columns to fold at and file is the file to fold.
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
@@ -28,7 +28,7 @@ where col is the number of columns to fold at and file is the file to fold.
 
 Folding at the wrong length may be equivalent to a "Spindle or Mutilate" operation. For example:
 
-```<!---sh-->
+``` <!---sh-->
     ./heckbert 40 < heckbert.c > ph.c ; make ph ; ./ph 20 < heckbert.c > bar.c ; make bar
 ```
 

1987/hines/README.md

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

1987/korn/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./korn
 ```
 
@@ -29,14 +29,14 @@ Several points are important to understand this program:
 2. What is the value of the symbol `"have"`?  (hint: the value is NOT 4
 characters, or `'h'`, or a string)  Consider the fact that:
 
-```<!---c-->
+``` <!---c-->
     char *x;
 ```
 
 defines a pointer to a `char` (i.e. an address), and that the `=` assigns
 things of compatible types.  Since:
 
-```<!---c-->
+``` <!---c-->
     x = "have";
 ```
 
@@ -44,13 +44,13 @@ is legal C, what type of value is `"have"`?
 
 3. Note that the following expressions yield the same value:
 
-```<!---c-->
+``` <!---c-->
     x[3]	*(x+3)	  *(3+x)
 ```
 
 since addition is commutative.  What can be said about this value?
 
-```<!---c-->
+``` <!---c-->
     3[x]
 ```
 

1987/lievaart/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
 ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./lievaart
     # enter a level and start playing as described below
 ```
@@ -17,7 +17,7 @@
 
 To see what it would have looked like without the size restrictions:
 
-```<!---sh-->
+``` <!---sh-->
     ./lievaart2
     # enter a level and start playing as described below
 ```

1987/wall/README.md

@@ -1,13 +1,13 @@
 ## To build:
 
-```<!---sh-->
+``` <!---sh-->
     make all
     ```
 
 
 ## To use:
 
-```<!---sh-->
+``` <!---sh-->
     ./wall
     # enter some numbers
 
@@ -18,14 +18,14 @@
 
 ## Try:
 
-```<!---sh-->
+``` <!---sh-->
     ./try.sh
 ```
 
 You may of course run the commands manually and enter text as you wish. For
 instance you might try one or both of:
 
-```<!---sh-->
+``` <!---sh-->
     ./wall | bc
 
     ./wall | cat

1987/westley/README.md

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