Basic wording/link pass (thanks WebStorm)

Author: NotNite

Diff for: .gitignore

@@ -12,10 +12,13 @@ yarn-debug.log*
 yarn-error.log*
 pnpm-debug.log*
 
-
 # environment variables
 .env
 .env.production
 
 # macOS-specific files
 .DS_Store
+
+# shut up
+/.vscode
+/.idea

Diff for: src/content/docs/blog/moonlight-api-v2.md

@@ -7,7 +7,7 @@ authors: [notnite, cynosphere, adryd]
 
 Been a while, eh? The last post we wrote for moonlight was [when we first introduced it](/blog/reintroducing-moonlight). Sounds like it's time to change that!
 
-moonlight development was stalled for a while this year, particularly due to lack of motivation. Less people than expected tinkering with moonlight gave us less reason to update it, and so it fell behind with Discord updates, eventually breaking catastrophically for several months. Thanks to [redstonekasi](https://github.com/redstonekasi) for submitting pull requests for fixing a *lot* of things while none of us had the energy to.
+moonlight development was stalled for a while this year, particularly due to lack of motivation. Fewer people than expected tinkering with moonlight gave us less reason to update it, and so it fell behind with Discord updates, eventually breaking catastrophically for several months. Thanks to [redstonekasi](https://github.com/redstonekasi) for submitting pull requests for fixing a *lot* of things while none of us had the energy to.
 
 About a week ago, [Ari](https://github.com/adryd325) had the idea of making a centralized repository for Discord client mappings. This short conversation would lead to one of the greatest nerdsnipes in moonlight history.
 

Diff for: src/content/docs/dev/helper-scripts.md

@@ -4,7 +4,7 @@ sidebar:
   order: 3
 ---
 
-Inside of the moonlight repository, there is a `scripts` folder with some tools in it.
+Inside the moonlight repository, there is a `scripts` folder with some tools in it.
 
 ## update.js
 

Diff for: src/content/docs/dev/mappings.md

@@ -18,7 +18,7 @@ moonlight.moonmap.addExport("discord/components/common/index", "AIconButRenamed"
 });
 ```
 
-If you're registering your own module, you'll need to find the Webpack module ID. You can do this in a Webpack module using [Spacepack](/ext-dev/api/#spacepack):
+If you're registering your own module, you'll need to find the Webpack module ID. You can do this in a Webpack module using [Spacepack](/ext-dev/api#spacepack):
 
 ```ts
 moonlight.moonmap.addModule(spacepack.findByCode(/* ... */)[0].id, "discord/my/custom/module");

Diff for: src/content/docs/dev/setup.md

@@ -24,17 +24,18 @@ You will need [pnpm](https://pnpm.io), as moonlight uses it for dependency and w
 
 ## Project structure
 
-moonlight is split into a [pnpm workspace](https://pnpm.io/workspaces). The project is comprised of multiple packages:
+moonlight is split into a [pnpm workspace](https://pnpm.io/workspaces). The project contains multiple packages:
 
 - `core`: core code and utilities responsible for loading extensions
 - `injector`: the entrypoint for moonlight loaded by the patched Discord client
   - loads the config and detected extensions from disk and forwards them to the other stages
   - loads host modules
-  - sets up `node-preload` to be ran when the browser window is created
+  - sets up `node-preload` to run when the browser window is created
 - `node-preload`: ran before Discord's code on the Node side
   - receives the config/detected extensions from `injector` and forwards it to `web-preload`
   - loads node modules
-  - loads `web-preload` and forwards some inforation to it
+  - loads `web-preload` and forwards some information to it
+  - starts Discord once everything is ready
 - `web-preload`: ran before Discord's code on the web side
   - receives the loaded config and detected extensions from `node-preload`
   - loads extensions and installs their Webpack modules and patches

Diff for: src/content/docs/ext-dev/api.md

@@ -15,7 +15,7 @@ The global types are available [here](https://github.com/moonlight-mod/moonlight
 
 ## Extension libraries
 
-Remember to [add the module as a dependency](/ext-dev/webpack/#webpack-module-dependencies).
+Remember to [add the module as a dependency](/ext-dev/webpack#webpack-module-dependencies).
 
 ### Context Menu
 

Diff for: src/content/docs/ext-dev/cookbook.md

@@ -55,7 +55,7 @@ Remember to [restart the dev server](/ext-dev/pitfalls#restarting-dev-mode-is-re
 
 Mark the extension as a dependency of your extension:
 
-```ts title="manifest.json"
+```json title="manifest.json"
 {
   "dependencies": ["markdown"]
 }
@@ -112,13 +112,13 @@ export default function MyElement() {
 }
 ```
 
-React [must be imported when using JSX](/ext-dev/pitfalls/#using-jsx).
+React [must be imported when using JSX](/ext-dev/pitfalls#using-jsx).
 
 ## Using Spacepack to find code dynamically
 
 ```ts
 import spacepack from "@moonlight-mod/wp/spacepack_spacepack";
-const { something } = spacepack.findByCode(...)[0].exports;
+const { something } = spacepack.findByCode(/* ... */)[0].exports;
 ```
 
 Remember to add your find to [your extension dependencies](/ext-dev/webpack#webpack-module-insertion) and [declare Spacepack as a dependency](#using-another-extension-as-a-library).

Diff for: src/content/docs/ext-dev/devtools.md

@@ -25,7 +25,7 @@ To see the source of a module, print the function with `spacepack.inspect`:
 spacepack.inspect(/* module ID */)
 ```
 
-The returned value will be a function you can double click to see the module source.
+The returned value will be a function you can double-click to see the module source.
 
 You can chain `inspect` with `findByCode` (or an equivalent) when trying to find the source of a patch in a rush:
 

Diff for: src/content/docs/ext-dev/official-repository.md

@@ -33,9 +33,9 @@ Then, create a pull request to [the official repository][extensions], adding a m
 To prevent extensions from going unmaintained on the official repository, an adoption policy is in place for other developers to take over ownership of an extension. You can adopt an extension in one of the following scenarios:
 
 - You have written consent from a developer to adopt it
-- The extension has been outdated for over 3 months, and the developer did not respond after contact after 7 days
+- The extension has been outdated for over 3 months, and the developer did not respond to contact after 7 days
 
-An extension is defined as "outdated" when its features do not work, the extension crashes the client, or it has not been updated for the latest [API level](/ext-dev/migrating-api-levels/). We encourage developers to reach out for permission in a public space, like GitHub issues or in the moonlight Discord server, so that the response can be verified.
+An extension is defined as "outdated" when its features do not work, the extension crashes the client, or it has not been updated for the latest [API level](/ext-dev/migrating-api-levels). We encourage developers to reach out for permission in a public space, like GitHub issues or in the moonlight Discord server, so that the response can be verified.
 
 [extensions]: <https://github.com/moonlight-mod/extensions>
 
@@ -47,7 +47,7 @@ Extensions that violate the following rules cannot be submitted to the official
   - Examples: animated custom statuses, rainbow roles, scheduled messages, automatic message responses (like a bot would to a command), mass deleting messages
 - Respect the privacy of other users. No logging of other users' actions or long-term scraping of the Discord API.
   - Examples: message loggers/"anti delete", message archival, read states via "hidden pixel" tracking
-- Respect the privacy of the user. Interactions with third party services must be clearly denoted inside of the plugin tagline or description.
+- Respect the privacy of the user. Interactions with third party services must be clearly denoted inside the extension tagline or description.
   - Examples: HTTP APIs
 
 If you're unsure if your extension can be submitted or not, feel free to ask!

Diff for: src/content/docs/ext-dev/pitfalls.md

@@ -7,21 +7,21 @@ sidebar:
 
 ## Web vs Node.js
 
-Node.js code cannot be imported directly from the web side. You must use `moonlight.getNatives`. See [the cookbook](/ext-dev/cookbook/#sharing-code-between-nodejs-and-the-web) for how to access Node.js exports.
+Node.js code cannot be imported directly from the web side. You must use `moonlight.getNatives`. See [the cookbook](/ext-dev/cookbook#sharing-code-between-nodejs-and-the-web) for how to access Node.js exports.
 
 ## Webpack require is not Node.js require
 
 The `require` function used in Webpack modules and patches is not the same as the function in Node.js. Instead, it lets you require other Webpack modules by their IDs.
 
-If you have a Webpack module you want to load, [you can require it by its ID](/ext-dev/webpack/#importing-other-webpack-modules).
+If you have a Webpack module you want to load, [you can require it by its ID](/ext-dev/webpack#importing-other-webpack-modules).
 
 ## The web entrypoint is not a Webpack module
 
-You cannot use Webpack modules inside of `index.ts`, because it is loaded before Webpack is initialized. Instead, [create your own Webpack module](/ext-dev/webpack/#webpack-module-insertion) and use that.
+You cannot use Webpack modules inside of `index.ts`, because it is loaded before Webpack is initialized. Instead, [create your own Webpack module](/ext-dev/webpack#webpack-module-insertion) and use that.
 
 ## Webpack modules only load when required
 
-By default, Webpack modules will not load unless they are required by another module or the `entrypoint` flag is set. If you need a module to run as soon as possible, [set the entrypoint flag](/ext-dev/webpack/#webpack-module-insertion).
+By default, Webpack modules will not load unless they are required by another module or the `entrypoint` flag is set. If you need a module to run as soon as possible, [set the entrypoint flag](/ext-dev/webpack#webpack-module-insertion).
 
 ## Spacepack findByCode matching itself
 
@@ -76,7 +76,7 @@ import { someState } from "@moonlight-mod/wp/yourExtension_someModule";
 const { someState } = require("yourExtension_someModule");
 ```
 
-Remember to [type your module](/ext-dev/webpack/#importing-other-webpack-modules) when using import statements.
+Remember to [type your module](/ext-dev/webpack#importing-other-webpack-modules) when using import statements.
 
 ## Restarting dev mode is required in some scenarios
 

Diff for: src/content/docs/ext-dev/webpack.md

@@ -160,7 +160,7 @@ You can specify:
 
 - Extension IDs and Webpack module names (e.g. `{ ext: "common", id: "stores" }`)
   - Use this if you're using [an extension library](/ext-dev/api).
-  - Make sure to [mark the extension as a dependency](/ext-dev/cookbook/#using-another-extension-as-a-library) in your extension manifest.
+  - Make sure to [mark the extension as a dependency](/ext-dev/cookbook#using-another-extension-as-a-library) in your extension manifest.
 - Webpack module names (e.g. `{ id: "discord/Dispatcher" }`)
   - Use this if you're using [mappings](/ext-dev/mappings).
 - Strings and regexes to match against other modules
@@ -206,7 +206,7 @@ Remember to [add the module as a dependency](#webpack-module-dependencies).
 
 ## Common patterns
 
-You will see familiar things when [reading Discord Webpack modules](/ext-dev/devtools/#reading-module-sources):
+You will see familiar things when [reading Discord Webpack modules](/ext-dev/devtools#reading-module-sources):
 
 - The pattern `n(/* some number */)` represents a require, and is another module ID inside of the argument. You can pass that module ID to `spacepack.inspect` to read the required module source.
 - `Z` and `ZP` usually correspond to `default` exports.

Diff for: src/content/docs/using/why-moonlight.mdx

@@ -25,7 +25,7 @@ A common question we get is what moonlight does differently, and why it's worth
     Modify any piece of code you want using regex or ASTs, or add your own code as a Webpack module
   </Card>
   <Card title="Open extension system" icon="puzzle">
-    [Develop extensions locally](/ext-dev/getting-started/#build-and-run-the-extension) or [make a third party repository](/ext-dev/getting-started/#publishing-to-github-pages), no recompiling moonlight required
+    [Develop extensions locally](/ext-dev/getting-started#build-and-run-the-extension) or [make a third party repository](/ext-dev/getting-started#publishing-to-github-pages), no recompiling moonlight required
   </Card>
   <Card title="Community-made mappings" icon="seti:code-search">
     [Community-maintained mappings of the Discord client](https://github.com/moonlight-mod/mappings), available as a library