Improve markdown guidelines wording

Amongst the changes here is that we do not need to have the hex or html
code (numbers) for open and close parentheses (in links) as there are
names. '(' is & followed by lpar; and the ')' is the same but 'rpar;'
instead. This makes it easier to remember and type and it generates the
same html as well (they are all valid). Now the markdown files are
consistent in this (in some cases hex was used and in others the html
code).

Although many markdown files were updated no html files needed to be
updated as it generates the same html. Even so I ran the appropriate
rules to do so just to verify this.

2011/eastman/README.md

@@ -48,7 +48,7 @@ aren't familiar with it. Back in its day, this demo inspired lust and awe in
 geeks around the world.
 
 The graphics are
-[raytraced](https://en.wikipedia.org/wiki/Ray_tracing_(graphics)), with
+[raytraced](https://en.wikipedia.org/wiki/Ray_tracing_(graphics)), with
 procedural textures on the ball and the back wall.  I did cheat a little to
 simplify the calculations: it uses a parallel projection, but textures the back
 wall to look as if there were a floor being viewed in perspective.  The shadow