docs(utils): fix grammar + typos (#10659)

Co-authored-by: Brooks Lybrand <[email protected]>

Author: MichaelDeBoey

docs/utils/cookies.md

@@ -14,7 +14,7 @@ While you may create these cookies manually, it is more common to use a [session
 
 In Remix, you will typically work with cookies in your `loader` and/or `action` functions (see <Link to="../mutations">mutations</Link>), since those are the places where you need to read and write data.
 
-Let's say you have a banner on your e-commerce site that prompts users to check out the items you currently have on sale. The banner spans the top of your homepage, and includes a button on the side that allows the user to dismiss the banner so they don't see it for at least another week.
+Let's say you have a banner on your e-commerce site that prompts users to check out the items you currently have on sale. The banner spans the top of your homepage and includes a button on the side that allows the user to dismiss the banner so they don't see it for at least another week.
 
 First, create a cookie:
 

docs/utils/data.md

@@ -5,7 +5,7 @@ toc: false
 
 # `data`
 
-This is a utility for use with [Single Fetch][single-fetch] to return raw data accompanied with a status code or custom response headers. This avoids the need to serialize your data into a `Response` instance to provide custom status/headers. This is generally a replacement for `loader`/`action` functions that used [`json`][json] or [`defer`][defer] prior to Single Fetch.
+This is a utility for use with [Single Fetch][single-fetch] to return raw data accompanied by a status code or custom response headers. This avoids the need to serialize your data into a `Response` instance to provide custom status/headers. This is generally a replacement for `loader`/`action` functions that used [`json`][json] or [`defer`][defer] prior to Single Fetch.
 
 ```tsx
 import { data } from "@remix-run/node"; // or cloudflare/deno

docs/utils/parse-multipart-form-data.md

@@ -6,7 +6,7 @@ title: unstable_parseMultipartFormData
 
 Allows you to handle multipart forms (file uploads) for your app.
 
-Would be useful to understand [the Browser File API][the-browser-file-api] to know how to use this API.
+It would be useful to understand [the Browser File API][the-browser-file-api] to know how to use this API.
 
 It's to be used in place of `request.formData()`.
 
@@ -26,7 +26,7 @@ export const action = async ({
     uploadHandler // <-- we'll look at this deeper next
   );
 
-  // the returned value for the file field is whatever our uploadHandler returns.
+  // The returned value for the file field is whatever our uploadHandler returns.
   // Let's imagine we're uploading the avatar to s3,
   // so our uploadHandler returns the URL.
   const avatarUrl = formData.get("avatar");

docs/utils/sessions.md

@@ -6,9 +6,9 @@ title: Sessions
 
 Sessions are an important part of websites that allow the server to identify requests coming from the same person, especially when it comes to server-side form validation or when JavaScript is not on the page. Sessions are a fundamental building block of many sites that let users "log in", including social, e-commerce, business, and educational websites.
 
-In Remix, sessions are managed on a per-route basis (rather than something like express middleware) in your `loader` and `action` methods using a "session storage" object (that implements the `SessionStorage` interface). Session storage understands how to parse and generate cookies, and how to store session data in a database or filesystem.
+In Remix, sessions are managed on a per-route basis (rather than something like express middleware) in your `loader` and `action` methods using a "session storage" object (that implements the `SessionStorage` interface). Session storage understands how to parse and generate cookies and how to store session data in a database or filesystem.
 
-Remix comes with several pre-built session storage options for common scenarios, and one to create your own:
+Remix comes with several pre-built session storage options for common scenarios and one to create your own:
 
 - `createCookieSessionStorage`
 - `createMemorySessionStorage`
@@ -198,13 +198,13 @@ export default function LogoutRoute() {
 }
 ```
 
-<docs-warning>It's important that you logout (or perform any mutation for that matter) in an `action` and not a `loader`. Otherwise you open your users to [Cross-Site Request Forgery][csrf] attacks. Also, Remix only re-calls `loaders` when `actions` are called.</docs-warning>
+<docs-warning>It's important that you log out (or perform any mutation for that matter) in an `action` and not a `loader`. Otherwise, you open your users to [Cross-Site Request Forgery][csrf] attacks. Also, Remix only re-calls `loaders` when `actions` are called.</docs-warning>
 
 ## Session Gotchas
 
-- Because of nested routes, multiple loaders can be called to construct a single page. When using `session.flash()` or `session.unset()`, you need to be sure no other loaders in the request are going to want to read that, otherwise you'll get race conditions. Typically if you're using flash, you'll want to have a single loader read it; if another loader wants a flash message, use a different key for that loader.
+- Because of nested routes, multiple loaders can be called to construct a single page. When using `session.flash()` or `session.unset()`, you need to be sure no other loaders in the request are going to want to read that, otherwise you'll get race conditions. Typically, if you're using flash, you'll want to have a single loader read it; if another loader wants a flash message, use a different key for that loader.
 
-- Every time you modify session data, you must `commitSession()` or your changes will be lost. This is different than what you might be used to, where some type of middleware automatically commits session data for you.
+- Every time you modify session data, you must `commitSession()` or your changes will be lost. This is different from what you might be used to, where some type of middleware automatically commits session data for you.
 
 ## `createSession`
 
@@ -281,7 +281,7 @@ const { getSession, commitSession, destroySession } =
   });
 ```
 
-The `expires` argument to `createData` and `updateData` is the same `Date` at which the cookie itself expires and is no longer valid. You can use this information to automatically purge the session record from your database to save on space, or to ensure that you do not otherwise return any data for old, expired cookies.
+The `expires` argument to `createData` and `updateData` is the same `Date` at which the cookie itself expires and is no longer valid. You can use this information to automatically purge the session record from your database to save on space or to ensure that you do not otherwise return any data for old, expired cookies.
 
 ## `createCookieSessionStorage`
 
@@ -291,7 +291,7 @@ The main advantage of cookie session storage is that you don't need any addition
 
 However, cookie-based sessions may not exceed browser cookie size limits of 4k bytes. If your cookie size exceeds this limit, `commitSession()` will throw an error.
 
-The other downside is that you need to update the `Set-Cookie` header in every loader and action that modifies the session (this includes reading a flashed session value). With other strategies you only need to set the session cookie once, because it doesn't actually store any session data, just the key to find it elsewhere.
+The other downside is that you need to update the `Set-Cookie` header in every loader and action that modifies the session (this includes reading a flashed session value). With other strategies you only need to set the session cookie once, because it doesn't store any session data, just the key to find it elsewhere.
 
 ```ts
 import { createCookieSessionStorage } from "@remix-run/node"; // or cloudflare/deno
@@ -307,7 +307,7 @@ const { getSession, commitSession, destroySession } =
   });
 ```
 
-Note that other session implementations store a unique session ID in a cookie and use that ID to look up the session in the source of truth (in-memory, filesystem, DB, etc.). In a cookie session, the cookie _is_ the source of truth so there is no unique ID out of the box. If you need to track a unique ID in your cookie session you will need to add an ID value yourself via `session.set()`.
+Note that other session implementations store a unique session ID in a cookie and use that ID to look up the session in the source of truth (in-memory, filesystem, DB, etc.). In a cookie session, the cookie _is_ the source of truth so there is no unique ID out of the box. If you need to track a unique ID in your cookie session, you will need to add an ID value yourself via `session.set()`.
 
 ## `createMemorySessionStorage`
 

docs/utils/unstable-create-memory-upload-handler.md

@@ -26,4 +26,4 @@ export const action = async ({
 };
 ```
 
-**Options:** The only options supported are `maxPartSize` and `filter` which work the same as in `unstable_createFileUploadHandler` above. This API is not recommended for anything at scale, but is a convenient utility for simple use cases and as a fallback for another handler.
+**Options:** The only options supported are `maxPartSize` and `filter` which work the same as in `unstable_createFileUploadHandler` above. This API is not recommended for anything at scale but is a convenient utility for simple use cases and as a fallback for another handler.