Fix documentation typos

Author: adamgraham

Documentation~/articles/behaviors.md

@@ -52,4 +52,4 @@ Invokes timed events at a set interval and/or duration.
 
 ### [UpdateBehaviour](/api/Zigurous.Architecture/UpdateBehaviour)
 
-An abstract class to derive from that can run in any update mode. The update mode can be changed as needed without occuring any additional performance cost.
+An abstract class to derive from that can run in any update mode. The update mode can be changed as needed without incurring any additional performance cost.

Documentation~/articles/events.md

@@ -4,13 +4,13 @@ slug: "/manual/events"
 
 # Events
 
-Events are powerful tool provided by Unity. The **Architecture Toolkit** extends this system by allowing events to be saved as ScriptableObjects. This means the same event can be referenced and listened to by multiple systems throughout the project.
+Events are a powerful tool provided by Unity. The **Architecture Toolkit** extends this system by allowing events to be saved as ScriptableObjects. This means the same event can be referenced and listened to by multiple systems throughout the project.
 
 <hr/>
 
 ## 📅 Game Event
 
-An event can be created through the Asset menu, `Zigurous > Events > Game Event`. There are no properties on an event, but they can be extended further with subclasses if needed. See the [GameEvent](/api/Zigurous.Architecture/GameEvent) Scripting API.
+An event can be created through the Asset menu, `Zigurous > Events > Game Event`. There are no properties on an event, but they can be extended with subclasses if needed. See the [GameEvent](/api/Zigurous.Architecture/GameEvent) Scripting API.
 
 <hr/>
 

Documentation~/articles/scriptable-variables.md

@@ -10,7 +10,7 @@ All of these variables can be created through the Asset menu, `Zigurous > Variab
 
 For example, the player can declare their hitpoints as a `FloatVariable` instead of a `float`. A health bar script would also declare a hitpoints property as a `FloatVariable`. Both behaviors could reference the same variable asset without needing any dependencies between them.
 
-The downside with this is it can be cumbersome to create assets for every variable declared in a behavior. Instead of declaring `FloatVariable` we can declare a `FloatReference` for additional flexibility. This allows the value to either be a constant value or a reference to a variable asset; the choice is customizable in the editor. These reference types derive from [ValueReference\<TValue, TVariable\>](/api/Zigurous.Architecture/ValueReference-2).
+The downside with this is it can be cumbersome to create assets for every variable declared in a behavior. Instead of declaring `FloatVariable` we can declare a `FloatReference` for additional flexibility. This allows the value to be a fixed value or a reference to a variable asset; the choice is customizable in the editor. These reference types derive from [ValueReference\<TValue, TVariable\>](/api/Zigurous.Architecture/ValueReference-2).
 
 <hr/>
 

Runtime/Behaviors/UpdateBehaviour.cs

@@ -4,7 +4,7 @@ namespace Zigurous.Architecture
 {
     /// <summary>
     /// A behavior that can run in any update mode. The update mode can be
-    /// changed as needed without occuring any additional performance cost.
+    /// changed as needed without incurring any additional performance cost.
     /// </summary>
     public abstract class UpdateBehaviour : MonoBehaviour
     {