Fixed some typos in the documentation.

Author: kblaschke

docs/Compiler-Internals.md

@@ -21,7 +21,7 @@ scanner looks for these kinds of symbols, with letters always being case-insensi
 - Numbers in integer and floating-point notation with an optional exponent. Note that these numbers are always positive,
   negativity is applied later via the `-` unary operator in the parser.
 - Identifiers starting with an underscore or alphabetical letter, and also numbers on any following character.
-  These can be returned as two diffent tokens:
+  These can be returned as two different tokens:
     - If the (lower-case) name exists in the function table, the name is returned as a `FUN` token.
     - Anything else is returned as a `VAR` token and identifies a variable.
 
@@ -140,7 +140,7 @@ type `prjm_eval_compiler_node`, which stores a few additional flags only require
 #### Function Argument List
 
 Inside a function argument list, all expressions are collected in a special `prjm_eval_compiler_arg_list` wrapper holding
-one compiler node object for each potential function argument. It also keeps the arugment count as a separate variable
+one compiler node object for each potential function argument. It also keeps the argument count as a separate variable
 for easy access.
 
 When the arguments have been collected and the function is reduced in the parser, the action will then compare the

docs/Expression-Syntax.md

@@ -59,7 +59,7 @@ z = sin(4.0);
 
 ### Variable and Function Names, Limits
 
-Variable and function names are generally case-insensitve, making `variable` equivalent to `vArIaBlE`.
+Variable and function names are generally case-insensitive, making `variable` equivalent to `vArIaBlE`.
 
 Any text in expressions - starting with either a letter from a to z or an underscore, followed by more of these
 characters and also numbers from 0 to 9 - is first checked to be a built-in function. If it is not a function, the
@@ -81,7 +81,7 @@ in the same way as gmegabuf.
 Note the index must always be written with two digits. `reg3` is _not_ considered a global variable and will only have a
 local scope as any other variable. The same is true for more digits like `reg123`.
 
-Same as with gmegabuf, global variables are not necessarily `0` when a preset is initialized and they can change at any
+Same as with gmegabuf, global variables are not necessarily `0` when a preset is initialized, and they can change at any
 time when two presets using the same global variables are blended during a transition.
 
 ### Constants
@@ -121,7 +121,7 @@ Example: `$'a'` converts to `97`.
 
 ### Operator Precedence
 
-Operator precedence is defined in a similar way as in C, with the expection of the `^` operator, which has a different
+Operator precedence is defined in a similar way as in C, except the `^` operator, which has a different
 meaning in Milkdrop presets (pow() instead of binary XOR).
 
 See the [C precedence table on cppreference.com](https://en.cppreference.com/w/c/language/operator_precedence) for
@@ -515,7 +515,7 @@ level, which can hang up the application.
 ### Internal Functions and Aliases
 
 The following functions are defined internally, some being aliases to the above functions, others being used as actual
-implementations of operators. Deoending on the operator being unary or binary, each function has one or two parameters.
+implementations of operators. Depending on the operator being unary or binary, each function has one or two parameters.
 
 - _aboeq => Operator `>=`
 - _above => Operator `>`