Include deprecated directive

Author: leebyron

spec/Section 3 -- Type System.md

@@ -895,9 +895,15 @@ engine supports.
 
 GraphQL implementations should provide the `@skip` and `@include` directives.
 
+GraphQL implementations that support the type system language must provide the
+`@deprecated` directive when representing deprecated portions of the schema.
 
 ### @skip
 
+```graphql
+directive @skip(if: Boolean!) on FIELD | FRAGMENT_SPREAD | INLINE_FRAGMENT
+```
+
 The `@skip` directive may be provided for fields, fragment spreads, and
 inline fragments, and allows for conditional exclusion during execution as
 described by the if argument.
@@ -914,6 +920,10 @@ query myQuery($someTest: Boolean) {
 
 ### @include
 
+```graphql
+directive @include(if: Boolean!) on FIELD | FRAGMENT_SPREAD | INLINE_FRAGMENT
+```
+
 The `@include` directive may be provided for fields, fragment spreads, and
 inline fragments, and allows for conditional inclusion during execution as
 described by the if argument.
@@ -935,6 +945,31 @@ must *not* be queried if either the `@skip` condition is true *or* the
 `@include` condition is false.
 
 
+### @deprecated
+
+```graphql
+directive @deprecated(
+  reason: String = "No longer supported"
+) on FIELD_DEFINITION | ENUM_VALUE
+```
+
+The `@deprecated` directive is used within the type system language to indicate deprecated portions of the schema, such as deprecated fields on a type or
+deprecated enum values.
+
+Deprecations include a reason for why it is deprecated, which can include
+markdown formatting.
+
+In this example type definition, `oldField` is deprecated in favor of
+using `newField`.
+
+```graphql
+type ExampleType {
+  newField: String
+  oldField: String @deprecated(reason: "Use `newField`.")
+}
+```
+
+
 ## Initial types
 
 A GraphQL schema includes types, indicating where query and mutation