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

2019/adamovsky/.entry.json

@@ -58,12 +58,12 @@
 	    "entry_text" : "unlambda script"
 	},
 	{
-	    "file_path" : "deobfuscation.c",
+	    "file_path" : "deobfuscated.c",
 	    "inventory_order" : 200,
 	    "OK_to_edit" : true,
 	    "display_as" : "c",
 	    "display_via_github" : true,
-	    "entry_text" : "Deobfuscated source code"
+	    "entry_text" : "deobfuscated source code"
 	},
 	{
 	    "file_path" : "iocccsize_2018.c",

2019/adamovsky/README.md

@@ -162,7 +162,7 @@ and the call with current continuation `c`.
 is, how the state of the program is stored and how the Unlambda functions are
 implemented.
 
-More on this in the **Deobfuscation** section.
+More on this in the **Obfuscation** section.
 
 
 ### Build notes:
@@ -197,9 +197,9 @@ for storing `char`s for later printing. This might produce some warnings, but
 since it was developed using `char`s it should be always used safely.
 
 
-### Deobfuscation:
+### Obfuscation:
 
-- You can examine the [deobfuscation.c](%%REPO_URL%%/2019/adamovsky/deobfuscation.c) file. It is the original
+- You can examine the [deobfuscated.c](%%REPO_URL%%/2019/adamovsky/deobfuscated.c) file. It is the original
 final version of the interpreter, before I started the downsizing. It accepts
 one more optional parameter that specifies a filename for the output Unlambda
 function (it's the Unlambda function that remains after all function
@@ -254,13 +254,13 @@ were shuffled both for `S` functions and Apply functions in the same way to hide
 the meaning of `f` and `r` prefixes.
 
 
-### Identification deobfuscation:
+### Identification spoiler:
 
 The alternative build path `make identify` output commemorates a [previous IOCCC
 winning entry][9] which uses similar methods to mess with the size tool.
 
 
-### Judges' debobfuscaiton:
+### Judges' spoiler:
 
 It is not a bug, it is a feature. :)
 

2019/adamovsky/index.html

@@ -496,7 +496,7 @@ and the call with current continuation <code>c</code>.</li>
 is, how the state of the program is stored and how the Unlambda functions are
 implemented.</li>
 </ul>
-<p>More on this in the <strong>Deobfuscation</strong> section.</p>
+<p>More on this in the <strong>Obfuscation</strong> section.</p>
 <h3 id="build-notes">Build notes:</h3>
 <p>The program does not require any special treatment by compilers. Some warnings
 had to be suppressed when compiling with <code>-Wall -Wextra -pedantic</code>. Those were
@@ -524,9 +524,9 @@ world situation even when <code>size_t</code> is bigger than <code>long long</co
 for storing <code>char</code>s for later printing. This might produce some warnings, but
 since it was developed using <code>char</code>s it should be always used safely.</li>
 </ul>
-<h3 id="deobfuscation">Deobfuscation:</h3>
+<h3 id="obfuscation">Obfuscation:</h3>
 <ul>
-<li><p>You can examine the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/deobfuscation.c">deobfuscation.c</a> file. It is the original
+<li><p>You can examine the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/deobfuscated.c">deobfuscated.c</a> file. It is the original
 final version of the interpreter, before I started the downsizing. It accepts
 one more optional parameter that specifies a filename for the output Unlambda
 function (it’s the Unlambda function that remains after all function
@@ -570,10 +570,10 @@ continuation and exit functions were swapped. The names of <code>S</code> and Ap
 were shuffled both for <code>S</code> functions and Apply functions in the same way to hide
 the meaning of <code>f</code> and <code>r</code> prefixes.</p></li>
 </ul>
-<h3 id="identification-deobfuscation">Identification deobfuscation:</h3>
+<h3 id="identification-spoiler">Identification spoiler:</h3>
 <p>The alternative build path <code>make identify</code> output commemorates a <a href="../../2014/birken/index.html" title="Best use of port 1701">previous IOCCC
 winning entry</a> which uses similar methods to mess with the size tool.</p>
-<h3 id="judges-debobfuscaiton">Judges’ debobfuscaiton:</h3>
+<h3 id="judges-spoiler">Judges’ spoiler:</h3>
 <p>It is not a bug, it is a feature. :)</p>
 <p>The crash is caused by a stack overflow. Conventional Unlabmda interpreters
 implement the Unlambda execution stack using data structures on the heap. This
@@ -623,7 +623,7 @@ be applied.</p>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/try.sh">try.sh</a> - script to try entry</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/advent.unl">advent.unl</a> - unlambda script</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/crash.unl">crash.unl</a> - unlambda script</li>
-<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/deobfuscation.c">deobfuscation.c</a> - Deobfuscated source code</li>
+<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/deobfuscated.c">deobfuscated.c</a> - deobfuscated source code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/iocccsize_2018.c">iocccsize_2018.c</a> - 2018 iocccsize.c source</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/sierpinski.unl">sierpinski.unl</a> - unlambda code</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/spam.unl">spam.unl</a> - unlambda code</li>