From 53cc60e8077fcf8a1483971ef557287401605e10 Mon Sep 17 00:00:00 2001
From: Rob Richard <rob@1stdibs.com>
Date: Fri, 8 Nov 2024 11:48:03 -0500
Subject: [PATCH] PR feedback

---
 spec/Section 3 -- Type System.md | 23 ++++++++++++++---------
 1 file changed, 14 insertions(+), 9 deletions(-)

diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md
index d394121c3..a162255d4 100644
--- a/spec/Section 3 -- Type System.md	
+++ b/spec/Section 3 -- Type System.md	
@@ -1943,11 +1943,6 @@ by a validator, executor, or client tool such as a code generator.
 
 GraphQL implementations should provide the `@skip` and `@include` directives.
 
-GraphQL implementations are not required to implement the `@defer` and `@stream`
-directives. If either or both of these directives are implemented, they must be
-implemented according to this specification. GraphQL implementations that do not
-support these directives must not make them available via introspection.
-
 GraphQL implementations that support the type system definition language must
 provide the `@deprecated` directive if representing deprecated portions of the
 schema.
@@ -2169,6 +2164,14 @@ to the relevant IETF specification.
 scalar UUID @specifiedBy(url: "https://tools.ietf.org/html/rfc4122")
 ```
 
+GraphQL implementations are not required to implement the `@defer` and `@stream`
+directives. If either or both of these directives are implemented, they must be
+implemented according to this specification. GraphQL implementations that do not
+support these directives must not make them available via introspection. The
+[Directives Are Defined](#sec-Directives-Are-Defined) validation rule will
+prevent GraphQL Operations containing the `@defer` or `@stream` directive from
+being executed by a GraphQL service that does not implement these directives.
+
 ### @defer
 
 ```graphql
@@ -2182,9 +2185,8 @@ The `@defer` directive may be provided for fragment spreads and inline fragments
 to inform the executor to delay the execution of the current fragment to
 indicate deprioritization of the current fragment. A query with `@defer`
 directive will cause the request to potentially return multiple responses, where
-non-deferred data is delivered in the initial response and data deferred is
-delivered in a subsequent response. `@include` and `@skip` take precedence over
-`@defer`.
+deferred data is delivered in subsequent responses. `@include` and `@skip` take
+precedence over `@defer`.
 
 ```graphql example
 query myQuery($shouldDefer: Boolean) {
@@ -2226,7 +2228,10 @@ directive @stream(
 The `@stream` directive may be provided for a field of `List` type so that the
 backend can leverage technology such as asynchronous iterators to provide a
 partial list in the initial response, and additional list items in subsequent
-responses. `@include` and `@skip` take precedence over `@stream`.
+responses. `@include` and `@skip` take precedence over `@stream`. The
+[Stream Directives Are Used On List Fields](#sec-Stream-Directives-Are-Used-On-List-Fields)
+validation rule is used to prevent the `@stream` directive from being applied to
+a field that is not a `List` type.
 
 ```graphql example
 query myQuery($shouldStream: Boolean) {