Fixed a few typos in the README.

README.md

@@ -9,15 +9,15 @@ Additionally, the arithmetic operators (+ - * < >) are all axis aligned... unlik
 
 
 # Proggy Vector
-New for 2019 is a vector (scalable) version of Proggy Clean Slashed-Zero. The "ProggyVector Regular" font is a modified version of the Hack Font. It comes in woff, svg, eot, ttf (with Mac variants), and otf (with Mac variants). Here is a sample.
+New for 2019 is a vector (scalable) version of Proggy Clean Slashed-Zero. Proggy Vector comes in woff, svg, eot, ttf (with Mac variants), and otf (with Mac variants). Here is a sample.
 
 ![Proggy Vector](https://raw.githubusercontent.com/bluescan/proggyfonts/master/ProggyVector/ProggyVector_Sample.png)
 
-The modifications were made using the Bird Font editor. Both the modifications made by SourceFoundry for Hack and my subsequent modifications are licensed under MIT. However, Hack started life out elsewhere, so please read the licensing information in ProggyVector_Readme_And_Licensing.txt. There's nothing arduous.
+Proggy Vector Regular is a modified version of the Hack Font. The modifications were made using the Bird Font editor. Both the modifications made by SourceFoundry for Hack and my subsequent modifications are licensed under MIT. However, Hack started life out elsewhere, so please read the licensing information in ProggyVector_Readme_And_Licensing.txt. There's nothing arduous.
 
-I have ONLY tested the non-Mac ttf and otf files in Windows. I have NOT tested the included svg, eot, and woff files. The web format woff file was generated by importing the otf into FontForge and exporting. I have also included the BirdFont (.birdfont) project file in case anyone would like to make further edits.
+The web format woff file was generated by importing the otf into FontForge and exporting. I have also included the BirdFont (.birdfont) project file in case anyone would like to make further edits.
 
-In my opinion, Windows did a better job rendering the ttf version over the otf version (even though the otf supports cubic beziers which should not be approximations of the authored curves). Point size 10 works well for me in Visua Studio. Here's a sample.
+Windows appears to do a better job rendering ttf fonts over otf versions (even though otf supports cubic beziers which should not be approximations of the authored curves). Point size 10 of the ttf works well for me in Visual Studio. Here's a sample.
 
 ![Proggy Vector](https://raw.githubusercontent.com/bluescan/proggyfonts/master/ProggyVector/ProggyVector_SampleVS.png)
 
@@ -26,7 +26,7 @@ Note the 100% at the lower left. If magnification is not set to 100% the text wi
 
 # Proggy Original
 
-The original fonts are distributed as ttf, fon, pcf, and dfont files. The fon format works well with Visual Studio, a command prompt, Photoshop, etc. Some editors do not recognize fon fonts in which case you should use the ttf version (12pt PC, 16pt Mac). Not all fonts are available in all formats.
+The original bitmap fonts are distributed as ttf, fon, pcf, and dfont files. The fon format works well with Visual Studio, a command prompt, Photoshop, etc. Some editors do not recognize fon fonts in which case you should use the ttf version (12pt PC, 16pt Mac). Not all fonts are available in all formats.
 
 The original fonts are pixel-based and only look good at a particular point size. The ttf fonts should be used at their intended point size as they are basically conversions of the pixel based bitmap versions. 
 These fonts will not benefit form having ClearType turned on. You're better off using some other ttf font that is curve-based and not pixel-based if you want sub-pixel anti-aliasing.