Skip to content

Commit 447dbb9

Browse files
committed
default root operation type name -> default operation type name
1 parent 9bfc339 commit 447dbb9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

spec/Section 3 -- Type System.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -212,18 +212,18 @@ type MyMutationRootType {
212212
**Default Root Operation Type Names**
213213

214214
:: While any type can be the root operation type for a GraphQL operation, the
215-
_default root operation type name_ for the {`query`}, {`mutation`}, and
215+
_default operation type name_ for the {`query`}, {`mutation`}, and
216216
{`subscription`} root types are {"Query"}, {"Mutation"}, and {"Subscription"}
217217
respectively.
218218

219219
The type system definition language can omit the schema definition when each
220-
root type present uses its respective _default root operation type name_ and no
221-
other type uses a default root operation type name.
220+
root type present uses its respective _default operation type name_ and no other
221+
type uses a default operation type name.
222222

223223
Likewise, when representing a GraphQL schema using the type system definition
224224
language, a schema definition should be omitted if each root type present uses
225-
its respective _default root operation type name_ and no other type uses a
226-
default root operation type name.
225+
its respective _default operation type name_ and no other type uses a default
226+
operation type name.
227227

228228
This example describes a valid complete GraphQL schema, despite not explicitly
229229
including a {`schema`} definition. The {"Query"} type is presumed to be the

0 commit comments

Comments
 (0)