convert spoiler language and towards deobfuscation language

2018/burton2/index.html

@@ -506,11 +506,13 @@ whitespace surrounds English words, not necessarily C tokens, as in <code>a+=1;<
 designed to allow exhaustive, hand-counted values for comparison with the tool values.
 These test cases were vital in debugging and regression testing, and provided a way to
 determine which tool was correct when there were differences.</p>
-<pre><code>    A version of this tool in more clearly written C
-    is presented for the Judge&#39;s consideration as a more accurate replacement for `iocccsize`.
-    This obfuscated entry is derived from (and compatible with) that code,
-    but due to obfuscation, has had some significant, deep changes for the contest.
-    Nevertheless, the more clearly written code remains a spoiler for this entry.</code></pre>
+<blockquote>
+<p>A version of this tool in more clearly written C<br>
+is presented for the Judge’s consideration as a more accurate replacement for <code>iocccsize</code>.<br>
+This obfuscated entry is derived from (and compatible with) that code,<br>
+but due to obfuscation, has had some significant, deep changes for the contest.<br>
+Nevertheless, the more clearly written code remains deobfuscation information about this entry.</p>
+</blockquote>
 <p>NB: <code>iocccsize</code> gets a different answer from <code>tac</code> on its own
 <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/iocccsize.c">iocccsize.c</a> source code;
 <code>tac</code> gets the correct answer. This is due to the aforementioned bugs within <code>iocccsize</code>,