Merge pull request #174 from enisdenjo/patch-1

docs: Fix a few typos in the README

readme.md

@@ -5,13 +5,13 @@ This is a parser for graphql, written to mirror the graphql-js reference impleme
 
 spec target: June 2018 (Schema definition language, block strings as descriptions, error paths & extension)
 
-This parser is used by [gqlgen](https://github.com/99designs/gqlgen), and it should be reasonablly stable.
+This parser is used by [gqlgen](https://github.com/99designs/gqlgen), and it should be reasonably stable.
 
 Guiding principles:
 
  - maintainability: It should be easy to stay up to date with the spec
- - well tested: It shouldnt need a graphql server to validate itself. Changes to this repo should be self contained.
+ - well tested: It shouldn't need a graphql server to validate itself. Changes to this repo should be self contained.
  - server agnostic: It should be usable by any of the graphql server implementations, and any graphql client tooling.
  - idiomatic & stable api: It should follow go best practices, especially around forwards compatibility.
- - fast: Where it doesnt impact on the above it should be fast. Avoid unnecessary allocs in hot paths.
- - close to reference: Where it doesnt impact on the above, it should stay close to the [graphql/graphql-js](https://github.com/graphql/graphql-js) reference implementation.
+ - fast: Where it doesn't impact on the above it should be fast. Avoid unnecessary allocs in hot paths.
+ - close to reference: Where it doesn't impact on the above, it should stay close to the [graphql/graphql-js](https://github.com/graphql/graphql-js) reference implementation.