Format fixes in html files in 2011

2011/fredriksson/README.md

@@ -149,10 +149,10 @@ Just say
 ### Limitations and remarks
 
 * Using warning options (such as `-Wall`) when building gives a lot of warning,
-  such as `suggest parentheses around '&&' within '||'`, `value computed is
-  not used`, `implicit declaration of function 'putchar'`, `implicit
-  declaration of function 'getchar'`, `control reaches end of non-void
-  function` and `format not a string literal and no format arguments`.
+  such as "`suggest parentheses around '&&' within '||'`", "`value computed is
+  not used`", "`implicit declaration of function 'putchar'`", "`implicit
+  declaration of function 'getchar'`", "`control reaches end of non-void
+  function`" and "`format not a string literal and no format arguments`".
   Please ignore them all, since they just try to tell you that the source
   is obfuscated.
 
@@ -184,17 +184,16 @@ Just say
   for each char, and that a C compiler is on `$PATH`; the latter is hard coded
   to be 'gcc', but any compiler would work, provided that it supports
   C99, or long lines as an extension. This code has been tested on:
+    - GNU/Linux FC4, i386, gcc
+    - GNU/Linux FC7, x86_64, gcc 4.1.2, tcc 0.9.24 and icc 10.0 (Btw, tcc has
+    its roots in IOCCC...)
+    - GNU/Linux FC9, x86_64, gcc 4.?.?
+    - GNU/Linux CentOS 5, gcc 4.1.2
+    - GNU/Linux Ubuntu 11.04, gcc 4.5.2
+    - SunOS 5.8, UltraSPARC IIIi, gcc 4.1.2
+    - SunOS 5.9, UltraSPARC IIIi, gcc 4.1.1 and Sun ONE Studio 8 CC
+    - AIX 5.3, IBM eServer p5-550, gcc 3.3.3 and AIX CC Version 6
 
-- GNU/Linux FC4, i386, gcc
-- GNU/Linux FC7, x86_64, gcc 4.1.2, tcc 0.9.24 and icc 10.0
-- GNU/Linux FC9, x86_64, gcc 4.?.?
-- GNU/Linux CentOS 5, gcc 4.1.2
-- GNU/Linux Ubuntu 11.04, gcc 4.5.2
-- SunOS 5.8, UltraSPARC IIIi, gcc 4.1.2
-- SunOS 5.9, UltraSPARC IIIi, gcc 4.1.1 and Sun ONE Studio 8 CC
-- AIX 5.3, IBM eServer p5-550, gcc 3.3.3 and AIX CC Version 6
-
-  (Btw, tcc has its roots in IOCCC...)
 
 
 ### NOTICE to those who wish for a greater challenge:
@@ -254,7 +253,7 @@ If you get stuck, come back and read below for additional hints and information.
 * It also shows the power of boolean logic and bitwise arithmetic.
 
 * This is the first (?) entry in the history of IOCCC, that cannot be
-  totally de-obfuscated by the author. This is due to the clever choice of
+  totally deobfuscated by the author. This is due to the clever choice of
   the actual algorithm, that is obfuscated by nature, and it is an open
   research problem whether a simpler algorithm exists, with the same time
   complexity.

2011/fredriksson/index.html

@@ -510,7 +510,7 @@ threshold, and search for “<code>ioccc</code>”, with option <code>-vk5</code
 <h3 id="limitations-and-remarks">Limitations and remarks</h3>
 <ul>
 <li><p>Using warning options (such as <code>-Wall</code>) when building gives a lot of warning,
-such as <code>suggest parentheses around '&amp;&amp;' within '||'</code>, <code>value computed is   not used</code>, <code>implicit declaration of function 'putchar'</code>, <code>implicit   declaration of function 'getchar'</code>, <code>control reaches end of non-void   function</code> and <code>format not a string literal and no format arguments</code>.
+such as “<code>suggest parentheses around '&amp;&amp;' within '||'</code>”, “<code>value computed is   not used</code>”, “<code>implicit declaration of function 'putchar'</code>”, “<code>implicit   declaration of function 'getchar'</code>”, “<code>control reaches end of non-void   function</code>” and “<code>format not a string literal and no format arguments</code>”.
 Please ignore them all, since they just try to tell you that the source
 is obfuscated.</p></li>
 <li><p>Only standard input is handled. And <em>only</em> if <code>stdin</code> comes from a file,
@@ -534,16 +534,18 @@ handle this just fine even in C89 mode, though.</p></li>
 <li><p>The code should be reasonably portable, it assumes standard ASCII codes
 for each char, and that a C compiler is on <code>$PATH</code>; the latter is hard coded
 to be ‘gcc’, but any compiler would work, provided that it supports
-C99, or long lines as an extension. This code has been tested on:</p></li>
-<li><p>GNU/Linux FC4, i386, gcc</p></li>
-<li><p>GNU/Linux FC7, x86_64, gcc 4.1.2, tcc 0.9.24 and icc 10.0</p></li>
-<li><p>GNU/Linux FC9, x86_64, gcc 4.?.?</p></li>
-<li><p>GNU/Linux CentOS 5, gcc 4.1.2</p></li>
-<li><p>GNU/Linux Ubuntu 11.04, gcc 4.5.2</p></li>
-<li><p>SunOS 5.8, UltraSPARC IIIi, gcc 4.1.2</p></li>
-<li><p>SunOS 5.9, UltraSPARC IIIi, gcc 4.1.1 and Sun ONE Studio 8 CC</p></li>
-<li><p>AIX 5.3, IBM eServer p5-550, gcc 3.3.3 and AIX CC Version 6</p>
-<p>(Btw, tcc has its roots in IOCCC…)</p></li>
+C99, or long lines as an extension. This code has been tested on:</p>
+<ul>
+<li>GNU/Linux FC4, i386, gcc</li>
+<li>GNU/Linux FC7, x86_64, gcc 4.1.2, tcc 0.9.24 and icc 10.0 (Btw, tcc has
+its roots in IOCCC…)</li>
+<li>GNU/Linux FC9, x86_64, gcc 4.?.?</li>
+<li>GNU/Linux CentOS 5, gcc 4.1.2</li>
+<li>GNU/Linux Ubuntu 11.04, gcc 4.5.2</li>
+<li>SunOS 5.8, UltraSPARC IIIi, gcc 4.1.2</li>
+<li>SunOS 5.9, UltraSPARC IIIi, gcc 4.1.1 and Sun ONE Studio 8 CC</li>
+<li>AIX 5.3, IBM eServer p5-550, gcc 3.3.3 and AIX CC Version 6</li>
+</ul></li>
 </ul>
 <h3 id="notice-to-those-who-wish-for-a-greater-challenge">NOTICE to those who wish for a greater challenge:</h3>
 <p><strong>If you want a greater challenge, don’t read any further</strong>:
@@ -596,7 +598,7 @@ variable definitions)</li>
 </ul></li>
 <li><p>It also shows the power of boolean logic and bitwise arithmetic.</p></li>
 <li><p>This is the first (?) entry in the history of IOCCC, that cannot be
-totally de-obfuscated by the author. This is due to the clever choice of
+totally deobfuscated by the author. This is due to the clever choice of
 the actual algorithm, that is obfuscated by nature, and it is an open
 research problem whether a simpler algorithm exists, with the same time
 complexity.</p></li>

2011/hamaji/README.md

@@ -32,7 +32,7 @@ This program solves [Nonograms](http://en.wikipedia.org/wiki/Nonogram) which is
 also known as "Paint by Numbers".
 
 This entry roars as the Year of the Dragon: A year considered
-some to be good luck.  Well it was certainly true that the
+by some to be good luck.  Well it was certainly true that the
 IOCCC was lucky to get such a fine submission!
 
 The source code is a solution to a Paint by Numbers puzzle when you

2011/hamaji/index.html

@@ -426,7 +426,7 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
 <p>This program solves <a href="http://en.wikipedia.org/wiki/Nonogram">Nonograms</a> which is
 also known as “Paint by Numbers”.</p>
 <p>This entry roars as the Year of the Dragon: A year considered
-some to be good luck. Well it was certainly true that the
+by some to be good luck. Well it was certainly true that the
 IOCCC was lucky to get such a fine submission!</p>
 <p>The source code is a solution to a Paint by Numbers puzzle when you
 paint by C. Try your hand at solving a few of the other <code>.nono</code>

2011/richards/README.md

@@ -69,7 +69,7 @@ You will probably get warnings while compiling the code. In particular:
 * I don't include any headers I don't strictly need to, so you'll get warnings
   about (at least) `memcpy()`, `isdigit()`, `atoi()`, `calloc()`, `malloc()`
   and `alloca()` if you didn't use `-DAH`.
-        - NOTE from judges: we added these includes in 2023.
+        - **NOTE from judges**: we added these includes in 2023.
 
 * GCC likes to complain about `while (a = b)` (assignments as a condition).
 
@@ -88,7 +88,7 @@ Platforms which work but not at all optimization levels or needing special
 flags:
 
  * owcc 1.9 + x86 + Windows: Needs `-DNM -DAH -fno-stack-check`
- * gcc 4.4.5 + sh4: -O0 works, higher optimization levels don't work for unknown reasons.
+ * gcc 4.4.5 + sh4: `-O0` works, higher optimization levels don't work for unknown reasons.
 
 
 <!--

2011/richards/index.html

@@ -452,7 +452,7 @@ compile flag <code>-DAH</code>.</p></li>
 about (at least) <code>memcpy()</code>, <code>isdigit()</code>, <code>atoi()</code>, <code>calloc()</code>, <code>malloc()</code>
 and <code>alloca()</code> if you didn’t use <code>-DAH</code>.</p>
 <ul>
-<li>NOTE from judges: we added these includes in 2023.</li>
+<li><strong>NOTE from judges</strong>: we added these includes in 2023.</li>
 </ul></li>
 <li><p>GCC likes to complain about <code>while (a = b)</code> (assignments as a condition).</p></li>
 <li><p>I don’t return from <code>main()</code>, even though it’s declared to return <code>int</code>.</p></li>
@@ -470,7 +470,7 @@ flags:</p>
 flags:</p>
 <ul>
 <li>owcc 1.9 + x86 + Windows: Needs <code>-DNM -DAH -fno-stack-check</code></li>
-<li>gcc 4.4.5 + sh4: -O0 works, higher optimization levels don’t work for unknown reasons.</li>
+<li>gcc 4.4.5 + sh4: <code>-O0</code> works, higher optimization levels don’t work for unknown reasons.</li>
 </ul>
 <!--
 

2011/toledo/README.md

@@ -82,6 +82,7 @@ you remove both the X11 include files and replace them with
 ```
 
 you ought to be able to compile and run this program on Windows.
+
 **NOTE**: this is what [toledo.alt2.c](%%REPO_URL%%/2011/toledo/toledo.alt2.c) is for.
 
 

2011/toledo/index.html

@@ -455,8 +455,8 @@ the source early on, right before the code gets hard to follow, or using the
 <p>Like Oscar’s previous winning X11 program for the 19th IOCCC, if
 you remove both the X11 include files and replace them with</p>
 <pre><code>    #include &quot;layer.c&quot;</code></pre>
-<p>you ought to be able to compile and run this program on Windows.
-<strong>NOTE</strong>: this is what <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.alt2.c">toledo.alt2.c</a> is for.</p>
+<p>you ought to be able to compile and run this program on Windows.</p>
+<p><strong>NOTE</strong>: this is what <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.alt2.c">toledo.alt2.c</a> is for.</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <pre><code>        /=========\\
         \==\   /==/                ||