Fixes in 1998 html files

This includes some notices to those who wish for a greater challenge.

In the 1998/schweikh3 the man page (and its copy to demonstrate the
entry) have been updated slightly but only in comment (move 'or' from
the command suggested to render it in text to its own line before the
next command also in comment).

The bugs file was updated for an entry or two.

bugs.md

@@ -1790,6 +1790,42 @@ There was no IOCCC in 1997.
 </div>
 <hr style="width:10%;text-align:left;margin-left:0">
 
+<div id="1998_chaos">
+## 1998/chaos
+</div>
+
+### STATUS: INABIAF - please **DO NOT** fix
+### Source code: [1998/chaos/chaos.c](%%REPO_URL%%/1998/chaos/chaos.c)
+### Information: [1998/chaos/index.html](1998/chaos/index.html)
+
+The author stated the following:
+
+> Memory `malloc(3)`ed is never freed.  This shouldn't be a big deal, since only
+one block is ever allocated, and the OS should recover it.
+>
+> My local flavor of lint doesn't seem to like the fact that I never `return`
+from `main()`.  Feh, what does it know?  Otherwise, ignoring lint's over
+protectiveness ("Of course I'm not using all of the functions defined in
+`curses.h`!"), it's lint clean.
+>
+>
+> If the compiler happens to generate the byte sequence "AlWuzEre" in the
+executable by chance, the program may be unable to locate the embedded string.
+As a result, running the program without an external data file may act in
+undefined ways.
+> If the compiler doesn't store `char * P`'s data in a nice contiguous stream,
+it would be bad.  As above, it would break running the program without an
+external data file.
+>
+> If the incoming data is corrupt, the results are undefined.  (Although dumping
+core is a popular result.)
+>
+> When a point passes behind the camera, it is still plotted.  The object will
+"bounce" off the camera, but the result (some points in front, some reflected
+from the rear) looks really odd.  And it sometimes hangs.  So just don't fly
+through objects.  You'll be happier.
+
+
 
 <div id="1998_dlowe">
 ## 1998/dlowe