@@ -83,7 +83,7 @@ app.Run();
 This sets up a `HTTP` `POST` end point at `/graphql` where the body of the post is expected to be a GraphQL query. You can change the path with the `path` argument in `MapGraphQL<T>()`
 
 :::tip
-`MapGraphQL` follows the GraphQL over HTTP behavior that EntityGraphQL adopted in v6. GraphQL execution errors are returned in the GraphQL response body rather than by changing the route shape or adding a special endpoint mode.
+`MapGraphQL` follows the [GraphQL over HTTP spec](https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md). GraphQL errors are returned in the response body - always read `errors` there. See [Tool integration](./integration) for the status codes used.
 :::
 
 _You can authorize the route how ever you wish using ASP.NET. See the Authorization section for more details._
 
@@ -9,7 +9,7 @@ Being GraphQL there are many tools that integrate well with EntityGraphQL.
 EntityGraphQL supports GraphQL introspection queries so tools like GraphiQL and Relay can work against your schema.
 
 :::tip GraphQL over HTTP
-`MapGraphQL()` follows the [GraphQL over HTTP spec](https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md), the behavior EntityGraphQL adopted in v6. GraphQL execution errors are returned in the GraphQL response body rather than by changing the route shape or adding a special endpoint mode. HTTP status codes follow the spec per negotiated media type: with `application/graphql-response+json` (the default) a request error (no `data` in the response) returns `400`, a partial success (`data` plus `errors`) returns `294` and a clean result `200`; with the legacy `application/json` every well-formed request returns `200` and clients must read the body. Either way, always read `errors` from the response body.
+`MapGraphQL()` follows the [GraphQL over HTTP spec](https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md) (adopted in v6). GraphQL errors are returned in the response body - always read `errors` there. Status codes follow the spec: with `application/graphql-response+json` (the default) a request error returns `400` and a partial success `294`; with legacy `application/json` every well-formed request returns `200`.
 :::
 
 ## Introspection