amirho/react.dev
1
0
Fork 0
mirror of https://github.com/reactjs/react.dev.git synced 2026-02-23 12:13:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update concurrent-mode-suspense.md (#2495)

Browse Source 
According to [ProofreadNOW](https://www.proofreadnow.com/blog/bid/101485/If-I-Were-or-If-I-Was-Which-is-Correct),
> Guideline: Use were (instead of was) in statements that are contrary to fact.
This commit is contained in:
Kevin Sullivan
2020-03-09 06:03:31 -07:00
committed by GitHub
parent 7c28a3e88a
commit 705cacfa70
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/docs/concurrent-mode-suspense.md
View File

@@ -119,7 +119,7 @@ So what's the point of Suspense? There are a few ways we can answer this:
* **It lets you orchestrate intentionally designed loading states.** It doesn't say _how_ the data is fetched, but it lets you closely control the visual loading sequence of your app.
* **It helps you avoid race conditions.** Even with `await`, asynchronous code is often error-prone. Suspense feels more like reading data *synchronously* — as if it was already loaded.
* **It helps you avoid race conditions.** Even with `await`, asynchronous code is often error-prone. Suspense feels more like reading data *synchronously* — as if it were already loaded.
## Using Suspense in Practice {#using-suspense-in-practice}