From c7c9306d29d15709fa62d5920ade5efba13ae6a3 Mon Sep 17 00:00:00 2001 From: Stephen Hanson Date: Thu, 24 Oct 2019 14:57:25 -0500 Subject: [PATCH] Fix typo in suspense documentation (#2467) Removes a redundant "about this" in the concurrent-mode suspense docs. --- 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 b79fb6c5..ef6fe4aa 100644 --- a/content/docs/concurrent-mode-suspense.md +++ b/content/docs/concurrent-mode-suspense.md @@ -130,7 +130,7 @@ We expect to see a lot of experimentation in the community with other libraries. Although it's technically doable, Suspense is **not** currently intended as a way to start fetching data when a component renders. Rather, it lets components express that they're "waiting" for data that is *already being fetched*. Unless you have an idea for a solution that helps prevent waterfalls, we suggest to prefer APIs that favor or enforce fetching before render. The current documentation for [Relay Suspense API](https://relay.dev/docs/en/experimental/api-reference#usepreloadedquery) doesn't yet dive deep into preloading, but we plan to publish more about these techniques in the near future. -Our messaging about this hasn't been very consistent about this in the past. Suspense for Data Fetching is still experimental, so you can expect our recommendations to change over time as we learn more from production usage and understand the problem space better. +Our messaging about this hasn't been very consistent in the past. Suspense for Data Fetching is still experimental, so you can expect our recommendations to change over time as we learn more from production usage and understand the problem space better. ## Traditional Approaches vs Suspense {#traditional-approaches-vs-suspense}