From d71c6e3695c2d8789866bd2a8ff59be6a6b1a4e6 Mon Sep 17 00:00:00 2001
From: Sibiraj <45618743+sibiraj-sr@users.noreply.github.com>
Date: Sun, 30 Jun 2019 13:20:44 +0530
Subject: [PATCH] Remove tooling support info in fragment docs (#2096)

---
 content/docs/fragments.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/content/docs/fragments.md b/content/docs/fragments.md
index 04de0463..33619db2 100644
--- a/content/docs/fragments.md
+++ b/content/docs/fragments.md
@@ -18,7 +18,7 @@ render() {
 }
 ```
 
-There is also a new [short syntax](#short-syntax) for declaring them, but it isn't supported by all popular tools yet.
+There is also a new [short syntax](#short-syntax) for declaring them.
 
 ## Motivation {#motivation}
 
@@ -113,8 +113,6 @@ class Columns extends React.Component {
 
 You can use `<></>` the same way you'd use any other element except that it doesn't support keys or attributes.
 
-Note that **[many tools don't support it yet](/blog/2017/11/28/react-v16.2.0-fragment-support.html#support-for-fragment-syntax)** so you might want to explicitly write `<React.Fragment>` until the tooling catches up.
-
 ### Keyed Fragments {#keyed-fragments}
 
 Fragments declared with the explicit `<React.Fragment>` syntax may have keys. A use case for this is mapping a collection to an array of fragments -- for example, to create a description list: