graphql · benjie · Apr 28, 2023 · Apr 28, 2023 · Aug 21, 2023 · Oct 17, 2024
diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md
@@ -757,7 +757,7 @@ type Person {
 }
 ```
 
-Valid operations must supply a nested field set for any field that returns an
+Valid operations must supply a selection of fields for any field that returns an
-Valid operations must supply a selection of fields for any field that returns an
+Valid operations must supply a valid sub _selection set_ for any field that returns an
-Valid operations must supply a selection of fields for any field that returns an
+Valid operations must supply a valid sub _selection set_ for any field that returns an
 object, so this operation is not valid:
 
 ```graphql counter-example

diff --git a/spec/Section 5 -- Validation.md b/spec/Section 5 -- Validation.md
@@ -468,7 +468,7 @@ should be unambiguous. Therefore any two field selections which might both be
 encountered for the same object are only valid if they are equivalent.
 
 During execution, the simultaneous execution of fields with the same response
-name is accomplished by {MergeSelectionSets()} and {CollectFields()}.
+name is accomplished by {CollectSubfields()}.
 
 For simple hand-written GraphQL, this rule is obviously a clear developer error,
 however nested fragments can make this difficult to detect manually.