From 60f4a5368d506c51c8976f78ca93c68737198060 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Wed, 13 Aug 2014 22:47:37 -0700 Subject: Typo fixes. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 16ba35c..5253eb6 100644 --- a/README.md +++ b/README.md @@ -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 -- cgit v1.2.3