Merge pull request #373 from lukajk1/fix/typos-in-docs

fix minor typos in 'your first shaderpack'

Author: jbritain

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

@@ -7,7 +7,7 @@ sidebar:
 ---
 
 
-## Foreward
+## Foreword
 This tutorial is based on one written by [saadam1n](https://github.com/saadam1n/MinecraftShaderProgramming). This newer tutorial has been necessitated by the fact that since the tutorial was written, the general state of development on Minecraft shaders has advanced somewhat, and other developers have identified several areas where this can be improved.
 
 ## Prerequisites
@@ -36,10 +36,10 @@ For the next part it is important to note that since most of the game's developm
 
 ## How Shaders Work
 
-A "shader" is, by definition, any program that is executed on the GPU. For Minecraft, these shader programs (also know as passes) can be sorted into two distinct categories: fullscreen passes, which execute for the entire screen, and gbuffers passes, which execute only for specific geometry. Each individual program is composed of several shader stages, two of which are required: a vertex shader, which executes once for each vertex of the geometry, and a fragment shader, which executes once for every pixel that covers the geometry. You can optionally include a compute, geometry, and/or tessellation stage for each pass.
+A "shader" is, by definition, any program that is executed on the GPU. For Minecraft, these shader programs (also known as passes) can be sorted into two distinct categories: fullscreen passes, which execute for the entire screen, and gbuffers passes, which execute only for specific geometry. Each individual program is composed of several shader stages, two of which are required: a vertex shader, which executes once for each vertex of the geometry, and a fragment shader, which executes once for every pixel that covers the geometry. You can optionally include a compute, geometry, and/or tessellation stage for each pass.
 
 :::tip[CPU vs GPU]
-Odds are, all your previous code has been executed on the CPU. Shaders are instead executed on the GPU (also know as a graphics or video card). CPUs are great at performing complex sequential tasks, whereas GPUs are great are executing simple tasks in parallel. In fact, modern high-end graphics cards are capable of performing *trillions* of calculations per second! You can read more about the differences [here](https://www.intel.com/content/www/us/en/products/docs/processors/cpu-vs-gpu.html).
+Odds are, all your previous code has been executed on the CPU. Shaders are instead executed on the GPU (also known as a graphics or video card). CPUs are great at performing complex sequential tasks, whereas GPUs are great at executing simple tasks in parallel. In fact, modern high-end graphics cards are capable of performing *trillions* of calculations per second! You can read more about the differences [here](https://www.intel.com/content/www/us/en/products/docs/processors/cpu-vs-gpu.html).
 :::
 
 For a full list of programs and what they do, see the [Iris Docs](/current/reference/programs/overview/).

src/content/docs/current/Guides/Your First Shaderpack/1_composite.mdx

@@ -64,7 +64,7 @@ Every shader's first line must be a version declaration. GLSL has two profiles:
 out vec2 texcoord;
 ```
 
-This is a variable declaration, but a special one. The `out` keyword means that the value will be passed to the fragment shader. The fragment shader can then have a corresponding `in` declaration which allows it to recieve this value. In older versions of GLSL, both `in` and `out` were represented with the `varying` keyword, thus variables passed between programs are often referred to as 'varyings'.
+This is a variable declaration, but a special one. The `out` keyword means that the value will be passed to the fragment shader. The fragment shader can then have a corresponding `in` declaration which allows it to receive this value. In older versions of GLSL, both `in` and `out` were represented with the `varying` keyword, thus variables passed between programs are often referred to as 'varyings'.
 
 :::note[Note]
 Values passed from vertex shaders to fragment shaders are interpolated! This means that if one vertex has a value of 0, and another has a value of 1, then a pixel halfway between these two vertices will have a value of 0.5. This can be prevented by adding the `flat` keyword the `in` and `out` declarations.

src/content/docs/current/Guides/Your First Shaderpack/2_gbuffers.mdx

@@ -92,7 +92,7 @@ normal = gl_NormalMatrix * gl_Normal; // this gives us the normal in view space
 normal = mat3(gbufferModelViewInverse) * normal; // this converts the normal to world/player space
 ```
 
-If you reload your shader, you will notice that there is an error that we have not defined `gbufferModelViewInverse`. To get this value, we declare it as a `uniform` before the `main` function. Uniforms are accessable by any shader program and have the same value wherever you access them. They are calculated on the CPU and uploaded to the GPU.
+If you reload your shader, you will notice that there is an error that we have not defined `gbufferModelViewInverse`. To get this value, we declare it as a `uniform` before the `main` function. Uniforms are accessible by any shader program and have the same value wherever you access them. They are calculated on the CPU and uploaded to the GPU.
 
 ```glsl
 uniform mat4 gbufferModelViewInverse;
@@ -157,7 +157,7 @@ if (color.a < alphaTestRef) { // alpha test
 ```
 
 - The first step multiplies the color by `glcolor` to get the biome tint.
-- The second step multiplies the color by Minecraft's defualt lighting color. You should remove this, as we are going to do our own lighting.
+- The second step multiplies the color by Minecraft's default lighting color. You should remove this, as we are going to do our own lighting.
 - Finally, if the color's alpha (transparency) is less than `alphaTestRef` (this is set by Iris, but usually 0.1), we `discard`, which tells the shader program to return and not write anything. This potentially saves us some texture writes.
 
 ## Writing Extra Data

src/content/docs/current/Guides/Your First Shaderpack/4_shadows.mdx

@@ -62,7 +62,7 @@ This is actually all we need to get Iris rendering a shadow map. Let's now go ba
 
 ## Reading the Shadow Map
 
-The shadow map is accessable as `shadowtex0`, so let's add this as a `sampler2D`.
+The shadow map is accessible as `shadowtex0`, so let's add this as a `sampler2D`.
 
 ```glsl
 uniform sampler2D shadowtex0;