[pull] main from remix-run:main

.github/ISSUE_TEMPLATE/config.yml

@@ -5,7 +5,7 @@ contact_links:
     about: If you've got an idea for a new feature in React Router, please open a new Discussion with the `Proposals` label
   - name: 🤔 Usage Question (Github Discussions)
     url: https://github.com/remix-run/remix/discussions/new?category=q-a
-    about: Open a Discussion in GitHub wih the `Q&A` label
+    about: Open a Discussion in GitHub with the `Q&A` label
   - name: 💬 Remix Discord Channel
     url: https://rmx.as/discord
     about: Interact with other people using React Router and Remix 📀

decisions/0003-infer-types-for-useloaderdata-and-useactiondata-from-loader-and-action-via-generics.md

@@ -32,7 +32,7 @@ export default function Route() {
 }
 ```
 
-For end-to-end type safety, it is then the user's responsability to make sure that `loader` and `action` also use the same type in the `json` generic:
+For end-to-end type safety, it is then the user's responsibility to make sure that `loader` and `action` also use the same type in the `json` generic:
 
 ```ts
 export const loader: LoaderFunction = () => {
@@ -108,7 +108,7 @@ export const loader: LoaderFunction = () => {
 
 export default function Route() {
   const { birthday } = useLoaderData<MyLoaderData>();
-  // ^ `useLoaderData` tricks Typescript into thinking this is a `Date`, when in fact its a `string`!
+  // ^ `useLoaderData` tricks Typescript into thinking this is a `Date`, when in fact it's a `string`!
 }
 ```
 
@@ -144,7 +144,7 @@ Though `loader` and `useLoaderData` exist together in the same file at developme
 Without the `loader` argument to infer types from, `useLoaderData` needs a way to learn about `loader`'s type at compile-time.
 
 Additionally, `loader` and `useLoaderData` are both managed by Remix across the network.
-While its true that Remix doesn't "own" the network in the strictest sense, having `useLoaderData` return data that does not correspond to its `loader` is an exceedingly rare edge-case.
+While it's true that Remix doesn't "own" the network in the strictest sense, having `useLoaderData` return data that does not correspond to its `loader` is an exceedingly rare edge-case.
 
 Same goes for `useActionData`.
 

integration/fetcher-layout-test.ts

@@ -231,7 +231,7 @@ test("fetcher calls index route loader when at index route", async ({
   expect(dataElement.text()).toBe("index data");
 });
 
-test("fetcher calls layout route action when at paramaterized route", async ({
+test("fetcher calls layout route action when at parameterized route", async ({
   page,
 }) => {
   let app = new PlaywrightFixture(appFixture, page);

integration/helpers/vite-plugin-cloudflare-template/worker-configuration.d.ts

@@ -5135,7 +5135,7 @@ declare module "assets:*" {
 //     https://opensource.org/licenses/Apache-2.0
 declare abstract class PipelineTransform {
   /**
-   * transformJson recieves an array of javascript objects which can be
+   * transformJson receives an array of javascript objects which can be
    * mutated and returned to the pipeline
    * @param data The data to be mutated
    * @returns A promise containing the mutated data

playground/vite-plugin-cloudflare/worker-configuration.d.ts

@@ -4272,7 +4272,7 @@ declare module "assets:*" {
 //     https://opensource.org/licenses/Apache-2.0
 declare abstract class PipelineTransform {
     /**
-     * transformJson recieves an array of javascript objects which can be
+     * transformJson receives an array of javascript objects which can be
      * mutated and returned to the pipeline
      * @param data The data to be mutated
      * @returns A promise containing the mutated data