From bdaae47306d8ddbc8f0444a9c4e223f8df74515f Mon Sep 17 00:00:00 2001 From: au711 Date: Sat, 10 Aug 2019 19:08:01 +0530 Subject: [PATCH] corrected some grammatical errors --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2572be8d..b5aa7fdc 100644 --- a/README.md +++ b/README.md @@ -83,13 +83,14 @@ Use it with `fetch`, Axios or other data fetching libraries, even GraphQL. ## Rationale -React Async is different in that it tries to resolve data as close as possible to where it will be used, while using a +React Async is different in that it tries to resolve data as close as possible to where it will be used, while using declarative syntax, using just JSX and native promises. This is in contrast to systems like Redux where you would configure any data fetching or updates on a higher (application global) level, using a special construct (actions/reducers). -React Async works really well even in larger applications with multiple or nested data dependencies. It encourages loading -data on-demand and in parallel at component level instead of in bulk at the route / page level. It's entirely decoupled +React Async works well even in larger applications with multiple or nested data dependencies. It encourages loading +data on-demand and in parallel at component level instead of in bulk at the route/ +page level. It's entirely decoupled from your routes, so it works well in complex applications that have a dynamic routing model or don't use routes at all. React Async is promise-based, so you can resolve anything you want, not just `fetch` requests. @@ -102,8 +103,8 @@ a cache. It can render a fallback UI while loading data, much like `