Skip to content

Commit 83697aa

Browse files
elazzabileebyron
authored andcommitted
Typo in Learn Queries (graphql#105)
1 parent 49d6a8a commit 83697aa

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/learn/Learn-Queries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The field `name` returns a `String` type, in this case the name of the main hero
2828

2929
> Oh, one more thing - the query above is *interactive*. That means you can change it as you like and see the new result. Try adding an `appearsIn` field to the `hero` object in the query, and see the new result.
3030
31-
In the previous example, we just asked for a the name of our hero which returned a String, but fields can also refer to Objects. In that case, you can make a *sub-selection* of fields for that object. GraphQL queries can traverse related objects and their fields, letting clients fetch lots of related data in one request, instead of making several roundtrips as one would need in a classic REST architecture.
31+
In the previous example, we just asked for the name of our hero which returned a String, but fields can also refer to Objects. In that case, you can make a *sub-selection* of fields for that object. GraphQL queries can traverse related objects and their fields, letting clients fetch lots of related data in one request, instead of making several roundtrips as one would need in a classic REST architecture.
3232

3333
```graphql
3434
# { "graphiql": true }

0 commit comments

Comments
 (0)