Point out bug in 2014/vik in years.html

This is to let the viewers know that sometimes the program will display
invalid input. The note is modelled after some of the other entries that
have bug reports. Okay it's also some shameless self promotion but never
mind that! :-)

As well a few minor changes in 2014/vik/README.md mostly being removing
double spaces in favour of single spaces (particularly in the general
text). There were some other formatting fixes as well.

In 2020/ferguson2/README.md I made a few adjustments as well (though I'm
aware of a few more changes in 2020/ferguson[12]/README.md I want to
make).

2014/vik/README.md

@@ -8,28 +8,33 @@ Daniel Vik
 ## Judges' comments:
 ### To build:
 
-    make
+	make all
 
 ### To run:
 
-    ./prog > foo.c
+	./prog > foo.c
 
 ### Try:
 
-    echo 'Want to hear me beep?' | ./prog  > audio_file.raw
+	echo 'Want to hear me beep?' | ./prog > audio_file.raw
+
+	echo 'No. I want chocolate!' | ./prog | mplayer -demuxer rawaudio -
 
-    echo 'No. I want chocolate!' | ./prog | mplayer -demuxer rawaudio -
 
 ### Selected Judges Remarks:
 
-This program sets a new tone for obfuscation.  But do you understand
-what it says about obfuscation?  Perhaps:
+This program sets a new tone for obfuscation. But do you understand
+what it says about obfuscation? Perhaps:
 
-    ./prog < prog.c > prog.raw
 
-might speak to your coding style?  If not, then perhaps:
+	./prog < prog.c > prog.raw
+
+
+might speak to your coding style? If not, then perhaps:
+
+
+	./prog < remarks.markdown | mplayer -demuxer rawaudio -
 
-    ./prog < remarks.markdown | mplayer -demuxer rawaudio -
 
 might help? :-)
 
@@ -42,41 +47,46 @@ I can tell, there are at least six chocolate references in this program.
 This program can convert text to Morse to a raw 44.1kHz stereo audio file.
 Via streaming to mplayer, you can listen to the Morse audio.
 
-Don't forget the last '-' as it makes mplayer read from stdin.)
+Don't forget the last '-' as it makes mplayer read from stdin.
+
 
 ## Convert audio file with Morse signals to text
 
-    $ ./prog e < audio_file.raw
+
+	$ ./prog e < audio_file.raw
+
 
 or alternatively pass a .wav file as input.
 
-The preferred input format 44.1kHz stereo,   but it does  a decent job on mono
-input and different frequencies  as well.
+The preferred input format 44.1kHz stereo, but it does a decent job on mono
+input and different frequencies as well.
+
 
 ### Portability
 
-The program is portable to most platforms. The only system  dependency is that
+The program is portable to most platforms. The only system dependency is that
 the program relies on writing binary data to stdout.
 
-Microsoft compilers adds a carriage  return to  newlines,   and to compile the
-program with this platform,   the following line  can be added  after the main
+Microsoft compilers add a carriage return to newlines, and to compile the
+program with this platform, the following line can be added after the main
 declaration in order for the program to run correctly:
 
-    _setmode(_fileno(stdout), 0x8000);
+
+	_setmode(_fileno(stdout), 0x8000);
 
 ### Known Issues
 
 The program uses a quite simple algorithm for detecting tone on and off events
-in the Morse signal.   Hence the program  does not work well  with noisy input
+in the Morse signal. Hence the program does not work well with noisy input
 signals. I have tested it with several samples of man made Morse recordings as
 well as computer generated ones.
 
-Generally, any recording from ham  radio transmissions  does not decode due to
-noise and echoes.   Other man made recordings may decode,  but some characters
-can be  incorrect  due to too big  variation  in length  of tones  and pauses.
+Generally, any recording from ham radio transmissions does not decode due to
+noise and echoes. Other man made recordings may decode, but some characters
+can be incorrect due to too big variation in length of tones and pauses.
 However I found some man made recordings on that decode reasonable well.
 
-If a recording don't decode,   you could try to  pre-process the input  with a
+If a recording doesn't decode, you could try to pre-process the input with a
 narrow bandpass filter on the frequency of the transmission.
 
 --------------------------------------------------------------------------------