33Thanks for contributing to GraphQL Scalars.
44
55The goal of the GraphQL Scalars project is to provide a directory of GraphQL
6- Custom Scalar specifications, contributed by the community. Contributed
6+ custom scalar specifications, contributed by the community. Contributed
77specifications are hosted on a GraphQL Foundation owned domain
88[ scalars.graphql.org] ( https://scalars.graphql.org ) , which can be referenced with
99the built-in ` @specifiedBy `
1010[ GraphQL directive] ( https://spec.graphql.org/draft/#sec--specifiedBy ) .
1111
12- GraphQL Custom Scalar specifications are language agnostic and thus can be used
12+ GraphQL custom scalar specifications are language- agnostic and thus can be used
1313to document and standardize behavior across different languages.
1414
1515Please ensure that you read the
@@ -20,10 +20,10 @@ this project.
2020
21211 . Copy the ` template-string.md `
2222 [ template] ( https://github.com/graphql/graphql-scalars/blob/main/scalars/template-string.md )
23- for Custom Scalars based on the built-in String Scalar , or otherwise use the
23+ for custom scalars based on the built-in String scalar , or otherwise use the
2424 ` template.md `
2525 [ template] ( https://github.com/graphql/graphql-scalars/blob/main/scalars/template.md )
26- for all other Custom Scalars . Templates are located in the
26+ for all other custom scalars . Templates are located in the
2727 [ graphql-scalars GitHub repository] ( https://github.com/graphql/graphql-scalars/tree/main/scalars ) .
2828
29292 . Modify your selected template, and save it in the correct place
@@ -42,7 +42,7 @@ this project.
42424 . Run ` npm test ` to ensure proper formatting before submitting a pull request.
4343
44445 . [ Open a new pull request] ( https://github.com/graphql/graphql-scalars/pulls )
45- for each Custom Scalar specification you would like to add.
45+ for each custom scalar specification you would like to add.
4646
4747### Review process for new specifications
4848
@@ -68,7 +68,7 @@ Specification semantics must not change, as specifications are publicly
6868available reference documents. We will permit small edits which do not change
6969specification semantics, such as typo fixes.
7070
71- A new version of a Custom Scalar specification must use a new URL but may still
71+ A new version of a custom scalar specification must use a new URL but may still
7272recommend using the old name.
7373
7474For example, ` scalars/contributed/my_username/date-time-v2.md ` may recommend
0 commit comments