From b75c2aecfb0fbe06c83c79376c0fa252f402c8bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Mon, 22 Dec 2014 13:56:10 -0800 Subject: [PATCH] Merge pull request #2759 from alextsg/patch-2 Update 05-maximum-number-of-jsx-root-nodes.md for capitalization --- docs/tips/05-maximum-number-of-jsx-root-nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tips/05-maximum-number-of-jsx-root-nodes.md b/docs/tips/05-maximum-number-of-jsx-root-nodes.md index 0ce319e633..d3e026f70a 100644 --- a/docs/tips/05-maximum-number-of-jsx-root-nodes.md +++ b/docs/tips/05-maximum-number-of-jsx-root-nodes.md @@ -9,4 +9,4 @@ next: style-props-value-px.html Currently, in a component's `render`, you can only return one node; if you have, say, a list of `div`s to return, you must wrap your components within a `div`, `span` or any other component. -Don't forget that JSX compiles into regular js; returning two functions doesn't really make syntactic sense. Likewise, don't put more than one child in a ternary. +Don't forget that JSX compiles into regular JS; returning two functions doesn't really make syntactic sense. Likewise, don't put more than one child in a ternary.