Update 1994 winning entries' README.md files

Format and typo fixes.

1994/shapiro/README.md

@@ -1,24 +1,26 @@
 # Most Well Rounded Obfuscation
 
-Andrew T. Shapiro
-CSES/CIRES University of Colorado
-Campus Box 216
-Boulder, CO 80309-0216
-USA
+Andrew T. Shapiro  
+CSES/CIRES University of Colorado  
+Campus Box 216  
+Boulder, CO 80309-0216  
+USA  
 
 ## To build:
 
-        make all
+```sh
+make all
+```
 
 [Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) fixed a bug on systems
 where `EOF != -1`. The problem is that `getc()` and the related functions do not
 return `-1` on EOF or error but rather `EOF`. However `EOF` is not required to be
 `-1` but merely an int < 0 and this program assumed that `getc()` will return
-`-1` on EOF or error, not `EOF`. On systems where `EOF != -1` it could be a
-problem. For the same reason one should not use `EOF` for the `getopt()`
+`-1` on EOF or error, not `EOF`. On systems where `EOF != -1` it could result in
+an infinite loop (for the same reason one should not use `EOF` for the `getopt()`
 functions as they return `-1` when all options are parsed (for details on the
 definition of `EOF` see `7.21 Input/output<stdio.h>` subsection 1 of the
-standard). An interesting problem occurred where changing the `-1` to `EOF`
+standard)). An interesting problem occurred where changing the `-1` to `EOF`
 caused both `warning: illegal character encoding in string literal` and `error:
 source file is not valid UTF-8`. But since `EOF` is simply an int < 0 and making
 the loop condition check that the return value is >= 0 does not cause a
@@ -28,7 +30,9 @@ assistance!
 
 ## To run:
 
-	./shapiro &
+```sh
+./shapiro &
+```
 
 ## Try:
 
@@ -86,7 +90,7 @@ obfuscation is a six member client/server hierarchy.
 (See the [shapiro.md](shapiro.md) file for a detailed description of the
 algorithm.)
 
-Lint complains about: precedence confusion, `K` may be used before set,
+`lint` complains about: precedence confusion, `K` may be used before set,
 main() returns random value to invocation environment, value type used 
 inconsistently, value type declared inconsistently, function argument 
 (number) used inconsistently, function returns value which is always