Update documentation

Author: adamgraham

Documentation~/articles/attributes.md

@@ -6,7 +6,7 @@ slug: "/manual/attributes"
 
 The **Architecture Toolkit** includes a few different C# attributes that are useful to customize the editor interface for custom data structures and behaviours without needing to write custom editor scripts.
 
-<br/>
+<hr/>
 
 ### [[ConditionalShow]](/api/Zigurous.Architecture/ConditionalShowAttribute)
 
@@ -17,7 +17,8 @@ Shows the field in the editor based on the state of another field.
 public bool useCustomValue;
 [ConditionalShow(nameof(useCustomValue))]
 public float customValue;
-
+```
+```csharp
 // enum condition
 public Axis axis;
 [ConditionalShow(nameof(axis), (int)Axis.X)]
@@ -39,7 +40,8 @@ Hides the field in the editor based on the state of another field.
 public bool useDefaultValue;
 [ConditionalHide(nameof(useDefaultValue))]
 public float customValue;
-
+```
+```csharp
 // enum condition
 public Option option;
 [ConditionalHide(nameof(option), (int)Option.B)]

Documentation~/articles/behaviours.md

@@ -6,7 +6,7 @@ slug: "/manual/behaviours"
 
 The **Architecture Toolkit** includes several behaviours that can be used across an application. All of the behaviours derive from `MonoBehaviour`.
 
-<br/>
+<hr/>
 
 ### [CursorLockState](/api/Zigurous.Architecture/CursorLockState)
 

Documentation~/articles/data-structures.md

@@ -6,7 +6,9 @@ slug: "/manual/data-structures"
 
 The **Architecture Toolkit** contains various data structures that may be useful throughout a project. The following data structures are available in the package:
 
-## Accumulators
+<hr/>
+
+## 🎲 Accumulators
 
 Accumulators work like a reducer function by accumulating a set of values into a single total value except you can store the values using identifiers. This is useful to accumulate values over time while adding and removing values as needed. The total value is updated automatically any time a value is added or removed.
 
@@ -24,7 +26,7 @@ Supported types:
 
 <hr/>
 
-## Ranges
+## 🎚️ Ranges
 
 Ranges allow you to specify a lower and upper bound which can then be used for a multitude of purposes including clamping values, interpolating numbers, generating random values, and more.
 
@@ -47,7 +49,7 @@ Included types:
 
 <hr/>
 
-## Misc
+## 💾 Misc
 
 - [Bitmask](/api/Zigurous.Architecture/Bitmask) - A bitmask representation that can be used for bitwise operations.
 - [Bool3](/api/Zigurous.Architecture/Bool3) - Stores a tuple of 3 booleans

Documentation~/articles/events.md

@@ -6,20 +6,20 @@ slug: "/manual/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.
 
-<br/>
+<hr/>
 
-### Game Event
+## 📅 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.
 
 <hr/>
 
-### Game Event Listener
+## 🎧 Game Event Listener
 
 A [GameEventListener](/api/Zigurous.Architecture/GameEventListener) component can be added to any game object that needs to listen for an event. This is a class that derives from `MonoBehaviour` and will register and unregister itself as a listener for the specified event. The listener also declares a standard `UnityEvent` response property that is invoked when the event is raised.
 
 <hr/>
 
-### Event Reference
+## 🎫 Event Reference
 
 The [EventReference](/api/Zigurous.Architecture/EventReference) class allows a `UnityEvent` or `GameEvent` to be referenced. The option to switch between the two choices is available in the editor. Anywhere you might declare a variable as a `UnityEvent` or a `GameEvent` consider declaring it as an `EventReference` for more flexibility.

Documentation~/articles/scriptable-variables.md

@@ -12,7 +12,9 @@ For example, the player can declare their hitpoints as a `FloatVariable` instead
 
 The downside with this is it can be cumbersome to create assets for every variable declared in a behaviour. 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).
 
-### Supported Types
+<hr/>
+
+## 📜 Supported Types
 
 - Bool
 - Bounds

Documentation~/articles/utilities.md

@@ -6,7 +6,7 @@ slug: "/manual/utilities"
 
 The **Architecture Toolkit** includes several utility classes that may be useful under specific situations.
 
-<br/>
+<hr/>
 
 ### [HashCode](/api/Zigurous.Architecture/HashCode)