Reword the recent deobfuscation changes

In most cases the word was changed to 'obfuscation' as it was about
obfuscation, not deobfuscation. In some cases like 1995/leo since the
file was (in 1995/leo) about a secret switch it was changed to
'secret.md' (and 'secret.html') but there were others like that as well.

One entry had the words 'spoiling the size rule' but this had been
changed to 'deobfuscating the size rule' which was obviously wrong.

In the latter YYYY/README.md files the judges had written after some
entries (brief summaries) '...

    ...We'll stop spouting spoilers now. Have fun exploring all the
    entries!

but that was changed to:

    ...We'll stop spouting deobfuscation information now. Have fun
    exploring all the entries!

which wasn't really about deobfuscation but just a brief summary of what
the entries did.

And in the most problematic case (at least for me :-), 2018/ferguson) I
had put a joke in:

    ... but it's the only Easter egg I won't spoil

but it was changed to 'won't deobfuscate' which not only is not what it
is but it spoilt the joke.

In some cases the word was changed back to 'SPOILER' (or similar) but in
most cases not. I believe it should be better now. There are some
caveats, however, as below.

Although make find_missing_links is okay I do not remember if this will
catch links that refer to '%%REPO_URL%%' or other pandoc tokens. This
means I might have to go back to some earlier years to verify links are
okay. That should not take that much time I hope.

It might also be that some wording can still be improved some but it is
hoped this will be discovered when checking links and looking over the
manifest (which obviously changed).

2012/endoh1/README.md

@@ -259,7 +259,7 @@ a usage of `I` (complex's imaginary unit), but I bet this is cygwin's issue;
 it is surely a C99 feature.
 
 
-### Deobfuscation
+### Obfuscation
 
 First of all, the source code itself serves as an initial configuration.
 Preprocessing directives (such as `#include`)'s `#` serve as walls.

2012/endoh1/index.html

@@ -554,7 +554,7 @@ used to clear screen and move cursor to home.</p>
 and gcc-4.5.3 and clang-3.1 on Cygwin. On Cygwin, gcc and clang complain about
 a usage of <code>I</code> (complex’s imaginary unit), but I bet this is cygwin’s issue;
 it is surely a C99 feature.</p>
-<h3 id="deobfuscation">Deobfuscation</h3>
+<h3 id="obfuscation">Obfuscation</h3>
 <p>First of all, the source code itself serves as an initial configuration.
 Preprocessing directives (such as <code>#include</code>)’s <code>#</code> serve as walls.</p>
 <p>This program uses <code>double complex</code> to represent any 2D vector. But, note that

2012/kang/README.md

@@ -150,7 +150,7 @@ The design of the program explicitly allows for `EOF` even if it does not equal
 endian-independent.
 
 
-### Debfuscation
+### Obfuscation
 
 Many obfuscations used are typical for standard IOCCC entries:
 
@@ -218,7 +218,7 @@ Having said this important trick, other details should be relatively easier to
 follow. The order of lookup table, for example, is very important,
 and the biggest constant 6177 is not arbitrarily chosen.
 
-Even [more deobfuscation information](https://gist.github.com/lifthrasiir/3909337) is available.
+Even more obfuscation information is [available](https://gist.github.com/lifthrasiir/3909337).
 
 
 ### Acknowledgement

2012/kang/index.html

@@ -493,7 +493,7 @@ character set and two’s complement representation.</li>
 <code>-1</code> (it has to be negative per the standard but not necessarily <code>-1</code>) and both
 <code>signed char</code> and <code>unsigned char</code>, for example. Furthermore it is
 endian-independent.</p>
-<h3 id="debfuscation">Debfuscation</h3>
+<h3 id="obfuscation">Obfuscation</h3>
 <p>Many obfuscations used are typical for standard IOCCC entries:</p>
 <ul>
 <li>Two arguments from <code>main()</code> function are reused as normal variables.</li>
@@ -547,7 +547,7 @@ one character.</li>
 <p>Having said this important trick, other details should be relatively easier to
 follow. The order of lookup table, for example, is very important,
 and the biggest constant 6177 is not arbitrarily chosen.</p>
-<p>Even <a href="https://gist.github.com/lifthrasiir/3909337">more deobfuscation information</a> is available.</p>
+<p>Even more obfuscation information is <a href="https://gist.github.com/lifthrasiir/3909337">available</a>.</p>
 <h3 id="acknowledgement">Acknowledgement</h3>
 <p>The cleaner (size-optimized) version of this program was originally published
 in my website in July 2011. Sun Park and others have reviewed it and made me

2012/omoikane/.entry.json

@@ -66,12 +66,12 @@
 	    "entry_text" : "script to try entry"
 	},
 	{
-	    "file_path" : "deobfuscation.html",
+	    "file_path" : "obfuscation.html",
 	    "inventory_order" : 200,
 	    "OK_to_edit" : true,
 	    "display_as" : "html",
 	    "display_via_github" : false,
-	    "entry_text" : "Deobfuscation information web page"
+	    "entry_text" : "JavaScript page with full recording of development"
 	},
 	{
 	    "file_path" : "2012_omoikane.tar.bz2",

2012/omoikane/README.md

@@ -83,7 +83,7 @@ We have no way to test the second version, sorry (tm Canada :-) )!
 ## Judges' remarks:
 
 The judges have nothing to add that has not already been written about in the
-[deobfuscation.html](deobfuscation.html) (requires JavaScript) file!  :-)
+[obfuscation.html](obfuscation.html) (requires JavaScript) file!  :-)
 
 
 ## Author's remarks:
@@ -195,7 +195,7 @@ default, this means `Nyaruko` may not faithfully encode files on MingW.
 
 ### Extra files
 
-[deobfuscation.html](deobfuscation.html) - Contains full recording of how the code went from
+[obfuscation.html](obfuscation.html) - Contains full recording of how the code went from
 blank state to an obfuscated program, gzipped to fit under 1MB. Requires
 JavaScript.
 

2012/omoikane/index.html

@@ -443,7 +443,7 @@ binary mode on <code>stdin</code> and <code>stdout</code>.</p>
 <p>We have no way to test the second version, sorry (tm Canada :-) )!</p>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>The judges have nothing to add that has not already been written about in the
-<a href="deobfuscation.html">deobfuscation.html</a> (requires JavaScript) file! :-)</p>
+<a href="obfuscation.html">obfuscation.html</a> (requires JavaScript) file! :-)</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <h3 id="usage">Usage</h3>
 <p><code>Nyaruko</code> is a binary to text filter. Given some input on <code>stdin</code>,
@@ -524,7 +524,7 @@ combinations:</p>
 <p>Note that on MingW, <code>stdin</code> and <code>stdout</code> are not opened in binary mode by
 default, this means <code>Nyaruko</code> may not faithfully encode files on MingW.</p>
 <h3 id="extra-files">Extra files</h3>
-<p><a href="deobfuscation.html">deobfuscation.html</a> - Contains full recording of how the code went from
+<p><a href="obfuscation.html">obfuscation.html</a> - Contains full recording of how the code went from
 blank state to an obfuscated program, gzipped to fit under 1MB. Requires
 JavaScript.</p>
 <!--
@@ -559,7 +559,7 @@ JavaScript.</p>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/omoikane/omoikane.c">omoikane.c</a> - entry source code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/omoikane/try.alt.sh">try.alt.sh</a> - script to try alternate code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/omoikane/try.sh">try.sh</a> - script to try entry</li>
-<li><a href="deobfuscation.html">deobfuscation.html</a> - Deobfuscation information web page</li>
+<li><a href="obfuscation.html">obfuscation.html</a> - JavaScript page with full recording of development</li>
 </ul>
 <h2 id="secondary-files">Secondary files</h2>
 <ul>

2012/tromp/.entry.json

@@ -39,7 +39,7 @@
 	    "OK_to_edit" : false,
 	    "display_as" : "html",
 	    "display_via_github" : false,
-	    "entry_text" : "author supplied debofuscation information"
+	    "entry_text" : "author supplied obfuscation information"
 	},
 	{
 	    "file_path" : "primes.pl",

2012/tromp/how.html

@@ -383,7 +383,7 @@
 <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 
 <!-- BEFORE: 1st line of markdown file: 2012/tromp/how.md -->
-<h1 id="deobfuscation">Deobfuscation</h1>
+<h1 id="obfuscation">Obfuscation</h1>
 <p>The program implements a so called <a href="https://en.wikipedia.org/wiki/Krivine_machine">Krivine
 machine</a>, enhanced with a <a href="https://en.wikipedia.org/wiki/BIOS">basic
 input/output system</a> and a reference

2012/tromp/how.md

@@ -1,4 +1,4 @@
-# Deobfuscation
+# Obfuscation
 
 The program implements a so called [Krivine
 machine](https://en.wikipedia.org/wiki/Krivine_machine), enhanced with a [basic

2012/tromp/index.html

@@ -787,7 +787,7 @@ Higher Order Symbol. Comput. 20, 3 (September 2007), 199-207.
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/tromp.c">tromp.c</a> - entry source code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/Makefile">Makefile</a> - entry Makefile</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/tromp.orig.c">tromp.orig.c</a> - original source code</li>
-<li><a href="how.html">how.html</a> - author supplied debofuscation information</li>
+<li><a href="how.html">how.html</a> - author supplied obfuscation information</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/primes.pl">primes.pl</a> - post process entry output to print primes</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/try.sh">try.sh</a> - script to try entry</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2012/tromp/hw.bf">hw.bf</a> - hello world brainfuck source code</li>