sgit -e 's/Un\*x/Unix/g' -e 's/UN\*X/UNIX/g' .

This is not only to help with formatting - especially important in
markdown files -  but it's no longer really necessary to do it. One
might not feel the need to do it in non-markdown files but I did it
anyway to be consistent. Thus instead of showing Un*x/UN*X it shows
Unix/UNIX.

A question of whether or not it should all be the same case is another
thing entirely but if this is desired at some point it should be easy to
do anyway - with some care in case it's in formatted text.

A note about the glob: why '.' when there are C files and other file
types where it could be dangerous to modify? Because I did a git grep
first so I knew that it was safe.

1989/rules.txt

@@ -154,12 +154,12 @@ POINTS TO PONDER:
 	We tend to dislike programs that:
 
 		* are very hardware specific
-		* are very OS or Un*x version specific
+		* are very OS or Unix version specific
 		     (index/strchr differences are ok, but 
 		      socket/streams specific code is likely not to be)
 		* dump core or have compiler warnings
 		     (it is ok only if you warn us in the 'remark' header item)
-		* won't compile under both BSD or SYS V Un*x
+		* won't compile under both BSD or SYS V Unix
 		* use an excessively long compile line to get around the
 		     size limit
 		* are longer than they need to be