fix: typos and grammar isssues (#398)

This PR fixes minor typos and grammatical issues across the project.

I have:
- [x] Written a clear PR title and description (above)
- [x] Signed the [Khan Academy CLA](https://www.khanacademy.org/r/cla)
- [ ] Added tests covering my changes, if applicable
- [ ] Included a link to the issue fixed, if applicable
- [ ] Included documentation, for new features
- [x] Added an entry to the changelog

Author: NathanBaulch

docs/CHANGELOG.md

@@ -30,6 +30,8 @@ Note that genqlient now requires Go 1.23 or higher, and is tested through Go 1.2
 
 ### Bug fixes:
 
+- fixed minor typos and grammatical issues across the project
+
 ## v0.8.1
 
 This release fixes a bug introduced in v0.8.0 breaking path resolution on Windows, along with some other small features and bugs.

docs/CODE_OF_CONDUCT.md

@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within

docs/CONTRIBUTING.md

@@ -56,4 +56,4 @@ See the [versioning strategy](versioning.md) for when to make a release. To make
 - Add a new section to the changelog for the release (see comments in the changelog for instructions), and add a brief summary of the release at the top.
 - Make a PR with the above. (Example: [#208](https://github.com/Khan/genqlient/pull/208).)
 - After it merges, tag it as the new release, e.g. `git checkout main && git pull && git tag v0.X.Y && git push origin v0.X.Y`.
-- Then, create a release in github, either [on the web](https://github.com/Khan/genqlient/releases/new) or with `export VERSION=v0.6.0; gh release create $VERSION --latest --verify-tag --generate-notes --title $VERSION`. (TODO(benkraft): Figure out how to pull in the changelog we've already written instead!)
+- Then, create a release in GitHub, either [on the web](https://github.com/Khan/genqlient/releases/new) or with `export VERSION=v0.6.0; gh release create $VERSION --latest --verify-tag --generate-notes --title $VERSION`. (TODO(benkraft): Figure out how to pull in the changelog we've already written instead!)

docs/design.md

@@ -89,7 +89,7 @@ type User2 struct {
 }
 ```
 
-Moreover, these types names should be as stable as possible: changing one part of a query (or another query) shouldn't change the type-names.  And ideally, we might deduplicate: in a query like `{ self { id } myChildren { id } }` we'd be able to use a single type for both `self` and `myChildren`.  Although maybe, if you want that, you have to use a fragment; it's clearly in conflict with having stable names.  Or we can actually make this configurable!
+Moreover, these type names should be as stable as possible: changing one part of a query (or another query) shouldn't change the type-names.  And ideally, we might deduplicate: in a query like `{ self { id } myChildren { id } }` we'd be able to use a single type for both `self` and `myChildren`.  Although maybe, if you want that, you have to use a fragment; it's clearly in conflict with having stable names.  Or we can actually make this configurable!
 
 In other tools:
 - Apollo mostly uses named types (except alternatives of an interface/fragment are inline in TypeScript, but not in Flow), and in the above example names them, respectively, `MyQuery_user_User` and `MyQuery_user_User_children_User`, or maybe in some versions `MyQuery_user` and `MyQuery_user_children` in Flow/TypeScript.  In Java and Scala in some cases they use nested types, e.g. `MyQuery.User.Children`.

docs/faq.md

@@ -97,7 +97,7 @@ If your tools are backed by [gopls](https://github.com/golang/tools/blob/master/
 
 ### genqlient fails after `go mod tidy`
 
-If genqlient fails with an error `missing go.sum entry for module providing package`, this is typically because `go mod tidy` removed its dependencies  because they weren't imported by your Go module.  You can read more about this in golang/go#45552; see in particular [this comment](https://github.com/golang/go/issues/45552#issuecomment-819545037).  In short, if you want to be able to `go run` on newer Go you'll need to have a (blank) import of genqlient's entrypoint in a special `tools.go` file somewhere in your module so `go mod tidy` doesn't prune it:
+If genqlient fails with an error `missing go.sum entry for module providing package`, this is typically because `go mod tidy` removed its dependencies because they weren't imported by your Go module.  You can read more about this in golang/go#45552; see in particular [this comment](https://github.com/golang/go/issues/45552#issuecomment-819545037).  In short, if you want to be able to `go run` on newer Go you'll need to have a (blank) import of genqlient's entrypoint in a special `tools.go` file somewhere in your module so `go mod tidy` doesn't prune it:
 
 ```go
 //go:build tools

docs/genqlient.yaml

@@ -232,7 +232,7 @@ bindings:
     # unmarshaler and marshaler are also valid here, see above for details.
 
 # A list of packages for which genqlient should automatically generate
-# bindings.  This is equivalent to adding a entry
+# bindings.  This is equivalent to adding an entry
 #   TypeName:
 #       type: github.com/you/yourpkg/models.TypeName
 # to the bindings map, above, for each exported type in the package.  Multiple

docs/genqlient_directive.graphql

@@ -222,7 +222,7 @@ directive genqlient(
   #      name
   #    }
   #  }
-  # will cause gnqlient to generate:
+  # will cause genqlient to generate:
   #  type Resp struct {
   #    User User
   #  }

docs/operations.md

@@ -355,7 +355,7 @@ and genqlient will generate a Go field `MyGreatName string`.  Note that the alia
 
 ### Type names
 
-genqlient generates quite verbose type names in many cases. (In short, this is because the same `User` GraphQL type must map to different Go types depending which fields are requested; see the FAQ for [more](faq.md#why-does-genqlient-generate-such-complicated-type-names-).
+genqlient generates quite verbose type names in many cases. (In short, this is because the same `User` GraphQL type must map to different Go types depending on which fields are requested; see the FAQ for [more](faq.md#why-does-genqlient-generate-such-complicated-type-names-).
 
 For example, in the following query there are two different user structs.
 ```graphql
@@ -400,7 +400,7 @@ For any GraphQL types or fields with documentation in the GraphQL schema, genqli
 # This query gets the current user.
 #
 # If you also need to specify options on the query, you can put
-# the @genqlient directive after the docuentation, like this:
+# the @genqlient directive after the documentation, like this:
 #
 # @genqlient(omitempty: true)
 query GetUser { ... }

docs/schema.md

@@ -96,7 +96,7 @@ The GraphQL spec officially defines the `Int` type to be a [signed 32-bit intege
 - [Apollo Client](https://github.com/apollographql/apollo-client) doesn't check (but implicitly is limited to 53 bits by JavaScript)
 - [shurcooL/graphql](https://github.com/shurcooL/graphql) requires integers be passed as a `graphql.Int`, defined to be an `int32`
 
-By default, genqlient maps GraphQL `Int`s to Go's `int`, meaning that on 64 bit systems there's no client-side restriction. This is convenient for most use cases, but means the client won't prevent you from passing a 64-bit integer to a server that will reject or truncate it.
+By default, genqlient maps GraphQL `Int`s to Go's `int`, meaning that on 64-bit systems there's no client-side restriction. This is convenient for most use cases, but means the client won't prevent you from passing a 64-bit integer to a server that will reject or truncate it.
 
 If you prefer to limit integers to `int32`, you can set a binding in your `genqlient.yaml`:
 

docs/subscriptions.md

@@ -129,7 +129,7 @@ To change the websocket protocol from its default value `graphql-transport-ws`,
 
 ## Authenticate subscriptions
 
-Graphql allows to authenticate subscriptions using HTTP headers (inside the http upgrade request) or using connection parameters (first message inside the websocket connection).
+Graphql supports authenticated subscriptions using HTTP headers (inside the http upgrade request) or using connection parameters (first message inside the websocket connection).
 To authenticate using both methods, you need to add a `graphql.WebSocketOption` to the `graphql.NewClientUsingWebSocket` method.
 
 ### Example using HTTP headers