Skip to content

Commit 892619a

Browse files
authored
Fix typos in dataloader docs
1 parent 9e55498 commit 892619a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/book/content/advanced/dataloaders.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Avoiding the N+1 Problem With Dataloaders
22

33
A common issue with graphql servers is how the resolvers query their datasource.
4-
his issue results in a large number of unneccessary database queries or http requests.
4+
This issue results in a large number of unneccessary database queries or http requests.
55
Say you were wanting to list a bunch of cults people were in
66

77
```graphql
@@ -129,7 +129,7 @@ impl Cult {
129129

130130
Once created, a dataloader has the functions `.load()` and `.load_many()`.
131131
When called these return a Future.
132-
In the above example `cult_loader.load(id: i32)` returns `Future<Cult>`. If we had used `cult_loader.load_may(Vec<i32>)` it would have returned `Future<Vec<Cult>>`.
132+
In the above example `cult_loader.load(id: i32)` returns `Future<Cult>`. If we had used `cult_loader.load_many(Vec<i32>)` it would have returned `Future<Vec<Cult>>`.
133133

134134

135135
### Where do I create my dataloaders?

0 commit comments

Comments
 (0)