From ce44eb69219f0e99c390d81e022ace51be059129 Mon Sep 17 00:00:00 2001 From: olivia Date: Tue, 20 Feb 2018 20:03:58 +0100 Subject: [PATCH] fix broken link in maintainer blog post --- .../_posts/2018-02-19-meet-jekyll-s-new-lead-developer.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_posts/2018-02-19-meet-jekyll-s-new-lead-developer.markdown b/docs/_posts/2018-02-19-meet-jekyll-s-new-lead-developer.markdown index 95beb1fd..46011ed1 100644 --- a/docs/_posts/2018-02-19-meet-jekyll-s-new-lead-developer.markdown +++ b/docs/_posts/2018-02-19-meet-jekyll-s-new-lead-developer.markdown @@ -20,7 +20,7 @@ Node.js community, both online and as a volunteer organizer with JSConf EU. In my conversations with Olivia, it is clear that Jekyll's vision of simplicity for the user ([no magic!](/philosophy#1-no-magic)) and letting -users' [content be king](/philosphy#3-content-is-king) will remain a top +users' [content be king](/philosophy#3-content-is-king) will remain a top priority. In just the last few weeks as the transition has been occurring, we have seen some incredible work on performance that will make future versions of Jekyll work better at scale. She will be prioritizing work on