From 7e59754669555861a56b3395306998640351ed22 Mon Sep 17 00:00:00 2001
From: Brian Vaughn <bvaughn@fb.com>
Date: Sat, 27 Jul 2019 15:48:58 -0700
Subject: [PATCH] Fixed a typo in Profiler docs (Array -> Set)

---
 text/0051-profiler.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/text/0051-profiler.md b/text/0051-profiler.md
index 71f68d00..ef5241c7 100644
--- a/text/0051-profiler.md
+++ b/text/0051-profiler.md
@@ -108,7 +108,7 @@ Start time isn't just the commit time less the "actual" time, because in async r
 #### `commitTime: number`
 Commit time could be roughly determined using e.g. `performance.now()` within the `onRender` callback, but multiple `Profiler` components would end up with slightly different times for a single commit. Instead, an explicit time is provided (shared between all `Profiler`s in the commit) enabling them to be grouped if desirable.
 
-#### `interactions: Array<{ name: string, timestamp: number }>`
+#### `interactions: Set<{ name: string, timestamp: number }>`
 Set of interactions that were being tracked (via the `interaction-tracking` package) when this commit was initially scheduled (e.g. when `render` or `setState` were called).
 
 In the event of a cascading render (e.g. an update scheduled from an effect or `componentDidMount`/`componentDidUpdate`) React will forward these interactions along to the subsequent `onRender` calls.