From b755baf2d74a51376bb37f970cb002c0aa1e39d9 Mon Sep 17 00:00:00 2001 From: jjangga0214 Date: Tue, 20 Aug 2019 17:58:42 +0900 Subject: [PATCH] Update docs/source/intro/benefits.md fix typo --- docs/source/intro/benefits.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/intro/benefits.md b/docs/source/intro/benefits.md index 7e6ce0a..938b19e 100644 --- a/docs/source/intro/benefits.md +++ b/docs/source/intro/benefits.md @@ -53,7 +53,7 @@ Developing your GraphQL API with the Apollo platform gives teams access to moder ## Declarative data fetching -One of the main advantages of adopting GraphQL is its declarative approach to data fetching. With GraphQL, there's no need to call multiple endpoints from the client or aggregate the data manually like you have to with traditional REST data fetching. Instead, you specify exactly the data you need and GraphQL gives you exactly what you asked for. +One of the main advantages of adopting GraphQL is its declarative approach to data fetching. With GraphQL, there's no need to call multiple endpoints from the client or aggregate the data manually like you have to with traditional REST data fetching. Instead, you specify the exact data you need and GraphQL gives you exactly what you asked for. With REST, you would have to call all of these endpoints for each item in the list, filter down the data you need, and aggregate all of the remaining data into the shape your components consume.