Prettify

Author: dondonz

CONTRIBUTING.md

@@ -5,8 +5,8 @@ Thanks for contributing to GraphQL Scalars.
 The goal of the GraphQL Scalars project is to provide a directory of GraphQL
 Custom Scalar specifications, contributed by the community. Contributed
 specifications will be hosted on a GraphQL Foundation owned domain
-[scalars.graphql.org](https://scalars.graphql.org), which can be referenced with the built-in
-`@specifiedBy` GraphQL directive.
+[scalars.graphql.org](https://scalars.graphql.org), which can be referenced with
+the built-in `@specifiedBy` GraphQL directive.
 
 GraphQL Custom Scalar specifications are language agnostic and thus can be used
 to document and standardize behavior across different languages.
@@ -69,4 +69,5 @@ available reference documents. We will permit small edits which do not change
 specification semantics, such as typo fixes.
 
 A new version of a Custom Scalar specification should have a new scalar name,
-either with a number appended such as `<scalar-name>2`, or a different name such as `OffsetDateTime` to differentiate from `DateTime`.
+either with a number appended such as `<scalar-name>2`, or a different name such
+as `OffsetDateTime` to differentiate from `DateTime`.

scalars/new-scalar.md

@@ -5,8 +5,8 @@ Thanks for contributing to GraphQL Scalars.
 The goal of the GraphQL Scalars project is to provide a directory of GraphQL
 Custom Scalar specifications, contributed by the community. Contributed
 specifications will be hosted on a GraphQL Foundation owned domain
-[scalars.graphql.org](https://scalars.graphql.org), which can be referenced with the built-in
-`@specifiedBy` GraphQL directive.
+[scalars.graphql.org](https://scalars.graphql.org), which can be referenced with
+the built-in `@specifiedBy` GraphQL directive.
 
 GraphQL Custom Scalar specifications are language agnostic and thus can be used
 to document and standardize behavior across different languages.
@@ -67,4 +67,5 @@ available reference documents. We will permit small edits which do not change
 specification semantics, such as typo fixes.
 
 A new version of a Custom Scalar specification should have a new scalar name,
-either with a number appended such as `<scalar-name>2`, or a different name such as `OffsetDateTime` to differentiate from `DateTime`.
+either with a number appended such as `<scalar-name>2`, or a different name such
+as `OffsetDateTime` to differentiate from `DateTime`.