convert spoiler language and towards deobfuscation language

1998/df/README.md

@@ -111,20 +111,20 @@ I decided it would be better this way...
 These restrictions have been removed for your convenience.
 
 The following lines describe how this program works; if you don't
-want to know it at this time, please skip them. If this entry would
-by some mistake win the contest, please do not rot13 this - I hate
-rot13 spoilers since it is somewhat complicated on a Mac to
-reverse them. Anyone out there should have enough discipline and
-rot13 shouldn't be required, really. After all, we are not children
-anymore :-)
+want to know it at this time, please skip them.
+
+You should have enough discipline to make an effort to understand
+the code without reading the deobfuscation information below.
+After all, we are not children anymore :-)
+
+## Deobfuscation information
 
 <hr style="width:10%;text-align:left;margin-left:0">
 
 This paragraph is not part of the author's remarks, but is a helpful
 gift from the judges; if you read too fast to stop yourself, this should
 give you enough time to stop, which you really need to do RIGHT NOW if
-you don't want to read the spoilers, which really do spoil everything,
-we mean it.
+you don't want to read the deobfuscation information: we mean it.
 
 <hr style="width:10%;text-align:left;margin-left:0">
 

1998/df/index.html

@@ -481,18 +481,16 @@ My first private version would only run when compiled on a Friday.
 I decided it would be better this way…
 These restrictions have been removed for your convenience.</p>
 <p>The following lines describe how this program works; if you don’t
-want to know it at this time, please skip them. If this entry would
-by some mistake win the contest, please do not rot13 this - I hate
-rot13 spoilers since it is somewhat complicated on a Mac to
-reverse them. Anyone out there should have enough discipline and
-rot13 shouldn’t be required, really. After all, we are not children
-anymore :-)</p>
+want to know it at this time, please skip them.</p>
+<p>You should have enough discipline to make an effort to understand
+the code without reading the deobfuscation information below.
+After all, we are not children anymore :-)</p>
+<h2 id="deobfuscation-information">Deobfuscation information</h2>
 <hr style="width:10%;text-align:left;margin-left:0">
 <p>This paragraph is not part of the author’s remarks, but is a helpful
 gift from the judges; if you read too fast to stop yourself, this should
 give you enough time to stop, which you really need to do RIGHT NOW if
-you don’t want to read the spoilers, which really do spoil everything,
-we mean it.</p>
+you don’t want to read the deobfuscation information: we mean it.</p>
 <hr style="width:10%;text-align:left;margin-left:0">
 <p>The source file needs to be present because the words are read from
 it. The wordlist is encoded within the source using a 24 entry

1998/dorssel/README.md

@@ -112,7 +112,7 @@ is the same as
 ```
 
 - The file [dorssel.html](dorssel.html) contains all the information needed to
-understand this program.  For an obfuscated spoiler, try
+understand this program.  For deobfuscation information, try:
 
 ``` <!---sh-->
     ./dorssel < dorssel.md

1998/dorssel/index.html

@@ -468,7 +468,7 @@ text that can be reversibly Morsified, i.e.</li>
 <pre><code>    ./dorssel &lt; dorssel.c | ./dorssel</code></pre>
 <ul>
 <li>The file <a href="dorssel.html">dorssel.html</a> contains all the information needed to
-understand this program. For an obfuscated spoiler, try</li>
+understand this program. For deobfuscation information, try:</li>
 </ul>
 <pre><code>    ./dorssel &lt; dorssel.md</code></pre>
 <!--

1998/schnitzi/README.md

@@ -115,7 +115,8 @@ looping.  To see the resulting program run, redirect the output from
 
 and then compile it.
 
-### Spoilers And Hints:
+
+### Deobfuscation And Hints:
 
 The big key to this program is figuring out what the names of the
 functions ought to be; a bit of research may allow you to guess at

1998/schnitzi/index.html

@@ -470,7 +470,7 @@ looping. To see the resulting program run, redirect the output from
 <code>schnitzi</code> into another file, like this</p>
 <pre><code>    ./schnitzi 4 &gt; sort.c</code></pre>
 <p>and then compile it.</p>
-<h3 id="spoilers-and-hints">Spoilers And Hints:</h3>
+<h3 id="deobfuscation-and-hints">Deobfuscation And Hints:</h3>
 <p>The big key to this program is figuring out what the names of the
 functions ought to be; a bit of research may allow you to guess at
 a few crucial ones.</p>

1998/tomtorfs/README.md

@@ -99,7 +99,7 @@ Count the number of non-whitespace characters in the source
 file to find out what dark force drove me to write this ;-).
 
 
-### Spoiler
+### Deobfuscation
 
 First of all, if you run a C beautifier on the program (thereby of course losing
 the nice code shape I worked so hard on ;-) ) the code will become a bit more

1998/tomtorfs/index.html

@@ -445,7 +445,7 @@ valid exit value to indicate failure (replace them with <code>EOF</code> resp.
 <h3 id="special-notes">Special notes</h3>
 <p>Count the number of non-whitespace characters in the source
 file to find out what dark force drove me to write this ;-).</p>
-<h3 id="spoiler">Spoiler</h3>
+<h3 id="deobfuscation">Deobfuscation</h3>
 <p>First of all, if you run a C beautifier on the program (thereby of course losing
 the nice code shape I worked so hard on ;-) ) the code will become a bit more
 readable.</p>