From 734f1b39b69dabc41b254067eb5aeb60aee002e7 Mon Sep 17 00:00:00 2001 From: Johan Magnusson Date: Tue, 21 Feb 2023 08:55:23 +0100 Subject: [PATCH] docs: Update overview.md (#5011) Remove unnecessary word _doing_ --- docs/react/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/react/overview.md b/docs/react/overview.md index e9979c0bb9..00ca87039e 100644 --- a/docs/react/overview.md +++ b/docs/react/overview.md @@ -7,7 +7,7 @@ TanStack Query (FKA React Query) is often described as the missing data-fetching ## Motivation -Most core web frameworks **do not** come with an opinionated way of fetching or updating data in a wholistic way. Because of this developers end up building either meta-frameworks which encapsulate strict opinions about data-fetching, or they invent their own ways of doing fetching data. This usually means cobbling together component-based state and side-effects, or using more general purpose state management libraries to store and provide asynchronous data throughout their apps. +Most core web frameworks **do not** come with an opinionated way of fetching or updating data in a wholistic way. Because of this developers end up building either meta-frameworks which encapsulate strict opinions about data-fetching, or they invent their own ways of fetching data. This usually means cobbling together component-based state and side-effects, or using more general purpose state management libraries to store and provide asynchronous data throughout their apps. While most traditional state management libraries are great for working with client state, they are **not so great at working with async or server state**. This is because **server state is totally different**. For starters, server state: