diff --git a/README.md b/README.md
index ec61c1a..adefba0 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@ Lightweight Alpine Docker container that runs Robot Framework using Selenium Chr
 
 This repository has a Dockerfile that creates a container to run Robot Framework scripts locally, avoiding the hassles of setting up Python and Robot Framework locally.
 
-### Versioning
+## Versioning
 
 * robotframework: latest
 * robotframework-seleniumlibrary: latest
@@ -14,10 +14,15 @@ This repository has a Dockerfile that creates a container to run Robot Framework
 * Chrome webdriver: latest
 * Chromium browser: latest
 
-### Pre-requisites
+## Pre-requisites
 
 Docker should be already installed and running.
 
+## Assumptions
+
+All of the helper scripts here are written for Mac/Linux in bash.  It should be possible to translate these over to a Windows equivilant or possibly use WSL (Windows Subsystem For Linux) to run these.
+
+## Setup
 
 ### 1) Create docker image and shared volume:
 
@@ -122,7 +127,7 @@ Found a work around for Chrome error in headless mode here which eliminates the
 
 ## Disclaimer
 
-* I build this mainly to use for my own personal use.  YMMV. 
+* I built this for my own personal use.  YMMV. 
 * It works on my system :)
 * It is pitch black. You are likely to be eaten by a grue.
 
diff --git a/presentation/Robot Framework.pdf b/presentation/Robot Framework.pdf
new file mode 100644
index 0000000..a863ebf
Binary files /dev/null and b/presentation/Robot Framework.pdf differ
diff --git a/tests/g-resource/common.robot b/tests/g-resource/common.robot
index 590a079..24e8f0f 100644
--- a/tests/g-resource/common.robot
+++ b/tests/g-resource/common.robot
@@ -6,7 +6,6 @@ Library             DateTime
 ${URL}  https://www.thecrumb.com
 ${BROWSER}  headlesschrome
 
-
 *** Keywords ***
 Setup Browser
   Open Browser          ${URL}   ${BROWSER}
diff --git a/todo.md b/todo.md
deleted file mode 100644
index c955d12..0000000
--- a/todo.md
+++ /dev/null
@@ -1,17 +0,0 @@
-1) Setup resource dir and add common - move crhome setup there so tests are simpler looking
-will explain that during preso
-
-2) come up with some simple tests that progressively get more complex
-
-- open browser
-- take screenshot
-- screen size examples
-- variables
-- keywords
-- settings
-- debugging
-- running tests, suites, etc
-
-
-See other examples...
-