From ea7f924072740b7dec6e6c1a4fe1da1ad1e98436 Mon Sep 17 00:00:00 2001 From: Nate Barbettini Date: Tue, 13 Feb 2018 14:12:36 -0800 Subject: [PATCH] Fix grammar in Pagination section --- site/learn/BestPractice-Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/learn/BestPractice-Introduction.md b/site/learn/BestPractice-Introduction.md index d500f7345b..069124bf4d 100644 --- a/site/learn/BestPractice-Introduction.md +++ b/site/learn/BestPractice-Introduction.md @@ -54,7 +54,7 @@ When designing a GraphQL schema, it's important to keep in mind all the problems ### Pagination -The GraphQL type system allows for some fields to return [lists of values](/learn/schema/#lists-and-non-null) however leaves the pagination of longer lists of values up to the API designer. There are a wide range of possible API designs for pagination, each of which has pros and cons. +The GraphQL type system allows for some fields to return [lists of values](/learn/schema/#lists-and-non-null), but leaves the pagination of longer lists of values up to the API designer. There are a wide range of possible API designs for pagination, each of which has pros and cons. Typically fields that could return long lists accept arguments "first" and "after" to allow for specifying a specific region of a list, where "after" is a unique identifier of each of the values in the list.