From a57f347ca92d7aa22180b3b1287d22277b75f71b Mon Sep 17 00:00:00 2001 From: Joe Hoyle Date: Fri, 25 Oct 2019 11:06:09 +0200 Subject: [PATCH] Add "the" in "In long term" (#2481) --- content/docs/concurrent-mode-suspense.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/concurrent-mode-suspense.md b/content/docs/concurrent-mode-suspense.md index ef6fe4aa..f31adb5f 100644 --- a/content/docs/concurrent-mode-suspense.md +++ b/content/docs/concurrent-mode-suspense.md @@ -88,7 +88,7 @@ This demo is a teaser. Don't worry if it doesn't quite make sense yet. We'll tal Suspense is not a data fetching library. It's a **mechanism for data fetching libraries** to communicate to React that *the data a component is reading is not ready yet*. React can then wait for it to be ready and update the UI. At Facebook, we use Relay and its [new Suspense integration](https://relay.dev/docs/en/experimental/a-guided-tour-of-relay#loading-states-with-suspense). We expect that other libraries like Apollo can provide similar integrations. -In long term, we intend Suspense to become the primary way to read asynchronous data from components -- no matter where that data is coming from. +In the long term, we intend Suspense to become the primary way to read asynchronous data from components -- no matter where that data is coming from. ### What Suspense Is Not {#what-suspense-is-not}