wordsmithing

Author: leebyron

spec/Appendix B -- Notation Conventions.md

@@ -248,10 +248,7 @@ entry has a unique key, and can be directly referenced by that key.
 ordered map, which does not have an entry with that key, is ordered after
 existing entries.
 
-**Preserving order**
-
-To improve legibility, when possible implementations should preserve observable
-order for unordered data collections. For example, if applying a grammar to an
-input string produces an unordered set, serializing that set (to a string or
-other observable output) should produce the same order found in the original
-input string.
+Note: Ordered data collection are only specified when strictly necessary. To
+improve legibility and stability of outputs it is recommended to preserve
+observable order. For example if applying a grammar to an input string produces
+a set, serializing that set should reproduce the original order.

spec/Section 4 -- Introspection.md

@@ -117,16 +117,13 @@ Tools built using GraphQL introspection should respect deprecation by
 discouraging deprecated use through information hiding or developer-facing
 warnings.
 
-**Ordering**
+**Stable Ordering**
 
-When possible, implementations should preserve observable order for unordered
-data collections. For example, if a schema was produced from a source
-{TypeSystemDocument} then introspection of fields, input fields, arguments, enum
-values, directives, union members, implemented interfaces and so on should
-produce the same order as found in the source.
-
-Note: This recommendation is to improve legibility and stability of schema
-representations.
+To improve legibility and stability of schema representations, it is recommended
+to preserve observable order for all data collections. For example, if a schema
+was produced from a source {TypeSystemDocument} then introspection of fields,
+input fields, arguments, enum values, directives, union members, implemented
+interfaces and so on should reproduce the original order.
 
 **Schema Introspection Schema**