From c084776ff7e0d249fd26418c55edbcf31d5320c7 Mon Sep 17 00:00:00 2001 From: Bob Eagan Date: Fri, 24 Jan 2014 11:10:16 -0700 Subject: [PATCH] fix incorrect link --- docs/05-reusable-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/05-reusable-components.md b/docs/05-reusable-components.md index 83561f94..b3a3b6b8 100644 --- a/docs/05-reusable-components.md +++ b/docs/05-reusable-components.md @@ -123,7 +123,7 @@ var MyComponent = React.createClass({ Components are the best way to reuse code in React, but sometimes very different components may share some common functionality. These are sometimes called [cross-cutting concerns](http://en.wikipedia.org/wiki/Cross-cutting_concern). React provides `mixins` to solve this problem. -One common use case is a component wanting to update itself on a time interval. It's easy to use `setInterval()`, but it's important to cancel your interval when you don't need it anymore to save memory. React provides [lifecycle methods](/react/docs/working-with-the-browser.html) that let you know when a component is about to be created or destroyed. Let's create a simple mixin that uses these methods to provide an easy `setInterval()` function that will automatically get cleaned up when your component is destroyed. +One common use case is a component wanting to update itself on a time interval. It's easy to use `setInterval()`, but it's important to cancel your interval when you don't need it anymore to save memory. React provides [lifecycle methods](/react/docs/component-specs.html#lifecycle-methods) that let you know when a component is about to be created or destroyed. Let's create a simple mixin that uses these methods to provide an easy `setInterval()` function that will automatically get cleaned up when your component is destroyed. ```javascript /** @jsx React.DOM */