From a8e273f84416412fb26c36eb5b1a30a21917570a Mon Sep 17 00:00:00 2001 From: Jonas Gebhardt Date: Mon, 30 Jun 2014 10:41:42 -0700 Subject: [PATCH] fix link in community roundup #18 --- docs/_posts/2014-03-14-community-roundup-18.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_posts/2014-03-14-community-roundup-18.md b/docs/_posts/2014-03-14-community-roundup-18.md index ef08539ee39f7..275c8fc307db5 100644 --- a/docs/_posts/2014-03-14-community-roundup-18.md +++ b/docs/_posts/2014-03-14-community-roundup-18.md @@ -22,7 +22,7 @@ We're looking forward to part 2! ## React vs. async DOM manipulation -Eliseu Monar ([@eliseumds](https://twitter.com/eliseumds))'s post "[ReactJS vs async concurrent rendering](http://eliseu.tk/post/77843550010/vitalbox-pchr-reactjs-vs-async-concurrent-rendering)" is a great example of how React quite literally renders a whole array of common web development work(arounds) obsolete. +Eliseu Monar ([@eliseumds](https://twitter.com/eliseumds))'s post "[ReactJS vs async concurrent rendering](http://eliseumds.tumblr.com/post/77843550010/vitalbox-pchr-reactjs-vs-async-concurrent-rendering)" is a great example of how React quite literally renders a whole array of common web development work(arounds) obsolete.