improved indentation and whitespace for markdown code blocks

All code blocks in markdown have been intended by at least 4 spaces.

We add `--tab-stop=8` to all `pandoc(1)` executions in order to set
a better tab stop indentation, especially for tab intended code blocks.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.5.3 2024-03-26"
to "1.6 2024-03-31".

Fixed `1991/brnstnd/sorta.README.md` so that the sorta code
is code blocks.

Removed unneeded paragraph group in copyright in `inc/footer.default.html`.

Fixed excess whitespace after list Author on entry `index.html` page.

Changed `bin/output-index-author.sh` VERSION from "1.5.2 2024-03-26"
to "1.6 2024-03-31".

Performed `make www` to perform the above and test under macOS.

TODO: Fix the problem of the initial line of code being extra intended.
TODO: Fix excess whitespace around code that is inline.

2015/hou/README.md

@@ -1,7 +1,7 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 
@@ -10,7 +10,7 @@ make
 The current status of this entry is:
 
 ```
-STATUS: INABIAF - please **DO NOT** fix
+    STATUS: INABIAF - please **DO NOT** fix
 ```
 
 For more detailed information see [2015 hou bugs](../../bugs.html#2015_hou).
@@ -19,15 +19,15 @@ For more detailed information see [2015 hou bugs](../../bugs.html#2015_hou).
 ## To use:
 
 ```sh
-echo something | ./prog
-./prog < file
+    echo something | ./prog
+    ./prog < file
 ```
 
 
 ## Try:
 
 ```sh
-./try.sh
+    ./try.sh
 ```
 
 
@@ -43,8 +43,8 @@ the reference code!
 Some things that make you go, "huh?"
 
 ```sh
-./prog < prog.c | cut -c-5
-./prog < Makefile | cut -c-4
+    ./prog < prog.c | cut -c-5
+    ./prog < Makefile | cut -c-4
 ```
 
 How are those values magically returned?
@@ -52,7 +52,7 @@ How are those values magically returned?
 What happens with a large file? Something over 256K.
 
 ```sh
-./prog < large_file
+    ./prog < large_file
 ```
 
 Where does that message come from?