docs: Fix typos

aklinker1 · aklinker1 · commit 2f441716ff26 · 2026-01-02T18:20:21.000-06:00
diff --git a/docs/content/server/routes/_index.md b/docs/content/server/routes/_index.md
@@ -71,18 +71,21 @@ export const app = createApp().get(
 );
 ```
 
-All available properties are typed, so you're editor can tell you what's available.
+All available properties are typed, so your editor can tell you what's available.
 
 ## Handler Context
 
 The handler function receives "context" as its first argument. This object contains information about the request:
 
 - `route` &ndash; The matched route
-- `path` &ndash; The parsed path parameters
+- `path` &ndash; The full URL pathname
+- `params` &ndash; The parsed path parameters
 - `query` &ndash; The parsed query parameters
 - `body` &ndash; The parsed request body
 - `request` &ndash; The original `Request` instance
 - `url` &ndash; The parsed URL
+- `set` &ndash; Util for setting response headers
+- `status` &ndash; Util for setting the response status
 
 ### Decorate
 
diff --git a/docs/content/server/routes/path-params.md b/docs/content/server/routes/path-params.md
@@ -33,9 +33,9 @@ There are three ways to define a path parameter:
 2. `**` &ndash; Anonymous wildcard
 3. `**:paramName` &ndash; Named wildcard
 
-Wildcard parameters accept any number of path segments, and can be accessed by `params["**"]` or `params.paramName`, depending on if it is named or anonymous.
+Wildcard parameters accept any number of path segments, and can be accessed by `params["**"]` or `params.paramName`, depending on if it is anonymous or named.
 
-Here's an example using a named wildcard parameter to throw a 404 error if the API endpoint is not found:
+Here's an example using an anonymous wildcard parameter to throw a 404 error if the API endpoint is not found:
 
 ```ts
 const app = createApp({ prefix: "/api" })
diff --git a/docs/content/server/routes/request-body.md b/docs/content/server/routes/request-body.md
@@ -71,7 +71,7 @@ Or you can use Zeta's built-in client which will [build the `FormData` for you](
 
 ## Files
 
-Similar to individual file uploads, Zeta provides a util for uploading `FileList`s: [`UploadFilesBody`](https://jsr.io/@aklinker1/zeta/doc/schema/~/UploadFilesBody) based on an input `File`.
+Similar to individual file uploads, Zeta provides a util for uploading `FileList`s: [`UploadFilesBody`](https://jsr.io/@aklinker1/zeta/doc/schema/~/UploadFilesBody).
 
 ```ts
 import { UploadFilesBody } from "@aklinker1/zeta/schemas";
@@ -87,7 +87,7 @@ const app = createApp().post(
 );
 ```
 
-In the handler, instead of a `FileList`, you'll be provided an array of `File` instances.
+In the handler, instead of a `FileList`, you'll be provided a `File[]`.
 
 On the client side, the body is still `FormData`, but the key is `files` instead:
 
@@ -126,7 +126,7 @@ const app = createApp().post(
 
 ## Other
 
-If you need to upload another data type, like for example CSV, you can do so by adding the `contentType` metadata to your body schema:
+If you need to upload another data type, like CSV, you can do so by adding the `contentType` metadata to your body schema:
 
 ```ts
 import { z } from "zod";
diff --git a/docs/content/testing/test-client.md b/docs/content/testing/test-client.md
@@ -61,4 +61,4 @@ describe("App", () => {
 });
 ```
 
-Details for how to use the `client` object can be found in Zeta's [Client-side docs](@/client/_index.md);
+Details for how to use the `client` object can be found in Zeta's [Client-side docs](@/client/_index.md).
