Fixes in 2020/ferguson1

Typo fix.

Rename COMPILING -> COMPILING.md and HACKING -> HACKING.md. I have not
tested the formatting on either of these but they should be okay.

Updated the COMPILING (portability information) as I know it works under
Apple M1 chips too.

2020/ferguson1/COMPILING.md

@@ -13,15 +13,18 @@ should you run into trouble.
 
 # Portability
 
-I have tested this under macOS Catalina, Fedora (29 and also 31 - no that's not
-a typo, I upgraded from 29 to 31 as I had delayed upgrading to 30 due to a
-number of issues and being busy) and CentOS 7.7.1908. It obviously requires
-ncurses but other than that nothing extra should be needed. Note that the
-testing of Fedora 29 was earlier in the development however (but then 29 is also
-EOL).
+I have tested this under macOS Catalina, macOS Ventura (and probably between the
+two), Fedora (29 and also 31 - no that's not a typo, I upgraded from 29 to 31 as
+I had delayed upgrading to 30 due to a number of issues and being busy) and
+CentOS 7.7.1908. It should work under any modern linux system and maybe other
+Unices as well as macOS (as noted).
+
+It obviously requires ncurses but other than that nothing extra should be
+needed. Note that the testing of Fedora 29 was earlier in the development
+however (but then 29 is also EOL).
 
 Furthermore I do not believe - but I cannot confirm either - that endianness
-matters; I only have Intel CPUs.
+matters; I only have Intel CPUs and arm64 (MacBook Pro M1).
 
 I imagine that it works for 32-bit systems but I do not know for sure.
 

2020/ferguson1/HACKING.md

@@ -1,9 +1,11 @@
-# WARNING: There are some things cited in this document that are no longer
-# correct, might be misleading or otherwise not clear. This is both intentional
-# and unintentional. This is especially true for claims that something means
-# something specific. Put another way just because the table says something
-# doesn't mean it's the whole truth: no misleading comments but misleading
-# document that talks about some parts of the code!
+## Warning / caveat about this document
+
+WARNING: There are some things cited in this document that are no longer
+correct, might be misleading or otherwise not clear. This is both intentional
+and unintentional. This is especially true for claims that something means
+something specific. Put another way just because the table says something
+doesn't mean it's the whole truth: no misleading comments but misleading
+document that talks about some parts of the code!
 
 In this document I provide information to the herpetologist hackers to help them
 to modify certain things and add features for their studying of snakes. Or if

2020/ferguson1/Makefile

@@ -420,7 +420,7 @@ MAY_NEED_GCC= gcc
 ##############################
 #
 OBJ= prog.o termcaps.o
-DATA= COMPILING HACKING bugs.md cannibalism.log \
+DATA= COMPILING.md HACKING.md bugs.md cannibalism.log \
     chocolate-cake.md crazy.log gameplay.md \
     snake-colours.sh snake.1 spoilers.md \
     termcaps.c terminals.md troubleshooting.md

2020/ferguson1/README.md

@@ -314,7 +314,7 @@ I can think of at the least the following:
     the max size or very close to it. In fact if you have the shedding size to be
     even one on every move even if you normally can't win with the same size
     screen you might find it happens much more easily! You could of course play
-    with these paramters in different ways together - there are certainly
+    with these parameters in different ways together - there are certainly
     different combinations than I have given.
 -   Of course you could also enable one or both cheat modes. You might be
     considered a filthy cheat but both modes are quite fun (one being enabled by

2020/ferguson1/spoilers.md

@@ -40,7 +40,7 @@ actually done in more detail.
 
 First I initialise curses; if this fails I print an error message ('curses
 error') and return 1.  Next the screen size is determined and I subtract 1 from
-each the x/y. If it's too small curses is ended and an error message ('screen
+both x/y. If it's too small curses is ended and an error message ('screen
 too small') is printed - returning 1.
 
 Next the max size of the snake is determined: if `MAXSIZE` is specified then