chore: add clarifying note for composite and expand term (#1078)

* remove mentions of composite

* Apply suggestions from code review

Co-authored-by: Benjie <benjie@jemjie.com>

* add note

* Capitalise first letter in note block

* remove the term and alter the wording

* typo

* Update spec/Section 5 -- Validation.md

Co-authored-by: Benjie <benjie@jemjie.com>

* Update spec/Section 5 -- Validation.md

Co-authored-by: Benjie <benjie@jemjie.com>

* Update spec/Section 5 -- Validation.md

Co-authored-by: Benjie <benjie@jemjie.com>

---------

Co-authored-by: Benjie <benjie@jemjie.com>

spec/Section 5 -- Validation.md

@@ -446,7 +446,8 @@ SameResponseShape(fieldA, fieldB):
 - If {typeA} or {typeB} is Scalar or Enum:
   - If {typeA} and {typeB} are the same type return {true}, otherwise return
     {false}.
-- Assert: {typeA} and {typeB} are both composite types.
+- Assert: {typeA} is an object, union or interface type.
+- Assert: {typeB} is an object, union or interface type.
 - Let {mergedSet} be the result of adding the selection set of {fieldA} and the
   selection set of {fieldB}.
 - Let {fieldsForName} be the set of selections with a given response name in
@@ -455,6 +456,9 @@ SameResponseShape(fieldA, fieldB):
   - If {SameResponseShape(subfieldA, subfieldB)} is {false}, return {false}.
 - Return {true}.
 
+Note: In prior versions of the spec the term "composite" was used to signal a
+type that is either an Object, Interface or Union type.
+
 **Explanatory Text**
 
 If multiple field selections with the same response names are encountered during
@@ -910,7 +914,7 @@ fragment inlineNotExistingType on Dog {
 }
 ```
 
-#### Fragments on Composite Types
+#### Fragments on Object, Interface or Union Types
 
 **Formal Specification**