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.

2001/anonymous/README.md

@@ -121,7 +121,7 @@ The build script should give an example command to compile the program.
 ### Features
 
 [Basic Block](https://en.wikipedia.org/wiki/Basic_block)
-[Cache](https://en.wikipedia.org/wiki/Cache_(computing)): Rather than
+[Cache](https://en.wikipedia.org/wiki/Cache_(computing)): Rather than
 translating each instruction individually the dynamic binary translator
 generates a translation for an entire basic block of subject code.  Having
 translated a block once, the target code generated will be stored for the
@@ -136,7 +136,7 @@ The program runs [dynamically
 linked](https://en.wikipedia.org/wiki/Dynamic_linker) [ELF
 binaries](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format), and
 when the subject program attempts to make a call to a standard
-[library](https://en.wikipedia.org/wiki/Library_(computing)), the translator
+[library](https://en.wikipedia.org/wiki/Library_(computing)), the translator
 attempts to make an appropriate call to the native system libraries on the
 target machine.  This involves mangling between different calling conventions,
 etc.
@@ -207,9 +207,9 @@ on to the next line of code.
 Due to space limitations only a handful of instructions are supported; these
 instructions which are supported are supported in somewhat non-conventional
 ways: chunks of the architecture (e.g. flags) are just ignored, the ELF
-[loader](https://en.wikipedia.org/wiki/Loader_(computing)) does not really load
+[loader](https://en.wikipedia.org/wiki/Loader_(computing)) does not really load
 the [ELF binary](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format),
-the target [library linking](https://en.wikipedia.org/wiki/Linker_(computing))
+the target [library linking](https://en.wikipedia.org/wiki/Linker_(computing))
 can only pass up to 3 parameters to the target library function, etc.
 
 In short, please consider this a full disclaimer for any bug that may

2001/dgbeards/README.md

@@ -160,7 +160,7 @@ program would probably be rated somewhere around 1700-1900.  It is better
 than most players, but will get destroyed by experienced human opponents.
 
 This program searches to a fixed depth of 3
-[ply](https://en.wikipedia.org/wiki/Ply_(game_theory)).  Because it does not
+[ply](https://en.wikipedia.org/wiki/Ply_(game_theory)).  Because it does not
 search very deep, it performs very poorly in quiet strategic positions.
 In such positions, it will often just shuffle pieces around aimlessly
 until a tactical exchange presents itself.