Merge pull request graphql#15 from graphql/typos

Fixing typos

Author: dondonz

.github/ISSUE_TEMPLATE.md

@@ -1 +0,0 @@
-TODO

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
-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,5 +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,
-such as `<scalar-name>2`, `<scalar-name>3`, or a completely different name like
-OffsetDateTime is different to DateTime.
+either with a number appended such as `<scalar-name>2`, or a different name such
+as `OffsetDateTime` to differentiate from `DateTime`.

scalars/contributed/andimarek/date-time.md

@@ -1,10 +1,10 @@
 # Custom Scalar spec DateTime
 
-"Author: andimarek"
+Author: andimarek
 
-"Date: 2022-10-18"
+Date: 2022-10-18
 
-This is a String based Scalars (TODO: add link to explanation).
+This is a String-based Scalar.
 
 # Overview
 

scalars/guide.md

@@ -140,16 +140,16 @@ programmatically, `rawInputValueToLiteral` might not be needed.
 These three functions need to be compatible to each other, specifically:
 
 **Rule 1:** every valid input for `parseRawInputValue` must be a valid input for
-`rawInputVariableToLiteral` and vice versa. This rule ensures that every raw
-input value can be represented as literal.
+`rawInputValueToLiteral` and vice versa. This rule ensures that every raw input
+value can be represented as literal.
 
 **Rule 2:** for every valid input for `parseLiteral` there must at least one
 corresponding input for `parseRawInputValue` resulting in the same coerced input
 value. This rule ensures that all literals can be represented as raw input
 value.
 
-**Rule 3:** every output for `rawInputVariableToLiteral` must be a valid input
-for `parseLiteral`.
+**Rule 3:** every output for `rawInputValueToLiteral` must be a valid input for
+`parseLiteral`.
 
 These rules ensure that for every valid literal we have at least one valid raw
 value and vice versa.

scalars/new-scalar.md

@@ -5,15 +5,12 @@ 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
-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.
 
-The scalars will be hosted at https://scalars.graphql.org. We are currently
-setting this up.
-
 Please ensure that you read the
 [Code of Conduct](https://graphql.org/codeofconduct/) before contributing to
 this project.
@@ -70,5 +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,
-such as `<scalar-name>2`, `<scalar-name>3`, or a completely different name like
-OffsetDateTime is different to DateTime.
+either with a number appended such as `<scalar-name>2`, or a different name such
+as `OffsetDateTime` to differentiate from `DateTime`.