docs(components): fix grammar + typos (#10649)

Author: MichaelDeBoey

docs/components/form.md

@@ -6,7 +6,7 @@ title: Form
 
 A progressively enhanced HTML [`<form>`][form_element] that submits data to actions via `fetch`, activating pending states in `useNavigation` which enables advanced user interfaces beyond a basic HTML form. After a form's action completes, all data on the page is automatically revalidated from the server to keep the UI in sync with the data.
 
-Because it uses the HTML form API, server rendered pages are interactive at a basic level before JavaScript loads. Instead of Remix managing the submission, the browser manages the submission as well as the pending states (like the spinning favicon). After JavaScript loads, Remix takes over enabling web application user experiences.
+Because it uses the HTML form API, server-rendered pages are interactive at a basic level before JavaScript loads. Instead of Remix managing the submission, the browser manages the submission as well as the pending states (like the spinning favicon). After JavaScript loads, Remix takes over enabling web application user experiences.
 
 Form is most useful for submissions that should also change the URL or otherwise add an entry to the browser history stack. For forms that shouldn't manipulate the browser history stack, use [`<fetcher.Form>`][fetcher_form].
 
@@ -79,7 +79,7 @@ If you are using [`<ScrollRestoration>`][scroll_restoration_component], this let
 
 ### `replace`
 
-Replaces the current entry in the history stack, instead of pushing the new entry.
+Replaces the current entry in the history stack instead of pushing the new entry.
 
 ```tsx
 <Form replace />

docs/components/link.md

@@ -18,7 +18,7 @@ import { Link } from "@remix-run/react";
 
 ### `to: string`
 
-The most basic usage takes an href string:
+The most basic usage takes an `href` string:
 
 ```tsx
 <Link to="/some/path" />
@@ -49,8 +49,8 @@ Defines the route discovery behavior when using [`future.v3_lazyRouteDiscovery`]
 </>
 ```
 
-- **render** - default, discover the route when the link renders
-- **none** - don't eagerly discover, only discover if the link is clicked
+- **render** — default, discover the route when the link renders
+- **none** — don't eagerly discover, only discover if the link is clicked
 
 ### `prefetch`
 
@@ -66,10 +66,10 @@ Defines the data and module prefetching behavior for the link.
 </>
 ```
 
-- **none** - default, no prefetching
-- **intent** - prefetches when the user hovers or focuses the link
-- **render** - prefetches when the link renders
-- **viewport** - prefetches when the link is in the viewport, very useful for mobile
+- **none** — default, no prefetching
+- **intent** — prefetches when the user hovers or focuses the link
+- **render** — prefetches when the link renders
+- **viewport** — prefetches when the link is in the viewport, very useful for mobile
 
 Prefetching is done with HTML `<link rel="prefetch">` tags. They are inserted after the link.
 
@@ -136,8 +136,8 @@ Defines the relative path behavior for the link.
 <Link relative="path" />;
 ```
 
-- **route** - default, relative to the route hierarchy so `..` will remove all URL segments of the current route pattern
-- **path** - relative to the path so `..` will remove one URL segment
+- **route** — default, relative to the route hierarchy so `..` will remove all URL segments of the current route pattern
+- **path** — relative to the path so `..` will remove one URL segment
 
 ### `reloadDocument`
 
@@ -168,7 +168,7 @@ A -> C
 
 ### `state`
 
-Adds persistent client side routing state to the next location.
+Adds a persistent client side routing state to the next location.
 
 ```tsx
 <Link to="/somewhere/else" state={{ some: "value" }} />

docs/components/prefetch-page-links.md

@@ -5,7 +5,7 @@ toc: false
 
 # `<PrefetchPageLinks />`
 
-This component enables prefetching of all assets for a page to enable an instant navigation to that page. It does this by rendering `<link rel="prefetch">` and `<link rel="modulepreload"/>` tags for all the assets (data, modules, css) of a given page.
+This component enables prefetching of all assets for a page to enable an instant navigation to that page. It does this by rendering `<link rel="prefetch">` and `<link rel="modulepreload"/>` tags for all the assets (data, modules, CSS) of a given page.
 
 `<Link rel="prefetch">` uses this internally, but you can render it to prefetch a page for any other reason.
 

docs/components/scroll-restoration.md

@@ -46,7 +46,7 @@ Optional. Defines the key used to restore scroll positions.
 
 <summary>Discussion</summary>
 
-Using `location.key` emulates the browser's default behavior. The user can navigate to the same URL multiple times in the stack and each entry gets its own scroll position to restore.
+Using `location.key` emulates the browser's default behavior. The user can navigate to the same URL multiple times in the stack, and each entry gets its own scroll position to restore.
 
 Some apps may want to override this behavior and restore position based on something else. Consider a social app that has four primary pages:
 
@@ -55,7 +55,7 @@ Some apps may want to override this behavior and restore position based on somet
 - "/notifications"
 - "/search"
 
-If the user starts at "/home", scrolls down a bit, clicks "messages" in the navigation menu, then clicks "home" in the navigation menu (not the back button!) there will be three entries in the history stack:
+If the user starts at `"/home"`, scrolls down a bit, clicks `"messages"` in the navigation menu, then clicks `"home"` in the navigation menu (not the back button!) there will be three entries in the history stack:
 
 ```
 1. /home
@@ -65,7 +65,7 @@ If the user starts at "/home", scrolls down a bit, clicks "messages" in the navi
 
 By default, React Router (and the browser) will have two different scroll positions stored for `1` and `3` even though they have the same URL. That means as the user navigated from `2` → `3` the scroll position goes to the top instead of restoring to where it was in `1`.
 
-A solid product decision here is to keep the users scroll position on the home feed no matter how they got there (back button or new link clicks). For this, you'd want to use the `location.pathname` as the key.
+A solid product decision here is to keep the users' scroll position on the home feed no matter how they got there (back button or new link clicks). For this, you'd want to use the `location.pathname` as the key.
 
 ```tsx
 <ScrollRestoration
@@ -75,7 +75,7 @@ A solid product decision here is to keep the users scroll position on the home f
 />
 ```
 
-Or you may want to only use the pathname for some paths, and use the normal behavior for everything else:
+Or you may want to only use the pathname for some paths and use the normal behavior for everything else:
 
 ```tsx
 <ScrollRestoration