Updated README

Author: Blitzy

Assets/Scenes.meta

@@ -7,28 +7,25 @@ The UI Manager is a stack-based UI controller class. It is designed to make push
 The core functionality of UI Manager is made up of only two simple classes: `UIManager` and `Screen`.
 
 ### UIManager
-`UIManager` is responsible for instantiating and maintaining the screen stack. When you want to push or pop a screen to the stack, you interact with `UIManager`. `UIManager` has a few prerequisites that should be understood when using it:
+`UIManager` is responsible for instantiating and maintaining the screen stack. When you want to push or pop a screen to the stack, you interact with `UIManager`.  
+
+`UIManager` has a few prerequisites that should be understood when using it:
 
 > ### Prerequisites
-> 
-> > 1. **IUpdateTransmitter**
-> > UIManager is built on top of the IUpdateTransmitter and IUpdateObserver interfaces. UIManager is
-> > an IUpdateObserver that needs to register with an IUpdateTransmitter in order to receive
-> > 'OnUpdate' calls every frame.  
 > >
-> > 2. **Screen Prefab Folder**
+> > 1. **Screen Prefab Folder**
 > > The UIManager looks for screen prefabs by name inside a specific folder that you specify in the 
 > > constructor. This folder must reside within a folder called 'Resources' in the Unity project.
 > > 
 > >     ![Prefab Directory](_images/prefab_directory.png)  
 > >     *Example of a screen prefab directory structure.*
 > > 
 > > 
-> > 3. **UI Root Canvas**  
+> > 2. **UI Root Canvas**  
 > > The UI Manager organizes all screens underneath a root Canvas object. You must provide the UI
 > > Manager what Canvas object you want to use for this purpose.
 > > 
-> > 4. ***Optional* UI Camera**
+> > 3. ***Optional* UI Camera**
 > > If you want to render your UI with a seperate Unity Camera you can pass it to the UIManager 
 > > inside the constructor. By default, Unity does not use a seperate Camera to render UI elements,
 > > so this isn't necessary unless you need it.
@@ -96,13 +93,13 @@ The core functionality of UI Manager is made up of only two simple classes: `UIM
 > to you as the developer to decide how to use in your project.
 >
 > ### Core Fields
-> > ####keepCached
+> > #### keepCached
 > > `UIManager` gives you the option to disable a screen object instead of destroying it completely when 
 > > the screen is popped from the stack. This will keep the screen object cached in memory and when it is 
 > > pushed to the stack again will reuse the cached object instead of instancing a new one from the prefab.
 >
 > ### Core Methods
-> > ####OnSetup
+> > #### OnSetup
 > > `OnSetup` is called after instantiating a screen prefab. It is only called once for the lifecycle of 
 > > the `Screen`.
 > > #### OnPush
@@ -139,7 +136,7 @@ Included with the core `UIManager` classes is an example scene with example scri
 Open the scene *UIExample* inside the *Example* folder.
 
 Press play in the editor and play with the example to get a grasp of how it is organized.
-When you're ready to look at the setup process and various screens in detail you should start by looking at the script `UI/Examples/Scripts/GameManager.cs`
+When you're ready to look at the setup process and various screens in detail you should start by looking at the script `UIManager/Examples/Scripts/GameManager.cs`
 
 This script is the entry point for the example and is where the `UIManager` is setup and the first screen is pushed onto the stack.