diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2014-08-13 22:47:37 -0700 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2014-08-13 22:56:33 -0700 |
| commit | 60f4a5368d506c51c8976f78ca93c68737198060 (patch) | |
| tree | 3e2e9c30cd377abb14567840e685beb1eab8eeb0 | |
| parent | d612fe464bfc7f298a790d2e2f4101f23244042d (diff) | |
Typo fixes.
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -81,10 +81,10 @@ syntax for line breaks and fenced code blocks. In all of this, I have been guided by eight years experience writing markdown implementations in several languages, including the first markdown parser not based on regular expression substitutions -([pandoc](http://github.com/jgm/pandoc) and the first markdown parsers +([pandoc](http://github.com/jgm/pandoc)) and the first markdown parsers based on PEG grammars ([peg-markdown](http://github.com/jgm/peg-markdown), -[lunamark](http://github.com/jgm/lunamark). Maintaining these projects +[lunamark](http://github.com/jgm/lunamark)). Maintaining these projects and responding to years of user feedback have given me a good sense of the complexities involved in parsing markdown, and of the various design decisions that can be made. I have also explored differences between |