replace trailing whitespace with blackslash in README.md

As an alternative to the markdown trailing whitespace as a line
break, we use a trailing blackslash as a markdown line break.

1994/shapiro/README.md

@@ -1,9 +1,9 @@
 # Most Well Rounded Obfuscation
 
-Andrew T. Shapiro  
-CSES/CIRES University of Colorado  
-Campus Box 216  
-Boulder, CO 80309-0216  
+Andrew T. Shapiro\
+CSES/CIRES University of Colorado\
+Campus Box 216\
+Boulder, CO 80309-0216\
 US
 
 
@@ -58,29 +58,29 @@ The basic theme (pun) of this program is:
 >       ~~~~
 
 
-My entry ([shapiro.c](shapiro.c)) is mostly comment, formatted in the shape of a 
-clock. If you strip out the comments and look at the code you will 
-quickly realize that the comments were the important part and that 
-the code does very little (see pun above). It writes (to stdout) 
-another C program ([shapiro_t2.c](shapiro_t2.c)). This is the first level of 
+My entry ([shapiro.c](shapiro.c)) is mostly comment, formatted in the shape of a\
+clock. If you strip out the comments and look at the code you will\
+quickly realize that the comments were the important part and that\
+the code does very little (see pun above). It writes (to stdout)\
+another C program ([shapiro_t2.c](shapiro_t2.c)). This is the first level of\
 obfuscation.
 
 The second program ([shapiro_t2.c](shapiro_t2.c) if you use the Makefile
 prints a clock in the upper right hand corner of your VTxxx/ANSI display.
 
 Most of the surface obfuscation in the second program
-([shapiro_t2.c](shapiro_t2.c)) 
-was an attempt to make it as small as possible. You should be able to 
-see around this with cb(1) and some more intelligent variable names. 
-Once you get past this you will realize that the third level of 
-obfuscation is a six member client/server hierarchy. 
+([shapiro_t2.c](shapiro_t2.c))\
+was an attempt to make it as small as possible. You should be able to\
+see around this with cb(1) and some more intelligent variable names.\
+Once you get past this you will realize that the third level of\
+obfuscation is a six member client/server hierarchy.\
 (See the [shapiro.md](shapiro.md) file for a detailed description of the
 algorithm.)
 
 `lint` complains about: precedence confusion, `K` may be used before set,
-main() returns random value to invocation environment, value type used 
-inconsistently, value type declared inconsistently, function argument 
-(number) used inconsistently, function returns value which is always 
+main() returns random value to invocation environment, value type used\
+inconsistently, value type declared inconsistently, function argument\
+(number) used inconsistently, function returns value which is always\
 ignored, function returns value which is sometimes ignored.
 All of which are harmless (famous last words).