@@ -18,7 +18,7 @@ tool should report validation errors and not allow the
1818formulation or execution of requests known to be invalid at that given point in
1919time.
2020
21- ** Type system evolution **
21+ ** Type System Evolution **
2222
2323As GraphQL type system schema evolves over time by adding new types and new
2424fields, it is possible that a request which was previously valid could later
@@ -1082,7 +1082,7 @@ fragment ownerFragment on Human {
10821082}
10831083```
10841084
1085- #### Fragment spread is possible
1085+ #### Fragment Spread is Possible
10861086
10871087** Formal Specification**
10881088
@@ -1107,7 +1107,7 @@ type matches the type condition. They also are spread within the context of a
11071107parent type. A fragment spread is only valid if its type condition could ever
11081108apply within the parent type.
11091109
1110- ##### Object Spreads In Object Scope
1110+ ##### Object Spreads in Object Scope
11111111
11121112In the scope of an object type, the only valid object type fragment spread is
11131113one that applies to the same type that is in scope.
@@ -1170,7 +1170,7 @@ that if one inspected the contents of the {CatOrDogNameFragment} you could note
11701170that no valid results would ever be returned. However we do not specify this as
11711171invalid because we only consider the fragment declaration, not its body.
11721172
1173- ##### Object Spreads In Abstract Scope
1173+ ##### Object Spreads in Abstract Scope
11741174
11751175Union or interface spreads can be used within the context of an object type
11761176fragment, but only if the object type is one of the possible types of that
@@ -1960,7 +1960,7 @@ query listToNonNullList($booleanList: [Boolean]) {
19601960This would fail validation because a ` [T] ` cannot be passed to a ` [T]! ` .
19611961Similarly a ` [T] ` cannot be passed to a ` [T!] ` .
19621962
1963- ** Allowing optional variables when default values exist **
1963+ ** Allowing Optional Variables when Default Values Exist **
19641964
19651965A notable exception to typical variable type compatibility is allowing a
19661966variable definition with a nullable type to be provided to a non-null location
0 commit comments