add vs code extension links, clean up some development info

Author: jbritain

src/content/docs/current/Guides/Your First Shaderpack/0_intro.mdx

@@ -16,14 +16,24 @@ This tutorial is based on one written by [saadam1n](https://github.com/saadam1n/
 :::
 
 You will need:
-- A suitable text editor for modifying shader code. One popular choice is [Visual Studio Code](https://code.visualstudio.com/), but any program which can edit text files is sufficient. A simpler but popular editor is [Notepad++](https://notepad-plus-plus.org/).
+- A suitable text editor for modifying shader code (see below).
 - A computer capable of running OpenGL 3.3. If your computer was manufactured in the last 15 years it likely supports OpenGL 3.3. Note that whilst OpenGL works on macOS, Apple will not update the drivers to support any version past OpenGL 4.1 and some things may not work correctly.
 - A willingness to learn. Shaders are hard, and you can't just pick them up overnight. Do not expect to complete this tutorial and become the next Sonic Ether.
 - An instance of Minecraft with Iris, Optifine, or Oculus installed. Since this tutorial is in the Iris documentation, it is assumed you are using Iris.
 
+## Development Environment
+
+Any text editor is suitable for shader development. One popular choice is [Visual Studio Code](https://code.visualstudio.com/), but any program which can edit text files is sufficient. A simpler but popular editor is [Notepad++](https://notepad-plus-plus.org/).
+
+If you are using Visual Studio Code (which we recommend), there are a couple of extensions you can use which can help with development.
+
+- [GLSL Syntax for VS Code](https://marketplace.visualstudio.com/items?itemName=GeForceLegend.vscode-glsl)
+- [Language Server for Minecraft Shaderpacks](https://marketplace.visualstudio.com/items?itemName=GeForceLegend.vscode-mcshader)
+
 It's helpful to be able to see your game logs as the game is running. In the vanilla Minecraft launcher, you can do this by enabling 'keep the Launcher open while games are running' and 'Open output log when Minecraft: Java Edition starts" in the settings.
 If you do not use the vanilla launcher, but your launcher does not support viewing logs in realtime, a popular choice is [Prism Launcher](https://prismlauncher.org/).
-In Iris, it is also useful to enable debug mode. You can do this by pressing <kbd>Ctrl</kbd>+<kbd>D</kbd> in the shader selection screen.
+
+It is also useful to enable debug mode. You can do this by pressing <kbd>Ctrl</kbd>+<kbd>D</kbd> in the shader selection screen. For more info, see [debugging shaders](/current/reference/miscellaneous/debugging_shaders/).
 
 
 ## OpenGL and GLSL
@@ -43,3 +53,4 @@ Odds are, all your previous code has been executed on the CPU. Shaders are inste
 :::
 
 For a full list of programs and what they do, see the [Iris Docs](/current/reference/programs/overview/).
+

src/content/docs/current/Reference/Miscellaneous/debug_mode.mdx

@@ -16,10 +16,10 @@ The 'Use no error context' setting will prevent the game from loading on some AM
 # Finding Compilation Errors
 Iris does not have proper support for line numbers in error messages. Line numbers in error messages correspond to the patched version of your shader code, which will not necessarily line up with the line numbers in your original code, especially if you have made use of the `#include` directive. The patched shader output can be found in the `.minecraft/patched_shaders`. Here's an example.
 
-![`deferred2.fsh: ERROR: 0:336: 'something' : undeclared identifier`](../../../../assets/debugging/compilationerror.webp)
+![`deferred2.fsh: ERROR: 0:336: 'something' : undeclared identifier`](../../../../../assets/debugging/compilationerror.webp)
 In this error message, we can see that the error occurs on line 336 of `deferred2.fsh`.
 
-![line 336 says "something = 0;"](../../../../assets/debugging/patchederror.webp)
+![line 336 says "something = 0;"](../../../../../assets/debugging/patchederror.webp)
 Opening `.minecraft/patched_shaders/005_deferred2.fsh` and navigating to line 336, we can see the line causing the error. Using the surrounding context, and perhaps the find+replace option in your text editor/IDE, you should be able to find the offending line.
 
 # Attaching a Debugger

…ocs/current/How To/debugging_shaders.mdx …ence/Miscellaneous/debugging_shaders.mdxsrc/content/docs/current/How To/debugging_shaders.mdx renamed to src/content/docs/current/Reference/Miscellaneous/debugging_shaders.mdx src/content/docs/current/How To/debugging_shaders.mdx renamed to src/content/docs/current/Reference/Miscellaneous/debugging_shaders.mdx

@@ -8,16 +8,16 @@ sidebar:
 
 The source code of a shader pack is not the final code that is compiled and executed. In order to ensure maximum compatibility, Iris runs the shader code through [glsl-transformer](https://github.com/IrisShaders/glsl-transformer), which generates **patched shader code**. This is the code that actually ends up on the GPU. In the context of developing shaders, there are several important consequences to note:
 
-- Since the patcher removes non-necessary whitespace in the code, line numbers in errors will not match up with the line numbers in your code
+- Since the patcher removes non-necessary whitespace in the code, line numbers in errors will not match up with the line numbers in your code.
 - You cannot name your functions or variables in a similar manner as internal Iris variables:
     - `iris_`
     - `irisMain`
     - `moj_import`
-- The patcher will sometimes fix code that should otherwise fail
-- Conversely, the patcher may not be flawless. If you're experiencing a bug and have exhausted all other possibilites, its worth checking the patched shader code
+- The patcher will sometimes fix code that should otherwise fail.
+- Conversely, the patcher may not be flawless. If you're experiencing a bug and have exhausted all other possibilites, it's worth checking the patched shader code.
 
 :::tip
-When [debug mode](/current/reference/miscellaneous/patcher/) is enabled, the patched shader code can be found in the `/patched_shaders/` folder in the root of your Minecraft directory.
+When [debug mode](/current/reference/miscellaneous/debugging_shaders/) is enabled, the patched shader code can be found in the `/patched_shaders/` folder in the root of your Minecraft directory.
 :::
 
 More information can be found [here](https://github.com/IrisShaders/Iris/blob/1.21/docs/usage/debugging.md).