pr feedback

Author: pcattori

decisions/0012-type-inference.md

@@ -50,7 +50,7 @@ There are three major aspects to typesafety in a framework like React Router:
 
    Unlike the `useParams` generic, this isn't just a type cast.
    The `useLoaderData` generic ensures that types account for serialization across the network.
-   However, it still requires you to type of `typeof loader` every time.
+   However, it still requires you to add `typeof loader` every time.
 
    Not only that, but complex routes get very tricky to type correctly.
 
@@ -188,12 +188,12 @@ import * as Types from "./+types.product-details";
 ```
 
 TypeScript will even give you import autocompletion for the typegen file and the `+` prefix helps to distinguish it as a special file.
-Big thanks to Svelte Kit for showing us that `rootDirs` trick!
+Big thanks to Svelte Kit for showing us that [`rootDirs` trick](https://svelte.dev/blog/zero-config-type-safety#virtual-files)!
 
 ### TypeScript plugin
 
-Typegen gets a bad rap because its a hassle when typegen'd files are out-of-date.
-Most typegen solutions require you to then rerun a script to update the typegen'd files.
+Typegen solutions often receive criticism due to typegen'd files becoming out of sync during development.
+This happens because many typegen solutions require you to then rerun a script to update the typegen'd files.
 
 Instead, our typegen will automatically run within a TypeScript plugin.
 That means you should never need to manually run a typegen command during development.