From 892619a35bbbc73b6024c5bc877e868294e42129 Mon Sep 17 00:00:00 2001 From: Christian Legnitto Date: Sat, 25 Apr 2020 20:26:16 -1000 Subject: [PATCH] Fix typos in dataloader docs --- docs/book/content/advanced/dataloaders.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/book/content/advanced/dataloaders.md b/docs/book/content/advanced/dataloaders.md index 649af3db..5f0e4a94 100644 --- a/docs/book/content/advanced/dataloaders.md +++ b/docs/book/content/advanced/dataloaders.md @@ -1,7 +1,7 @@ # Avoiding the N+1 Problem With Dataloaders A common issue with graphql servers is how the resolvers query their datasource. -his issue results in a large number of unneccessary database queries or http requests. +This issue results in a large number of unneccessary database queries or http requests. Say you were wanting to list a bunch of cults people were in ```graphql @@ -129,7 +129,7 @@ impl Cult { Once created, a dataloader has the functions `.load()` and `.load_many()`. When called these return a Future. -In the above example `cult_loader.load(id: i32)` returns `Future`. If we had used `cult_loader.load_may(Vec)` it would have returned `Future>`. +In the above example `cult_loader.load(id: i32)` returns `Future`. If we had used `cult_loader.load_many(Vec)` it would have returned `Future>`. ### Where do I create my dataloaders?