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.

1984/rules.txt

@@ -6,7 +6,7 @@ from both Landon Curt Noll and Larry Bassel.
 
 I'm sure you have all seen gross, or down right structurally obscene C
 source code before.  Some people who deal with various parts of the
-UN*X  source wonder if some folks try rather hard to produce such
+UNIX  source wonder if some folks try rather hard to produce such
 down right smelly code.
 
 Now you have the chance to compete with the worst C hackers around
@@ -37,7 +37,7 @@ but dont let the lack of a 780 or 4.2 discourage you!
 
 chongo <flames about the contest will be kindly #ifdef'ed out> /\CC/\
 
-UN*X is a trademark of Usenet Hackers Anonymous
+UNIX is a trademark of Usenet Hackers Anonymous
 
 WARNING: The rules and mailing address for the contest change from year
          to year.  Be sure that you consult the current set of rules