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).

2013/endoh1/README.md

@@ -106,7 +106,7 @@ and to satisfy IOCCC's size rule.
 
 These led to the good obfuscation.
 
-See the [deobfuscation section](#Deobfuscation) in detail, if you need.
+See the [obfuscation section](#obfuscation) in detail, if you need.
 
 
 ### Limitation
@@ -120,7 +120,7 @@ Also, it requires a space between identifiers.  In short, use `(S K)` instead of
 Huge memory may be required to compile the program (about 300 MB on my machine).
 
 In addition, there are some limitations (and workarounds) mentioned in
-the [deobfuscation section](#Deobfuscation).
+the [obfuscation section](#obfuscation).
 
 But I think it would only matter when you run the attached programs.
 
@@ -156,7 +156,7 @@ run it as a standalone program, at least.  In fact, tcc does not support the
 macro, but does work.
 
 
-### Deobfuscation
+### Obfuscation
 
 The whole program is interpreted by macro expansion.
 For example, `S (K I)` is translated to a normal C code, `(s)((k)(i))`, or

2013/endoh1/index.html

@@ -450,7 +450,7 @@ and to satisfy IOCCC’s size rule.</p>
 <li>Short coding.</li>
 </ul>
 <p>These led to the good obfuscation.</p>
-<p>See the <a href="#Deobfuscation">deobfuscation section</a> in detail, if you need.</p>
+<p>See the <a href="#obfuscation">obfuscation section</a> in detail, if you need.</p>
 <h3 id="limitation">Limitation</h3>
 <p>This program supports only “Combinator-calculus style notation” of Lazy K.
 “Unlambda style” and “Iota and Jot” style are not supported.</p>
@@ -458,7 +458,7 @@ and to satisfy IOCCC’s size rule.</p>
 <code>(SK)</code>, “`sk”, <code>**i*i*i*ii*i*i*ii</code>, or <code>11111100011100</code>.</p>
 <p>Huge memory may be required to compile the program (about 300 MB on my machine).</p>
 <p>In addition, there are some limitations (and workarounds) mentioned in
-the <a href="#Deobfuscation">deobfuscation section</a>.</p>
+the <a href="#obfuscation">obfuscation section</a>.</p>
 <p>But I think it would only matter when you run the attached programs.</p>
 <h3 id="portability">Portability</h3>
 <p>I confirmed that the program successfully worked with the following compilers:</p>
@@ -486,7 +486,7 @@ It is a gcc extension, and also supported by clang. If your compiler does not
 support it, you cannot use the program as a library. But you can compile and
 run it as a standalone program, at least. In fact, tcc does not support the
 macro, but does work.</p>
-<h3 id="deobfuscation">Deobfuscation</h3>
+<h3 id="obfuscation-1">Obfuscation</h3>
 <p>The whole program is interpreted by macro expansion.
 For example, <code>S (K I)</code> is translated to a normal C code, <code>(s)((k)(i))</code>, or
 simply <code>s(k(i))</code>.</p>

2013/endoh2/README.md

@@ -62,7 +62,7 @@ I believe that the JPEG encoder is the world's smallest ever.
 Nevertheless, the program was too big to meet the IOCCC's size rule.  So I
 created a smaller bootstrap program that generates the main program.  `endoh2.c`
 contains fragments of the main program *as a comment* which `iocccsize -i` does
-*not* count.  I gratefully thank the judges for deobfuscating the size rule this
+*not* count.  I gratefully thank the judges for spoiling the size rule this
 year.
 
 I think the program will work on any major platforms and compilers.

2013/endoh2/index.html

@@ -441,7 +441,7 @@ I believe that the JPEG encoder is the world’s smallest ever.</p>
 <p>Nevertheless, the program was too big to meet the IOCCC’s size rule. So I
 created a smaller bootstrap program that generates the main program. <code>endoh2.c</code>
 contains fragments of the main program <em>as a comment</em> which <code>iocccsize -i</code> does
-<em>not</em> count. I gratefully thank the judges for deobfuscating the size rule this
+<em>not</em> count. I gratefully thank the judges for spoiling the size rule this
 year.</p>
 <p>I think the program will work on any major platforms and compilers.</p>
 <h3 id="legal">Legal</h3>

2013/endoh3/README.md

@@ -181,7 +181,7 @@ For the same reason, do not post a score that contains only `z1092`.
 You know, it is ["the famous song"](http://en.wikipedia.org/wiki/4%E2%80%B233%E2%80%B3).
 
 
-### Deobfuscation
+### Spoiler
 
 Here is a magical expression which I found by brute-force:
 

2013/endoh3/index.html

@@ -516,7 +516,7 @@ such as <code>C2E2</code>.</p>
 But I do not attach it to protect you from W****r.</p>
 <p>For the same reason, do not post a score that contains only <code>z1092</code>.
 You know, it is <a href="http://en.wikipedia.org/wiki/4%E2%80%B233%E2%80%B3">“the famous song”</a>.</p>
-<h3 id="deobfuscation">Deobfuscation</h3>
+<h3 id="spoiler">Spoiler</h3>
 <p>Here is a magical expression which I found by brute-force:</p>
 <pre><code>    (c % 32 + 5) * 9 / 5 % 13 + n / 32 * 12 - 22</code></pre>
 <p>Interestingly, it converts an ASCII number of ABC notes

2013/hou/README.md

@@ -192,7 +192,7 @@ quite memory consuming, requires IEEE754-compliant `double`, and assumes `int` t
 doesn't copy saved sessions across different endianness.
 
 
-### Deobfuscation
+### Spoiler
 
 ```
     3225  3225  3225  9  9    3225  3225

2013/hou/index.html

@@ -538,7 +538,7 @@ quite memory consuming, requires IEEE754-compliant <code>double</code>, and assu
 <li>Though technically endian-dependent, <code>a.c</code> remains portable providing that one
 doesn’t copy saved sessions across different endianness.</li>
 </ul>
-<h3 id="deobfuscation">Deobfuscation</h3>
+<h3 id="spoiler">Spoiler</h3>
 <pre><code>    3225  3225  3225  9  9    3225  3225
     1     1  1  1  1  1  1    1     1  1
     4225  1226  1  1  1  1    1222  1226

2013/misaka/.entry.json

@@ -50,12 +50,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" : "2013_misaka.tar.bz2",

2013/misaka/Makefile

@@ -115,7 +115,7 @@ PROG= ${ENTRY}
 #
 OBJ= misaka.o misaka2.o misaka3.o misaka4.o misaka5.o \
         misaka6.o misaka7.o misaka8.o misaka9.o
-DATA= bf.pl deobfuscation.html
+DATA= bf.pl obfuscation.html
 TARGET= ${PROG} horizontal_cat vertical_cat long_cat loong_cat \
 	loooong_cat loooooooong_cat long_fat_cat \
 	long_faat_cat same_as_long_cat

2013/misaka/README.md

@@ -263,7 +263,7 @@ needed for the program to work.
 
 * [bf.pl](%%REPO_URL%%/2013/misaka/bf.pl) - a perl brainfuck interpreter, in case you don't have one
 handy.
-* [deobfuscation.html](deobfuscation.html) - making of this program.
+* [obfuscation.html](obfuscation.html) - making of this program.
 
 
 ### About `Misaka`

2013/misaka/index.html

@@ -562,7 +562,7 @@ needed for the program to work.</p>
 <ul>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/misaka/bf.pl">bf.pl</a> - a perl brainfuck interpreter, in case you don’t have one
 handy.</li>
-<li><a href="deobfuscation.html">deobfuscation.html</a> - making of this program.</li>
+<li><a href="obfuscation.html">obfuscation.html</a> - making of this program.</li>
 </ul>
 <h3 id="about-misaka">About <code>Misaka</code></h3>
 <p>The name, layout, and functionality of <code>Misaka</code> is inspired by a particular
@@ -601,7 +601,7 @@ stackable figure:</p>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/misaka/misaka.orig.c">misaka.orig.c</a> - original source code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/misaka/bf.pl">bf.pl</a> - brainfuck interpreter in perl</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/misaka/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>