fix Makefile and README.md for 2000/tomx

2000/tomx/README.md

@@ -1,40 +1,43 @@
 # Most Complete Program:
 
-    Thomas P John
-    Mishybi Plamoottil
-    Parottukonam
-    Nalanchira P.O, Trivandrum-695015
-    India
+Thomas P John
+Mishybi Plamoottil
+Parottukonam
+Nalanchira P.O, Trivandrum-695015
+India
 
-    http://tomx.tripod.com/
+http://tomx.tripod.com/
 
+# To build:
 
-## Judges' Comments:
-### To use:
+```sh
+make
+```
 
-    make tomx
+### To run:
+
+```sh
+./tomx
+```
 
 ### Try:
 
-    rm -f ./tomx
-    sh tomx.c
-    ./tomx
+```sh
+rm -f ./tomx
+chmod +x ./tomx.c
+./tomx.c
+./tomx
+```
 
-If sh is your shell:
+as well as:
 
-    rm -f ./tomx
-    chmod +x ./tomx.c
-    ./tomx.c
-    ./tomx
+```sh
+rm -f ./tomx
+make -f tomx.c
+./tomx
+```
 
-### Also try:
-
-    rm -f ./tomx
-    make -f tomx.c
-    ./tomx
-
-
-### Selected Judges Remarks
+## Judges' comments:
 
 Polyglots have come and gone, but this was the first one we'd seen
 where one language *used* another to perform its tasks.  An interesting
@@ -42,8 +45,7 @@ approach.  Admittedly, it's not all that obfuscated - but there's more
 to it than you might think, since you have to make sure that your
 changes don't change the shell code or the makefile.
 
-
-### Selected Author's Comments:
+## Author's comments:
 
 ### Summary
 
@@ -61,23 +63,23 @@ Probably, this is the first entry ever to fully satisfy Rule #1
 ### Top 5 reasons (IMHO) why this code is an entry for IOCCC
 
 1. A glance at the source itself will tell you that most of the
-   Obfuscation is NOT in the C code per se, but in the comments
-   to the C code. (But sadly, I could not find an "International
-   Obfuscated C COMMENT contest". So I HAD to send this entry
-   here to the IOCCC itself).
+Obfuscation is NOT in the C code per se, but in the comments
+to the C code. (But sadly, I could not find an "International
+Obfuscated C COMMENT contest". So I HAD to send this entry
+here to the IOCCC itself).
 
 2. Of the 3 languages in the source, the least obfuscated is
-   C (But again, there was NO obfuscated make/shscript contest)
-   (Does this hint for a rule in IOCCC-2001 that the major
-   obfuscation should be in C and not elsewhere???. Mmmmm...).
+C (But again, there was NO obfuscated make/shscript contest)
+(Does this hint for a rule in IOCCC-2001 that the major
+obfuscation should be in C and not elsewhere???. Mmmmm...).
 
 3. Extending Argument #2... Obfuscation done in the C code
-   (comments?) create obfuscated code for the other 2 languages.
-   This opens new possibilities to be explored in depth in future
-   IOCCCs.
+(comments?) create obfuscated code for the other 2 languages.
+This opens new possibilities to be explored in depth in future
+IOCCCs.
 
 4. LOOKS like a Makefile, WORKS like a shell script and COMPILES
-   like a C program.
+like a C program.
 
 5. Does something useful (See Notes #1, #2).
 
@@ -90,13 +92,13 @@ the main(), leaving the complexities of the C file elsewhere and making this
 source still acceptable to "make" and "sh". The following modification to the
 last few lines will compile the IOCCC's famous `mkentry.c`.
 
+```make
+.PHONY: /* true clean */ 
+#undef   true 
+#include "mkentry.c"
+```
 
-	    .PHONY: /* true clean */ 
-	    #undef   true 
-	    #include "mkentry.c"
-
-
-    Ain't that useful?
+Ain't that useful?
 
 2. By extending this program's idea, It is possible to do some
 very interesting things like generating C code on execution