From a9e07a8b3c36eb49e5da3c88e8a7895591303a37 Mon Sep 17 00:00:00 2001
From: Ivan Vergiliev <ivan.vergiliev@gmail.com>
Date: Wed, 6 Apr 2016 20:19:14 +0300
Subject: [PATCH] Document that stateless functional components can return null
 in v15

---
 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 9f45a9f7a..7b92692fa 100644
--- a/docs/05-reusable-components.md
+++ b/docs/05-reusable-components.md
@@ -301,6 +301,6 @@ However, you may still specify `.propTypes` and `.defaultProps` by setting them
 
 > NOTE:
 >
-> Due to some implementation details, returning `null` or `false` to indicate you don't want to render anything won't work in a functional component (see [react/4599](https://github.com/facebook/react/issues/4599) for details). Consider returning `<noscript />` instead.
+> In React v0.14, stateless functional components were not permitted to return `null` or `false` (a workaround is to return a `<noscript />` instead). This was fixed in React v15, and stateless functional components are now permitted to return `null`.
 
 In an ideal world, most of your components would be stateless functions because in the future we’ll also be able to make performance optimizations specific to these components by avoiding unnecessary checks and memory allocations. This is the recommended pattern, when possible.