Merge pull request #1082 from xexyl/thanks-fmt-fixes

thanks-for-fixes.md

@@ -240,11 +240,11 @@ and the third arg was an `int`.  Cody notes that he tried to keep the ASCII art
 as close to the original as possible. The line lengths are the same but some
 spaces had to be changed to non-spaces.
 
-As noted above, a very funny problem occurred depending on the compiler and whether or not the
+As noted above, a very funny problem occurred depending on the compiler and
-optimiser was enabled that had to be fixed: one compiler would work fine but
+whether or not the optimiser was enabled that had to be fixed: one compiler
-another might enter an infinite loop or segfault but then once the optimiser
+would work fine but another might enter an infinite loop or segfault but then
-state was changed the compiler that worked no longer worked (in the same was as
+once the optimiser state was changed the compiler that worked no longer worked
-the other one not working) and the one that didn't work did!
+(in the same was as the other one not working) and the one that didn't work did!
 
 We encourage you to see the README.md file to see how odd this problem was and
 what Cody did to fix it!
@@ -253,8 +253,8 @@ what Cody did to fix it!
 ## [1986/wall](1986/wall/wall.c) ([README.md](1986/wall/README.md]))
 
 Cody fixed this so that it does not require `-traditional-cpp`. This took a fair
-bit of tinkering as this entry *is* strange; fixing `-traditional-cpp` is, as noted earlier, very
+bit of tinkering as this entry *is* strange; fixing `-traditional-cpp` is, as
-complicated, but we encourage you to look at [original
+noted earlier, very complicated, but we encourage you to look at [original
 code](1986/wall/wall.orig.c) to see how different C was in 1986.
 
 Yusuke originally patched this to use `strdup()` on two strings and this let it
@@ -1668,8 +1668,12 @@ Cody added the following words of wisdom: 'this is not a pipe'.
 ## [2011/richards](2011/richards/richards.c) ([README.md](2011/richards/README.md]))
 
 Cody fixed a minor problem that showed up in both linux and macOS. He notes
-however that as of this time this entry does not work properly with macOS. See
+however that as of this time this entry does not work properly with macOS at
-[bugs.md](/bugs.md) for more details.
+least with the silicon chip (Intel has not been tested) and it is quite possibly
+an inherent problem in macOS to do with executing code in in memory/JIT and in
+particular with the silicon chip. See [bugs.md](/bugs.md) for more details and a
+document from Apple about how it might be fixed if anyone is brave enough to
+try.
 
 
 ## [2011/vik](2011/vik/vik.c) ([README.md](2011/vik/README.md]))