From 426e7f27e24136af48c4eccf194c276523d0b0d0 Mon Sep 17 00:00:00 2001 From: Leonel Mandarino Date: Fri, 17 Jan 2025 11:28:50 -0300 Subject: [PATCH] Fix typo on mutations.mdx --- src/pages/learn/mutations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/learn/mutations.mdx b/src/pages/learn/mutations.mdx index 641c83c2af..00a4100f92 100644 --- a/src/pages/learn/mutations.mdx +++ b/src/pages/learn/mutations.mdx @@ -41,7 +41,7 @@ Like queries, mutation fields are added to one of the [root operation types](htt Mutation fields can also accept arguments and you might notice that the `review` argument has an input type set to `ReviewInput`. This is known as [Input Object type](/learn/schema/#input-object-types), which allows us to pass in a structured object containing information the mutation can use instead of individual scalar values only. -Also like just like queries, if the mutation field returns an Object type, then you specify a selection set of its fields in the operation: +Also just like queries, if the mutation field returns an Object type, then you specify a selection set of its fields in the operation: ```graphql # { "graphiql": true, "variables": { "ep": "JEDI", "review": { "stars": 5, "commentary": "This is a great movie!" } } }