formatting

Author: fotoetienne

spec/Section 2 -- Language.md

@@ -287,6 +287,7 @@ defined using the Markdown syntax (as specified by
 Descriptions may appear before:
 
 **In type system definitions:**
+
 - Schema definitions.
 - Type definitions (scalars, objects, interfaces, unions, enums, input objects).
 - Field definitions.
@@ -296,6 +297,7 @@ Descriptions may appear before:
 - Directive definitions.
 
 **In executable documents:**
+
 - Operation definitions (queries, mutations, subscriptions) in their full form
   (not the shorthand form).
 - Fragment definitions.

spec/Section 3 -- Type System.md

@@ -52,11 +52,18 @@ choose to only allow {TypeSystemExtensionDocument} and not allow
 
 ## Type System Descriptions
 
-Documentation is a first-class feature of GraphQL type systems. GraphQL schema and all other definitions (e.g. types, fields, arguments, etc.) which can be described should provide a {Description} unless they are considered self descriptive.
-
-Descriptions in the type system definition language occur immediately before the definition they describe and are made available via introspection, ensuring the documentation of a GraphQL service remains consistent with its capabilities.
-
-Note: See Section 2, "Descriptions", for normative rules and syntax details. Type system descriptions follow the same Markdown format and rules as executable document descriptions.
+Documentation is a first-class feature of GraphQL type systems. GraphQL schema
+and all other definitions (e.g. types, fields, arguments, etc.) which can be
+described should provide a {Description} unless they are considered self
+descriptive.
+
+Descriptions in the type system definition language occur immediately before the
+definition they describe and are made available via introspection, ensuring the
+documentation of a GraphQL service remains consistent with its capabilities.
+
+Note: See Section 2, "Descriptions", for normative rules and syntax details.
+Type system descriptions follow the same Markdown format and rules as executable
+document descriptions.
 
 ## Schema