From 2fa52f375b6fa8e872950a9152dc8e222778ee4e Mon Sep 17 00:00:00 2001 From: Seba Date: Sun, 8 May 2016 21:26:40 -0300 Subject: [PATCH] [docs] Remove mention of 'nested object' as an allowed children in React.Children.map Replace it with 'keyed fragment', since ReactFragments were made a replecement for Objects as allowed children in #4700 --- docs/docs/ref-01-top-level-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/ref-01-top-level-api.md b/docs/docs/ref-01-top-level-api.md index 24252f8e73..926995357f 100644 --- a/docs/docs/ref-01-top-level-api.md +++ b/docs/docs/ref-01-top-level-api.md @@ -98,7 +98,7 @@ Verifies the object is a ReactElement. array React.Children.map(object children, function fn [, object thisArg]) ``` -Invoke `fn` on every immediate child contained within `children` with `this` set to `thisArg`. If `children` is a nested object or array it will be traversed: `fn` will never be passed the container objects. If children is `null` or `undefined` returns `null` or `undefined` rather than an array. +Invoke `fn` on every immediate child contained within `children` with `this` set to `thisArg`. If `children` is a keyed fragment or array it will be traversed: `fn` will never be passed the container objects. If children is `null` or `undefined` returns `null` or `undefined` rather than an array. #### React.Children.forEach