From 53cda16c377b552963e103a9ec9f1213dbca5e67 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C3=A1vid=20Nam=C3=A9nyi?= Date: Thu, 22 Jul 2021 14:10:08 +0200 Subject: [PATCH] remove duplicated word from BestPractice-Introduction page --- src/content/learn/BestPractice-Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/learn/BestPractice-Introduction.md b/src/content/learn/BestPractice-Introduction.md index 9b31e1c644..31b49df89a 100644 --- a/src/content/learn/BestPractice-Introduction.md +++ b/src/content/learn/BestPractice-Introduction.md @@ -58,7 +58,7 @@ The GraphQL type system allows for some fields to return [lists of values](/lear 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. -Ultimately designing APIs with feature-rich pagination led to a best practice pattern called "Connections". Some client tools for GraphQL, such as [Relay](https://facebook.github.io/relay/), know about the Connections pattern and can automatically provide automatic support for client-side pagination when a GraphQL API employs this pattern. +Ultimately designing APIs with feature-rich pagination led to a best practice pattern called "Connections". Some client tools for GraphQL, such as [Relay](https://facebook.github.io/relay/), know about the Connections pattern and can automatically provide support for client-side pagination when a GraphQL API employs this pattern. Read more about this in the article on [Pagination](/learn/pagination/).