diff --git a/README.org b/README.org
index c0537d1eb94bcfda9f96509ab9a8a8b788d8ed5a..ca58dbe3546d25919d20ae7682028265c9ad609d 100644
--- a/README.org
+++ b/README.org
@@ -1,105 +1,3 @@
#+TITLE: DOTS Info
-* Table of Contents :TOC:
-- [[#preface-why][Preface, "Why?"]]
-- [[#required-packages][Required Packages]]
- - [[#dots-packages][DOTS Packages]]
-- [[#platform-packages][Platform Packages]]
-- [[#builds][Builds]]
-- [[#entities][Entities]]
-
-* Preface, "Why?"
-Unity is in the midst of a transformation that will fundamentally change the way
-games are written. While those changes are not in the mainstream distribution of
-the engine, it is imminent. This document aims to consolidate and summarise
-information on the requirements and use of this new Data-Oriented Technology
-Stack, and serve as a reference for project setup and development in the future.
-
-It is still a good idea to learn the "classic", object-oriented approach taken
-by both our game development module and the current series of learning materials
-that Unity provides. Much of the programming, concepts and techniques will still
-be useful and will still be necessary with some changes.
-* Required Packages
-** DOTS Packages
-Installing the DOTS packages requires opening the Package Manger within the
-project (Select =Window > Package Manager=), then add by name (select from the
-drop-down "+" menu). Enter the following package names (one at a time):
-+ =com.unity.entities=
-+ =com.unity.rendering.hybrid=
-+ =com.unity.dots.editor=
-+ =com.unity.physics= \leftarrow The re-implementation of the physics engine built on DOTS
-These packages are marked experimental, so be sure to save often and make use of
-good version control practices. Be sure to push changes to the remote repository
-often, and use branches when writing and testing new functionality before merging
-with parent branches.
-
-I expect we will be working simultaneously so we can work out any issues, talk
-about problems etc. together.
-*** Domain Reload
-As noted in the [[https://docs.unity3d.com/Packages/com.unity.entities@0.17/manual/install_setup.html][entities documentation]], Domain Reload occurs when entering play
-mode within the editor, and is especially slow when using DOTS. To disable this,
-enable the "=Enter Play Mode Settings=" checkbox in the =Editor= section of the
-Project Settings, while leaving its child options unchecked.
-* Platform Packages
-It is also necessary to install the DOTS based platform packages for Unity (The
-default tool-chains will not be replaced by default).
-
-Install, in the same way as above, the =com.unity.platforms.<platform>= packages,
-where =<platform>= is the desired target, for example I will install
-=com.unity.platforms.linux= and =com.unity.platforms.windows= to produce binaries
-for Linux and Windows.
-* Builds
-Building through the standard =File > Build and Run= or =<ctrl+b>= will not work
-with DOTS. You must create a "Classic Build Configuration" for each target
-platform through the asset manager:
-
-=+ > Build > <Platform> Classic Build Configuration=
-
-From now on you must build the project by selecting this configuration and using
-the options shown in the inspector.
-* Entities
-In the standard OOP model of game development, functionality is tied to
-individual instances of objects. Each Monobehaviour (the class that from which
-all standard scripts inherit) has its own ~Start()~, ~Update()~, similar and
-accompanying methods. The engine will run all of these sequentially.
-
-In this model, each game object is treated as a collection of data (the entity),
-with this data organised into "components". These components are analogous to a
-struct in C, they are mutable collections of data, they do not have their own
-functionality in the form of methods.
-
-It is the job of a =System= to read and transform the data of the entities. For
-example you may have many entities with a ~Character~ component, each with an
-~hp~ variable. This will include all players, enemies and NPCs. Characters may
-be poisoned during the game, adding a ~Poison~ component to their entity. This
-component will contain a value ~float rate~ to determine how much damage to deal
-each second, and a ~float duration~ to determine how long the character will be
-poisoned for.
-
-You may define a ~StatusSystem~, which manages status effects (in this case
-poisoning). It will operate on all of the entities with a ~Character~ /and/ a
-~Poison~ component, and update the ~hp~ variable based on the data related to
-the poison.
-
-What will this look like? Within the StatusSystem's ~OnUpdate()~ method:
-#+begin_src csharp :exports code
-float dT = Time.DeltaTime;
-
-Entities
- .WithAll<Character, Poison>()
- .ForEach(
- // define the lambda that transforms the data
- (ref Character ch, ref Poison poison, in Entity entity) => {
- ch.hp -= poison.rate * dT;
- poison.duration -= dT;
- if (poison.duration <= 0) // remove the poison component if it has expired
- EntityManager.RemoveComponent<Poison>(entity);
- })
- .ScheduleParallel();
-#+end_src
-
-Some keywords are used in the lambda definition that relate to C#'s implementation:
-+ ~ref~ creates a mutable reference to the given argument
-+ ~in~ creates an immutable reference to the argument (here we are not modifying
- ~entity~, only passing the reference to the ~EntityManager~ in order to remove
- the component)
+I have moved this document to [[https://github.com/OliverMead/dots-guide][github]] for code syntax highlighting and so the table of contents works