From d30c0211c5393ee85479d6eb543d3f7f6bd3dfc8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Wed, 20 May 2015 10:15:35 -0700 Subject: [PATCH] [docs] Fix 404 due to relative url Closes #3914 --- docs/10.7-update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/10.7-update.md b/docs/10.7-update.md index f2466b04..4e3cf84d 100644 --- a/docs/10.7-update.md +++ b/docs/10.7-update.md @@ -8,7 +8,7 @@ next: pure-render-mixin.html React lets you use whatever style of data management you want, including mutation. However, if you can use immutable data in performance-critical parts of your application it's easy to implement a fast `shouldComponentUpdate()` method to significantly speed up your app. -Dealing with immutable data in JavaScript is more difficult than in languages designed for it, like [Clojure](http://clojure.org/). However, we've provided a simple immutability helper, `update()`, that makes dealing with this type of data much easier, *without* fundamentally changing how your data is represented. You can also take a look at Facebook's [Immutable-js](https://facebook.github.io/immutable-js/docs/) and the [Advanced Performance](react/docs/advanced-performance.html) section for more detail on Immutable-js. +Dealing with immutable data in JavaScript is more difficult than in languages designed for it, like [Clojure](http://clojure.org/). However, we've provided a simple immutability helper, `update()`, that makes dealing with this type of data much easier, *without* fundamentally changing how your data is represented. You can also take a look at Facebook's [Immutable-js](https://facebook.github.io/immutable-js/docs/) and the [Advanced Performance](/react/docs/advanced-performance.html) section for more detail on Immutable-js. ## The main idea