Docs fixes

docs/openapi-fetch/about.md

@@ -20,18 +20,18 @@ description: openapi-fetch Project Goals, comparisons, and more
 
 ### vs. Axios
 
-[Axios](https://axios-http.com) doesn’t automatically typecheck against your OpenAPI schema. Further, there’s no easy way to do that. Axios does have more features than openapi-fetch such as request/responce interception and cancellation.
+[Axios](https://axios-http.com) doesn’t automatically typecheck against your OpenAPI schema. Further, there’s no easy way to do that. Axios does have more features than openapi-fetch such as interceptors and advanced cancellation.
 
 ### vs. tRPC
 
 [tRPC](https://trpc.io/) is meant for projects where both the backend and frontend are written in TypeScript (Node.js). openapi-fetch is universal, and can work with any backend that follows an OpenAPI 3.x schema.
 
 ### vs. openapi-typescript-fetch
 
-[openapi-typescript-fetch](https://github.com/ajaishankar/openapi-typescript-fetch) predates openapi-fetch, and is nearly identical in purpos, but differs mostly in syntax (so it’s more of an opinionated choice):
+[openapi-typescript-fetch](https://github.com/ajaishankar/openapi-typescript-fetch) predates openapi-fetch, and is nearly identical in purpose, but differs mostly in syntax (so it’s more of an opinionated choice):
 
-- This library has a built-in `error` type for `3xx`/`4xx`/`5xx` errors whereas openapi-typescript-fetch throws exceptions (requiring you to wrap things in `try/catch`)
-- This library has a more terse syntax (`get(…)`) wheras openapi-typescript-fetch requires chaining (`.path(…).method(…).create()`)
+- openapi-typescript-fetch throws exceptions for non-OK responses (requiring you to wrap things in `try/catch`) rather than follow the fetch API spec of not throwing.
+- openapi-typescript-fetch’s syntax is more verbose, and relies on chaining (`.path(…).method(…).create()`).
 
 ### vs. openapi-typescript-codegen