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/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>